Facebook Errors While Publishing

If you're facing an error while publishing to Facebook, please find the most frequent errors below with their solution:

Error 1:

Your access token has expired or has been invalidated

Solution:

This error usually results when we have lost your profile connection and need you to reconnect it to ContentStudio. Most social networks need you to re-authorize applications from third parties (like ContentStudio) every 2-3 months or so, to make sure you can use them to publish them on your profile.

This can also happen if you have changed your account password.

Here's what to do:

🔧 Try reconnecting your social network to renew token - accept all permissions, sign in, and once renewed, try to publish again.

Note: You must be an Admin of the page/group to be able to reconnect it. 

Error 2:

OAuthException: (#32) Page request limited reached (code 32, subcode null)

Solution:

OAuthException: Invalid parameter (code 100, subcode 2061006)

Solution:

🔧 Mostly, this occurs when a URL is not in the right format. Please check the field where the URL link is pasted and correct the URL. Give it another try.

Error 4:

OAuthException: Invalid parameter (code 100, subcode 1349125)

Solution:

This error appears when the image that you're trying to upload is either corrupted or in a format that we do not support. 

🔧 Make sure the image is either JPG, PNG, and is not more than 4 MB. Also, ascertain that your file is not corrupted. 

And if you have downloaded the image from another website, make sure the download is complete before uploading it! 

Error 5:

It looks like you were misusing this feature by going too fast. You've been blocked from using it. Learn more about blocks in the Help Center. (code 368, subcode 1390008)

Solution:

🔧 Please refrain from posting "spam" or identical pictures. Facebook blocks the content and the page both. 

Error 6:

Your message couldn't be sent because it includes content that other people on Facebook have reported as abusive. (code 368, subcode 1346003)

Solution:

This error pretty much sums it up! Facebook users have reported the material as being offensive, and it could not be posted. Please refrain from publishing that would violate their ToS. 

🔧 Here's what to do:

• If your content wasn't offensive and you think it was a mistake, you might want to try to get in touch with Facebook and submit a manual review. Facebook Support team will determine if it complies with their ToS.  
• Make sure your content is compliant with the platform's regulations.
• You can wait for a while. This block can be temporary and sometimes all you need to do is wait for it to pass so you can publish your post again.

Alternatively:

If you are sharing content to Facebook with a URL shortener, your URL shortener may be blacklisted by Facebook.

To solve this, you will have to:

• Reach out to Facebook support to whitelist your URL shortener.
• If it is a URL without shortened, the domain must have been blacklisted by Facebook. The owner of a website will have to reach out to Facebook to whitelist their URL.

You can use your own branded URL shortener by using Replug which comes with a custom domain feature and have one-click integration with ContentStudio.

Error 7:

Please reduce the amount of data you're asking for, then retry your request (code 1, subcode null)

Solution:

This is a known Facebook API bug! It can happen to inactive pages when they attempt to publish "heavy" posts that include too much text, link. image and tags etc.). First of all, you should check your Facebook Page to see if the post was published or not, and take action accordingly.

🔧 This might help:

• Take out other sections of content (image, URL) and try to publish again.
• Try posting natively on Facebook.com, or scheduling the post and adding the Page mention by hand afterward

Error 8:

OAuthException: An unexpected error has occurred. Please retry your request later. (code 2, subcode null)

Solution:

We don't really know the trigger; however since there is an unintended error, it can only mean something temporary. 

🔧Here's what to do:

• Firstly, check whether the post was actually published on the Facebook page, or not - although the initial attempt was unsuccessful, this could happen that the post is actually published a minute later. 
• Secondly, if the post has not already been written, try scheduling and publishing it for a later time.

Error 9:

OAuthException: Service temporarily unavailable (code 2, subcode 1609010)

Solution:

This means Communication via Facebook API was temporarily inaccessible, so at that time we were unable to process the publishing operation. 

🔧You can try to:

• Check whether the post was actually published on the Facebook page, or not - although the initial attempt was unsuccessful, this could happen that the post is actually published a minute later. 
• Try scheduling and publishing it for a later time.

Error 10:

An unknown error occurred

Solution:

If you are getting this error, then the issue most likely is that your Facebook page access token does not have enough permission to publish content. Sometimes, your posts are published, but few times they are failed. 

