# NousResearch/hermes-agent · Telegram forum topic thread_id lost in cron delivery

## Open now

- Nothing open on GitHub.

Multiple fixes and reports addressing a bug where explicit thread_id values for Telegram forum topics are dropped or ignored during cron-scheduled message delivery. Covers delivery target resolution, session isolation, and routing logic.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #16795: Cron Telegram topic delivery drops explicit thread_id

## Prior & competing PRs

- **#16815: fix(cron): preserve explicit thread_id in delivery target resolution (#16795)**. closed without merge · fix tier `suggested`
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `6ce796b49`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#16797: fix: preserve telegram cron topic delivery**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#16846`, `#16795`

## Fix status

- No merged fix on record.