Source
Documentation (escalation policies) — PagerDuty
Checked for PagerDuty on 6 Nov 2026
- Page
- https://docs.pagerduty.com/incident-management/schedules/escalation-policies
- Checked
- 6 Nov 2026, 04:47 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:845fe8d4a262ce89b57c117432c900137c450fa25bda0b62748581c8c305ffb7
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Free plan limit Report an error
“Escalation policies are available on all pricing plans, although the Free plan is limited to a single escalation policy. Other plans do not have a set limit on the number of escalation policies.”
-
Single service binding Report an error
“Services in PagerDuty can only be associated with one escalation policy. An escalation policy, however, can be associated with as many services as you like.”
-
Default mobilization ep Report an error
“Every PagerDuty account includes an escalation policy called Default Mobilization EP, with the Account Owner assigned to it. This is an empty, internal, account-level escalation policy that ships with your account.”
-
Escalation rules limit Report an error
“You can add up to 20 escalation rules to an escalation policy.”
-
Repeat policy limit Report an error
“An escalation policy can be repeated up to nine times.”
-
Multiuser notification limits Report an error
“Multi-user notifications on each escalation level are limited to 50 users or schedules on Business, Digital Operations (legacy), and Enterprise for Incident Management plans, and five on Professional and Free plans.”
-
Escalation timeout default Report an error
“The default escalation timeout is 30 minutes but can be adjusted.”
-
Escalation timeout minimums Report an error
“With a single target on an escalation rule, the minimum escalation timeout is one minute. If there is more than one target in an escalation rule, the minimum escalation timeout is three minutes.”
-
Acknowledgment stops escalation Report an error
“Once a responder acknowledges, the policy stops escalating and PagerDuty stops sending notifications.”
-
Policy snapshot on trigger Report an error
“An incident follows the escalation policy's structure as it was when the incident triggered. Changes made to an escalation policy after an incident triggers will not affect any currently open incidents.”
-
Skip empty rules Report an error
“If nobody is on-call in the first rule (due to a coverage gap in a schedule, for example), PagerDuty assigns the incident to the next escalation rule with an on-call responder.”
-
Team association Report an error
“An escalation policy can only be associated with one Team at a time.”
-
Team field availability Report an error
“Team Available on Business, Digital Operations (legacy), and Enterprise for Incident Management plans.”
-
Oncall handoff notifications Report an error
“On-call handoff notifications (OCHONs) can notify users up to 48 hours before they go on-call, and are configured on a user's profile.”
-
Round robin assignment Report an error
“If your account has Round Robin Scheduling, optionally select the checkbox to Assign via Round Robin.”
-
Inactive users skipped Report an error
“Deleted users are marked as inactive on an escalation policy. These users will be skipped when the escalation policy runs.”
-
Delete policy permanent Report an error
“Deleting an escalation policy is permanent and cannot be restored.”
-
Live call routing multi responder Report an error
“If you have Live Call Routing enabled to Connect Directly and there is more than one responder on an escalation rule, PagerDuty will randomly cycle through all responders on that rule.”
-
Multi user notification same rule Report an error
“If you select more than one user or schedule, each will be notified at the same time per escalation rule.”
-
Schedule notifies current oncall Report an error
“Schedule Targets: Select on-call schedules as targets if you want to notify the user who is currently on-call when an incident is triggered, assigned, or escalated to the schedule's rule on an escalation policy.”
-
Ochon policy settings Report an error
“Select when the escalation policy should send on-call handoff notifications: always or when in use by a service.”
-
No initial notification delay Report an error
“It does not delay the first notification. Whoever is at the first rule is always notified the moment an incident triggers. There is no setting to delay this initial notification.”
-
Retrigger resumes policy Report an error
“If an acknowledged incident re-triggers, it resumes following the escalation policy.”
Scores citing this record
- The Engineering Manager On-call schedules, rotations & escalation
- The Engineering Manager Pricing transparency
- The ICT Risk Officer On-call schedules, rotations & escalation
- The ICT Risk Officer Integrations, API & administration
- The IT Operations Manager On-call schedules, rotations & escalation
- The MSP NOC Lead On-call schedules, rotations & escalation
- The MSP NOC Lead Integrations, API & administration
- The Skeptic On-call schedules, rotations & escalation
- The Skeptic Alert delivery, routing & noise reduction
- The Skeptic Integrations, API & administration
- The SRE Lead On-call schedules, rotations & escalation
- The SRE Lead Alert delivery, routing & noise reduction
- The SRE Lead Pricing transparency