On-call
Escalation policies, schedules, and alerts that keep firing until acknowledged.
On-call in Uptimely is a durable workflow: when an incident or alert with an attached on-call policy opens, the policy executes rule by rule until someone acknowledges or the rules run out — surviving restarts, with every notification attempt logged.
Escalation policies
A policy is an ordered list of escalation rules. Each rule notifies users, teams, or an on-call schedule, then waits its configured escalation delay. If the incident or alert is still unacknowledged when the delay expires, the next rule fires. Policies can repeat from the top a configured number of times.
Schedules and rotations
Schedules define who is on duty when: rotation layers with configurable hand-off intervals and restriction times (only page this layer during business hours, for example). Escalation rules that target a schedule notify whoever the schedule resolves to at that moment.
How people get paged
On-call notifications go to the contact methods each user verified on their account: email, SMS, and voice call. Device push is used for in-app notifications where enabled. Acknowledging from any surface stops the escalation.
Acknowledge and resolve
Acknowledgement is gated on the actual resource state — acknowledging an already-resolved incident doesn't restart anything, and duplicate executions are prevented by idempotent execution logs. The execution timeline for every policy run (who was notified, on which channel, and what happened) is visible on the incident or alert.