WhatsApp error code reference

When a WhatsApp message fails, Meta returns a numeric error code. Nexor surfaces this code in the lead timeline, health checks, and API responses. Use the table below to identify the cause and take the right action.

You can manage your WhatsApp configuration directly in Meta Business Manager:

Code	What it means	What to do
130472	Meta applied an experimental sending restriction.	Pause the affected send. Try an appropriate alternative such as a Utility message when it genuinely is operational. Do not reclassify promotions as Utility.
130497	The account is not allowed to message users in that country.	Check country restrictions on the Business Portfolio in Meta and enable the destination country.
131000	Meta reported a temporary general error.	Wait a few minutes and retry once. If it continues, save the error code, timestamp, and health check result.
131026	WhatsApp could not deliver the message to this recipient. This is a generic, terminal delivery failure for that lead’s WhatsApp channel.	Nexor marks the lead as unreachable on WhatsApp, cancels pending WhatsApp tasks for that lead, and tries call then email. Only a real inbound message from the lead re-enables WhatsApp. If you see many 131026 errors from the same import, the source data (missing country codes, wrong format) is usually the problem.
131031	The WhatsApp Business Account is locked by Meta.	Check the policy notice in Meta Business Manager and complete whatever Meta requires. Do not keep sending from a locked account.
131032	The WhatsApp Business Account has a restriction.	Check the reason in Meta, pause affected sends, and fix the cause. If the reason is not visible, grant Full Control of the Business Portfolio to your Nexor account manager to help review.
131033	Meta has disabled the WhatsApp Business Account.	Confirm the status in Meta. Prepare a new WhatsApp Business Account with the client. Do not keep sending from a disabled account.
131042	Meta cannot process billing for this message. A payment method is missing, declined, or has an unsettled balance. The message “Currency is not configured” usually means a credit line is not associated with the WABA.	Open Billing and payments in Meta Business Manager, fix the payment method or balance, wait 15 to 30 minutes, and retry with an approved template.
131047	The 24-hour customer service window is closed. Free-form text is not allowed outside this window.	Send an approved template instead. The window reopens when the recipient replies.
131049	Meta blocked a Marketing message to protect recipient engagement. Nexor cannot override this.	Nexor stops retrying Marketing to that lead for 14 days and tries a Utility template if one is available and appropriate. If neither works, the agent falls back to call or email. Review your audience quality if this happens frequently.
132001	The template name does not exist or is not available.	Check the template name, language, and approval status in Meta. Use an approved template that matches exactly.
132012	The message content does not match the approved template format.	Compare text, field order, buttons, and attachments with the approved version. Fill in all required fields.
Subcode 3835016	The account has a restriction on creating new templates.	Check quality and restrictions in Meta, remove unused templates if you reached the limit, and request a review from Meta support.

What Nexor does automatically

When a message fails with a billing error (131042), Nexor does not retry that send on WhatsApp. It keeps the lead’s cadence active and attempts call or email when applicable. If three distinct leads fail within ten minutes on the same number, Nexor flags a billing incident for that WABA.
When a Marketing message is blocked (131049), Nexor stops Marketing attempts to that lead for 14 days. If a Utility template is available and fits the context, it sends that instead. Per-WABA hourly monitoring reduces send rate at 5% block rate and pauses Marketing for 24 hours at 20% or 10 consecutive blocks.
When delivery fails terminally (131026), Nexor marks the lead unreachable on WhatsApp, cancels WhatsApp-only tasks, and tries the next available channel. Only a real inbound message from the lead re-enables WhatsApp for them.
When Meta blocks a message due to an experiment (130472), Nexor stops Marketing to that specific recipient number and tries Utility if appropriate.

Quick Start

Getting started

WhatsApp

Channels

Agents

Meetings

Integrations

Account

Inbox

API Reference

Leads

Agents

Meetings

Messages

Webhooks

Conversions

Reports

WhatsApp error code reference

What Nexor does automatically

Next steps

Delivery and quality

Troubleshooting

​What Nexor does automatically

​Next steps

Delivery and quality

Troubleshooting

What Nexor does automatically

Next steps