WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
When Meta rejects a WhatsApp message, it returns an error code. Omnifox translates it and tells you what happened and what to do, but it helps to know the most common codes: many of them aren't Omnifox or channel failures, they're Meta rules about the customer, the template or the account.
Where you see the error
- In the conversation: the message that didn't go out is marked as failed. Below it you'll see a title, the explanation and the recommended action. If you open the technical details, Meta's code is shown.
- In Settings → Channels: when Meta restricts the whole number (for example, because of a payment issue), the channel card shows the notice with the code.
- In Broadcasts: each failed recipient in a campaign shows its reason.
Code table
| Code | What it means | What to do |
|---|---|---|
| 131026 | Message undeliverable. The number doesn't have WhatsApp, uses a very old version of the app, hasn't accepted WhatsApp's current terms, or can't receive business messages. | Confirm the number with the customer and ask them to update WhatsApp. If nothing changes, reach them on another channel. Retrying won't fix it. |
| 131047 | More than 24 hours have passed since the customer's last message: the customer service window is closed. | Send an approved template. When the customer replies, you can write freely again. |
| 131049 | Meta chose not to deliver the message to protect the user experience: it limits how many marketing messages each person receives. | Don't resend it right away. Wait for the customer to write, or try another day. If the message is truly transactional (a confirmation, a reminder), use a Utility template. |
| 130497 | Your WhatsApp Business account isn't allowed to message users in that country. It's a Meta restriction on the account, not on the message. | Write to us so we can look into it. Meanwhile, reach that customer on another channel. |
| 141006 | Meta couldn't charge the payment method of your WhatsApp Business account. It is not a token issue. New conversations (templates and campaigns) are blocked; replies within the 24-hour window still go out. | Review and update the payment method in Meta Business Suite (WhatsApp Manager → payment settings). If you pay for messages with Omnifox's WhatsApp balance, check that it has funds and write to us. |
| 131042 | Same as above, but seen on a specific message: Meta couldn't process the send because of a payment issue. | Same fix as 141006. |
| 131031 | Meta locked or restricted the WhatsApp Business account. While it lasts, no message goes out. | Go to Meta Business Suite → WhatsApp Manager and check the account's quality and status. There's usually a payment problem (141006) or pending business verification behind it. If you think it's a mistake, appeal from there. |
| 131056 | Too many messages to the same number in a short time. | Wait a few minutes before retrying. Check that no workflow or AI agent is sending bursts of messages to the same person. |
| 132000 | The number of variables sent doesn't match what the template expects. | Fill in every variable (body, header and buttons) before sending. |
| 132001 | The template doesn't exist in that language or isn't approved. | Check the template's name, language and status, and sync your templates from Meta. |
| 132012 | A variable has a format Meta rejects: line breaks, tabs or more than 4 consecutive spaces, or a header with a different file type than the one approved. | Clean up the variable values and use the same header file type (image, video or document) that was approved. |
| 190 | The channel's access token expired or was revoked (for example, someone changed the Facebook password or removed permissions). Every send on the channel fails. | Reconnect the channel in Settings → Channels. Omnifox checks tokens daily and alerts admins before they expire. If all your channels fail at once and you didn't change anything, it may be a Meta outage: wait a few minutes before reconnecting. |
| 368 | Temporary block for violating WhatsApp policies (for example, many user reports or blocks). | Wait for the block to end and check the account quality in WhatsApp Manager. To keep it from happening again, only message contacts who opted in and reduce your marketing volume. |
| 131053 | Meta didn't accept the attachment because of its size or format. | Images up to 5 MB, video and audio up to 16 MB, documents up to 100 MB. Use JPG/PNG, MP4, MP3 or PDF. |
| 131048 | Meta limited your account because of high sending volume (possible spam). | Pause campaigns and check the quality rating in WhatsApp Manager. |
Common problems
- The AI agent replies, but nothing reaches the customer: look at the error on the first failed message. If it's 131031, 141006 or 190, the problem is the account or the channel, not the agent.
- Only customers from one country fail: it's almost always 130497. Write to us.
- Templates fail but replies go out: usually 141006 (payment), or a badly built template (132000, 132001, 132012).
- I can't find the code: open the technical details of the failed message; the number is there. If it's a code that isn't in this table, share it with support.
Related articles
- Troubleshoot WhatsApp connection errors
- Top up your WhatsApp (Meta) balance and understand conversation charges
- WhatsApp access token: what it is and when it expires
- Send a WhatsApp template from a conversation
- WhatsApp template categories (Marketing, Utility, Authentication)
- Sync templates from Meta
Related articles
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.
-
Connect WhatsApp by scanning a QR code
Link your WhatsApp to Omnifox in a minute, just like WhatsApp Web. Great for trying things out: it has caps, no broadcasts and it isn't the official API.