When a social message fails, CoSchedule shows an error on the message. Find the error text below to see what it means and what to do. This applies to every plan, including the free plan.
Read the error on a message
- On your calendar, open the social message that didn't publish.
- Read the error on the message. A yellow warning means CoSchedule is still trying to send it. A red error means it failed.
- Find the error text in the table below.
A failed message doesn't retry by itself. After you fix the cause, reschedule the message.
Social message errors
Error | Network | What it means | What to do |
|---|---|---|---|
The service responded in an unexpected way and may prevent publication of this message. | Any network | A general error. The network responded in a way CoSchedule didn't expect. | Wait for CoSchedule's remaining attempts. If it still fails, reschedule once. If it fails again, contact support with a link to the message. See Why a social message did not publish. |
Scheduled too far in the past | Any network | The message wasn't sent within the retry window after its scheduled time. | Reschedule it. If it's tied to a WordPress post, make your WordPress and calendar timezones match. See Why a social message did not publish. |
CoSchedule is still processing the media | Any network | An image or video isn't ready to send yet. While the warning is yellow, CoSchedule is still retrying. | Wait for the retries to finish. If the message fails, upload the media again and reschedule. See Fix image and video errors in social messages. |
Video is still being processed | Any network | CoSchedule is still processing the video. Large videos can take several minutes. | Wait for the retries to finish. If the message fails, reschedule it. Schedule video messages at least 30 minutes ahead. See Fix image and video errors in social messages. |
We had trouble sending the photo(s) which are attached to this message | Any network | The image was added by URL instead of uploaded as a file. | Remove the image, upload it from your computer and reschedule. See Fix image and video errors in social messages. |
Your message failed to send because it requires approval from 1 or more team members. Please have them approve the message and reschedule. | Any network | The message needed approval, and no one approved it before CoSchedule's attempts to send it ran out. | Get the message approved, then reschedule it. See Set up and use social approvals. |
Facebook blocked this message from being sent | Facebook judged activity on the Page to be suspicious, abusive or unsafe. | Check whether Facebook restricted your Page and request a review if needed, then reschedule. See Facebook blocked this message from being sent. | |
Facebook couldn't accept your message because it is experiencing temporary downtime | Facebook had a temporary outage, and CoSchedule's attempts to send the message ran out. The post may already be live. | Check your Facebook Page first. If the post isn't there, reschedule it. See Facebook couldn't accept your message because it is experiencing temporary downtime. | |
Facebook denied CoSchedule's request to send this message for this user | The person who connected the Page no longer has admin access to it. Facebook's part of the message says the user must be an administrator of the Page. | Have someone with full control of the Page reconnect the profile, then reschedule. See Facebook denied CoSchedule's request to send this message for this user. | |
Facebook denied CoSchedule's request to send this message. Facebook does not allow you to share Facebook links when publishing a link message. | Facebook doesn't let tools like CoSchedule publish a link message that links to Facebook, such as a Facebook event. | Share it directly on Facebook, or send it as an image message with the Facebook link in the message text. See Facebook does not allow you to share Facebook links when publishing a link message. | |
Facebook encountered an error because your message contains a missing or invalid image | CoSchedule couldn't send the image to Facebook, usually because the file is too large or didn't upload. | Check the image's size and file type, fix it and reschedule. See Facebook encountered an error because your message contains a missing or invalid image. | |
Facebook Open Graph data did not match the message | CoSchedule couldn't read the preview image from the page you linked to. The message usually still publishes. | If the message failed, fix the Open Graph data and reschedule it. See Facebook Open Graph data did not match the message. | |
Facebook Open Graph data did not return a title for the url. We will re-scrape and try again. | CoSchedule couldn't read a title from the page you linked to. | Check the linked page's Open Graph tags. See Fix a wrong link image or missing link in a social message. | |
Instagram failed to process the media for this message. Please re-upload your media and try again | Instagram couldn't process the image or video, and CoSchedule's attempts ran out. | Remove the media, upload it again so only the new upload is attached, and reschedule. See Fix Instagram messages that failed or published wrong. | |
Pinterest denied publishing social message because the limit was reached. Click here for more information: | Your Pinterest account reached a 24-hour limit that Pinterest sets. | Reschedule the message at least 24 hours after its original time. See Pinterest denied publishing social message because limit was reached. | |
You have reached your monthly Bitly quota | Any network that uses Bitly | Your Bitly account reached its monthly limit, so Bitly wouldn't shorten the link and the message failed. | Raise your limit with Bitly, or turn off Bitly for the message or the calendar. Then reschedule. See Shorten links with Bitly. |
If a LinkedIn message failed with an error that isn't listed here, see Fix LinkedIn publishing problems.
WordPress errors
These errors come from the WordPress integration.
Error | What it means | What to do |
|---|---|---|
Could Not Reach WordPress Admin | Your site asks for basic HTTP authentication, so CoSchedule couldn't reach the WordPress admin area. | Turn on WordPress Basic HTTP Auth for the site in CoSchedule and enter your server's HTTP auth username and password, not your WordPress login. See Fix "Could not reach WordPress admin" and firewall problems. |
Problem with your server's timestamp | Your web server's time settings are missing or wrong. | Ask your web host to turn on time syncing and set PHP's timezone. See Fix WordPress timezone and timestamp problems. |