You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Window evaluated: last 24 full hours (2026-08-18T23:25:24Z to 2026-08-19T23:25:24Z, UTC)
Total runs analyzed: 344
Detection-enabled runs: 313 (91.0%)
Regular runs: 31 (9.0%)
Misconfigured workflows found: 0
Note
No misconfigured workflows detected in this window. Detection coverage is high (91% of runs) and no naming, frequency, or consistency red flags surfaced.
Comparison Chart
Regular runs had a higher success rate (93.5%) than detection-enabled runs (90.7%), but detection runs used far fewer tokens on average (36,302 vs 77,703) — driven largely by high-frequency, lightweight detection workflows like PR Sous Chef and the reviewer bots.
Misconfigured Workflows
No misconfigured workflows detected in this window.
One naming-rule candidate, Daily Agentic Workflow AIC Usage Audit, contains "audit" but runs without gh-aw-detection: true. This is excluded per its documented repository-level opt-out: it is source-managed from githubnext/agentic-ops and mirrored into this repo without a local override (see .github/workflows/agentic-token-audit.md).
Note: rule 3 ("detection-enabled but detection-related steps failed") could not be reliably evaluated — the available run data has no field distinguishing a detection-step failure from a general workflow failure, so flagging on this basis would have produced false positives. The 29 failed detection-enabled runs observed in the window appear to be ordinary task failures unrelated to the detection feature itself.
Only 2 days of history are available in cache-memory (trending/detection-metrics/history.jsonl); a trend chart requires at least 7 entries and was not generated this run. Trend will appear once sufficient history accumulates.
Recommendations
No corrective action needed this cycle — detection configuration is healthy across the fleet.
Continue accumulating daily metrics; a 30-day trend chart will become available once the history log reaches 7 entries (currently 2).
Consider adding a per-step "detection status" field to run summaries so a future pass can reliably detect rule-3 (detection-step-specific) failures rather than relying on overall run conclusion.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Summary
Note
No misconfigured workflows detected in this window. Detection coverage is high (91% of runs) and no naming, frequency, or consistency red flags surfaced.
Comparison Chart
Regular runs had a higher success rate (93.5%) than detection-enabled runs (90.7%), but detection runs used far fewer tokens on average (36,302 vs 77,703) — driven largely by high-frequency, lightweight detection workflows like PR Sous Chef and the reviewer bots.
Misconfigured Workflows
No misconfigured workflows detected in this window.
One naming-rule candidate,
Daily Agentic Workflow AIC Usage Audit, contains "audit" but runs withoutgh-aw-detection: true. This is excluded per its documented repository-level opt-out: it is source-managed fromgithubnext/agentic-opsand mirrored into this repo without a local override (see.github/workflows/agentic-token-audit.md).Note: rule 3 ("detection-enabled but detection-related steps failed") could not be reliably evaluated — the available run data has no field distinguishing a detection-step failure from a general workflow failure, so flagging on this basis would have produced false positives. The 29 failed detection-enabled runs observed in the window appear to be ordinary task failures unrelated to the detection feature itself.
View All Run Metrics
View Historical Trend
Only 2 days of history are available in cache-memory (
trending/detection-metrics/history.jsonl); a trend chart requires at least 7 entries and was not generated this run. Trend will appear once sufficient history accumulates.Recommendations
All reactions