OpenClaw Channel Pairing Failed
Resolve an expired, missing, or unapproved channel pairing request and confirm that the sender passes message policy.
A direct message creates no reply, the pairing code is rejected, or logs show a sender waiting for approval.
Pairing is an approval boundary for direct-message senders. Approve only a request you can tie to the intended account.
Generate a fresh request
Send the bot a new direct message, then list pending requests for the channel:
openclaw pairing list --channel <channel>Some channel commands also accept the channel as a positional value. Use the syntax printed by your installed version.
Approve the current code
Pairing codes are time-limited. For Telegram, they currently expire after one hour. Approve the newest request from the expected sender, not a code copied from an older screenshot.
Check the Gateway and logs
openclaw gateway status
openclaw channels status --probe
openclaw logs --followIf no pairing request appears, the channel may not be receiving messages at all. Fix transport, token, or network issues first.
Check overlapping policy
Pairing approval does not override every room or group allowlist. Confirm the sender, account, and channel policy all refer to the same identity.
Expected result
The pending request disappears after approval, the sender is recognized, and a new direct message reaches the agent without another pairing prompt.
Source notes
Technical facts on this page were checked against primary sources.