openclaw - 💡(How to fix) Fix weixin getUpdates fetch failed after upgrade to 2026.5.4 [5 comments, 6 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#77837Fetched 2026-05-06 06:20:28
View on GitHub
Comments
5
Participants
6
Timeline
8
Reactions
4
Timeline (top)
commented ×5closed ×1mentioned ×1subscribed ×1

After upgrading from OpenClaw 2026.5.3-1 to 2026.5.4, the weixin plugin continuously throws TypeError: fetch failed in getUpdates. All inbound message delivery is broken.

  • Plugin: @tencent-weixin/openclaw-weixin v2.3.1 and v2.4.1 both affected
  • Downgrading OpenClaw back to 2026.5.3-1 immediately restores normal operation

Error Message

[5424d3e4645e-im-bot] getUpdates error: TypeError: fetch failed, stack=TypeError: fetch failed [5424d3e4645e-im-bot] getUpdates: 3 consecutive failures, backing off 30s

Root Cause

After upgrading from OpenClaw 2026.5.3-1 to 2026.5.4, the weixin plugin continuously throws TypeError: fetch failed in getUpdates. All inbound message delivery is broken.

  • Plugin: @tencent-weixin/openclaw-weixin v2.3.1 and v2.4.1 both affected
  • Downgrading OpenClaw back to 2026.5.3-1 immediately restores normal operation

Fix Action

Fix / Workaround

weixin getUpdates fetch failed after upgrade to 2026.5.4

Code Example

[5424d3e4645e-im-bot] getUpdates error: TypeError: fetch failed, stack=TypeError: fetch failed
[5424d3e4645e-im-bot] getUpdates: 3 consecutive failures, backing off 30s
RAW_BUFFERClick to expand / collapse

Title

weixin getUpdates fetch failed after upgrade to 2026.5.4

Bug type

Regression (worked in 2026.5.3-1, fails in 2026.5.4)

Beta release blocker

No

Summary

After upgrading from OpenClaw 2026.5.3-1 to 2026.5.4, the weixin plugin continuously throws TypeError: fetch failed in getUpdates. All inbound message delivery is broken.

  • Plugin: @tencent-weixin/openclaw-weixin v2.3.1 and v2.4.1 both affected
  • Downgrading OpenClaw back to 2026.5.3-1 immediately restores normal operation

Steps to reproduce

  1. Install openclaw-weixin plugin (v2.3.1 or v2.4.1)
  2. Run OpenClaw 2026.5.4 on Windows
  3. Weixin channel starts but getUpdates fails immediately

Relevant logs

[5424d3e4645e-im-bot] getUpdates error: TypeError: fetch failed, stack=TypeError: fetch failed
[5424d3e4645e-im-bot] getUpdates: 3 consecutive failures, backing off 30s

Additional context

  • Standalone Node.js fetch('https://ilinkai.weixin.qq.com') from the same machine works fine (returns HTTP 404 as expected)
  • Only the Gateway's internal fetch fails
  • No TLS/proxy configuration involved
  • No relevant config warnings from doctor

Environment

  • OpenClaw: 2026.5.4
  • OS: Windows 11 (build 26200)
  • Node: v24.14.1
  • Install method: npm

extent analysis

TL;DR

Downgrade OpenClaw to version 2026.5.3-1 to resolve the TypeError: fetch failed issue in the weixin plugin.

Guidance

  • Verify that the issue is specific to the weixin plugin by checking if other plugins are working correctly with OpenClaw 2026.5.4.
  • Test the fetch function in a standalone Node.js environment to ensure it's working as expected, as mentioned in the additional context.
  • Check the OpenClaw changelog for version 2026.5.4 to see if there are any changes that could be causing the issue with the weixin plugin.
  • Consider reaching out to the OpenClaw or weixin plugin maintainers to report the issue and ask for assistance.

Notes

The issue seems to be specific to the combination of OpenClaw 2026.5.4 and the weixin plugin, as downgrading OpenClaw resolves the issue. There may be a compatibility problem or a bug introduced in OpenClaw 2026.5.4 that's causing the fetch function to fail.

Recommendation

Apply workaround: Downgrade OpenClaw to version 2026.5.3-1, as it has been confirmed to resolve the issue. This is a temporary solution until the root cause is identified and fixed.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING