Repository navigation
[detection-analysis] Detection Analysis Report — 2026-11-08 #76005
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #76336. |
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
403onactions/workflows) partway through the continuation fetch, and storage usage reached ~983 MB of the 1 GB budget. Actual data analyzed spans 2026-11-08T03:18Z → 2026-11-08T23:12Z (~20 of the 24 hours) — the earliest ~4 hours of the window (2026-11-07T23:14Z–2026-11-08T03:18Z) were not collected. Figures below reflect this partial-but-majority sample, not the full 24h window.aw_info.json— i.e. the agent job never executed, consistent with activation/admission-skip or non-agentic jobs)gh-aw-detection: false): 1 (0.2%)Warning
6 workflows show a failing
detectionjob, but all 6 failures cluster in a ~3-hour window (08:44–11:55 UTC on 2026-11-08) and share the identical failing step — "Install AWF binary" — which also failed in theagentjob for half of them. This points to a shared, transient infrastructure issue (e.g. a binary release/CDN hiccup) rather than 6 independent per-workflow detection misconfigurations.Comparison Chart
Note: the "Regular Runs" group has only 1 run in this window (
gh-aw-detection: falseis rare — only one workflow, Daily GitHub Docs SEO Optimizer, opted out, and it ran once), so the regular-vs-detection comparison is based on an extremely small regular-run sample this period.Misconfigured Workflows
Install AWF binary)Install AWF binary) — agent job also failed on same stepInstall AWF binary)Install AWF binary)Install AWF binary) — agent job also failed on same stepInstall AWF binary) — agent job also failed on same stepRecommended next step: Rather than per-workflow fixes, investigate whether the AWF binary download source (release artifact/CDN) had an outage between 08:44–11:55 UTC on 2026-11-08. All 6 occurrences are single, isolated runs for their respective workflows (no workflow shows a sustained or repeated pattern), so no
gh-aw-detectionfrontmatter change is indicated for any of them. No workflow in this window matched the "detection explicitly disabled on a frequently-run workflow" rule (only 1 regular run total, for Daily GitHub Docs SEO Optimizer, well under the >3-runs threshold) or the "flag alternates within window" rule.View All Run Metrics
Full per-workflow breakdown (129 workflows, 602 classified runs):
View Historical Trend
Trend covers the last 30 days (26 of 30 days have data; gaps on 2026-10-10, 10-11, 10-14, and 11-01). Today's entry (2026-11-08) carries the partial-coverage caveat noted above.
Recommendations
gh-aw-detectionmisconfiguration. Check the AWF release/CDN source for an outage in that window.agentanddetectionjobs areskipped— the failure is in its customCollect failure evidencejob, out of scope for this detection-focused report but worth a separate look.References:
agentanddetectionjobs failed on "Install AWF binary"detectionjob failed on "Install AWF binary" whileagentsucceededagent/detectionboth skipped; failure is in the customCollect failure evidencejob (out of scope, noted for follow-up)All reactions