Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feishu] Group chat session abnormally ends (status: done) causing no response to group messages, DM works fine [4 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#61994•Fetched 2026-04-08 03:10:21
View on GitHub
Comments
4
Participants
1
Timeline
4
Reactions
0
Author
SuidgeSuidge
Participants
SuidgeSuidge
Timeline (top)
commented ×4

In Feishu channel, group chat sessions abnormally enter done status, causing the bot to not respond to group messages. DM sessions remain running and work correctly.

Core symptoms:

  • DM session: status: running ✅
  • Group session: status: done ❌ (ends shortly after conversation, no idle timeout)
  • Gateway restart: ineffective
  • Switching openclaw-lark / feishu plugins: same behavior

Root Cause

Suspected Root Causes

Fix Action

Fix / Workaround

Workarounds

Code Example

{
  channels: {
    feishu: {
      enabled: true,
      connectionMode: websocket,
      dmPolicy: open,
      groupPolicy: open,
      requireMention: false,
      streaming: true,
      topicSessionMode: enabled
    }
  },
  session: {
    threadBindings: {
      enabled: true,
      idleHours: 24,
      maxAgeHours: 0
    }
  }
}
RAW_BUFFERClick to expand / collapse

Description

In Feishu channel, group chat sessions abnormally enter done status, causing the bot to not respond to group messages. DM sessions remain running and work correctly.

Core symptoms:

  • DM session: status: running ✅
  • Group session: status: done ❌ (ends shortly after conversation, no idle timeout)
  • Gateway restart: ineffective
  • Switching openclaw-lark / feishu plugins: same behavior

Environment

  • OpenClaw Version: 2026.4.5
  • OS: macOS (Darwin 25.4.0, arm64)
  • Node: v25.8.2
  • Feishu Plugin: openclaw-lark v2026.4.1 / feishu (legacy)
  • Connection Mode: WebSocket

Config snippet

{
  channels: {
    feishu: {
      enabled: true,
      connectionMode: websocket,
      dmPolicy: open,
      groupPolicy: open,
      requireMention: false,
      streaming: true,
      topicSessionMode: enabled
    }
  },
  session: {
    threadBindings: {
      enabled: true,
      idleHours: 24,
      maxAgeHours: 0
    }
  }
}

Reproduction Steps

  1. Chat with bot in Feishu group (Group ID: oc_14b6bd5bd0930846e3128fe952606503)
  2. Bot responds normally
  3. After several hours or Gateway restart
  4. Group session status becomes done, no longer responds to new messages
  5. DM session remains running, works fine

Investigation Results

Ruled out factors

CheckResultNote
WebSocket connectionOKDM messages received
Event subscriptionOKim.message.receive_v1 enabled
Bot permissionsOKAPI can read/send group messages
Plugin versionN/ASame behavior with both plugins
Gateway restartNo fixIssue persists
Session binding configOKGroup routing correct in bindings

Key findings

Session status comparison:

DM session (working):

  • key: agent:agent-qwen:feishu:direct:ou_8072af0701714ee36e1e66d6690be4d7
  • status: running
  • updatedAt: 1775491113931

Group session (broken):

  • key: agent:agent-qwen:feishu:group:oc_14b6bd5bd0930846e3128fe952606503
  • status: done
  • updatedAt: 1775490682465 (no updates after this)
  • endedAt: 1775489214381

Session history analysis:

  • Last user message in group: 23:26:41
  • Bot messages sent via message tool (delivery-mirror type) did NOT update session status
  • Feishu webhook events not triggering session wake-up

Suspected Root Causes

  1. Feishu webhook group message delivery issue - DM webhook works, group webhook has no delivery. Contacted Feishu support for investigation.

  2. OpenClaw group session wake-up logic bug - topicSessionMode enabled may affect group session routing. Group session updatedAt not updating on message events.

  3. Session state management issue - After group session enters done, no auto-wake mechanism. New message events not triggering session rebuild/activation.

Expected Behavior

  1. Group chat with new messages should auto-wake session (or create new session)
  2. Session updatedAt should update on every message event
  3. Sessions with status: done should auto-recover to running on new messages

Actual Behavior

  1. Group messages not triggering session wake-up
  2. Session stays done, unresponsive to new messages
  3. Manual intervention required to recover

Workarounds

  • Use DM channel (works fine)
  • Waiting for Feishu support feedback on webhook delivery

Additional Context

  • Affected Group ID: oc_14b6bd5bd0930846e3128fe952606503
  • Session Key: agent:agent-qwen:feishu:group:oc_14b6bd5bd0930846e3128fe952606503
  • Session ID: 1194f152-a9db-4751-91ab-64e9077a73da

Attempted fixes:

  • Gateway restart × multiple
  • Plugin switch (openclaw-lark ↔ feishu)
  • Feishu admin panel config check

extent analysis

TL;DR

Investigate and potentially fix the Feishu webhook group message delivery issue or the OpenClaw group session wake-up logic bug to resolve the abnormal done status of group chat sessions.

Guidance

  1. Verify Feishu webhook configuration: Ensure that the Feishu webhook is correctly configured to deliver group messages, and check with Feishu support for any issues on their end.
  2. Review OpenClaw session wake-up logic: Investigate the topicSessionMode enabled feature and its impact on group session routing, and consider updating the session wake-up logic to handle group messages correctly.
  3. Implement session auto-recovery mechanism: Develop a mechanism to auto-recover group sessions from the done status to running when new messages are received, to prevent manual intervention.
  4. Monitor session updatedAt updates: Verify that the session updatedAt field is updating correctly on every message event, and adjust the session state management accordingly.
  5. Test with a different group or setup: Try reproducing the issue with a different group or setup to isolate the problem and determine if it's specific to the current configuration.

Example

No specific code example is provided, as the issue requires investigation and potential fixes in the Feishu webhook configuration or the OpenClaw session wake-up logic.

Notes

The root cause of the issue is still uncertain, and further investigation is needed to determine whether it's a Feishu webhook issue, an OpenClaw group session wake-up logic bug, or a session state management problem.

Recommendation

Apply a workaround by using the DM channel until the root cause is identified and fixed, as the DM channel is working correctly. Additionally, wait for Feishu support feedback on the webhook delivery issue and investigate the OpenClaw session wake-up logic to resolve the problem.

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…
#api#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

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

Back to top recommendations

TRENDING