CONFIGURATION_CHECK_FAILED
Applicable alarms (1)
Likely outcomes — click to expand
Based on 37 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 4 ZERP issues filed on these missions)
Frequently co-occurring alarms (% of the 37 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm means the distro hover configuration checker did not complete in a normal, diagnosable way.
Unlike alarms such as REQUIRED_NODES_MISSING, REQUIRED_NODES_DUPLICATED, or HARDWARE_CONFIGURATION_INCORRECT, this alarm does not provide a clean corner-specific diagnosis. It indicates abnormal timing or sequencing during the hover power-up / identification process.
See DISTRO HOVER CONFIGURATION CHECKER for a description of how the diagnostic works.
Troubleshooting Steps
Section titled “Troubleshooting Steps”Related pages
Section titled “Related pages”graph TD
is-draft-configuration-check-failed-a{"<small><b>Step 1</b></small><br/>Question: Is CONFIGURATION_CHECK_FAILED activ..."}
power-cycle-the-vehicle-and-send-a-pr{"<small><b>Step 2</b></small><br/>Question: Power cycle the vehicle and send a pr..."}
the-aircraft-may-return-to-service["<small><b>Step 3</b></small><br/>Action: The aircraft may return to service."]
escalate-to-p2-firmware-motors-on-c{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to P2 Firmware Motors On Call."}}
continue-troubleshooting-using-the-a["<small><b>Step 5</b></small><br/>Action: Continue troubleshooting using the al..."]
is-draft-configuration-check-failed-a -->|Yes| power-cycle-the-vehicle-and-send-a-pr
is-draft-configuration-check-failed-a -->|No| continue-troubleshooting-using-the-a
power-cycle-the-vehicle-and-send-a-pr -->|Yes| the-aircraft-may-return-to-service
power-cycle-the-vehicle-and-send-a-pr -->|No| escalate-to-p2-firmware-motors-on-c
style is-draft-configuration-check-failed-a fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-vehicle-and-send-a-pr fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-firmware-motors-on-c fill:#fef3c7,stroke:#f59e0b,color:#78350f
style continue-troubleshooting-using-the-a fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
CONFIGURATION_CHECK_FAILED active on /distro_a.power_status?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.