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-24T23:26 → 2026-08-25T23:26
Total runs analyzed: 251 (52 additional run directories had no downloaded logs and were excluded)
Detection-enabled runs: 251 (100%)
Regular runs (gh-aw-detection: false): 0 (0%)
Misconfigured workflows found: 0
Note
No misconfigured workflows were detected in this window. Every run in the sample had gh-aw-detection enabled (either by default or explicitly true); no workflow disabled detection, and every detection job that executed completed successfully.
Comparison Chart
Metric
Regular Runs
Detection Runs
Run count
0
251
Success rate
0.0% (no data)
92.0%
Failure count
0
20
Avg tokens/run
0
50,172
Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
251 runs across the window all had detection enabled (233 explicit true, 18 defaulted). 246 of these runs had a detection job present in job_details, and all 246 completed with conclusion: success — zero detection-job failures.
The 20 overall run failures in the window were all attributable to the agent job itself (e.g. repeated failures in the "AI Moderator" workflow), not to the detection feature — these fall outside the scope of this report's detection-specific rules, but are worth a look separately since 3 of those "AI Moderator" runs also had no detection job present in job_details at all despite the feature flag being true.
View Historical Trend
Trend history was initialized this run — only 1 data point now exists in the cache-memory store (/tmp/gh-aw/cache-memory/trending/detection-metrics/history.jsonl). A 30-day trend chart will be generated automatically once at least 7 daily snapshots have accumulated.
Recommendations
No action needed on gh-aw-detection configuration — every active workflow in this window is running with detection enabled and the detection job is passing cleanly.
Worth a separate look (outside detection scope): the "AI Moderator" workflow failed its agent job in all 3 of its runs this window, and in each of those runs the detection job never appears in job_details at all (rather than running and failing). That's consistent with the agent job failing before detection could execute, but is worth confirming it isn't a workflow config issue that also happens to suppress detection.
Continue accumulating daily metrics snapshots — the trend chart needs 6 more days of history before it will render.
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
gh-aw-detection: false): 0 (0%)Note
No misconfigured workflows were detected in this window. Every run in the sample had
gh-aw-detectionenabled (either by default or explicitlytrue); no workflow disabled detection, and everydetectionjob that executed completed successfully.Comparison Chart
Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
251 runs across the window all had detection enabled (233 explicit
true, 18 defaulted). 246 of these runs had adetectionjob present injob_details, and all 246 completed withconclusion: success— zero detection-job failures.The 20 overall run failures in the window were all attributable to the
agentjob itself (e.g. repeated failures in the "AI Moderator" workflow), not to the detection feature — these fall outside the scope of this report's detection-specific rules, but are worth a look separately since 3 of those "AI Moderator" runs also had nodetectionjob present injob_detailsat all despite the feature flag beingtrue.View Historical Trend
Trend history was initialized this run — only 1 data point now exists in the cache-memory store (
/tmp/gh-aw/cache-memory/trending/detection-metrics/history.jsonl). A 30-day trend chart will be generated automatically once at least 7 daily snapshots have accumulated.Recommendations
gh-aw-detectionconfiguration — every active workflow in this window is running with detection enabled and the detection job is passing cleanly.agentjob in all 3 of its runs this window, and in each of those runs thedetectionjob never appears injob_detailsat all (rather than running and failing). That's consistent with the agent job failing before detection could execute, but is worth confirming it isn't a workflow config issue that also happens to suppress detection.All reactions