Repository navigation
[audit-workflows] Agentic Workflow Audit — 2026-10-22 #71226
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #71497. |
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.
Summary
The sampled runs show recurring driver exits and a high AI Moderator failure rate, with zero missing tools. The 30-day request returned 338 runs from only 17 hours on October 22; the 24-hour request returned 100 runs from 4 hours 44 minutes. Both hit collection limits, so these are partial samples rather than full-period rollups.
Collection and health
Daily Credit Limit Testrun gives 277/324 (85.5%). The sample had 82 errors, 37 driver exits, 9 agent-logic failures, 0 missing tools, and 0 warnings.Findings and recommendations
Handle agent failureappeared in 32 failures across 17 workflows;Checkout PR branchappeared in 20 failures across five workflows. Both failure patterns recur in recent audits. Review the common conclusion handler and checkout step across affected workflows.Daily Cache Strategy Analyzerused 3,377,391 tokens in 35 action minutes, the largest sampled run.Trend charts
The collected October 22 bucket contains 277 successful and 47 failed executed runs after excluding the intentional-failure run, for an adjusted 85.5% rate. Only one daily bucket was available, so this does not show a 30-day trend.
The sampled bucket contains 53,668,233 tokens after excluding the intentional-failure run; the largest individual run used 3.38 million tokens. A seven-day moving average is unavailable because the fetch produced only one daily bucket.
View full findings
driver_exit_failure_hotspot,ai_moderator_failure_hotspot, andincomplete_log_coverage.References:
All reactions