Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: OpenClaw 2026.5.22 + @tencent-weixin/openclaw-weixin 2.4.4 performance issue

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…

OpenClaw 2026.5.22 + @tencent-weixin/openclaw-weixin 2.4.4

Symptoms:

  1. Gateway HTTP server starts normally in 6.9s.
  2. openclaw-weixin provider takes ~78s from "starting weixin provider" to "weixin monitor started".
  3. provider auth prewarm takes ~93s.
  4. eventLoopMax reaches ~76s.
  5. A simple business script returns quickly when executed directly, but Weixin end-to-end query takes ~70s.
  6. Logs also show typing send error: AbortError and intermittent getUpdates fetch failed.

Expected: Weixin provider startup should not block for ~78s, auth prewarm should not block event loop, typing/getUpdates failures should be degraded/retried without delaying normal replies.

Error Message

  1. Logs also show typing send error: AbortError and intermittent getUpdates fetch failed.
  2. Logs also show typing send error: AbortError and intermittent getUpdates fetch failed.

Root Cause

OpenClaw 2026.5.22 + @tencent-weixin/openclaw-weixin 2.4.4

Symptoms:

  1. Gateway HTTP server starts normally in 6.9s.
  2. openclaw-weixin provider takes ~78s from "starting weixin provider" to "weixin monitor started".
  3. provider auth prewarm takes ~93s.
  4. eventLoopMax reaches ~76s.
  5. A simple business script returns quickly when executed directly, but Weixin end-to-end query takes ~70s.
  6. Logs also show typing send error: AbortError and intermittent getUpdates fetch failed.

Expected: Weixin provider startup should not block for ~78s, auth prewarm should not block event loop, typing/getUpdates failures should be degraded/retried without delaying normal replies.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

OpenClaw 2026.5.22 + @tencent-weixin/openclaw-weixin 2.4.4

Symptoms:

  1. Gateway HTTP server starts normally in 6.9s.
  2. openclaw-weixin provider takes ~78s from "starting weixin provider" to "weixin monitor started".
  3. provider auth prewarm takes ~93s.
  4. eventLoopMax reaches ~76s.
  5. A simple business script returns quickly when executed directly, but Weixin end-to-end query takes ~70s.
  6. Logs also show typing send error: AbortError and intermittent getUpdates fetch failed.

Expected: Weixin provider startup should not block for ~78s, auth prewarm should not block event loop, typing/getUpdates failures should be degraded/retried without delaying normal replies.

Steps to reproduce

sudo systemctl restart openclaw

Expected behavior

Weixin provider startup should not block for ~78s, auth prewarm should not block event loop, typing/getUpdates failures should be degraded/retried without delaying normal replies.

Actual behavior

  1. Gateway HTTP server starts normally in 6.9s.
  2. openclaw-weixin provider takes ~78s from "starting weixin provider" to "weixin monitor started".
  3. provider auth prewarm takes ~93s.
  4. eventLoopMax reaches ~76s.
  5. A simple business script returns quickly when executed directly, but Weixin end-to-end query takes ~70s.
  6. Logs also show typing send error: AbortError and intermittent getUpdates fetch failed.

OpenClaw version

5.22

Operating system

Ubuntu 22.04

Install method

No response

Model

gpt-5-mini

Provider / routing chain

weixin--->openclaw--->wechat agent ---> db agent

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

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

Weixin provider startup should not block for ~78s, auth prewarm should not block event loop, typing/getUpdates failures should be degraded/retried without delaying normal replies.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING