Owner-visible list/close role for recued-core/linear-issue-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.
Linear issue closure watcher lifecycle review
Owner-visible list/close role for recued-core/linear-issue-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.
Complete workflow
Linear Issue Closure Loop
4 pinned recipes
Workflow pack for Recued-created Linear issues. It composes the Linear capability pack with a closure ledger: create one owner-approved issue in one Linear team, optionally attach it to a configured project, persist only the connection/team/project/issue linkage in data.shared, and let a scheduled watcher re-read that exact issue until Linear reports it completed or canceled. This pack does not replace Linear workflow states, issue views, project views, cycles, roadmaps, native notifications, automations, comments, or general issue reporting; it adds Recued-visible closure state for issues 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.
Workflow origin for the Linear issue closure loop. It creates exactly one owner-approved issue through recued-core.linear.issue.create, and when the issue succeeds it seeds durable data.shared closure state for linear-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, move, cancel, complete, delete, archive, assign, label, subscribe to, comment on, or otherwise mutate Linear issues beyond the approved issue create.
Scheduled adopter for Linear issue closure rows seeded by create-linear-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of Linear issue, and closes the shared row when Linear reports the issue completed or canceled. It can notify the owner on terminal issue state, but it never creates, updates, moves, cancels, completes, deletes, archives, assigns, labels, subscribes to, comments on, or otherwise mutates Linear issues.
Low-frequency timeout role for recued-core/linear-issue-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.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
active_rows
?
timed_out_rows
?
closed_rows
?
▼
Process (10 steps)
close_key
trim
Trim whitespace from setting close key
close_is_timed_out
starts_with
Check if close key starts with data.shared.recipe.recued-core_linear-issue-closure.timed_out.
close_is_closed
starts_with
Check if close key starts with data.shared.recipe.recued-core_linear-issue-closure.closed.
close_allowed
any
Check if any of the conditions are true
close_terminal_row
?
skip: step.close_allowed not_equal true
lifecycle_rows
flatten
Flatten nested lists in
shown_rows
slice
Take a subset of
row_count
count
Count items in lifecycle rows
table
to_table
Format results as a data table
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
close key
setting
=
row limit
setting
=
50
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.