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-10-18T23:21:57Z → 2026-10-19T23:21:57Z
Total runs analyzed: 598 (full window coverage confirmed — initial download hit a 3,000-item/1 GB continuation limit, so it was paged backward through 5 fetches until the continuation cursor reached the window start with no partial flag remaining)
Detection-enabled runs: 519 (86.8%)
Regular runs (gh-aw-detection: false): 79 (13.2%)
Misconfigured workflows found: 3
Warning
3 workflows explicitly disable gh-aw-detection while running more than 3 times in the window (Rule 1). All three are smoke-test workflows (Smoke Copilot, Smoke Copilot SDK Routed, Smoke Pi Routed) with the override hardcoded in their .md frontmatter — likely intentional for engine-routing smoke tests, but flagged per the configured threshold since no exception/comment documents the intent. No detection-job-level failures (Rule 2) or flapping configurations (Rule 3) were found.
Comparison Chart
Metric
Regular Runs
Detection Runs
Run count
79
519
Success rate
73.4%
81.9%
Failure count
21
94
Avg. tokens
135,940
148,432
Misconfigured Workflows
Workflow
Misconfiguration Type
Run Count
Recommended Fix
Smoke Copilot
gh-aw-detection: false on a high-frequency workflow (Rule 1)
4
Confirm the disable is intentional for engine-routing smoke testing; if so, add a frontmatter comment documenting why, otherwise remove the override.
Smoke Copilot SDK Routed
gh-aw-detection: false on a high-frequency workflow (Rule 1)
4
Same as above.
Smoke Pi Routed
gh-aw-detection: false on a high-frequency workflow (Rule 1)
236 distinct workflows ran in the window; the remainder were mostly single/low-frequency smoke-test workflows with 1–3 runs each.
View Historical Trend
9 daily snapshots over the last 30 days (cache-memory trending history). Regular-run volume has grown from single digits to 21–79/day over the past week, while detection success rate has fluctuated 76–93%; today's 81.9% sits mid-range.
Recommendations
Document or remove the gh-aw-detection: false override in smoke-copilot.md, smoke-copilot-sdk-routed.md, and smoke-pi-routed.md — add a short frontmatter comment explaining the smoke-test rationale so future audits don't re-flag it, or re-enable detection if there's no longer a reason to skip it.
No detection-job failures were observed this window — the detection feature itself appears healthy across the 519 detection-enabled runs.
Regular-run success rate (73.4%) continues to trail detection-run success rate (81.9%); worth a follow-up to confirm this gap is driven by the smoke-test workloads above rather than a broader reliability issue in non-detection workflows.
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
2026-10-18T23:21:57Z→2026-10-19T23:21:57Zpartialflag remaining)gh-aw-detection: false): 79 (13.2%)Warning
3 workflows explicitly disable
gh-aw-detectionwhile running more than 3 times in the window (Rule 1). All three are smoke-test workflows (Smoke Copilot,Smoke Copilot SDK Routed,Smoke Pi Routed) with the override hardcoded in their.mdfrontmatter — likely intentional for engine-routing smoke tests, but flagged per the configured threshold since no exception/comment documents the intent. No detection-job-level failures (Rule 2) or flapping configurations (Rule 3) were found.Comparison Chart
Misconfigured Workflows
gh-aw-detection: falseon a high-frequency workflow (Rule 1)gh-aw-detection: falseon a high-frequency workflow (Rule 1)gh-aw-detection: falseon a high-frequency workflow (Rule 1)Example run: §39176941475 (Smoke Copilot)
View All Run Metrics
Top 20 workflows by run count in the window:
236 distinct workflows ran in the window; the remainder were mostly single/low-frequency smoke-test workflows with 1–3 runs each.
View Historical Trend
9 daily snapshots over the last 30 days (cache-memory trending history). Regular-run volume has grown from single digits to 21–79/day over the past week, while detection success rate has fluctuated 76–93%; today's 81.9% sits mid-range.
Recommendations
gh-aw-detection: falseoverride insmoke-copilot.md,smoke-copilot-sdk-routed.md, andsmoke-pi-routed.md— add a short frontmatter comment explaining the smoke-test rationale so future audits don't re-flag it, or re-enable detection if there's no longer a reason to skip it.References:
All reactions