Skip to content

Zipping Point Autodiscrepancy GENERAL GUIDE

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (12)
DROID_ERROR_AUTO_KIOSKDROID_ERROR_AUTO_KIOSK_ABORT_REQUESTEDDROID_ERROR_AUTO_KIOSK_ASCEND_TO_TARGET_Z_FAILEDDROID_ERROR_AUTO_KIOSK_ASCENT_MOTION_FAILEDDROID_ERROR_AUTO_KIOSK_DID_NOT_CAPTURE_PACKAGEDROID_ERROR_AUTO_KIOSK_FALLBACK_ASCENT_FAILEDDROID_ERROR_AUTO_KIOSK_FALLBACK_DESCENT_FAILEDDROID_ERROR_AUTO_KIOSK_LINE_TENSION_TOO_HIGHDROID_ERROR_AUTO_KIOSK_MISSION_FAILEDDROID_ERROR_AUTO_KIOSK_PORTAL_DESCENT_FAILEDDROID_ERROR_AUTO_KIOSK_PUT_PACKAGE_BACK_FAILEDDROID_ERROR_AUTO_KIOSK_WINCH_OPERATION_FAILED
Likely outcomes (0 missions) — click to expand

Based on 0 missions where this alarm fired in the last 90 days (for DROID_ERROR_AUTO_KIOSK) as of 2026-10-13

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

The process for troubleshooting discrepancies with zipping points differs from that for other assets. The zipping point does not have its own logs, and error codes are often generated by the droid, which means they often do not contain enough information to successfully root cause an issue without video logs. The following process is intended to reduce zipping point downtime and avoid unnecessary review of logs.

Using/Setting Up Baraza for Triaging Zipping Point

Section titled “Using/Setting Up Baraza for Triaging Zipping Point”
  1. Go to https://baraza2.platform.flyzipline.com/ and click on “Missions and Flights”.
  2. Click on “Columns” on the left side of the screen, and make sure you have selected “Mission ID”, “Mission Start”, “Duration”, “Assets”, “Status”, and “Mission Root Errors”. Pin them all to the left side of the screen so that it looks like this:

image-20260209-225834.png

  1. Throughout the troubleshooting process, you will be using this menu to search for the past missions of the zipping point AND droid. Here are some things you may want to consider as you triage.
    • Did the zipping point fail multiple missions in a row? Do they have the same error code/cause?
    • Did the droid fail multiple missions in a row? Do they have the same error code/cause?
    • Is the mission duration long enough that the droid ever reached the zipping point? (Ex. If a mission is 30s long, the zipping point cannot be at fault and should be cleared)
    • Are the mission start times recent, or are there some failures from yesterday/several hours ago that are possibly unrelated to the issue being investigated.

NOTE: Sometimes, baraza will filter by a category that is not being displayed. Ensure you are only applying intentional filters by clicking the filter icon in the top left of the page.

1 question
Open the discrepancy and note the associated error codes in Zerp. Is the winch_cutter_deployed_in_zipping_point or droid_left_behind alarm present?

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.