> ## 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 Flow health: throttled and blocked Flows

> How WhatsApp monitors endpoint Flows, what throttled and blocked mean for sending and opening, how a Flow recovers, and how this applies to Flowella.

WhatsApp watches every Flow that uses an endpoint. If the endpoint becomes slow, unavailable or starts returning errors, WhatsApp first **throttles** the Flow, limiting it to 10 sends an hour, and then **blocks** it if things get worse, so nobody can open it. Health is restored automatically once the endpoint recovers. Static Flows, with no endpoint, aren't monitored.

> [!NOTE]
>
> **In Flowella.** Partly supported. HubSpot-form Flows run on Flowella's endpoint, so Flowella keeps it healthy and checks it answers WhatsApp's health check before every publish. Flowella doesn't show Meta's health alerts, or the Throttled and Blocked states, on the Flows page. Flows from the [Flow designer](https://knowledge.flowella.io/app/flow-designer.md) and the Flowella API are static, so WhatsApp doesn't monitor them.

## What WhatsApp measures

| Metric | What it means |
| - | - |
| **Endpoint error rate** | How often the endpoint returns an error or a response WhatsApp can't use |
| **Client error rate** | How often the Flow fails on customers' phones, for example because of bad navigation |
| **Endpoint latency** | How long the endpoint takes to answer. Meta suggests under 1 second. |
| **Endpoint availability** | Whether the endpoint can be reached at all, including its health checks |

Meta sends several alerts, as webhooks, before it throttles or blocks a Flow.

## What each state means

| State | Sending | Opening |
| - | - | - |
| **Published** | No limit | Works |
| **Throttled** | Up to 10 new Flow messages an hour | Customers can still open Flows they received |
| **Blocked** | Not allowed | Customers can't open Flows they already received |

Recovery runs in the same steps backwards: Blocked to Throttled, then Throttled to Published, as WhatsApp sees the endpoint is healthy again. You don't need to republish.

## If a Flow is throttled or blocked

| Alert | What to fix |
| - | - |
| Latency | Make the endpoint respond faster |
| Availability | Keep the endpoint reachable from the internet, and make sure it answers health checks |
| Error rate | Check the errors listed in the alert against Meta's Flows error codes |

For a Flow built from a HubSpot form in Flowella, [contact Flowella support](https://flowella.io/support) with the form name and when the problem started. For a Flow you run on your own endpoint, fix the endpoint and wait for WhatsApp to detect the recovery.

## What WhatsApp checks before it publishes

| Check | What's needed |
| - | - |
| Phone number | A verified, registered phone number on the WhatsApp Business Account |
| Encryption key | A signed public key uploaded to that phone number. Endpoint Flows only. |
| Endpoint | Set, reachable and answering health checks. Endpoint Flows only. |
| Meta app | An app connected to the Flow |
| Flow JSON | Valid, on a version that isn't frozen or expired |
| Webhooks | The WhatsApp Business Account subscribed to Flow webhooks |

> [!NOTE]
>
> **In Flowella.** Flowella handles each of these for HubSpot-form Flows. When one fails, the form's row shows a sync error such as **Registration required** or **Not accepted**. See [Sync errors](https://knowledge.flowella.io/app/flows.md#sync-errors) and [Flows error codes](https://knowledge.flowella.io/whatsapp/errors/flows-error-codes.md).

## Related

> [card] [Flow endpoints and security](https://knowledge.flowella.io/whatsapp/flows/flow-endpoints-and-security.md)
>
> How endpoint Flows talk to a server.

> [card] [WhatsApp Flows overview](https://knowledge.flowella.io/whatsapp/flows/flows-overview.md)
>
> All the states a Flow moves through.

> [card] [Flows error codes](https://knowledge.flowella.io/whatsapp/errors/flows-error-codes.md)
>
> Publishing and endpoint errors.

Checked against Meta's documentation on 18 November 2026: [Flow health and monitoring](https://developers.facebook.com/documentation/business-messaging/whatsapp/flows/guides/healthmonitoring), [Lifecycle of a Flow](https://developers.facebook.com/documentation/business-messaging/whatsapp/flows/guides/lifecycle) and [Flows webhooks](https://developers.facebook.com/documentation/business-messaging/whatsapp/flows/guides/flowswebhooks).


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