openclaw - 💡(How to fix) Fix [Bug]: Native OpenClaw is extremely slow/unresponsive with Feishu (Lark) in mainland China vs. Chinese fork [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#68576Fetched 2026-04-19 15:10:02
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

When using the native OpenClaw with the same CodePlan model and Feishu (Lark) setup as the Chinese modified fork, the agent is extremely slow or completely unresponsive to messages in mainland China, while the forked version works quickly.

Root Cause

When using the native OpenClaw with the same CodePlan model and Feishu (Lark) setup as the Chinese modified fork, the agent is extremely slow or completely unresponsive to messages in mainland China, while the forked version works quickly.

Code Example

docker run -d \
  --name openclaw \
  -p 60934:3000 \
  -v /deployment/docker/openclaw/data:/app/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e NODE_ENV=production \
  -e TZ=Asia/Shanghai \
  -e OPENCLAW_PORT=3000 \
  -e REDIS_URL='redis://:[email protected]:6379/2' \
  --restart unless-stopped \
  --network openclaw-net \
ghcr.io/openclaw/openclaw:latest

I have also changed the skill source to the domestic mirror: https://cn.clawhub-mirror.com

### Expected behavior

The agent should respond to Feishu (Lark) messages promptly, similar to the forked Chinese version of OpenClaw using the same CodePlan model and Feishu workflow. It should reliably reply to every message within a reasonable timeframe without ignoring requests or experiencing significant delays.

### Actual behavior

The agent either ignores Feishu messages entirely or replies extremely slowly, even with the same CodePlan model, Feishu configuration, and the domestic skill mirror `https://cn.clawhub-mirror.com` set up. There are no visible replies in the Feishu thread, and the gateway logs show no successful response events, indicating a failure to process or deliver the reply.

### OpenClaw version

2026.4.15

### Operating system

debian 13

### Install method

_No response_

### Model

qwen-3.6 plus

### Provider / routing chain

qwen-3.6 plus

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

When using the native OpenClaw with the same CodePlan model and Feishu (Lark) setup as the Chinese modified fork, the agent is extremely slow or completely unresponsive to messages in mainland China, while the forked version works quickly.

Steps to reproduce

Deployed in PVE LXC Debian, run the following command:

docker run -d \
  --name openclaw \
  -p 60934:3000 \
  -v /deployment/docker/openclaw/data:/app/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e NODE_ENV=production \
  -e TZ=Asia/Shanghai \
  -e OPENCLAW_PORT=3000 \
  -e REDIS_URL='redis://:[email protected]:6379/2' \
  --restart unless-stopped \
  --network openclaw-net \
ghcr.io/openclaw/openclaw:latest

I have also changed the skill source to the domestic mirror: https://cn.clawhub-mirror.com

### Expected behavior

The agent should respond to Feishu (Lark) messages promptly, similar to the forked Chinese version of OpenClaw using the same CodePlan model and Feishu workflow. It should reliably reply to every message within a reasonable timeframe without ignoring requests or experiencing significant delays.

### Actual behavior

The agent either ignores Feishu messages entirely or replies extremely slowly, even with the same CodePlan model, Feishu configuration, and the domestic skill mirror `https://cn.clawhub-mirror.com` set up. There are no visible replies in the Feishu thread, and the gateway logs show no successful response events, indicating a failure to process or deliver the reply.

### OpenClaw version

2026.4.15

### Operating system

debian 13

### Install method

_No response_

### Model

qwen-3.6 plus

### Provider / routing chain

qwen-3.6 plus

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue might be resolved by investigating and adjusting the network configuration or dependencies, specifically the Redis connection, to improve the responsiveness of the OpenClaw agent in mainland China.

Guidance

  • Verify the Redis connection string REDIS_URL='redis://:[email protected]:6379/2' to ensure it is correct and the Redis server is accessible and responsive.
  • Check the network configuration and firewall rules to ensure that the OpenClaw container can communicate with the Feishu service and the domestic skill mirror without any restrictions.
  • Investigate potential differences in the network environment or dependencies between the native OpenClaw setup and the forked Chinese version that might cause the slowdown or unresponsiveness.
  • Consider monitoring the performance and logs of the OpenClaw agent and the Redis server to identify any bottlenecks or errors that could be contributing to the issue.

Example

No specific code snippet can be provided without more information about the OpenClaw configuration or the Feishu integration. However, ensuring the Redis connection is properly configured is crucial:

-e REDIS_URL='redis://:[email protected]:6379/2'

This should be verified against the actual Redis setup.

Notes

The issue seems to be related to the environment or configuration rather than the OpenClaw version itself, as the forked version works under similar conditions. The lack of detailed logs or error messages makes it challenging to provide a more specific solution.

Recommendation

Apply workaround: Adjust the network configuration and verify the Redis connection to improve the OpenClaw agent's responsiveness, as the issue appears to be environment-specific rather than a version-specific bug.

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…

FAQ

Expected behavior

The agent should respond to Feishu (Lark) messages promptly, similar to the forked Chinese version of OpenClaw using the same CodePlan model and Feishu workflow. It should reliably reply to every message within a reasonable timeframe without ignoring requests or experiencing significant delays.

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]: Native OpenClaw is extremely slow/unresponsive with Feishu (Lark) in mainland China vs. Chinese fork [1 participants]