LinkedIn undelivered error messages

Did you run into an error when publishing your post? Here you'll find the most common LinkedIn errors and how you can resolve them.

For any posts that haven’t made it to LinkedIn, check your Undelivered view for error messages in your dashboard by going to Publish > Undelivered

Permissions issues

You do not have permission to post to LinkedIn. Update your LinkedIn Company Page role to Super Admin and then reconnect the profile before trying again.

Explanation: This indicates that you do not have the proper permissions set up on the Company Page.
Solution: Check your permissions on LinkedIn and ensure that it is set to Super Admin.

Connection issues

LinkedIn is experiencing a connection issue. Please reconnect your LinkedIn profile from +Profiles

Explanation: This error can appear when there is an issue with the access token for LinkedIn and the account needs to be reconnected.
Solution: Check out our article, Reconnect a LinkedIn Profile for detailed instructions on how to reconnect your LinkedIn profile, then try re-posting your message from your Undelivered view.

The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.

Explanation: This error will be returned when there is a timeout issue or if a URL was used where the website has various security or sharing limitations in place on the images.
Solution: Try reposting the message after about 5 or 10 minutes.
If the post includes a URL and a link preview is being used, check if the image has a security restriction. In that case, you could edit the link preview by switching to the LinkedIn tab in the Compose Box and choosing the option to replace it with your own image. Check out this article for the steps.

Image/video issues

You cannot post more than 9 images to LinkedIn at once.

Explanation: Due to LinkedIn API restrictions you are unable to post more than 9 images.
Solution: Please remove some images and repost.

The image you have attached exceeds the maximum width and height requirements for LinkedIn. For best results, please select another image that has the accepted width of up to 900px and height of 470px.

Explanation: The image or video does not meet LinkedIn's requirements when posting from an API. These can be different than what is allowed when posting directly on LinkedIn.
Solution: Please see the Image guidelines or Video guidelines for the recommended sizes. Thereafter try re-posting your message from your Undelivered view.

We could not publish your video to LinkedIn. Please try again.

Explanation: The video does not meet LinkedIn's requirements when posting from a third-party platform.
Solution: Please see the Video guidelines to see the recommendations for LinkedIn. Thereafter try re-posting your message from your Undelivered view.

LinkedIn servers are unavailable at the moment. Please wait a few minutes before posting again. If you have an image attached, make sure the file is not corrupted and there's no special characters on the file name.

504 Gateway Timeout

Explanation: This error message is often displayed when LinkedIn is experiencing downtime as you are posting.
Solution: Wait for 5 to 10 minutes before you try re-posting the message from your Undelivered view. If it fails with the same error message, please check downdetector.com for any LinkedIn outages.

LinkedIn unknown media status value

Explanation: The video could be too large, have the wrong height/width, or have an incorrect bitstream. Please verify the details of the video file and try to post again.
Solution: Please see the recommended sizes in the image and video guidelines. Thereafter try re-posting your message from your Undelivered view.

Response status code does not indicate success: 404 (Not Found).

Explanation: This error appears if you are using images from links that are not publicly accessible.
Solution: You must ensure that the links you use have publicly-accessible images.

An invalid request URI was provided. Either the request URI must be an absolute URI or BaseAddress must be set.

Explanation: The image's link does not have the necessary HTTPS prefix.
Solution: To fix this, you need to be able to alter the code on the web page you are linking to. If you have that access, you can add anog:imagemeta data tag to the page and provide an absolute link, including HTTPS.
For example, https://www.sendible.com/hubfs/assets/link%20preview%20images/sendible-insights-blog-feature.png. Or, if you cannot alter the code on the web page, you can edit the link preview. Switch to the LinkedIn tab in the Compose Box and choose to replace it with another image. Viewers can click on the image once the post has been published and will be taken to the website for the link in the message's body. For the steps, please check out our support guide: How can I edit my link previews for LinkedIn?

Post content issues

The calculated target audience size is too small for the given targeting. An audience size of 300 is needed.

Explanation: This error will appear when you try to post to a LinkedIn Company Page with geotargeting set up with an audience that doesn't meet the 300-follower minimum.
Solution: Please adjust your LinkedIn geolocation to allow for an audience of greater than 300 followers. Please see our LinkedIn Geotargeting setup guide for more information

Size of array cannot be higher than the maxLength

Explanation: This error message indicates that the LinkedIn post exceeds the maximum character limit.
Solution: Please edit your post so that it is under the LinkedIn character limit and try re-posting.

You can't send duplicate content to the same company page or profile. Please check Profiles > My Profiles if the same company page or profile has been set up twice.

LinkedIn has declined this post as it’s a duplicate of a post that was published to this Profile recently. If you do still wish to send this post, please adjust the content before attempting to send it again.

Explanation: LinkedIn does not allow duplicate messages to be sent to a Company Page or personal Profile within a short time frame (usually 10 minutes). This error is triggered when a post is sent to the same Profile or Company Page and scheduled to go out simultaneously or in quick succession.
Solution: Please verify that you only send one version of the post to your LinkedIn account. Try re-posting to only one of the accounts, and if you're still seeing this issue with your post, please submit a ticket with the post in question, and we will investigate further.

You are forbidden from sending right now as you have reached one of LinkedIn's rate limits. Please wait a few minutes before posting again.

Explanation: LinkedIn has set a maximum number of posts that can be delivered through their API, and there are different guidelines for Company Pages and individual Profiles. Further information about those restrictions can be found in the article, Best practices: LinkedIn posting limits. Or there could have been a temporary issue on LinkedIn's end which meant that LinkedIn could not process the post when you received the undelivered error.
Solution: If you did not exceed the maximum number of posts that can be sent to LinkedIn's API during a 24hr hours, kindly repost.

Unknown errors

There was an unknown error on LinkedIn's end which prevent your post from being sent successfully. Please try again.

Explanation: This error message displays when LinkedIn is experiencing temporary issues.
Solution: Wait for 5 to 10 minutes before you try re-posting the message from your Undelivered view. If it fails with the same error message, please check downdetector.com for any LinkedIn outages.

Error while copying content to a stream

Explanation: This error message is triggered when LinkedIn is experiencing a timeout issue.
Solution: Wait a few minutes and try re-posting the message from the undelivered section.

Still an issue?

No worries! We can take it from here.

Please submit a support ticket and be sure to mention you have gone through the typical troubleshooting steps. In addition, providing screenshots and including where you were and the steps you took when the issue happened will help us resolve it more quickly!