Cairn

Telegram polling heartbeat NetworkError reconnect handling

NousResearch/hermes-agent · cluster 62047

Data as of

Nothing open on GitHub. Fix merged in #62098. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #62098. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #62098. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug was identified where python-telegram-bot NetworkError and TimedOut exceptions raised during the polling heartbeat were not being routed into the reconnect path. These members address classifying and routing those transport errors to trigger reconnection properly.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #62098 fix(telegram): classify PTB heartbeat transport errors

    merged to main

    files: plugins/platforms/telegram/adapter.py, tests/gateway/conftest.py, tests/gateway/test_telegram_network_reconnect.py

4 PRs closed without merging

From the close comments: done elsewhere 3 · closed without comment 1

  • #62060 fix(telegram): route PTB NetworkError to reconnect ladder in polling heartbeat · closed without comment
  • #62104 fix(telegram): PTB NetworkError/TimedOut in heartbeat reconnect path (#62047) · done elsewhere → 97fb9e1, 90bd5b0
  • #62106 fix(telegram): PTB NetworkError/TimedOut in heartbeat reconnect path (engine-on pilot, mirrors #62104) (#62047) · done elsewhere → 97fb9e1, 90bd5b0, #62104
  • #63007 fix(telegram): route PTB NetworkError/TimedOut from polling heartbeat into reconnect path (#62047) · done elsewhere → #62098, #62047, #62104, #62106
Closed issues · 1
  • Closed#62047[Bug]: Telegram polling heartbeat swallows python-telegram-bot NetworkError, so reconnect is never triggered
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs
#62098
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
10 Jul 2026

For your agent

The same facts, typed.

cluster/62047.json
cluster/62047.md