[detection-analysis] Detection Analysis Report — 2026-08-28 #56468
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #56740. |
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
gh-aw-detection: false): 2 (0.7%)Note
No misconfigured workflows were detected in this window. The
gh-aw-detectionfeature is behaving consistently across the fleet: all runs with detection enabled that reached thedetectionjob completed it successfully (280 success, 1 skipped, 7 runs where theagentjob itself never started and so the job wasn't scheduled).Comparison Chart
Regular runs show a higher success rate (100%) than detection-enabled runs (75.9%), but this is not attributable to the detection feature itself — see analysis below.
Misconfigured Workflows
No misconfigured workflows detected in this window.
Two workflows explicitly disabled detection (
gh-aw-detection: false) but each had only a single run in the 24h window, well under the >3-runs threshold used to flag an active misconfiguration:Neither showed alternating detection flags, and no
detectionjob in the window had a failing conclusion (280 success / 1 skipped / 7 not scheduled because theagentjob didn't run) — so no rule-2 or rule-3 flags either.Note: the ">3 runs in the last 7 days" threshold in rule 1 was evaluated against the 24h window only, since only 24h of logs are available to this analysis. Both flagged-candidate workflows should be rechecked against a full 7-day window if detection needs to be audited more strictly.
View All Run Metrics
Top workflows by run count in the window (all runs shown had detection enabled unless noted):
Remaining 116 workflows each had exactly 1 run in the window (all detection-enabled), omitted here for brevity — full detail is in the run logs.
Aggregate metrics:
The lower detection-group success rate reflects that it contains nearly the entire fleet (286 of 288 runs), including many single-run experimental/daily workflows with unrelated agent-level failures — it is not evidence that the detection feature causes failures. No
detectionjob itself failed in this window.View Historical Trend
Trending history now has 2 daily entries (started 2026-08-25). At least 7 entries are needed before a 30-day trend chart can be generated — check back once more daily runs accumulate.
Recommendations
gh-aw-detection: false. If their run frequency increases past 3 runs/week, revisit whether the opt-out is still justified.References:
All reactions