🔍 Agentic Workflow Audit Report - November 10, 2025 #3551
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it was created by an agentic workflow more than 1 week 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.
-
🔍 Agentic Workflow Audit Report - November 10, 2025
This audit analyzed 100 workflow runs from the last 24 hours (November 6-10, 2025), identifying 13 failures, 2 missing tool requests, and 2 MCP server failures. The overall system maintains an 82% success rate with a total cost of $25.55 and 34.7M tokens consumed.
📈 Workflow Health Trends
Success/Failure Patterns
The workflow health trends show strong performance over the past 5 days, with success rates consistently above 80%. The peak successful runs occurred on November 9th, indicating high workflow activity. The lower panel shows the success rate percentage hovering around the 80-85% range, which is healthy but could be improved by addressing the recurring failures identified below.
Token Usage & Costs
Token usage shows significant daily variation, with November 9th showing the highest consumption at 11.6M tokens ($9.54). The moving average indicates a stable cost trend, averaging around $5 per day. This variation correlates with workflow activity levels and the complexity of tasks being performed.
Full Audit Details
Audit Summary
Run Status Breakdown
Engine Distribution
While engine detection based on workflow names shows most workflows as "unknown", the configured workflows use:
Missing Tools
Two tool requests were identified that could not be fulfilled:
Analysis
Both missing tool requests came from the Daily Firewall Logs Collector and Reporter workflow. This workflow appears to be encountering limitations in:
Recommendation: These issues should be resolved as the Python scientific libraries are now installed and the gh-aw MCP server is configured. Future runs of this workflow should succeed.
MCP Server Failures
Two MCP server connection failures were detected:
Analysis
Both MCP server failures occurred in the same Scout workflow run. This indicates that the Scout workflow has external dependencies on:
Recommendation:
Failed Workflow Runs
Detailed Failure Analysis
Smoke Test Failures
All three smoke test workflows failed in the same run series:
These appear to be part of a scheduled smoke test run that encountered issues.
Recurring Failure Patterns
Performance Metrics
Top 10 Most Expensive Runs
Cost Analysis
The most expensive workflow was Go Pattern Detection at $4.27, which processed over 4M tokens. Analysis and reporting workflows tend to be more expensive due to their comprehensive data collection and processing requirements.
Recommendations
High Priority
Investigate Recurring Failures
Fix Smoke Test Issues
MCP Server Reliability
Medium Priority
Cost Optimization
Tool Availability
Low Priority
Success Rate Improvement
Monitoring & Alerting
Historical Context
This is the first comprehensive audit with persistent cache storage. Future audits will be able to compare:
The audit data has been stored in
/tmp/gh-aw/cache-memory/audits/2025-11-10.jsonfor future reference.Next Steps
Data Coverage: This audit analyzed 100 workflow runs spanning 5 days (November 6-10, 2025). The trend charts reflect this available data range.
References:
Beta Was this translation helpful? Give feedback.
All reactions