Cairn
NousResearch/hermes-agent

Telegram duplicate inbound update deduplication work

Cluster 68502 · gateway. Data as of

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

The short answer

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

These issues and PRs concern Telegram gateways processing repeated inbound updates from Telegram's retry mechanism, resulting in duplicate replies. The work involves deduplicating updates by ID, fencing replayed updates before dispatch, and persisting update receipts across adapter rebuilds and restarts.

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.

  • #118769 fix(telegram): fence replayed updates before dispatch and observer effects

    merged to main

    files: contributors/emails/[redacted:email], plugins/platforms/telegram/adapter.py, plugins/platforms/telegram/update_admission.py, tests/gateway/test_telegram_polling_progress.py, tests/plugins/test_telegram_update_admission.py, website/docs/user-guide/messaging/telegram.md

  • #120257 fix(telegram): keep update receipts across adapter rebuilds and restarts

    merged to main

    files: plugins/platforms/telegram/adapter.py, plugins/platforms/telegram/update_admission.py, tests/plugins/test_telegram_update_admission.py

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #68906 fix(telegram): dedup inbound updates by update_id · superseded by another PR → #118769, #68502
  • #119674 fix(telegram): deduplicate repeated inbound updates from Telegram retries · superseded by another PR → #120257, #118769, #68502
Closed issues · 1
  • Closed#68502Telegram gateway processes duplicate inbound messages, causing duplicate replies
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.40: 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
#118769, #120257
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Sep 2026

For your agent

The same facts, typed.

cluster/68502.json
cluster/68502.md