Guide

Why did my Instagram post fail to publish? Every error, decoded

An Instagram post can fail because the file is incompatible, Instagram cannot download it, your connection lost permission, the media is still processing, or the account hit a publishing restriction. The useful clue is the full error message and, for a scheduler, its code and subcode. Start by checking whether the post is already live. Then fix the cause before you retry.

This guide covers both a failed upload in Instagram and a scheduled post that Instagram refused. They use different publishing paths. A photo that works in the Instagram app can still fail through a scheduler, and a scheduler's API error does not necessarily explain a spinner in the native app.

First, check the destination, time and actual post

  1. Open the intended Instagram profile. Check the feed and Reels tab, or Stories if that was the destination. If you manage several accounts, confirm the handle. A timeout can mean the scheduler missed Instagram's reply after Instagram accepted the post.
  2. Read the status for Instagram itself. A cross-post can succeed on Mastodon and fail on Instagram. A missing first comment is also different from a failed post. If the post exists, fix the comment separately.
  3. Check the scheduled time and approval status. A draft, a post awaiting approval, or a schedule in another timezone has not necessarily reached Instagram. A future post needs a schedule correction, not an upload repair.

Save the complete error text, the time with timezone, the account handle and the post's identifier in your scheduler. In PostBaton, open Failed deliveries for the reason and reference code. The failed-post help page explains the statuses and the Retry button.

Match the complete Instagram error, including its subcode

Meta can return a broad code plus a more specific subcode. Copy both. A plain “400” or “could not publish” is not enough to distinguish a file problem from a permission problem. The examples below come from Meta's Instagram error reference; a tool may display its own reference instead.

Common Instagram publishing errors and the next action
Code / subcodeMeaningNext action
9004 / 2207052Media URL fetch failed.Check the download link without signing in.
-2 / 2207003Media download timed out.Check file hosting and transfer speed.
9007 / 2207027Media is not ready.Wait for processing to finish.
24 / 2207008Container is missing or expired.Have the tool check or recreate it.
36000 / 2207004Image is too large.Export a smaller JPEG.
36001 / 2207005Image format is unsupported.Convert the actual file to JPEG.
36003 / 2207009Image shape is unsupported.Crop or pad the image.
352 / 2207026Video format is unsupported.Re-export the video.
36004 / 2207010Caption is too long.Shorten the final submitted caption.
9 / 2207042Publishing quota reached.Wait for quota to become available.
4 / 2207051Suspected spam.Stop repeated sends and check the account.
25 / 2207050Account is restricted.Resolve the prompt inside Instagram.
-1 / 2207001Instagram server error.Check whether it posted, then retry later.

This is a diagnostic map for common failures, not a promise that every Instagram response fits a known row. If your code is absent, keep its message intact and use the sections below. Do not substitute another tool's code just because its wording looks similar.

1. The photo is the wrong format, size or shape

For API publishing, Meta documents JPEG images up to 8 MB with an aspect ratio between 4:5 and 1.91:1. These are upload requirements for this path, even if Instagram's own app accepts your original. See the current Meta media reference.

A practical repair is a square JPEG exported at 1080 by 1080 pixels. For a portrait feed image, try 1080 by 1350. Keep the original, then export a new copy. Renaming photo.heic to photo.jpg does not convert it. Open the exported file to confirm it is readable before attaching it again.

A tall screenshot can be padded onto a square canvas if cropping would cut off the words. Exporting at maximum quality can leave an unnecessarily large file, so reduce quality or dimensions if the error names file size. Change one property at a time when diagnosing a recurring failure.

In PostBaton, ig_image_required means the post has no media; a caption alone cannot publish to Instagram. ig_image_format means the file could not be supplied as a supported JPEG. ig_aspect_ratio names the shape problem. The media requirements guide explains the conversion and preparation PostBaton performs.

2. Instagram cannot fetch the media URL

When a scheduler submits a media URL, Instagram downloads that file from its own servers. The URL must remain accessible during that process. A link that works in your signed-in browser can still fail for Instagram. Meta describes this URL-based flow in its content publishing guide.

For a link you control, test it in a private browser window. It should return the media file, not a login page or a sharing-page preview. Check whether it expires before the scheduled publishing time. Hosting logs can help distinguish a request refused with 403 from a missing file returning 404 or a slow download.

If the scheduler owns the upload, send its support team the failure time and post identifier. Ask them to check the media URL's availability when Instagram requested it. You should not need to make an entire private storage bucket public to repair one post. Reattaching the file can be a useful fresh-upload test, but repeated uploads will not repair a hosting configuration problem.

3. The Reel needs a different export

An MP4 extension describes the container, not everything inside it. The video codec, audio codec and export settings also matter. Meta's media reference lists MP4 or MOV, H.264 or HEVC video, and AAC audio for Reels. A 9:16 frame is recommended, rather than a universal requirement for every accepted Reel.

For a repair attempt, export a fresh MP4 using H.264 and AAC with a standard preset in your editor. Play the exported file from beginning to end. Confirm its duration and file size against the current media reference and your scheduler's own limits before uploading it.

If a simple test clip works but the campaign video fails on the same account, focus on the export. If every clip fails with an authentication message, focus on the connection. This comparison is more useful than changing the caption, reconnecting and re-exporting all at once.

4. The media is processing, or its container expired

