Failed posts show a red status on the calendar and in the Queue. Open the post and check the Publishing status card in the right-hand column — it lists every channel the post targeted and whether that channel succeeded or failed. The card tells you which channel failed; the cause is almost always one of the ones below.
A failed post is final. PostVito does not retry it, and reconnecting the channel does not bring it back. Fix the underlying cause first, then re-schedule the post from the client’s content pack. Posts that are still scheduled are unaffected and will publish normally once the channel is healthy.
Expired access token
Platforms expire the access tokens PostVito publishes with. When a client’s token lapses — often after a password change or a long gap — publishing stops until you reconnect. Fix: open the client, go to Channels, and click Reconnect on the flagged row. That fixes everything still scheduled; anything that already failed needs re-scheduling from the pack.
Media too large or too long
Every platform has its own caps. Oversized images are compressed for you on the way out, so they rarely cause a failure — videos are not. A video over the platform’s size or length cap fails outright, so export a smaller or shorter version and re-upload it. The limits worth knowing:
- TikTok: video over 4 GB or 10 minutes. TikTok is video-only in PostVito — image posts can’t be sent there.
- Instagram: video over 300 MB or 90 seconds.
- X: video over 512 MB or 2 minutes 20 seconds.
Carousel aspect mismatch (Instagram)
Instagram requires every image in a carousel to share one aspect ratio. Mix a 4:5 portrait slide with a 1:1 square and Instagram rejects the whole post. Fix: re-crop every slide to a single ratio in the pack editor, then re-schedule.
Duplicate content
TikTok and Instagram can silently reject a post that’s identical to a recent one. If you’re re-posting to test, change the caption, an image, or the hashtags before you try again.
Channel not connected
If a client disconnected a channel — or it was never connected — posts to it fail. Reconnect the channel on the client page, then re-schedule the post.
Posts that were deliberately held
Not everything that doesn’t go out has failed. Posts are held on purpose when the client is paused or archived, and when the workspace’s billing is degraded. If a whole client’s output stops at once, check the client’s status and your subscription before hunting for a platform fault.
Note: Because a failed post can’t be retried, the fastest route back is the pack it came from: fix the cause, open the client’s content pack, and schedule the post again from there.