🔧 If you are facing this issue, what you need to do is:

• Reconnect your pages and make sure you have given all of the permissions while connecting your Facebook Page.
• Follow this guideline to reauthorize the ContentStudio application.
• If it still doesn't work, please try to publish it again later.

Error 11:

#200 Insufficient permission to post to group (code 200, subcode null)

Solution:

This usually occurs when a person who makes a post or tries to upload it to a Facebook Group lacks the permissions to do so.

You may not have done all the needed settings to be able to post. 

🔧 If you haven't already, please:

• Make sure you are an admin. 
• Reauthorize app.
• Add the ContentStudio App to your Facebook Group. Click here to learn how
• Log in again, and make sure you have enabled all the permissions. 
• Try re-publishing.

Error 12:

Permissions error (code 200, subcode 1609008)

Solution:

This happens when you're trying to publish a Facebook link in your post. 

🔧  Refrain from publishing facebook.com links!

Error 13:

Error validating access token: The user is enrolled in a blocking, logged-in checkpoint (code 190, subcode 490)

Solution:

• Clear the cookies & cache 
• Sign in to your Facebook profile and reauthorize access.
• Respond to security questions at the checkpoint, when prompted

Error 14:

The user must be an administrator, editor, or moderator of the page in order to impersonate it. If the page business requires Two Factor Authentication, the user also needs to enable Two Factor Authentication

Solution:

If the business page that you are managing have enabled two-factor authentication, you need to enable the Two-factor authentication on your account level. After that, please reconnect your account and you will not be facing this error.

Error 15:

The 'manage_pages' permission must be granted before impersonating a user's page.

Solution:

If you are publishing content to your client's social media pages and they have added you as an administrator, in such case, you will be getting this error.

🔧 Make sure, you have the administration access to those social media pages and while connecting the account, you allow the manage_permissions to the Groups/Pages section so your post publishes without any issues.

Error 16:

The url you supplied is invalid or This link could not be posted

Solution:

When we publish a message that includes a link to the message, Facebook takes a look at this link and indexes it. When Facebook servers are overloaded they can’t index it during the request time. Facebook throws one of the errors mentioned above. Facebook still indexes the link, so the second try couple minutes later usually goes without any problems.

Right now, we have not added the Retry attempt if this certain problem appears but we will be adding this soon. 

🔧 Meanwhile, you can republish the same content to your social channel.

Error 17:

contentstudio.page.link Your content couldn't be shared, because this link goes against our Community Standards (code 368, subcode 1404102)

Solution:

If you are sharing content to Facebook with a URL shortener, your URL shortener must be blacklisted by Facebook.

1. To solve this, you will have to reach out to the Facebook support to whitelist your URL shortener.
2. If it is a URL without shortened, the domain must have been blacklisted by Facebook. The owner of a website will have to reach out to Facebook to whitelist their URL.

Error 18:

Missing or invalid image file (code 324, subcode 2069019)

Solution:

Error 19:

The user has not authorized application

Error 20:

Facebook error: (#120) invalid album id

Solution:

It appears that Facebook Group posts are failing with either this error or the "Unsupported request - method type: post" error. According to our Tech Team, both errors are caused by a bug in the Facebook API. It is not just Contentstudio that is experiencing these errors, many others have as well, and Facebook is looking into it.

You can find the bug report here: https://developers.facebook.com/support/bugs/355025889408144/?join_id=f2a668b38105e4

Here is what we have found so far:

We have found that Facebook tries to detect question-like posts (whether they contain a question mark, character/emoji that looks like a question mark, or wording like "Why" or "Is this" or "Are you").

It seems they will return an error if they determine the Group post is a question:

• We receive the "(#120) Invalid album id" error response if the post contains an image.

• We get an "Unsupported request - method type: post" error if there is no image (text only, or text + link preview).

The post text is still published in both cases (so image posts will be published without the image, but link previews will appear).

A Possible Solution:

• Your post text should be edited so there are no question marks or anything that looks like a question - you may have to experiment to find out what Facebook allows and what they reject.
• Publish your post without using a question mark "?" as well. If that does not work, you could replace it with an interrobang "‽" (the only question mark-like symbol that appears to work right now). However, the wording is equally important.