0x00030127 - ZIP_EXECUTIVE_CODE_FAILOVER_COMMAND_NOT_READY
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x00030127) 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 is an intermediate error code. It indicates that Compute B is either in an errored state or not communicating with compute A
Additional reference: Compute Failover Reference Document.
Troubleshooting Step
Section titled “Troubleshooting Step”graph TD
is-the-executive-service-running-on-co{"<small><b>Step 1</b></small><br/>Question: Is the executive service running on c..."}
power-cycle-compute-b-and-ensure-that["<small><b>Step 2</b></small><br/>Action: Power cycle compute B and ensure that..."]
retry-the-mission["<small><b>Step 3</b></small><br/>Action: Retry the mission."]
are-there-other-terminal-or-root-caus{"<small><b>Step 4</b></small><br/>Question: Are there other terminal or root caus..."}
follow-the-troubleshooting-guide-for("<small><b>Step 5</b></small><br/>Reference: Follow the troubleshooting guide for ...")
inspect-compute-b-executive-journal["<small><b>Step 6</b></small><br/>Action: Inspect Compute B executive journal l..."]
escalate-to-p2-exec-on-call{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
is-the-executive-service-running-on-co -->|Yes| are-there-other-terminal-or-root-caus
is-the-executive-service-running-on-co -->|No| power-cycle-compute-b-and-ensure-that
power-cycle-compute-b-and-ensure-that --> retry-the-mission
are-there-other-terminal-or-root-caus -->|Yes| follow-the-troubleshooting-guide-for
are-there-other-terminal-or-root-caus -->|No| inspect-compute-b-executive-journal
inspect-compute-b-executive-journal --> escalate-to-p2-exec-on-call
style is-the-executive-service-running-on-co fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-compute-b-and-ensure-that fill:#dcfce7,stroke:#22c55e,color:#14532d
style retry-the-mission fill:#dcfce7,stroke:#22c55e,color:#14532d
style are-there-other-terminal-or-root-caus fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-the-troubleshooting-guide-for fill:#f3e8ff,stroke:#a855f7,color:#581c87
style inspect-compute-b-executive-journal fill:#dcfce7,stroke:#22c55e,color:#14532d
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.