Repository navigation
[detection-analysis] Detection Analysis Report — 2026-11-07 #75767
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #76005. |
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-11-06T23:29:52Z→2026-11-07T23:29:52Zgh-aw-detectionistrueor absent (the default)gh-aw-detection: falseexplicitly setNote
No misconfigured workflows were detected in this window. All 55 "regular" (detection-disabled) runs belong to one-off
Smoke *test-harness workflows with a single run each in the window — none crossed the >3-runs-in-7-days threshold used to flag an actively-used workflow with detection turned off. Nodetectionjob showed a failing conclusion, and no workflow alternated between enabled/disabled settings within the window.Comparison Chart
Detection-enabled runs ran at a higher success rate (89.9% vs 80.0%) but consumed roughly 3.3x the average tokens (441,710 vs 135,657) of regular runs — expected, since detection-enabled runs include heavier analytical/data-generation workflows (e.g.
Daily Go Test Parallelizer,Ponytail Reviewer) while mostgh-aw-detection: falseruns are lightweight one-shot smoke tests.Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics (top 30 of 207 workflows by run count)
Smoke *workflows)The remaining ~180 workflows are single-run
Smoke *CI/test-harness workflows (29 withgh-aw-detection: false, the rest with detection enabled) and a long tail of low-frequency scheduled/PR workflows.View Historical Trend
39 daily data points on record (2026-10-09 → 2026-11-07, 26 of 30 recent days have data; gaps shown as breaks, not interpolated).
Recommendations
gh-aw-detectionconfiguration this window — adoption (90.7% detection-enabled) and detection-job health are both healthy.collect_failure_evidencestep failures, see clusterfailure-d317ca089a5bb99c) and Daily Documentation Diagram / Daily Cli Tools Tester (success rates 66.7%/50.0% with very high token usage). These are general reliability issues, not detection misconfigurations.Smoke *workflows withgh-aw-detection: false— they're intentionally detection-disabled smoke tests today, but if any of them become part of regular scheduled/active usage (>3 runs/week), re-evaluate whether detection should be re-enabled.Coverage Note
Log collection hit the agentic-workflows MCP server's per-request API count limit (3000) twice while paging backward through the 24h window, requiring one follow-up continuation fetch. After that fetch, storage reached ~977 MB of the 1 GB budget with 947 run directories downloaded (592 agent-executed + 355 activation-only/non-execution runs). A small ~29-minute gap remains at the oldest edge of the window (
2026-11-06T23:13:46Z–23:42:55Z) that was not fully re-fetched due to the storage budget. This represents ~98% coverage of the 24-hour window; findings above reflect this near-complete subset, not a guaranteed 100% census.References:
collect_failure_evidencefailureAll reactions