Optimizing Status Message Delivery: What's the Best Approach for Batching? #859
Unanswered
TheOneironaut
asked this question in
Q&A
Replies: 1 comment
-
Hi! The best approach would be to send "status" to WAHA and WAHA handles it :) We'll check GOWS for the Frame Too Large and see how we can handle it properly! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the most effective way to split and send status messages to a large number of contacts while avoiding overload and errors like Frame Too Large?
Should all contacts be fetched before each batch to ensure accurate segmentation, even though this process may take 30 seconds to a minute?
Would it be better to fetch contacts from the database once and update periodically, even if some changes might not be reflected in real-time?
Is it feasible to fetch the list once and track changes dynamically during the sending process?
What is the ideal batching strategy to maintain a balance between performance, speed, and contact list accuracy?
I would love to hear any insights or suggestions.
Thank you very much! 🙏
Beta Was this translation helpful? Give feedback.
All reactions