[audit-workflows] π Agentic Workflow Audit β 2026-07-10 (partial 5.6h Β· prod 92.9% healthy) #44841
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #45015. |
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 β 2026-07-10
Window: partial ~5.6h (15:39β21:15Z) Β· 104 complete run summaries analyzed Β· engine
logsbridge timed out at 120s so ~170 downloaded run dirs were empty (chronic tooling limit, see below).Health at a glance
token_usage_summary)Bottom line: Production fleet is healthy (92.9% ex-smoke, zero agent-quality issues). The 81.7% overall is dragged down entirely by smoke/CI test harnesses and chronic 0-turn copilot-CLI startup failures β no new agent-behavior regressions.
Engine reliability
π Trend charts
Overall success has oscillated in the 81β92% band over 30 days; today's 81.7% sits at the low end of the healthy range, consistent with prior partial evening windows (07-02/07-03 troughs, 07-04/07-05 rebounds). The dip is composition-driven β a high share of noisy smoke runs in this slice β not a production-quality regression, which held at 92.9%.
Reported daily tokens landed at 7.25M, the highest single-window figure in two weeks and above the 7-day moving average β but this reflects reporting coverage (
token_usage_summarypopulated) as much as true volume, sincerun.TokenUsageremains empty. Token accounting is only sparsely comparable day-to-day because of the ongoing reporting gap (below).π§© Failure clusters (all 0-turn / pre-agent)
Recurring β known & tracked
smoke-ci-copilot-cli-100pct-fail-on-pushcopilot-sdk-driver-failuressafe-output-partial-failure-intoleranceπ New this window
opencode-engine-onboarding-100pct-failtoken_usage.jsonlβ hard smoke-assert fails (x3): Smoke Codex (1) + Smoke OpenCode (2) fail because these engines emit an emptytoken_usage.jsonland the smoke test hard-asserts it non-empty. This is the first time the token-reporting gap causes hard test failures rather than just null metrics.token-usage-jsonl-empty-hard-assertPersistent tooling limits (audit infra)
logsbridge 120s timeout: the MCPlogsfetch for-1dtimed out at 120s again; only 104 of ~275 run dirs had complete summaries. Recurring across recent audits β audit coverage is capped to whatever downloads before the timeout.run.TokenUsageempty: the authoritative per-run token field is empty for all 104 runs; onlytoken_usage_summarycarries data. Ongoingtoken-usage-reporting-gap, now escalated to breaking smoke tests.β Recommendations
token_usage.jsonlfor codex/opencode β either emit real usage or downgrade the "non-empty" assert to a warning for engines that can't report per-turn tokens, so smoke tests reflect real health.logscoverage β the 120s bridge timeout keeps truncating the dataset. Considercount-limited orbefore_run_idpaginated fetches to guarantee complete coverage per audit.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions