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-09-04T23:30:08Z → 2026-09-05T23:30:08Z, UTC)
Total runs analyzed: 269
Detection-enabled runs: 269 (100%)
Regular runs (gh-aw-detection: false): 0 (0%)
Misconfigured workflows found: 0
Note
All 269 runs in this window had the gh-aw-detection feature enabled (241 explicitly true, 28 via default). No run explicitly opted out with gh-aw-detection: false, so there is no regular-run baseline to compare against this cycle, and no misconfiguration patterns (rules 1–3) were triggered.
Comparison Chart
Regular runs show 0 across every metric because no workflow in this window disabled detection.
Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
Per-workflow breakdown across 99 distinct workflows (269 total runs):
Historical trending data now has 6 daily snapshots in trending/detection-metrics/history.jsonl (needs ≥7 to render a trend chart). No trend chart generated this run — check back after tomorrow's cycle.
Recent snapshots (regular vs. detection runs, detection success rate):
Timestamp (UTC)
Regular Runs
Detection Runs
Detection Success Rate
Misconfigured
2026-08-25T23:26:00Z
0
251
92.0%
0
2026-08-28T02:00:00Z
2
286
75.9%
0
2026-08-28T23:00:00Z
3
348
91.7%
0
2026-08-29T23:29:00Z
11
319
94.0%
0
2026-08-30T23:41:03Z
3
403
87.6%
3
2026-09-05T23:30:08Z (today)
0
269
84.0%
0
Note: there is a ~5-day gap between the last snapshot (2026-08-30) and today's — the trending cache wasn't updated on the days in between.
Recommendations
No action required for detection misconfiguration — no workflow explicitly disabled gh-aw-detection. Of 269 runs, 265 detection jobs succeeded, 2 were skipped, and 2 are absent from job_details; none show a failing detection-job conclusion, so rule 2 is not triggered anywhere.
Regular-run baseline is empty. If the intent of tracking "Regular Runs" is to catch workflows that intentionally opt out of detection, note that zero workflows currently do so in this repo — worth confirming that's expected rather than an oversight in workflow configuration.
A handful of workflows (e.g. Avenger, Auto-Triage Issues) show 0% success across all their runs in this window — in each case the agent job itself completed with conclusion: failure while the detection job succeeded, so these are agent-level failures unrelated to gh-aw-detection and fall outside this report's misconfiguration rules. Still worth investigating separately (8 failing runs combined).
Detection-runs' overall success rate this window (84.0%) is roughly in line with the 6-day trend (67–92%); no anomalous drop tied to the detection feature itself.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.com
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
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
All 269 runs in this window had the
gh-aw-detectionfeature enabled (241 explicitlytrue, 28 via default). No run explicitly opted out withgh-aw-detection: false, so there is no regular-run baseline to compare against this cycle, and no misconfiguration patterns (rules 1–3) were triggered.Comparison Chart
Regular runs show 0 across every metric because no workflow in this window disabled detection.
Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
Per-workflow breakdown across 99 distinct workflows (269 total runs):
View Historical Trend
Historical trending data now has 6 daily snapshots in
trending/detection-metrics/history.jsonl(needs ≥7 to render a trend chart). No trend chart generated this run — check back after tomorrow's cycle.Recent snapshots (regular vs. detection runs, detection success rate):
Note: there is a ~5-day gap between the last snapshot (2026-08-30) and today's — the trending cache wasn't updated on the days in between.
Recommendations
gh-aw-detection. Of 269 runs, 265 detection jobs succeeded, 2 were skipped, and 2 are absent fromjob_details; none show a failing detection-job conclusion, so rule 2 is not triggered anywhere.Avenger,Auto-Triage Issues) show 0% success across all their runs in this window — in each case theagentjob itself completed withconclusion: failurewhile thedetectionjob succeeded, so these are agent-level failures unrelated togh-aw-detectionand fall outside this report's misconfiguration rules. Still worth investigating separately (8 failing runs combined).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