#Proactive outbound WhatsApp sends via the message tool always fail

1 messages ยท Page 1 of 1 (latest)

devout adder
#

Version: 2026.3.12 (also tested on 2026.3.13, same behavior)
Platform: Linux x86_64, Docker container
Install method: docker-compose with alpine/openclaw image

Problem:
Proactive outbound WhatsApp sends via the message tool always fail with:

Error: No active WhatsApp Web listener (account: default). Start the gateway, then link WhatsApp with: openclaw channels login --channel whatsapp --account default.

What works:

โœ… Inbound WhatsApp (messages from phone โ†’ bot)
โœ… Reactive replies within an active WhatsApp session
โœ… channels status reports linked / running / connected
โœ… Telegram outbound works fine
What doesn't work:

โŒ message tool with channel=whatsapp
โŒ Cron job proactive sends to WhatsApp
Steps taken that didn't fix it:

docker restart
openclaw channels login --channel whatsapp (re-links without QR, says "linked")
Cleared ~/.openclaw/credentials/whatsapp/default/ and re-paired via QR scan
Downgraded from 2026.3.13 โ†’ 2026.3.12
Logs on startup:

CopyCopied!
[whatsapp] [default] starting provider (+xxxxxxxxx)
[whatsapp] Listening for personal WhatsApp inbound messages.
No "outbound sender registered" or similar log line ever appears.

Related: Appears similar to issue #34741

Any fix or workaround appreciated โ€” this blocks all cron/proactive WhatsApp automation.