X/Twitter error library

When using a scheduling tool like Buffer, there will be instances when a social network refuses the post and replies with an error message.

Let’s take action on those! Search the “Error” column below for the error you see, and then troubleshoot with the advice in the “Solutions” column on the right.

Error Reason for error message Solution
"It looks like this post may have been shared recently. Check out our guide to repeating posts in the FAQs."

X/Twitter has detected this post is a duplicate.

X/Twitter has a strict policy when it comes to repeatedly posting identical or nearly identical posts.

To check for duplication, X/Twitter compares the text of any new post with your recent posts before it gets published.

Please edit the copy of the post, then retry the failed post. Change keywords in the caption and ensure any duplicate posts are well spaced out over time.
"The daily posting limit for this channel has been reached! Please try reducing the amount of times per day in your schedule and try again later."

This error indicates you’ve hit X/Twitter’s daily posting limit.

X/Twitter allows you to post 2,4000 posts per day. However, the daily limit is monitored and broken down into smaller limits for semi-hourly intervals. X/Twitter also limits the number of direct messages that any account can send, as well the number of follows.

Please slow down posting. Try publishing your post again in a few hours.
"It looks like you may have already reposted this post. Unfortunately, we’re only able to repost once per post. If the post is your own, you can find some tips for re-sharing this post in our FAQs."

X/Twitter has detected you have already reposted this post recently.

X/Twitter has a strict policy when it re-sharing the same content repeatedly and compares the text of any new post with your recent posts before it gets published, to check for duplication.

Please don’t try to re-post the same content repeatedly. Also ensure that you schedule any duplicate posts far apart. 
"Oops, it looks like that X/Twitter profile was locked when we tried to Publish this. Please visit Twitter.com and send a post from their dashboard to unlock your account and then retry the post." This error indicates X/Twitter has temporarily locked your account due to spam activity and we are unable to complete posting on your behalf. Head to X/Twitter and try signing into your account to understand why it was temporarily locked. Follow any instructions provided by X/Twitter. Once your account is unlocked, please refresh your X/Twitter channel in Buffer and resume posting.
"So sorry, it looks like this X/Twitter account has been suspended. It might be worth getting in touch with X/Twitter." This error indicates X/Twitter has suspended access to your account and we are unable to complete posting on your behalf.

Head to X/Twitter and try signing into your account to understand why it was suspended. Follow any instructions provided by X/Twitter. Once your account is restored, please refresh your X/Twitter channel in Buffer and resume posting.

Sometimes X/Twitter can suspend an account by mistake. To fix this, you’ll need to file an appeal with X/Twitter here.

"We can't complete this request because this link has been identified by X/Twitter or our partners as being potentially harmful." The post contains a link that X/Twitter has blocked

Edit the post and remove the link in order to publish it.

You can read more about X/Twitter's approach to blocking links here, which covers the categories of links that they're likely to block (e.g. malicious links that could steal personal information, spammy links that mislead people or disrupt their experience, hateful conduct, etc). If you believe the link has been blocked by X/Twitter in error, you can report it to them via this form.


📝 Seeing a different error on your post? Feel free to get in touch via hello@buffer.com and let us know the error message you see--we'll be happy to help! 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Get in touch Get in touch