CadenzovaYour scheduler said "published". Your profile says otherwise. Here's what actually goes wrong between "sent" and "live" on each platform, how to fix it, and how to stop finding out from a customer.
When a scheduler publishes for you, it hands the post to the platform's API and gets a response back. For a plain text post that response usually means the post exists. For anything with media, it often only means the platform accepted the job: Instagram, TikTok and YouTube then download, transcode and check the file in the background, and that step can still fail minutes later. A scheduler that marks the post "published" at hand-off will show a green tick for a post nobody can see.
That gap is why "my scheduled post said it posted but it isn't there" is one of the most common complaints about every scheduling tool. The fix is to check the post again after processing, using the platform's own ID for it.
| Platform | What usually goes wrong | Fix |
|---|---|---|
| Expired connection token; the Instagram account is personal rather than Business/Creator; the Facebook Page link broke; a Reel's video codec, length or aspect ratio is rejected during processing; more than 5 hashtags (Instagram's limit since December 2025) | Reconnect; switch to a professional account; re-export video as H.264 MP4, 9:16; cut hashtags to 5 | |
| TikTok | Post stuck "processing"; video rejected after upload; privacy level not allowed for the account; spam limits from posting too often | Wait and re-check; re-export the video; use a privacy level your account allows; space posts out |
| Destination link flagged; image too small; board deleted or renamed; token expired | Check the link isn't shortened or blocked; use 1000×1500 images; re-pick the board; reconnect | |
| YouTube Shorts | Upload processed as private or unlisted (common for apps still in Google's audit); processing failed; over 3 minutes or not vertical | Check the video's visibility in YouTube Studio; keep Shorts vertical and short |
| X / Bluesky / Threads | Over the character limit (280 / 300 / 500); duplicate-post rejection; rate limits | Trim the post (use a character counter); vary near-identical posts; retry later |
In October 2026 Cadenzova changed what "published" means. After a post is sent, it looks the post up again on Instagram, Pinterest, YouTube, TikTok and Bluesky and only notifies you once the platform confirms it is live. Posts still processing are re-checked automatically, and if Cadenzova can't confirm a post after 45 minutes it tells you instead of quietly reposting. Failures come with a plain-English reason and a next step (reconnect, shorten the caption, fix the media), and temporary problems like rate limits or outages retry at 5, 20 and 60 minutes. Problems that a retry can't fix, like an expired login or a rejected file, are never retried blindly. See social media automation for the full publishing setup.
Most often the connection token expired, the account isn't a Business or Creator account, or the video failed Instagram's processing. Reconnect the account first, then check the media meets Instagram's specs.
Many schedulers mark a post published as soon as the platform accepts the upload. Video posts are processed afterwards and can still fail. Check the platform's own posts or processing view before reposting so you don't post twice.
Only after checking it isn't sitting there as private, unlisted or still processing. Reposting a post that eventually goes live gives you a duplicate.
For X and LinkedIn, Cadenzova reports the platform's own confirmation when the post is created. The live re-check covers Instagram, Pinterest, YouTube, TikTok and Bluesky.