> ## 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 Flows error codes: publishing, sending, endpoints

> What WhatsApp Flows errors 139000 to 139006, 132068 and 132069 and endpoint errors mean, which Flowella badge each one shows, and how to fix them.

WhatsApp Flows errors come from three places. **Publishing errors** (139000 to 139006) appear when Flowella creates, updates or publishes a Flow from your form. **Sending errors** (132068 and 132069) appear when you send a template whose Flow Meta has blocked or throttled. **Endpoint errors** appear when someone fills in a Flow that talks to Flowella while it's open. Flowella builds and publishes the Flow JSON for you, so most of Meta's Flow JSON validation errors never reach you.

> [!NOTE]
>
> **In Flowella.** Publishing errors show as a badge on the form's row on the **Flows** page, with more detail on the info icon. Select **Try again** after you fix the cause. Sending errors show in the Inbox, the template's **Send log** and HubSpot workflow history, with WhatsApp's wording and the code. See [Sync errors](https://knowledge.flowella.io/app/flows.md#sync-errors).

## Publishing errors

| Code | Meta's meaning | Flowella badge and message | What to do |
| - | - | - | - |
| **139000** | Integrity block: Meta found an integrity problem on the account and won't let it create or publish Flows. | **Verification required**: "Your WhatsApp Business Account needs Meta business verification before you can publish flows. Complete verification in Meta Business Manager, then try again." | Complete [business verification](https://knowledge.flowella.io/whatsapp/accounts/business-verification.md). If you're already verified, contact Meta support: the block is on Meta's side. |
| **139001** | The Flow is already published and can't be updated, or Meta saved the Flow JSON but couldn't process it. | **Published flow**: Meta doesn't allow edits to a published Flow. | Select **Try again**. Flowella publishes a new version. If it keeps failing, contact Flowella support. |
| **139002** | The Flow can't be published: it isn't a draft, it has validation errors, or its endpoint, public key, phone number or app isn't ready. | **Not accepted**: Meta couldn't publish the Flow, usually because the endpoint failed Meta's encrypted health check or the Flow isn't a draft. | Select **Try again**. If it keeps happening, contact Flowella support. |
| **139003** | A Flow can't be deprecated before it's published, or it's already deprecated. | Not shown | Nothing to do. |
| **139004** | A published Flow can't be deleted, only deprecated. | Not shown | Nothing to do. |
| **139006** | Not enough data yet for Flow metrics. | Not shown | Wait for more Flow completions. |
| **133010** | The number isn't registered. | **Registration required** | See [Error 133010](https://knowledge.flowella.io/whatsapp/errors/error-133010.md). |
| No code | Meta's validation found problems in the Flow's layout, for example two file fields, more than five opt-ins or a submit button label over 35 characters. | **Layout issue** | Fix the form. See [Limits and gotchas](https://knowledge.flowella.io/app/flows.md#limits-and-gotchas). |
| Other codes, such as **100** | Another Meta error, for example an invalid parameter. | **Meta rejected** | Check Meta Business Manager, then select **Try again**. |

> [!NOTE]
>
> Flowella writes every Flow as Flow JSON 7.3 with data API 3.0. If Meta retires that version, syncing the form again publishes it at the version Flowella then uses.

## Sending errors

These appear when you send a template with a Flow button.

| Code | Meta's meaning | What to do |
| - | - | - |
| **132068** | The Flow is **blocked**, so no messages with it can be sent. Meta blocks a Flow whose health checks fail. | Contact [Flowella support](https://flowella.io/support) with the form name, so the team can check the Flow's endpoint. |
| **132069** | The Flow is **throttled**, and 10 messages with it have already gone out in the last hour. | Wait for the hour to pass before you send more. If it keeps happening, contact Flowella support. |

## Endpoint errors

Flows built from HubSpot forms use an endpoint that Flowella hosts, so the Flow can check answers and send them to HubSpot. Native Flowella forms and forms from other providers don't use one. Meta reports endpoint problems to Flowella. The person filling in the Flow sees a general error.

| Error | What it means |
| - | - |
| `timeout_error` | The endpoint took longer than 10 seconds to answer. |
| `no_http_response_error`, `unexpected_http_status_code` | The endpoint closed the connection or returned an unexpected status. |
| `public-key-missing`, `public-key-signiture-verification`, `response-decryption-error`, `business-decryption-error` | The phone number's Flow encryption key is missing, unsigned or out of step. Flowella sets the key when it publishes the Flow, so syncing again usually fixes it. |
| `cannot_be_served` | The Flow can't be opened, for example because it isn't published or the account is blocked for integrity reasons. |
| HTTP `427` | The Flow token is no longer valid, for example because the form was already submitted. WhatsApp disables the Flow button for that person. |

If people report that a Flow shows an error when they open it or submit it, sync the form again. If it continues, contact [Flowella support](https://flowella.io/support) with the form name and the time.

## Related

* [Flows](https://knowledge.flowella.io/app/flows.md)
* [Form design best practices](https://knowledge.flowella.io/app/form-design-best-practices.md)
* [WhatsApp error codes](https://knowledge.flowella.io/whatsapp/errors/error-codes.md)

Checked against Meta's [WhatsApp Flows error codes](https://developers.facebook.com/documentation/business-messaging/whatsapp/flows/reference/error-codes) and [WhatsApp error codes](https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes) pages on 18 November 2026.


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