[audit-workflows] π Agentic Workflow Audit β 2026-08-13 (38-day gap): 6 chronic issues resolved, new Design Decision Gate hotspot #52590
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #52790. |
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
Daily audit of the last 24h of agentic workflow runs in
github/gh-aw(2026-08-12T21:36Z β 2026-08-13T21:09Z, full coverage confirmed). This audit follows a 38-day monitoring gap (prior audit: 2026-07-06) β see the anomaly flagged below.341 runs Β· 298 success Β· 43 failure Β· 87.39% raw success rate (87.32% excluding 2 intentional-failure guardrail tests)
The headline is good news: six previously-chronic issues appear resolved, and the mix of failures has shifted from a few dominant repeat offenders to a thin long tail plus one new concentrated hotspot.
Key metrics
Resolved this window (all were chronic/recurring as of the last audit):
avenger-err-config-no-structured-logsβ Avenger 6/6 success (was 100%-fail chronic since ~06-08, firing every ~90min)chroot-node-not-availableβ Daily Issues Report Generator ran successfullycodex-gh-aw-binary-not-found-for-mcpβ Daily Cache Strategy Analyzer ran successfullypi-gpt54-0tok-agentjob-failβ Auto-Triage Issues 4/4 success on pi/gpt-5.4aoai-apikey-persistent-transient-api-errorβ both AOAI Smoke variants succeededplaywright-install-cli-failureβ not recurringUnclear β needs maintainer confirmation:
Smoke CI, the prior #1 chronic offender (100% fail on every push as of 07-06, ~31% of all fleet failures), produced zero runs in this 24h window. Logs alone can't distinguish "fixed and quiet," "disabled," "renamed," or "no pushes triggered it" β please confirm workflow status.New hotspot:
Design Decision Gate ποΈ(claude engine) failed 4/14 = 28.6% of its runs, independently corroborated by the built-in observability insights (29% hotspot flag). All 4 failures show real token consumption (14,955β17,389 tokens) butTurns=0β the classic longrun-0turn signature previously seen chronically incopilot-sdk-driver-failures, but this is the first time it has concentrated this heavily on one specific (PR-gating) workflow rather than spreading thin. Since this workflow gates PR merges, it's a higher-priority target than the same signature elsewhere.Still open / recurring:
copilot-sdk-driver-failures/claude-agent-job-fail-longrunβ signature persists but now diffused thin across ~20 different workflows (1 fail each, 10Kβ82K real tokens, 7β52min durations) rather than concentratedcode-scanning-fixer-0tok-agentjob-failβ 2/4 fail, but signature evolved: now real token usage (14.8K/10.1K tok, 26min) rather than the original instant 0-tok fail β likely should merge into the longrun familydaily-fact-codex-gpt54-0turnβ 3rd recurrence, low-volume (1 run, 0-tok)token-usage-reporting-gapβ improved (90.6% of runs now report tokens, up from near-zero) but not fully closedTrend charts
Daily success/failure counts and success-rate line over the last 30 days plus today. The shaded band marks the 38-day audit gap (2026-07-06 β 2026-08-13) β deliberately left disconnected rather than interpolated, since no data exists for that span. Visible history shows a volatile June (68β98% swinging day to day) settling into today's healthy 87.4%, consistent with the resolved-issues list above.
Daily AI Credits (AIC) consumption, chosen over raw token totals per the known
token-usage-reporting-gapissue. The 7-day moving average line stops at the gap boundary rather than bridging it; today's single post-gap reading (14,282 AIC) is shown as an isolated diamond marker since one point can't support a rolling average. Today's AIC is roughly half of the late-June peak (~29.6K), consistent with the lower overall failure/retry volume this window.Per-run failure sample used for hotspot confirmation
Design Decision Gate ποΈrun Β§31729681682 (PR #52541, run_attempt=2): jobagentfailed at step "Execute Claude Code CLI" withmetrics={TokenUsage:15341, Turns:0, ToolCalls:null}β real token consumption, zero recorded turns. Raw CLI stderr was not accessible (permission-denied on theusage/log subdirectory), so the exact failure reason inside the Claude Code CLI process could not be captured from this audit alone.Recommendations
Execute Claude Code CLIstderr/exit-code capture on Design Decision Gate first β it's the most concentrated instance of the still-open longrun-0turn family, and it gates PR merges.code-scanning-fixer-0tok-agentjob-failinto the longrun family β its failure signature has evolved to match (real tokens, long duration) rather than the original instant 0-tok fail.Full findings, dedup'd issue tracking, and per-workflow trend snapshots have been merged into repo-memory (
known-issues.json,recommendations.json,anomalies.json,workflow-trends.json,metrics-summary.json,audit-history.jsonl).References:
All reactions