Session-chat routes and concurrent-run cap enforcement
Cluster 112690. Data as of
Nothing open on GitHub. Fix merged in #113127 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113127. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113127. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern session-chat API endpoints that consume the concurrent-run budget but were not subject to its cap, and work to make them respect and return 429 responses at that limit.
Open issues0
Open PRs0
Fixes on record
-
#113127 fix(api-server): session-chat routes answer 429 at the concurrent-run cap they already consume (#112690, salvage #112691)
files:
gateway/platforms/api_server.py,tests/gateway/test_api_server.py,website/docs/user-guide/features/api-server.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#112691 fix(api-server): session-chat routes respect the concurrent-run cap they already consume · done elsewhere →
9934972,#112690
Closed issues · 1
- Closed#112690Session-chat endpoints consume the concurrent-run budget but are exempt from the cap
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #113127
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 17 Sep 2026