CRITICAL_LOG_PROCESSOR_TIMEOUT
Applicable alarms (1)
Likely outcomes — click to expand
Based on 77 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 20 ZERP issues filed on these missions)
Top work orders
- Maintenance Check Flight (MCF) · MAINTENANCE_ACTION 13
Frequently co-occurring alarms (% of the 77 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm is raised when the Exec V4 critical log processor exceeds its expected processing timeout.
The operational impact, expected root causes, telemetry indicators, and maintenance actions still need to be documented.
Engineering follow-up needed
Section titled “Engineering follow-up needed”Daniel Kolbman:
- Define the exact failure condition that triggers this alarm.
- Document likely root causes.
- Identify expected aircraft behavior and mission impact.
- Provide recommended troubleshooting and recovery procedures.
- Identify any telemetry or Baraza templates that should be referenced.
graph TD
collect-background-and-triage-guidance("<small><b>Step 1</b></small><br/>Reference: This page is currently a placeholder ...")
style collect-background-and-triage-guidance fill:#f3e8ff,stroke:#a855f7,color:#581c87 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.