Common Facebook Errors

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 isn't necessarily a fix for this since you cannot reply to a deleted comment. However, you can check whether or not the comment has been deleted. In the conversation, you can click out to view the post on Facebook. If you no longer see the comment displayed on the post, you can confirm that the comment has been deleted and no longer exists.

image

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 mean various things. It can indicate that the recipient has closed your chat or has blocked your page. It could also be possible that the recipient has restrictive permissions on their Facebook Messenger settings that prevents third party responders/apps to send them messages.

How do I fix this?

In cases like this, you'll need to use Facebook Messenger directly to respond to the user. There will be a link at the top of the conversation which will allow you to access the conversation 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 has a restriction where it only allows you to respond to a customer within 24 hours after their initial message. We have a workaround where we tell Facebook that your response is an 'Account Update', and that allows Facebook to let that message through. However, if you have other apps like Recart, ManyChat, and other FB Messaging apps that abuse the 'Account Update' tag, Facebook will then block your Page from using that tag further. This affects Re:amaze, as well as the other third party apps that use the 'Account Update' tag as well.

How do I fix this?

Double check if 24 hours has elapsed since the customer has left their initial message. You can try replying directly through Facebook Messenger. There will be a link at the top of the conversation which will allow you to access the conversation from the Messenger Inbox. From our experience, this error will resolve 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 has limits on outbound sending with third party apps and will temporarily throttle your Page if it detects that this is happening. We usually find this to be true if customers are using third party tools like ManyChat, Recart, etc. that send a lot of marketing/promotional material. Unfortunately, when this happens, it impacts all third party apps connected to your Page, including Re:amaze and prevents you from sending out further messages for a while.

How do I fix this?

In cases like this, you'll need to use Facebook Messenger directly to respond to the user, or you can wait for your temporary throttle to end to respond from Re:amaze. If you would like to respond directly through Messenger, there will be a link at the top of the conversation which will allow you to access the conversation 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 21st, 2020, Facebook has been 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 this also prevents you from including attachments in your response to customers.

You can check out these articles for more info:

How do I fix this?

First you'll want to double check that your response doesn't include any attachments. If you have an attachment in your response, you'll need to remove it. However, instead you can include a URL to view the attachment.
If the attachment isn't the issue, you'll want to check your Facebook Messenger channel settings to ensure you have Personas disabled. You can access your social channel settings from Settings > Channel Settings > Social Channels.

image

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?

You're receiving this error because Facebook is requiring you to complete Publishing Authorization before you can leave a comment. If you manage a Page with a large audience you may be asked to confirm your identity and secure your account through a new 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

If you're not seeing your Facebook error here, feel free to reach out to our support team.

Contact Us

Not finding what you're looking for? Contact Us Directly