BAD_DOCK_INFORMATION
Applicable alarms (1)
Likely outcomes — 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.
Background
Section titled “Background”This alarm is set when any of the information provided to the navigation system by the mission assignment is considered “bad” – for example, a dock that is missing a surveyed heading, a tower that has no bays, etc.
This alarm is always terminal and indicates the mission given to the vehicle was faulty.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
escalate-to-p2-fleet-core-on-call-the{{"<small><b>Step 1</b></small><br/>Escalation: Escalate to P2 Fleet Core On Call. Th..."}}
to-attempt-a-new-mission-ensure-that-y("<small><b>Step 2</b></small><br/>Reference: To attempt a new mission, ensure that...")
escalate-to-p2-fleet-core-on-call-the --> to-attempt-a-new-mission-ensure-that-y
style escalate-to-p2-fleet-core-on-call-the fill:#fef3c7,stroke:#f59e0b,color:#78350f
style to-attempt-a-new-mission-ensure-that-y fill:#f3e8ff,stroke:#a855f7,color:#581c87 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.