See at a glance whether every message you send was sent, delivered or seen, and why any message failed.
No more guessing or re-sending: every outbound message in the Inbox now shows its status as soon as it changes.
Message status
Every message you send from the Inbox, whether a basic message or a template, shows a live status on WhatsApp, Facebook Messenger, Instagram and Webchat. The status updates on its own, so there is no need to refresh the page.
| Status | Icon | Meaning |
|---|---|---|
| Sent | Single grey tick | The channel accepted the message. |
| Delivered | Double grey tick | The message reached the customer's device or chat window. |
| Seen | Double blue tick | The customer read the message. |
| Failed | Red X | The message could not be delivered; a reason is attached. Hover over the red X to see it. |
- Status only moves forward. Out-of-order or duplicate webhooks never downgrade a message or change its time.
- Gaps are shown honestly. If a channel cannot confirm a step, it shows "not available", and messages stay at their last truthful status rather than guessing.
- One vocabulary everywhere. A configurable mapping, editable by admins only, turns each channel's own states into Sent, Delivered, Seen and Failed, with localised labels including Arabic.
Error reference
Find the code shown on a failed message below to learn what it means and what to do next. Action buttons for each error are planned for the next phase.
Channel errors (Meta)
| Code | Shown to the agent | Cause | How to avoid |
|---|---|---|---|
| 131047 | Messaging window expired | More than 24 hours have passed since the customer last replied. | Check the window first; outside it, send an approved template. |
| 10-2018278 | Message not sent | Sent outside the allowed messaging window on Messenger or Instagram. | Reply promptly; do not re-engage old conversations via the API. |
| 2534022 | Message not sent | Sent outside the allowed messaging window (same condition as 10-2018278). | Reply promptly; check the window before sending. |
| 10-2018065 | Permission required | Sent outside the window without News Messaging permission. | Stay inside the window. |
| 131049 | Message not delivered | Meta withheld the message to protect user engagement, usually because of the marketing message limit. | Wait at least 24 hours and space out marketing messages. |
| 131056 | Too many messages | Too many messages were sent to the same recipient in a short time. | Rate-limit per recipient, then retry. |
| 131050 | Marketing messages disabled | The customer opted out of marketing messages. | Do not retry; track the user_preferences webhook. |
| 131026 | Message not delivered | The number is not on WhatsApp, the customer has not accepted the terms, or the WhatsApp app is outdated. | Validate numbers and contact the customer another way. |
| 131045 | Phone number not registered | The sending phone number is not registered. | Register the number, then retry. |
| 131031 | WhatsApp account restricted | A policy violation, or the request data did not match (for example, a wrong two-step verification PIN). | Follow Meta policies and check the Health Status API. |
| 368 | WhatsApp account restricted | The account is restricted or disabled for a platform policy violation. | Follow Meta policies and keep message quality high. |
| 130497 | Country restriction | The account is not allowed to message that country. | Check the allowed countries for your business category. |
| 10-1893063 | Messaging restricted | The Page is temporarily restricted because of policy-violating activity. | Follow the Messaging Policies and wait for the restriction to lift. |
| 2388019 | Template limit reached | The limit of 250 templates has been exceeded. | Delete unused templates. |
| 2593107 | Sync limit reached | Sync can run only once per phone number. | Offboard and re-onboard the customer. |
| 132018 | Template validation error | Invalid template parameters. | Send exactly the variables the template defines, with no line breaks, and match the template name and language. |
| 131008 | Missing required parameter | The request omits a required parameter. | Validate the payload against the endpoint reference. |
| 131009 | Invalid parameters | A parameter value is not accepted. | Check the supported values in the endpoint reference. |
| 131062 | BSUID recipient not supported | An authentication template was sent to a BSUID instead of a phone number. | Send to the phone number when it is available. |
| 190-463 | Expired | The login status or token has expired or was revoked. | Reconnect the channel and set up an alert for expiry. |
| 190-467 | Invalid Access Token | The token has expired, was revoked or is otherwise invalid. | Use long-lived tokens and alert early. |
| 551-1545041 | Message not sent | The recipient is unavailable. | Not fixable; skip the contact. |
| 551-1893047 | Message not sent | The recipient is unavailable. | Not fixable; skip the contact. |
| 10903-1893062 | Message not sent | The commenter's privacy settings block private replies. | Not fixable; skip the contact. |
| 130472 | Message not sent | The message was held back as part of a Meta experiment. | Expected behavior; do not retry. |
Platform errors (ERR-*)
Note
ERR-* codes are the platform's own, so their causes are inferred from the message text.
| Code | Shown to the agent | Cause | How to avoid |
|---|---|---|---|
| ERR-A4 | Sending not available | The user's role cannot send templates. | Grant permission or ask an admin to send. |
| ERR-B1 | Bot not found | No bot is linked to the conversation. | Check the bot link; contact support. |
| ERR-B2 | WhatsApp not connected | WhatsApp is not connected for the bot. | Connect it under Channels. |
| ERR-C1 | Template unavailable | The template was removed or is not approved. | Sync templates and choose another. |
| ERR-C2 | Template not supported | The template category is not supported. | Use a supported category. |
| ERR-C3 | Missing information | Required template variables are empty. | Fill in every variable before sending. |
| ERR-C4 | Media required | The template needs media that was not attached. | Attach the media. |
| ERR-D1 | Business messaging disabled | Pay-as-you-go is not enabled for WhatsApp. | Enable it in Billing. |
| ERR-D2 | Insufficient balance | The wallet balance is too low. | Top up and set low-balance alerts. |
| ERR-D3 | Billing unavailable | Billing is temporarily unavailable. | Retry shortly. |
| ERR-D4 | Wallet unavailable | The workspace wallet could not be loaded. | Retry; contact support if it persists. |
| ERR-D5 | Wallet unavailable | The workspace wallet could not be loaded. | Retry; contact support if it persists. |
| ERR-D6 | Billing issue | The billing configuration could not be processed. | Contact support. |
| ERR-D7 | Pricing unavailable | No price is configured for the destination. | Contact support to add pricing. |
| ERR-D8 | Billing issue | The workspace has no valid billing plan. | Subscribe to a plan or fix the existing one. |
| ERR-D9 | WhatsApp limit reached | The plan's WhatsApp message quota is used up. | Upgrade the plan or wait for the quota to reset. |
| ERR-G1 | Billing unavailable | Billing is temporarily unavailable. | Retry shortly. |
| ERR-E1 | Status unavailable | The conversation status could not be confirmed. | Retry or reopen the conversation. |
| ERR-G3 | Message status unknown | It is unknown whether the message was sent. | Check the conversation before resending. |
| ERR-F2 | Billing pending | The message was delivered; billing is pending. | No action needed. |
| ERR-F3 | Usage pending | The message was delivered; usage processing is pending. | No action needed. |
Quick guide for agents and admins
Use this guide to decide your next step.
- Rules: window, marketing-limit and opt-out errors are Meta's rules. Use templates outside the window and respect opt-outs.
- Fix, then retry: registration, template, billing and connection errors.
- Wait, then retry: rate and marketing limits.
- Do not retry: restrictions, opt-outs and unavailable recipients.
- Check before resending when the status is unknown, to avoid duplicates.
Still need help? Contact our support team and share the error code you see.
Comments
0 comments
Please sign in to leave a comment.