WhatsApp template status: approved, pending, paused, disabled, and what sends

What each WhatsApp template status means on the Beacon Messenger templates page, how Meta moves a template between them, and what happens to a Shopify notification that points at one.

Open the WhatsApp page in Beacon Messenger and the templates table has a Status column with a coloured badge on every row. Most of the time it says approved in green and you never think about it. Then one morning a row is amber and says paused, or red and says disabled, and the order confirmations that depended on it have stopped. This post explains every status Meta can put on a template, what the badge colour is telling you, how a template moves from one status to another, and exactly what the app does when an automation points at a template that is not approved.

Where the status comes from

The app does not decide a template's status. Meta does, and the app asks. Each time you press Refresh templates on the WhatsApp page the app calls Meta's message templates endpoint for your WhatsApp Business Account, reads back every template with its name, language, category, components and status, and stores the list against your shop together with the time of the refresh, which is the Last refreshed line under the table. Up to a thousand templates come back in one refresh, so the list is complete for any store we have met.

Between refreshes the app works from the stored copy. That matters for two reasons. If Meta changes a status while you are not looking, say by pausing a template at 3am, the badge keeps showing the old status until someone refreshes, although the sending behaviour described below is driven by Meta's real answer at send time, not by the badge. And if an automation names a template that is not in the stored list, the app fetches a fresh list from Meta once before giving up, so a template created an hour ago is found even if nobody pressed Refresh.

The six statuses and the three colours

Template statuses as shown on the WhatsApp page
Meta statusBadgeWhat it meansWill a message send?
APPROVEDGreenReviewed and accepted. The only status the automation editor offers in its template picker.Yes
PENDINGAmberSubmitted and waiting for review. Meta says this takes up to 24 hours; in practice most templates clear in minutes.No. Meta refuses the send
REJECTEDRedReview failed. The reason is in the Meta Business Suite next to the template.No
PAUSEDAmberApproved, but Meta has stopped it for a few hours because customers reported or blocked it. Comes back automatically.No, until the pause lifts
DISABLEDRedPaused too many times, or disabled for a policy reason. Does not come back.No
IN_APPEALAmberYou appealed a rejection and Meta is reviewing again.No

The colour rule in the app is deliberately simple: approved is green, rejected and disabled are red because they need a human to do something, and everything else is amber because it will probably resolve itself if you wait. The badge text is the Meta status in lower case, so what you see on the page is what you will see in the Meta Business Suite.

Pending: the one you see most

Every new template starts here. You create it in the Meta Business Suite or through the WhatsApp Manager, Meta runs it through an automated check and sometimes a human one, and the status flips to approved or rejected. Utility templates with plain order text usually clear in under ten minutes; marketing templates and anything with a URL button take longer. The documented maximum is 24 hours.

While a template is pending it does not appear in the automation editor, because the picker only lists approved templates. If you are setting up a new automation and the template you just created is missing, that is why: refresh the list, check the badge, and wait for green. The Send a test message button has the same requirement. It needs an approved template with no variables, and if there is none it says so and suggests Meta's default hello_world template, which every new WhatsApp Business Account comes with.

Paused: what triggers it and how long it lasts

Paused is the status that causes the most alarm because it happens to templates that were approved and working. Meta tracks the quality of each template from customer reactions over a rolling window: blocks, reports and how often people stop the conversation after receiving it. When the rating drops to low, Meta pauses the template. The first pause lasts three hours, the second six hours, and a third low rating within the window disables the template outright. Meta emails the account admins and shows the reason in the Business Suite.

For a utility template such as an order confirmation, a pause almost always means one of two things. Either the template is being sent to people who did not expect it, for example a shipping update going to customers who never opted in, or the content reads as marketing, for example a confirmation with a discount code at the end. The fix is the content and the audience, not the template settings. Beacon Messenger only sends to customers whose orders have a phone number and who have not opted out, which keeps the first problem rare, but the content is yours.

  • Check the quality rating on the phone number as well. It is shown on the WhatsApp page next to the number and reflects the same signals across all templates. A number at low quality is a wider problem than one paused template.
  • Do not create a copy of a paused template with a new name to get around the pause. Meta watches for this and the copy inherits the trouble.
  • After the pause lifts, the status returns to approved on its own. Refresh templates to see the badge change.

What an automation does with a template that is not approved

This is the part worth knowing before it happens. When an order event fires, the automation looks up its template by name and language in the stored list, and if it is not there, fetches once from Meta. If the template is genuinely gone, because it was deleted or renamed, the message is logged as skipped with the reason template_not_found and nothing is sent. The template language mismatch post covers the most common cause of that, where the name is right but the language code is not.

If the template exists but is paused, pending, rejected or disabled, the app still hands the message to Meta, because the status in the stored copy may be stale and Meta is the one who knows. Meta refuses it, and the message is logged as failed with Meta's error text, which names the status. So the practical rule for reading the message log is: skipped means the app decided not to send, failed means Meta decided. A run of failed messages that all share one template name, starting at one minute and stopping a few hours later, is the signature of a pause.

  1. Open the message log and filter to failed. Note the template name and the first and last timestamps.
  2. Open the WhatsApp page, press Refresh templates, and read the badge for that template.
  3. Amber paused: wait it out, then fix the content or audience so it does not happen again. Messages that failed during the pause are not retried automatically; resend the ones that matter from the order page.
  4. Red disabled: create a replacement template with different wording, wait for approved, and point the automation at it from the automation editor.
  5. Red rejected: read the reason in the Business Suite and follow the rejected template post.

Keeping the badges honest

The Last refreshed line is the age of everything in the table. A good habit is to refresh whenever you have been in the Meta Business Suite, because that is where statuses change, and to glance at the table once a week otherwise. Nothing bad happens if you forget: sending is governed by Meta's live answer, and the badge only tells you what Meta said last time you asked. The table is there so that when a message fails, the reason is one click away rather than a login to another dashboard.

Two related posts go deeper on the red statuses. The rejected template post lists the reasons Meta gives and how to reword around each one, and the language mismatch post explains why a template can show approved in the table and still produce template_not_found in the log.

Questions about WhatsApp template status

How long does a WhatsApp template stay pending?

Meta's documented maximum is 24 hours. Utility templates with plain text usually clear in minutes; marketing templates and templates with buttons take longer. The automation editor and the test message button only list approved templates, so refresh the templates page and wait for the green badge before building the automation.

Why was my approved WhatsApp template paused?

Meta pauses a template when its quality rating drops to low, which comes from customers blocking, reporting or leaving the conversation after receiving it. The first pause is three hours, the second six, and a third low rating disables the template. For order notifications the usual cause is marketing content inside a utility message or sending to people who did not expect it.

What happens to Shopify order messages while a template is paused?

The app still submits them and Meta refuses each one, so they appear in the message log as failed with Meta's error naming the paused status. They are not retried automatically when the pause lifts. Filter the log to failed for that period and resend the ones that matter from the order page.

What is the difference between skipped and failed in the message log?

Skipped means Beacon Messenger decided not to send: no phone number, opted out, or template_not_found because no template with that name and language exists. Failed means the app sent and Meta refused, which is what a paused, pending, rejected or disabled template produces. The template name and language in the automation must match the template exactly, including the language code.

More guides