On this page
Error 139000, "Blocked By Integrity", means Meta has not cleared your WhatsApp Business Account for forms yet, so it refused to publish (or sometimes to create) a form. It is a decision about the account, made before Meta looks at what the form contains. Your draft in VGraple CRM is kept, and nothing you built needs to change.
Symptom
You press Publish on a WhatsApp form, in the forms list or at the last step of the form editor, and a red message appears instead of the form going live. It begins "Meta has not cleared this WhatsApp Business Account for forms yet, so it refused to publish this form". It then lists what Meta asks for, the messaging limit and message quality of the form's number when VGraple CRM has read them, and ends with Meta's own reply, for example:
Blocked by Integrity (Meta error 139000/4233020, reference AbC123xyz)
The number after the slash, 4233020 in the case we have seen, is a subcode. Meta's wording for it is "Integrity requirements not met". Any subcode with 139000 is the same refusal for you, and the same fix applies.
The form stays a draft in the list, and nothing was sent to customers.
Why it happens
Meta's Flows error codes reference lists 139000 as "Blocked By Integrity" with the description "An integrity issue was identified with your account, which prevents you from creating or publishing your Flow." Meta's resolution is to contact its support.
Meta's getting-started page for Flows says that to send Flows to customers you need to verify your business and maintain a high message quality. Those are the two conditions Meta publishes.
Meta's support team told us a third on 17 November 2026: forms need a messaging limit of 2,000. New business portfolios start at 250 customers a day, so a young account is usually below it. Meta support also told us three things about that limit:
- It rises automatically as quality signals build.
- Meta cannot raise it by hand.
- Business verification alone does not lift it.
Which condition am I missing?
| Condition | Where it comes from | How to check it in VGraple CRM |
|---|---|---|
| Verified business | Meta's Flows documentation | Meta Business Manager, Security Centre. See business verification |
| High message quality | Meta's Flows documentation | Message quality on the WhatsApp channel card in Settings, then Channels, then WhatsApp. High is the goal |
| Messaging limit of 2,000 | Meta Direct Support | Daily limit on the same card. 250 customers a day is below it |
The refusal message in VGraple CRM already shows the limit and quality of the number the form belongs to when they are known. If the card shows no limit yet, press Refresh on the channel card to read it from Meta.
Fix
- Confirm the account is the one you expect. A form belongs to one WhatsApp Business Account. If you have numbers on more than one account, the message names the number the form was built for when it can.
- Complete business verification if it is not done. See Complete Meta Business Verification. It is one of Meta's two published conditions, even though it does not raise the limit by itself.
- Protect message quality. Send only to customers who opted in, use templates they expect, and review anything that gets blocked or reported. See phone number quality rating.
- Build sending history to opted-in customers. Meta support told us the limit rises as quality signals build, and that it helps to reach more customers, not the same small group over and over. Messaging tiers and limits explains how the tiers move and what Meta reviews.
- Do not wait on a manual change. Meta cannot raise the limit by hand, so a support case asking for a higher limit will not move it. If you open a case about the refusal itself, include the code and reference from the message.
- Publish the same draft again later. Nothing needs to be rebuilt. Open Settings, then Channels, then WA Forms, and press Publish on the draft once your limit and quality have moved. If a refusal still comes back, the message tells you again what Meta asks for.
While you wait, drafts remain fully editable, and this refusal does not stop you sending ordinary messages, broadcasts or chatbot flows.
How VGraple CRM handles it
VGraple CRM does not block publishing for any limit. We have seen forms publish on accounts still at 250, so a pre-emptive block would turn away accounts Meta would have accepted. Instead:
- It explains the refusal when Meta gives it. The plain message replaces the bare code, and Meta's own reply stays at the end of it.
- It keeps the draft. A refused publish changes nothing about the form. If you pressed Publish at the end of the editor, the form is saved as a draft and pressing Publish again updates that draft rather than creating a second one. Until you discard it, the draft keeps its number and template, because it cannot move to another WhatsApp Business Account; Discard this draft and start again removes it so you can choose again.
- It warns beforehand. When the default number's messaging limit is known and below 2,000, the forms page says: "Meta may refuse to publish a form until the messaging limit of {the number} reaches 2,000. Drafts are kept." When the limit has not been read yet, or is 2,000 or more, it says nothing.
- It keeps the evidence. Every refused publish is recorded in your workspace's audit trail with Meta's code, subcode and reference.
Example
A travel agency builds two forms, a booking enquiry and a feedback form, on a number at the 250 limit, and publishing the first one returns error 139000. The refusal message now says plainly what Meta asks for. The agency keeps both drafts, finishes business verification, sends its next season's offers to customers who opted in, and publishes the same drafts again when its limit has moved.
Does the same error appear when I create a form?
Sometimes. Meta's description says the integrity issue prevents you from creating or publishing a Flow, so the refusal can arrive at the Create step instead. In that case VGraple CRM says it refused to create the form, nothing was created, and your questions are still on the page, so nothing is lost.
Prevention
Treat forms as something an established account earns, and plan for it. Verify the business early, grow the number's quality and sending history on messages customers asked for, and build your forms as drafts in the meantime. The form editor and its drafts work on every plan from the first day, so your forms are ready to publish the moment Meta clears the account. For the full build and send walkthrough, see Build Meta WhatsApp Flows, and for other codes you may meet when sending, see WhatsApp error codes.