Low-frequency timeout role for recued-core/azure-devops-pull-request-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.
Azure DevOps pull request comment closure watcher timeout
Low-frequency timeout role for recued-core/azure-devops-pull-request-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
Azure DevOps Pull Request Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created Azure DevOps pull request comments. It composes the Azure DevOps capability pack with a closure ledger: add one owner-approved top-level thread comment to an existing Azure DevOps pull request, persist only the connection/organization/project/repository/pull-request/thread linkage in data.shared, and let a scheduled watcher re-read that exact pull request until Azure DevOps reports it completed or abandoned. This pack does not replace Azure DevOps pull request comments, native notifications, review approvals, completion or abandon controls, branch policies, builds, service hooks, or general code review reporting; it adds Recued-visible closure state for pull request 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 Azure DevOps pull request comment closure loop. It reads one Azure DevOps repository, pull request, and current thread comments for context, creates exactly one owner-provided top-level thread comment through recued-core.azure-devops.pull_request.thread.create, and when the thread succeeds it seeds durable data.shared closure state for azure-devops-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not complete, abandon, approve, vote on, edit, retarget, assign reviewers to, delete, or otherwise mutate Azure DevOps pull requests.
Scheduled adopter for Azure DevOps pull request comment closure rows seeded by comment-azure-devops-pull-request-with-closure. It lists only Recued-originated pull-request-comment watches, re-reads a bounded batch of Azure DevOps pull request, and closes the shared row when Azure DevOps reports that pull request completed or abandoned. It can notify the owner on terminal pull request state, but it never creates, updates, approves, votes on, completes, abandons, deletes, resolves, comments on, edits branches for, changes reviewers on, or otherwise mutates Azure DevOps pull requests.
Owner-visible list/close role for recued-core/azure-devops-pull-request-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.