Source
On-call schedules, rotations & escalation — found from sitemap — Squadcast
Checked for Squadcast on 17 Nov 2026
- Page
- https://support.incidents.cloud.solarwinds.com/escalation-policies/create-and-manage-escalation-policies
- Checked
- 17 Nov 2026, 13:47 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c99b2f8e676613a66161e8c1d10a634d446ddfc1a54fc51c441b697197f5b7cf
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Escalation policy recipients Report an error
“Incident notifications can be configured to escalate to Users, Squads or Schedules in a given order and time. You can create different Escalation Policies for different Services.”
-
Escalation policy role permission Report an error
“The User Role for the user in the Team must have the necessary permissions in order to manage Escalation Policies.”
-
Escalation repeat limit Report an error
“You can repeat any Escalation Policy for a maximum of 3 times only.”
-
Escalation time range Report an error
“Time input can be between 1 and 48 hours (inclusive).”
-
Escalation rule order Report an error
“The order of the rules will be carried out based on the time input. That is, from the shortest to the longest time, irrespective of the order in which the rules are placed while defining.”
-
Notification rule channels Report an error
“As an Admin, you can select one or more of the available notification channels (Email, Push, SMS, and Phone) to explicitly specify the channel via which the mapped users need to receive the incident notifications”
-
Escalation round robin Report an error
“Yes, please refer to the documentation here.”
-
Escalation deletion restriction Report an error
“Before deleting an Escalation Policy, ensure that it is not associated with any of the Services or that there are no open incidents associated with the Escalation Policy, otherwise you will be prohibited from deleting it.”
-
Escalation triggered state Report an error
“If the incident has transitioned away from the Triggered state when it was assigned to a specific Escalation Policy, then the rest of the rules in the Escalation Policy will not be executed.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Engineering Manager On-call schedules, rotations & escalation
- The Engineering Manager Alert delivery, routing & noise reduction
- The Engineering Manager Integrations, API & administration
- The ICT Risk Officer On-call schedules, rotations & escalation
- The ICT Risk Officer Alert delivery, routing & noise reduction
- The ICT Risk Officer Integrations, API & administration
- The IT Operations Manager On-call schedules, rotations & escalation
- The IT Operations Manager Alert delivery, routing & noise reduction
- The IT Operations Manager Integrations, API & administration
- The MSP NOC Lead On-call schedules, rotations & escalation
- The MSP NOC Lead Alert delivery, routing & noise reduction
- 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 Integrations, API & administration