OpenClaw Messages Are Ignored
Find why a healthy OpenClaw channel ignores DMs or group messages by checking pairing, allowlists, mention gates, and routing logs.
The channel transport is connected, but a specific sender, direct message, group, or unmentioned message receives no reply.
A connected transport only proves that OpenClaw can reach the channel provider. Sender policy and group gates can still reject the message before the model sees it.
Watch one fresh message
openclaw channels status --probe
openclaw logs --followSend one new message while logs are open. Look for a pairing request, blocked sender, allowlist miss, mention requirement, group policy, or routing decision.
Direct messages
List pending pairing requests for the channel and approve only the sender you recognize:
openclaw pairing list <channel>
openclaw pairing approve <channel> <CODE>If DM policy is allowlist-based, confirm the exact sender identifier used by that channel. Display names are not always stable identifiers.
Group messages
Check whether the group is allowed and whether requireMention is enabled. Mention the bot explicitly during the first test. Some providers also have a platform-level privacy or event-subscription setting that determines whether the bot receives unmentioned messages at all.
Separate policy from model failure
If logs show that the inbound message was accepted and a model run started, the channel gate worked. Continue with model authentication, tool errors, or outbound delivery. If no inbound event appears, fix provider visibility or transport configuration first.
Expected result
Logs show one accepted inbound event from the intended sender, the correct agent/session route, and one visible reply. Other unapproved senders remain blocked.
Source notes
Technical facts on this page were checked against primary sources.