Cairn
NousResearch/hermes-agent

Telegram polling conflict retry state persistence

Cluster 82303 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These members concern a bug where the conflict recovery counter or marker resets on each retry attempt, causing the retry ladder to loop indefinitely rather than progress. The work involves preserving conflict state across retries during Telegram polling.

Open issues1

  • Issue#82303Telegram polling conflict counter resets on every retry — infinite (1/5) loop persists in v0.20.0 (follow-up to #58484)

Open PRs2

  • PR#82327fix(telegram): preserve conflict retry ladder
  • PR#123728fix(telegram): keep conflict recovery marker until getUpdates progress (#82303)
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.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
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/82303.json
cluster/82303.md