Cairn
NousResearch/hermes-agent

Telegram send retries on ambiguous NetworkError may duplicate messages

Cluster 64238 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

One issue and two pull requests concern Telegram message sending, where a non-timeout NetworkError may be retried even though the request might already have reached Telegram, potentially producing duplicate messages. The pull requests propose not resending in these ambiguous or post-write cases.

Open issues1

  • Issue#64238[Telegram] Non-timeout NetworkError is blindly re-sent after the request may have reached Telegram → duplicate messages (no send idempotence)

Open PRs1

  • PR#64272fix(telegram): don't resend post-write NetworkError to avoid duplicate messages

1 PR closed without merging

From the close comments: duplicate 1

  • #64279 fix(telegram): do not blindly resend ambiguous NetworkError on send (#64238) · duplicate → #64272, #64238
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/64238.json
cluster/64238.md