Problem
The Agentic Commands and Q workflows fire multiple identical instances at the same timestamp on the same branch. On 2026-06-08, four exact-duplicate pairs were triggered within a 1-second window on copilot/formal-spec-awf-config-sources-spec, resulting in wasted compute and potential race conditions between parallel agent sessions.
Evidence
- Analysis window: 2026-05-25 to 2026-06-08
- Sessions analyzed: 50
- Key metrics and examples:
Agentic Commands fired twice at 2026-06-08T17:41:33Z on copilot/formal-spec-awf-config-sources-spec (run IDs: 27155900106, 27155900035)
Agentic Commands fired twice again at 2026-06-08T17:41:34Z on the same branch (run IDs: 27155901522, 27155901398)
Q fired twice at 2026-06-08T17:41:33Z (run IDs: 27155900025, 27155900013)
Q fired twice again at 2026-06-08T17:41:34Z (run IDs: 27155901716, 27155901417)
- 38 out of 50 total workflow runs were part of simultaneous same-second fan-out events
formal-spec-awf-config-sources-spec branch accumulated 21 total workflow runs in a single session
View all simultaneous fan-out events
| Timestamp |
Branch |
Workflows triggered |
| 2026-06-08T17:41:33Z |
formal-spec-awf-config-sources-spec |
Agentic Commands ×2, Q ×2, Addressing comment ×1 |
| 2026-06-08T17:41:34Z |
formal-spec-awf-config-sources-spec |
Agentic Commands ×2, Q ×2 |
| 2026-06-08T18:04:52Z |
bump-mcp-gateway-to-v0325 |
Q, AI Moderator, Smoke CI, Content Moderation, Agentic Commands |
| 2026-06-08T18:06:10Z |
fix-cli-docker-build |
Content Moderation, Q, AI Moderator, Agentic Commands, Smoke CI |
| 2026-06-08T18:30:52Z |
fix-cli-docker-build |
CWI, CGO, Smoke CI, Doc Build - Deploy |
Proposed Change
Add concurrency groups to the Agentic Commands and Q workflow YAML files to prevent duplicate simultaneous instances per branch:
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: false # or true depending on desired behavior
Also audit what event combination is causing the same workflow to trigger twice in the same second (e.g., both push and pull_request events firing on the same commit).
Expected Impact
- Eliminate redundant duplicate agent sessions that do identical work in parallel
- Reduce total workflow run count by an estimated 15–30% per active branch
- Prevent race conditions between parallel instances writing to the same branch
Notes
- Distinct root cause category: event-trigger deduplication / concurrency configuration
- Data quality: only 1 day of session data available (50 runs); pattern may be more pervasive over the full 14-day window
- No
events.jsonl files were found in session logs; analysis is based on sessions-list.json metadata only
Generated by ⚡ Copilot Opt · ⌖ 44.3 AIC · ⊞ 19.7K · ◷
Problem
The
Agentic CommandsandQworkflows fire multiple identical instances at the same timestamp on the same branch. On 2026-06-08, four exact-duplicate pairs were triggered within a 1-second window oncopilot/formal-spec-awf-config-sources-spec, resulting in wasted compute and potential race conditions between parallel agent sessions.Evidence
Agentic Commandsfired twice at2026-06-08T17:41:33Zoncopilot/formal-spec-awf-config-sources-spec(run IDs: 27155900106, 27155900035)Agentic Commandsfired twice again at2026-06-08T17:41:34Zon the same branch (run IDs: 27155901522, 27155901398)Qfired twice at2026-06-08T17:41:33Z(run IDs: 27155900025, 27155900013)Qfired twice again at2026-06-08T17:41:34Z(run IDs: 27155901716, 27155901417)formal-spec-awf-config-sources-specbranch accumulated 21 total workflow runs in a single sessionView all simultaneous fan-out events
Proposed Change
Add
concurrencygroups to theAgentic CommandsandQworkflow YAML files to prevent duplicate simultaneous instances per branch:Also audit what event combination is causing the same workflow to trigger twice in the same second (e.g., both
pushandpull_requestevents firing on the same commit).Expected Impact
Notes
events.jsonlfiles were found in session logs; analysis is based on sessions-list.json metadata only