WhatsApp error 132069: Flow is throttled
Last verified against Meta for Developers - Cloud API error codes
Flow is in throttled state and 10 messages using this flow were already sent in the last hour.What error 132069 means
Code 132069 means the WhatsApp Flow you are sending is in a THROTTLED state, and in that state only 10 messages per hour that use the Flow are allowed. You have already sent those 10, so further sends fail until the hour rolls over or the Flow is returned to a healthy state. Meta throttles a Flow when its health checks are failing intermittently or when the Flow is not yet published and is being sent in preview or draft mode.
Throttling sits between healthy and blocked (132068). It is the platform limiting exposure of a Flow it does not fully trust. The numbers are small by design: 10 per hour is enough to test, not enough to run a campaign.
The fix is not to wait it out indefinitely but to resolve whatever put the Flow into the throttled state; Meta's guidance is simply "correct the Flow".
Why it happens
- The Flow is in draft or unpublished state and is being sent to real users.
- The Flow's endpoint is intermittently failing health checks.
- A recently edited Flow whose health status has not yet recovered.
- Sending more than 10 messages per hour with a Flow that is still in testing.
How to fix WhatsApp error 132069
- 1Check the Flow's status and health_status in WhatsApp Manager or via the Flows API.
- 2If it is a draft, publish it; published healthy Flows are not subject to the 10-per-hour cap.
- 3Stabilize the endpoint so health checks pass consistently (see 132068 for the checklist).
- 4Pause sends using the Flow until its state returns to healthy, then resume.
- 5If you only need testing volume, keep test sends under 10 per hour.
How to stop it recurring
Gate production campaigns on the Flow being published and healthy, checked via the API before dispatch. Keep a separate test Flow for development so throttling on it never affects customers, and alert on Flow health changes so an endpoint problem is noticed before the throttle bites. The blocked end-state is 132068, whose endpoint checklist is the same one to work through; general endpoint debugging steps are in the webhook debugging guide.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
Error 132069 - quick answers
What does WhatsApp error 132069 mean?
Code 132069 means the WhatsApp Flow you are sending is in a THROTTLED state, and in that state only 10 messages per hour that use the Flow are allowed. You have already sent those 10, so further sends fail until the hour rolls over or the Flow is returned to a healthy state.
How do I fix WhatsApp error 132069?
1. Check the Flow's status and health_status in WhatsApp Manager or via the Flows API. 2. If it is a draft, publish it; published healthy Flows are not subject to the 10-per-hour cap. 3. Stabilize the endpoint so health checks pass consistently (see 132068 for the checklist). 4. Pause sends using the Flow until its state returns to healthy, then resume. 5. If you only need testing volume, keep test sends under 10 per hour.
Can I retry after error 132069?
Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.