Skip to content

Misleading log: Listening for personal WhatsApp inbound messages — group messages received but not routed #83779

@alissonaguiar

Description

@alissonaguiar

Summary

The WhatsApp provider logs "Listening for personal WhatsApp inbound messages" at startup. Group messages are captured by the web monitor (web-inbound module) but are not routed to agent sessions unless the group is registered in channels.whatsapp.groups.

The log message is misleading — it implies only DM messages are being listened to, but group messages ARE received by the monitor. They just aren't dispatched.

Suggestion

  1. Log should say "Listening for WhatsApp inbound messages (DM + N groups)" with the count of configured groups
  2. When a web-inbound message arrives from an unregistered group, emit a debug/warn log: "Dropping message from unregistered group. Add to channels.whatsapp.groups to enable."
  3. Document clearly that channels.whatsapp.groups is required for inbound routing, not just groupAllowFrom

Environment

  • OpenClaw: 2026.5.12, 2026.5.18

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low-priority cleanup, docs, polish, ergonomics, or speculative work.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions