batch-health

Automated batch health auditing cross-references expected runs parsed from aeon.yml schedules against actual GitHub Actions runs in the 06:00–07:30 UTC morning window, classifying execution status as OK, MISSING, or FAILED to detect silent misses.

A batch run gap is a missed scheduled execution within the expected morning window. Incident management detects silent misses by parsing aeon.yml schedules, fetching actual runs, cross-referencing results, and automatically generating batch-health issues when outages occur.

To monitor scheduled skills, run a batch-health audit that evaluates the 06:00–07:30 UTC morning window. The audit parses aeon.yml schedules, filters enabled skills, fetches actual runs, and cross-references results to verify expected executions.

Batch-health works with cron-audit schedules defined in aeon.yml by parsing the configuration to build expected run lists, filtering enabled scheduled skills by cron schedule and day of month to verify morning window executions.

When a scheduled skill misses its expected execution window, the audit classifies it as MISSING and automatically generates a batch-health issue. This incident logging alerts operations teams to batch-level outages for immediate investigation.

Post-batch health auditing is needed because scheduled skills can fail silently without standard error alerts. The audit validates all enabled skills fired correctly, detects execution gaps, and files outage issues to support daily operations reliability.