WhatsApp API error 132068: Flow is blocked
Error 132068 means the message tried to send a WhatsApp Flow that is currently blocked. A blocked Flow can't be sent until it's corrected.
Quick answer
The Flow is blocked. Find out why in the Flow's status, correct the Flow, and send it again once it's no longer blocked.What WhatsApp error 132068 means
Meta documents 132068 as: Flow is in blocked state, and the action is to correct the Flow.
Why error 132068 happens
Flow errors come from the state of the Flow itself rather than the message carrying it. Typical reasons:
- The Flow's endpoint has been failing or responding too slowly, so the Flow was blocked.
- Problems with the Flow's health or its endpoint that Meta flagged.
- Sending an old Flow that was left in a broken state.
- A change to the endpoint, such as a new deployment, that broke the Flow's data exchange.
How to fix error 132068
Work through these in order; the first one that turns up a problem is usually the fix.
- Open the Flow's status and health information to see why it's blocked.
- If it uses an endpoint, check the endpoint is reachable, fast and answering correctly.
- Correct the Flow and publish or update it as needed.
- Send a test to yourself before using it in campaigns again.
- Keep a simpler fallback message ready for customers while the Flow is being fixed.
Should you retry after 132068?
Sends using a blocked Flow keep failing. Fix the Flow first, then send again.
How error 132068 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 132068, the "(#132068)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.