When connecting and operating Botcake chatbot(especially Automation features), sometimes you will encounter some errors that make the bot not reply. We have provided a list of common error codes to help you understand the situation and the reason for the error. Then, you can take appropriate action to operate the chatbot channel effectively.
Last updated
| No. | Error Code | Reason | Solution |
|---|---|---|---|
1
#551 This person is not available
Customers blocked the message of the page on Facebook.
Customers blocked your page on Facebook.
Customers' accounts may be restricted by FB (checkpoints)
FB does not send full data to Webhook
You have not installed Pancake V2 Extension
Navigate customers to unblock your page, unblock your page's messages on Facebook.
Manually send messages with Pancake or Facebook
Install Pancake V2 Extension
2
#2022 You have been temporarily blocked from performing this action
You have not clicked Refresh permission when sending Broadcast or flows.
Your page is blocked from sending messages.
Please go to your profile picture > click and choose Refresh Permission. If it still doesn't work, check if you have received the notification that the message sending feature is blocked
3
(#10903) This user cant reply to this activity.
Customer has blocked your page on Facebook so you can't send messages from a comment
Can't send messages because the comment is more than 7 days interaction => Facebook doesn't allow
Navigate customers to unblock your page
4
(#1705) There was an error posting to this wall - undefined.
A customer has blocked your page on Facebook, so you can't leave a comment.
Navigate customers to unblock your page
5
(#10900) Activity already replied to
Customers have never sent a message to your page; or this comment has been responded to through comment using Facebook instead of Botcake, then Botcake cannot send messages from this comment to them.
Navigate customers to re-comment so customers can interact directly with the page, then the Botcake can reply with messages
6
(#200) Permissions error
The bot has been stopped so it can't reply, because you may have changed your password or have not logged in to the bot for a long time or there are strange activities on Facebook (checkpoints).
Please go to your profile picture > click and choose Refresh Permission.
7
(#230) Requires pages_messaging permission to manage the object - null.
You don’t have management and access permission to the page, so you can't send messages to customers.
Log out of Facebook → Connect to Facebook (connect / log back in) → in the screen that appears, select Edit settings → select the page that needs to be edited → and grant full permission to use your page.
8
Customers don't have an avatar/name
Expired Access Token
Re-login, after re-login, the next interaction with the customer (customers send messages, you send messages) will update the name and avatar of the customer.
9
(#100) The URL provided is not whitelisted for messenger extension.
The product could not be sent via message because in the advanced messaging settings of the FB page, the domain that is allowed to be accessed in the messenger web view has not been added.
Go to Facebook page settings → Select advanced messaging, navigate to the whitelisted domains → Add domain: https://yourdomain.com
10
(#100) Invalid comment_id parameter.
Because the customer has deleted the comment, Botcake can't inbox from the comment
Can't fix it because the customer deleted the comment
11
Unsupported post request. Object with ID '2812261655522872' does not exist, cannot be loaded due to missing permissions, or does not support this operation.
Because the customer has deleted the comment, Botcake can't reply to the comment
Can't fix it because the customer deleted the comment
12
(#1705) There was an error during posting.
Botcake can't like comments because FB has system error
Error from the FB system, so we have to wait for FB to fix it
13
(#-1) Unexpected internal error.
Botcake can't reply to comments because FB has system error
Error from the FB system, so we have to wait for FB to fix it
