Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Feishu channel: message tool triggers "missing tool result in session history" in v2026.5.16+ [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#84134•Fetched 2026-05-20 03:43:41
View on GitHub
Comments
1
Participants
2
Timeline
13
Reactions
1
Author
avatasiaavatasia
Participants
avatasiaavatasiaclawsweeper[bot]clawsweeper[bot]
Timeline (top)
labeled ×9commented ×1cross-referenced ×1mentioned ×1

Error Message

Feishu channel — message tool shows "Something went wrong" error in OpenClaw v2026.5.16+. Internal error logged: [openclaw] missing tool result in session history; inserted synthetic error result for transcript repair. 4. User sees the "Something went wrong" error in Feishu

  • No error is shown to the user
  • OpenClaw injects a synthetic error to repair the transcript structure
  1. OpenClaw detects the missing result and injects a synthetic error
  2. Since v2026.5.12, this internal error is sanitized and shown to users as "Something went wrong"
  • v2026.5.12: "raw provider error payloads are sanitized and replaced with generic 'Something went wrong' message"
  1. Long-term: Fix the CardKit streaming ack race condition so tool results are properly written to session history before the synthetic error is injected

Root Cause

## Root Cause (suspected)
**v2026.5.16** introduced Feishu **CardKit streaming cards** with a delta + retry mechanism.
The new CardKit streaming protocol has a **race condition**:
1. `message` tool call → CardKit delta streaming → retry logic → final ack
2. If retry succeeds but ack is not properly propagated → **result is not written to session history**
3. OpenClaw detects the missing result and injects a synthetic error
4. Since v2026.5.12, this internal error is **sanitized** and shown to users as "Something went wrong"
This did **NOT** occur in v2026.5.12 where CardKit streaming did not exist.
---
## Changelog References
- **v2026.5.16-beta.3**: "Feishu can now send CardKit streaming cards as delivered deltas and retry failed updates, preventing duplicated or dropped streamed text"
- **v2026.5.16-beta.4**: Feishu CardKit fixes for issue #82417 and #82419
- **v2026.5.18**: Further Feishu CardKit related fixes
- **v2026.5.12**: "raw provider error payloads are sanitized and replaced with generic 'Something went wrong' message"
---
## Additional Context
- WeChat channel **does NOT** have this issue
- Enterprise WeChat **does NOT** have this issue
- Feishu channel works normally with **direct text replies** (agent output via normal path, not the `message` tool)
- The `message` tool is an **OpenClaw core tool** — it fails on Feishu but works correctly on Enterprise WeChat
- Related GitHub issues: [#77518](https://github.com/openclaw/openclaw/issues/77518), [#5430](https://github.com/openclaw/openclaw/issues/5430), [#8643](https://github.com/openclaw/openclaw/issues/8643)
---
## Suggested Fix
1. **Short-term**: Document that `message` tool in Feishu is broken in v2026.5.16+ and recommend using Enterprise WeChat or direct agent output instead
2. **Long-term**: Fix the CardKit streaming ack race condition so tool results are properly written to session history before the synthetic error is injected

Code Example

## Root Cause (suspected)
**v2026.5.16** introduced Feishu **CardKit streaming cards** with a delta + retry mechanism.
The new CardKit streaming protocol has a **race condition**:
1. `message` tool call → CardKit delta streaming → retry logic → final ack
2. If retry succeeds but ack is not properly propagated → **result is not written to session history**
3. OpenClaw detects the missing result and injects a synthetic error
4. Since v2026.5.12, this internal error is **sanitized** and shown to users as "Something went wrong"
This did **NOT** occur in v2026.5.12 where CardKit streaming did not exist.
---
## Changelog References
- **v2026.5.16-beta.3**: "Feishu can now send CardKit streaming cards as delivered deltas and retry failed updates, preventing duplicated or dropped streamed text"
- **v2026.5.16-beta.4**: Feishu CardKit fixes for issue #82417 and #82419
- **v2026.5.18**: Further Feishu CardKit related fixes
- **v2026.5.12**: "raw provider error payloads are sanitized and replaced with generic 'Something went wrong' message"
---
## Additional Context
- WeChat channel **does NOT** have this issue
- Enterprise WeChat **does NOT** have this issue
- Feishu channel works normally with **direct text replies** (agent output via normal path, not the `message` tool)
- The `message` tool is an **OpenClaw core tool** — it fails on Feishu but works correctly on Enterprise WeChat
- Related GitHub issues: [#77518](https://github.com/openclaw/openclaw/issues/77518), [#5430](https://github.com/openclaw/openclaw/issues/5430), [#8643](https://github.com/openclaw/openclaw/issues/8643)
---
## Suggested Fix
1. **Short-term**: Document that `message` tool in Feishu is broken in v2026.5.16+ and recommend using Enterprise WeChat or direct agent output instead
2. **Long-term**: Fix the CardKit streaming ack race condition so tool results are properly written to session history before the synthetic error is injected
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Bug Description

Feishu channel — message tool shows "Something went wrong" error in OpenClaw v2026.5.16+.

Every message tool call in the Feishu DM triggers: ⚠️ Something went wrong while processing your request. Please try again, or use /new to start a fresh session.

Internal error logged: [openclaw] missing tool result in session history; inserted synthetic error result for transcript repair.

Steps to reproduce

Steps to Reproduce

  1. Use OpenClaw v2026.5.16 or v2026.5.18
  2. In Feishu DM, send: "用 message 工具发 test" (or any instruction that triggers the message tool)
  3. The agent calls the message tool
  4. User sees the "Something went wrong" error in Feishu

Expected behavior

  • The message tool executes successfully
  • Message is delivered to Feishu
  • No error is shown to the user

Actual behavior

  • The message tool executes but its result is not written to session history
  • OpenClaw injects a synthetic error to repair the transcript structure
  • User sees the sanitized "Something went wrong" message (added in v2026.5.12)

OpenClaw version

2026.5.18 (reproducible in 2026.5.16-beta.3+) |

Operating system

Debian 12 (bookworm) on ARM64

Install method

No response

Model

minimax

Provider / routing chain

feishu/lark->openclaw->minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

v2026.5.18 <img width="990" height="215" alt="Image" src="https://github.com/user-attachments/assets/07e1ccaa-102f-49fd-97db-04f1a586f3d5" /> v2026.5.12 <img width="370" height="224" alt="Image" src="https://github.com/user-attachments/assets/d861d2c0-3268-447c-9486-4b4451305f87" />

## Root Cause (suspected)
**v2026.5.16** introduced Feishu **CardKit streaming cards** with a delta + retry mechanism.
The new CardKit streaming protocol has a **race condition**:
1. `message` tool call → CardKit delta streaming → retry logic → final ack
2. If retry succeeds but ack is not properly propagated → **result is not written to session history**
3. OpenClaw detects the missing result and injects a synthetic error
4. Since v2026.5.12, this internal error is **sanitized** and shown to users as "Something went wrong"
This did **NOT** occur in v2026.5.12 where CardKit streaming did not exist.
---
## Changelog References
- **v2026.5.16-beta.3**: "Feishu can now send CardKit streaming cards as delivered deltas and retry failed updates, preventing duplicated or dropped streamed text"
- **v2026.5.16-beta.4**: Feishu CardKit fixes for issue #82417 and #82419
- **v2026.5.18**: Further Feishu CardKit related fixes
- **v2026.5.12**: "raw provider error payloads are sanitized and replaced with generic 'Something went wrong' message"
---
## Additional Context
- WeChat channel **does NOT** have this issue
- Enterprise WeChat **does NOT** have this issue
- Feishu channel works normally with **direct text replies** (agent output via normal path, not the `message` tool)
- The `message` tool is an **OpenClaw core tool** — it fails on Feishu but works correctly on Enterprise WeChat
- Related GitHub issues: [#77518](https://github.com/openclaw/openclaw/issues/77518), [#5430](https://github.com/openclaw/openclaw/issues/5430), [#8643](https://github.com/openclaw/openclaw/issues/8643)
---
## Suggested Fix
1. **Short-term**: Document that `message` tool in Feishu is broken in v2026.5.16+ and recommend using Enterprise WeChat or direct agent output instead
2. **Long-term**: Fix the CardKit streaming ack race condition so tool results are properly written to session history before the synthetic error is injected

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • The message tool executes successfully
  • Message is delivered to Feishu
  • No error is shown to the user
#batch processing#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Feishu channel: message tool triggers "missing tool result in session history" in v2026.5.16+ [1 comments, 2 participants]