[audit-workflows] Agentic Workflow Audit — 2026-06-19 (91.5% overall, prod-main rebound; Avenger 100% hotspot) #40393
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #40516. |
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-06-19
Window: last-24h evening/afternoon cluster (16:18Z–21:29Z, ~18.8h compute) · 106 runs
Headline: Healthy day. Prod-main rebounded from 06-18's 74.2% trough to 85.2%. All 9 failures map to known recurring issues — zero new failure class. The dominant story is Avenger, which failed 4/4 runs (100%) and is escalating day-over-day.
📊 Trend Charts
Overall success rate sits at 91.5%, comfortably back above the 90% reference line after the 06-16 (71.2%) dip and the 06-18 prod-main trough. The 26-day band holds in the high-80s/low-90s; today's 9 failures are concentrated in a handful of chronically-broken workflows rather than spread across the fleet.
Token history through 06-18 shows the usual 20–70M daily range with the 7-day MA steady around ~40M. Today's token point is intentionally omitted: token/turn metrics were unavailable this window (the logs were fetched without artifact download, so every
token_usage.jsonlcame back empty). This is an audit-side data-collection gap, not a workflow regression.🔴 Failure Breakdown (all 9 known-recurring)
Expand failure detail
avenger-err-config-no-structured-logscopilot-sdk tool-perm-lockoutcopilot-sdk tool-perm-lockoutcopilot-sdk tool-perm-lockoutcodex binary/model-not-founddoc-unbloat-empty-output{items:[]}Every failure is a clean agent-job redden (0 tokens, 0 turns) — no partial work was lost on these, and no safe-output partial-failure reddening was observed this window.
ERR_CONFIG no-structured-logsfollow-up-invocation bug persists ~6 days after the fix branch (copilot/aw-avenger-failed-fix) was opened. Recommendationrec-avenger-empty-followup-invocationre-escalated to HIGH — treat a follow-up invocation that produces no structured logs after a successful first pass as no-op/success rather than hard-failing the agent job.rec-sdk-toolperm-allowlist-or-relax-guardremains unresolved after 12 days.fix-cache-strategy-binary-path) still open.✅ Health Signals
🎯 Suggested Next Actions
--artifactsnext cycle so token/cost metrics and engine_counts are populated.Data gaps this window
--artifacts; alltoken_usage.jsonlempty, summarytok=0).summary.engine_counts=none,aw_info.jsonartifacts not downloaded). Affected-workflow engines inferred from historical mapping in repo memory.References:
Beta Was this translation helpful? Give feedback.
All reactions