Scheduled Posts Not Publishing? Here's How to Fix It

You scheduled a post for 9 AM. It is now 11 AM and your feed is empty. No error notification, no explanation — the post just did not go out.

This is one of the most frustrating things in social media management, and it happens to everyone eventually. The good news is that there are only about a dozen reasons a scheduled post fails, and most of them take under five minutes to fix.

Here is a step-by-step diagnostic guide covering every common cause and exactly how to resolve it.

1. Token or Connection Expired

This is the most common reason scheduled posts fail. When you connect a social media account to a scheduling tool, the tool receives an authentication token from the platform. These tokens expire — typically every 60 to 90 days — and when they do, the tool loses permission to post on your behalf.

What it looks like: All scheduled posts for a specific account fail at once. You might see error messages like "authentication expired," "reconnect your account," or "invalid token." Posts for other accounts still publish normally.

Why it happens: Meta (Instagram and Facebook) tokens expire every 60 days. LinkedIn tokens expire every 60 days. X/Twitter tokens can expire after 90 days or when you change your password. TikTok tokens expire every 60 days.

How to fix it:

• In PostEverywhere: Go to Settings and then Connected Accounts. Any expired connection will show a red warning badge. Click Reconnect, log into the platform, and re-authorize. All pending scheduled posts will automatically retry.
• In Meta Business Suite: Go to Business Settings, then Accounts, then Apps. Remove the expired connection and re-add it.
• In Buffer: Go to Channels, find the disconnected account, and click Reconnect.
• In Hootsuite: Go to My Profile, then Social Networks, and reconnect the flagged account.

Pro tip: Set a recurring calendar reminder every 50 days to proactively refresh your connections before they expire. In PostEverywhere, you will receive email alerts 7 days before a token expires so you never get caught off guard.

2. Account Permissions Changed

Even if your token is valid, the post will fail if the permissions behind it changed. This typically happens when someone on your team adjusts roles in the native platform — for example, downgrading a user from Admin to Editor on a Facebook Page, or removing posting access on a LinkedIn Company Page.

What it looks like: Token shows as connected, but posts fail with a "permissions" or "access denied" error. Only specific account types (like Pages or Business accounts) are affected.

Why it happens: Someone changed roles in the platform's native settings. The account was converted from Personal to Business or vice versa. A team member who originally authorized the connection left the organization.

How to fix it:

1. Check who authorized the original connection — they need to still have Admin or posting access.
2. In Meta Business Suite, go to Page Settings and then Page Roles to verify the connected user still has the right role.
3. On LinkedIn, check Company Page admin settings.
4. Disconnect and reconnect the account using credentials from a user who has full posting permissions.

3. API Rate Limits Hit

Every social media platform limits how many API calls a scheduling tool can make in a given time window. If your tool exceeds these limits — usually because you are publishing a high volume of posts across many accounts — some posts will be queued or dropped.

What it looks like: Some posts publish and others do not. Failures seem random rather than affecting one specific account. Posts scheduled close together are more likely to fail.

Why it happens: Meta allows roughly 200 API calls per user per hour. LinkedIn limits to approximately 100 calls per day per app. X/Twitter has notoriously tight rate limits, especially since 2023. Scheduling many posts to publish at the same time (like the top of every hour) creates spikes.

How to fix it:

• Spread your posting times out — avoid scheduling 10 posts for exactly 9:00 AM across different accounts.
• In PostEverywhere, we automatically stagger posts within a 5-minute window to avoid rate limit collisions. If you are using another tool, manually offset your times by 2-3 minutes.
• If you are hitting limits regularly, check whether multiple team members have connected the same accounts through different tools — each tool uses separate API quota.

Stop fighting rate limits. PostEverywhere handles API throttling automatically. Start your 14-day free trial — no credit card required.

4. Image or Video Format Not Supported

You attached a WebP image to an Instagram post, or a MOV video to a LinkedIn update. The post fails because the platform does not accept that file format through its API, even if the native app would accept it.

What it looks like: The post fails with a "media format not supported" or "invalid media" error. Text-only versions of the same post publish fine.

Why it happens: Each platform has specific format requirements through their APIs, and these requirements are often stricter than what the native app accepts.

Supported formats by platform:

• Instagram: JPG and PNG for images. MP4 for video. No WebP, GIF, or HEIC through the API.
• Facebook: JPG, PNG, and GIF for images. MP4 for video.
• LinkedIn: JPG, PNG, and GIF for images. MP4 for video. Maximum 9 images per post.
• X/Twitter: JPG, PNG, GIF, and WebP for images. MP4 for video.
• TikTok: MP4 and WebM for video only. No image posts through the API.

How to fix it:

• Convert WebP and HEIC images to JPG or PNG before uploading.
• Use our Instagram image resizer to get images into the right format and dimensions.
• For video, convert to MP4 with H.264 encoding — this is universally accepted.

5. File Size Too Large

