Agentic Workflow Audit — 2026-03-03 #19348
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-04T05:51:18.787Z.
|
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 all agentic workflow runs from the last 24 hours (2026-03-03 UTC).
Overview
26 workflow runs executed in the past 24 hours across schedule, pull_request, and push triggers. The overall health is moderate — most scheduled workflows succeeded, but 4 distinct failures were detected across 3 workflows, and 1 missing tool was reported. The Changeset Generator dominated token usage at ~238M tokens (~96% of total).
Summary Stats
Workflow Health Chart
The chart above shows success/failure runs per workflow. 4 workflows reported failures —
Smoke Codexhad the highest failure count (3 runs, all on PRs),AI ModeratorandIssue Monsterboth had 2 failures each (on push to non-main branches, likely expected infrastructure failures). The core scheduled workflows (Contribution Check,Daily Doc Updater,Chroma Issue Indexer) all completed successfully.Token & Cost Distribution
Changeset Generatoraccounts for 96.0% of all token usage (~238M of 248M total across token-tracked runs), driven by 2 large PR changesets. The next highest areSmoke Claude(~3.8M) andChroma Issue Indexer(~3.4M). Cost efficiency is reasonable given the volume —Changeset Generatorat 238M tokens for 2 runs is expected for a full codebase analysis workflow.Critical Issues
1. Copilot Policy Access Denied —
Copilot PR Prompt Pattern AnalysisError: Access denied by policy settings— the Copilot CLI reported organization policy restrictions preventing access.gh-awrepository — the scheduled prompt analysis workflow may need re-authorization or policy exception. Check https://github.com/settings/copilot.2. Smoke Codex Failures on PRs (2 PRs, 3 runs)
copilot/fix-allowed-repos-validation,copilot/update-generated-footer-history-linkAgent Container Smoke Test,Changeset Generator,Smoke Copilot) all succeeded on the same PRs.Missing Tools
GitHub Remote MCP Authentication Test — MCP Toolsets Not Loaded
success(workflow still completed successfully)MCP toolsets unavailable in runner - tools not loadedsuccessdespite the missing tool report, indicating the missing tool was correctly detected and reported rather than causing failure.Firewall Analysis
Network Firewall Summary — 45.7% Block Rate
The 149 blocked requests to unknown/unclassified destinations are likely internal container networking overhead (normal). The 4 blocked
github.com:443and 2 blockedcodeload.github.com:443requests came fromChangeset Generator— this workflow attempts direct GitHub API access which is intentionally blocked by the firewall (the MCP server is expected to handle GitHub API calls instead).Assessment: Firewall is functioning correctly. No suspicious or unexpected domain access attempts detected.
Successful Workflows
View Successful Runs
Recommendations
Copilot PR Prompt Pattern Analysis— this is a scheduled workflow that failed due to access policy, not a transient error.Smoke Codexfailures — the pattern across 2 different PRs on the same day may indicate a regression in the Codex smoke test task definition or environment.Issue Monsteractivation failures occurred on non-main branches (push events todu2,copilot/*branches) — these appear to be expected failures due to branch-specific configuration, not regressions.References:
Beta Was this translation helpful? Give feedback.
All reactions