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) — observed run span 2026-07-20T13:16:30Z → 2026-07-20T23:14:05Z
Total runs analyzed: 161
Detection-enabled runs: 54 (33.5%)
Regular runs: 107 (66.5%)
Misconfigured workflows found: 5
Warning
5 workflows were flagged as potentially misconfigured for the gh-aw-detection feature. See the table below for details and recommended fixes. Four are name-heuristic flags (name implies an analysis/monitoring role but detection is not enabled); one is a real detection-job failure.
Classification uses features.gh-aw-detection from each run's aw_info.json directly (true → detection-enabled; false/absent/unset → regular).
Comparison Chart
Detection-enabled runs had a lower success rate (90.7% vs 97.2%) and higher average token usage (68,602 vs 28,459) than regular runs over the window — expected, since detection adds a post-agent analysis job and tends to run on heavier analytical workflows.
Metric
Regular Runs
Detection Runs
Run count
107
54
Success rate
97.2%
90.7%
Failures
3
5
Avg tokens
28,459
68,602
Average token figures are influenced by a few outliers (e.g. Daily Cache Strategy Analyzer ≈2.18M tokens with detection on; Smoke Copilot ≈965K without).
Misconfigured Workflows
Workflow
Misconfiguration type
Runs
Recommended fix
Daily Regulatory Report Generator
Name implies detection (report) but gh-aw-detection not enabled
1
Add gh-aw-detection: true to frontmatter, or document an intentional opt-out.
Daily Security Observability Report
Name implies detection (report) but gh-aw-detection not enabled
1
Add gh-aw-detection: true — a security report especially should run threat detection.
Deep Report
Name implies detection (report) but gh-aw-detection not enabled
1
Add gh-aw-detection: true, or rename if it is not an analysis/reporting workflow.
MCP Inspector Agent
Name implies detection (inspector) but gh-aw-detection not enabled
1
Add gh-aw-detection: true; this run also failed (conclusion=failure) — investigate separately.
Daily Code Metrics and Trend Tracking Agent
Detection enabled but the detection job failed
1
Investigate run 29770233192 — threat detection did not complete; the overall run also failed.
No workflows triggered the explicit-false-on-active-workflow rule (only Smoke Copilot and Smoke Copilot Sub Agents set gh-aw-detection: false, each with a single run in-window), and no workflow alternated its detection flag within the window.
View All Run Metrics
Per-workflow breakdown (72 distinct workflows). Detection column: ✅ on = all runs detection-enabled, ⚠️ mixed, — off = none enabled.
Trend across the 2 recorded snapshots (2026-07-16 → 2026-07-20): both run volumes grew, and regular-run success rate recovered sharply (78.9% → 97.2%) while detection success rate held steady (~90%). Misconfigured count is unchanged at 5.
Recommendations
Enable detection on reporting/inspection workflows. The four name-heuristic flags (Daily Regulatory Report Generator, Daily Security Observability Report, Deep Report, MCP Inspector Agent) either produce analytical output or inspect repository state — add gh-aw-detection: true to their frontmatter, or add a documented opt-out if detection is intentionally excluded.
Fix the failing detection job on Daily Code Metrics and Trend Tracking Agent (run 29770233192): both the detection job and the overall run failed. Confirm the detection engine/credentials are configured before it silently ships unscanned output.
Watch the detection success gap. Detection runs trail regular runs by ~6.5 points on success rate; most detection failures coincide with zero-token runs (e.g. Daily BYOK Ollama Test, Daily Issues Report Generator, CI Optimization Coach), suggesting agent-execution failures upstream of detection rather than detection itself.
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-07-20T13:16:30Z→2026-07-20T23:14:05ZWarning
5 workflows were flagged as potentially misconfigured for the
gh-aw-detectionfeature. See the table below for details and recommended fixes. Four are name-heuristic flags (name implies an analysis/monitoring role but detection is not enabled); one is a real detection-job failure.Classification uses
features.gh-aw-detectionfrom each run'saw_info.jsondirectly (true→ detection-enabled;false/absent/unset → regular).Comparison Chart
Detection-enabled runs had a lower success rate (90.7% vs 97.2%) and higher average token usage (68,602 vs 28,459) than regular runs over the window — expected, since detection adds a post-agent analysis job and tends to run on heavier analytical workflows.
Average token figures are influenced by a few outliers (e.g.
Daily Cache Strategy Analyzer≈2.18M tokens with detection on;Smoke Copilot≈965K without).Misconfigured Workflows
report) butgh-aw-detectionnot enabledgh-aw-detection: trueto frontmatter, or document an intentional opt-out.report) butgh-aw-detectionnot enabledgh-aw-detection: true— a security report especially should run threat detection.report) butgh-aw-detectionnot enabledgh-aw-detection: true, or rename if it is not an analysis/reporting workflow.inspector) butgh-aw-detectionnot enabledgh-aw-detection: true; this run also failed (conclusion=failure) — investigate separately.detectionjob failedNo workflows triggered the explicit-
false-on-active-workflow rule (onlySmoke CopilotandSmoke Copilot Sub Agentssetgh-aw-detection: false, each with a single run in-window), and no workflow alternated its detection flag within the window.View All Run Metrics
Per-workflow breakdown (72 distinct workflows). Detection column: ✅ on = all runs detection-enabled,⚠️ mixed, — off = none enabled.
View Historical Trend
Trend across the 2 recorded snapshots (2026-07-16 → 2026-07-20): both run volumes grew, and regular-run success rate recovered sharply (78.9% → 97.2%) while detection success rate held steady (~90%). Misconfigured count is unchanged at 5.
Recommendations
Daily Regulatory Report Generator,Daily Security Observability Report,Deep Report,MCP Inspector Agent) either produce analytical output or inspect repository state — addgh-aw-detection: trueto their frontmatter, or add a documented opt-out if detection is intentionally excluded.Daily Code Metrics and Trend Tracking Agent(run 29770233192): both the detection job and the overall run failed. Confirm the detection engine/credentials are configured before it silently ships unscanned output.Daily BYOK Ollama Test,Daily Issues Report Generator,CI Optimization Coach), suggesting agent-execution failures upstream of detection rather than detection itself.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions