MB SuiteMB Suite

My post wasn't published or my account got disconnected

Updated 2026-10-07

In two lines: you don't have to hunt for the problem — if a scheduled post fails, we notify you with the reason and the action that fixes it. This article helps you interpret that reason and get the post out.

How you find out

When a scheduled post fails — on every network or just some of them — we notify you through three surfaces at once: an email with the reason and a link to the post, an in-app notification in the bell, and a banner at the top of the post when you open it in the Planner. Successful publications don't send email: no news is good news.

The notice goes to whoever created the post. If that person is no longer a member of the account (for example, a post created by someone who left the team), it escalates to the owners and admins so it never goes unnoticed.

The notice isn't instant on purpose. When the failure looks temporary —the network couldn't download your file, or its processing fell over— we retry on our own, uploading the file again and spacing each attempt out, up to 3 tries. Many of those glitches resolve themselves in that window and you never even find out. When the network rejects the file or the content outright, we don't retry —it would fail the same way— and we tell you right away. When there was more than one attempt, the closing line of the email tells you how many.

What each reason means

The email, the bell and the banner always show the same reason. These are the ones you can act on:

  • The connection is no longer valid — the account's access to the platform stopped working. Reconnect it from Configuration > Integrations and the post goes out on the retry.
  • A permission is missing on the connection — the connection is alive but lacks a permission needed to publish. Reconnect the account granting all requested permissions.
  • The network account is restricted or has a pending verification — the network (for now, Instagram) rejected the publication because of the account's status, not the connection or the file. Sign in to the Instagram app with that account, check Account Status, complete whatever it asks for and then retry. No need to reconnect in MB Suite — but until it's resolved, upcoming posts on that network will fail too.
  • The file doesn't meet the platform's requirements — format, aspect ratio, duration or size, and the network said so explicitly. We don't retry this one on our own, and retrying from the planner won't fix it either: the retry re-sends the same file. Publish the content again in a new post, with a file that matches the network's specs. On LinkedIn this reason also shows up when the post carries something LinkedIn doesn't publish —a video with other files, or more than 20 images—: we stop it before sending anything, so nothing goes out trimmed, and the line underneath tells you which case it is. Move the video to its own post, or remove the extra images, and publish again.
  • The content doesn't meet the platform's rules — usually text length or a field the network requires. The retry re-sends the same text, so publish it again in a new post with the text adjusted.
  • Publishing was temporarily limited — the network throttled your account. Nothing to fix: retry in a few minutes.
  • There was a temporary error on the platform — the failure is on the network's side, not in your post. This is also where a file the network couldn't download lands. We retry these on our own; if the notice reached you anyway, retry the publication with the same file.
  • We didn't receive confirmation within 1 hour — we sent the post but the network never confirmed it. Read the warning below before retrying.
When the reason is that we didn't get confirmation within 1 hour, check the network before retrying: the post may have gone live anyway. That's why in that case the button reads Review and retry instead of the usual retry — a blind retry can publish the same content twice.

The line under the reason: what the network replied

The reason above is our reading of the failure. Right under it, both the banner and the email show the network's own words, verbatim, under the line What Instagram replied: — with the name of the network that failed. It's short, technical and usually in English —the platform writes it, not us— and it's the piece that tells you whether the problem is your file or the network's moment.

  • It's your file — the message names a concrete property: the format, the aspect ratio, the size, the duration. Something in the vein of unsupported video format or aspect ratio not supported. That same file will fail again, even on a retry: publish the content with another file — in the same post if it's Failed (swap the file and publish it again), or in a new post if it's Partial.
  • It's the moment, not your file — the message talks about fetching, downloading, processing, or a server error; for example the media could not be fetched from this uri. Your file is fine: the network couldn't pick it up. We already retried on our own, so if the notice reached you anyway, retry from the planner with the same file.
