#WhatsApp group

6 messages · Page 1 of 1 (latest)

austere scaffold
#

I've been troubleshooting a WhatsApp group issue and found your responses in a few threads. My situation seems slightly different:

Symptom: Group messages arrive at web-inbound (logged) but the agent never runs at all — no processing, no reply attempt, no error. Direct chat works perfectly.

What makes this different from media/delivery issues:
The agent is not even triggered. Sessions.json shows the group session was created but has no systemSent, no status, no transcript — zero agent activity.

Already tested:

  • groupPolicy: "open" âś…
  • groupAllowFrom with member phone number âś…
  • requireMention: false per group âś…
  • Groups explicitly in groups section with correct JIDs âś…
  • Two separate groups — same behavior on both
  • No sendPolicy in config
  • typingMode: "never" — no effect

Version: 2026.4.14 (updated today)

Log pattern (always stops here):

{"module":"web-inbound"} from: [group]@g.us → "inbound message"

Nothing after. No dispatch, no run, no error.

Is this the same regression as #67394 or something different? Any specific log I can pull to help diagnose?

Cola isso num DM para o Krill ou no thread mais relevante que você encontrou. É direto, técnico e facilita a vida dele para responder rápido.

charred raftBOT
#

This sounds different from the “group messages never reach the linked device” family.

Why I’m leaning that way:

  • your message is already hitting web-inbound
  • if the post-inbound handler were throwing, I’d expect failed handling inbound web message
  • “session exists but no transcript / no status / no systemSent” matches a clean skip before agent dispatch, not a delivery/media problem

The biggest gotcha here is this:

  • channels.whatsapp.groups is its own group allowlist
  • if groups is present at all, only matching groups pass
  • that is true even with groupPolicy: "open"

Docs confirm that here: https://docs.openclaw.ai/channels/whatsapp
Logs/debugging here: https://docs.openclaw.ai/help/faq

So my first suspicion is:

#
  1. group id/account scoping mismatch in channels.whatsapp.groups, or
  2. mention gating still effectively on for that resolved group, or
  3. a silent skip in group gating

Please grab these:

openclaw --version
openclaw logs --follow

Then send a test group message and paste any lines matching:

  • web-inbound
  • inbound web message
  • failed handling inbound web message
  • Skipping group message
#
  • Group message stored for context
  • group mention debug

Also paste a sanitized copy of:

  • channels.whatsapp for that account
  • the bindings entry for that group/agent

Fastest diagnostic test:

  • temporarily set channels.whatsapp.groups to just:
{
  "*": { requireMention: false }
}

If that suddenly works, it’s almost certainly a group-id/account match problem, not #67394.

#

One more subtle thing: if you have account-scoped WhatsApp config, make sure the groups block is under the same account the inbound message resolves to.

austere scaffold
#

Hey Krill! It worked 🎉

The "*": { requireMention: false } test confirmed it — was a group-id/account mismatch, not #67394.

After restoring the specific group JIDs with requireMention: false, it's working correctly now.

Thanks for the fast and precise diagnosis — saved us a lot of time! 🙏