Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: WhatsApp listener dies after upgrade — "No active WhatsApp Web listener" on all outbound messages (resolved by reverting to v2026.03.11) [1 comments, 2 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#52773•Fetched 2026-04-08 01:19:37
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
renantealbeldarenantealbelda
Participants
ArtyomkunArtyomkunrenantealbeldarenantealbelda
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

Bug After upgrading beyond v2026.03.11, all outbound WhatsApp messages fail with:

No active WhatsApp Web listener

Resolution Manually reverting to v2026.03.11 (29dc654) fully resolved the issue. WhatsApp outbound restored immediately after rollback with no other changes.

Error Message

  1. Error: No active WhatsApp Web listener

Root Cause

Bug After upgrading beyond v2026.03.11, all outbound WhatsApp messages fail with:

No active WhatsApp Web listener

Resolution Manually reverting to v2026.03.11 (29dc654) fully resolved the issue. WhatsApp outbound restored immediately after rollback with no other changes.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Bug After upgrading beyond v2026.03.11, all outbound WhatsApp messages fail with:

No active WhatsApp Web listener

Resolution Manually reverting to v2026.03.11 (29dc654) fully resolved the issue. WhatsApp outbound restored immediately after rollback with no other changes.

Steps to reproduce

  1. Upgrade OpenClaw past v2026.03.11
  2. Attempt to send any outbound WhatsApp message
  3. Error: No active WhatsApp Web listener

Expected behavior

WhatsApp outbound messaging should remain functional across version upgrades.

Actual behavior

Inbound messages continue to be received normally. openclaw status --probe falsely reports the channel as "linked, running, connected" despite the listener being dead.

What I tried (none resolved the issue)

  • Multiple openclaw gateway restart cycles
  • openclaw channels login re-linking on all accounts
  • Force-killing all zombie gateway/node processes and clearing stale PID/lock files
  • Full WhatsApp device logout + fresh QR scan
  • Reviewing for Split-Brain gateway conflicts (standalone binary vs. LaunchAgent)

OpenClaw version

2026.03.13

Operating system

  • OS: macOS Ventura 13.x - OpenClaw: affected on builds newer than 2026.03.11 - Resolved version: 2026.3.11 (commit 29dc654) - Channel: WhatsApp (multi-account: default + realestateoutreach)

Install method

No response

Model

gemini-flash-latest / anthropic-opus-4.5

Provider / routing chain

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

The stale-socket auto-restart loop in the WhatsApp provider logs was the most visible symptom — the provider kept restarting but never recovered the listener. This points to a possible regression in the WA session initialization or socket keepalive logic introduced after 2026.03.11.

extent analysis

Fix Plan

To resolve the "No active WhatsApp Web listener" error after upgrading OpenClaw past v2026.03.11, follow these steps:

  • Revert to version v2026.03.11 (29dc654) as a temporary solution.
  • To fix the issue without downgrading, update the WhatsApp provider configuration to handle the new session initialization or socket keepalive logic:
    • Check the openclaw configuration file for any changes related to WhatsApp session management.
    • Update the WhatsApp channel configuration to include any new required parameters for session initialization or socket keepalive.

Example code snippet to update the WhatsApp channel configuration:

# Update the WhatsApp channel configuration
whatsapp_config = {
    'session_init_timeout': 30,  # adjust the session initialization timeout
    'socket_keepalive_interval': 60  # adjust the socket keepalive interval
}

# Apply the updated configuration
openclaw.channels.update('whatsapp', whatsapp_config)
  • Restart the OpenClaw gateway and WhatsApp provider after applying the configuration changes:
openclaw gateway restart
openclaw provider restart whatsapp

Verification

To verify that the fix worked:

  • Check the OpenClaw gateway and WhatsApp provider logs for any errors related to session initialization or socket keepalive.
  • Attempt to send an outbound WhatsApp message to ensure it is delivered successfully.
  • Run openclaw status --probe to verify the WhatsApp channel is reported as "linked, running, connected".

Extra Tips

  • Monitor the OpenClaw and WhatsApp provider logs for any issues related to session initialization or socket keepalive.
  • Consider updating the OpenClaw configuration to include any new required parameters for session initialization or socket keepalive.
  • If issues persist, try resetting the WhatsApp device and re-linking the WhatsApp account.

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

WhatsApp outbound messaging should remain functional across version upgrades.

#autograd error#model save/load#optimization#mixed precision#training loop

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]: WhatsApp listener dies after upgrade — "No active WhatsApp Web listener" on all outbound messages (resolved by reverting to v2026.03.11) [1 comments, 2 participants]