MB SuiteMB Suite

My post wasn't published or my account got disconnected

Updated 2026-08-03

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 red banner in the post's drawer inside 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: before telling you anything, we run 3 automatic retries spaced apart. Many temporary network glitches resolve themselves in that window, and you never even find out.

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 file doesn't meet the platform's requirements — format, duration or size. Swap the media for one that matches the network's specs and retry.
  • The content doesn't meet the platform's rules — usually text length or a field the network requires. Adjust the post and retry.
  • 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. Retry the publication.
  • 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 Revisar y reintentar instead of the usual retry — a blind retry can publish the same content twice.

How you resolve it from the planner

  • Open the failed post in the Planner. The banner at the top of the drawer states the reason and which networks failed.
  • If the cause is the connection or a missing permission, press Ir a Integraciones — the button takes you straight to the integrations screen to reconnect.
  • If the cause is the file or the content, fix the post right there in the drawer.
  • Press Reintentar publicación. Only the networks that failed are republished — the ones that already went out aren't touched.
  • If it fails again, we notify you again with the new reason. You won't be left in the dark after a retry.
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 Lista 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.

You got no notice and the post never went out

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 Pending 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.