Platforms enforce maximum file sizes, and scheduling tools are often stricter than the native apps because of upload time constraints and API limitations.

What it looks like: Upload appears to succeed, but the post fails when it tries to publish. Error messages mention "file too large" or "upload timeout."

Why it happens: You are uploading high-resolution images or long videos that exceed the platform's API limits.

Maximum file sizes:

• Instagram: 8 MB for images, 650 MB for Reels (up to 15 minutes)
• Facebook: 10 MB for images, 10 GB for video
• LinkedIn: 10 MB for images, 5 GB for video
• X/Twitter: 5 MB for images, 512 MB for video
• TikTok: 4 GB for video
• YouTube: 256 GB for video (but scheduling tools may have lower limits)

How to fix it:

• Compress images before uploading — most social images look identical at 80% quality.
• For video, use a tool like HandBrake to reduce file size without visible quality loss.
• If you are scheduling YouTube uploads through a YouTube scheduler, check the tool's specific upload limit — it may be lower than YouTube's native 256 GB cap.

6. Character Limit Exceeded

You wrote a caption that works on LinkedIn (3,000 characters) and cross-posted it to X without trimming. The post fails because it exceeds the platform's character limit.

What it looks like: The post fails with a "content too long" error. Only affects specific platforms when cross-posting.

Why it happens: Character limits vary significantly across platforms:

• X/Twitter: 280 characters (4,000 for X Premium)
• Instagram: 2,200 characters
• Facebook: 63,206 characters
• LinkedIn: 3,000 characters
• TikTok: 2,200 characters for captions
• YouTube: 5,000 characters for descriptions

How to fix it:

• When cross-posting, always customize the caption per platform rather than posting identical content everywhere.
• In PostEverywhere, the editor shows a live character count per platform and warns you before you exceed the limit.
• For X, write the short version first, then expand for longer-form platforms.

7. Banned Hashtags Triggering Review

Certain hashtags are flagged by platforms as spam, inappropriate, or associated with harmful content. Using even one banned hashtag can cause your post to be silently suppressed or held for review, making it look like the scheduled post never published.

What it looks like: The post appears to publish (no error message), but gets zero reach. In some cases, the post is held in a review queue and never surfaces. Instagram is particularly aggressive about this.

Why it happens: Platforms maintain constantly-updated lists of restricted hashtags. Some seem completely innocuous — hashtags like #adulting, #beautyblogger, and #pushups have been restricted on Instagram at various points.

How to fix it:

• Search each hashtag individually on the platform before using it. If a hashtag page says "recent posts are hidden," it is restricted.
• Reduce your hashtag count — 3-5 highly relevant hashtags outperform 30 generic ones on most platforms in 2026.
• Remove hashtags from the caption and add them as a first comment instead (supported on Instagram and TikTok).

Never get caught by banned hashtags. PostEverywhere flags restricted hashtags before you schedule. Try it free for 14 days.

8. Account Restricted by Platform

If a platform has restricted your account — temporarily or permanently — no scheduling tool can post on your behalf. Restrictions happen for policy violations, unusual activity patterns, or even by mistake.

What it looks like: All posts for one specific account fail, even after reconnecting. You may see "account restricted" or "action blocked" errors. When you log into the native app, you might see a warning banner.

Why it happens: Too many actions in a short period (mass following, mass liking). Content that violated community guidelines. Using unauthorized automation tools. Multiple failed login attempts triggering security locks.

How to fix it:

1. Log into the platform natively (not through a scheduling tool) and check for any warnings or notifications.
2. If there is a restriction, follow the platform's appeal process.
3. Wait out temporary blocks — most are 24-48 hours.
4. Avoid aggressive automation patterns. Use reputable social media scheduling tools with official API partnerships rather than tools that use browser automation or unofficial methods.

9. Timezone Mismatch

You scheduled a post for 9 AM, but it published at 9 AM in the wrong timezone — or it has not published yet because the tool thinks 9 AM has not happened yet in the timezone it is using.

What it looks like: Posts publish at unexpected times. A post scheduled for morning goes out in the evening. Posts seem to publish "late" consistently.

Why it happens: Your scheduling tool, your browser, and the platform might all be operating in different timezones. If you recently traveled or changed your system timezone, the mismatch can be subtle.

How to fix it:

• Check your timezone setting in your scheduling tool. In PostEverywhere, go to Settings and then Timezone to confirm it matches your target audience's timezone.
• If you manage accounts for audiences in different timezones, use a social media management tool that lets you set timezone per account rather than using one global setting.
• When scheduling, confirm whether the displayed time is in your local timezone or the account's timezone.

10. Scheduling Tool Outage

Sometimes the problem is not on the platform side — your scheduling tool itself is experiencing downtime. Server issues, deployment bugs, or infrastructure problems can prevent posts from being dispatched.

What it looks like: All posts across all platforms and accounts fail simultaneously. The tool's dashboard may be slow, unresponsive, or showing errors.

