Low-frequency timeout role for recued-core/canva-comment-reply-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.
Canva comment reply closure watcher timeout
Low-frequency timeout role for recued-core/canva-comment-reply-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
Canva Comment Reply Closure Loop
4 pinned recipes
Workflow pack for Recued-sent Canva comment replies. It composes the Canva capability pack with a closure ledger: reply once to an existing Canva preview comment thread through the existing approval gate, persist only the connection/design/thread/reply linkage in data.shared, and let a scheduled watcher re-read that exact thread until Canva reports it resolved. This pack does not replace Canva comments, native notifications, comment resolution, design review dashboards, webhook administration, or general design status reporting; it adds Recued-visible closure state for comment replies Recued sent.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Workflow origin for the Canva comment reply closure loop. It reads one preview Canva comment thread and reply page for context, creates exactly one owner-provided plaintext reply through recued-core.canva.comment.reply.create, and when the reply succeeds it seeds durable data.shared closure state for canva-comment-reply-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create comment threads, resolve or delete comments, mutate designs, export files, configure webhooks, or call arbitrary Canva endpoints.
Scheduled adopter for Canva comment reply closure rows seeded by reply-canva-comment-with-closure. It lists only Recued-originated comment-reply watches, re-reads a bounded batch of Canva preview comment thread, and closes the shared row when Canva reports that thread resolved. It can notify the owner on resolution, but it never replies to comments, resolves or deletes comment threads, mutates designs, exports files, creates webhooks, or calls arbitrary Canva endpoints.
Owner-visible list/close role for recued-core/canva-comment-reply-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.
How it works
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
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.