Telegram media group splitting causes run interruptions
NousResearch/hermes-agent · cluster 1409 · gateway
Data as of
Nothing open on GitHub. Fix merged in #1422. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #1422. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes concern Telegram batch or photo-burst messages being split across multiple turns, which can interrupt active runs. The work focuses on buffering or grouping media to prevent self-interruption.
Open issues0
Open PRs0
Fixes on record
-
#1422 fix(gateway): prevent Telegram photo burst interrupts
files:
gateway/platforms/base.py,gateway/platforms/telegram.py,gateway/run.py,tests/gateway/test_image_enrichment.py,tests/gateway/test_interrupt_key_match.py,tests/gateway/test_telegram_documents.py,tests/gateway/test_telegram_photo_interrupts.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#1410 fix(gateway): prevent Telegram photo burst interrupts · merged via another change →
#1422
Closed issues · 2
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.39: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #1422
- Closed issues
- 2
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.