Failed posts and storage

When a scheduled post didn't go out

Open the post from the calendar or the bell: it says what happened in one sentence and offers the fix — Reconnect account, Edit post or Retry now. The network's original message stays under Details; include it if you write to us.

Updated 14 November 2026

How you find out

A failed post is marked Failed in the calendar and appears in the bell. We also email you (Notifications → “Scheduled posts that didn’t go out”), and a webhook post.failed goes out if you set one up. The same reason and fix are shown everywhere.

Fix and retry

Do what the reason says — reconnect the account, edit the post, or wait for a limit — then press Retry now. To deal with many at once, set the calendar's Status filter to Failed, select the posts, and Retry them or Reschedule to next slot.

If our publishing service was down at the scheduled time and the post would be more than an hour late, we don't publish it late — it's marked failed so you can post it now or pick a new time.

“Check” — we couldn't confirm the post

Sometimes we send a post and the network doesn't answer in time. Then the post is marked Unconfirmed (“Check” on the calendar), because it may already be live. Look at the profile first and post again only if it isn't there — retrying blindly can make a duplicate.

Every reason, and what to do

These are the reasons the calendar, the bell, the email and the webhook (errorCode) can show.

  1. The account is locked by your plan

    Your plan doesn't cover this account right now, so the post waited 7 days and then stopped. Make the account active on Connections or upgrade, then reschedule it.

    Code account_locked · Button in the app: See plans

  2. Publishing was paused for the account

    Publishing was paused for this account when the post was due, so we held it back rather than publish it late. Post it now or pick a new time.

    Code account_paused

  3. The post missed its time

    Our publishing service was down at the scheduled time, so we held the post back rather than publish it late — that's on us. Post it now or pick a new time.

    Code missed_time

  4. ClipEmber hit the network's daily app limit

    ClipEmber hit the network's daily limit for our app — that's on our side, not your account. Retry in a few hours or reschedule for tomorrow.

    Code app_limit

  5. TikTok Inbox is full of unfinished uploads

    TikTok paused new uploads because earlier ones are still waiting in this account's TikTok Inbox. Finish or dismiss them in the TikTok app, then retry.

    Code tiktok_inbox_full

  6. TikTok blocked the account from posting

    TikTok has blocked this account from posting, so we can't publish to it. Check the TikTok app for details.

    Code posting_banned

  7. YouTube’s 24-hour upload limit for a channel

    YouTube limits how many videos a channel can upload through apps in 24 hours, and this channel reached that limit. Pick a time after the 24 hours are up, and spread YouTube posts out across the day.

    Code channel_upload_limit · Button in the app: Edit post

  8. The account hit the network's posting limit

    The network limited how often this account can post, and the limit was still on after several tries. Retry in a few hours or pick a later time.

    Code rate_limited

  9. We lost access to the account

    We lost access to this account — its sign-in expired, was revoked, or can't be read. Reconnect it, then retry.

    Code reconnect · Button in the app: Reconnect account

  10. No account connected

    No account is connected for this network. Connect one, then retry.

    Code not_connected · Button in the app: Reconnect account

  11. TikTok didn't accept the audience

    TikTok didn't accept who can see this post — the account's options changed (for example it went private), or branded content can't be 'Only me'. Open the post, choose the audience again, then retry.

    Code tiktok_audience · Button in the app: Edit post

  12. The video is too long or too short

    The video is longer or shorter than this network allows. Trim it in the editor, then retry.

    Code video_length · Button in the app: Edit post

  13. TikTok couldn't download the video

    TikTok couldn't download the video from our storage — that's on our side. Retry; if it happens again, contact us.

    Code video_fetch

  14. The network didn't accept the video format

    The network didn't accept the video's format — size, aspect ratio, frame rate or encoding. Export it as a 9:16 MP4 (1080×1920, 24–60 fps), upload it again, then retry.

    Code video_format · Button in the app: Edit post

  15. The video is missing

    The video for this post is missing or couldn't be processed. Upload it again or re-render the clip, then reschedule.

    Code media_missing · Button in the app: Edit post

  16. The clip needs a fresh render

    This clip needs a fresh render before it can go out (its watermark setting doesn't match the file we have). Re-render it — recompiles are free — then retry.

    Code watermark · Button in the app: Edit post

  17. Publishing to the network is switched off

    Publishing to this network isn't switched on on our side — that's on us, not your account. Contact us and we'll sort it out.

    Code not_configured

  18. The network turned the post down

    The network turned the post down — its own reason is in the details. Fix what it mentions and retry, or contact us if it's unclear.

    Code platform_rejected

  19. “We couldn't confirm this post”

    We sent the post but the network didn't answer in time, so it may already be live. Check the profile first and post again only if it isn't there.

    Code unconfirmed

  20. Any other reason

    We couldn't publish this post and don't recognise the reason — it may be on our side. Retry; if it fails again, contact us with the details.

    Code unknown

Still stuck? Email hello@clipember.com — a person on the team reads it.