Engineering
WhatsApp error 132016 (template disabled): replace the template without repeating the mistake
What to do after a template is permanently disabled: Meta's two routes (new template or edit and resubmit), a replacement checklist, switching every sender of the old name, and keeping the new one out of the pause cycle.
By Broadchat teamPublished 6 min read
In short
WhatsApp error 132016 means the "Template has been paused too many times due to low quality and is now permanently disabled." It happens on the third low-quality pause. Meta's fix is to "Create a new template with different content"; its pausing page also allows editing a disabled template and resubmitting it for approval. Either way, change the content and the audience that caused the blocks, then update every campaign, bot and integration that still sends the old name.
Key takeaways
- 132016 is the end of the pause cycle: 3 hours, then 6 hours, then disabled on the third low-quality instance.
- Unlike a pause, a disable does not lift with time; the template stays unsendable until it is replaced or edited and re-approved.
- Meta's error page says to create a new template with different content; copying the old text under a new name invites the same result.
- Every place that sends the old template name (campaigns, bots, order webhooks, CRM triggers) keeps failing until you switch it.
- The replacement needs a cleaner audience and lower frequency, not just new words.
WhatsApp error 132016 means the template you are sending is permanently disabled. Meta's error reference says the "Template has been paused too many times due to low quality and is now permanently disabled," and gives one fix: "Create a new template with different content." If you have reached this code, the same template was already paused with error 132015 twice. Waiting will not help this time.
How a template gets to 132016
Meta's template pausing rules work in three steps. When a template's quality rating falls to the lowest level (Active - Low quality, quality_score RED), it is paused for 3 hours the first time and 6 hours the second time. The third time it is disabled. Each change is announced by the message_template_status_update webhook and in WhatsApp Manager.
So a disabled template is a record of three separate moments when enough recipients blocked, reported or ignored it. That history matters for the replacement: the same message to the same people will produce the same signals.
Your two options
| Option | What Meta says | When it fits | Trade-off |
|---|---|---|---|
| Create a new template | Error reference: "Create a new template with different content." | The message itself was the problem, or you want a clean start | New name to roll out everywhere; new review, which can take up to 24 hours |
| Edit and resubmit the disabled one | Pausing page: "If an approved template has become disabled, you may also edit it and resubmit it for approval." | You want to keep the name that your systems already use | Still needs a review; a light edit does not change why people blocked it |
Whichever you choose, "different content" should mean a different message, not three words swapped. Meta's review guidance lists duplicate content among common rejection reasons, so a near-copy under a new name can also be rejected.
What it looks like
Illustrative send response (wording varies):
{
"error": {
"message": "(#132016) Template is disabled",
"type": "OAuthException",
"code": 132016,
"error_data": {
"messaging_product": "whatsapp",
"details": "Template has been paused too many times due to low quality and is now permanently disabled."
},
"fbtrace_id": "AmQ2Wk7Lp9VtR3nXc5sZbF"
}
}Your webhook log should show an earlier pair of PAUSED events for the same message_template_id, followed by DISABLED.
Step-by-step recovery
- Find every sender of the old name. Search campaigns, chatbot flows, automations, order and payment webhooks, and any script that calls the API. Each one will keep failing until it is switched.
- Work out what went wrong. Check list sources, frequency and timing for the three periods that ended in a pause. Note which segment blocked or opted out most.
- Write a genuinely different message. Lead with the reason the customer would want it, make the business name clear, keep the offer short, and add an opt-out quick reply such as "Stop offers".
- Check the category. A promotional message must be Marketing. Putting an offer into a Utility template is a separate problem that Meta handles with recategorisation and, for repeated cases, error 131064.
- Submit the new template (or edit and resubmit the old one) and wait for approval.
- Switch every sender you found in step 1 to the approved template, including its new variables.
- Relaunch small. Send first to customers who bought or replied recently, and watch the new template's quality rating before widening.
A worked example
Meera handles WhatsApp for a coaching institute in Kota. Its marketing template admission_open_2026 ("Admissions open! Call now for 20% scholarship") went to every number in the enquiry database each week. It was paused in August, paused again in September and disabled in October; the next morning the CRM trigger that welcomed new enquiries started failing with 132016 too, because it reused the same template.
She splits the job in two. New enquiries get a utility-style follow-up tied to the form they just filled, with no promotion in it, submitted as a new template. The marketing message becomes scholarship_test_nov26, rewritten around a specific scholarship test date and fee (₹499), with a "Stop updates" quick reply, sent only to students who enquired in the last 60 days, and only twice a month. She deletes admission_open_2026 once both are approved and switched.
Keeping the replacement healthy
- Treat the first pause as the alarm. That is the cheapest moment to change the audience.
- Separate transactional and promotional sends, so that a tired offer cannot take a welcome or order message down with it.
- Cap frequency per customer and drop numbers that never read your messages.
- Make opting out easy. A quick-reply opt-out is a softer signal for you than a block or a report.
How Broadchat handles a disabled template
When Meta's status webhook reports a template as disabled, Broadchat marks it as not sendable in CRM → WhatsApp Templates and records DISABLED as the reason, so it no longer behaves like an approved template in the panel. Failed messages show "The template is disabled because of low quality." with code 132016 in message info. Create the replacement in CRM → WhatsApp Templates, run Sync Templates once Meta approves it, and then update the campaigns, chatbot steps and automations that used the old one. Broadchat does not swap templates in your flows automatically.
For writing replacements that pass review, see why WhatsApp templates get rejected and the WhatsApp message templates guide. All codes are in the WhatsApp API error codes cheat-sheet.
Sources
- WhatsApp error codes — Meta for Developers, checked 1 November 2026
- Template pausing — Meta for Developers, checked 1 November 2026
- Template fundamentals (review time and template limits) — Meta for Developers, checked 1 November 2026
Broadchat team · Product and partner success team
The people who build and support Broadchat, the white-label WhatsApp Business API platform. We write from what we see while onboarding partners and their clients on the official WhatsApp Cloud API, and we check every article against Meta's current documentation.
Last updated:
Frequently asked questions
What does WhatsApp error 132016 mean?
It means the template was paused too many times because of low quality and is now permanently disabled. It happens on the third low-quality instance, after a 3-hour and a 6-hour pause, and it does not lift with time.
Can a disabled WhatsApp template be restored?
Not by waiting. Meta's error reference says to create a new template with different content, and its template pausing page says you may also edit a disabled template and resubmit it for approval. Both routes need a fresh review.
Can I recreate the same template with a new name?
You can submit it, but it is a poor idea. The same message to the same people tends to collect the same blocks and reports, and Meta's review guidance lists duplicate content as a common rejection reason. Change the message and the audience.
Why are my order messages failing with 132016 when only the offer was bad?
Because some flow, trigger or integration is still sending the disabled template by name. Find every place that uses it and switch each one to an approved template.
Does 132016 affect my other templates or my number?
The disable applies to that template. But the signals behind it, such as blocks and reports, also feed your phone number's quality rating, so keep sending the same way and other limits, such as error 131048, can follow.