Sentry issue triage digest
Scheduled read-only issue triage digest for one Sentry organization and project. It reads unresolved issues, recent project events, recent releases, and legacy user feedback through recued-core.sentry, renders compact tables, and optionally sends an in-app nudge when issues are visible. It never deletes issues, bulk-mutates issues, updates alerts, creates projects, creates deploys, uploads files, reads DSNs, or calls arbitrary Sentry API routes.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (23 steps)
issues_raw
?
events_raw
?
releases_raw
?
feedback_raw
?
issues
default
Apply default
events
default
Apply default
releases
default
Apply default
feedback
default
Apply default
issue_count
count
Count items in issues
event_count
count
Count items in events
release_count
count
Count items in releases
feedback_count
count
Count items in feedback
has_issues
compare
Check if issue count is greater than 0
notify_enabled
compare
Check if setting notify when issues equals true
should_notify
all
Check if all conditions are true
notify
?
skip: step.should_notify not_equal true
issue_rows
slice
Take a subset of
event_rows
slice
Take a subset of
release_rows
slice
Take a subset of
issue_table
to_table
Format results as a data table
event_table
to_table
Format results as a data table
release_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
sentry
setting
=
channels
setting
=
in_app
end hour
setting
=
10
weekdays
setting
=
1,2,3,4,5
row limit
setting
=
20
start hour
setting
=
8
issue query
setting
=
is:unresolved
stats period
setting
=
24h
notify when issues
setting
=
true
project id or slug
setting
=
organization id or slug
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.