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 (UTC), 2026-08-03T23:38Z to 2026-08-04T23:38Z
Total runs analyzed: 101 (67 additional runs in the window had no captured agent metadata — logs directory was empty, likely pre-execution failures — and were excluded from classification)
Detection-enabled runs: 83 (82.2%)
Regular runs: 18 (17.8%)
Misconfigured workflows found: 6
Warning
6 misconfigured workflows were detected in this window — see table below.
Comparison Chart
Detection-enabled runs had a higher success rate (95.2%) than regular runs (72.2%), and higher average token usage (36,122 vs 18,946) — consistent with detection runs skewing toward more complex/heavier workflows in this repo.
Misconfigured Workflows
Workflow
Misconfiguration Type
Run Count
Recommended Fix
Smoke Aider
detection-disabled-high-frequency
5
Add gh-aw-detection: true to workflow frontmatter — high-frequency workflow (>3 runs observed) should have detection enabled.
Smoke Goose
detection-disabled-high-frequency
4
Add gh-aw-detection: true to workflow frontmatter — high-frequency workflow (>3 runs observed) should have detection enabled.
Daily Regulatory Report Generator
name-suggests-detection-missing
1
Workflow name implies audit/monitoring intent — add gh-aw-detection: true to frontmatter.
PR Code Quality Reviewer
detection-enabled-run-failed
2
Investigate failed run(s) with detection enabled — check workflow logs for detection-step errors (example run: 30943711376).
Issue Monster
detection-enabled-run-failed
1
Investigate failed run with detection enabled — check workflow logs for detection-step errors (example run: 30946538261).
Daily BYOK Ollama Test
detection-enabled-run-failed
1
Investigate failed run with detection enabled — check workflow logs for detection-step errors (example run: 30957197799).
Note: "Daily Agentic Workflow AIC Usage Audit" was checked against the name-pattern rule but excluded per its documented repository-level opt-out (source-managed from githubnext/agentic-ops).
Note on detection-enabled-run-failed: no dedicated detection-step status is exposed in aw_info.json, so this rule uses overall run conclusion as a proxy for failed detection-enabled runs. Confirm these are genuine detection-step issues (vs. unrelated task failures) before filing fixes.
Note on detection-disabled-high-frequency: run counts here reflect only the 24h window (a lower bound on the 7-day count required by the rule); since 24h ⊆ 7d, any workflow with >3 runs in 24h necessarily has >3 runs in the trailing 7 days, so these are confidently flagged. No workflow alternated between detection-enabled/disabled within the window.
Regular-run volume spiked sharply around 2026-07-21–07-24 (up to ~197/day) then dropped off after 2026-07-29, while detection-run volume has been climbing since late July, peaking at 185 on 2026-08-03. Detection success rate has stayed consistently in the high-80s to high-90s range across the 30-day window.
Recommendations
Add gh-aw-detection: true to Smoke Aider and Smoke Goose — both run frequently (5 and 4 runs respectively in this 24h window alone) without detection enabled.
Add gh-aw-detection: true to Daily Regulatory Report Generator — its name signals an audit/reporting workflow that should be covered by detection.
Investigate the failed detection-enabled runs on PR Code Quality Reviewer, Issue Monster, and Daily BYOK Ollama Test to confirm whether failures are detection-step related or unrelated task errors.
No workflows showed inconsistent (alternating) gh-aw-detection settings within the 24h window — continue monitoring for config drift in future runs.
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
Warning
6 misconfigured workflows were detected in this window — see table below.
Comparison Chart
Detection-enabled runs had a higher success rate (95.2%) than regular runs (72.2%), and higher average token usage (36,122 vs 18,946) — consistent with detection runs skewing toward more complex/heavier workflows in this repo.
Misconfigured Workflows
gh-aw-detection: trueto workflow frontmatter — high-frequency workflow (>3 runs observed) should have detection enabled.gh-aw-detection: trueto workflow frontmatter — high-frequency workflow (>3 runs observed) should have detection enabled.gh-aw-detection: trueto frontmatter.Note: "Daily Agentic Workflow AIC Usage Audit" was checked against the name-pattern rule but excluded per its documented repository-level opt-out (source-managed from
githubnext/agentic-ops).Note on
detection-enabled-run-failed: no dedicated detection-step status is exposed inaw_info.json, so this rule uses overall run conclusion as a proxy for failed detection-enabled runs. Confirm these are genuine detection-step issues (vs. unrelated task failures) before filing fixes.Note on
detection-disabled-high-frequency: run counts here reflect only the 24h window (a lower bound on the 7-day count required by the rule); since 24h ⊆ 7d, any workflow with >3 runs in 24h necessarily has >3 runs in the trailing 7 days, so these are confidently flagged. No workflow alternated between detection-enabled/disabled within the window.View All Run Metrics
View Historical Trend
Regular-run volume spiked sharply around 2026-07-21–07-24 (up to ~197/day) then dropped off after 2026-07-29, while detection-run volume has been climbing since late July, peaking at 185 on 2026-08-03. Detection success rate has stayed consistently in the high-80s to high-90s range across the 30-day window.
Recommendations
gh-aw-detection: truetoSmoke AiderandSmoke Goose— both run frequently (5 and 4 runs respectively in this 24h window alone) without detection enabled.gh-aw-detection: truetoDaily Regulatory Report Generator— its name signals an audit/reporting workflow that should be covered by detection.PR Code Quality Reviewer,Issue Monster, andDaily BYOK Ollama Testto confirm whether failures are detection-step related or unrelated task errors.gh-aw-detectionsettings within the 24h window — continue monitoring for config drift in future runs.All reactions