Who on this PagerDuty schedule cannot actually be paged
Use “Who on this PagerDuty schedule cannot actually be paged” in Recued. A person can SIT on an on-call schedule with zero notification rules — PagerDuty will assign them the incident and notify nobody, and no screen in the product says anything is wrong. This finds them.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (27 steps)
days
clamp
Clamp setting window days between 1 and 90
since
date_add
Add 0 days to
until
date_add
Add days days to
schedules_raw
?
schedules
default
Apply default
have_schedules
template
Generate text from a template
fail: step.schedules is_empty
schedule_count
count
Count items in schedules
requested_schedule
trim
Trim whitespace from setting schedule id
first_schedule_id
default
Apply default
target_schedule
default
Apply default
target_row
find
Find first match in
schedule_name
default
Apply default
users_raw
?
users
default
Apply default
have_users
template
Generate text from a template
fail: step.users is_empty
user_count
count
Count items in users
unpageable
filter
Filter by condition
unpageable_count
count
Count items in unpageable
pageable
filter
Filter by condition
pageable_count
count
Count items in pageable
rules_unknown
filter
Filter by condition
rules_unknown_count
count
Count items in rules unknown
no_contact
filter
Filter by condition
no_contact_count
count
Count items in no contact
card
to_summary
Format results as a summary card
unpageable_table
to_table
Format results as a data table
roster_table
to_table
Format results as a data table
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
pagerduty
setting
=
schedule id
setting
=
window days
setting
=
7
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.