Nothing open on GitHub. Fix merged in #81036 on 7 Aug 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #81036. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #81036. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the Telegram gateway becomes permanently unresponsive after a network outage due to the reconnect watcher failing to fire when a fatal handler wedges. Includes the associated fix.
Open issues0
Open PRs0
Fixes on record
-
#81036 fix(gateway): recover Telegram after fatal disconnect wedge (#80598)
files:
gateway/run.py,plugins/platforms/telegram/adapter.py,tests/gateway/test_runner_fatal_adapter.py,tests/gateway/test_telegram_network_reconnect.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#80700 fix(gateway): recover Telegram after fatal disconnect wedge (#80598) · merged via another change →
#81036,#80598
Closed issues · 1
- Closed#80598[Bug]: Telegram gateway goes permanently deaf after network outage — reconnect watcher never fires (fatal handler wedges)
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
- #81036
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Aug 2026