[audit-workflows] π‘οΈ Agentic Workflow Audit β 2026-07-23 (healthiest since ~06-24; 97.2%, 0 novel anomalies) #47668
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #47867. |
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-07-23
Window: partial day-slice, 251 fully-downloaded runs (logs MCP timed out at 300s before full aggregation; 228 folders empty). First audit since 2026-07-06 (17-day gap).
Headline: Fleet is the healthiest it has looked since ~06-24. Zero novel anomalies, zero missing-tools / missing-data / MCP failures. Every real failure maps to a known family, and several chronic dominant offenders (Smoke CI, Avenger, PR CQR, Cache Strategy) are absent or recovered.
π Key Metrics
Engine health: claude 46/46 (100%) Β· codex 10/10 (100%) Β· copilot 149/154 (96.8%) Β· pi 37/39 (94.9%) Β· antigravity 1/1 Β· gemini 1/1.
π Trend Charts (30d)
Workflow health rebounds to 97.2% β the top of the 30-day band, well clear of the 90% line and a clean recovery from the 82β86% prod-main trough of the 06-30...07-06 Smoke-CI-dominated stretch. Failure bars are near-flat this slice (7 total, 6 real).
Token reporting is back: 10.97M tokens flowed through
token_usage_summaryafter the 06-19β07-06 reporting gap where daily totals were null/tiny. The moving average lifts off the floor β trust the last point more than the mid-window dip, which reflects missing data, not low usage.π Failure Analysis β 6 real fails, all known families, 0 novel
Full failure breakdown
safe-output-partial-failure-intolerancecopilot-sdk-drivercopilot-sdk-driverchroot-node-not-availablesecurity-gate-trip(NEW)Clustering: copilot
Execute-CLI0-turn family = 3 fails (down from ~71-78% of all fleet fails on 06-30/07-06).safe-output-partial= 2 (now the leading true-signature recurring fail). Security-gate-trip = 1 (probably a real CVE/license finding).β Chronic Offenders β Recovered / Absent
err-config/no-structured-logschronic 100%-fail (recur18, fired ~every 90min).π― Recommendations
safe-output-partialnon-fatal handling β PR Sous Chef (pi/gpt-5.4) reddens 2/20 at Process Safe Outputs after the agent produced valid 55K-token output. Make the safe_outputs job tolerant of a single failed item (skip-and-warn / per-item status) so one bad item can't red a successful agent run. This is now the highest-value fix since the copilot-CLI-0turn family has declined.ποΈ Repo Memory
Updated all six files:
audit-history.jsonl(+1 entry),metrics-summary.json(latest_window + 07-23 history point),known-issues.json(16 issues β 6 recoveries de-escalated to WATCH, 1 NEW gate-trip),recommendations.json(16 β 2 new),anomalies.json(Smoke CI / Avenger / copilot-0turn de-escalated),workflow-trends.json(29-wf snapshot).References:
All reactions