whatsapp-web.js: Messages sent but never delivered to the contact
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
I’m having a weird issue: when the whatsapp-web.js client is online for some time, some messages that are sent are never actually delivered to the contact. They stay with one gray “tick” forever.
The most weird thing about this bug is that these messages appear on the mobile app with 1 gray tick as well, but never get delivered.
Sometimes clearing the whatsapp session works, but only for some time. It has to be done again and again.
This issue is happening consistently across multiple numbers, and i’ve been scratching my head a lot trying to figure out what’s happening.
Expected behavior
The messages that are sent should be delivered to the contacts after some time.
Steps to Reproduce the Bug or Issue
- Start the whatsapp-web.js client, and use for some time (e.g. 1 or 2 hours).
- Send a message via the
sendMessagemethod. - Some contacts don’t actually receive these messages, they stay with one gray “tick” forever. No delivered or read events are generated by the whatsapp client.
Relevant Code
No response
Browser Type
Chromium
WhatsApp Account Type
Standard
Does your WhatsApp account have multidevice enabled?
Yes, I am using Multi Device
Environment
OS: Docker + Alpine 3.15 Phone OS: Android whatsapp-web.js version: 1.23.1 WhatsApp Web version [run await client.getWWebVersion()]: 2.2350.52 Node.js Version: 16.20.2-r0
Additional context
Related issues, which might ou might not be the same problem: https://github.com/pedroslopez/whatsapp-web.js/issues/2603 https://github.com/pedroslopez/whatsapp-web.js/issues/2554
About this issue
- Original URL
- State: open
- Created 7 months ago
- Reactions: 1
- Comments: 22 (6 by maintainers)
I’ve been using the lib for 3 years now, and only recently these kinds of problems started. I’ts most likely a bug in whatsapp itself, and the annoying part is that it happens randomly after using the lib normally for some time.
And yes, I’m using the lib very frequently to send messages - with multiple numbers - therefore it’s not a problem of keeping the client active. In fact, the more messages are sent, the bigger the probability of this problem occuring.
Yes. It has become more serious lately (more frequent).
Same here…
Dear all, the same here. The storage of the disk was utilised up till 99% on aws EC2, i increased disk size and everything is working smoothly now.
Dear all, thank you for all the suggestions. I found out what the issue was on my side. My whatsapp web js is running on Google Cloud Server VM. The storage of the disk was utilised up till 90% most of the time and the issues above started happening. I upgraded the storage to 30GB (was 10GB before) and everything is working smoothly now. There are no more disconnection or unsent messages.
And it’s very strange because these messages even show up in the whatsapp app in the mobile phone… but they stay forever with one gray tick, never delivered. That’s why it seems like a bug in whatsapp itself.
I am facing the same issue. When i reconnect it works for some time…
I am facing the same issue. Reconnect sometimes solved the issue but there is no indication when it has the issue
Yes. You can. However bear in mind if large number of people report Spam, your number can be banned by whatsapp.
interestingly, the solution has been found, By the way I am also exploring this interesting library but I want to know: can they make a map of more than 1000 contacts who will receive messages? I’ve read WhatsApp’s policy, which forbids sending mass messages. Can’t this kind of use become a problem for WhatsApp?
@daveckw @stefanfuchs
@daveckw interesting… I’m using amazon ECS here. I’ll try to increase the disk space in the tasks, see if it helps.