Half One: Restricting a Schedule to Working Hours
Working hours are set on the rotation, in Step 3 of schedule creation:Which days of the week the rotation is active. Weekdays only, for a schedule that does not run at weekends.
The time zone that Active Days and Active Hours are measured in. If the schedule form shows a Time Zone field above the rotations, it applies to every rotation. For follow-the-sun, enter each region’s hours converted to that zone. If each rotation has its own Timezone field, set each one to that region’s zone.
Half Two: What Happens Outside Those Hours
Here is the part that surprises people. The instinct is to add a 24/7 fallback as the next step in the same path. That works, in the sense that someone is eventually paged, but the delay is spent first, every single time, on every out-of-hours alert.The Fix: Two Paths, Not Two Steps
Model the time-of-day decision as Dynamic Paths, so the right path is chosen up front rather than the wrong step timing out:1
Path 1: during working hours
Add a Time window condition to path 1 (Add condition, then Time window) and match the days, hours and time zone to the rotation. The path doesn’t look at the schedule, so if the rotation’s hours change later, update the Time window too.
- Step 1: the business-hours schedule
- Step 2: the 24/7 fallback, for when the business-hours responder does not answer
2
Path 2: outside working hours
Put the 24/7 fallback as step 1 of the Default Escalation Path, which runs when no other path matches. If your Default path already pages the business-hours schedule, create another path with a Time window covering the hours outside path 1’s window, and make the 24/7 fallback its step 1.
- Step 1: the 24/7 fallback, directly
To hold a low-urgency alert instead of waking the fallback, use a Deferral Path. Rootly checks Deferral Paths first. A matching alert waits until the deferral window ends, then pages through the path set in After Deferral. Only alerts from Alert Sources, Live Call Routing and the API are deferred. A policy holds at most 50 deferred alerts, and any more page at once.
Check Your Work
A business-hours schedule looks fine in the UI at 2pm on a Tuesday. The failure only shows up out of hours, which is exactly when nobody is watching.- Use 24/7 coverage only where it belongs. Turn on Enable 24/7 coverage for this Schedule only for schedules meant to be continuous. Rootly then flags gaps and pages the Fallback Assignee during them. On a business-hours schedule, every hour outside the active window is a gap. See Enabling 24/7 Coverage.
- Check the schedule’s timeline. Open the schedule and check its timeline for the week ahead. Any stretch with no shift on it is a time when a step targeting this schedule pages no one.
- Test outside the window. Trigger an alert through the same alert source and route your real alerts use, at a time when the business-hours rotation is not active. On the alert timeline, confirm the after-hours path was chosen and the 24/7 fallback was paged at its first step. A manual page is not a full test: it skips Deferral Paths, and a page to one user skips the escalation policy. This is the single check that catches the empty-step trap.
Related Pages
Schedules
Rotations, Active Days and Active Hours, and coverage gap detection.
Escalation Policies
Dynamic Paths, Deferral Paths, and step delays.
On-Call Shifts
Each person’s upcoming shifts, overrides, and calendar export.