Summary
The message tool fails with No active WhatsApp Web listener for both WhatsApp accounts, despite openclaw channels status --probe confirming both are enabled, configured, linked, running, connected.
This is a continuation/regression of #14406 — the workaround (hard restart) no longer works as of 2026.3.13.
Steps to Reproduce
- Gateway running, WhatsApp connected (confirmed via
channels status --probe)
- Use the
message tool to send a proactive WhatsApp message
- Error:
No active WhatsApp Web listener (account: default)
- Hard restart gateway (
openclaw gateway restart)
- Confirm WhatsApp reconnected via
channels status --probe → shows connected
- Try
message tool again → same error
Expected Behavior
After a hard restart, the message tool should be able to find the WhatsApp listener and send proactive messages.
Actual Behavior
The message tool consistently returns No active WhatsApp Web listener regardless of:
- Fresh gateway start
- Hard restart
- Both accounts (
default and secondary website-builder)
Meanwhile, auto-reply (inbound message → bot responds) works fine, confirming the WhatsApp connection is alive.
Impact
- All proactive WhatsApp sends are broken (follow-ups, notifications, outbound campaigns)
- Agents can only respond reactively, not initiate conversations
- CRM follow-up crons fail silently
- Client-facing bots cannot send scheduled messages
Environment
- OpenClaw: 2026.3.13 (61d171a)
- Node: v22.22.0
- OS: Linux 5.15.0-171-generic (x64, Ubuntu)
- WhatsApp accounts: 2 (default + website-builder), both show
connected
- Channel status output:
- WhatsApp default: enabled, configured, linked, running, connected, dm:open, allow:*
- WhatsApp website-builder: enabled, configured, linked, running, connected, dm:open, allow:*
Related Issues
Notes
The root cause from #14406 (code-splitting creating duplicate Map<string, Listener> instances) seems to have not been fully resolved. The hard restart workaround mentioned in #14406 no longer repopulates the correct Map in 2026.3.13.
Summary
The
messagetool fails withNo active WhatsApp Web listenerfor both WhatsApp accounts, despiteopenclaw channels status --probeconfirming both areenabled, configured, linked, running, connected.This is a continuation/regression of #14406 — the workaround (hard restart) no longer works as of 2026.3.13.
Steps to Reproduce
channels status --probe)messagetool to send a proactive WhatsApp messageNo active WhatsApp Web listener (account: default)openclaw gateway restart)channels status --probe→ showsconnectedmessagetool again → same errorExpected Behavior
After a hard restart, the
messagetool should be able to find the WhatsApp listener and send proactive messages.Actual Behavior
The
messagetool consistently returnsNo active WhatsApp Web listenerregardless of:defaultand secondarywebsite-builder)Meanwhile, auto-reply (inbound message → bot responds) works fine, confirming the WhatsApp connection is alive.
Impact
Environment
connectedRelated Issues
Notes
The root cause from #14406 (code-splitting creating duplicate
Map<string, Listener>instances) seems to have not been fully resolved. The hard restart workaround mentioned in #14406 no longer repopulates the correct Map in 2026.3.13.