Cairn
NousResearch/hermes-agent

Telegram send_message timeout retry behavior

Cluster 47229 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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.

These members identify and address the absence of retry logic in the Telegram send_message function when timeout errors occur. They represent a bug report and related fix attempts for the same issue.

Open issues1

  • Issue#47229Telegram send_message does not retry on timeout errors

Open PRs1

  • PR#105094fix(tools): keep delivering remaining Telegram chunks after a timeout

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #47238 Fix: Telegram send_message should retry on timeout errors · done elsewhere → 6e36048, dc4de14, af381ef, #35664
  • #47923 fix(telegram): retry send_message on timeout errors · duplicate → #47238, #42927, #47229
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.50: 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
agent
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/47229.json
cluster/47229.md