Skip to content

DISTRO_MISSION_STATUS_UNAVAILABLE

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
DISTRO_MISSION_STATUS_UNAVAILABLE
Likely outcomes (65 missions, 24 issues) — 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)

Grounding 25% (6 of 24 issues) Discrepancy 75% (18 of 24 issues)

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.

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.

  • DISTRO_MISSION_STATUS_UNAVAILABLE
1 escalation
Escalate to P2 Firmware Controls on call

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.