This repository has been archived by the owner on Nov 7, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 609
frequent instability in the api #596
Comments
Same problem here |
mee to |
we already talked about this on telegram. |
Any practices to reduce this problem? |
mee to |
This issue is stale because it has been open 6 days with no activity. Remove the stale label or comment or this will be closed in 2 days |
Any practices to reduce this problem? |
I can't identify it, but it's basically when you send some messages, example: 10 recipients with 5 messages each |
Draft
9 tasks
Did you mean, an overload on submissions? Wouldn't it be interesting to build a submission queue within the api? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using the api on a linux server, running with pm2. but after a while the api stops working and becomes inaccessible.
Monitoring the logs via pm2, the error below appears.
It works again when I restart pm2
The text was updated successfully, but these errors were encountered: