[agent-job-health] Agent Job Health Monitor - 2026-08-18: 3.33% fleet failure rate, 3 untracked schedule blind spots #53854
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Window: 2026-08-17T22:46:22Z to 2026-08-18T22:46:22Z (24h, agent-job scope only)
history.jsonl- this is the baseline entry, so no day-over-day comparison is available yet.Note
Fleet-wide agent-job health is stable this window (3.33% run-weighted failure rate, concentrated in a handful of chronic-offender workflows already under active investigation). No regression signal - this is the first recorded baseline. The one actionable finding is in Schedule Heartbeat below: 3 scheduled workflows have gone silent well past their expected cadence.
Failure Rate by Step
Tracked Failures
Execute GitHub Copilot CLIsignature; not independently re-verified this windowNo duplicate issue opened for this cluster - recommend the 4 unconfirmed rows above be attached to #52253 once re-verified (see Recommendations).
Novel Failure Clusters
Two single-occurrence, single-workflow failures - below the >=2-workflow / >=10%-of-runs threshold for opening a new issue. Each already has a per-run auto-filed failure issue; neither has a root-cause tracking issue yet:
Schedule Heartbeat
Warning
3 of 187 schedule-triggered workflows have gone silent well beyond 2x their expected cadence, with no open issue tracking the gap. All three last runs completed successfully - they simply stopped being triggered, which is the defining "silent blind spot" pattern this check targets.
.github/workflows/craft.lock.yml.github/workflows/daily-hippo-learn.lock.yml.github/workflows/smoke-ci.lock.ymlsmoke-cialso has apull_requesttrigger, so it may still be running on PR events even though itsschedule:trigger looks dormant. An issue has been opened for this finding (see below) since it was untracked.Full per-workflow breakdown (80 workflows, 300 runs)
Note: PR Sous Chef, Issue Monster, and Contribution Check - the fleet's known chronic offenders - had zero agent-job failures this window. Their visible failure volume (many open "[aw] Failed jobs: ..." issues, e.g. the PR Sous Chef
safe_outputs-job JSON-parse crash tracked in #53804) is entirely in thesafe_outputsjob, which is out of scope for this report.Recommendations
timeout-minutesfor Agentic Workflow Audit Agent above the current 30 minutes if this becomes recurring (see [aw] Agentic Workflow Audit Agent timed out #53835).References:
All reactions