Fix held, failed, or stuck posts
What a hold, a failure, and a post stuck in Publishing mean, how to clear the common causes, and how to retry without posting twice
Written by the Krevaya team · Updated
A held post is paused but still queued, and it goes out on its own once the reason clears or you fix it. A failed post has stopped and needs you to retry it. A post showing Publishing is being sent right now. Start by opening the post in Posts and reading the message in its details.
Read the post's status
In Posts, the List view has tabs for Drafts, Approved, Scheduled, Published, Rejected, and Failed.
| What you see | What it means | What to do |
|---|---|---|
| A yellow message on an Approved or Scheduled post | Held: paused, still queued | Fix the cause it names, or wait if it says when it will go out |
| Publishing | A send is in progress | Wait and refresh; don't make a copy |
| Failed, with a red message | The attempt ended without publishing | Fix the cause, then choose Retry publish |
| Scheduled time has passed, no message | Automatic publishing may be paused | Check Publish mode in Settings → Publishing; Off pauses everything |
Krevaya tells you about failures in the notification bell and by email by default, and about holds in the bell. Change these in Settings → Notifications.
Common holds
- Posting limit reached: the account hit its plan's cap or the platform's own limit for the last 24 hours, or a platform's shared daily allowance is used up. The message says when it will go out. On X, the monthly allowance resets on the 1st at 00:00 UTC.
- Daily limit reached on an approved post with no set time: raise the cap in Settings → Publishing → Posting limits, or give the post a specific time.
- No account is connected for the platform: connect it in Channels and the post publishes. A scheduled post still waiting more than 12 hours after its time goes back to drafts with a note, so it never goes out late without warning.
- No account is assigned to this post's brand: assign one to the brand on the Brands page, or connect the brand's own account. Krevaya never posts through another brand's account.
- Queued because several posts to the same platform already went out in this run: nothing to do; the rest go out on the next pass.
- A choice is missing: open the post and complete its panel, such as TikTok's Who can see this video, YouTube's visibility and Is this video made for kids?, a Pinterest Board, or a community, category, space, or list.
- The connection expired: reconnect the account in Channels. The post then publishes on a later pass.
- Krevaya has paused posting to a platform: Krevaya occasionally pauses one platform for everyone. The post stays queued and goes out when posting resumes; if it's more than 12 hours late by then, it comes back to you as a draft.
- Content couldn't be screened: Krevaya checks captions and media before publishing. If the check can't run, it tries again automatically. If the message says the post is held for review, contact support with the post's link.
Common failures
| Failure | What to fix |
|---|---|
| Access expired or was revoked | Reconnect the same account in Channels (for Facebook and Instagram, include the Page), then Retry publish |
| Too many media items, or pictures and videos mixed where they can't be | Reduce the set or post the video separately; Krevaya never drops items to fit |
| Video processing, length, or size | Export a compatible version and replace the media |
| The platform refused the content | Read the platform's reason, for example a duplicate on X, a community rule, or a deleted Pinterest board, then fix and retry |
Stuck in Publishing
Most sends finish within minutes; videos can take longer while the platform processes them. If a post stays in Publishing for more than about 15 minutes, Krevaya marks it Failed with "publish interrupted; retry". Before retrying, check the destination to see whether the post already went out. For TikTok, check your profile, because the video may already exist.
Retry safely
- Failed posts don't retry on their own. Fix the cause first.
- Open the post and choose Retry publish, or Schedule it for later. Don't duplicate it to retry.
- Watch the status until it shows Published, then open the live post.
Reconnecting an account doesn't resend failed posts; retry each one. If a problem persists, send support the post link, the destination, the approximate time and time zone, and the exact message. Never include passwords, API keys, or webhook URLs.