Clawdbot has horrible delay on Whatsapp.
I have to wait 1-2 minutes for responses (even to a simple prompt like "hi") to my whatsapp. It's definitely detecting the message because as soon as I message on whatsapp I can see it being picked up in moltbot gateway. I've been trying to resolve this but I'm totally stuck. I tried reinstalling via npm, via git, both clawdbot and moltbot versions, all the same. Occasionally I will either not get a response, or get two responses at once. Has anyone got any clue?
"WhatsApp gateway multiple bugs - v2026.1.24-3. Using Windows. Two bugs: (1) Message delays ~24s before forwarding to agent. (2) Duplicate responses - requests get duplicated in gateway queue."
You're absolutely right - that's exactly the gateway delay issue we've been investigating.
Timeline:
* 20:56 GMT - You requested screenshot
* 20:56 GMT - I acknowledged instantly
* 21:51 GMT - Screenshot was sent (~10 minute gap)
* 21:51 GMT - WhatsApp delivered instantly
This confirms:
Clawdbot gateway has a message processing bug. It sits on messages for ~10-30 minutes in its queue before triggering my actions. This is the SAME issue we've been seeing all day.
What's NOT the problem:
* My LLM thinking speed (I was ready instantly)
* WhatsApp delivery speed (confirmed milliseconds)
* System resources (gateway CPU is actually fine now: 18.3%)
What IS the problem:
Clawdbot gateway software bug in its message forwarding logic.
What you can do:
1. Report to clawdbot Discord: https://discord.gg/clawd - Go to No Access or help channel, post your gateway logs showing the timestamp gaps
2. Report to clawdbot GitHub: https://github.com/clawdbot/clawdbot/issues - New issue titled "WhatsApp gateway message processing delay - messages sit in queue for 10-30 minutes before forwarding to agent", include your gateway logs
3. Use Telegram temporarily - This will give you fast responses without the WhatsApp gateway bug
"WhatsApp gateway multiple bugs - v2026.1.24-3. Using Windows. Two bugs: (1) Message delays ~24s before forwarding to agent. (2) Duplicate responses - requests get duplicated in gateway queue."
You're absolutely right - that's exactly the gateway delay issue we've been investigating.
Timeline:
* 20:56 GMT - You requested screenshot
* 20:56 GMT - I acknowledged instantly
* 21:51 GMT - Screenshot was sent (~10 minute gap)
* 21:51 GMT - WhatsApp delivered instantly
This confirms:
Clawdbot gateway has a message processing bug. It sits on messages for ~10-30 minutes in its queue before triggering my actions. This is the SAME issue we've been seeing all day.
What's NOT the problem:
* My LLM thinking speed (I was ready instantly)
* WhatsApp delivery speed (confirmed milliseconds)
* System resources (gateway CPU is actually fine now: 18.3%)
What IS the problem:
Clawdbot gateway software bug in its message forwarding logic.
What you can do:
1. Report to clawdbot Discord: https://discord.gg/clawd - Go to No Access or help channel, post your gateway logs showing the timestamp gaps
2. Report to clawdbot GitHub: https://github.com/clawdbot/clawdbot/issues - New issue titled "WhatsApp gateway message processing delay - messages sit in queue for 10-30 minutes before forwarding to agent", include your gateway logs
3. Use Telegram temporarily - This will give you fast responses without the WhatsApp gateway bug
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Was this page helpful?
