Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix WhatsApp: auto-reply delivery silently fails for secondary-account group sessions with :thread: suffix

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…

Auto-reply delivery (the automatic posting of assistant text to the originating chat) silently fails for WhatsApp group sessions on non-default (secondary) accounts. The assistant generates a reply, but it is never dispatched to WhatsApp. No error is logged. The session appears successful.

Error Message

Auto-reply delivery (the automatic posting of assistant text to the originating chat) silently fails for WhatsApp group sessions on non-default (secondary) accounts. The assistant generates a reply, but it is never dispatched to WhatsApp. No error is logged. The session appears successful. 5. Actual: reply exists in session transcript but never dispatched. No `[whatsapp] Sending message` log entry. No error.

Root Cause

Auto-reply delivery (the automatic posting of assistant text to the originating chat) silently fails for WhatsApp group sessions on non-default (secondary) accounts. The assistant generates a reply, but it is never dispatched to WhatsApp. No error is logged. The session appears successful.

Fix Action

Workaround

Agent uses the `message` tool explicitly with `channel: "whatsapp"`, `accountId: "secondary"`, and `target: "<group-JID>"` for all replies in these sessions.

RAW_BUFFERClick to expand / collapse

Summary

Auto-reply delivery (the automatic posting of assistant text to the originating chat) silently fails for WhatsApp group sessions on non-default (secondary) accounts. The assistant generates a reply, but it is never dispatched to WhatsApp. No error is logged. The session appears successful.

Affected session pattern

Session keys with the :thread:whatsapp-account-<name> suffix: ``` agent:<id>:whatsapp:group:<jid>:thread:whatsapp-account-secondary ```

Not affected

  • DM sessions on the same secondary account (key pattern: `agent:<id>:whatsapp:direct:<number>`) — auto-delivery works fine
  • Group sessions on the default account (no thread suffix) — auto-delivery works fine

Reproduction

  1. Configure a secondary WhatsApp account with a group
  2. Receive an inbound message in that group
  3. Agent generates a text reply (stopReason=stop, non-NO_REPLY)
  4. Expected: reply auto-delivered to WhatsApp group
  5. Actual: reply exists in session transcript but never dispatched. No `[whatsapp] Sending message` log entry. No error.

Evidence

  • Session `a986464a` (agent: personal-assistant, group: `[email protected]`)
  • Two assistant replies generated, both with `didSendViaMessagingTool: false`
  • Gateway log shows inbound messages at 10:49 and 10:50 but zero outbound sends
  • Using the `message` tool explicitly with `accountId: "secondary"` from the same session works fine

Likely cause

The auto-reply dispatcher resolves delivery target from the session key. The `:thread:whatsapp-account-secondary` suffix likely causes the dispatcher to either:

  • Not recognize the delivery context (account mismatch)
  • Silently skip delivery (no accountId resolution from session key)

Workaround

Agent uses the `message` tool explicitly with `channel: "whatsapp"`, `accountId: "secondary"`, and `target: "<group-JID>"` for all replies in these sessions.

Environment

  • OpenClaw 2026.5.12 (f066dd2)
  • WhatsApp plugin (Baileys)
  • Two WhatsApp accounts: default + secondary

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING