---
title: "WhatsApp API Error Codes: 131026, 131049, 131047 Fixes | ConfirmX"
description: "What the common WhatsApp Business API errors mean and what to do: 131026 undelivered, 131047 outside the window, 131049 marketing withheld, 131042 billing, 133010 not registered."
url: https://confirmx.net/en/guides/whatsapp-error-codes/
lang: en
last_updated: 2026-11-02
---

# WhatsApp Business API error codes: 131026, 131049, 133010 and more

When a message fails, Meta returns a code. ConfirmX shows a plain title, Meta’s text and the code on the message itself. This table explains each one and what to do.

ConfirmX team · 2 November 2026 · 3 min read

## Common codes

| Code | Meaning | What to do |
| --- | --- | --- |
| **131026** | Not delivered. The number may not be on WhatsApp or is temporarily unavailable. | Check the number. ConfirmX retries by itself (below). |
| **131047** | Outside the 24-hour window. | Send an approved template. |
| **131049** | Meta withheld a marketing message from this customer. | Don’t re-send. Utility messages aren’t affected. |
| **130472** | The customer is in a Meta marketing test group. | Nothing to do. |
| **131042** | A billing or account issue. | Check your payment method in Meta Business Manager. |
| **131048** | Your number’s quality dropped. | Review templates and opt-in, and reduce complaints. |
| **131056** | Sending limit reached. | Slow down and try later. |
| **132000 – 132015** | A template error: name, language or variables. | Check variable mapping, or recreate the template. |
| **133010** | The number isn’t registered on the Cloud API. | Not a token problem. Contact us to re-register with the two-step PIN. |
| **190** | The connection expired. | Reconnect the account. |
| **200, 10** | Missing permissions. | An admin grants them in Business Manager. |

## Error 131026 in detail

Most WhatsApp failures don’t happen at send time; they arrive later in a status update. When 131026 arrives, ConfirmX re-sends automatically after 15 seconds, 45 seconds, 2 minutes, 15 minutes and 1 hour.

- This applies to messages under 3 hours old.
- It doesn’t include campaign messages.
- You can click Retry now instead of waiting.

## Errors that pause a campaign

ConfirmX pauses a campaign on 131042 (billing), 131048 (quality) or a not-registered error such as 133010, so you don’t spend quality or money on messages that won’t arrive. Unsent recipients go back to pending. After fixing the cause, click Resume.

> Note
>
> The campaign screen shows it is paused without the reason. You’ll find the reason in the recipients’ error column and on the WhatsApp Accounts page.

## What retries and what doesn’t

- **Retried at send time**: service, network and rate-limit problems.
- **Not retried**: templates, the window, billing, quality and withheld marketing messages, because retrying wouldn’t change anything.

## Questions

### Why does a message show as sent and then fail?

Meta accepts the request first, then reports the delivery result in a separate update.

### Can I re-send a 131049 message?

Not right away. Meta withheld it on purpose. If it is about an order, use a Utility template.

### Does 133010 mean the token expired?

No. The number lost its Cloud API registration, and refreshing the token won’t fix it.

## Read next

- [WhatsApp’s 24-hour rule: when you can reply freely and when you need a template](https://confirmx.net/en/guides/whatsapp-24-hour-window/)
- [How to set up WhatsApp order confirmation, step by step](https://confirmx.net/en/guides/whatsapp-order-confirmation-setup/)