Escalation Paths
This table is the source of truth for escalation path names and Slack handles.
- Use
[[EscalationPath:<id>]]for almost everything, where<id>is the value in the ID column below.
Example:Escalate to [[EscalationPath:p2-exec]].renders as “Escalate to P2 Exec On Call.” - Use
[[EscalationPathSlack:<id>]]only when you specifically need the Slack handle to show in the topic. The<id>still comes from the ID column below.
Example:Post the result in [[EscalationPathSlack:p2-exec]].renders as “Post the result in @p2-exec-on-call.”
When a team name or Slack channel changes, update its row in this table’s source data and every topic that references that escalation path ID will automatically render the updated value.
How the table is populated and validated
This table is built from site/src/data/escalation-paths.json. Each entry in that file becomes one row in the table. The file is maintained manually; the table is not populated or synchronized automatically from Slack or incident.io.
Each row maps three separate values:
- Name: The escalation path name displayed in the troubleshooting guide.
- ID: The stable value authors use in
[[EscalationPath:<id>]]shortcodes. - Slack: The Slack user group that readers can contact, when the escalation path has one.
These values do not need to have matching names. For example, an escalation path ID may point to a Slack user group whose handle uses a different team name. Do not construct or guess the Slack handle from the ID or display name. The Slack value must be the exact handle of an active Slack user group, not a Slack channel name or an incident.io escalation path name.
For every pull request, escalation-path validation checks the entire repository:
- Every escalation-path shortcode in a topic or procedure must use an ID found in
escalation-paths.json. - Every non-null Slack value in
escalation-paths.jsonmust exactly match an active user group in the live Slack workspace. - The JSON must contain valid, unique IDs and correctly formed name and Slack values.
Because the check validates the entire escalation-path directory, it can find an existing problem that is unrelated to the pull request. For example, a pull request may fail if a Slack user group was renamed or disabled after the repository entry was last updated.
The validator supports comparing escalation path names with live incident.io escalation paths, but that comparison is currently disabled. Enabling it would add an incident.io name check; it would not replace the Slack check or automatically populate Slack handles.
Validation confirms that the referenced ID and Slack user group exist. It does not confirm that the escalation path routes to the correct responders. Confirm new or changed routing with the affected team.
How to add a new escalation path
Section titled “How to add a new escalation path”Before you add a row to this table, the upstream escalation route should already work. A table entry does not create the Slack user group or the incident.io escalation path; it only gives authors a canonical ID to use once those systems are already configured.
Steps to set up a new escalation path
- Create or confirm the Slack user group: Ask a Slack workspace admin or IT owner to create or confirm the Slack user group if the table row will include a Slack handle. The handle must be an active Slack user group handle, such as
@zip-eol-oncall, not just a channel name or proposed alias. - Create the matching incident.io escalation path: Ask an incident.io admin or on-call configuration owner to create the matching incident.io escalation path. In incident.io, they should go to the on-call or escalation paths area, create a new escalation path, give it the exact display name you plan to use in this table, configure the routing steps to page or notify the correct responders, and save it.
- Add the row to the table: Add the row to the table below by editing
site/src/data/escalation-paths.json. Use a lowercase, hyphenated ID, the exact incident.io escalation path name, and the active Slack user group handle. - Create the PR: Create the PR and let CI validate the change. The escalation path check verifies that all shortcodes resolve and that every non-null Slack handle matches an active Slack user group.
Escalation paths
Section titled “Escalation paths”| Name | ID | Slack |
|---|---|---|
| Aircraft Structures & Mechanisms On Call | aircraft-structures-and-mechs | @aircraft-structures-and-mechs-on-call |
| ASW Delivery Support On Call | asw-delivery-support | @asw-delivery-support-oncall |
| ASW Fleet & Delivery On Call | asw-fleet-and-delivery | - |
| ASW Maintenance and Operations | asw-mx-noc | @asw-mx-noc-on-call |
| ATX GSSO | atx-gsso | @atx-gsso-oncall |
| Cell SIM Support On Call | cell-sim-support | @cell-sim-on-call |
| Chassis Isolation Escalation | chassis-isolation | @p-2-chassis-isolation-on-call |
| Cloud Comms On Call | cloud-comms | - |
| DFW GSSO | dfw-gsso-oncall | @dfw-gsso-oncall |
| Droid Executive On Call | droid-executive | - |
| Engineering | engineering | - |
| On call FW High Drag On-Call | fw-high-drag-on-call | @fw-high-drag-on-call |
| GSSO Leads | gsso-leads-oncall | @gsso-leads-oncall |
| HOU GSSO | hou-gsso-oncall | @hou-gsso-oncall |
| IT Networking On Call | it-networking | @it-networking-oncall |
| Manufacturing On Call | manufacturing | @manufacturing-on-call |
| Manufacturing Test Software On Call | manufacturing-test-software | @manufacturing-test-software-on-call |
| Dock EOL and Health Check On Call | dock-mfg-eol | - |
| Droid EOL On Call | droid-mfg-eol | @droid-eol-oncall |
| Zip EOL On Call | zip-mfg-eol | @zip-eol-oncall |
| Motion Planning On Call | motion-planning | - |
| OTA Support On Call | ota-support | @ota-oncall |
| P2 Aircraft Autonomy On Call | p2-aircraft-autonomy | @zip-motion-planning-on-call |
| P2 Aircraft Hardware On Call | p2-aircraft-hardware | @p2-aircraft-hardware-on-call |
| P2 Application Software Triage On Call | p2-application-software-triage | - |
| P2 ASW On Call | p2-asw | - |
| P2 Autonomy On Call | p2-autonomy | - |
| P2 Avionics Hardware On Call | p2-avionics-hardware | @p2-avionics-hardware-oncall |
| P2 Busbars On Call | p2-busbars | @p2-busbars-on-call |
| P2 Data Platform On Call | p2-data-platform | @data-platform-on-call |
| P2 Dock Embedded On Call | p2-dock-embedded | @p2-dock-embedded-on-call |
| P2 Dock Hardware On Call | p2-dock-hardware | @p2-dock-hardware-oncall |
| P2 Droid On Call | p2-droid | @p2-droid-on-call |
| P2 Droid Autonomy On Call | p2-droid-autonomy | @p2-droid-on-call |
| P2 Droid Controls On Call | p2-droid-controls | @p2-droid-controls-on-call |
| P2 Droid Controls & Dynamics On Call | p2-droid-controls-dynamics | - |
| P2 Droid Hardware On Call | p2-droid-hardware | - |
| P2 EE On Call | p2-ee | - |
| P2 Embedded Linux On Call | p2-embedded-linux | @p2-embedded-linux-oncall |
| P2 Embedded Platform On Call | p2-embedded-platform | @p2-embedded-platform-oncall |
| P2 Exec On Call | p2-exec | @p2-exec-on-call |
| P2 Firmware Motors On Call | p2-firmware-motors | @p2-motors-incidents |
| P2 Firmware Platform On Call | p2-firmware-platform | @p2-firmware-platform-on-call |
| P2 Firmware Power On Call | p2-firmware-power | @p2-firmware-power-on-call |
| P2 Firmware Safety On Call | p2-firmware-safety | @p2-firmware-safety-on-call |
| P2 Fleet Core On Call | p2-fleet-core | @p2-fleet-core-oncall |
| P2 FSE On Call | p2-fse | - |
| P2 Maps On Call | p2-maps | - |
| P2 Nav On Call | p2-nav | @p2-nav-on-call |
| P2 Onboard Data Platform On Call | p2-onboard-data-platform | @onboard-data-platform-on-call |
| P2 Routing On Call | p2-routing | - |
| P2 Safety On Call | p2-safety | - |
| P2 Smart Carts | p2-smart-carts | - |
| P2 Zip Autonomy On Call | p2-zip-autonomy | - |
| P2 Zip Controls On Call | p2-zip-controls | @p2-zip-controls-on-call |
| P2 Zip DAA Tracker On Call | p2-zip-daa-tracker | @p2-zip-daa-tracker-on-call |
| P2 Zip Hardware On Call | p2-zip-hardware | - |
| PHX GSSO | phx-gsso-oncall | @phx-gsso-oncall |
| Powertrain On Call | powertrain | @pwt-on-call |
| Powertrain ME | powertrain-me | - |
| RTK On Call | rtk | - |
| Service Engineering | service-engineering | @p2-service-eng-on-call |
| Site Auxiliary On Call | site-auxiliary-on-call | @site-auxiliary-on-call |
| SMI On Call | smi | - |
| Systems Engineering | systems-engineering | @systems-engineering-oncall |
| UTM On Call | utm-on-call | @utm-on-call |
| Zerp Team | zerp | - |
| Zip Executive On Call | zip-executive | - |
| Zip Aircraft Perception | zip-aircraft-perception | @zip-aircraft-perception-oncall |
| Zipping Point On Call | zipping-point | @zipping-point-on-call |
| No escalation paths match this search. | ||
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.