-
-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG][NOWEB] - Some messages are not delivered to our webhook #671
Comments
+1 |
2 similar comments
Hi! @itesainnovation @HuangDaHui @masitings could you send the full logs around the errors please at [email protected] 🙏 |
Hi all! Could you try to update to |
Has there been any progress in the correction? I have many complaints from customers about lost messages, new contacts who had no conversation history call and the message does not appear in the API. This is really urgent. @devlikepro |
Hi! Could you try updating to For rest 10% we're looking for proper solution, but no luck so far - the only thing left is to move entire NOWEB to new golang based engine MEOW with better key handling :( If you face the issue after updating to 2024.12.2 - pleease send logs (as much as possible) to [email protected], it will help understand further research direction! |
@Lange1990 could you send a day/hour log (when missing messages happened) to [email protected] from docker container, that will be really helpful 🙏 |
An important percent of messages our sessions receive are not being delivered to our webhook.
We check the container logs and found this two issues:
Error: Connection Closed
We are getting this error and therefore messages are not being delivered to our webhook.
PDO message without response after 15 seconds. Phone possibly offline
We also got this issue and message was not delivered. Is there a way to attempt a sequence of retries after this?
We are using the latest version.
Thanks!
The text was updated successfully, but these errors were encountered: