DISTRO_MISSION_STATUS_UNAVAILABLE
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 65 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 24 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| RIGHT DOOR ASSY, DROID, P2 | 21827 | 18 |
| LEFT DOOR ASSY, DROID, P2 | 21830 | 18 |
| PARALAND ASSY, DROID, P2 | 18427 | 14 |
| BATTERY, DROID, P2 | 24544 | 12 |
| ASSY PCBA, FRONT MOTOR NODE, DROID, P2 | 25279 | 10 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm triggers if the distro mission status stops transmitting a feedback message. Often this is happening due to the distro crashing, running at too slow of a rate, or publishing mission status too infrequently.
Exec watchdog alarm
Section titled “Exec watchdog alarm”- DISTRO_MISSION_STATUS_UNAVAILABLE
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
escalate-to-p2-firmware-controls-on-ca{{"<small><b>Step 1</b></small><br/>Escalation: Escalate to P2 Firmware Controls on call"}}
style escalate-to-p2-firmware-controls-on-ca fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.