Cairn

Feishu message routing and reply fallback fixes

NousResearch/hermes-agent · cluster 24808 · gateway

Data as of

6 open items. Fix attempted, not merged.

The short answer

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

Multiple issues and fixes addressing Feishu's handling of withdrawn reply targets, stale thread_id fallback behavior, and related message routing edge cases. Themes include 230011 exception handling, thread_id stripping on retry, and 99992402 field validation errors.

Open issues3

  • Issue#24808gateway/feishu: fallback send in _send_with_retry should strip thread_id from metadata
  • Issue#35576Bug: Auto-resume sends to stale thread_id causing Feishu 99992402 'field validation failed'
  • Issue#52042[Feishu] Replies quoting a withdrawn tool-progress bubble are silently dropped (inconsistent 230011 fallback)

Open PRs3

  • PR#35663fix(gateway/feishu): fall back to chat_id routing on stale thread_id (99992402)
  • PR#52076fix(feishu): handle withdrawn reply targets in both response-code and exception paths (#52042)
  • PR#54497fix(feishu): support topic group message sending

2 PRs closed without merging

From the close comments: closed without comment 1 · other 1

  • #24813 fix(gateway/feishu): in-process WS reconnect + fallback send strips thread_id · other
  • #52064 fix(feishu): fall back to create when reply raises exception for withdrawn message · closed without comment
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.20: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/24808.json
cluster/24808.md