WhatsApp error 132068: Flow is blocked

Code 132068 applies to WhatsApp Flows, the interactive multi-screen forms you can attach to messages and templates. It means the Flow you referenced is in a BLOCKED state, so messages that try to launch it are refused. Meta blocks a Flow when its health checks fail, most commonly because the endpoint your Flow depends on is unreachable, returns errors, or does not pass the encryption and signature validation that Flows require. A Flow can also be blocked if its JSON fails validation after a change.

Until the underlying issue is corrected and the Flow returns to a healthy state, every send that uses it fails with 132068. The rest of your messaging, including other templates and other Flows, is unaffected.

The recipient, token, and the template wrapping the Flow are not the problem; the Flow itself needs attention.

Monitor the Flow endpoint like any production API: uptime checks, latency alerts, and a signed-response test in CI. Keep the encryption keypair under configuration management and rotate it in a controlled way. Publish Flow changes through a staging Flow first so a broken edit cannot block the production one. Flow health failures often masquerade as webhook problems; the endpoint checklist in the webhook debugging guide applies to Flow endpoints too. The throttled halfway state is 132069.