Skip to main content
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.
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 and the Flowella API are static, so WhatsApp doesn’t monitor them.

What WhatsApp measures

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

What each state means

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

For a Flow built from a HubSpot form in Flowella, contact Flowella 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

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 and Flows error codes.

Flow endpoints and security

How endpoint Flows talk to a server.

WhatsApp Flows overview

All the states a Flow moves through.

Flows error codes

Publishing and endpoint errors.
Checked against Meta’s documentation on 18 November 2026: Flow health and monitoring, Lifecycle of a Flow and Flows webhooks.
Last modified on November 18, 2026