Telegram typing indicator lingering after cron deliveries
Cluster 50791 · cron. Data as of
2 open items. Fix merged in #100908 on 2 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #100908. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #100908. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read #100908, then check whether your report is the one still open.
Read #100908Pick up a Lab taskMost members concern the Telegram typing indicator staying active during or after cron/automation message delivery, with several PRs proposing changes to avoid re-triggering typing or to mark cron deliveries as final. One PR also covers broader cron live-adapter delivery confirmation and empty payload handling, which goes somewhat beyond the typing issue.
Open issues1
- Issue#50791Telegram typing indicator lingers after cron delivery
Open PRs1
- PR#50792fix(telegram): don't re-arm typing after cron deliveries
Fixes on record
-
#100908 fix(cron): live-adapter delivery is confirmed by positive evidence, empty payloads fail closed, cron pushes notify (#77763, salvage #100284 #58262)
files:
cron/jobs.py,cron/scheduler.py,gateway/delivery.py,hermes_cli/config_defaults.py,hermes_cli/cron.py,tests/cron/test_cron_live_delivery_confirmation.py,tests/gateway/test_delivery_silence_filter.py,tests/hermes_cli/test_cron.py,tools/cronjob_tools.py,website/docs/user-guide/features/cron.md
2 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1
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.22: 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
- cron
- Merged PRs
- #100908
- Closed issues
- 2
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 2 Sep 2026