Repository navigation
[audit-workflows] Agentic Workflow Audit — 2026-08-20 (fleet-wide codex outage, 80.6% success rate) #54358
Closed
Replies: 2 comments
|
This discussion was automatically closed because it expired on 2026-08-21T21:46:11.347Z.
|
0 replies
|
This discussion was automatically closed because it expired on 2026-08-21T21:46:11.347Z.
|
0 replies
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.
Overview
Full ~24h audit (444 runs, last cycle was 2026-07-06 — a 45-day audit-cadence gap). Fleet success rate: 80.6% raw / 80.7% adjusted (excl. intentional-failure guardrail workflows Daily Credit Limit Test and Daily Max Ai Credits Test — only 3 runs matched, so the exclusion barely moves the needle this cycle). The dominant new signal is a fleet-wide codex-engine outage (0/18, 100% fail) — the rest of the fleet is broadly on the established chronic baseline, with two other notable escalations below.
Key metrics
Charts
Success rate sits at 80.6%, a step down from the 86.25% recorded on 2026-07-06 — driven almost entirely by the new codex outage rather than a broad-based decline. The 45-day gap between audit points is visible as empty space in the trend; day-to-day granularity is lost for that stretch, so this reading is a two-point comparison, not a trend line.
Daily AIC (16,508.6) is broadly in line with the pre-gap baseline (~29.6K on the last full day observed, prior to several partial-window readings), used here in preference to raw tokens since the fleet's
TokenUsageaggregation gap (tracked astoken-usage-reporting-gap) still affects reliability of the raw token metric. No single-workflow cost spike stands out this cycle.Findings
Collection phase — outliers and hard failures
registry.npmjs.orgin 36.8 minutes (99.98% of all requests), hit its 30-min timeout, and failed viadriver_exit. Root cause: the workflow'stools.bashallowlist includesnpm*/npx *, butallowed_domainsis restricted to*.grafana.net,*.sentry.io,defaults— no npm registry host.intentional_failure=true(unlike its sibling "Daily Credit Limit Test"), requiring a name-regex workaround in this cycle's rollup.Clustering phase — known issues vs. novel anomalies
codex-gh-aw-binary-not-found-for-mcp— escalated to CRITICAL, from one chronic workflow to a total engine outage (recurrence 6).claude-agent-job-fail-longrun— new severe instance (npm firewall storm) + Design Decision Gate added to affected list.copilot-sdk-driver-failures— recurrence 25; Ponytail Reviewer and Daily Go Test Parallelizer now lead this family sinceSmoke CIno longer exists under that name (it appears restructured into ~13 per-engine "Smoke X" workflows) —smoke-ci-copilot-cli-100pct-fail-on-pushis marked RESOLVED-OBSOLETE.safe-output-partial-failure-intolerance— PR Sous Chef (5/71 fail at "Process Safe Outputs"); engine attribution corrected to pi (all 71 runs), not copilot as previously logged.pi-gpt54-0tok-agentjob-fail— flipped from RECOVERED-WATCH back to OPEN (Auto-Triage Issues relapse).daily-max-ai-credits-test-mistagged(LOW severity, data-quality).Recommendation phase — smallest actionable fix set
registry.npmjs.orgtoallowed_domains(or add retry backoff) for any workflow whosetools.bashallowlist includesnpm*/npx *. Audit other workflows for the same gap before it repeats elsewhere.intentional_failureauto-tagging for the AI-credit guardrail path.Next actions
Codex outage (#1) is the clear top priority — it's a full engine outage affecting 10 workflows including moderation coverage, not a routine chronic-workflow recurrence. Repo memory (
known-issues.json,workflow-trends.json,recommendations.json,anomalies.json,metrics-summary.json,audit-history.jsonl) has been updated with all findings above, cross-referenced against prior cycles, and validated within storage limits (75 KB / 7 files).References:
All reactions