The template status lifecycle
A template moves through a sequence of states, and approval is the middle of it rather than the end. An approved template can be paused for quality, reinstated, paused again and eventually disabled permanently, all without anyone touching it.
The error returned when sending with a paused template.
The error returned when a template is permanently disabled.
Webhook fields that report the lifecycle: status and quality updates.
The states
In the order a template usually meets them.
- PENDING: submitted and awaiting review.
- APPROVED: usable for sending.
- REJECTED: refused at review, usually on structure or category.
- PAUSED: temporarily unusable after a quality decline.
- DISABLED: permanently unusable, the end of the line.
How a template gets paused
Not by anything you do. Recipients block or report messages sent with it, the template's own quality rating falls from green to yellow to red, and Meta pauses it to stop the decline.
A pause is temporary and lifts on its own. What matters is what happens next: repeated pauses escalate, and a template that keeps returning to red ends up permanently disabled rather than paused again.
The two webhooks
Both are needed to see the whole cycle, and subscribing to one without the other leaves a blind spot.
- message_template_status_update: approval, rejection, pausing and disabling.
- message_template_quality_update: the quality rating moving between green, yellow and red.
- The quality webhook is the early warning; the status webhook is the consequence.
- Neither is on by default, so both have to be subscribed.
Why yellow is the moment to act
By the time a template is paused, sending with it already fails and a campaign is already broken. Yellow is the state where it is still working and the decline is visible.
Acting on yellow means looking at the audience as well as the wording. A well written template sent to people who did not expect it collects blocks just as fast as a badly written one, and rewriting the copy while keeping the list changes nothing.
What editing does
An approved template can be edited, which sends it back through review. That is useful and it has a consequence people meet in production: if the edit changes the number of variables, every send from an unchanged integration starts failing with error 132012.
Treat a template's variable count as part of the integration contract rather than as copy somebody in marketing owns.
Common mistakes
- Treating approval as permanent. An approved template can be paused and eventually disabled.
- Subscribing to status but not quality. The quality field is the early warning.
- Editing a template's variables without checking the code that sends it.
EasyCoexistence forwards both template webhooks to your endpoint, so a quality decline reaches your system at yellow rather than being discovered when a send fails.
Frequently asked questions
Does an approved template stay approved?
Not necessarily. Sustained negative feedback can pause it and eventually disable it permanently.
What is the difference between paused and disabled?
A pause lifts on its own. Disabled is permanent and the template cannot be used again.
How do I see it coming?
Subscribe to the template quality webhook. It reports the move to yellow while the template still works.
Why did sends start failing after an edit?
If the edit changed the variable count, the unchanged integration now sends the wrong number of parameters and gets error 132012.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on