[detection-analysis] Detection Analysis Report — 2026-09-09 #59818
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #60068. |
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-09-08T23:33:55Z→2026-09-09T23:33:55Zgh-aw-detection: false): 1 (0.3%)Note
No misconfigured workflows were detected in this window. The single opted-out workflow (
Daily GitHub Docs SEO Optimizer) only had 1 run in the window, below the >3-run threshold used to flag an intentional opt-out as noteworthy, and nodetectionjob failures or inconsistent per-run settings were observed elsewhere.Comparison Chart
Detection-enabled runs vastly outnumber regular (opted-out) runs (313 vs 1), consistent with
gh-aw-detectionbeing enabled by default across the fleet. Detection-enabled runs show a lower success rate (80.2% vs 100.0%) and higher average token usage (163,365 vs 134,195) than the single regular run — though with n=1 for the regular group, this comparison isn't statistically meaningful this window.Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
Top workflows by run count in the window (114 workflows total ran at least once; showing top 20 by volume):
Aggregate figures:
View Historical Trend
Across the last 8 recorded snapshots (2026-08-25 → 2026-09-09), detection-enabled run volume has held in the ~250–400/day range with success rates fluctuating 67–94%. Regular (opted-out) run volume is consistently near-zero (0–39), reflecting that almost no workflows in this repo explicitly disable detection. The one prior spike (39 regular runs on 2026-09-03, 3 misconfigured that day) has since resolved back to 0–1.
Recommendations
Issue Monster(37.9% success, 29 runs) andAI Moderator(12.5% success, 8 runs) have unusually low success rates this window; worth a separate investigation into whether their failures are detection-related or unrelated agent/task errors (job-level data suggests these areagent-side conclusions, notdetection-job failures, so out of scope for this report's misconfiguration rules).Daily GitHub Docs SEO Optimizer'sgh-aw-detection: falsesetting — if its run frequency grows past 3 runs/window, it will trigger the opt-out flag in future reports; confirm this opt-out is intentional.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