Low-frequency timeout role for recued-core/jira-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.
Jira issue closure watcher timeout
Low-frequency timeout role for recued-core/jira-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.
Complete workflow
Jira Issue Closure Loop
4 pinned recipes
Workflow pack for Recued-created Jira issues. It composes the Jira capability pack with a closure ledger: create one owner-approved Jira issue in one configured cloud/project, persist only the connection/cloud/project/issue linkage in data.shared, and let a scheduled watcher re-read that exact issue until Jira reports the issue has reached the Done status category. This pack does not replace Jira workflow transitions, assignments, boards, sprints, automations, native notifications, webhooks, comments, worklogs, labels, due dates, or general issue reporting; it adds Recued-visible closure state for Jira 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 Jira issue closure loop. It creates exactly one owner-approved issue through recued-core.jira.issue.create, and when the issue succeeds it seeds durable data.shared closure state for jira-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, transition, assign, delete, comment on, attach to, link, watch, vote on, add worklogs to, or otherwise mutate Jira issues beyond the approved issue create.
Scheduled adopter for Jira issue closure rows seeded by create-jira-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of Jira issue, and closes the shared row when Jira reports that issue has reached the Done status category. It can notify the owner on closure, but it never creates, updates, transitions, assigns, deletes, attaches to, links, watches, votes on, comments on, adds worklogs to, or otherwise mutates Jira issues.
Owner-visible list/close role for recued-core/jira-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.
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.