🔍 Agentic Workflow Audit Report - 2025-12-24 #7490
Closed
Replies: 2 comments
-
|
/plan |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This discussion was automatically closed because it was created by an agentic workflow more than 3 days ago. |
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.
-
Audit Summary
📊 Trend Analysis
Workflow Health
Analysis: Success rate of 55.8% indicates significant stability concerns with 38 failed runs out of 86 total. This is a decline from the previous audit (December 22) which showed 76.92% success rate, suggesting increased workflow fragility.
Token Usage & Cost
Analysis: Daily cost of $11.17 with 28.9M tokens consumed represents a 49% cost increase compared to the previous audit ($7.50). This higher spend correlates with the increased failure rate - failed workflows still consume tokens before terminating.
Full Report
Missing Tools
Three distinct missing tools were detected across multiple workflows:
safeinputs-ghplaywright_navigateAnalysis: The
safeinputs-ghtool appears to be a legitimate need for authenticated GitHub CLI operations. The Playwright navigation tool is correctly identified as missing. The directory creation issue highlights a security policy conflict where workflows cannot create directories via Bash.Error Analysis
Critical Errors (Top 10 by frequency)
Timezone Comparison Error (91 occurrences)
Cannot compare tz-naive and tz-aware datetime-like objectsCode Pattern False Positives (21-16 occurrences)
} catch (error) {,const isError = ...)Module Resolution Errors (11 occurrences)
Cannot find module './read_buffer.cjs'MCP Connection Errors (10 occurrences)
Invalid URL,MCP error -32000: Connection closed,spawn uvx ENOENTFirewall Network Policy Violations (5 occurrences)
--network host is not allowed (bypasses firewall)JSON Parse Errors (4 occurrences each)
Unexpected token '#', "### Ran Pl"... is not valid JSONError Patterns by Workflow
Highest Error Counts:
MCP Server Failures
safeoutputsAnalysis: The safeoutputs MCP server experienced connection failures in the Smoke Claude workflow. This server provides safe output mechanisms for GitHub operations (issues, PRs, discussions). Failures indicate either server instability or network connectivity issues.
Firewall Analysis
Top Allowed Domains (by request count)
api.github.com:443- 2,936 requests (GitHub API)api.githubcopilot.com:443- 2,561 requests (Copilot API)api.enterprise.githubcopilot.com:443- 2,408 requests (Enterprise Copilot)registry.npmjs.org:443- 205 requests (npm packages)github.com:443- 116 requests (GitHub web)proxy.golang.org:443- 55 requests (Go modules)api.mcp.github.com:443- 26 requests (MCP server)cdn.playwright.dev:443- 11 requests (Playwright assets)playwright.download.prss.microsoft.com:443- 11 requests (Playwright binaries)Analysis: Firewall is functioning correctly with 0 denied requests. All traffic is to expected and legitimate domains. The high volume of GitHub and Copilot API calls (87% of all traffic) is normal for agentic workflows.
Performance Metrics
Cost Breakdown by Engine:
Affected Workflows
Workflows with Multiple Failures (≥2)
Workflows with Single Failures
Historical Context
Comparing with previous audit (2025-12-22):
Key Trends:
Recommendations
1. URGENT: Fix Daily Issues Report Generator Timezone Bug
2. Improve Error Detection Pattern Accuracy
} catch (error) {being flagged as errors3. Resolve Module Resolution Issues
Cannot find module './read_buffer.cjs'in multiple workflows4. Stabilize MCP Server Connections
uvx(uv package runner) is available in workflow environments5. Add safeinputs-gh Tool
6. Review Directory Creation Security Policy
7. Investigate Success Rate Decline
8. Optimize Token Usage and Cost
9. Monitor Issue Monster and Tidy Workflows
10. Improve Smoke Test Reliability
Next Steps
References:
Beta Was this translation helpful? Give feedback.
All reactions