Facebook Channel Common Errors
Error: “Unsupported post request. Cannot be loaded due to
missing permissions, or does not support this operation”
You might see the error message like this:
Unsupported post request. Object with ID '100343472848953' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation of Meta
When you connect the channel to our platform. There is a screen that allows you to give the permission we need. please make sure you select all the permission that is asked on that screen.
Since meta have changed the number of permissions needed, so expect the Facebook page permission, you will also need to connect your Facebook business management in the “Integration” -> E-commerce -> Facebook Business. The solution is to reconnect your Facebook page, and select the page you want to connect, and give all the permissions our platform needs.
Error: “Sending payload: 2534015 (#100) Invalid message data”
According to the meta error code, this error is because the type of data you are sending isn’t allowed for your message type. If you are in an omni channel, you should check the supported channel in every message element. There are social icons like below screenshot:
You can learn more information.
Error: “Sending payload: 1545041 (#551) This person isn't available at the moment”
Either the user generated a lot of errors on our end or the user might block your bot, so the message will not be delivered. Learn more information
Error: “You have been temporarily blocked from performing
this action”
You might see the error message below:
Error sending payload: (#2022) You have been temporarily blocked from performing this action. It means that Facebook has issued a temporary block on your Facebook account. We are unable to send to any account that has been blocked by Facebook. We would advise you to check your Facebook business manager or page alert notification center for more information regarding this issue.
Error: “Hide comment error: (#200) Users can only edit
their own comments published by the same app”
You see this error if you are using the “hide comments” action in the flow. Learn more information.
You can hide most comments on Posts with the following exceptions:
Error: “Connecting different FB pages to different workspaces using 1 FB account”
Users have a few issues where they connect one page to a specific workspace and it disconnects when they add another page to a different workspace.
Possible reason for the error:
Error: “Comment reply error: You've already posted this. Posting the same content repeatedly on Facebook isn't allowed”
you can’t post the same content repeatedly.
You can add a randomizer to send different messages or use OpenAI
to dynamically generate personalized content.
Error: “Message not sent because outside 24 hours”
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. You will see that error message.
For WhatsApp, you will need to send a template message, for Messenger, you will need to send recurring notification or one time notification.
For the Instagram user, you can capture the user’s email or phone number, and you can reach out to the user through email or SMS even they are out of 24-hour window. More information:
Messaging
- Messenger Platform - Documentation - Meta for Developers
Platform
Policy Overview - Messenger Platform - Documentation - Meta for Developers
The solution is to use a condition like the screenshot
below, and make sure you are always reaching the user who interacts with your
chatbot for the past 24 hours, and using different methods to reach out to the
user who are out of the 24-hour interaction window.
Also, you can reach out to the user through email or SMS. You need to make sure the user has opt-in to receive SMS & email messages.
Error: “1893016 Calls to this API have exceeded the rate
limit”
The reason for this is, Facebook has a rate limit that You can only send one opt-in request per week with the same, specific title to a person. This includes the default value of "Updates and promotions".
So, if you are testing the recurring notification request, you might receive the message when it’s first-time trigger, but it might not trigger in the following test.
Also,
These requirements and limitations are subject to change as we are always striving for the best user and business experience. More details.
Error: “I can’t receive recurring notification request
message”
The reason for this is, Facebook has a rate limit that You can only send one opt-in request per week with the same, specific title to a person. This includes the default value of "Updates and promotions".
So, if you are testing the recurring notification request, you might receive the message when it’s first-time trigger, but it might not trigger in the following test.
Also,
These requirements and limitations are subject to change as we are always striving for the best user and business experience. More information.