0x00100480 ZIP_EXECUTIVE_V4_DROID_NOT_IN_FLIGHT_TARGET
Viewing this guide for
Applicable alarms (2)
0x00100480ZIP_EXECUTIVE_V4_DROID_NOT_IN_FLIGHT_TARGET
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x00100480) 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 Zip Executive alarm indicates the Droid was not in the flight systemd target when Zip Executive expected it. First rule out an unprovisioned JP6 Droid, then use Droid executive watchdog alarms and the systemd target command to choose the next troubleshooting path.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
check-jp6-droid-unprovisioned["<small><b>Step 1</b></small><br/>Action: Follow JP6 Droid Unprovisioned/top..."]
does-mission-still-fail{"<small><b>Step 2</b></small><br/>Question: Does the mission still fail with ZIP..."}
open-systemd-target-template["<small><b>Step 3</b></small><br/>Action: In Baraza, open the failing mission a..."]
are-exec-watchdog-alarms-set{"<small><b>Step 4</b></small><br/>Question: Are either of these Exec watchdog ala..."}
follow-droid-executive-unavailable["<small><b>Step 5</b></small><br/>Action: Follow the guide for the Exec watchdo..."]
reboot-zip-and-droid["<small><b>Step 6</b></small><br/>Action: Reboot the Zip and Droid with a reboo..."]
was-retry-successful{"<small><b>Step 7</b></small><br/>Question: Was the mission retry successful?"}
return-to-service["<small><b>Step 8</b></small><br/>Action: Return the Aircraft and Droid to serv..."]
check-systemd-target-command["<small><b>Step 9</b></small><br/>Action: Pull up the debug_droid_systemd_targ..."]
is-flight-command-present{"<small><b>Step 10</b></small><br/>Question: Is there a FLIGHT command on /comp..."}
escalate-embedded-platform{{"<small><b>Step 11</b></small><br/>Escalation: Escalate to P2 Embedded Platform On C..."}}
escalate-p2-exec{{"<small><b>Step 12</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
check-jp6-droid-unprovisioned --> does-mission-still-fail
does-mission-still-fail -->|No, the retry succeeds| return-to-service
does-mission-still-fail -->|Yes, or the Droid was alrea...| open-systemd-target-template
open-systemd-target-template --> are-exec-watchdog-alarms-set
are-exec-watchdog-alarms-set -->|Yes| follow-droid-executive-unavailable
are-exec-watchdog-alarms-set -->|No| reboot-zip-and-droid
reboot-zip-and-droid --> was-retry-successful
was-retry-successful -->|Yes| return-to-service
was-retry-successful -->|No| check-systemd-target-command
check-systemd-target-command --> is-flight-command-present
is-flight-command-present -->|Yes| escalate-embedded-platform
is-flight-command-present -->|No| escalate-p2-exec
style check-jp6-droid-unprovisioned fill:#dcfce7,stroke:#22c55e,color:#14532d
style does-mission-still-fail fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style open-systemd-target-template fill:#dcfce7,stroke:#22c55e,color:#14532d
style are-exec-watchdog-alarms-set fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-droid-executive-unavailable fill:#dcfce7,stroke:#22c55e,color:#14532d
style reboot-zip-and-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style was-retry-successful fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-systemd-target-command fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-flight-command-present fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-embedded-platform fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-p2-exec fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
Follow JP6 Droid Unprovisioned. If the Droid is provisioned, return here and continue. If the Droid was unprovisioned, re-provision it and retry the mission.
2 question
Does the mission still fail with
ZIP_EXECUTIVE_V4_DROID_NOT_IN_FLIGHT_TARGET after following JP6 Droid Unprovisioned? 3 action
In Baraza, open the failing mission and apply the debug_droid_systemd_target template.
4 question
Are either of these Exec watchdog alarms set?
- DROID_EXECUTIVE_RESPONSES_WIRELESS_UNAVAILABLE
- DROID_EXECUTIVE_RESPONSES_WIRED_UNAVAILABLE
- DROID_EXECUTIVE_RESPONSES_WIRELESS_UNAVAILABLE
- DROID_EXECUTIVE_RESPONSES_WIRED_UNAVAILABLE
6 action
Reboot the Zip and Droid with a reboot mission, then try the mission again.
7 question
Was the mission retry successful?
8 action
Return the Aircraft and Droid to service after the retry succeeds.
9 action
Pull up the
debug_droid_systemd_target log plot on the most recent mission attempt. 10 question
Is there a
FLIGHT command on /compute_a.systemd_target_agent.droid.command.target? 11 escalation
Escalate to P2 Embedded Platform On Call.
12 escalation
Escalate to P2 Exec On Call.
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.