In this article, we will outline common Inbox errors that can occur when replying to users in the Inbox. We will provide context and recommendations for each of these errors, organized by social network.

For other common questions related to the Inbox, please take a look at our Inbox FAQ (Frequently Asked Questions) article.

Facebook

1

Facebook error: (#100) No matching user found (code 100, subcode 2018001) ‘null - null’

Context

This error occurs when a Facebook Page (you) attempts to reply to a Facebook message/conversation that has already been terminated. Facebook conversations initiated in Guest mode can be terminated by the user at any time or terminated automatically after 24 hours. You will not be able to reply to this type of message once it is terminated.

This error can also occur when trying to answer to a DM (Direct Message) received from another Facebook Page.

2

Facebook error: (#10900) Activity already replied to (code 10900, subcode null)

Context

This error occurs when a comment has already been responded to via private message (in private) - directly on Facebook or with another 3rd party tool. You can only respond in private to a comment once.

3

Facebook error: (#10903) This user cant reply to this activity (code 10903, subcode null)

Context

This error occurs when a user's privacy settings prevent others from responding in private to their comments. It is not possible to reply in private to these users.

4

Facebook error: (#2022) You have been temporarily blocked from performing this action. (code 2022, subcode null) 'null - null'

Context/Recommendation

This error happens when a Page's ability to send commerce messages has been temporarily disabled. Facebook does not disclose any details on why it has disabled the Page, nor when the restriction is going to be lifted.We recommend to ensure you are compliant with Messenger Platform Policy and try again later.

5

Unsupported get request. Object with ID '{id}' does not exist, cannot be loaded due to missing permissions, or does not support this operation.

Context/Recommendation

This error occurs when we are unable to submit a comment on your behalf. This can occur if the post has audience restriction that does not allow us to publish the comment.

6

Received Facebook error response of type null: An unknown error occurred (code 1, subcode 99) 'null - null'

Context/Recommendation

This error occurs when there is a temporary issue with the API, usually due to downtime. We recommend to wait and retry the operation later.

7

Facebook error: (#230) Permissions disallow message to user.

Context/Recommendation

This error occurs when you try to send a message to a Facebook user who has certain restrictions in place. More specifically, this user has disabled the Apps Platform. We recommend to reply to the message natively.

8

Facebook error: (#551) This person isn't available right now. (code 551, subcode 1545041) 'null - null

Context/Recommendation

Since Messenger allows users to opt out of conversations, it is possible that the user being replied to has changed their settings/preferences since starting the conversation/or the user has removed the Messenger app. We recommend to try replying natively from Facebook.

Instagram

1

Facebook error: This API call does not support the requested response format (code 20, subcode 1772179) 'Mentions Are Not Allowed by User Settings - Mentions are not allowed per target user's settings - Please remove the invalid mentions.' errorUserTitle=

Context/Recommendation

This error occurs when an Instagram user disables @mentions in their Privacy - Mentions settings. This prevents other accounts from mentioning them in captions, comments, etc. We recommend to leave out the @mention from the comment to post it successfully.

2

Error while publishing a comment on Instagram ad. Received Facebook error response of type OAuthException: This API call does not support the requested response format (code 20, subcode 1772107) 'Instagram Comment Not Added - Your Instagram comment was not added - please try again

Context/Recommendation

This error may indicate that Instagram's automated systems consider your reply as spam (although it might not be). Instagram does not disclose any further information on this (as any details could potentially lead to circumventing the rules). We recommend to try the following:

Avoid using the same reply to multiple comments - it can be considered as an "automated" reply
Avoid using too short of replies, or replies consisting of emojis only
Utilize our Saved replies feature

3

Error while publishing a message on Instagram. Received Facebook error response of type OAuthException: (#100) The thread owner has archived or deleted this conversation, or the thread does not exist. (code 100, subcode 2534001) 'null - null'

Context

This error occurs when you attempt to send an Instagram direct message (DM) in a conversation that was already deleted by “thread owner” (the recipient, i.e. your Business profile).

4

Error while publishing a comment on Instagram ad. Received Facebook error response of type OAuthException: Invalid parameter (code 100, subcode 1772083) 'Ad ID is not associated with Instagram Media - The Ad ID you provided is not associated with Instagram Media you are trying to change.'

Context/Recommendation

This error occurs when an ad has been updated. Each time an ad is updated, all old comments made before this change will not be removable or able to be replied to from any 3rd party tool like Agorapulse. Instagram has not provided us with a way to sync ad comments once ad updates have been made. We will continue to sync new comments that you will be able to reply to or delete until the ad is updated again.

As a workaround, we recommend to open the comment natively and take action there.

5

Error while publishing a comment on Instagram ad. Received Facebook error response of type OAuthException: A user access token is required to request this resource. (code 102, subcode null) 'null - null'

Context/Recommendation

This error can occur when an access token has expired, been revoked, or is otherwise invalid. We recommend to refresh the token by following the steps in the How to manage tokens in Agorapulse article and trying again.

6

Error while publishing a message on Instagram. Received Facebook error response of type OAuthException: An unexpected error has occurred. Please retry your request later. (code 2, subcode null) 'null - null'

Context/Recommendation

This error code does not contain additional information. We recommend retrying this action again later.

7

Due to Instagram API restrictions, it's not possible to reply to this ad comment on Agorapulse. Please reply directly on Instagram.

Context/Recommendation

There are several reasons why you this error may occur when replying to an ad comment, including:

The ad in question is an Instagram dynamic ad (which you are unable to reply to through Agorapulse)
The ad has been updated since it's initial launch
The ad no longer exists on Instagram

We recommend to click the View on Instagram button, which will take you directly to the comment on Instagram where you can reply.

8

OAuthException: This API call does not support the requested response format (code 20, subcode 1772111) 'Create Comment Failed - Spam Detected - To protect the Instagram community, your comment was flagged as spam and could not be added. Please review your comment's content and try again.

Context/Recommendation

Avoid using the same reply to multiple comments - it can be considered as an "automated" reply
Avoid using too short of replies, or replies consisting of emojis only
Utilize our Saved replies feature

Twitter

1

Forbidden

Context

This error occurs when attempting to message a user, but the request is not allowed. This may happen because:

The user is not following you
The user has blocked you

There is no workaround for this error and you will not be able to send message to such a user.