Active Messages - Error Codes June 06, 2024 12:21 Updated When a shipment fails, it is possible to analyze the details of the failure by downloading a csv file. To do this, simply click on the button Report as shown in the example below: Possible errors are listed below in a table with 3 columns, namely: Error Code: error code — name given to the error Description: brief description of what the error means Suggested Action: Suggested action after receiving the respective error Error Code Description Suggested Action 1 - General Error A general error occurred in Blip You can send the message again 2 - General Timeout A timeout error occurred in Blip You can send the message again 38 — Authorization Max Throughput Rate Reached Maximum message throughput reached You can send the message again when there is no high message load on your chatbot 51 — Dispatch Error General shipping error The destination channel is not available. You can send the message again 81 — Gateway error General gateway processing error General gateway errors, including channel API errors. If the message has a code at the end in square brackets, check the company documents for the error.WhatsApp Business API docs 86 — Gateway operation timed out The gateway operation timed out You can send the message again 100 — Invalid parameter The request included one or more incompatible or incorrectly written parameters. Examine the content of the variables to determine whether it is transmitted with more than four spaces or contains line breaks. 429 — Too Many Requests WhatsApp API response status code does not indicate success You can send the message again after the limit is normalized 1505 — Invalid recipient for channel Invalid recipient for WhatsApp channel You can remove your audience's number because they do not currently have a WhatsApp account 1601 — General broadcast processing error Generic error during campaign transmission processing You can send the message again 1602 — Recipient in attendance When the number is being answered, the active message will not be sent You can send the message again as soon as the recipient's service ends 130472 — user's number is part of an experiment The message was not sent as part of a Meta experiment. You can speak to this number in the following ways: There is a customer service window between the customer and the company; There is an open marketing conversation between the customer and the company; There is an open-ended conversation between the customer and the company. 131026 — Message Undeliverable The message could not be delivered. The reasons may be the following: The recipient's phone number is not registered with WhatsApp. The recipient has not accepted the new Terms of Service and the new Privacy Policy. Marketing Template Message Limits per User. The recipient is using an old version of WhatsApp. You must use the following versions of WhatsApp (or later): Android: 2.21.15.15 SMBA: 2.21.15.15 iOS: 2.21.170.4 SMBI: 2.21.170.4 KaiOS: 2.2130.10 Web: 2.2132.6 Check with the recipient that they have allowed you to contact them via WhatsApp and are using the latest version of the app. 131031 - Account has been locked The WhatsApp Business account associated with the app was restricted or disabled for violating the platform's policy. Consult the documentation WhatsApp Business Platform Policy Monitoring to learn more about policy violations and how to resolve them. 131051 — Unsupported message type The message type is not supported. Consult Messages to see supported message types before trying again. 131052 — Media downloads, error User-uploaded media could not be downloaded. The media could not be downloaded for one or more reasons (for example, an unsupported media type). 131053 — Media upload error The media used in the message could not be loaded. The media could not be loaded for one or more reasons (for example, an unsupported media type) When HTTP status codes are used by the WhatsApp Business API Client, you will see messages in the format below: WhatsApp API response status code does not indicate success: 504 (GatewayTimeout) WhatsApp API response status code does not indicate success: 502 (BadGateway). WhatsApp API response status code does not indicate success: 503 (ServiceUnavailable). For these scenarios, you can try sending the message again later. See the documentation below for more information: Error and status messages Cloud API error codes In rare cases, the status received may be success and failure, if this happens, the message may be considered to have been delivered successfully. This happens because the user is connected to WhatsApp on two devices, so one received the message successfully and the other did not. Read more in the Meta article. If you receive an error that is not mentioned in this article, please contact support Blip For more information, visit the discussion on the subject in our community or the videos on our channel. 😃 Related articles Sending WhatsApp Active Messages on Blip Desk Audience file configuration - Bulk notification sending Doubts about message templates on WhatsApp Managing Access Permissions How to reset users through Beholder?