`stale_mission_lock_pending_confirmation` Aircraft Locked by Cloud
Viewing this guide for
Applicable alarms (1)
stale_mission_lock_pending_confirmation
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 cloud Fleet Scheduler is responsible for sending missions to aircraft and locking the aircraft and other required mission assets to a lease for the mission. When the cloud successfully sends a mission to the aircraft, the Obsatories system assigns locks the leased assets until a terminal MissionUpdate status (status of COMPLETED, ENDED_IN_FAILURE, or REJECTED) is received by the cloud from the aircraft. If that message is not received the cloud will lock the aircraft and associated assets to the lease indefinitely until a Call Home request is received from the aircraft. A Call Home request will not be sent until the aircraft’s Zip Executive service is restarted.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-the-aircraft-docked{"<small><b>Step 1</b></small><br/>Question: Is the Aircraft docked?"}
place-the-aircraft-into-a-dock-and-then["<small><b>Step 2</b></small><br/>Action: Place the Aircraft into a Dock and th..."]
an-open-grounding-issue-exists-in-zerp["<small><b>Step 3</b></small><br/>Action: An open grounding issue exists in Zer..."]
power-cycle-the-aircraft-power-cycle-ai["<small><b>Step 4</b></small><br/>Action: Power cycle the Aircraft Power Cycl..."]
confirm-that-the-aircraft-completes-the["<small><b>Step 5</b></small><br/>Action: Confirm that the aircraft completes t..."]
is-the-issue-resolved{"<small><b>Step 6</b></small><br/>Question: Send the Zip its next mission. The st..."}
what-is-the-terminal-mission-status{"<small><b>Step 7</b></small><br/>Question: The stale mission lock is cleared. Is..."}
the-aircraft-may-return-to-service("<small><b>Step 8</b></small><br/>Reference: The Aircraft may return to service.")
troubleshoot-the-new-mission-outcome("<small><b>Step 9</b></small><br/>Reference: Do not delete and re-create the Zip; ...")
is-the-stuck-mission-a-softwareupdate{"<small><b>Step 10</b></small><br/>Question: Is the stuck mission a SoftwareUpdate?"}
follow-the-persistent-ota-mission-issues-guide("<small><b>Step 11</b></small><br/>Reference: Follow the Persistent OTA Mission Is...")
did-re-registering-the-zip-clear-the-stale-mission{"<small><b>Step 12</b></small><br/>Question: Only perform this recovery after conf..."}
send-a-health-checks-mission-after-re-registering["<small><b>Step 13</b></small><br/>Action: Send the Zip a Health Checks mission."]
did-the-health-checks-mission-pass-after-re-registering{"<small><b>Step 14</b></small><br/>Question: Did the Health Checks mission complet..."}
the-aircraft-may-return-to-service-after-re-registering("<small><b>Step 15</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-asw-delivery-support-oncall{{"<small><b>Step 16</b></small><br/>Escalation: Escalate to ASW Delivery Support On C..."}}
is-the-aircraft-docked -->|Yes| an-open-grounding-issue-exists-in-zerp
is-the-aircraft-docked -->|No| place-the-aircraft-into-a-dock-and-then
place-the-aircraft-into-a-dock-and-then --> an-open-grounding-issue-exists-in-zerp
an-open-grounding-issue-exists-in-zerp --> power-cycle-the-aircraft-power-cycle-ai
power-cycle-the-aircraft-power-cycle-ai --> confirm-that-the-aircraft-completes-the
confirm-that-the-aircraft-completes-the --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| what-is-the-terminal-mission-status
is-the-issue-resolved -->|No| is-the-stuck-mission-a-softwareupdate
what-is-the-terminal-mission-status -->|COMPLETED| the-aircraft-may-return-to-service
what-is-the-terminal-mission-status -->|ENDED_IN_FAILURE or REJECTED| troubleshoot-the-new-mission-outcome
is-the-stuck-mission-a-softwareupdate -->|Yes| follow-the-persistent-ota-mission-issues-guide
is-the-stuck-mission-a-softwareupdate -->|No| did-re-registering-the-zip-clear-the-stale-mission
did-re-registering-the-zip-clear-the-stale-mission -->|Yes| send-a-health-checks-mission-after-re-registering
did-re-registering-the-zip-clear-the-stale-mission -->|No| escalate-to-asw-delivery-support-oncall
send-a-health-checks-mission-after-re-registering --> did-the-health-checks-mission-pass-after-re-registering
did-the-health-checks-mission-pass-after-re-registering -->|Yes| the-aircraft-may-return-to-service-after-re-registering
did-the-health-checks-mission-pass-after-re-registering -->|No| escalate-to-asw-delivery-support-oncall
style is-the-aircraft-docked fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style place-the-aircraft-into-a-dock-and-then fill:#dcfce7,stroke:#22c55e,color:#14532d
style an-open-grounding-issue-exists-in-zerp fill:#dcfce7,stroke:#22c55e,color:#14532d
style power-cycle-the-aircraft-power-cycle-ai fill:#dcfce7,stroke:#22c55e,color:#14532d
style confirm-that-the-aircraft-completes-the fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style what-is-the-terminal-mission-status fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style troubleshoot-the-new-mission-outcome fill:#f3e8ff,stroke:#a855f7,color:#581c87
style is-the-stuck-mission-a-softwareupdate fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-the-persistent-ota-mission-issues-guide fill:#f3e8ff,stroke:#a855f7,color:#581c87
style did-re-registering-the-zip-clear-the-stale-mission fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style send-a-health-checks-mission-after-re-registering fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-health-checks-mission-pass-after-re-registering fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service-after-re-registering fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-asw-delivery-support-oncall fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Is the Aircraft docked?
2 action
Place the Aircraft into a Dock and then continue to the next step.
3 action
An open grounding issue exists in Zerp for the aircraft with an associated alarm
stale_mission_lock_pending_confirmation. 4 action
Power cycle the Aircraft (Power Cycle Aircraft).
5 action
Confirm that the aircraft completes the Call Home process and rejects the prior locked mission.
Use Fleet Wrangler to confirm that the last mission status shows
Use Fleet Wrangler to confirm that the last mission status shows
ZIP_MISSION_STATUS_REJECTED with the error ZIP_EXECUTIVE_CODE_CALL_HOME_HANDSHAKE_FAILED (0x00030009): Mission rejected as a part of the Call Home handshake. 6 question
Send the Zip its next mission.
The stale mission lock is cleared when Fleet Wrangler reports a terminal mission status of
The stale mission lock is cleared when Fleet Wrangler reports a terminal mission status of
COMPLETED, ENDED_IN_FAILURE, or REJECTED. Did the new mission reach one of these terminal statuses? 7 question
The stale mission lock is cleared. Is the mission status
COMPLETED, ENDED_IN_FAILURE, or REJECTED? 8 reference
The Aircraft may return to service.
9 reference
Do not delete and re-create the Zip; troubleshoot the new mission outcome before returning the Aircraft to service.
10 question
Is the stuck mission a
SoftwareUpdate? 11 reference
Follow the Persistent OTA Mission Issues guide.
12 question
Only perform this recovery after confirming that the new mission did not reach a terminal status of
1. Turn off the Zip and change the dock operation mode to Diagnostic.
2. Record which dock the Zip is occupying.
3. Record all notes and tags currently applied to the Zip in Fleet Wrangler, including the software version, EV3, and any special configurations.
4. Delete the Zip in Fleet Wrangler.
5. Wait 2 minutes, then turn the Zip back on through the dock in Fleet Wrangler or via SSH.
6. Restore all notes and tags that were previously applied to the Zip in Fleet Wrangler.
7. Return the dock to Standard operation mode and confirm that Fleet Wrangler reports the dock in Standard mode.
Did this clear the stale mission on the Zip?
COMPLETED, ENDED_IN_FAILURE, or REJECTED and that the stale mission remains on the Zip.1. Turn off the Zip and change the dock operation mode to Diagnostic.
2. Record which dock the Zip is occupying.
3. Record all notes and tags currently applied to the Zip in Fleet Wrangler, including the software version, EV3, and any special configurations.
4. Delete the Zip in Fleet Wrangler.
5. Wait 2 minutes, then turn the Zip back on through the dock in Fleet Wrangler or via SSH.
6. Restore all notes and tags that were previously applied to the Zip in Fleet Wrangler.
7. Return the dock to Standard operation mode and confirm that Fleet Wrangler reports the dock in Standard mode.
Did this clear the stale mission on the Zip?
13 action
Send the Zip a Health Checks mission.
14 question
Did the Health Checks mission complete successfully and pass?
15 reference
The Aircraft may return to service.
16 escalation
Escalate to ASW Delivery Support On Call. Further support may be obtained via secondary escalation to P2 Exec 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.