A scheduler can create an Instagram media container before the media is ready to publish. Meta exposes statuses including IN_PROGRESS, FINISHED, ERROR, EXPIRED and PUBLISHED. An unpublished container expires after 24 hours. The content publishing guide documents this lifecycle.

“Not ready” calls for checking processing status. It does not automatically mean your account disconnected. Let the scheduler finish its current attempt. If processing ends in an error, keep that error and inspect the file. If the container expired, the tool must create a fresh container from accessible media before publishing.

For a recurring “not ready” failure, ask support whether the tool waited for FINISHED and what status it read afterward. That gives them a concrete investigation. Creating another copy of the scheduled post while the original is still processing makes the result harder to track.

5. One carousel item fails, or the tool supports fewer items

Check every attachment, including the last slide. If one file differs in format or export settings, make a consistent replacement. Also confirm that you selected a carousel rather than a single-image post or Reel.

Meta's current media reference supports up to 20 carousel items, while PostBaton currently accepts 2 to 10. A larger album working inside Instagram does not make it valid in PostBaton. For ig_too_many_carousel_items, reduce the set to 10 or fewer. Other schedulers may have their own supported counts.

Preserve the intended slide order when replacing files. If you split a large album, review each resulting caption as well, so the second post does not tell readers to swipe through slides that belong to the first.

6. The connection expired or lost permission

A connection that worked last week can lose access. In Meta's Graph API error handling guide, codes 190 and 102 concern invalid or expired authentication. Codes 10 and 200 through 299 concern permissions.

Reconnect the affected account through your scheduler's normal connection screen. Sign in as the person who can authorize that Instagram account, review the permissions requested, and select the intended profile. Then confirm the handle shown in the scheduler before retrying the failed delivery.

If reconnecting succeeds but publishing is still refused, give support the new error. They may need to distinguish an account permission from the app's own access. Repeating the same consent flow cannot fix an application that lacks approval for the operation it is attempting.

7. The account type or login path is wrong

Instagram API publishing requires a professional account, Business or Creator. Posting normally from a personal account does not establish that a scheduler can publish for it. Meta offers different connection paths, so use the instructions for the one your tool actually uses.

PostBaton's Instagram connection instructions explain its setup. A Facebook Login integration can have different setup requirements from Instagram Login. Do not create or relink Facebook Pages merely because an unrelated troubleshooting article assumes the other flow.

PostBaton's Instagram connection is still awaiting Meta approval for general availability. This guide also helps readers using other tools or the Instagram app. Existing review or test access does not establish that a new customer can connect Instagram today.

8. Publishing quota, throttling or an account restriction

Quota and request throttling need different remedies. A publishing quota is an allowance over a time window. Throttling concerns requests. A spam or account restriction may require action inside Instagram. Read the subcode before treating all three as “try again.”

For a quota error, ask the tool to check the account's content_publishing_limit, including quota_usage and config.quota_total. Meta exposes those fields in the publishing-limit reference. Use the reported allowance rather than an old article's fixed daily number. Spreading posts across a day does not create more quota within a rolling window.

For a restriction or suspected-spam response, stop repeated sends. Open Instagram and check for a security prompt or account-status issue. Follow the resolution Instagram provides. Reconnecting a scheduler does not itself remove a restriction imposed on the account.

9. The caption or requested feature is rejected

Inspect the caption actually sent to Instagram, including a saved signature, hashtags or text added by automation. If the error says it is too long, shorten that final version. An editor's visible draft may differ from the submitted text.

If an error names a tag, location or another optional field, remove that field in a saved revision and try the supported form. Features available inside Instagram, including some music and editing options, do not necessarily have an equivalent in your scheduler. Check the tool's supported features before rebuilding the same unsupported request.

10. The Instagram app itself will not upload

If you are posting directly in Instagram, start with a different test: save your caption and original file, then check whether a simple photo uploads using a stable connection. If possible, compare Wi-Fi with mobile data. Update the app and check whether it has access to the selected photo or video.

If a simple photo works, return to the original file and its edits. If uploads fail across files and networks, look for an account prompt or a broader service problem. Keep a screenshot and report the issue through Instagram. Avoid clearing app data or reinstalling until you have saved anything you need from local drafts.

A native-app spinner does not expose a Graph API subcode. Do not diagnose an expired scheduler token from that symptom alone, or assume a post is published just because the upload progress completed.

Fix the cause, then retry the failed destination

Before resending, look on Instagram once more. A post accepted during a timeout may appear after the scheduler labels the attempt unsuccessful. If you published a replacement manually while investigating, record its link and deal with the original queued delivery so it does not later create another copy.

In PostBaton, fix the stated problem, open Failed deliveries, and press Retry on the affected delivery. Other destinations that succeeded do not need another send. PostBaton checks recent Instagram posts for matching text before retrying. That reduces duplicate risk but cannot rule it out: a newly accepted post may not yet appear in Instagram's readback. See how retry checks work and why social schedulers can double-post.

If it fails again, send support the full error, code and subcode, account handle, scheduled time with timezone, file format and dimensions, and what you changed. Include whether the post appears on Instagram. Keep passwords, access tokens and private media download links out of a public support thread.

Choose a scheduler that makes the next action clear

When comparing tools, look for a reason on each failed destination, a visible final failure, and a documented retry process. A checkmark for “Instagram support” does not answer what happens after a timeout.

For PostBaton's capabilities and current limits, read PostBaton vs Buffer and the pricing page. You can start with the networks available to your account today and see delivery results in the same workspace.

Start scheduling free