Skip to content

COULD_NOT_RUN

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
COULD_NOT_RUN
Likely outcomes (0 missions) — click to expand

Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

This alarm occurs when the Terrain Proximity Check is missing required inputs to determine whether the Zip satisfies map clearance requirements.

This could be due to missing inputs from nav, maps, or the cloud.

1 question
Is this the first time that the alarm has occurred?

Conduct incident response and escalate to P2 Zip Autonomy 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.