Low-frequency timeout role for recued-core/figma-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.
Figma comment reply closure watcher timeout
Low-frequency timeout role for recued-core/figma-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
Figma Comment Reply Closure Loop
4 pinned recipes
Workflow pack for Recued-sent Figma comment replies. It composes the Figma capability pack with a closure ledger: reply once to an existing Figma file comment through the existing approval gate, persist only the connection/file/comment/reply linkage in data.shared, and let a scheduled watcher re-read that exact file comment until Figma reports it resolved or the comment is no longer present. This pack does not replace Figma comments, native notifications, design review dashboards, webhook administration, comment resolution controls, or general file-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 Figma comment reply closure loop. It reads one Figma file's comments for context, creates exactly one owner-provided reply on an existing comment through recued-core.figma.comment.create, and when the reply succeeds it seeds durable data.shared closure state for figma-comment-reply-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create top-level comments, delete comments, add reactions, mutate files, export images, configure webhooks, or call arbitrary Figma endpoints.
Scheduled adopter for Figma comment reply closure rows seeded by reply-figma-comment-with-closure. It lists only Recued-originated comment-reply watches, re-reads a bounded batch of Figma file's comments, and closes the shared row when Figma reports the watched root comment resolved or no longer returns it. It can notify the owner on resolution or disappearance, but it never creates, edits, deletes, or resolves comments, adds reactions, mutates files, exports images, configures webhooks, or calls arbitrary Figma endpoints.
Owner-visible list/close role for recued-core/figma-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.