WhatsApp & Meta error directory
Meta speaks in error codes. This directory turns the common ones into plain language: what the message means, whether it is something you fix or we fix, and the exact next step. Find your error below, or open a full guide where one exists.
The two kinds of error
Almost every WhatsApp error a HabariChat user sees falls into one of two groups. Knowing which group you are in tells you where to look:
- Connection errors (Embedded Signup). These appear while you are connecting a number, inside Meta's secure sign-up popup. They are almost always a setting on your number or business that needs to change first.
- Send-time errors (Cloud API). These appear after you are connected, when a message or campaign cannot be delivered. They point to a token, a template, the 24-hour window, or a recipient.
Connection errors (Embedded Signup)
You see these as you connect a WhatsApp number to HabariChat. Start with a dedicated guide if there is one for your message.
Auto labels / automatic events
"Your phone number is already linked to automatic events." Turn off Auto labels, then reconnect.
All Embedded Signup errors
PIN locks, "number already in use", admin rights, display names, verification codes and more.
Keep the number on your phone
Connect through Coexistence so the number stays live in your WhatsApp Business app.
Send-time errors (WhatsApp Cloud API)
These appear after a number is connected, when a reply, notification or campaign cannot go out. Most trace back to one of the codes below. The code is the part in brackets, for example (#131047).
| Code | What it means | What to do |
|---|---|---|
#131047 | Re-engagement message. More than 24 hours have passed since the customer's last message, so a plain text reply is not allowed. | Send an approved message template to reopen the chat. Inside the 24-hour window, free-form replies work normally. |
#131026 | Message undeliverable. The recipient cannot receive the message, often a number that is not on WhatsApp or cannot be reached. | Check the number is correct, in full international format, and active on WhatsApp. Remove dead numbers from your contact list. |
#131049 | Meta limited delivery to protect the user experience (per-user marketing frequency). | Reduce how often you message that contact. Make marketing relevant and spaced out so quality stays high. |
#190 | Access token expired or invalid. The link between HabariChat and Meta needs refreshing. | Reconnect the channel from your dashboard. If it keeps happening, message us and we will re-link it. |
#368 / #131031 | The account is temporarily restricted or locked for a policy or quality issue. | Review Meta's policy notice in Business Manager and fix the cause. Contact support if you need help reading it. |
#132000 to #132016 | Template problem: parameters do not match, the template was paused for low quality, or it was disabled or not approved. | Open Message templates, match the variables exactly, and resubmit or pick an approved template. |
#80007 / rate limited | Too many messages in a short time, so Meta is throttling sends. | Slow the send rate. Large campaigns are paced automatically. See Sending limits. |
#131000 / #100 | A generic "something went wrong" or an invalid parameter in the request. | Retry once. If it persists, send us the full message and code so we can trace the request. |
How to read any Meta error
- Read the whole message. Meta usually names the exact setting, template or window, and where to change it.
- Copy the code in brackets. For example
#3441061or#131047. The code is stable and the same for everyone, so it is searchable. - Note the trace ID. The long string after the colon is unique to your attempt. It changes every time and helps us look up your exact session.
- Fix the setting, then retry. Many errors clear on the next attempt once the named setting is corrected.