Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Feishu card action button callback broken - wrong field names in parseFeishuCardActionEventPayload [1 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#60631•Fetched 2026-04-08 02:48:59
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
phx-openlcawphx-openlcaw
Participants
phx-openlcawphx-openlcaw

Feishu interactive card button callbacks are silently ignored since v2026.3.31. Clicking card buttons (e.g., PR merge approval cards) produces no response from the agent.

Root Cause

The parseFeishuCardActionEventPayload function (introduced in commit f248fc8f86, 2026-03-27) uses incorrect field names to extract context from the Feishu card callback event payload, causing validation to always fail.

Wrong field names used vs Feishu actual field names:

Code usesFeishu actually sends
context.open_id(not present in callback)
context.user_idopen_message_id
context.chat_idopen_chat_id

Because the fields don't match, the event is treated as invalid and silently dropped.

Fix Action

Fix

v2026.4.2 has fixed this by using the correct Feishu field names (open_message_id, open_chat_id) and adding fallback handling for DM vs group chat contexts.

Workaround

Upgrade to OpenClaw v2026.4.2+:

npm install -g openclaw@latest

Code Example

npm install -g openclaw@latest
RAW_BUFFERClick to expand / collapse

Description

Feishu interactive card button callbacks are silently ignored since v2026.3.31. Clicking card buttons (e.g., PR merge approval cards) produces no response from the agent.

Root Cause

The parseFeishuCardActionEventPayload function (introduced in commit f248fc8f86, 2026-03-27) uses incorrect field names to extract context from the Feishu card callback event payload, causing validation to always fail.

Wrong field names used vs Feishu actual field names:

Code usesFeishu actually sends
context.open_id(not present in callback)
context.user_idopen_message_id
context.chat_idopen_chat_id

Because the fields don't match, the event is treated as invalid and silently dropped.

Impact

  • All Feishu card button interactions are broken since v2026.3.31
  • PR merge approval cards, confirmation cards, and any interactive card with buttons are non-functional
  • Users clicking buttons get no response

Steps to Reproduce

  1. Send a Feishu interactive card with action buttons via OpenClaw
  2. Click any button on the card in Feishu
  3. Observe: no callback is received by the agent

Expected Behavior

Clicking a card button should trigger the callback, and the agent should receive the button's value JSON as a message.

Affected Versions

  • v2026.3.31 and later (until fix)

Fix

v2026.4.2 has fixed this by using the correct Feishu field names (open_message_id, open_chat_id) and adding fallback handling for DM vs group chat contexts.

Workaround

Upgrade to OpenClaw v2026.4.2+:

npm install -g openclaw@latest

extent analysis

TL;DR

Upgrade to OpenClaw v2026.4.2 or later to fix the issue with Feishu interactive card button callbacks being silently ignored.

Guidance

  • Verify the issue by checking the version of OpenClaw being used and confirming that it is v2026.3.31 or later.
  • To fix the issue, upgrade to OpenClaw v2026.4.2 or later using the command npm install -g openclaw@latest.
  • After upgrading, test the Feishu interactive card button callbacks to ensure they are working as expected.
  • If upgrading is not possible, consider reaching out to the OpenClaw support team for alternative solutions or workarounds.

Example

No code snippet is necessary in this case, as the fix is to upgrade to a newer version of OpenClaw.

Notes

The fix is only applicable to versions v2026.3.31 and later. Earlier versions may not be affected by this issue.

Recommendation

Upgrade to OpenClaw v2026.4.2 or later, as this version has fixed the issue with incorrect field names in the parseFeishuCardActionEventPayload function.

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…
#request error#file not found#serialization error#model compatibility#GPU setup

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 card action button callback broken - wrong field names in parseFeishuCardActionEventPayload [1 participants]