[audit-workflows] Daily Agentic Workflow Audit — 2026-04-14 #26295
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #26496. |
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.
-
Summary
The 24-hour audit for 2026-04-14 analyzed 50 workflow runs across the
github/gh-awrepository. All runs completed cleanly with zero errors, zero missing tools, and zero missing data — the healthiest audit window observed to date. Of the 47 completed runs, 10 succeeded with meaningful AI execution and 37 were appropriately skipped (correct event-based filtering).Overall health: ✅ Excellent
Active Workflow Performance
The following 6 workflows executed with real AI compute:
Execution Drift — Design Decision Gate 🏗️
The Design Decision Gate showed significant turn variability: 6 to 17 turns across two runs (avg 11.5). This may indicate:
Recommendation: Monitor over the next 7 days. If variance persists >3x, review prompt determinism and add turn-budget guardrails.
Network Firewall — AI Moderator
The AI Moderator workflow had 2 blocked requests out of 5 (40%) targeting
ab.chatgpt.com:443andchatgpt.com:443. These appear to be external ChatGPT endpoints accessed during moderation checks — not expected in the workflow's design.Recommendation: Review the AI Moderator prompt/tools to ensure it isn't inadvertently making outbound calls to ChatGPT. If Codex/OpenAI routing is intended, verify the domains are allowlisted in the workflow config.
Reliability — 3 High-Anomaly Events
Cross-run analysis detected 3 events with anomaly score > 0.6 in the
tool_resultstage. These represent newly observed log templates rare enough to flag. No immediate action required, but worth monitoring for recurrence.Firewall Analysis
Blocked domains:
ab.chatgpt.com:443— AI Moderator (2 requests)chatgpt.com:443— AI Moderator (2 requests)-(unnamed) — Daily Workflow Updater (10 requests, likely internal routing)MCP Tool Usage
All 50 runs stayed read-only except 1 PR push + 1 review submission + 5 comments — actuation rate matches expected patterns.
📊 Trend Charts (Last 3 Audit Days)
Workflow Health Trends
Today's run shows a sharp drop in raw token count vs. Apr 12 (2.7M vs 47M) and significantly lower costs ($1.03 vs $15.73). This reflects fewer active PR/issue triggers today rather than a problem — skipped runs are appropriately filtered. The 100% success rate continues the trend from Apr 11's 93% baseline.
Token Usage & Cost Trends
Daily costs dropped dramatically from the Apr 12 spike ($15.73 for 85 runs) to $1.03 today (50 runs). The Apr 12 spike correlates with 37 successful runs vs. today's 10 — fewer incoming PRs/issues means fewer AI-powered reviews triggered. Efficiency per run (tokens/turn) remains stable.
Recommendations
References:
Beta Was this translation helpful? Give feedback.
All reactions