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), covering runs from 2026-09-02T11:19Z to 2026-09-02T22:56Z
Total runs analyzed: 237
Detection-enabled runs: 237 (100%)
Regular runs (gh-aw-detection: false): 0 (0%)
Misconfigured workflows found: 0
Note
No workflows in this window explicitly disable the gh-aw-detection feature, and no detection job failures were found. All 237 runs across 82 workflows ran with threat detection enabled (the default).
Comparison Chart
Because no runs opted out of detection this window, the "Regular Runs" bars are 0 across the board — this is a true reading of the data, not a gap in collection. Detection-enabled runs finished at an 87.76% success rate with an average of 206,016 tokens per run.
Misconfigured Workflows
No misconfigured workflows detected in this window.
Detection-run success rate has held in the 78–92% band over the last ~4 recorded snapshots, with today's 87.76% at the higher end. Regular-run counts have been at or near zero since 2026-09-01, consistent with detection being enabled fleet-wide.
Recommendations
No detection-configuration fixes are needed this window — keep monitoring for any workflow that newly adds gh-aw-detection: false, since the runbook's rule-1 threshold (>3 runs/7 days while disabled) would flag it going forward.
Outside the scope of detection misconfiguration, two workflows show sustained failure patterns worth a look by their owners:
Avenger — 0% success rate across all 8 runs this window (agent job fails every time, 0 tokens consumed), e.g. run §33624861220. Detection itself succeeds, so this looks like an unrelated agent-side issue (config, credentials, or a broken trigger), not a detection misconfiguration.
Code Scanning Fixer — 0% success rate across 2 runs, e.g. run §33632778572.
Continue the daily trend snapshot so a real "flip" to gh-aw-detection: false on a high-traffic workflow (rule 1) or an alternating configuration (rule 3) is caught early.
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 workflows in this window explicitly disable the
gh-aw-detectionfeature, and nodetectionjob failures were found. All 237 runs across 82 workflows ran with threat detection enabled (the default).Comparison Chart
Because no runs opted out of detection this window, the "Regular Runs" bars are 0 across the board — this is a true reading of the data, not a gap in collection. Detection-enabled runs finished at an 87.76% success rate with an average of 206,016 tokens per run.
Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
View Historical Trend
Detection-run success rate has held in the 78–92% band over the last ~4 recorded snapshots, with today's 87.76% at the higher end. Regular-run counts have been at or near zero since 2026-09-01, consistent with detection being enabled fleet-wide.
Recommendations
gh-aw-detection: false, since the runbook's rule-1 threshold (>3 runs/7 days while disabled) would flag it going forward.gh-aw-detection: falseon a high-traffic workflow (rule 1) or an alternating configuration (rule 3) is caught early.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions