0x00100341 ZIP_EXECUTIVE_V4_SECONDARY_FAILED
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x00100341) 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 secondary controller entered a failed state. This can result in a dock ASAP if it happens mid-flight.
Additional reference: Compute Failover Reference Document.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-there-a-terminal-or-root-cause-erro{"<small><b>Step 1</b></small><br/>Question: Is there a terminal or root cause err..."}
follow-the-troubleshooting-guide-for-th("<small><b>Step 2</b></small><br/>Reference: Follow the troubleshooting guide for ...")
inspect-compute-b-executive-journal-log["<small><b>Step 3</b></small><br/>Action: Inspect Compute B executive journal l..."]
is-compute-unhealthy-requested-seen{"<small><b>Step 4</b></small><br/>Question: Is ZIP_EXECUTIVE_V4_COMPUTE_UNHEALTHY..."}
follow-compute-unhealthy-requested-guide("<small><b>Step 5</b></small><br/>Reference: Follow 0x00100337 ZIP_EXECUTIVE_V4_C...")
escalate-to-p2-exec-on-call{{"<small><b>Step 6</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
is-there-a-terminal-or-root-cause-erro -->|Yes| follow-the-troubleshooting-guide-for-th
is-there-a-terminal-or-root-cause-erro -->|No| inspect-compute-b-executive-journal-log
inspect-compute-b-executive-journal-log --> is-compute-unhealthy-requested-seen
is-compute-unhealthy-requested-seen -->|Yes| follow-compute-unhealthy-requested-guide
is-compute-unhealthy-requested-seen -->|No| escalate-to-p2-exec-on-call
style is-there-a-terminal-or-root-cause-erro fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-the-troubleshooting-guide-for-th fill:#f3e8ff,stroke:#a855f7,color:#581c87
style inspect-compute-b-executive-journal-log fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-compute-unhealthy-requested-seen fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-compute-unhealthy-requested-guide fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-exec-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
Keep in mind that the error is on Compute B.
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.