Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Bug Report - WhatsApp session not restored [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#49952•Fetched 2026-04-08 01:00:50
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
jrr00064jrr00064
Participants
jrr00064jrr00064RyceRyce
Timeline (top)
labeled ×2referenced ×2commented ×1

WhatsApp Web session is saved to disk but not restored when the gateway restarts. After updating to 2026.3.13, WhatsApp appears "connected" in status but cannot send/receive messages after gateway restart. Requires manual re-linking every time.

Root Cause

WhatsApp Web session is saved to disk but not restored when the gateway restarts. After updating to 2026.3.13, WhatsApp appears "connected" in status but cannot send/receive messages after gateway restart. Requires manual re-linking every time.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

WhatsApp Web session is saved to disk but not restored when the gateway restarts. After updating to 2026.3.13, WhatsApp appears "connected" in status but cannot send/receive messages after gateway restart. Requires manual re-linking every time.

Steps to reproduce

1.⁠ ⁠⁠ openclaw channels login --channel whatsapp --account default ⁠ 2.⁠ ⁠Send message → works 3.⁠ ⁠⁠ openclaw gateway restart ⁠ 4.⁠ ⁠After send message → fails: "No active WhatsApp Web listener"

Expected behavior

Whatsapp works normally

Actual behavior

1.⁠ ⁠⁠ openclaw channels login --channel whatsapp --account default ⁠ 2.⁠ ⁠Send message → works 3.⁠ ⁠⁠ openclaw gateway restart ⁠ 4.⁠ ⁠After send message → fails: "No active WhatsApp Web listener"

OpenClaw version

2026.3.13

Operating system

• VPS: Oracle Ubuntu ARM64

Install method

npm but long time ago the 1st version

Model

Ollama cloud minimax 2.5

Provider / routing chain

Ollama

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the WhatsApp Web session not being restored after a gateway restart, we need to modify the session persistence mechanism.

  • Update the openclaw configuration to enable persistent sessions for WhatsApp Web:
// config.json
{
  "channels": {
    "whatsapp": {
      "sessionPersistence": true
    }
  }
}
  • Implement a restart hook to reload the saved WhatsApp Web session:
// restart_hook.js
const openclaw = require('openclaw');

openclaw.on('restart', () => {
  openclaw.channels.whatsapp.reloadSession();
});
  • Ensure the whatsapp channel is properly configured to use the persisted session:
// whatsapp_channel.js
const openclaw = require('openclaw');

openclaw.channels.whatsapp.init({
  session: openclaw.channels.whatsapp.loadSession()
});

Verification

After applying these changes, restart the gateway and attempt to send a message via WhatsApp Web. The session should be restored, and the message should be sent successfully.

Extra Tips

  • Verify that the sessionPersistence option is enabled for the WhatsApp Web channel.
  • Check the OpenClaw logs for any errors related to session persistence or WhatsApp Web connectivity.
  • Consider implementing additional logging or monitoring to detect and respond to future session persistence issues.

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 works normally

#api#ssr#installation#tensor shape#autograd error#environment setup#docker error#permission error#memory optimization#batch processing

Still need to ship something?

×6

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

Back to top recommendations

TRENDING