[audit-workflows] Agentic Workflow Audit — 2026-08-04: 93.2% success, 2 new failure clusters (Goose, Aider) #50409
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #50693. |
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.
Agentic Workflow Audit — 2026-08-04
Window: full 24h, 2026-08-03T21:42Z → 2026-08-04T21:45Z · 220 runs collected across 3 paginated fetches (no gaps between pages).
Headline numbers
All 15 failures are 0-turn/driver-level (14
driver_exit, 1agent_logic) — zero missing-tool, missing-data, or agent-logic-content failures in the real (non-intentional) set.Daily Max Ai Credits Testfailed by design (credit-guardrail trip) and is excluded from rate rollups per policy.The health chart shows today's 93.2% sitting comfortably inside the pre-gap baseline band (60–98%), with the shaded region marking the 29-day audit blind spot. No sign of fleet-wide degradation resuming after the gap.
Token usage looks like a cliff from ~50M/day (mid-June) to ~6M today, but most of that drop is a reporting-coverage artifact: the long-standing
token-usage-reporting-gapknown issue means most July days havenullfleet-wide token totals rather than genuine near-zero usage. Today's 6.28M is the first fully-populated multi-page collection since the gap and should be treated as the new reliable baseline going forward, not evidence of a 8x usage drop.Engine reliability breakdown
Failure clusters (evidence-linked)
1. Smoke Goose — 100% failure (4/4 this window, 5/5 in a wider same-engine query) — NEW cluster, no prior record in memory
Two distinct root causes observed across the failing runs, both surfaced in
agent-stdio.logafter real container start:Authentication error: Authentication failed for (172.30.0.30/redacted) Status: 401 Unauthorized. Response: Incorrect API key provided: github_pat_.../ghs_1536...— a GitHub token (PAT/installation token) is being sent to the model proxy where an OpenAI-shaped key is expected.Warning: Failed to start extension 'safeoutputs'and'github'— connection refused tolocalhost:8080/mcp/safeoutputsand/mcp/github— the MCP gateway is unreachable from the Goose harness at startup on every run.Evidence: run_ids 30951782455, 30944874071, 30932534640, 30908234685 (
/tmp/gh-aw/aw-mcp/logs/run-(id)/agent-stdio.log).2. Smoke Aider — 100% failure (2/2) — NEW cluster, no prior record in memory
aider_harness.cjs'spip installstep fails before the agent ever starts. Root cause chain: installing aider's dependencyfastuuidhas no prebuilt wheel for the PyPy 3.11 runner, so pip falls back to a source build viamaturin/cargo, which needsindex.crates.io. That domain is not in the workflow's allowed-domains list — the CONNECT tunnel returns403, cargo/maturin fails, andaider_harness.cjsthrowsError: Aider installation failed.Evidence: run_ids 30951915720, 30944867248 —
pip: error: subprocess-exited-with-error→Could not connect to server (CONNECT tunnel failed, response 403)→maturin failed→Error: Aider installation failed.3.
copilot-sdk-driver-failures(known issue, recurring since 2026-06-02, recur=24 as of last record) — 4 more instances todayPR Code Quality Reviewer ×3 (run_ids 30943711376, 30943794959, 30935203223 — all 4-turn/1-turn sessions with real tool activity, 0 blocked domains, 0 failed tool executions, then a silent driver exit code 1) and Linter Miner ×1 (real aic=122.4/tokens=68.7K then same silent exit). Both workflow names were already in this issue's
affectedlist from the 07-05/07-06 audits — this is a clean recurrence, not a new signature.4. Isolated singletons (not deep-dived — single occurrence each, no artifact fetched): CI Optimization Coach, Daily Agent of the Day Blog Writer (both already-known
affectedname), Slide Deck Maintainer — consistent with historical 0-turn driver-exit noise floor, not escalated.Recommendations (smallest actionable set)
agent-stdio.log.)index.crates.ioto Smoke Aider's allowed-domains, or pin an aider/fastuuid version with a prebuilt PyPy wheel to avoid the cargo/maturin build path entirely. (Evidence: 2/2 runs, identicalCONNECT tunnel failed, response 403→maturin failedchain.)safeoutputs/githubextensions fail to connect on 100% of Goose runs (localhost:8080/mcp/...connection refused), independent of the auth issue above. Likely the gateway isn't ready when Goose's harness starts, or Goose isn't using the same gateway wiring as other engines.copilot-sdk-driver-failures— track as-is; today's 4 instances are consistent with the existing 24-recurrence pattern and already-known affected workflow list.Repo memory
known-issues.json,workflow-trends.json,metrics-summary.json,audit-history.jsonl, andanomalies.jsonupdated:copilot-sdk-driver-failuresrecurrence bumped to 25 (last_seen 2026-08-04); two new OPEN issues added (smoke-goose-proxy-auth-mcp-gateway-failure,smoke-aider-fastuuid-crates-io-blocked); today's metrics appended.References:
All reactions