Calendar and publishing
When a post fails
A failed post keeps the reason the platform gave. Open the post to read it.
What is checked before you schedule
Most of what a platform refuses is knowable up front, so MORR checks it while the screen is still open rather than letting you find out hours later. Both clients run the same list, against the same table of per-channel rules.
| Checked | Example |
|---|---|
| A channel is attached | A post with none is never claimed by anything |
| There is something to post | A caption, media, or both |
| The channel takes this kind of post | YouTube only takes video; Instagram will not take text alone |
| The caption fits | 280 characters on X, 500 on Threads, 2,200 elsewhere |
| The first comment fits | 300 characters on Bluesky, 500 on Threads, 2,200 on Instagram |
| A carousel has no more slides than the channel takes | Ten on Instagram, four on X. Fixed by Split into two posts, not by removing work |
| The video is not too long | 15 minutes on Instagram, 140 seconds on X |
| The video is not too short | 3 seconds on Instagram, 4 on Pinterest |
| The video is a shape the channel takes | Instagram feed runs 4:5 to 1.91:1 |
| The media actually uploaded | A local-only file would reach the publisher empty |
Size is not on the list, because it is not a reason to stop. A video over the publisher's 300 MB (Bluesky's 100 MB) is made to fit before it is queued. See Writing a post.
| Reason | What it usually is | Fix |
|---|---|---|
| Channel not connected | The link expired or was revoked | Reconnect it under Settings → Workspace → Channels, then reschedule |
| Media unreachable | The file only exists on a device that is offline | See Where your files live |
| Rejected by the platform | Aspect ratio, length, or a content rule | Fix the media and reschedule |
| Rate limited | Too many posts to that account too quickly | MORR retries on its own, with a growing gap |