No Docked Zip Reported, but is Showing Occupied and Buddied to Aircraft
Background
Section titled “Background”On FleetWrangler’s Dock page, an Aircraft will appear buddied but not docked even though the Aircraft is currently occupying a Dock. This happens when a Dock is power cycled or software is updated while an Aircraft is currently occupying that Dock. When a Dock boots up, it doesn’t know its Bay ID. It sends the Aircraft an empty Bay ID and the cloud then receives that empty Bay ID. This is a known bug in Zip Software in the .19 release and is still apparent in the .24 release.
This could also be caused by a currently outstanding bug in obs as of 9/3/25.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
restart-the-aircraft-s-flight-target["<small><b>Step 1</b></small><br/>Action: Restart the Aircraft’s flight target."]
wait-20-seconds["<small><b>Step 2</b></small><br/>Action: Wait 20 seconds."]
check-the-bay-page-in-fleetwrangler["<small><b>Step 3</b></small><br/>Action: Check the bay page in FleetWrangler t..."]
is-the-issue-resolved{"<small><b>Step 4</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 5</b></small><br/>Reference: The Aircraft may return to service.")
power-cycle-the-aircraft["<small><b>Step 6</b></small><br/>Action: Power cycle the Aircraft."]
check-the-bay-page-in-fleetwrangler-2["<small><b>Step 7</b></small><br/>Action: Check the bay page in FleetWrangler t..."]
is-the-issue-resolved-2{"<small><b>Step 8</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service-2("<small><b>Step 9</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-asw-delivery-support-on-call{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to ASW Delivery Support On C..."}}
restart-the-aircraft-s-flight-target --> wait-20-seconds
wait-20-seconds --> check-the-bay-page-in-fleetwrangler
check-the-bay-page-in-fleetwrangler --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| the-aircraft-may-return-to-service
is-the-issue-resolved -->|No| power-cycle-the-aircraft
power-cycle-the-aircraft --> check-the-bay-page-in-fleetwrangler-2
check-the-bay-page-in-fleetwrangler-2 --> is-the-issue-resolved-2
is-the-issue-resolved-2 -->|Yes| the-aircraft-may-return-to-service-2
is-the-issue-resolved-2 -->|No| escalate-to-asw-delivery-support-on-call
style restart-the-aircraft-s-flight-target fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-20-seconds fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-the-bay-page-in-fleetwrangler fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style power-cycle-the-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-the-bay-page-in-fleetwrangler-2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-2 fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service-2 fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-asw-delivery-support-on-call 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.