Error Code: 100, Subcode: 33
An error occurred posting to Facebook: type: GraphMethodException, code: 100, error_subcode: 33, message: Unsupported post request. Object with ID '[COMMENT ID NUMBER]' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api, x-fb-trace-id: B12/TErD7ak [HTTP 400].
What causes this error?
You're likely receiving this error because the comment you're trying to reply to has been deleted from the post.
How do I fix this?
There is no fix for this since you cannot reply to a deleted comment. To confirm, open the conversation and select the link to view the post on Facebook. If the comment no longer appears on the post, it has been deleted.
Error Code: 551, Subcode: 1545041
An error occurred posting to Facebook: type: OAuthException, code: 551, error_subcode: 1545041, message: (#551) This person isn't available right now, x-fb-trace-id: BD8bLj0X0/I [HTTP 400].
What causes this error?
This error can indicate several things. The recipient may have closed your chat or blocked your page. It is also possible that the recipient has restrictive permissions on their Facebook Messenger settings that prevent third-party apps from sending them messages.
How do I fix this?
You will need to respond to the user directly through Facebook Messenger. There will be a link at the top of the conversation that allows you to access it from the Messenger inbox.
Error Code: 10, Subcode: 2018278
An error occurred posting to Facebook: type: OAuthException, code: 10, error_subcode: 2018278, message: (#10) This message is sent outside of allowed window. Learn more about the new policy here: [https://developers.facebook.com/docs/messenger-platform/policy-overview](https://developers.facebook.com/docs/messenger-platform/policy-overview), x-fb-trace-id: Cgkpcs2GM2y [HTTP 400].
What causes this error?
Facebook only allows you to respond to a customer within 24 hours of their initial message. Re:amaze has a workaround that tags your response as an Account Update to allow it through. However, if other apps connected to your page such as Recart or ManyChat have abused the Account Update tag, Facebook may block your page from using it, which affects Re:amaze and all other third-party apps that rely on it.
How do I fix this?
Check whether 24 hours have passed since the customer's initial message. You can try replying directly through Facebook Messenger using the link at the top of the conversation. In most cases, this error resolves on its own after some time has passed.
Error Code: 2022
An error occurred posting to Facebook: type: OAuthException, code: 2022, message: (#2022) You have been temporarily blocked from performing this action., x-fb-trace-id: GTzBKWk2SXQ [HTTP 400].
What causes this error?
Facebook limits outbound sending through third-party apps and will temporarily throttle your page if it detects excessive activity. This is commonly caused by third-party tools such as ManyChat or Recart sending large volumes of marketing material. When this happens, it affects all third-party apps connected to your page, including Re:amaze.
How do I fix this?
You will need to respond to users directly through Facebook Messenger while the throttle is active, or wait for it to end before responding through Re:amaze. To respond through Messenger, use the link at the top of the conversation to access it from the Messenger inbox.
Error Code: 10, Subcode: 2018336
An error occurred posting to Facebook: type: OAuthException, code: 10, error_subcode: 2018336, message: (#10) *This action is not permitted due to new data privacy regulation in Europe. Please review the developer documentation for more info*, x-fb-trace-id: F2zfjmxt6JB [HTTP 400].
What causes this error?
Starting December 21, 2020, Facebook began disabling certain capabilities in the EEA to comply with the ePrivacy directive. This affects the Personas feature, which allows you to reply to Facebook Messenger messages using your own Re:amaze identity, and also prevents you from including attachments in responses.
- https://www.bbc.com/news/technology-55350795
- https://developers.facebook.com/docs/messenger-platform/europe-updates
How do I fix this?
First, check that your response does not include any attachments. If it does, remove the attachment and include a URL to the file instead.
If attachments are not the issue, check your Facebook Messenger channel settings to confirm that Personas is disabled. You can access your social channel settings from Settings > Channel Settings > Social Channels.
Error Code: 190, Subcode: 460
An error occurred posting to Facebook: type: OAuthException, code: 190, error_subcode: 460, message: Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons., x-fb-trace-id: Eihnec0vEYO [HTTP 400]. Please try again or contact support. rmz-trace-id: 801b3746-aea8-41b6-9e97-612f4a234d2e
What causes this error?
Your Facebook password was changed, which invalidated Facebook's token and disconnected the account from Re:amaze.
How do I fix this?
You will need to reconnect your Facebook account. Before doing so, make sure that:
- You are a full admin on the associated Facebook page.
- You have given Re:amaze full permission to view all pages and all permissions.
Check out this article for step-by-step instructions.
Error Code: 200, Subcode: 2424008
An error occured posting to Facebook: type: OAuthException, code: 200, error_subcode: 2424008, message: Permissions error, error_user_title: Page Publishing Authorization is Required, error_user_msg: Access to your Pages is temporarily restricted until you complete Publishing Authorization., x-fb-trace-id: DMvvPiYaXxx [HTTP 400].
What causes this error?
Facebook is requiring you to complete Publishing Authorization before you can leave a comment. Pages with large audiences may be asked to confirm their identity and secure their account through Facebook's Page Publishing Authorization process.
How do I fix this?
You will need to go through the Page Publishing Authorization process before you're able to reply to customers. You can follow Facebook's instructions here: https://www.facebook.com/help/1939753742723975
What went wrong? (Optional)