4 replies

Whatsapp group message ignored

Logs show:

2026-02-12T11:42:09.840Z warn Closing open session in favor of incoming prekey bundle

2026-02-12T11:42:09.840Z warn Closing open session in favor of incoming prekey bundle

After that, I sent another message and openclaw received it successfully, but that previous message was not even received by openclaw:

Now I can see the full picture. There's no trace of your 12:42 message being received at all — no web-inbound log entry for it. Compare with the "test test" message at 11:44:25 which has a clear inbound message log line.

So the message wasn't silently dropped after being received — it was never delivered to OpenClaw by the WhatsApp bridge. The prekey renegotiation at 11:42:09 caused it to be lost at the protocol level.

Now I can see the full picture. There's no trace of your 12:42 message being received at all — no web-inbound log entry for it. Compare with the "test test" message at 11:44:25 which has a clear inbound message log line.

So the message wasn't silently dropped after being received — it was never delivered to OpenClaw by the WhatsApp bridge. The prekey renegotiation at 11:42:09 caused it to be lost at the protocol level.

What can I do to prevent this from happening?

FotC�

Friends of the Crustacean 🦞🤝•4w ago•

4 replies

Cosmic

Whatsapp group message ignored

Logs show:

2026-02-12T11:42:09.840Z warn Closing open session in favor of incoming prekey bundle

2026-02-12T11:42:09.840Z warn Closing open session in favor of incoming prekey bundle

After that, I sent another message and openclaw received it successfully, but that previous message was not even received by openclaw:

Now I can see the full picture. There's no trace of your 12:42 message being received at all — no web-inbound log entry for it. Compare with the "test test" message at 11:44:25 which has a clear inbound message log line.

So the message wasn't silently dropped after being received — it was never delivered to OpenClaw by the WhatsApp bridge. The prekey renegotiation at 11:42:09 caused it to be lost at the protocol level.

Now I can see the full picture. There's no trace of your 12:42 message being received at all — no web-inbound log entry for it. Compare with the "test test" message at 11:44:25 which has a clear inbound message log line.

So the message wasn't silently dropped after being received — it was never delivered to OpenClaw by the WhatsApp bridge. The prekey renegotiation at 11:42:09 caused it to be lost at the protocol level.

What can I do to prevent this from happening?

Whatsapp group message ignored

Similar Threads

Whatsapp group message ignored

Similar Threads

Similar Threads

Similar Threads