Agentic Workflow Audit — 2026-03-15 #21030
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #21183. |
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. Analysis covers runs from the last 24 hours (2026-03-15).
Summary
Trend Charts
Workflow Health (Last 30 Days)

Today saw 3 failures against 8 successes (72.7% success rate for agent runs). The bulk of runs are event-triggered skips (slash commands, issue/PR reactions not matching), which is expected behavior.
Token Usage (Last 30 Days)

Today's 8.6M tokens is driven primarily by Chroma Issue Indexer (4.26M), Copilot PR Prompt Pattern Analysis (1.83M), and Contribution Check (1.45M). Cost tracking unavailable (no billing data in run metadata).
Failed Runs
Issue Monster — Configuration Failure [HIGH]
Run: §23104177948
Duration: 47s | Event: schedule
Root cause: Lockdown mode is enabled (
lockdown: true) but no custom GitHub token is configured.Impact: Workflow failed at activation — no agent ran, no output produced.
Resolution: Configure the required secret:
This was followed by
Artifact not found for name: agentin the safe_outputs job.Impact: AI Moderator could not process PR #21024. No moderation output was produced.
Resolution: The branch
copilot/update-action-pin-modemay have been deleted, force-pushed, or merged before the agent could run. This is likely transient — subsequent PR events should work normally.Missing Tools
GitHub Remote MCP Authentication Test — MCP Toolset Unavailable [MEDIUM]
Run: §23104007518
Duration: 5.6m | Tokens: 1,070,347 | Outcome: success (noop fallback)
Tools requested but unavailable:
list_issues,get_repository(GitHub MCP server)Reason:
MCP toolsets unavailable in runner - tools not loadedImpact: Minimal — the workflow completed successfully by using the
missing_toolsafe output. However, the test's purpose is to verify MCP authentication, so the missing tools indicate the remote MCP mode is not functioning as expected.Resolution: Verify that
GH_AW_GITHUB_MCP_SERVER_TOKENis set and that the remote MCP server is reachable from the runner environment.Firewall Analysis
api.githubcopilot.com:443api.openai.com:443ab.chatgpt.com:443The 2 blocked requests to
ab.chatgpt.comoriginated from the AI Moderator (codex engine). This appears to be an analytics/telemetry endpoint from the OpenAI/ChatGPT client SDK — not a data exfiltration concern. The firewall is correctly blocking it. No action required.Top Token Consumers
Recommendations
GH_AW_GITHUB_TOKENsecret. This is a blocking configuration issue preventing the workflow from running at all.lgtm/needs-worklabel names exist or if there's a size/validation constraint being hit.copilot/update-action-pin-modebranch was unavailable when the agent ran. Consider adding retry logic or graceful handling for deleted/merged branches.References:
Beta Was this translation helpful? Give feedback.
All reactions