When a post fails or the account disconnects

A post that did not go out says so. Open the Social Hub and click the red Failed chip above the timeline to see only those. Each card carries the reason Facebook or Instagram gave, which is what tells you what to fix.

A failed post filtered on the timeline, showing the failure reason in red with Retry and Delete buttons — The reason is on the card. Fix that first — Retry on its own just repeats the failure.

Match the message to the cause

“No Instagram Business account is linked”

The Facebook Page you are connected to has no Instagram professional account attached, so there is nowhere for an Instagram post to go. Link a Business or Creator account to that Page in your Meta settings, then reconnect in Hubl so it looks again. Full steps in Connect Facebook and Instagram.

“Facebook connection is no longer valid”

The stored access has been revoked or has expired. This usually follows someone removing Hubl from the Page’s connected apps, or the person who connected it losing their own admin rights on the Page. Reconnect — see below.

“Processing timeout”

The post got stuck part-way through publishing and Hubl gave up after ten minutes. Almost always a transient problem at Meta’s end. Check the Page first, then retry: a timeout can mean it published and Hubl never heard back.

“Expired”

The post’s time passed more than six hours ago without it publishing, so Hubl stopped trying rather than surprising your followers with yesterday’s notice. This is what you find after a connection was broken for a day. Decide whether the post is still worth sending; if it is, edit the date and retry.

Anything else

Other messages come straight from Facebook or Instagram, most often about the content itself — an image the network refused, or a caption it would not accept. Change what the message names, then retry.

Retry safely

Open the Page first

Before retrying anything, look at your actual Facebook Page or Instagram profile. If the post is already there, do not retry: delete the failed card in Hubl with Delete instead. Retrying a post that quietly succeeded is how the same notice ends up published twice.

Fix the cause

Reconnect, link Instagram, change the image — whatever the message named. Retrying before the cause is fixed just produces the same failure a few minutes later.

Retry once

Retry puts the post back in the queue for the next run, within about fifteen minutes. It does not publish instantly, so give it that long before pressing anything else.

Warning

Do not press Retry and then also Post now on the same post. Both send it; together they can send it twice.

Reconnect the account

Check the connection's health

Open Settings → Integrations. Hubl checks the connection on every load. Active means it works. Needs reconnection in red, with a line explaining it, means it does not.

The Facebook Page integration card showing Connected alongside a red Needs reconnection badge and an explanation — Connected and working are two different things. The second badge is the one that matters.

Connect again

Click Connect and go through the Facebook authorization again with an account that administers the Page. You do not need to disconnect first, and scheduled posts survive it. Use Re-check afterwards to confirm the badge turns Active.

Note

Connecting needs the Manage integrations permission, which the Communications Team role does not include. If the buttons are greyed out, this is a job for an administrator rather than your social media volunteer.

A post that never appeared at all

Nothing on the timeline and nothing on your Page usually means one of:

It is still a draft. Campaign posts show as Draft until the campaign is scheduled. Open the campaign and use Schedule these posts — see Promote an event with a campaign.
It was cancelled. Filter the timeline by Cancelled. Cancelling a campaign stops every post it had left.
It went to a different Page. If someone used Change Page, posts after that point went to the new one. The Social Hub header names the Page you are posting to.

A campaign with failures

A campaign card showing N failed means some of its run did not go out. Open it, fix the underlying cause once, and retry the failed posts from the Social Hub timeline. Fixing the connection does not automatically re-send what failed while it was broken.

Tip

Evergreen queues tell you rather than waiting to be found: organization administrators get an in-app alert when an evergreen post fails, and email alerts can be switched on in the queue’s settings.