Cairn
NousResearch/hermes-agent

Telegram polling 409 conflict retry counter and infinite loop

Cluster 58484. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members all concern Telegram polling hitting repeated 409 Conflict errors, where the conflict retry counter appears to reset or not increment, so the fatal/restart path may never be reached. Some are issue reports and others are proposed fixes, with approaches such as preserving the counter across retries or adding a wall-clock escalation.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1 · other 1

  • #58492 fix(telegram): keep polling conflict counter across successful retries · other → #58492, #64361
  • #64064 fix(telegram): escalate persistent 409 Conflict to fatal via wall-clock gate · superseded by another PR → b8295cf
  • #64082 fix(telegram): break infinite 409 conflict loop by not resetting counter on polling success (#63724) · duplicate → #63724, #58484, #58492, #64064, #64082
Closed issues · 2
  • Closed#58484Telegram polling conflict (1/5) retry counter never increments — infinite reconnect loop
  • Closed#63724Telegram: persistent 409 Conflict loops forever — conflict counter resets on start_polling(), fatal/restart path unreachable, bot silently deaf
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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

Closed issues
2
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/58484.json
cluster/58484.md