Cairn

Telegram polling conflict retry and recovery fixes

NousResearch/hermes-agent · cluster 75017 · gateway

Data as of

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

The short answer

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

Multiple fixes addressing Telegram 409 polling conflict errors, including retry loop behavior, backoff preservation, stale session cleanup, and gateway reconnection handling. Related instrumentation and SQLite warning issues are also touched.

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.

  • #55905 fix(telegram): recover when polling updater stops while process stays alive (#55769)

    merged to mainSuggested link · files and diff not shown

  • #78344 fix(telegram+sqlite): resolve polling conflict loop + misleading WAL warning

    merged to main

    files: hermes_state.py, plugins/platforms/telegram/adapter.py, tests/gateway/test_telegram_conflict.py

5 PRs closed without merging

From the close comments: merged via another change 3 · done elsewhere 1 · other 1

  • #2297 fix(gateway): retry Telegram 409 polling conflicts before giving up · merged via another change → #2312
  • #25232 fix(gateway): route conflict-retry start_polling failure to reconnect ladder · done elsewhere → f260aa6
  • #64506 fix(telegram): instrument getUpdates request via subclass re-tag, not slotted attr (#64482) · merged via another change → #64574
  • #75073 fix(telegram): clear stale polling sessions on conflict retry · other
  • #75096 fix(telegram): preserve conflict retry backoff after transient progress · merged via another change → #78344, #75073
Closed issues · 1
  • Closed#75017Telegram polling conflict: self-perpetuating retry loop from drop_pending_updates=False
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.25: 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

Subsystem
gateway
Merged PRs
#55905, #78344
Closed issues
1
Attempts
5 PRs closed without merging
Fix link checked
4 Aug 2026

For your agent

The same facts, typed.

cluster/75017.json
cluster/75017.md