In Flowella. Supported, with nothing to set up: Meta applies the limits to your number. Flowella doesn’t slow its sends to match your number’s throughput, and it doesn’t retry messages that Meta refuses for speed. A message refused with 130429 or 131056 shows as failed, with the reason, in the Inbox, the template’s Send log and HubSpot workflow history.
Meta’s limits
Throughput counts inbound and outbound messages of every type, not just templates. A number at full throughput is still bound by its portfolio’s messaging limit and by the per-user marketing limit.
The pair rate limit
Throughput is meant for sending to many different people. Sending to one person is limited much more tightly: about one message every 6 seconds. You can send a burst of up to 45 messages in 6 seconds, but the burst borrows from later. After it, you have to wait as long as those messages would have taken at the normal rate. For example, a burst of 20 means roughly a 2-minute wait before that person can get another message. Above the limit, Meta refuses messages to that person with 131056 until you’re back under it. You can keep messaging everyone else. In Flowella, the pair limit usually comes from automation rather than people typing:- A HubSpot workflow that sends several messages to the same contact with no delay between steps.
- Several workflows that enrol the same contact at the same moment.
- A test that sends the same template to your own phone over and over.
The upgrade to 1,000 messages per second
Meta upgrades a number automatically, at no cost, when all of these are true:
The upgrade takes up to a minute. During that minute the number can’t send, and Meta returns 131057 (account in maintenance mode). After the first upgrade, later increases happen with no downtime. Meta signals the upgrade with a
phone_number_quality_update webhook whose event is THROUGHPUT_UPGRADE. Higher throughput doesn’t change what you pay.
What you see
Meta refuses these messages as Flowella sends them, so they fail straight away rather than after a delivery attempt.
For 130429, 131056 and 131057, Flowella shows its 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. In HubSpot, the Error code output is
FLOWELLA_META:generic for Send WhatsApp Template and FAILED for Send WhatsApp Message and Send WhatsApp Reply.
For 80007, Flowella shows “Meta rate-limited this action. Wait a moment and try again.” and HubSpot shows FLOWELLA_META:rate_limited.
See Error 130429 and Error 131056 for the full fixes.
What to do
1
Space out messages to the same contact
Add a delay of at least a minute between WhatsApp steps in a HubSpot workflow, and stop several workflows from messaging the same contact at once. This avoids 131056.
2
Resend failed messages later
A message refused for speed isn’t queued by Meta. Wait a few minutes, then send it again. For a bulk send, start a new job with only the failed recipients.
3
Split very large sends
If a bulk send to a large list returns 130429, split the list into several jobs and schedule them a few minutes apart. See Bulk send.
4
Check a co-existence number's cap
If the number is also used in the WhatsApp Business app, its throughput stays at 20 messages per second. Plan large sends from a Cloud API-only number instead.
Related
Messaging limits
How many different people your portfolio can message in 24 hours.
Quality rating
The number rating that throughput upgrades depend on.
Co-existence
Using one number in the WhatsApp Business app and Flowella.
WhatsApp error codes
Every code Flowella shows, with what to do.

