Why did my scheduled post not post?

If it keeps happening, it isn’t only you. G2’s review summary for Hootsuite, as shown on 22 October 2026, counts 370 mentions of posting issues, “including limitations on photo uploads and unexpected posting failure…”, and 248 of linking issues with Instagram (G2: Hootsuite pros and cons). A director of marketing reviewing Later on G2 wrote that “posts fail to publish or disconnect, particularly with Instagram” (G2 review, 31 July 2025). Every scheduling tool posts through the same platform rules, so the causes below apply whichever tool you use.

First, check that it really failed

1. Look at the account itself. Open the profile, and the platform’s own list of scheduled posts if it has one. A post that went out an hour early or late usually means the schedule used a different time zone, not a failure.
2. Read the error. Your scheduling tool or the platform usually says what went wrong: an expired session, a missing permission, a rejected file, a limit. Note the exact words.
3. See whether it’s one post or all of them. If every post to one account fails, suspect the connection or a permission. If one post fails and the rest go out, suspect that post’s media or text.

Cause by cause, with the fix

1. The connection expired or was revoked

Tools post with an access token the platform issued when you connected the account. Tokens expire on each platform’s timetable, and end early when someone removes the app’s access. Fix: reconnect through the platform’s own sign-in, reschedule what failed, and note when the new connection runs out.

2. A permission is missing

The connected account must be allowed to post there: the right account type, a role on the Page, and every permission the tool asked for. Fix: check the account type and the role, then reconnect and grant everything the tool asks for.

3. The media is outside the platform’s limits

Each platform sets its own limits on size, length, shape and format. Fix: check the file against the limits below, export it again and reschedule.

4. A platform limit or paid-access limit was reached

Platforms cap how much one account or one app may post in a period, and X charges for API use. Fix: wait for the reset, spread posts out, and on X check the API credits.

5. The platform had a problem

Sometimes nothing is wrong on your side. Fix: check the platform’s status page, linked below, and post again once it’s fixed.

Platform by platform

From each platform’s own pages, read on 22 October 2026. Platforms change these rules, so check the link before you rely on a number.

Instagram

• Account type. Tools publish through Meta’s Instagram API, and “to use the APIs, your app users must have an Instagram professional account”: business or creator (Meta: Instagram Platform overview). An account linked to a Facebook Page that requires Page Publishing Authorization can’t be published to until that is done (Meta: content publishing).
• Expired access. A tool’s long-lived Instagram token lasts 60 days and can be renewed while valid, but “tokens that have not been refreshed in 60 days will expire and can no longer be refreshed” (Meta: Instagram business login). In the Instagram app, Website permissions, then Apps and websites, lists the apps connected to the account (Instagram Help).
• Daily cap. Meta limits how many posts one account can publish through the API in 24 hours, counting a carousel as one; its pages currently give the cap as both 100 and 50. Over it, the advice is to try again the following day (Meta: Instagram error codes).
• Media. Images must be JPEG, up to 8 MB, with an aspect ratio between 4:5 and 1.91:1. Reels must be MOV or MP4, from 3 seconds to 15 minutes and up to 300 MB; 9:16 avoids cropping. Captions take up to 2,200 characters, 30 hashtags and 20 @ tags (Meta: IG User media reference).
• A restricted account. If the account is “inactive, checkpointed, or restricted”, Meta’s advice is to sign in to the Instagram app and complete any actions it asks for (Meta: Instagram error codes).
• Meta Business Suite. Connecting Instagram there needs a professional account, full control of the Facebook Page, and both in the same business portfolio (Meta Business Help: connect Instagram to a Page), and an Instagram account can belong to only one business portfolio (Meta Business Help).
• Instagram’s own scheduler takes up to 25 posts a day, up to 30 days ahead, and “product tagging, collaborative posts, sponsored posts and fundraisers aren’t compatible with scheduled content at this time” (Instagram Help: schedule posts).

Facebook Pages

• A role on the Page. A tool posts as the Page with a Page access token, and “the person requesting the token must have a role on the Page” (Meta: long-lived tokens). If that role is removed, posting fails with an error saying the user “does not have an appropriate role on the Page” (Meta: Graph API errors).
• Password changes. After a password change the person must log in to the tool again (Meta: Graph API errors), and Meta warns developers that “Facebook will not notify you that an access token has become invalid” (Meta: access token errors). Reconnect after any password change.
• Duplicates. “Duplicate posts cannot be published consecutively. Change the content of the post and try again” (Meta: Graph API errors).
• Meta Business Suite. Meta says a scheduled post may not publish if you lack access to publish, the linked Instagram account has an unresolved issue or was hacked, or a system error stopped it. Ask the owner for access, sign in to the Instagram app to read its notices, or open Content, then Scheduled, find the error and click Publish now (Meta Business Help: troubleshoot scheduling errors).
• Outages. Meta’s status page covers its business tools, including Meta Business Suite and the Graph API.

