# NousResearch/hermes-agent · Feishu thread_id routing error and fix attempts

## Open now

- 1 issue, 3 PRs open on GitHub.
- #78975: Feishu cron delivery fails with \[99992402\] — receive_id_type="thread_id" is not a valid Feishu API value
- PR #78989: fix(feishu): use reply API instead of invalid receive_id_type="thread_id" on create fallback
- PR #93432: fix(feishu): preserve cron topic reply anchors
- PR #104747: fix(feishu): stop losing topic messages to invalid receive_id_type=thread_id routing

A bug where Feishu cron delivery fails due to an invalid receive_id_type='thread_id' value, with related pull requests proposing fixes via retry logic or switching to a reply API.

## TL;DR

- 5 member(s): 1 open issue(s), 0 closed issue(s), 3 open PR(s), 0 merged PR(s), 1 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.40`: 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.

## Open related issues

- #78975: Feishu cron delivery fails with \[99992402\] — receive_id_type="thread_id" is not a valid Feishu API value

## Prior & competing PRs

- **#78989: fix(feishu): use reply API instead of invalid receive_id_type="thread_id" on create fallback**. open
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#75940`, `#75940`
  - files: `plugins/platforms/feishu/adapter.py`, `tests/gateway/test_stream_consumer_thread_routing.py`
- **#81494: fix(feishu): retry post messages without thread routing on 99992402**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#81184`, `#81184`
- **#93432: fix(feishu): preserve cron topic reply anchors**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `cron/scheduler.py`, `plugins/platforms/feishu/adapter.py`, `tests/cron/test_scheduler.py`, `tests/gateway/test_feishu.py`, `tests/tools/test_cronjob_tools.py`, `tests/tools/test_send_message_tool.py`, `tools/cronjob_tools.py`, `tools/send_message_tool.py`
- **#104747: fix(feishu): stop losing topic messages to invalid receive_id_type=thread_id routing**. open
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#59444`, `#33584`, `#33582`, `#68234`, `#59444`
  - files: `plugins/platforms/feishu/adapter.py`, `tests/gateway/test_feishu_reply_target_recovery.py`, `tests/gateway/test_stream_consumer_thread_routing.py`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`