Having facebook errors while trying to publish? Here is a possible solution.
If you’re facing an error while publishing to Facebook, Kindly find the most frequent errors with their possible solutions below:
Your access token has expired or has been invalidated
This error usually results when we have lost your profile connection and need you to reconnect it to ContentBurger account. You are advised to authorize your third party applications every 2-3 months in other to ensure successful post publishing on your profile.
This can also happen if you have changed your account password.
Here’s what to do:
- Try reconnecting you social account 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.
OAuthException: (#32) Page request limited reached (code 32, subcode null)
- The API call limit for your page was exceeded. It’s focused on daily active persons (DAP): the higher the DAP on your domain, the higher the level of the rate cap. Once the threshold is reached, Facebook locks the Page and the only way to get this “resolved” is to wait until the Page is unlocked again.
OAuthException: Invalid parameter (code 100, subcode 2061006)
- Mostly, this error occurs when a URL is not in the right format. Kindly check the field where the URL link is pasted and correct the URL. Then give it another try.
OAuthException: Invalid parameter (code 100, subcode 1349125)
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, ensure that your file is not corrupted. If you have downloaded the image from another website, make sure the download is complete before uploading it!
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)
- Please refrain from posting “spam” or identical pictures. Facebook blocks the content and the page both.
Your message couldn't be sent because it includes content that other people on Facebook have reported as abusive. (code 368, subcode 1346003)
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 contents that 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.
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 the 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 ContentBurger.
Please reduce the amount of data you're asking for, then retry your request (code 1, subcode null)
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.
The following steps 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
OAuthException: An unexpected error has occurred. Please retry your request later. (code 2, subcode null)
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.
OAuthException: Service temporarily unavailable (code 2, subcode 1609010)
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.
An unknown error occurred
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.
- If it still doesn’t work, please try to publish it again later.
#200 Insufficient permission to post to group (code 200, subcode null)
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’.
- Kindly reauthorize app.
- Log in again, and make sure you have enable all permission.
- Try re-publishing.
Permissions error (code 200, subcode 1609008)
This happens when you’re trying to publish a Facebook link in your post.
Refrain from publishing facebook.com links!
Error validating access token: The user is enrolled in a blocking, logged-in checkpoint (code 190, subcode 490)
This error might occur when Facebook temporarily flags your account due to security or privacy purposes – this may include suspicious login, objectionable content, breach of terms, etc.
Ultimately, this means your session/access token to Facebook has been expired. This can also happens if you have:
1. Changed your account password.
2. You have not made a post to Facebook in the past 60 days from ContentBurger.
- Clear the cookies & cache
- Sign in to your Facebook profile and reauthorize access.
- Respond to security questions at the checkpoint, when prompted
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
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.
The 'manage_pages' permission must be granted before impersonating a user's page.
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.
Please 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.
The url you supplied is invalid or This link could not be posted
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.
Kindly republish the same content to your social channel.