Meta’s wording: Cloud API message throughput has been reached. Meta’s fix is to try again later, or send less often.
What causes it
- A large bulk send, or several bulk sends from the same number running at once.
- A HubSpot workflow that enrols many contacts at the same moment, for example after a list import, with a WhatsApp step straight away.
- A co-existence number, which is capped at 20 messages per second whatever its volume.
How to confirm it in Flowella
- Inbox and Send log. Flowella’s general message, “WhatsApp (Meta) rejected this request. If it persists, check Meta Business Manager or contact support.”, with WhatsApp’s wording and the code underneath.
- HubSpot.
FLOWELLA_META:genericfor Send WhatsApp Template, orFAILEDfor Send WhatsApp Message and Send WhatsApp Reply. - Pattern. Many failures from the same number within the same minute, each with 130429.
How to fix it
1
Resend the failed messages
Meta doesn’t queue refused messages, and Flowella doesn’t retry them. Wait a few minutes, then send again to the recipients that failed. For a bulk send, start a new job with only those recipients.
2
Split very large sends
Divide the list into several jobs and schedule them a few minutes apart. See Bulk send.
3
Stagger HubSpot enrolments
Add a short Delay before the WhatsApp step in workflows that enrol thousands of contacts at once.
4
Use a Cloud API-only number for big campaigns
A co-existence number stays at 20 messages per second. Send large campaigns from a number that isn’t also used in the WhatsApp Business app.

