DROID_ERROR_AUTO_KIOSK_DESCEND_TO_LID_FAILED
Applicable alarms (1)
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”The Zipping Point “descend to lid” phase occurs after the Droid has completed its initial controlled descent into the kiosk. During the descend to lid phase, the Droid attempts to pass through the lid. This phase may fail if the Droid fails to reach its target position in the allotted time or fails to perceive that it has reached its target position in the allotted time. Most commonly, this means that the droid reached the top of the lid, but was not able to pass through.
See also: Zipping Point V4 Triage General Process
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
assign-measure-lid-forces-work-order["<small><b>Step 1</b></small><br/>Action: Assign the V4 Zipping Point: Measure..."]
return-asset-to-service-after-work-order["<small><b>Step 2</b></small><br/>Action: Once the work order is completed, ret..."]
assign-measure-lid-forces-work-order --> return-asset-to-service-after-work-order
style assign-measure-lid-forces-work-order fill:#dcfce7,stroke:#22c55e,color:#14532d
style return-asset-to-service-after-work-order fill:#dcfce7,stroke:#22c55e,color:#14532d 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.