Fix a Failed Post

Posts fail sometimes. Meta rate-limits, tokens expire, media gets rejected. Krumzi's rule is that a failure is never silent. You get a red chip on the calendar, a plain-language reason, a one-click retry, and an email.

Find what needs attention

Open the calendar. Failed posts show as red chips, and there's a needs-attention tray gathering failures and connection problems in one place. In list view, the Failed tab has a live count.

Click the post to see the reason. Krumzi writes these in plain language rather than passing through Meta's error codes.

Common reasons and fixes

Connection expired or revoked

The most common one. Meta tokens expire, and they're revoked when you change your password, remove the app, or change Page roles. Go to Accounts, click Reconnect on the orange card, and approve again. Your paused posts resume on their original schedule.

Media rejected

Usually an aspect ratio or file size the platform won't take. The composer validates before you schedule, so this mostly happens when a design changed after scheduling. Open the post, use Refresh design, and retry.

Rate limited

Meta caps how many posts an account can publish in a rolling window. Wait, then retry. If you hit this regularly, space your schedule out.

Partial

A Partial status means it went out on one platform but not the other. Open the post to see which one succeeded. Retry only affects the target that failed, so you won't double-post.

Retrying

Click the post and hit retry in the popover. It's available from month, week, and list view. Krumzi re-renders the design and tries again.

If you'd rather not publish it after all, cancel it from the same popover.

Post published but looks out of date

Krumzi renders fresh at schedule time, so this is rare. If a queued post is showing an old version, open it and click Refresh design to pull the latest.

Still stuck

Reach out through the chat widget in the app with the post's date and the reason shown on the chip. See Contact Support.