Bug type

Regression (worked before, now fails)

Summary

On OpenClaw 2026.3.12, WhatsApp channel appears as linked and OK, but inbound messages are not actually delivered to the bot (sender sees only one tick in WhatsApp). The channel repeatedly enters reconnect/auth loops with 440 session conflict and 401 Unauthorized errors.

Environment

• OpenClaw version: 2026.3.12 (6472949)
• OS: Linux 6.12.47+rpt-rpi-2712 (arm64) (Raspberry Pi)
• Node: 22.22.0
• Gateway: ws://127.0.0.1:18789 (local loopback)
• Channel: WhatsApp ON, account linked as +5215591923398
• Account policy seen in status: dm:allowlist · allow:+525591923398

What I expected

After successful QR link (Linked! Credentials saved), inbound WhatsApp messages should be received by OpenClaw and bot replies should be sent normally (double tick / conversation flow works).

What actually happens

• WhatsApp sometimes shows bot as linked/online, but inbound messages are not processed.
• Sender sees only one tick (message not delivered to bot session).
• Repeated channel restart/reconnect behavior appears in logs.
• Errors include:
• status 440: session conflict
• 401 Unauthorized (Connection Failure) with varying location values
• intermittent WhatsApp session logged out

Steps attempted

1. openclaw channels logout --channel whatsapp
2. openclaw channels login --channel whatsapp --verbose
3. QR scanned multiple times, including full relink attempts
4. Gateway restarts
5. Repeated validation with openclaw status --deep and channel logs
6. Verified allowlist contains correct number (+525591923398)

Issue persists.

Relevant diagnostics

openclaw status --all highlights

• WhatsApp channel reports: linked · +5215591923398 · auth 3m ago · accounts 1
• Account: default with dm:allowlist · allow:+525591923398
• Gateway may report timeout from CLI while service is running (openclaw-gateway pid ...)

openclaw channels logs --channel whatsapp --lines 400 excerpts

• WhatsApp Web connection closed (status 440: session conflict).
• WhatsApp session logged out. Run openclaw channels login --channel web to relink.
• [default] channel exited ... 401 Unauthorized (Connection Failure) with locations such as:
• cln
• vll
• cco
• frc
• odn
• lla
• many [default] starting provider + Listening for personal WhatsApp inbound messages events between failures

Additional note

Error text suggests openclaw channels login --channel web, but CLI returns:

• Unsupported channel: web
  (so expected command seems to be --channel whatsapp)

Request

Please help identify root cause and recommended stable recovery path for this reconnect/auth conflict loop (440/401) where channel appears linked but inbound delivery fails.

Steps to reproduce

1. Configure WhatsApp channel in OpenClaw and link via:
   openclaw channels login --channel whatsapp --verbose
2. Scan QR in WhatsApp Linked Devices until CLI shows:
   Linked! Credentials saved
3. Verify channel appears healthy in:
   openclaw status --all (WhatsApp shows linked / OK)
4. Send DM to the linked OpenClaw WhatsApp number from allowed sender (+525591923398)
5. Observe sender side: only one tick (not delivered), no bot response
6. Check logs:
   openclaw channels logs --channel whatsapp --lines 400
7. Observe repeated failures:

• 440 session conflict
• 401 Unauthorized (Connection Failure)
• restart loops (starting provider / Listening ...) and occasional session logged out

Expected behavior

After successful QR linking, inbound WhatsApp DMs should be consistently delivered to OpenClaw and bot replies should be sent normally (messages should not remain at single tick). The channel should remain authenticated without
entering 440/401 reconnect loops.

Actual behavior

Channel often shows as linked/OK, but inbound WhatsApp messages are not delivered (sender sees single tick) and no bot reply is produced. Logs repeatedly show 440 session conflict, 401 Unauthorized (Connection Failure),
auto-restart attempts, and intermittent session logged out.

OpenClaw version

2026.3.12 (6472949)

Operating system

Linux 6.12.47+rpt-rpi-2712 (arm64) (Raspberry Pi)

Install method

No response

Model

openai-codex/gpt-5.3-codex

Provider / routing chain

Gateway local loopback (ws://127.0.0.1:18789) → OpenClaw WhatsApp channel (default account)

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