[detection-analysis] Detection Analysis Report — 2026-08-17 #53522
Closed
Replies: 2 comments
|
Copilot pass by here. Ugh, discussion good. Me leave paw print. 🦴 Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
0 replies
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #53851. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
2026-08-16T23:20:00Z→2026-08-17T23:20:00ZWarning
3 workflows were flagged as misconfigured relative to the
gh-aw-detectionfeature policy. See details below.Comparison Chart
Detection-enabled runs succeeded 96.8% of the time (92/95) vs. 60.0% (3/5) for regular runs in this window — though the regular-run sample is small (5 runs) and dominated by a couple of already-flagged workflows, so the gap shouldn't be read as detection causing higher reliability. Average token usage was higher for detection runs (~74.4k vs ~36.3k), consistent with the extra detection pass adding overhead.
Misconfigured Workflows
gh-aw-detectionabsent, >3 runs/7d (8 runs)gh-aw-detection: trueto the workflow frontmatter — this is a daily analysis/reporting workflow that should carry detectiongh-aw-detection: truegh-aw-detection: true; confirm whether low run volume (2/7d) reflects an intentional schedule changegh-aw-detectionabsent, >3 runs/7d (8 runs)gh-aw-detection: trueNo alternating-configuration issues (Rule 4) and no detection-step failures on detection-enabled runs (Rule 3) were found in this window.
View All Run Metrics
41 unique workflows, 100 runs total. Top workflows by run count:
Detection status for a subset of runs (~20) was cross-referenced against current workflow lockfiles by name, since some historical workflows have since been renamed; one initial fuzzy-match mismatch (Agentic Workflow Audit Agent →
audit-workflows.lock.yml, detection true) was caught and corrected during verification.View Historical Trend
This is the first run recording detection metrics to the trending cache (
/tmp/gh-aw/cache-memory/trending/detection/history.jsonl). No trend chart yet — one historical data point exists. A trend chart will be generated starting from the next run once 2+ data points are available.Recommendations
gh-aw-detection. Enabling detection would add a validation layer while investigating the failure cause separately.Daily Agentic Workflow AIC Usage Audit) so it isn't re-flagged.gh-aw-detection: truefor alldaily-*analysis/report/audit workflows by default, since 94 of 95 detection-enabled runs in this window succeeded — the pattern is well-proven at this point.All reactions