DROID_ERROR_AUTO_KIOSK_DOOR_OPEN_FAILED
Viewing this guide for
Applicable alarms (1)
DROID_ERROR_AUTO_KIOSK_DOOR_OPEN_FAILED
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days 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 error may occur anytime doors are commanded open in a zipping point loading. There are two behaviors that require the doors to close:
- Nominal state progression: Doors are commanded open when the Droid enters the zipping point.
- Off nominal state progression: Doors are commanded open after the Droid has lifted off the platform to release a stuck or heavy package.
This can be an issue with the droid door hardware, but could also occur because the operator loaded a package that was too large or too heavy for the droid.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
did-the-alarm-occur-during-a-dlb{"<small><b>Step 1</b></small><br/>Question: Did the alarm occur during a Droid Le..."}
complete-the-dlb-work-orders["<small><b>Step 2</b></small><br/>Action: Complete the work orders listed below..."]
complete-the-zipping-point-v4-triage-ge("<small><b>Step 3</b></small><br/>Reference: Complete the Zipping Point V4 Triage...")
assign-the-v4-zipping-point-perform-sta["<small><b>Step 4</b></small><br/>Action: Assign the V4 Zipping Point: Perform..."]
while-waiting-for-the-results-of-the-in{"<small><b>Step 5</b></small><br/>Question: While waiting for the results of the ..."}
if-there-are-no-other-issues-with-the-z["<small><b>Step 6</b></small><br/>Action: If there are no other issues with the..."]
was-the-weight-of-the-package-near-or-g{"<small><b>Step 7</b></small><br/>Question: Was the weight of the package near or..."}
yes-if-there-are-no-other-issues-with-t["<small><b>Step 8</b></small><br/>Action: If there are no other issues with the..."]
no-escalate-to-p2-droid-autonomy-on-cal{{"<small><b>Step 9</b></small><br/>Escalation: Escalate to P2 Droid Autonomy On Call"}}
did-the-alarm-occur-during-a-dlb -->|Yes| complete-the-dlb-work-orders
did-the-alarm-occur-during-a-dlb -->|No| complete-the-zipping-point-v4-triage-ge
complete-the-zipping-point-v4-triage-ge --> assign-the-v4-zipping-point-perform-sta
assign-the-v4-zipping-point-perform-sta --> while-waiting-for-the-results-of-the-in
while-waiting-for-the-results-of-the-in -->|Yes| if-there-are-no-other-issues-with-the-z
while-waiting-for-the-results-of-the-in -->|No| was-the-weight-of-the-package-near-or-g
was-the-weight-of-the-package-near-or-g -->|YES| yes-if-there-are-no-other-issues-with-t
was-the-weight-of-the-package-near-or-g -->|NO| no-escalate-to-p2-droid-autonomy-on-cal
style did-the-alarm-occur-during-a-dlb fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style complete-the-dlb-work-orders fill:#dcfce7,stroke:#22c55e,color:#14532d
style complete-the-zipping-point-v4-triage-ge fill:#f3e8ff,stroke:#a855f7,color:#581c87
style assign-the-v4-zipping-point-perform-sta fill:#dcfce7,stroke:#22c55e,color:#14532d
style while-waiting-for-the-results-of-the-in fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style if-there-are-no-other-issues-with-the-z fill:#dcfce7,stroke:#22c55e,color:#14532d
style was-the-weight-of-the-package-near-or-g fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style yes-if-there-are-no-other-issues-with-t fill:#dcfce7,stroke:#22c55e,color:#14532d
style no-escalate-to-p2-droid-autonomy-on-cal fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Did the alarm occur during a Droid Left Behind (DLB) event?
2 action
Complete the work orders listed below:
- Aircraft: Complete the work order for the relevant aircraft version:
- EV2: #195: Inspect Aircraft after Droid Left Behind (DLB)
- EV3: #662: Inspect Aircraft after Droid Left Behind (DLB)
- Droid: Complete the following work orders in order:
1. #1169: Reset Droid after DLB
2. #1196: Offload Droid Logs after DLB
- Aircraft: Complete the work order for the relevant aircraft version:
- EV2: #195: Inspect Aircraft after Droid Left Behind (DLB)
- EV3: #662: Inspect Aircraft after Droid Left Behind (DLB)
- Droid: Complete the following work orders in order:
1. #1169: Reset Droid after DLB
2. #1196: Offload Droid Logs after DLB
3 reference
Complete the Zipping Point V4 Triage General Process.
4 action
Assign the V4 Zipping Point: Perform Standard Field Inspection - Ranger work order, and open an incident channel. Tag
@zrangers or @dfw-zp-rangers (depending on location), and ask them to complete the work order and to notify you when it has been completed. 5 question
While waiting for the results of the inspection, review the video log from the droid’s center camera. Was the package larger than the height of the platform, touching the sides of the walls of the package cavity, or damaged in any way?
6 action
If there are no other issues with the zipping point, return it to service. Let the operator know that the package is too large/damaged, ask them to remove it, and clarify the size restrictions for packages.
7 question
Was the weight of the package near or greater than 3000g?
8 action
If there are no other issues with the zipping point, return it to service. Escalate to Zipping Point On Call in the incident channel to report that it is a failure related to package weight.
9 escalation
Escalate to P2 Droid Autonomy 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.