WhatsApp Channel Common Errors
Last updated
Was this helpful?
Last updated
Was this helpful?
You might see the error message below:
[{"code":131053,"title":"Media upload error","message":"Media upload error","error_data":{"details":"Sticker file could not be processed. Please choose a different file."}}]
The reason is:
This might be the url you are using in the message or template message isn’t publicly available to access.
Also, this can be the file format you are using are not supported by WhatsApp.
Solution:
We were unable to upload the media for one or more reasons, such as an. Refer to the error.error_data.details value for more information about why we were unable to upload the media.
You can check the URL you are using, and make sure the file url starts with https, and ends with the file format at the end of URL, and also this media file should be always publicly accessible.
If you see this error message, this message can be triggered if you are trying to use “WhatsApp Flow” feature, you will need to check if your meta business manager is verified or not.
For certain feature like WhatsApp Flow, meta requires verified business manager to get access.
The request included one or more unsupported or misspelled parameters.
You might see error message like this:
Error sending payload: 2018047 (#100)
Error sending payload: 2018062 (#100) The URL provided is not on the Messenger Extensions whitelist.
It’s possible that you are using a few user custom field variables, but some of the variables don’t have the value populated.
You can add a conditional check about all the variables you are about to use, and notify the admin if there are any errors.
You can also go to the error logs, and locate the user, and check the value of the variable used in the message, and confirm if all of them have the correct value.
You might see the error message like this:
[{"code":131048,"title":"Message failed to send because there are restrictions on how many messages can be sent from this phone number.This may be because too many previous messages were blocked or flagged as spam.","href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
This may be because too many previous messages were blocked or flagged as spam It’s because you have sent many messages to other users, but many messages were blocked or flagged as spam.
So meta has placed some limitations on your number. You need to maintain a healthy account quality, otherwise, your account or WABA number might get blocked.
You might see the error message like this:
The reason is that you don’t have enough funds to your 360dialog account, you will need to purchase more credit from 360dialog. please go to your 360dialog account, insights & billings and add more credits.
If you see this error, the reason is: Permission is either not granted or has been removed.
When you connect your WhatsApp account, you need to select all the permission required.
You might see the error code:
(#131008) Required parameter is missing Parameter of type text is missing text value
Reason:
The request is missing a required parameter.
Solution:
It’s possible that you are using a few user custom field variables, but some of the variables don’t have the value populated.
You can add a conditional check about all the variables you are about to use, and notify the admin if there are any errors.
You can also go to the error logs, and locate the user, and check the value of the variable used in the message, and confirm if all of them have the correct value.
This means that you have used a WhatsApp template message, but we can’t find this template message from your WhatsApp account.
This might be the user changing the message template or deleted it from the WhatsApp business manager and the changes have not been synced back into the Rapidbott Chatbot.
It looks like your whatsapp business account has been locked by meta. you need to contact meta to get support.
Also, you can go to your WhatsApp manager in the meta business manager for any notifications related to this error.
You might see the error message like this:
[{"code":130472,"title":"Failed to send message because this user's phone number is part of an experiment","href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
Learn more here:
You might see the error message like this:
[{"code":130472,"title":"Failed to send message because this user's phone number is part of an experiment","href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
You might see the error message like this:
[{"code":131047,"title":"Re-engagement message","message":"Re-engagement message","error_data":{"details":"Message failed to send because more than 24 hours have passed since the customer last replied to this number."},"href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
[{"code":470,"href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/api\/errors\/","title":"Message failed to send because more than 24 hours have passed since the customer last replied to this number"}]
This is because it has been more than 24 hours since you last received a user initiated message - the session is closed and you can no longer use free-form messages. Please find a way to restrict message sending if there was no incoming message for the given user/phone number within 24h. Alternatively, you can contact the user using a Template Message.
You might see the error like this:
(#131056) (Business Account, Consumer Account) pair rate limit hit
The reason for this error:
Too many messages sent from the sender phone number to the same recipient phone number in a short period of time.
Solution:
Wait and retry the operation, if you intend to send messages to the same phone number. You can still send messages to a different phone number without waiting
Learn more information here:
You might see the error message like this:
Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons.
Users who connected to WhatsApp have changed their password on their Facebook account. As a security measure Meta logs out all third-party platforms so reconnect once to establish the connection again will resolve the issue
The solution is to reconnect the channel. Because the user might have changed their password, so the previous token is not valid anymore.
You might see the error like this:
[{"code":131048,"title":"Spam Rate limit hit","message":"Spam Rate limit hit","error_data":{"details":"Message failed to send because there are restrictions on how many messages can be sent from this phone number.This may be because too many previous messages were blocked or flagged as spam."},"href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
Reason:
Message failed to send because there are restrictions on how many messages can be sent from this phone number. This may be because too many previous messages were blocked or flagged as spam.
Solution:
You will usually see the error message like this:
[{"code":131026,"title":"Receiver is incapable of receiving this message","message":"Receiver is incapable of receiving this message","error_data":{"details":"Message Undeliverable."}}]
Possible reasons:
Unable to deliver a message. Reasons can include:
· The recipient phone number is not a WhatsApp phone number.
· Recipient has not accepted our new Terms of Service and Privacy Policy.
· Recipient using an old WhatsApp version; must use the following WhatsApp version or greater:
o Android: 2.21.15.15
o SMBA: 2.21.15.15
o iOS: 2.21.170.4
o SMBI: 2.21.170.4
o KaiOS: 2.2130.10
o Web: 2.2132.6
Solution:
Confirm with the recipient that they agree to be contacted by you over WhatsApp and are using the latest version of WhatsApp.
Learn more information:
You might see the error message like this:
[{"code":131047,"title":"Re-engagement message","message":"Re-engagement message","error_data":{"details":"Message failed to send because more than 24 hours have passed since the customer last replied to this number."},"href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
[{"code":470,"href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/api\/errors\/","title":"Message failed to send because more than 24 hours have passed since the customer last replied to this number"}]
This is because it has been more than 24 hours since you last received a user initiated message - the session is closed and you can no longer use free-form messages. Please find a way to restrict message sending if there was no incoming message for the given user/phone number within 24h. Alternatively, you can contact the user using a Template Message.
You might see the error like this:
(#131056) (Business Account, Consumer Account) pair rate limit hit
The reason for this error:
Too many messages sent from the sender phone number to the same recipient phone number in a short period of time.
Solution:
Wait and retry the operation, if you intend to send messages to the same phone number. You can still send messages to a different phone number without waiting
Learn more information here:
You might see the error message like this:
Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons.
Users who connected to WhatsApp have changed their password on their Facebook account. As a security measure Meta logs out all third-party platforms so reconnect once to establish the connection again will resolve the issue
The solution is to reconnect the channel. Because the user might have changed their password, so the previous token is not valid anymore.
You might see the error like this:
[{"code":131048,"title":"Spam Rate limit hit","message":"Spam Rate limit hit","error_data":{"details":"Message failed to send because there are restrictions on how many messages can be sent from this phone number.This may be because too many previous messages were blocked or flagged as spam."},"href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
Reason:
Message failed to send because there are restrictions on how many messages can be sent from this phone number. This may be because too many previous messages were blocked or flagged as spam.
Solution:
You will usually see the error message like this:
[{"code":131026,"title":"Receiver is incapable of receiving this message","message":"Receiver is incapable of receiving this message","error_data":{"details":"Message Undeliverable."}}]
Possible reasons:
Unable to deliver a message. Reasons can include:
· The recipient phone number is not a WhatsApp phone number.
· Recipient has not accepted our new Terms of Service and Privacy Policy.
· Recipient using an old WhatsApp version; must use the following WhatsApp version or greater:
o Android: 2.21.15.15
o SMBA: 2.21.15.15
o iOS: 2.21.170.4
o SMBI: 2.21.170.4
o KaiOS: 2.2130.10
o Web: 2.2132.6
Solution:
Confirm with the recipient that they agree to be contacted by you over WhatsApp and are using the latest version of WhatsApp.
Learn more information:
This error is because the user doesn't give enough permission.
This limit applies to meta channels(Messenger, Instagram, WhatsApp). If the user hasn't engaged with your bot for the past 24 hours.
You can’t reach them directly. For WhatsApp, you will need to send a template message, for Messenger, you will need to send recurring notification or one time notification.
There aren't any good options to reach the Instagram user if they are outside of a 24 hour window.
The error code 131026, Message undeliverable
Possible reasons:
Unable to deliver a message. Reasons can include:
· The recipient phone number is not a WhatsApp phone number.
· Recipient has not accepted our new Terms of Service and Privacy Policy.
· Recipient using an old WhatsApp version; must use the following WhatsApp version or greater:
o Android: 2.21.15.15
o SMBA: 2.21.15.15
o iOS: 2.21.170.4
o SMBI: 2.21.170.4
o KaiOS: 2.2130.10
o Web: 2.2132.6
Solution:
Confirm with the recipient that they agree to be contacted by you over WhatsApp and are using the latest version of WhatsApp.
Learn more information:
Unable to deliver a message. Reasons can include:
· The recipient phone number is not a WhatsApp phone number.
· Recipient has not accepted the new Terms of Service and Privacy Policy.
· Recipient using an old WhatsApp version; must use the following WhatsApp version or greater:
Confirm with the recipient that they agree to be contacted by you over WhatsApp and are using the latest version of WhatsApp.
The full error can be something looks like this:
[{"code":131042,"title":"Message failed to send because there were one or more errors related to your payment method.","href":"https:\/\/developers.facebook.com\/docs\/whatsapp\/cloud-api\/support\/error-codes\/"}]
This error usually happens in Cloud API, WhatsApp channel.
You will need to go to your Facebook business manager, and then WhatsApp manager, and then check if you have any payment issues with your billing. Because meta charge for the WhatApp template message, so you will need to set up the valid credit card in the billing section in your WhatsApp manager.
You might see the error message like this:
(#100) Unexpected key "index" on param "template['components'][0]['parameters'][0]".
Reason:
The request included one or more unsupported or misspelled parameters.
Solution:
This error means the template don’t exist The template does not exist in the specified language or the template has not been approved.
This error arises when a 3rd party storage (Cloudinary, S3 etc) is integrated and a file is shared using a flow without the required permissions resulting in files of certain formats not being delivered to users.
To resolve this, either disconnect your storage integration or enable the settings that allow us to share the files.
Below is an example from cloudinary;
Learn more information here:
The message could not be sent. You do not have enough funds on your conversation prepaid balance to engage in any paid conversation. Please proceed to -> 'Insights & Billing' in order to top up your balance and optionally enable auto-renewal, which will prevent you from running out of funds in the future.
Learn more information here:
Message was not sent as part of an. See.
Message was not sent as part of an. See.
Learn more here:
Check your quality status in the WhatsApp Manager and see the documentation for more information.
Check your quality status in the WhatsApp Manager and see the documentation for more information.
More information here:
See the endpoint's to determine which parameters are supported and how they are spelled.
Ensure when setting the business public key, it is a.
Ensure there is no mismatch between the phone number id you are and a previously stored phone number id.
Make sure your template has been approved and the template name and language locale are correct. Please ensure you follow.
