## 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