0x00100322 ZIP_EXECUTIVE_V4_COMPUTE_FAILOVER_REQUESTED
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x00100322) 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 fault-response code indicates that the executive requested a compute failover due to a flight-failing fault on compute A. This error code does not suggest that the failover actually occurred. That indication comes from ZIP_EXECUTIVE_V4_FAILOVER_SECONDARY_IN_CONTROL
Additional reference: Compute Failover Reference Document.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-there-a-root-cause-error{"<small><b>Step 1</b></small><br/>Question: Is there a terminal or root-cause err..."}
follow-root-cause-guide["<small><b>Step 2</b></small><br/>Action: Follow the troubleshooting guide for ..."]
escalate-to-p2-exec{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
is-there-a-root-cause-error -->|Yes| follow-root-cause-guide
is-there-a-root-cause-error -->|No| escalate-to-p2-exec
style is-there-a-root-cause-error fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-root-cause-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-exec 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.