WhatsApp error 131049 — Healthy ecosystem engagement / message not delivered
Meta message: “This message was not delivered to maintain healthy ecosystem engagement.”
Why it happens
- The user already received many marketing messages (from you or other businesses) recently
- Low engagement with your earlier messages: not read, not replied
- Users blocked or reported your messages
- The user did not clearly opt in
How to fix it
- Send marketing templates only to users who opted in
- Reduce how often you send marketing messages to the same user
- Personalise the content and make the offer relevant
- Use a Utility template for genuine updates (orders, bookings, payments) - never for promotions
- Wait before retrying the same user; an immediate retry usually fails again
Prevention: Keep your quality rating high and do not repeat the same promotion.
On SMSGatewayHub: Collect consent with opt-in contact groups (join keyword or opt-in link) and reach users Meta did not deliver to through automatic SMS or RCS fallback.
WhatsApp error 131050 — User stopped marketing messages
Meta message: “Unable to deliver the message. This recipient has chosen to stop receiving marketing messages on WhatsApp from your business.”
Why it happens
- The user tapped Stop / turned off marketing messages from your business in WhatsApp
How to fix it
- Do not resend marketing templates to this number
- You can still send Utility and Authentication templates when they are genuinely transactional
- Offer another channel (SMS) only where the user has consented
Prevention: Respect opt-outs and keep promotions relevant so users do not switch them off.
On SMSGatewayHub: Retargeting on SMSGatewayHub skips 131050 numbers automatically, and STOP replies are added to your opt-out list.
WhatsApp error 131026 — Message undeliverable
Meta message: “Message could not be delivered to the recipient.”
Why it happens
- The number is not on WhatsApp
- The user is on an old WhatsApp version
- The user has not accepted the latest WhatsApp terms
- The user blocked your business
- The number format is wrong
How to fix it
- Send to the full international number: country code + number, digits only (for India: 919876543210)
- Remove spaces, dashes, brackets and a leading 0
- Ask the user to update WhatsApp
- Use SMS for numbers that are not on WhatsApp
Prevention: Validate numbers before a campaign and remove numbers that fail repeatedly.
On SMSGatewayHub: Campaign uploads clean and de-duplicate numbers; failed numbers can get the message by SMS or RCS fallback, and retargeting skips 131026 numbers.
WhatsApp error 131047 — Re-engagement message (24-hour window closed)
Meta message: “More than 24 hours have passed since the recipient last replied to the sender number.”
Why it happens
- You sent a free-form (session) message after the 24-hour customer service window closed
How to fix it
- Send an approved template message instead
- When the customer replies, the 24-hour window opens again and free-form replies work
Prevention: Outside the 24-hour window always use approved templates.
On SMSGatewayHub: The team inbox shows whether the reply window is open and offers a "Send template" button when it is closed.
WhatsApp error 131048 — Spam rate limit hit
Meta message: “Message failed to send because there are restrictions on how many messages can be sent from this phone number.”
Why it happens
- Many of your earlier messages were blocked or reported as spam
- Low quality rating on the phone number
How to fix it
- Pause bulk sending and review recent templates and audiences
- Send only to opted-in users and reduce promotional volume
- Send useful, expected content
Prevention: Watch your quality rating in WhatsApp Manager and act when it turns yellow.
WhatsApp error 131056 — Pair rate limit hit
Meta message: “Too many messages sent from the sender phone number to the same recipient phone number in a short period of time.”
Why it happens
- Several messages to the same user within seconds, often from loops or repeated retries
How to fix it
- Wait before sending to the same user again
- Combine information into one message
- Fix retry loops in your integration
Prevention: Add a delay between messages to the same customer.
WhatsApp error 130429 — Rate limit hit (throughput)
Meta message: “Cloud API message throughput has been reached.”
Why it happens
- Your app sent more messages per second than the phone number allows
How to fix it
- Slow down and queue messages
- Retry failed messages with a back-off delay
- Spread large campaigns over time
Prevention: Follow Meta throughput limits; they grow with your messaging tier and quality.
On SMSGatewayHub: Campaigns are queued and sent at a safe speed; 429 responses are retried automatically.
WhatsApp error 131051 — Unsupported message type
Meta message: “Unsupported message type.”
Why it happens
- The message type is not supported (for example sending a type the API does not accept, or the user sent one the API cannot receive)
How to fix it
- Use a supported type: text, image, video, audio, document, sticker, location, contacts, interactive or template
Prevention: Check the type field in your API request.
WhatsApp error 132000 — Template parameter count mismatch
Meta message: “Number of parameters does not match the expected number of params.”
Why it happens
- The template has variables such as {{1}} and {{2}} but your request sent a different number of values
How to fix it
- Send exactly as many values as the template has variables
- Send them in the right order ({{1}}, {{2}}, ...)
- Do not leave any value empty
Prevention: Keep a copy of each approved template's variable list in your integration.
On SMSGatewayHub: Campaign uploads check every row and tell you which row is missing a value before anything is sent.
WhatsApp error 132001 — Template does not exist
Meta message: “Template name does not exist in the translation.”
Why it happens
- Wrong template name
- The language code in the request is not the language the template was approved in
- The template is not approved yet, or was deleted
How to fix it
- Use the exact template name (lowercase with underscores)
- Send the same language code the template was created with - for example en if it was created as English, en_US if it was created as English (US)
- Check the template status is Approved
Prevention: Sync templates before a campaign so you only pick approved ones.
On SMSGatewayHub: Only approved templates are offered in Send, Campaigns and the API template list.
WhatsApp error 132005 — Template hydrated text too long
Meta message: “Translated text too long.”
Why it happens
- After filling in the variables, the message is longer than Meta allows
How to fix it
- Shorten variable values
- Use short or tracked links instead of long URLs
- Move long details to a link or document
Prevention: Keep variable values short.
On SMSGatewayHub: Click-tracked short links keep URLs short and show who clicked.
WhatsApp error 132007 — Template format character policy violated
Meta message: “Template content violates a WhatsApp policy.”
Why it happens
- Spam-like or misleading content
- Restricted products or services
- Formatting that breaks Meta rules
How to fix it
- Edit the content and remove misleading or spammy wording
- Check the WhatsApp Business and Commerce policies
- Re-submit the template for review
Prevention: Write clear, honest templates.
WhatsApp error 132012 — Template parameter format mismatch
Meta message: “Variable parameter values formatted incorrectly.”
Why it happens
- The value type does not match the template, for example text where the header expects an image, or the wrong document type
How to fix it
- Send the parameter type the template expects (text, currency, date-time, image, video, document)
- Check the media link is public and of the right type
- Validate your JSON structure
Prevention: Test each template once before using it in bulk.
WhatsApp error 132015 — Template is paused
Meta message: “Template is paused due to low quality so it cannot be sent in a template message.”
Why it happens
- Users blocked or reported messages sent with this template
- Low engagement
How to fix it
- Improve the content and audience
- Reduce frequency
- Create a new, better template if needed
Prevention: Monitor template quality after every large campaign.
WhatsApp error 132016 — Template is disabled
Meta message: “Template has been paused too many times due to low quality and is now permanently disabled.”
Why it happens
- Repeated low-quality pauses
How to fix it
- Create a fresh template with improved content
- Send only to engaged, opted-in users
Prevention: Fix the cause of the first pause before sending again.
WhatsApp error 131008 — Required parameter is missing
Meta message: “The request is missing a required parameter.”
Why it happens
- A required field such as to, type or template name is missing in the API request
How to fix it
- Compare your request with the API reference and add the missing field
Prevention: Validate requests before sending.
WhatsApp error 131009 — Parameter value is not valid
Meta message: “One or more parameter values are invalid.”
Why it happens
- A value is in the wrong format, for example a bad phone number, language code or media ID
How to fix it
- Check each value against the API reference
- Use E.164 numbers without + or spaces in the to field when in doubt
Prevention: Log the full error details to see which parameter failed.
WhatsApp error 131052 — Media download error
Meta message: “Unable to download the media sent by the user.”
Why it happens
- The media the customer sent could not be downloaded (expired or unavailable)
How to fix it
- Ask the customer to send the file again
Prevention: Download incoming media soon after you receive the webhook.
WhatsApp error 131053 — Media upload error
Meta message: “Unable to upload the media used in the message.”
Why it happens
- Unsupported file type
- File too large
- The media link is not public or the file is corrupt
How to fix it
- Use supported formats (JPG/PNG images up to 5 MB, MP4 video up to 16 MB, PDF and Office documents up to 100 MB)
- Make sure the link opens publicly over https
- Re-upload the file
Prevention: Test media links in a browser before sending.
On SMSGatewayHub: Uploads in the panel check type, size and file content, and give a public https link.
WhatsApp error 190 — Access token expired or invalid
Meta message: “Invalid OAuth access token.”
Why it happens
- A temporary token expired or the token was revoked
How to fix it
- Use a permanent system-user token
- Update the token in your integration
Prevention: Never use temporary test tokens in production.
On SMSGatewayHub: On SMSGatewayHub the WhatsApp tokens are managed for you; you only use your SMSGatewayHub API key.
WhatsApp error 100 — Invalid parameter
Meta message: “Invalid parameter.”
Why it happens
- The request JSON or a field is not in the expected format
How to fix it
- Validate the JSON
- Check parameter names and structure
- Verify the template components
Prevention: Use a tested request sample.
WhatsApp error 368 — Temporarily blocked for policy violations
Meta message: “The WhatsApp Business Account is restricted or disabled for violating a platform policy.”
Why it happens
- Your account violated a WhatsApp Business or Commerce policy
How to fix it
- Check Account Quality in Meta Business Manager
- Stop the activity that caused the violation
- Submit an appeal if you believe it is a mistake
Prevention: Follow Meta policies and keep opt-ins.
WhatsApp error 131031 — Account has been locked
Meta message: “The business account has been locked.”
Why it happens
- Policy violation, or the data in the request could not be verified (for example the two-step verification PIN)
How to fix it
- Check Account Quality in Meta Business Manager
- Request a review
- Contact support with the request ID
Prevention: Keep two-step verification details safe.
WhatsApp error 131042 — Business eligibility payment issue
Meta message: “There was an error related to your payment method.”
Why it happens
- No valid payment method on the WhatsApp Business Account
- Card declined or international payments disabled
How to fix it
- Add a valid card in Meta Business Manager > Billing
- Enable international transactions on the card
- Re-check the billing details and currency
Prevention: Keep a backup payment method.
WhatsApp error 133010 — Phone number not registered
Meta message: “The phone number is not registered on the WhatsApp Business Platform.”
Why it happens
- The business number was never registered on the Cloud API, or registration failed
How to fix it
- Register the phone number (with its two-step verification PIN)
- Check the number status in WhatsApp Manager
Prevention: Confirm registration after connecting a new number.
On SMSGatewayHub: Numbers connected through SMSGatewayHub are registered for you during set-up.
WhatsApp error 131000 — Something went wrong
Meta message: “Message failed to send because of an unknown error.”
Why it happens
- A temporary problem on the WhatsApp side
How to fix it
- Retry after a short delay
- If it keeps failing, contact support with the message ID
Prevention: Retry with back-off.