Why it happens: Server downtime, database issues, failed deployments, or third-party infrastructure problems (like AWS or Google Cloud outages).

How to fix it:

• Check your tool's status page. PostEverywhere's status page is at status.posteverywhere.com. Buffer, Hootsuite, and Later all maintain public status pages.
• If the tool is down, there is nothing to do except wait — and then check that your missed posts get rescheduled.
• For critical posts, have a backup plan: save the content and images locally so you can publish natively if the tool is down.

11. Platform API Downtime

Even if your scheduling tool is running perfectly, posts will fail if the platform's own API is down. This is distinct from the platform itself being down — the website and app might work fine while the API that third-party tools use is experiencing issues.

What it looks like: Posts fail for one specific platform across all accounts, while posts to other platforms publish normally. Your scheduling tool shows "API error" or "service unavailable" messages.

Why it happens: Platforms update and maintain their APIs independently from their consumer products. Meta's API has scheduled maintenance windows. X/Twitter's API has become less reliable since 2023. LinkedIn's API occasionally has unannounced downtime.

How to fix it:

• Check the platform's developer status page (separate from their consumer status page).
• Wait for the API to recover — most outages resolve within 1-4 hours.
• In PostEverywhere, failed posts due to API downtime are automatically retried every 15 minutes for up to 24 hours. Other tools may require you to manually reschedule.

Built to handle the chaos. PostEverywhere auto-retries failed posts and alerts you instantly. Start your 14-day free trial.

12. Post Flagged by Automated Review

Platforms use AI systems to scan content before and after publishing. If your post triggers automated review — for containing certain keywords, linking to flagged domains, or matching patterns associated with spam — it may be held indefinitely or silently suppressed.

What it looks like: The post shows as "published" in your scheduling tool, but it is not visible on the platform. No error message. Reach and engagement are zero. This is sometimes called a "shadow ban," though platforms generally deny this practice exists.

Why it happens: Your caption contains words flagged by content filters. The link you shared is on a blocklist. Your image triggered visual content moderation. Your posting pattern matches known spam behavior (posting identical content across many accounts simultaneously).

How to fix it:

1. Check the post natively on the platform — look for "under review" notices.
2. Remove potentially flagged elements one at a time: links first, then hashtags, then specific words.
3. If the post was suppressed silently, delete it and repost with modified content.
4. Avoid common scheduling mistakes like posting identical content across dozens of accounts simultaneously — this is a major spam signal.
5. Space out posts for different accounts by at least a few minutes.

Your Diagnostic Checklist

When a scheduled post fails, run through this checklist in order:

1. Check the connection. Is the account still connected with a valid token?
2. Check permissions. Does the connected user still have posting access?
3. Check the content. Are the media formats, file sizes, and character counts within limits?
4. Check the timing. Is the timezone correct? Has the scheduled time actually passed?
5. Check the platform. Is the platform's API up and running?
6. Check the tool. Is your scheduling tool's status page showing any issues?
7. Check the account. Is there any restriction or flag on the account itself?

Most failures are caused by item 1 — expired tokens. If you fix nothing else, set up proactive token refresh reminders and you will eliminate the majority of scheduled post failures.

The best way to avoid these problems entirely is to use a social media scheduler that handles token refresh alerts, automatic retries, format validation, and character limit warnings before you even hit schedule. That is exactly what we built PostEverywhere to do.

FAQ

Why did my scheduled Instagram post not publish?

The most common reason is an expired authentication token. Instagram (through Meta) expires tokens every 60 days. Go to your scheduling tool's settings, check if your Instagram connection shows a warning, and reconnect if needed. If the connection is fine, check that your image is in JPG or PNG format (not WebP or HEIC) and under 8 MB.

How do I know if my social media account token has expired?

Most scheduling tools display a warning icon or red badge next to disconnected accounts. In PostEverywhere, you receive an email alert 7 days before a token expires. You can also check manually by going to your connected accounts settings — if a reconnect button appears, the token has expired.

Do scheduled posts fail if my computer is off?

No. Scheduled posts are stored on your scheduling tool's servers, not on your computer. Once a post is scheduled, your computer, phone, or browser do not need to be open. The scheduling tool's servers handle publishing at the designated time. The only exception is if you are using the platform's native scheduling (like Instagram's built-in scheduler), which also runs server-side.

Why did my post publish at the wrong time?

This is almost always a timezone mismatch. Check the timezone setting in your scheduling tool and make sure it matches your intended audience's timezone. If you recently traveled or changed your device's timezone, your scheduling tool may have auto-updated. Also check whether your tool displays times in your local timezone or UTC.

How often should I reconnect my social media accounts?

Proactively reconnect every 50-55 days to stay ahead of the typical 60-day token expiration. Set a recurring calendar reminder or use a scheduling tool that alerts you before tokens expire. If you change your password on any platform, reconnect immediately — password changes invalidate existing tokens on most platforms.