Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feishu group chat @mention reply fails with dropping caller-provided groupId error

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…

Error Message

Key Error Logs

The dropping caller-provided groupId error suggests the group chat session is created but the reply routing fails because the session-derived group context doesn't match the caller-provided groupId.

Root Cause

Root Cause Hypothesis

Fix Action

Fix / Workaround

feishu[default]: dispatch complete (queuedFinal=false, replies=0)

Code Example

feishu[default]: dispatch complete (queuedFinal=false, replies=0)

plugin tool name conflict (openclaw-lark): feishu_chat

effective tool policy: dropping caller-provided groupId 
that does not match session-derived group context

---

{
  "channels": {
    "feishu": {
      "enabled": true,
      "appId": "cli_a9252ce485f8dced",
      "appSecret": { "source": "file", "provider": "lark-secrets", "id": "/lark/appSecret" },
      "domain": "feishu",
      "connectionMode": "websocket",
      "requireMention": true,
      "groupPolicy": "open",
      "groups": {
        "*": { "enabled": true }
      }
    }
  }
}

---

plugin tool name conflict (openclaw-lark): feishu_chat
RAW_BUFFERClick to expand / collapse

Bug Report: Feishu Group Chat @ Mention Reply Failure

Environment

  • OpenClaw Version: 2026.5.7
  • OS: macOS Darwin 24.6.0 (arm64)
  • Node.js: v22.22.2
  • Feishu Plugins:
    • feishu (built-in, bundled)
    • openclaw-lark (official, npm @openclaw/lark v2026.4.10)

Problem Summary

Bot receives group chat @ mentions, shows "typing" indicator, but never replies.

Detailed Behavior

Working

  • Direct Messages (DM): Bot responds normally to DMs

Broken

  • Group Chat @ Mention:

    • User @mentions bot in group
    • Bot shows "typing" indicator
    • No reply is sent

  • Group Chat without @mention (when groupPolicy: "open"):

    • Any message in group triggers "typing" indicator
    • Bot attempts to process all messages

Key Error Logs

feishu[default]: dispatch complete (queuedFinal=false, replies=0)

plugin tool name conflict (openclaw-lark): feishu_chat

effective tool policy: dropping caller-provided groupId 
that does not match session-derived group context

Configuration

{
  "channels": {
    "feishu": {
      "enabled": true,
      "appId": "cli_a9252ce485f8dced",
      "appSecret": { "source": "file", "provider": "lark-secrets", "id": "/lark/appSecret" },
      "domain": "feishu",
      "connectionMode": "websocket",
      "requireMention": true,
      "groupPolicy": "open",
      "groups": {
        "*": { "enabled": true }
      }
    }
  }
}

Reproduction Steps

  1. Add bot to any Feishu group chat
  2. @mention the bot in the group
  3. Observe "typing" indicator appears
  4. No response is received

Attempted Fixes (All Failed)

AttemptResult
Change groupPolicy: "allowlist" → "open"No change
Remove groupAllowFrom restrictionNo change
Change requireMention: true → falseNo change
Restart gatewayNo change
Disable openclaw-lark pluginBot becomes completely unreachable

Timeline

  • Before feishu plugin: Group @mentions → no reply (no "typing" indicator)
  • After feishu plugin installed: Group @mentions → "typing" indicator → no reply
  • Additional issue: Non-@mention messages also trigger "typing" indicator

Plugin Conflict

plugin tool name conflict (openclaw-lark): feishu_chat

Both feishu (built-in) and openclaw-lark (official) plugins are enabled, causing tool name conflicts.

Root Cause Hypothesis

The dropping caller-provided groupId error suggests the group chat session is created but the reply routing fails because the session-derived group context doesn't match the caller-provided groupId.

Expected Behavior

Bot should reply to @mentions in group chats when requireMention: true and groupPolicy: "open".

Actual Behavior

Bot shows "typing" but never sends a reply to group chat @mentions.

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…
#agent execution#callback error#memory management#API rate limit#retriever 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 Feishu group chat @mention reply fails with dropping caller-provided groupId error