Scheduled feedback half of the Sentry to Linear exception handoff loop. It reads Linear issues created by create-approved-linear-issue-from-sentry, closes the Recued data.shared handoff when the Linear issue reaches a terminal state, and optionally notifies the owner to review the corresponding Sentry issue. It does not update Sentry issue status, update Linear issues, reopen work, create comments, change alerts, or call arbitrary APIs. Native Sentry and Linear synchronization owns normal issue resolution; this watcher only records Recued-visible exception closure.
Watch Linear resolution for Sentry handoff
Scheduled feedback half of the Sentry to Linear exception handoff loop. It reads Linear issues created by create-approved-linear-issue-from-sentry, closes the Recued data.shared handoff when the Linear issue reaches a terminal state, and optionally notifies the owner to review the corresponding Sentry issue. It does not update Sentry issue status, update Linear issues, reopen work, create comments, change alerts, or call arbitrary APIs. Native Sentry and Linear synchronization owns normal issue resolution; this watcher only records Recued-visible exception closure.
Complete workflow
Exception Handoff Loop - Sentry + Linear
3 pinned recipes
Workflow pack that closes the loop between exception-scoped Sentry issues and owner-approved Linear follow-up work. It depends on the Sentry and Linear capability packs, detects one unhandled matching Sentry issue at a time, writes a data.shared proposal, notifies the owner, provides a manual action recipe that either creates the Linear issue and links it back to the Sentry issue or dismisses the proposal, and watches created Linear issues until they reach a terminal state. It does not replace Sentry alerts, Sentry ownership rules, Sentry's native issue-tracker integrations, Sentry alert ticket creation, or Linear triage automation; use it only when the normal native path is unavailable, intentionally bypassed, or missing Recued-visible closure state.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Scheduled detection half of the Sentry to Linear exception handoff loop. It reads recent matching unresolved Sentry issues, writes one data.shared proposal for the first unhandled issue, and notifies the owner to review whether the issue should become exception Linear work. It never creates Linear issues, updates Sentry issue status, changes Sentry alerts or ownership rules, mutates Linear projects, or calls arbitrary APIs. Sentry alerts, Sentry issue ownership, native Sentry issue-tracker integrations, and Sentry alert ticket creation own their normal paths; this recipe only creates a Recued-visible exception proposal that an owner can approve or dismiss with create-approved-linear-issue-from-sentry.
Owner-invoked action half of the Sentry to Linear exception handoff loop. It reads one awaiting_owner_approval proposal written by sentry-linear-issue-proposal, then either creates exactly one Linear issue from deterministic Sentry context or dismisses the proposal as no Linear work needed. Running this recipe is the owner's approval or decline. It re-reads the Sentry issue before creating Linear work and takes no outward-facing action when there is no pending proposal, the live Sentry issue is no longer unresolved, or the required Linear destination is missing. Native Sentry to Linear issue tracking should own the normal create/link/sync path.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
handoffs
?
▼
Process (35 steps)
handoffs_family
filter
Filter by condition
created_handoffs
filter
Filter by condition
handoffs_with_linear_issue
filter
Filter by condition
candidate_rows
slice
Take a subset of
watch_count
count
Count items in handoffs with linear issue
has_candidate
compare
Check if candidate rows has data
proposal_key
default
Apply default
sentry_org
default
Apply default
sentry_issue_id
default
Apply default
sentry_issue_short_id
default
Apply default
linear_issue_id
default
Apply default
linear_identifier
default
Apply default
has_linear_issue
compare
Check if linear issue id has data
has_sentry_issue
compare
Check if sentry issue id has data
has_sentry_org
compare
Check if sentry org has data
has_linear_connection
compare
Check if setting linear has data
has_sentry_connection
compare
Check if setting sentry has data
ready_to_read_linear
all
Check if all conditions are true
linear_issue
?
skip: step.ready_to_read_linear not_equal true
linear_state_type
default
Apply default
linear_state_name
default
Apply default
linear_issue_url
default
Apply default
linear_completed
compare
Check if linear state type equals completed
linear_canceled
compare
Check if linear state type equals canceled
linear_terminal
any
Check if any of the conditions are true
ready_to_read_sentry
all
Check if all conditions are true
sentry_issue
?
skip: step.ready_to_read_sentry not_equal true
sentry_issue_status
default
Apply default
now
date_add
Add 0 minutes to
ready_to_close
all
Check if all conditions are true
close_handoff
?
skip: step.ready_to_close not_equal true
notify_enabled
compare
Check if setting notify owner equals true
should_notify
all
Check if all conditions are true
send_owner_notification
?
skip: step.should_notify not_equal true
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
linear
setting
=
sentry
setting
=
channels
setting
=
in_app
notify owner
setting
=
true
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.