When OpenClaw Stops Answering on WhatsApp

Relink WhatsApp when OpenClaw has lost its linked session or pairing never completed. If the session is active, send one traceable message from an authorized number and check where it stops before restarting or changing access rules.

Find out whether pairing completed

OpenClaw connects through WhatsApp Web and the gateway owns the linked session. Inspect the linked-device list on the phone and the connection state on the intended OpenClaw gateway. If the phone never registers the link, or the device was logged out, use openclaw channels login --channel whatsapp on the intended instance and complete the phone's linked-device flow. The same login flow can offer to install the WhatsApp plugin if it is missing.

If the phone cannot read the code, show the whole QR code at a readable size and reduce glare. If the code has expired, generate a fresh one. Check for both a linked-device entry and a connected state on the gateway before moving on. A successful scan with a gateway that keeps waiting is an incomplete connection.

Use one alias for each synthetic message. A healthy session does not by itself prove that a particular inbound message survived the policy layer.

WhatsApp - OpenClaw

Trace a direct message before testing a group

Use a sender you intend to authorize and test with a direct message containing a unique short string. Record the send time and look for the corresponding incoming event, any access decision you can see, and the outgoing reply. OpenClaw configuration controls who can message the bot. Review the WhatsApp access rule on the active instance if the gateway receives the message and the sender is blocked or asked to pair.

For an illustrative test, suppose the phone shows the test gateway as linked and an intended operator sends "Reply with WA-42" at 10:15. The gateway records the incoming message and an authorization rejection. Correct access for that sender and repeat using WA-43. A matching reply establishes the direct-message path. Test group access separately with the intended group and its configured rules.

Run the same trace once in a permitted direct chat and once in the intended group. Identify the first differing checkpoint before changing account settings.

Configuration - OpenClaw

Restart only when it tests a hypothesis

If the phone lists the linked device but the gateway stays in a connecting state, capture the current connection error and check whether it advances. When the instance has stopped responding or a connection error persists after the link is saved, use the host's restart control once. Because OpenClaw's gateway owns the linked session, check the same gateway and linked device after it comes back before generating another code.

A restart is useful if the gateway returns to a connected state and a new test message receives a reply. If it returns to the same error, preserve the logs and check whether the phone still recognizes the intended device. If several devices are linked, identify the OpenClaw entry before removing anything. Leave unrelated devices paired unless the phone reports a limit you need to resolve.

WhatsApp - OpenClaw

Check routing after the message gets in

If the WhatsApp message appears in the gateway's logs and passes the sender check, look for the start of the agent turn, the model response, and the outgoing send result. A reply that appears in the agent session but never reaches the phone points you toward outgoing delivery. If the turn itself fails, send an equally small prompt through the same agent's normal chat surface where available and compare the errors.

When an access or routing edit appears to have no effect, check the active instance and the configuration item before interrupting the gateway. OpenClaw's configuration docs direct operators to the hot-reload guidance to determine when a restart is required. After the change takes effect, repeat the WhatsApp test with a new marker and confirm receipt on the phone.

Configuration - OpenClaw

Sources