Sometimes social messages fail to publish as you expect them to. There are different reasons this may occur.
- Incorrect timezone settings in WordPress
- Social networks experiencing performance issues
- Reauthorization of social account required
Your message is set to "draft."
Your social message may not have sent because it was still set to "draft." Changing the status of the message to "scheduled" or "published" will set your message to go live immediately or in the future, depending upon what you've chosen as a publishing time.
Your published blog post had a date/time in the past.
You may have had a publishing date and time set for your blog post which was in the past, and created all of your social messages along with it. If you publish the post without updating the date and time to be current and use the old timestamp instead, your social messages will not send. This is because the post will have been published "in the past" and your messages that were scheduled to go out at the same time as the post will show an error.
To fix this simple issue you can do one of two options:
- Go into WordPress or the CoSchedule calendar and change the post date and time today at the current time.
- Reschedule your social messages to send on a hard date and time and
Both options will work. The first option will not affect your post in any way, and will automatically send your messages quickly. The updated time you choose must be within 15 minutes or so of the current time for your messages to send.
You might have a low traffic WordPress blog.
If you have a low-traffic blog, you may experience social messages that don't always send.
This is because of the way that WordPress changes the status on a published post, relying on someone to visit your blog to flag your post as published. It is that flagging of a post that CoSchedule uses as a cue to start sending social messages. Because CoSchedule will not send a message after it is scheduled, this may cause failed messages. If you have a low-traffic blog, we recommend you turn on your WordPress crons.
An incorrect timezone setting will cause social messages to publish incorrectly.
CoSchedule relies upon the time settings you use in WordPress. Be sure that you have the correct time zone selected in your WordPress installation, or the hour your social message is published may be off.
To access your time zone settings, go to the Settings > General section of your dashboard, and locate the time zone settings area. Use this guide to help you choose the correct settings.
The social network may be experiencing downtime or other issues.
At times, social networks experience issues out of our control. These are called soft failures. The might include such things as a message with too many characters, an invalid link in the message that the network won't accept, or even a hiccup on the server. Here are a few common issues:
- Twitter duplicate status (Read more from Twitter about duplicate status rules.)
- Twitter status is over 140 characters
- Twitter server error
- Twitter over capacity
- Twitter API URL not found
- Facebook API blinked and missed something (no, really)
- Facebook invalid link
- Facebook API request limit reached
- Facebook API request limit reached
- Facebook API server problem
- Facebook API unknown problem
Each network has different issues it may experience.
You need to reauthorize your social media account.
There are times when you will need to reauthorize your account. Failures caused by this are called hard failures. These occur when a password or login information for the social account has changed, or other reasons where the oauth token has expired.
When you need to reauthorize your account, it is important that you DO NOT delete a social account. Deleting an account will remove any messages associated with that account. You won't have any history, nor will any of your scheduled messages be published.
Reauthorizing an account will not have any effect on your messages.
Deleting an account will cause you to lose all messages, both from your history and those you have scheduled. Already published messages will not be removed from your social networks, but you will not see evidence of them in the CoSchedule plugin within WordPress. You will not see messages associated with that account listed under any post even if a message had been published to it previously.
You will be notified if your social messages fail to send.
We will make six attempts to send your social messages. If a message does not send, we will determine if it was a soft or hard failure, and notify all users who are admins with an email. The email will briefly explain what happened and the solution necessary to correct the issue.
You will also see social messages that did not send indicated in red on your calendar.