Skip to content
← All articles
Instagram scheduler: limits that set your calendar

Instagram scheduler: limits that set your calendar

An Instagram scheduler cannot repair an account. Three things set what a calendar can actually deliver: whether the account is a professional account reached over a supported login path, which format path the media takes, and one posting cap that moves with a rolling 24-hour window. None of the three is a caption problem, and no composer setting changes any of them. I am PostSider’s founder, and this is the operating decision I would want made before the first post goes into a client’s queue.

For the social media manager running Instagram for a business or a client, not for a personal account.

In short

  • A professional account on the right login path is the entry ticket, and a Page that requires Page Publishing Authorization blocks publishing until that step is completed.
  • Meta documents the cap as 100 posts in a 24-hour moving period in one part of its guide and 50 in the carousel section, so read the account’s live usage rather than trusting either number.
  • An unpublished container expires after 24 hours, and a carousel crops every slide from the first image.

A professional account is the entry ticket

Instagram publishing starts with a professional account. A personal account has no publishing path, so the first question in any client onboarding is not about the tool at all. The second question is which login path the account is connected through, because the path decides the API host, the token type and the permission names that have to be present.

Three paths exist and they are not interchangeable. Instagram API with Unified Login sends publishing calls to graph.facebook.com and authenticates with a Business Integration System User token. Instagram API with Instagram Login sends the same intent to graph.instagram.com, using an Instagram User access token and the instagram_business_basic and instagram_business_content_publish permissions. Instagram API with Facebook Login uses a Facebook Page token carrying instagram_basic, instagram_content_publish and pages_read_engagement, and it also needs the ad permissions when the Page role was granted through Business Manager. Ask which path an account sits on before troubleshooting: a fix written for one path is noise on another.

Page Publishing Authorization sits on top of that. A professional account connected to a Page that requires PPA cannot be published to until PPA is completed, and no app can tell in advance whether a given Page requires it. Complete it preemptively instead of discovering it at the moment a launch post is due.

Formats change the payload, not the caption

The caption survives every format. What changes is the declaration and the fields the container will accept, and that mapping is the whole difference between a queued post and a rejected one.

FormatDeclared asWhat the payload expects
Single imageimage postJPEG only; alt_text supported since 24 March 2025
Videomedia type VIDEOresumable upload session on rupload.facebook.com for large files
Reelsmedia type REELSno alt_text support
Storiesmedia type STORIESno alt_text support
Carouselup to 20 childrenimages, videos or a mix; every slide cropped from the first image, default 1:1

One video payload is not another. Declaring VIDEO, REELS or STORIES sends the file to a different destination, so a file that looks correct in the queue can still land somewhere the brief never asked for. A large video can go up through a resumable upload session on rupload.facebook.com instead of a single transfer.

The cap is a moving window, and Meta’s own docs disagree on it

Meta’s content publishing guide states a limit of 100 API-published posts within a 24-hour moving period, enforced on the publish call, with a carousel counting as a single post. The carousel section of the same guide states a limit of 50 published posts per 24 hours. Both numbers are in Meta’s documentation, and they disagree. I am not going to guess which one your account is subject to, and neither should any calendar.

Two things follow. First, treat the cap as a window rather than a daily reset: posts fall out of it as they age, so yesterday’s burst still occupies capacity this morning and stops occupying it later in the day. Second, read the account’s current usage from the content_publishing_limit endpoint before filling a heavy week, and surface that usage in the queue. A hard-coded number is either too tight and wastes capacity, or too loose and promises posts the account cannot publish.

A container that is not published in 24 hours is gone

Publishing is two calls and a status check, not one. You create the container with POST /media, publish it with POST /media_publish, and read GET /?fields=status_code to learn whether the container is eligible. The statuses you will see are EXPIRED, ERROR, FINISHED, IN_PROGRESS and PUBLISHED.

FINISHED is readiness, not publication. IN_PROGRESS is not readiness at all. Meta recommends querying status once per minute for no more than five minutes, which is a bounded wait rather than a promise that processing completes inside it. When the wait runs out, the container is still the object of record, and retrying the publish without knowing its state is how a single scheduled post becomes two published ones.

The cliff is the expiry: an unpublished container is gone after 24 hours. Nothing in the queue is lost, because the file and the caption still sit in your database, but the processed container is not recoverable. That is the difference between a stalled post and a deleted one, and the queue should say which happened.

