Reposition After Droid Left Behind
This alarm is covered by this guide. Background
Section titled “Background”On software release 2026.15, a Zip Executive persistent-state bug can prevent a maintenance reposition after an Aircraft has left its Droid behind. The Aircraft can appear to be in a state where the Droid is neither stowed nor correctly recognized as left behind, so the maintenance reposition may fail until Zip Executive restarts.
The intended workaround is to restart Zip Executive without rebooting the rest of the Aircraft stack, then attempt the maintenance reposition. A reboot mission may be rejected by the same bug, and a full Aircraft power cycle can restart distro and leave the winch cutter reporting the wrong terminal state for this recovery path.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
which-software-version-are-you-on{"<small><b>Step 1</b></small><br/>Question: Which software version are you on?"}
confirm-the-aircraft-is-post-dlb-on-2026-15{"<small><b>Step 2</b></small><br/>Question: Is this Aircraft docked after a confi..."}
disregard-this-guide["<small><b>Step 3</b></small><br/>Action: This guide is only applicable to 2026..."]
restart-zip-executive["<small><b>Step 4</b></small><br/>Action: In Fleet Wrangler, send the troublesh..."]
wait-for-executive-to-recover["<small><b>Step 5</b></small><br/>Action: In Fleet Wrangler, wait until **Recen..."]
retry-the-mx-reposition["<small><b>Step 6</b></small><br/>Action: Attempt the maintenance reposition ag..."]
did-the-retry-complete{"<small><b>Step 7</b></small><br/>Question: Did the maintenance reposition comple..."}
escalate-to-p2-exec{{"<small><b>Step 8</b></small><br/>Escalation: Escalate to P2 Exec On Call. Include ..."}}
continue-normal-post-dlb-maintenance("<small><b>Step 9</b></small><br/>Reference: Continue the normal post-Droid Left B...")
use-the-normal-troubleshooting-flow("<small><b>Step 10</b></small><br/>Reference: Use the normal troubleshooting flow f...")
which-software-version-are-you-on -->|2026.15| confirm-the-aircraft-is-post-dlb-on-2026-15
which-software-version-are-you-on -->|2026.15.1 or higher| disregard-this-guide
confirm-the-aircraft-is-post-dlb-on-2026-15 -->|Yes| restart-zip-executive
confirm-the-aircraft-is-post-dlb-on-2026-15 -->|No| use-the-normal-troubleshooting-flow
restart-zip-executive --> wait-for-executive-to-recover
wait-for-executive-to-recover --> retry-the-mx-reposition
retry-the-mx-reposition --> did-the-retry-complete
did-the-retry-complete -->|No| escalate-to-p2-exec
did-the-retry-complete -->|Yes| continue-normal-post-dlb-maintenance
style which-software-version-are-you-on fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style confirm-the-aircraft-is-post-dlb-on-2026-15 fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style disregard-this-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style restart-zip-executive fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-for-executive-to-recover fill:#dcfce7,stroke:#22c55e,color:#14532d
style retry-the-mx-reposition fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-retry-complete fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-p2-exec fill:#fef3c7,stroke:#f59e0b,color:#78350f
style continue-normal-post-dlb-maintenance fill:#f3e8ff,stroke:#a855f7,color:#581c87
style use-the-normal-troubleshooting-flow fill:#f3e8ff,stroke:#a855f7,color:#581c87 Hover or focus a block to preview it. Select the block to keep the preview open.
STOP_FLIGHT_TARGET_AND_RESTART_EXECUTIVE to the Aircraft. Do not send a reboot mission or full Aircraft power cycle for this workaround.
For general troubleshooting command steps, see How to Use Troubleshooting Commands.
STOP_FLIGHT_TARGET_AND_RESTART_EXECUTIVE succeeded. Open Details and confirm there is no failure response. Then confirm the Aircraft asset view updates again and shows the Zip Executive task as Sleep before retrying the reposition.STOP_FLIGHT_TARGET_AND_RESTART_EXECUTIVE was already attempted.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.