Parallelize messaging platform startup connections
Cluster 83791 · gateway. Data as of
Nothing open on GitHub. Fix merged in #86673 on 15 Aug 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 #86673. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #86673. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where messaging platform connections at gateway startup were serialized, causing one platform's failure to cascade to others. The work involves connecting platforms in parallel and capping cold-start budgets.
Open issues0
Open PRs0
Fixes on record
-
#86673 fix(gateway): parallel platform connects + capped Telegram cold-start budget (#85993, #83791)
files:
contributors/emails/[redacted:email],gateway/run.py,tests/gateway/test_multiplex_adapter_registry.py,tests/gateway/test_startup_connect_parallel.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#83809 fix(gateway): connect messaging platforms in parallel at startup (#83791) · merged via another change →
#86673,#85993
Closed issues · 1
- Closed#83791Follow-up: messaging-platform connects appear serialized — one platform's failure cascades to others
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
- Subsystem
- gateway
- Merged PRs
- #86673
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Aug 2026