> For the complete documentation index, see [llms.txt](https://en.help.firstline.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://en.help.firstline.cc/feature/channels/shi-yong-embedded-signup-zheng-he/message-error-codes-and-troubleshooting.md). # Message error codes and troubleshooting Organizes common WhatsApp message sending error codes, possible causes, and suggested fixes to help quickly identify where the problem occurred. When WhatsApp message sending fails, Meta may return an error code. Error codes can usually help determine whether the issue is related to recipient status, message frequency, templates, account restrictions, authorization permissions, or Meta service anomalies. It is recommended to first check the error code in FIRST LINE's message send failure record, then handle it according to the table below. {% hint style="info" %} Error codes and restriction rules may be adjusted by Meta. If the same error keeps occurring, it is recommended to also check [WhatsApp Manager](https://business.facebook.com/wa/manage/home) the phone number and account status, as well as [Meta Status](https://metastatus.com/) whether there is a service anomaly. {% endhint %} ## Common error codes | Error code | Meaning | Recommended action | | ------------------ | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `131026` | Message cannot be delivered | Confirm that the recipient's phone number is indeed using WhatsApp; ask the recipient to update WhatsApp to the latest version, and confirm they can proactively message the business number. | | `131049` | Meta did not send this message based on message interaction quality or marketing message restrictions | Do not immediately resend the same template. It is recommended to wait for a period of time before trying again, and check whether it falls under Meta's marketing message restrictions for a single user. | | `130472` | The recipient is within a specific Meta experiment scope, so the message was not sent | This is usually not a FIRST LINE configuration issue. You can try again later, or contact them through another applicable method. | | `131050` | The recipient has stopped receiving the business's marketing messages | Do not keep resending marketing templates. This user has opted out of receiving this type of message. | | `131048` | Sending frequency or spam restrictions | Go to WhatsApp Manager to check the phone number and template quality. If a large number of messages were recently blocked, reported, or downgraded in quality, Meta may temporarily limit sending volume. | | `130497` | This WhatsApp official account is restricted by country or region messaging limits | Confirm whether the business type and the recipient's location comply with Meta's WhatsApp Business Messaging Policy. | | `131056` | The same business phone number sent too many messages to the same recipient in a short period of time | Pause sending to that recipient and try again later; messages can usually still be sent to other recipients. | | `131000` | Unknown Meta error | Try again once first. If it continues, check Meta Status, then record the time, phone number, and error details to provide to FIRST LINE support. | | `131008` | Missing required parameter | Commonly occurs when template content, variables, or other required data are not fully provided. Please confirm that all variables in the template have actual values. | | `131009` | Invalid parameter content | Check whether the template variables, phone number, button URL, or other submitted content conform to the format required by Meta. | | `131016` | Meta service temporarily unavailable | First check Meta Status. If Meta's service is abnormal, you usually need to wait until the service recovers before sending again. | | `131021` | The sender and recipient are the same phone number | Please use another WhatsApp account for testing; the business number cannot send messages to itself. | | `131037` | The phone number provided by Meta has not yet passed display name approval | Go to WhatsApp Manager to check the display name status of that phone number, and complete the setup or review according to Meta's requirements. | | `131047` | The 24-hour customer service conversation window has been exceeded | When the customer has not replied for more than 24 hours, you cannot directly send a normal free-form message; please use an approved WhatsApp message template to reopen the conversation. | | `132015` | Message template has been paused | Go to WhatsApp Manager to check the quality and status of the template. The template can be sent again only after it returns to an available status. | | `132016` | Message template has been disabled | This template can no longer be used; usually you need to create a new template with different content and wait for Meta approval. | | `132000` | Template parameter count does not match | Check whether the number of template variables sent by FIRST LINE matches the Meta-approved template. | | `132012` | Template parameter format does not match | Check whether the template variable types and content formats, such as text, image, URL, or other fields, conform to the template definition. | | `368` | WhatsApp official account temporarily restricted due to policy issues | Go to WhatsApp Manager or Meta Business Support to check account quality and policy violation notices, then try again after handling them according to Meta's instructions. | | `100` | Incorrect sent parameter | Usually this means the submitted field does not meet Meta API requirements. If it still occurs during normal operation through FIRST LINE, please keep the error details and provide them to FIRST LINE support for investigation. | | `130429` / `80007` | Sending frequency or system rate limit | Pause bulk or repeated sending, try again later, and confirm the current sending limits and quality status of the WhatsApp official account. | | `190` | Authorization has expired, been revoked, or can no longer access WhatsApp assets | Please have the original authorized person, or someone with the same management permissions, complete WhatsApp authorization again. If the Meta account password, business permissions, or security settings were changed recently, please confirm those as well. | | `200` | Missing the permissions required to send messages from the current WhatsApp account | Confirm that the current Meta account still has management permissions for the Business Portfolio and WhatsApp official account; if permissions were adjusted, removed, or the service provider changed, please reauthorize and test again. | ## When sending fails, first check these items ### 1. Confirm the phone number and WhatsApp account status Go to [WhatsApp Manager](https://business.facebook.com/wa/manage/home), confirm: * The phone number in use still exists and is in normal status. * The phone number has completed the necessary verification or registration. * The WhatsApp official account is not restricted. * The sending volume and quality status are not abnormal. ### 2. Confirm whether 24 hours have been exceeded If the customer has not proactively sent a message to the business for more than 24 hours, FIRST LINE cannot directly recontact them using normal text and must use Meta-approved **WhatsApp message template**. Common related error codes:`131047`. ### 3. Confirm the message template is still usable Go to WhatsApp Manager to check the template status. If the template is paused, disabled, or the content format differs from the sent parameters, the message may not be sent. Common related error codes:`132015`、`132016`、`132000`、`132012`、`131008`、`131009`. ### 4. Confirm that all template variables have content If the template includes the customer's name, URL, image, or other dynamic data, confirm that each required field has a value when actually sending. For example, if the template expects the customer's name to be inserted, but the contact has no name data, it may cause message sending failure. ### 5. Confirm that authorization and management permissions are still valid If `190` or `200`appears, it is usually not a problem with the message content itself, but rather that Meta authorization or enterprise asset permissions have expired or are insufficient. Please confirm: * The original authorized person still has management permissions for the company's Business Portfolio. * The Meta account can still manage the currently used WhatsApp official account and phone number. * Whether the Meta account password, business permissions, or WhatsApp asset settings have been changed recently. * If the WhatsApp service provider was changed or the account was reset, whether FIRST LINE authorization needs to be completed again. If you cannot confirm, it is recommended that the original authorized person or someone with the same management permissions reauthorize and then perform a message test. ### 6. Confirm it is not a temporary Meta issue If many customers fail to send at the same time, or the error code is `131000`、`131016`, you can first check [Meta Status](https://metastatus.com/) whether there is currently a WhatsApp Business Platform service anomaly. ## Still can't determine? If the issue still cannot be resolved according to the error code and the methods above, please keep the following information and provide it to FIRST LINE support: * The time the issue occurred. * The WhatsApp phone number used. * The recipient's phone number. * The error code and error message shown by FIRST LINE. * Which WhatsApp message template was used, or whether it was a normal message. * Whether the issue occurred for a single recipient or multiple recipients at the same time. This information can help more quickly determine whether the problem is in FIRST LINE, WhatsApp account settings, message content, or the Meta platform.