X

• API credits. The X API “uses pay-per-usage pricing”: “Purchase credits upfront in the Developer Console. Credits are deducted as you make API requests” (X API pricing). When they run out, “API requests will fail until you purchase more credits” (X: usage and billing). Ask whoever pays for the tool’s X access to check the balance.
• Rate limits. Posting through the API is capped at 100 posts per user every 15 minutes and 10,000 per app every 24 hours; over a limit, X answers 429 until the window resets (X API rate limits).
• Access revoked. “An access token will be invalidated if a user explicitly revokes an application in their X account settings, or if X suspends an application,” and X tells developers to prompt the user to re-authorize (X authentication FAQ).
• Media. Images up to 5 MB, animated GIFs up to 15 MB, and video up to 20 minutes, or 125 minutes for X Premium accounts; the limits follow the account, not the tool (X media upload).
• Replies and quote posts. On X’s self-serve API plans, quote posts need an Enterprise plan, and a reply is allowed only when the original post’s author has mentioned or quoted the replying account (X: manage posts). A scheduled reply or quote post can fail for that reason alone.
• Outages. X reports API incidents on its developer platform status page.

LinkedIn

• Connections last 60 days. “Currently, all access tokens are issued with a 60-day lifespan,” and the refresh tokens that renew them without a new sign-in are available only to “a limited set of partners” (LinkedIn developer docs: authorization code flow). For most tools, that means reconnecting every two months.
• Posting as a Page needs a Page role. A tool can post for a company Page only if the person who connected it holds one of the Page roles LinkedIn lists (administrator, content admin or direct sponsored content poster); without one, LinkedIn answers with an access error (LinkedIn Posts API). If that person leaves, someone who still has a role must reconnect.
• Daily limits. LinkedIn caps API calls per app and per member over 24 hours; the limits “reset at midnight UTC every day”, and a request over the limit gets a 429 response (LinkedIn rate limits).
• Media. Videos must be MP4, three seconds to 30 minutes long (Videos API); images JPG, GIF or PNG with fewer than 36,152,320 pixels (Images API). A post that ends as “PUBLISH_FAILED” needs an edit before LinkedIn will try again (Posts API).
• Outages. LinkedIn reports API incidents on its API status page.

YouTube

• Upload limits. YouTube caps how many videos a channel can upload in 24 hours “across desktop, mobile, and YouTube API”, and the cap may vary by country or region, channel history and strikes. If you see “Daily Upload limit reached”, YouTube’s advice is to try again in 24 hours (YouTube Help: common uploading errors).
• The tool’s API quota. A tool that uploads through the YouTube Data API gets, by default, 100 uploads a day per project, and the quota resets at midnight Pacific Time (YouTube Data API: quota costs). Past it, uploads fail until the reset.
• Length and shape. Videos longer than 15 minutes need a verified account (YouTube Help). A Short can be up to three minutes long, with a square or vertical aspect ratio (YouTube Help: Shorts).
• Sign-in. An app’s access stops when you remove it, after six months unused, or after 7 days while the tool’s Google project is still in “Testing”. One Google Account can also hold only 100 live sign-ins per app; the next one invalidates the oldest “without warning”, which matters if one person connects many channels (Google Identity: refresh token expiration). Your Google Account’s linked apps page shows which apps have access.
• Strikes. With a Community Guidelines strike, a scheduled video won’t publish during the penalty period; it stays private and you reschedule it afterwards (YouTube Help: schedule video publish time).
• Outages. YouTube lists incidents it is fixing on its Known Issues page.

How to hear about it first

The worst way to learn about a failed post is from a client. Three habits catch most failures early:

1. Turn on failure alerts in your scheduling tool, and send them somewhere a person reads every day.
2. Check each account’s schedule daily: what was due, what went out, what is next.
3. Track when connections expire. For each account, note who holds admin rights, who connected it and when it needs reconnecting. The client onboarding checklist has a place for each.

In Growfinch, failures come to you:

• A post that fails for a temporary reason, such as a rate limit or a network error, is retried with growing gaps.
• When it fails for good, it becomes an exception in Approvals that says what happened, which account it affects and the fix: reconnect the account, top up X credits, or try again. Exceptions wait in the same queue as posts waiting for approval.
• An expired connection shows “needs reauthorization” and a Reconnect button.
• Before anything is scheduled, the dry run flags an account that needs reconnecting, a format the platform doesn’t take and a caption over the platform’s limit.
• Your own systems can listen for the post.failed, connection.expired and exception.created webhooks through the API.

A daily email of missed posts is planned.