Skip to content

Feishu channel broken since 5.27: never called, dispatch fails with 'Cannot read properties of undefined (reading run)' #88024

@leiJack-lo

Description

@leiJack-lo

Description

Feishu channel stops working starting from version 2026.5.27. Messages are received via WebSocket but dispatch to the agent fails with:

TypeError: Cannot read properties of undefined (reading 'run')

The root cause is that setFeishuRuntime() is exported from runtime-CjGuNoJc.js but never called anywhere in the codebase. This means getFeishuRuntime() returns undefined, and when monitor.account-BHNU313T.js tries to call core.channel.inbound.run(...), it throws.

Steps to Reproduce

  1. Install OpenClaw 2026.5.27+ (also reproduced on 2026.5.28-beta.1)
  2. Configure a Feishu channel with WebSocket connection mode
  3. Send a message to the bot from Feishu
  4. Gateway receives the message but fails to dispatch

Logs

feishu[default]: received message from ou_xxx in oc_xxx (p2p)
feishu[default]: dispatching to agent (session=agent:main:feishu:direct:ou_xxx)
feishu[default]: failed to dispatch message: TypeError: Cannot read properties of undefined (reading 'run')

Root Cause

In monitor-BBAkUIze.js, the monitorFeishuProvider function is called, but setFeishuRuntime(opts.runtime) is never invoked before monitorSingleAccount runs. Inside monitorSingleAccount, the code calls getFeishuRuntime() which returns undefined because the runtime was never set.

Workaround

Downgrading to OpenClaw 2026.5.22 (or earlier) fixes the issue. Confirmed working on 2026.5.18.

Environment

  • OpenClaw versions affected: 2026.5.27, 2026.5.28-beta.1
  • Last working version: 2026.5.22 (confirmed), 2026.5.18 (confirmed)
  • macOS, Node 22.22.2
  • Feishu connection mode: WebSocket

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority user-facing bug, regression, or broken workflow.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions