Skip to content
Recued
Menu
← Back to recipes

Google Task closure watcher timeout

by recued-core v1

Low-frequency timeout role for recued-core/google-tasks-task-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Complete workflow

Workflow pack for Recued-created Google Tasks tasks. It composes the Google Tasks capability pack with a closure ledger: create one owner-approved active task in an existing task list, persist only the connection/list/task linkage in data.shared, and let a scheduled watcher re-read that exact task until Google Tasks reports completion. This pack does not replace Google Tasks due dates, reminders, list organization, task moves, assignment-source behavior, hidden/deleted task handling, clear-completed cleanup, daily planning, or general task dashboards; it adds Recued-visible closure state for Google Tasks tasks Recued created.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Google Task closure watcher timeout
This recipe Background automation

Low-frequency timeout role for recued-core/google-tasks-task-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

googlewatchertimeoutowner-review
by recued-core pinned v1

Workflow origin for the Google Tasks task closure loop. It reads one task list for context, creates exactly one owner-approved active Google Task through recued-core.google-tasks.task.create, and when the task succeeds it seeds durable data.shared closure state for google-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not complete, update, delete, move, reorder, rename lists, mutate links, touch hidden/deleted or assignment-source fields, clear completed tasks, or otherwise mutate Google Tasks beyond the approved task create.

googlegoogle-taskstodotasks
by recued-core pinned v1
Google Task closure watcher
Background automation

Scheduled adopter for Google Tasks task closure rows seeded by create-google-task-with-closure. It lists only Recued-originated Google Task watches, re-reads a bounded batch of Google Task, and closes the shared row when Google Tasks reports completion. Rows that cannot be read remain open instead of closing from cached state. It can notify the owner on completion, but it never creates, updates, completes, deletes, moves, reorders, renames lists, mutates links, touches hidden/deleted or assignment-source fields, clears completed tasks, or otherwise mutates Google Tasks.

googlegoogle-taskstodotasks
by recued-core pinned v1

Owner-visible list/close role for recued-core/google-tasks-task-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.

googlewatcherreviewclose
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 16 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch
active_watches ?
Process (15 steps)
now date_add
Add 0 minutes to
rows_with_timeout filter
Filter by condition
timeout_checks is_past
Check if is in the past
expired_checks filter
Filter by condition
expired_rows map
Extract from each item
timeout_rows slice
Take a subset of
timeout_count count
Count items in timeout rows
timeout_keys replace
Replace text in item key
timeout_values merge
Combine objects together
write_timed_out ?
delete_active ?
skip: item.result.ok not_equal true
moved_rows filter
Filter by condition
moved_count count
Count items in moved rows
notify_owner ?
skip: step.moved_rows is_empty
summary to_summary
Format results as a summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

channels setting = in_app
batch limit setting = 25

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Send notifications
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

Tags

google watchertimeoutowner-reviewclosed-looprole:timeoutbundle:google-tasks-task-closure

Details

16 steps 2 configurable settings recipe_id: timeout-google-tasks-task-closure-watches