Low-frequency timeout role for recued-core/github-issue-comment-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.
GitHub issue comment closure watcher timeout
Low-frequency timeout role for recued-core/github-issue-comment-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
GitHub Issue Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created GitHub issue comments. It composes the GitHub capability pack with a closure ledger: add one owner-approved Markdown comment to an existing GitHub issue, persist only the connection/repository/issue/comment linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitHub reports it closed. This pack does not replace GitHub issue comments, native notifications, issue state controls, project boards, milestones, webhooks, or general issue reporting; it adds Recued-visible closure state for issue comments 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 GitHub issue comment closure loop. It reads one GitHub issue and current comments for context, creates exactly one owner-provided Markdown comment through recued-core.github-pack.issue.comment, and when the comment succeeds it seeds durable data.shared closure state for github-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, transfer, label, assign, lock, or otherwise mutate GitHub issues. It skips pull-request-shaped issue reads so code review remains on GitHub's pull request surfaces.
Scheduled adopter for GitHub issue comment closure rows seeded by comment-github-issue-with-closure. It lists only Recued-originated issue-comment watches, re-reads a bounded batch of GitHub issue, and closes the shared row when GitHub reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, transfers, labels, assigns, locks, comments on, or otherwise mutates GitHub issues.
Owner-visible list/close role for recued-core/github-issue-comment-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.