JPEG is the only supported image format, and extended JPEG variants such as MPO and JPS are not supported even though their filenames suggest otherwise. Shopping tags and filters are not supported either, so a design that relies on an in-app filter has to bake that look into the export. Check your exports against image sizes for each network before the assets enter a calendar.

Carousels carry their own rule. A carousel takes up to 20 images, videos or a mix, and every carousel image is cropped based on the first image, with a default 1:1 aspect ratio. The lead slide is the shape the other slides inherit, so its aspect ratio governs the set. A 4:5 lead with 16:9 followers means the follower slides are cropped to the lead, not to the ratio they were exported at.

Alt text has a format boundary too. The alt_text field was introduced for image posts on 24 March 2025 and is not supported for Reels or Stories, so accessibility work on those two formats happens somewhere other than the API payload.

What the queue should own, and what it should refuse

The queue owns everything that surrounds the call. Media has to sit on a publicly accessible server at the moment of the attempt, because Meta fetches the URL itself, and “public when you queued it” is a different guarantee from “public when it publishes”. A signed link that expires overnight is a supported file at upload time and an unreachable one at publish time.

Before anything is queued, a per-platform preview is the cheapest check in the system. PostSider’s composer shows that preview, including the crop each network will apply, and it holds a first-comment field for the tags or links that should not sit inside the caption. Reading the actual crop is different from reading the dimensions, and it is the step that catches a bad crop before it reaches the client.

Refusal is the queue’s other job. Approval is a state, and a post in the APPROVAL state refuses status and date changes until an admin-level action resolves it. That refusal is the feature: a calendar where dates can be moved around an unresolved approval is a calendar that publishes copy nobody signed off on.

When a post still does not come out the way the composer promised, keep the diagnosis short and move to the right layer. The publishing error runbook maps a symptom to the failing layer, whether that is the login path, the permission grant, media retrieval or the container state, and it does that without repeating the operating rules above.

A weekly Instagram calendar you can keep

Monday is the only day that needs a real check. Everything after it is cadence.

  1. Read the account’s publishing usage from the content_publishing_limit endpoint before filling the week, since the window is moving and last week’s burst may still count against it.
  2. Confirm the Page’s authorization status at onboarding, not on the day a post is due.
  3. Preview every carousel first, because the lead image decides the crop on all 20 slides.
  4. Keep formats on separate slots. A Reel, an image post and a Story are three payloads, and a late change to one leaves the others alone.
  5. Resolve anything sitting in APPROVAL before the week’s slots are promised to a client, since status and date changes are refused until an admin acts.
  6. If a post does not appear, read the container status before retrying, then take the symptom to the runbook instead of rebuilding the post.

Channel count is the other number worth planning against. PostSider’s plans run from Standard at $20 a month for 5 channels through Team at $35 for 10, Pro at $45 for 30 and Ultimate at $90 for 100, with unlimited team members from Team upward and a seven-day trial that does not ask for a card. The Instagram scheduler holds the calendar itself. The eligibility rules, the payload each format demands and the moving cap decide only what fits in it.

Frequently asked questions

Can I schedule posts for a personal Instagram account?

No. Publishing runs only for professional accounts, meaning business or creator accounts, reached through one of the supported login paths. A personal account has no publishing permissions to grant, so connect the professional account the brand actually posts from.

How many posts can one Instagram account publish in a day?

Meta's content publishing guide states 100 API-published posts in a 24-hour moving period, enforced on the publish call, and the guide's carousel section states 50 published posts per 24 hours. Because the two numbers disagree in Meta's own documentation, read the account's current usage from the `content_publishing_limit` endpoint rather than hard-coding either one.

Why did a scheduled Instagram post disappear instead of publishing?

The container most likely expired. A container is created first and published second, and an unpublished container expires after 24 hours. Meta recommends checking the status once per minute for no more than five minutes, so a publish attempt that stalls past that window leaves an EXPIRED container behind rather than a post.

Why does my carousel crop differently from the files I uploaded?

Every carousel image is cropped based on the first image, with a default 1:1 aspect ratio. The first slide sets the shape for the rest, so a landscape lead image changes how the following slides are cropped. Check the crop in a per-platform preview before the carousel is queued.

Can I schedule alt text with an Instagram post?

For single image posts, yes. The alt_text field was introduced for image posts on 24 March 2025. It is not supported for Reels or Stories, so those formats publish without it.

Let your AI post
to social media for you.

Connect your accounts, add PostSider to your AI and publish your first post in a few minutes.

7-day free trial · 30+ networks · No credit card · Cancel anytime