Why Didn't My Scheduled Social Media Post Publish?

A post that was going to go out at nine and did not is a bad morning. The good news is that the list of causes is short, and Hyvo knows which one it was.

Start at Posts

Every post Hyvo has published, queued or failed to publish is on the Posts screen, with its state on the row.

Find the post. The row will tell you which of the four things below happened, per account, because a post going to four accounts can succeed on three and fail on one.

That per account detail matters. "Failed" on a multi channel post usually means one channel failed, and the fix is on that channel rather than on the post.

Cause 1: The connection expired

The most common one by a distance.

Networks expire access tokens on their own schedule. Some of them also revoke immediately if you change your password, or if somebody removes the app from the network's settings page.

An expired connection cannot publish, so the queued post fails when its time comes.

Open Connect. An expired account says so on its row and offers Reconnect. Press it, approve the permissions again, and the account is live. Then republish the post.

Cause 2: The post was too long for that account

Every network has its own limit, and they are not close to each other. X is 280 characters. Bluesky is 300. Threads, Pinterest and Mastodon are 500. Instagram and TikTok are 2,200. LinkedIn is 3,000. Facebook is 63,206.

The composer counts per account and warns you before you schedule, but a post edited after scheduling, or one where an account was added later, can end up over.

Networks do not trim. They reject.

Cause 3: A media only network got no media

Instagram, Pinterest and TikTok have no text only post in their API at all. Not a short one, not an empty one. A post to any of the three needs an image or a video.

Hyvo checks this in the composer and blocks the publish rather than queuing something that cannot succeed. If a post got past that check, it usually means the media was removed after scheduling.

Cause 4: The network rejected it

The rarer one, and the only one that is not about your setup. A network can reject a post for its own reasons: duplicate content posted too soon after an identical post, rate limits during a burst, a link on a domain it does not like, or a temporary outage on their side.

The row will carry whatever reason the network returned. If it is a rate limit or an outage, republishing an hour later usually works.

Fix it, then republish

Once the cause is fixed, republish from the post itself rather than writing a new one. The post keeps its text, its media and its channels, so you are only repeating the part that failed.

FAQs

Does Hyvo retry a failed post automatically?

No. A silent retry can publish something hours late into a completely different context, so a failure waits for you.

Will the rest of a multi channel post still go out?

Yes. Each account publishes on its own, so a failure on one does not hold the others.

How do I know a connection is about to expire?

The account row on Connect shows the state. There is no countdown, because networks do not publish one.

The post says it published but I cannot see it. What now?

Check the account it published to, especially if you administer several Pages. If it published to the wrong Page, the connection is pointed at the wrong one and reconnecting lets you pick again.

Can I stop this happening again?

Reconnect accounts before a big batch, keep an eye on the per account character counter, and attach media to anything going to Instagram, Pinterest or TikTok. That covers three of the four.