Before you can schedule, the composer already checks your file against that network's requirements and blocks the post if something doesn't fit —There are media errors blocking publishing—. So if the post did get scheduled and then failed, your file had already passed that check: read the network's line first, before you go hunting for a problem inside the video.

How you resolve it from the planner

  • Open the failed post in the Planner — from the calendar, the board or the list. The banner at the top of the post states the reason and which networks failed.
  • If the cause is the connection or a missing permission, press Go to Integrations — the button takes you straight to the integrations screen to reconnect.
  • If the cause is the file or the content, don't retry: Retry publication re-sends exactly the version that failed. What you do next depends on whether anything went out. Failed (it didn't go out on any network): fix the post right there and publish it again with Schedule Post or Publish Now — while you have unsaved changes the retry button is disabled, precisely so the old version doesn't go out. Partial (it already went out on other networks): the post can't be edited; create it again with New Post, with the corrected file or text, and schedule it.
  • In every other case —once you've reconnected, if that was the cause—, press Retry publication. Only the networks that failed are republished — the ones that already went out aren't touched. On a Story post with several images or videos, only the stories still missing go out.
  • If it fails again, we notify you again with the new reason. You won't be left in the dark after a retry.
You can also retry without opening the post: in the calendar, the card menu has Retry; on the board, the card's action bar shows a circular-arrow button; in the list view, the row menu. All of them do the same thing as the banner button.
Retrying a publication requires full access to the Social Planner module. If you have read-only permissions you'll see the banner and the reason, but not the retry button — ask an admin on your team.
In the list view, the network icons of a failed post turn red and each one carries a tooltip with its own reason. It's the fastest way to spot whether several posts failed for the same cause — a sign the problem is the connection, not the content.

Some stories of the sequence went out and others didn't

A post in Story format with several images or videos publishes one story per file, one after another. If the sequence gets cut off midway, the post doesn't land on Failed: it lands on Partial, because there are already stories live on the account. The banner tells you exactly where it stopped — On Instagram, 1 of 4 stories went live and story 2 failed — with the reason right above it, and the email and the bell carry the same detail.

If the reason is outside the post —the connection, the account's status, a network hiccup— resolve it and press Retry publication: only the stories that were missing go out, picking up the sequence where it stopped. The ones already live are never published again, so the account doesn't end up with duplicates. If the reason is the file or the text, the retry would send those same stories again: publish the missing ones in a new Story post.

The stories that already went out stay published, even if you cancel the publication: Meta doesn't allow deleting them from MB Suite. If that content shouldn't be live, take it down from the Instagram app or from Meta Business Suite —stories expire on their own after 24 hours—. The conditions that apply to your use of MB Suite and to what you publish on the platforms are described in our Terms of Service.

You got no notice and the post never went out

If the post is in Publishing, it hasn't failed: it's still in progress. With a video —on Instagram, TikTok or LinkedIn— the network processes the file before the post goes live, and that can take a few minutes; it's also where a post waits while we retry it on our own after a temporary glitch. It moves on by itself, and if something fails, you get the notice with the reason.

If there was no failure notice at all, the post probably never got to the point of being published. Check these three causes in order.

If in Settings > Integrations the platform shows a Pending permissions chip or an expired-connection warning, the post won't go out until you renew the access. See Reauthorize an integration.

Did the post reach the Approved status and get scheduled?

A post in Draft or under review —Internal Review, Client Review— doesn't publish on its own. Make sure it's Approved and scheduled with a future date and time. If the date already passed while it was under review, schedule it again.

Is the format compatible with the platform?

Each network has its requirements. If the format or size don't meet that platform's specifications, the post may fail. See Formats and requirements per platform.

If several posts fail on the same network, the problem is the connection, not each post. We also warn the owners and admins that upcoming publications will keep failing until the account is reconnected — see Reauthorize an integration.

Still have questions?

Ask MIA, the MB Suite AI assistant: open it with the MB AI button (⌘J) in the top bar. MIA knows the section you're in, so you can ask it about what you see on screen — and it can also answer how-to questions about using MB Suite.