How to Check if Droid is Left Behind
Viewing this guide for
This alarm is covered by this guide. Background
Section titled “Background”To verify that a Droid has been left behind, check the current status of System Fault Responses in Fleet View.
Procedure
Section titled “Procedure”graph TD
is-this-a-recent-failure{"<small><b>Step 1</b></small><br/>Question: Is this a recent failure?"}
open-fleet-apps-here["<small><b>Step 2</b></small><br/>Action: Open Fleet apps herehttps://fleet-..."]
open-the-fleet-view-app["<small><b>Step 3</b></small><br/>Action: Open the Fleet View app."]
open-fleet-view-menu["<small><b>Step 4</b></small><br/>Action: In Fleet View, click the “three lines..."]
select-regions["<small><b>Step 5</b></small><br/>Action: In the drop down list, select **Regio..."]
select-site["<small><b>Step 6</b></small><br/>Action: In the Regions drop-down list, select..."]
select-aircraft["<small><b>Step 7</b></small><br/>Action: Select the Aircraft that has the Droi..."]
view-droids-left-behind["<small><b>Step 8</b></small><br/>Action: **Optional:** To view all Droids that..."]
check-executive-logs["<small><b>Step 9</b></small><br/>Action: If this is not a recent failure, look..."]
is-this-a-recent-failure -->|Yes| open-fleet-apps-here
is-this-a-recent-failure -->|No| check-executive-logs
open-fleet-apps-here --> open-the-fleet-view-app
open-the-fleet-view-app --> open-fleet-view-menu
open-fleet-view-menu --> select-regions
select-regions --> select-site
select-site --> select-aircraft
select-aircraft --> view-droids-left-behind
style is-this-a-recent-failure fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style open-fleet-apps-here fill:#dcfce7,stroke:#22c55e,color:#14532d
style open-the-fleet-view-app fill:#dcfce7,stroke:#22c55e,color:#14532d
style open-fleet-view-menu fill:#dcfce7,stroke:#22c55e,color:#14532d
style select-regions fill:#dcfce7,stroke:#22c55e,color:#14532d
style select-site fill:#dcfce7,stroke:#22c55e,color:#14532d
style select-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style view-droids-left-behind fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-executive-logs fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Is this a recent failure?
2 action
Open Fleet apps here.
3 action
Open the Fleet View app.
5 action
In the drop down list, select Regions.


6 action
In the Regions drop-down list, select the location where the Droid was left behind to view all Aircraft located at the site.


7 action
Select the Aircraft that has the Droid left behind.
The system displays the current state of the Aircraft and the System Fault Response. If the Droid was left behind, the System Fault Response is Droid Left Behind.

The system displays the current state of the Aircraft and the System Fault Response. If the Droid was left behind, the System Fault Response is Droid Left Behind.

8 action
Optional: To view all Droids that have been left behind, navigate to the “Droid Left Behind” section and click to see all Droids that have been left behind.


9 action
If this is not a recent failure, look for these lines that may be present in the aircraft executive logs:
"task_status": "In Progress: The safety app is performing a winch line cut."INFO "DockAsap trigger detected while delivering: CanDeliver failed: Winch line cutter squib is in a terminal state of Success, so deliveries cannot be performed.""reason": "The safety app has completed the winch line cut."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.
