LATCH_POLL_PERIOD_TOO_LONG
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”This alarm indicates that the latch service was starved of CPU. It indicates a software problem.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
select-one-of-the-following-statements{"<small><b>Step 1</b></small><br/>Question: Select one of the following statements:"}
resend-the-mission["<small><b>Step 2</b></small><br/>Action: Resend the mission."]
create-a-discrepancy-on-the-dock-and{{"<small><b>Step 3</b></small><br/>Escalation: Create a Discrepancy on the Dock and ..."}}
select-one-of-the-following-statements -->|The alarm occurred once and...| resend-the-mission
select-one-of-the-following-statements -->|The alarm has occurred more...| create-a-discrepancy-on-the-dock-and
style select-one-of-the-following-statements fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style resend-the-mission fill:#dcfce7,stroke:#22c55e,color:#14532d
style create-a-discrepancy-on-the-dock-and 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.