Twitter Errors While Publishing

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

Error 1:

403:The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following). message - Status is a duplicate. code - 187

Solution:

Twitter says: "For each tweet attempt, the text is compared with the user’s recent tweets. Any attempt that would result in duplication will be blocked, resulting in a 403 error. Therefore, a user cannot submit the same status twice in a row." 

Don't attempt to post repetitive content.

Error 2:

400:The request was invalid. An accompanying error message will explain why. This is the status code will be returned during version 1.0 rate limiting(https://dev.twitter.com/pages/rate-limiting). In API v1.1, a request without authentication is considered invalid and you will get this response. message - Image dimensions must be >= 4x4 and <= 8192x8192 code - 324

Solution:

This error is attributed to the incorrect dimensions of the image - users either attempt to upload excessively large image files (width or height exceeds 8192px), or too small "one-pixel" images ( 1x1px). The picture will vary between 4x4px and 8192x8192px. 

How to fix this? Check the image that you uploaded, and substitute it with an image that has the right dimensions.

Error 3:

This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following). message - Tweet needs to be a bit shorter. code - 186

Solution:

This error usually occurs when the tweet is too long- more than 280 characters. This is not permitted by Twitter. 

Before posting, please check the number of characters. Shorten your message and try again.

Error 4:

403:The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following). message - Error creating status. code - 189

Solution:

This error can occur if non-animated GIFs are added either directly as thumbnails, or if they are attached to the tweet in the URL link. 

Substitute non-animated GIFs or upload animated GIFs with another image format.

Error 5:

403:The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following). message - User is over daily status update limit. code - 185

Solution:

When you hit a limit, we will inform you with an error message about which limit you've crossed.

For Twitter limits that are time-based (like the Direct Messages, Tweets, changes to account email, and API request limits), you'll be able to try again after the time limit has elapsed. The Tweet limit of 2,400 updates per day is further broken down into semi-hourly intervals. If you hit your account update/Tweet limit, please try again in a few hours after the limit period has elapsed.

Error 6:

Duration X.minutes+XX.seconds+XXX.milliseconds exceeds max duration of 2.minutes+20.seconds

Solution

This error happens when you upload a video file which is too long. It is to be noted that the maximum length of video that can be uploaded to Twitter is 140 seconds (2 minutes & 20 seconds). Replace with a shorter clip.

Error 7:

This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following). message - To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account. code - 326

Solution

Twitter automated systems have detected suspicious activity from your account and flagged the content published as spam/malicious, therefore blocked the given Twitter account.   Login to Twitter and unlock the account, or contact Twitter

Your published content has been marked as spam/malicious by Twitter automated systems, thereby, blocking your account. Please login to your Twitter account and attempt to unlock your account by providing verification. If it still doesn't work, contact Twitter, and seek help.

What it means: Twitter has detected some suspicious activity from your account. This could either be because you've suddenly changed your tweeting patterns (jumping from 1 tweet per week to 14 tweets per day, for example) or because users have reported it. 

How to fix it: This is a temporary ban. All you have to do is log into your Twitter account, then come back into SocialBee and reconnect it. 

Error 8:

403:The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following). message - Missing required parameter: status. code - 170

Solution

This error results when the message field contains a blank or an empty tweet (no text, or emoji). 

Please add some content to your tweet, may it be text, image, or an emoji, and try to publish again. 

Error 9:

500:Something is broken. Please post to the group (https://dev.twitter.com/docs/support) so the Twitter team can investigate. message - Internal error code - 131

Solution

An unknown internal error occurred on Twitter's side (no API is flawless). Please try again later.

Error 10:

file is invalid

Solution:

The user has uploaded a video/image file that is not supported. Please upload only supported image/video format:

For Twitter, the optimum would be  16:9 (e.g. 1200 x 675 px).

Error 11:

The list failed validation: A list's name must start with a letter.

Solution

This error results after the user attempts to add a number or symbol at the start of a description to the Twitter list. 

Here's a Twitter rule: The first character of a Twitter list title must always be a letter. While numbers can be included after the first letter, symbols should be avoided.

Error 12:

“Missing or invalid url parameter.”

Solution:

“This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Please try again later.”

Sharing Facebook Image Link to Twitter

If you are resharing the Facebook Images with a link such as "https://scontent.xx.fbcdn.net/v/t1.0-9/s720x720/45285426_2541029032581760_1074713753624248320_n.jpg?_nc_cat=1&_nc_ht=scontent.xx&oh=f3555732d73b4ee10ee34b6787260b82&oe=5C49FDDA"

You need first to download the image to your device, after that re-upload this image to the Social Composer section in ContentStudio and share that content with the social channel.

This will avoid the error that you received in the first place. 

Error 15:

Publishing messages to twitter shows nothing

Solution:

• Nobody has an account with that username.
• The person who previously had that username has since changed it.
• The tweet it led to has been deleted.
• It never leads to a tweet or username at all but is, in fact, a broken link.
• That account has been banned.
• The tweet it led to was reported and removed.
• Disable the browser adds on or removing the cookies will solve the problem.

Error 16:

"This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Please try again later."

Solution:

While sharing the content on Twitter using default rplg.co domain can lead to this message. To avoid this, we'd recommend that you use the Custom Domain option while sharing the content to your social channels.

By using a custom domain has clear benefits:

• Increases brand awareness
• Keeps your brand on links that other people share
• Increase link trust
• Increase click-through rate by up to 34%

Error 17:

Posting Failed! X (Twitter) automation requires a Custom App. This post was created using automation with a Custom App, but switching to the ContentStudio app caused it to fail. Please reconnect this account with Custom App to continue posting

Solution:

You can reconnect your Twitter account with a custom app by following these steps:

• Create a Twitter App:
  • Sign in to Twitter Developer Portal, subscribe, and complete the developer agreement.
  • Create a new Twitter app.
• Set Up Your Twitter App:
  • Configure with “Read and write” permissions and set the callback URL to https://api-prod.contentstudio.io/twitter/connect .
  • Save the OAuth 2.0 Client ID and Client Secret.
• Connect with ContentStudio:
  • Log in to ContentStudio, click “Social Accounts,” and add the Custom App.
  • Enter the API Key and Secret, then paste the Consumer Key and Secret.
  • Confirm the callback URL and complete the authentication.

For more details, read the document here.