Agentic Workflow Audit — 2026-03-23 #22383
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-24T06:03:44.281Z.
|
Beta Was this translation helpful? Give feedback.
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
22 workflow runs completed in the last 24 hours with a 90.9% success rate (20 success / 2 failure). Token usage was 12.0M tokens at a cost of $1.77. One failure is a known design-by-intent behavior; the other is a genuine concern with excessive agent looping.
Workflow Health Trend
Success rates have held steady at ~88–91% over the past week, recovering from the 72.7% dip on 3/15. Today's 90.9% continues the healthy trend. The 3/20 audit showed only 4 non-skipped runs (80% SR) due to low run volume that day.
Token & Cost Trend
Today's $1.77 spend is slightly below yesterday's $3.31 peak. Token volume of 12.0M is comparable to the 3/21 high of 13.1M. The 3-day moving average has risen sharply — driven by heavy Claude/Copilot usage in Documentation Updater and jsweep workflows.
❌ Failed Runs
1. GitHub Remote MCP Authentication Test — §23422628558
● Listing background agentscalls, never making progress toward the task. No safe output was produced,agent_output.jsonwas never written, and the workflow concluded asfailure.Listing background agents. This may be a background agent feature interaction with the MCP auth test environment. Consider adding a turn-count circuit breaker or a timeout safeguard, and verify the MCP server is reachable during agent startup.2. Duplicate Code Detector — §23420898530
failureto alert maintainers.actions/setup/js/expired-entity cleanup handlers.✅ Notable Successful Runs
All 22 runs today
* Intentional failure — duplicates found, issue filed
Recommendations
Listing background agentsis a recurring risk for expensive no-op runs. Adding a max-turns guard or a health check before entering the main task loop would prevent token waste.failureconclusion — Consider whether the GitHub Actions workflow conclusion should besuccess(issue filed = job done) vsfailure(to draw attention). The current behavior creates noise in the success-rate metric.References:
Beta Was this translation helpful? Give feedback.
All reactions