Skip to content
Zipline Zipline Service Documentation

    Dock ASAP

    published HW: EV2HW: EV3

    If the Zip Executive On Call detects a DockASAP trigger during delivery while the Droid is descending, the Droid will now attempt to abort delivery, leading to a published mission failure. This does not include operator-commanded dock requests, which will still be rejected during an active delivery.

    The Zip will not enter a terminal failure state following automated DockASAP for certain issues deemed recoverable (example: C2 loss). Making a P2P ticket is still encouraged following a “non-terminal” DockASAP, even though intervention may not be necessary to proceed with another mission.

    Did this guide help you get unblocked?

    Open suggestions

    There are no open suggestions.

    Open pull requests

    There are no open pull requests.

    Edit this page on GitHub
    Topic history

    No topic history is available yet for this page.

    Suggest a change