openclaw - 💡(How to fix) Fix feishu: ErrCode 11310 when outbound message contains multiple markdown tables [2 comments, 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#69789Fetched 2026-04-22 07:48:17
View on GitHub
Comments
2
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
commented ×2closed ×1reopened ×1

When an outbound message contains multiple markdown tables, the message fails to deliver with a Feishu API error code 11310. From the user's perspective the message is silently dropped with no retry or fallback.

Error Message

When an outbound message contains multiple markdown tables, the message fails to deliver with a Feishu API error code 11310. From the user's perspective the message is silently dropped with no retry or fallback. Delivery fails with a generic error wrapping ErrCode 11310. No fallback is attempted.

  • Feishu API error: ErrCode 11310

Root Cause

When an outbound message contains multiple markdown tables, the message fails to deliver with a Feishu API error code 11310. From the user's perspective the message is silently dropped with no retry or fallback.

RAW_BUFFERClick to expand / collapse

Description

When an outbound message contains multiple markdown tables, the message fails to deliver with a Feishu API error code 11310. From the user's perspective the message is silently dropped with no retry or fallback.

Reproduction Steps

  1. Configure a Feishu channel with default settings (renderMode unset or "auto")
  2. Send a message that contains 6 or more markdown tables in a single reply
  3. Observe: delivery fails with Feishu card send failed: code 11310

Expected Behavior

Message is delivered. If the content exceeds the Feishu card table limit, the runtime should split the content into multiple messages or degrade gracefully.

Actual Behavior

Delivery fails with a generic error wrapping ErrCode 11310. No fallback is attempted.

Environment

  • Channel: Feishu
  • Feishu API error: ErrCode 11310

extent analysis

TL;DR

Splitting the message into multiple parts to avoid exceeding the Feishu card table limit may resolve the delivery failure.

Guidance

  • Investigate the Feishu API documentation to determine the exact table limit for a single message, as this will inform the splitting strategy.
  • Consider implementing a content splitting mechanism that divides the message into multiple parts when the table limit is exceeded, ensuring each part can be delivered successfully.
  • Verify that the renderMode setting does not impact the table limit or splitting behavior, to ensure consistency across different configurations.
  • Test the splitting mechanism with different numbers of tables to identify the optimal threshold for splitting.

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The exact Feishu API table limit is not specified in the issue, so it's essential to consult the official documentation for accurate information. Additionally, the splitting mechanism should be designed to handle various message formats and content types.

Recommendation

Apply a workaround by splitting the content into multiple messages when the table limit is exceeded, as this approach allows for a more robust and reliable delivery mechanism.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING