HIGH_EDGE_LATENCY
This alarm is covered by this guide. 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 system has a high clock error event and will not recover. The inputs to the system clock are GNSS, cell, and the wired dock connection.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft-for-steps-see{"<small><b>Step 1</b></small><br/>Question: Power cycle the Aircraft. For steps, ..."}
return-the-aircraft-to-service("<small><b>Step 2</b></small><br/>Reference: Return the Aircraft to Service.")
escalate-to-embedded-linux-oncall{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
power-cycle-the-aircraft-for-steps-see -->|Yes| return-the-aircraft-to-service
power-cycle-the-aircraft-for-steps-see -->|No| escalate-to-embedded-linux-oncall
style power-cycle-the-aircraft-for-steps-see fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-aircraft-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-embedded-linux-oncall fill:#fef3c7,stroke:#f59e0b,color:#78350f 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.