> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ocoya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why didn't my post publish?

> What to check when a scheduled Ocoya post didn't go out, and how to get it published.

When a scheduled post doesn't appear on your social channel, Ocoya has almost always tried to publish it and been refused by the network. The post keeps the error it received, so you can see exactly what happened and fix it.

Two things are worth knowing before you start:

* **Each channel publishes separately.** A post going to four channels is four separate attempts. Three can succeed while the fourth fails, so check every channel rather than assuming the whole post failed.
* **Ocoya does not retry a failed post.** Once a channel refuses a post, that attempt is finished. Fixing the problem does not republish it by itself — you need to schedule it again.

## Find the post and read the error

Open **Planner** and find the post on the date it was meant to go out. You can use the List, Board or Calendar view — whichever you prefer.

<Frame caption="Planner, with the List, Board and Calendar views and a filter for showing one channel at a time.">
  <img src="https://mintcdn.com/ocoya/AXU_TbAvrsHP8A-m/images/screenshots/calendar-view.png?fit=max&auto=format&n=AXU_TbAvrsHP8A-m&q=85&s=3f15874d552ea7d353d43ce0452bc7ee" alt="Ocoya Planner in Calendar view showing a month grid, a Draft panel on the left, an All profiles filter and a Share button above the calendar" width="2880" height="1800" data-path="images/screenshots/calendar-view.png" />
</Frame>

Open the post. Ocoya stores the message the network sent back, per channel, and that message is the fastest route to the cause. Work through the sections below to match it.

## The channel needs reconnecting

This is the most common cause by a wide margin.

Ocoya refreshes its access to your channel at the moment it publishes. If the network has expired or revoked that access, publishing fails there and then, even though the channel looked fine in your list the day before.

Access is typically revoked when someone changes the account password, removes Ocoya from the network's connected-apps list, changes who administers a Facebook Page, or lets the network's own token expiry lapse.

**How to fix it:** go to **Channels**, reconnect the affected channel, then reschedule the post.

<Frame caption="The Channels page lists every connected channel and when it was last connected.">
  <img src="https://mintcdn.com/ocoya/AXU_TbAvrsHP8A-m/images/screenshots/channels-overview.png?fit=max&auto=format&n=AXU_TbAvrsHP8A-m&q=85&s=359aeb8aa5cce06566be3d1286007250" alt="Ocoya Channels page showing a table of connected channels with their networks and connection dates, plus a Connect channel button" width="2880" height="1800" data-path="images/screenshots/channels-overview.png" />
</Frame>

## The post broke one of the network's rules

Ocoya checks your post against each network's limits before sending it. If a channel rejects the post, the error names the specific rule.

Every network has different rules, which is why the same post can publish fine to LinkedIn and fail on Instagram.

**Caption too long**

> *\[Network]* caption exceeds character limit

Shorten the caption for that channel. You can write a different caption per channel rather than trimming the whole post.

**Too many images, videos or GIFs**

> *\[Network]* allows a maximum of *\[n]* images per post

Remove the extras, or split the content across several posts. Discord accepts at most 10 attachments per post.

**File too large or too wide**

> Maximum *\[network]* image size of \*\[n]\*mb exceeded
> Maximum *\[network]* video width of \*\[n]\*px exceeded

Compress or resize the file. Reels, Stories and standard posts each have their own size and dimension limits on the same network.

**Video or GIF too long or too short**

Each network sets its own minimum and maximum duration, and Stories and Reels differ from standard video.

**Too many hashtags**

> *\[Network]* allows a maximum of *\[n]* hashtags per post

**The post was empty for that channel**

> *\[Network]* post is empty

A post can have content for one channel and nothing for another if the per-channel text was cleared. Add content for that channel, or remove it from the post.

### Rules specific to one network

| Network         | Requirement                                                                                                                       |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| LinkedIn        | A PDF carousel needs at least 2 images                                                                                            |
| Discord         | Maximum 10 attachments per post                                                                                                   |
| Google Business | Events and offers need a title, and a start and end time. The end time must be after the start time. A button needs a valid link. |
| Instagram       | The account must be a Business or Creator account, not personal                                                                   |

## The scheduled time was too close to now

Ocoya needs a short lead time to queue a post. If you schedule something for less than two minutes ahead, it is refused with:

> Choose a schedule time at least 2 minutes from now

Pick a time further out, or use **Publish now** instead.

## Nothing published at all, on any channel

If an entire day of posts didn't go out, the cause is usually one of these rather than a per-post problem:

1. **The post was still a draft.** Drafts never publish. Check whether the post shows as a draft in Planner.
2. **The post was awaiting approval.** If your brand uses post approval, a post that hasn't been approved will not go out.
3. **Your time zone isn't what you think.** A post scheduled for 9am publishes at 9am in your brand's time zone, which may not be your local one.
4. **You ran out of credits.** This only affects posts an automation was due to generate — credits are never needed to publish a post you already created.

## After you fix it

Because Ocoya doesn't retry, fixing the underlying problem doesn't republish anything. Reschedule the post:

1. Open the post in Planner.
2. Correct whatever the error named — reconnect the channel, shorten the caption, swap the image.
3. Set a new date and time at least two minutes ahead, and save.

If the post is time-sensitive and the moment has passed, use **Publish now** instead of scheduling.

<Note>
  If a post published to some channels but not others, don't reschedule the whole post — that would publish it twice on the channels that already succeeded. Remove the channels that worked, then reschedule for the ones that failed.
</Note>

## Still failing

If a post keeps failing and the error doesn't match anything above, [contact support](https://app.ocoya.com/?modal=support) and include:

* The exact error message shown on the post
* Which channel it was going to
* The date and time it was scheduled for

That's enough for the team to trace the publish attempt directly.

## Related

<Card title="What are credits?" icon="zap" href="/help/credits">
  What credits are used for, and what happens when you run out.
</Card>
