DROID_ERROR_AUTO_KIOSK_DESCENT_MOTION_FAILED
Viewing this guide for
Applicable alarms (1)
DROID_ERROR_AUTO_KIOSK_DESCENT_MOTION_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.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-approach-fiducials-error-in-trace{"<small><b>Step 1</b></small><br/>Question: Does DROID_ERROR_AUTO_KIOSK_APPROACH_..."}
follow-approach-fiducials-guide("<small><b>Step 2</b></small><br/>Reference: Follow the DROID_ERROR_AUTO_KIOSK_AP...")
isolated-or-persistent-failure{"<small><b>Step 3</b></small><br/>Question: This is usually caused by the droid g..."}
approved-to-return-to-service["<small><b>Step 4</b></small><br/>Action: Zipping Point is approved to return t..."]
escalate-to-p2-droid-autonomy{{"<small><b>Step 5</b></small><br/>Escalation: Escalate to P2 Droid Autonomy On Call."}}
is-approach-fiducials-error-in-trace -->|Yes| follow-approach-fiducials-guide
is-approach-fiducials-error-in-trace -->|No| isolated-or-persistent-failure
isolated-or-persistent-failure -->|Isolated occurrence| approved-to-return-to-service
isolated-or-persistent-failure -->|Persistent failure| escalate-to-p2-droid-autonomy
style is-approach-fiducials-error-in-trace fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-approach-fiducials-guide fill:#f3e8ff,stroke:#a855f7,color:#581c87
style isolated-or-persistent-failure fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style approved-to-return-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-droid-autonomy fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Does DROID_ERROR_AUTO_KIOSK_APPROACH_FIDUCIALS_NOT_DETECTED appear in the error trace?
2 reference
3 question
This is usually caused by the droid getting too low, trying to enter the zipping point, and bumping into the funnel.
Is this an isolated occurrence or a persistent failure?
Is this an isolated occurrence or a persistent failure?
4 action
Zipping Point is approved to return to service.
5 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
Open pull requests
There are no open pull requests.