DROID_ZIP_COMMANDER_MISSING_INPUTS
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”The Zip Commander is a piece of Droid software that tells the Zip to go upwind during a delivery in order to enable high wind deliveries without being blown away.
This error code is present when all of the data necessary for running the zip commander is not present. In most cases, this error code will be directly associated with other errors because if an upstream error causes an input for the zip commander to not be present, it will not run and will display this error. It is for this reason that it is suggested to diagnose upstream errors first before falling back to asking about this error. In the rare case that this is the only error present, please reach out to the engineering owners for diagnosis.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
are-there-other-error-codes-upstream-o{"<small><b>Step 1</b></small><br/>Question: Are there other error codes upstream ..."}
diagnose-those-errors-first-as-they-are["<small><b>Step 2</b></small><br/>Action: Diagnose those errors first as they a..."]
escalate-to-the-engineering-owners-to-d{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to the engineering owners to..."}}
are-there-other-error-codes-upstream-o -->|Yes| diagnose-those-errors-first-as-they-are
are-there-other-error-codes-upstream-o -->|No| escalate-to-the-engineering-owners-to-d
style are-there-other-error-codes-upstream-o fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style diagnose-those-errors-first-as-they-are fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-the-engineering-owners-to-d 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.