Gateway model connection error state classification fix
Cluster 116323. Data as of
Nothing open on GitHub. Fix merged in #116438 on 20 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 #116438. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116438. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the gateway incorrectly labels reset or cause-free API connection errors as 'not running' or 'unreachable', and work to distinguish between interrupted, unreachable, and ambiguous connection states.
Open issues0
Open PRs0
Fixes on record
-
#116438 Gateway chat reply no longer calls a reset model connection 'not running' (#116323, salvage #109701)
files:
contributors/emails/[email protected],gateway/run.py,tests/gateway/test_local_model_connection_reply.py,website/docs/reference/faq.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#116394 fix(gateway): distinguish interrupted, unreachable and ambiguous model connections (#116323) · done elsewhere →
30de041,#116438
Closed issues · 1
- Closed#116323[Bug]: Gateway classifies reset and cause-free APIConnectionError as endpoint not running/unreachable
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
- #116438
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026