Cairn
NousResearch/hermes-agent

Feishu thread_id error 99992402 fallback handling

Cluster 81169 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items concern a Feishu messaging failure (error 99992402) that occurs when routing messages via thread_id in topic chats, and attempts to implement or correct a fallback mechanism that replies in-thread rather than creating a new thread.

Open issues1

  • Issue#81169Feishu: post messages fail with 99992402 when routed via thread_id (cron origin deliveries in topic chats) — no fallback

Open PRs1

  • PR#94306fix(feishu): thread fallback must reply-in-thread, not create with thread_id

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #81184 fix(feishu): fall back to chat_id when post messages fail with 99992402 on thread_id · stale or abandoned
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.67: 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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/81169.json
cluster/81169.md