You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Daily audit of agentic workflow runs for 2026-03-12. This report covers workflow health, recent failures, trends, and key findings from the last 24 hours.
Note: The gh aw logs MCP tool requires GitHub CLI authentication (not available in this environment). Analysis was performed using the audit tool on specific runs, GitHub MCP issue/commit search, and the Workflow Health Dashboard from issue #20479. The fix for the cryptic exit status 1 error was merged today in commit 610ca86.
Summary
Metric
Value
Overall Health Score
72/100 (stable, flat from Mar 11)
Total Workflows
166
Healthy
158 (95%)
Critical/Warning
8 (5%)
Active Failures Audited
2
P1 Issues (Persistent)
1 (day 16+)
Commits Today
8+
Workflow Health Trend
Health score has been stable at 72/100 since March 11, recovering from a dip to 70 on March 10. The primary drag remains the persistent P1 lockdown token issue affecting 4 workflows. Two major workflows (Smoke Codex, Duplicate Code Detector) recovered on March 11 and remain healthy today.
Estimated Token & Cost Trends
Token usage estimated based on known workflow activity (~93K tokens for a single 16-min agent run, ~$0.50/hour across all engines). March 12 shows a partial day (audit ran at ~05:42 UTC). Note: actual token metrics are not exposed through the current API access level.
Critical Issues 🚨
P1 (Persistent, Day 16+): GH_AW_GITHUB_TOKEN Missing
All use lockdown: true which requires a custom GitHub token not currently provisioned. See tracking issue #20315.
Requires admin intervention — no programmatic fix path available.
Failures Audited Today
Go Logger Enhancement — Run (a href="https://github.com/github/gh-aw/actions/runs/22972502171")#177(/a) (FAILURE)
Duration: 17.9 minutes (agent job: 16.3 min)
Engine: Claude
Tool calls: 46 Read + 114 bash commands
Safe outputs: 0
Root cause: Agent entered extensive read-only code exploration mode (46 file reads, 114 bash commands exploring the codebase for logger patterns) and never produced any output. After ~16 minutes, the agent was killed and orphan processes were cleaned up.
Firewall: All clean (113 requests to api.anthropic.com, 1 to raw.githubusercontent.com)
Pattern: Same "agent timeout without output" pattern seen in jsweep. The agent needs better guidance to call noop or produce partial output when it cannot complete the full task.
Smoke Gemini — Run (a href="https://github.com/github/gh-aw/actions/runs/22981480373")#322(/a) (NO SAFE OUTPUT)
Duration: 4.2 minutes
Engine: Gemini (auto-gemini-3)
Safe outputs: 0 (safe-output-items.jsonl is empty)
Detection: Passed (threat detection ran, no issues found)
Root cause: Smoke Gemini runs on a schedule trigger without issue/PR context. The Gemini engine completes successfully but produces no meaningful output, resulting in no safe-output calls.
Pattern: This is a recurring issue for schedule-triggered smoke tests that need context to act on. The workflow health dashboard noted "100% failure rate on schedule (run [Custom Engine Test] Test Issue Created by Custom Engine #322 Mar 11) — likely add_comment context error on schedule trigger."
GH_AW_GITHUB_TOKEN missing for lockdown: true workflows
Admin must provision secret — tracking #20315 (day 16)
P2 — HIGH
Agent timeout without safe output (go-logger, jsweep)
Add timeout guidance to workflow prompts: "if analysis complete but no changes needed, call noop with summary"
P2 — HIGH
Smoke Gemini no-output on schedule
Add issue context guard for schedule trigger; consider removing schedule trigger if tool needs context
P3 — MEDIUM
Contribution Check: no PRs evaluated
Verify filter step is producing pr-filter-results.json correctly
INFO
compile --actionlint false negative
Community issue #20629 — distinguish lint findings from tooling integration failures
Audit Tool Limitation
The gh aw logs MCP tool currently requires GitHub CLI authentication, which is not available in this workflow's environment. This limits the ability to aggregate metrics across all workflow runs. The fix merged today in 610ca86 improves error visibility. Future audit runs should benefit from a token being provisioned for the audit workflow.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Daily audit of agentic workflow runs for 2026-03-12. This report covers workflow health, recent failures, trends, and key findings from the last 24 hours.
Summary
Workflow Health Trend
Health score has been stable at 72/100 since March 11, recovering from a dip to 70 on March 10. The primary drag remains the persistent P1 lockdown token issue affecting 4 workflows. Two major workflows (Smoke Codex, Duplicate Code Detector) recovered on March 11 and remain healthy today.
Estimated Token & Cost Trends
Token usage estimated based on known workflow activity (~93K tokens for a single 16-min agent run, ~$0.50/hour across all engines). March 12 shows a partial day (audit ran at ~05:42 UTC). Note: actual token metrics are not exposed through the current API access level.
Critical Issues 🚨
P1 (Persistent, Day 16+):
GH_AW_GITHUB_TOKENMissing4 workflows blocked: Issue Monster, PR Triage Agent, Daily Issues Report, Org Health Report
All use
lockdown: truewhich requires a custom GitHub token not currently provisioned. See tracking issue #20315.Requires admin intervention — no programmatic fix path available.
Failures Audited Today
Go Logger Enhancement — Run (a href="https://github.com/github/gh-aw/actions/runs/22972502171")#177(/a) (FAILURE)
api.anthropic.com, 1 toraw.githubusercontent.com)jsweep. The agent needs better guidance to callnoopor produce partial output when it cannot complete the full task.Smoke Gemini — Run (a href="https://github.com/github/gh-aw/actions/runs/22981480373")#322(/a) (NO SAFE OUTPUT)
add_commentcontext error on schedule trigger."New Issues Today (Created by Workflows)
compile --actionlintreports zero errors but exits nonzeroNotable Fixes Merged Today (8 commits)
Key improvements in the last 24 hours
fix: logs MCP tool surfaces actionable error instead of cryptic "exit status 1"— directly relevant to this audit!draftas policy increate-pull-request, not agent-overridable fallbackweb-searchtool is configuredcontents/pull-requests: writetosync_actionsreusable workflow callhandle_noop_message.cjsRecurring Patterns & Recommendations
GH_AW_GITHUB_TOKENmissing forlockdown: trueworkflowsnoopwith summary"pr-filter-results.jsoncorrectlycompile --actionlintfalse negativeAudit Tool Limitation
The
gh aw logsMCP tool currently requires GitHub CLI authentication, which is not available in this workflow's environment. This limits the ability to aggregate metrics across all workflow runs. The fix merged today in 610ca86 improves error visibility. Future audit runs should benefit from a token being provisioned for the audit workflow.References:
Beta Was this translation helpful? Give feedback.
All reactions