> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp throughput: messages per second per number

> How many WhatsApp messages a number can send per second (80, 1,000 or 20), the pair rate limit for one contact, and how to avoid errors 130429 and 131056.

Throughput is how many messages a WhatsApp business number can handle **per second**. Each registered number can handle up to **80 messages per second** by default. Meta upgrades busy, high-quality numbers to **1,000 messages per second** automatically. Numbers that also use the WhatsApp Business app ([co-existence](https://knowledge.flowella.io/whatsapp/accounts/co-existence.md)) are fixed at **20 messages per second**. Separately, one number can send only about **one message every 6 seconds to the same person**.

Throughput is not the same as your [messaging limit](https://knowledge.flowella.io/whatsapp/limits/messaging-limits.md). The messaging limit counts how many **different people** you can start conversations with in 24 hours. Throughput counts how fast messages go out.

> [!NOTE]
>
> **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

| Limit | Value | Applies to |
| - | - | - |
| Default throughput | 80 messages per second | Each registered business number |
| Higher throughput | 1,000 messages per second | Numbers that meet the [upgrade criteria](#the-upgrade-to-1000-messages-per-second) |
| Co-existence numbers | 20 messages per second, fixed | Numbers used in the WhatsApp Business app and the Cloud API at the same time |
| Pair rate limit | 1 message every 6 seconds to the same person (about 10 a minute or 600 an hour) | Each pair of business number and WhatsApp user |
| Pair burst | Up to 45 messages in 6 seconds to one person, then a wait | Each pair of business number and WhatsApp user |

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](https://knowledge.flowella.io/whatsapp/limits/messaging-limits.md) and by the per-user [marketing limit](https://knowledge.flowella.io/whatsapp/limits/per-user-marketing-limit.md).

### 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:

| Requirement | Detail |
| - | - |
| Messaging limit | The number's business portfolio has an **unlimited** [messaging limit](https://knowledge.flowella.io/whatsapp/limits/messaging-limits.md). |
| Volume | The number has messaged **100,000 or more** different people outside a customer service window in a moving 24-hour period. |
| Quality | The number's [quality rating](https://knowledge.flowella.io/whatsapp/limits/quality-score.md) is **Medium** (Yellow) or better. |

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.

| Code | What it means |
| - | - |
| **130429** | Your number sent faster than its throughput allows. |
| **131056** | Too many messages to the **same person** in a short time. |
| **131057** | The number is in maintenance mode, often during a throughput upgrade. |
| **80007** | Your WhatsApp Business Account made too many API requests, for example template or phone number lookups. |

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](https://knowledge.flowella.io/whatsapp/errors/error-130429.md) and [Error 131056](https://knowledge.flowella.io/whatsapp/errors/error-131056.md) 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](https://knowledge.flowella.io/app/bulk-send.md).

**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

> [card] [Messaging limits](https://knowledge.flowella.io/whatsapp/limits/messaging-limits.md)
>
> How many different people your portfolio can message in 24 hours.

> [card] [Quality rating](https://knowledge.flowella.io/whatsapp/limits/quality-score.md)
>
> The number rating that throughput upgrades depend on.

> [card] [Co-existence](https://knowledge.flowella.io/whatsapp/accounts/co-existence.md)
>
> Using one number in the WhatsApp Business app and Flowella.

> [card] [WhatsApp error codes](https://knowledge.flowella.io/whatsapp/errors/error-codes.md)
>
> Every code Flowella shows, with what to do.

Checked against Meta's documentation on 18 November 2026: [Throughput](https://developers.facebook.com/documentation/business-messaging/whatsapp/throughput), [About the WhatsApp Business Platform](https://developers.facebook.com/documentation/business-messaging/whatsapp/about-the-platform#rate-limits) and [WhatsApp error codes](https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes#throttling-errors).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.