Agentic Workflow Audit — 2026-03-24 #22761
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #22984. |
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.
-
Daily audit of agentic workflow runs for the 24-hour period ending 2026-03-24 21:04 UTC.
Summary
Workflow Health Trends
Today's audit shows an 81.25% success rate across 32 tracked runs. The success rate is slightly below the typical target range; two workflows experienced failures due to GitHub API errors and an indexing job misconfiguration. No MCP server failures were detected, which is a positive indicator of infrastructure health.
Token Usage & Cost Trends
Token usage is heavily skewed by two outlier runs — CI Cleaner (13.6M tokens, 145 turns) and Sergo - Serena Go Expert (4.4M tokens, 89 turns) — which together account for ~84% of total daily token spend. These two runs warrant attention as potential optimization targets.
❌ Failed Runs
Daily Documentation Updater — [§23510638836](https://github.com/github/gh-aw/actions/runs/23510638836) (scheduled, 20:26 UTC)
indexing(2.5 min)activationjob set outputs (lockdown_check_failed,model,secret_verification_result) but theindexingjob subsequently failed, causing all downstream jobs (agent,safe_outputs,update_cache_memory,conclusion) to be skippedlockdown_check_failedoutput value; check if the model or secrets for this workflow are correctly configuredSmoke Copilot — [§23509681603](https://github.com/github/gh-aw/actions/runs/23509681603) (PR #22738, branch: copilot/move-apm-packaging-into-own-job)
update_cache_memory+safe_outputsupdate_cache_memory:Unable to download artifact(s): Artifact not found for name: cache-memory— first-run or new branch with no prior cache artifactsafe_outputs: 4 outputs failed — discussion comment, issue creation, haiku-printer workflow dispatch, and PR review all failed withUnexpected end of JSON inputorServer Errorcache-memorydownload step conditional (continue-on-error: trueor existence check)Both smoke tests were cancelled around the same time (18:56 UTC), suggesting a possible runner capacity issue or deliberate cancellation.
🔧 Missing Tool Reports
add_smoked_labelThe
add_smoked_labelsafe-output action is not listed in the Smoke Codex workflow's available tools. The workflow attempted to call it but it was rejected. Fix: Addadd_smoked_labelto the Smoke Codex workflow's safe-output tools configuration, or replace it with theadd_labelstool.🔥 Top Token Consumers
Note: CI Cleaner consumed 64% of all tokens today with 145 turns — considerably more than typical for a CI cleanup workflow. This warrants investigation into whether it was operating on an unusually large set of stale runs.
Workflow Success Rates
View All 19 Workflows
Recommendations
High Priority:
lockdown_check_failed/ secret verification failure pattern suggests a configuration drift. Check model and secret settings for this workflow.continue-on-error: trueto the cache-memory download step for new branches; investigate safe_outputs retry behavior for transient GitHub API errors.Medium Priority:
3. Add
add_smoked_labelto Smoke Codex safe-output tools — the missing tool prevents proper smoke test labeling.4. Review CI Cleaner efficiency — 145 turns and 13.6M tokens is atypically high; consider adding turn/token limits or task scoping.
5. Investigate cancelled smoke runs — Smoke Claude and Smoke Codex were cancelled at 18:56 UTC; confirm this was intentional.
Low Priority:
6. Note on data completeness: Only 32 of 317 run directories contained
run_summary.jsonfiles. The remaining 285 runs haveworkflow-logsonly and may include many short-lived or pre-agent runs. This is expected behavior.References:
Beta Was this translation helpful? Give feedback.
All reactions