Back to Troubleshooting

Why a Post Wasn't Published

Beginner
3 min read
Updated 2026-04-13

If a scheduled post didn't go live at its planned time, the most common causes are platform connection errors, content policy violations flagged by the platform, or approval workflow issues. Here's how to diagnose and resolve each.

How to Find a Failed Post

Navigate to: Dashboard → Content Calendar

Filter by Status → Failed or Status → Pending (Overdue) to find posts that didn't publish as scheduled.

Click on any failed post to see its detail panel. The Status Reason field will show a brief explanation of why it didn't publish.

Cause 1: Platform Connection Error

What you'll see: Status reason shows "Platform disconnected" or "Authorization failed."

What happened: The connection between Aibrify and the platform expired or was revoked before the post's scheduled time.

Fix:

1. Go to Dashboard → Settings → Connected Platforms and reconnect the affected platform

2. Once reconnected, return to the failed post

3. Click Reschedule and choose a new time

4. Your team will be notified and can assist with rescheduling if needed

See the full guide: Troubleshooting Platform Connection Issues.

Cause 2: Content Policy Violation

What you'll see: Status reason shows "Rejected by platform" or "Content policy violation."

What happened: The social media platform's automated content moderation system flagged or rejected the post at publish time. This can happen due to:

- Image content containing text that the platform's policy restricts

- Caption language that triggers spam filters

- Hashtags that have been banned or restricted on the platform

- Links to URLs that the platform considers low-quality or spammy

Fix:

1. Your team will be automatically notified when a post is rejected by a platform

2. They will review the post and the platform's rejection reason

3. The post will be revised and rescheduled — your team will message you if they need guidance on the revision

If you believe the rejection was in error (false positive), message your team — they can request a manual review in some cases.

Cause 3: Post Awaiting Approval

What you'll see: Status shows "Pending Approval" and the scheduled time has passed.

What happened: The post was waiting for your approval and wasn't approved before its scheduled publish time. Aibrify does not publish content without your approval.

Fix:

1. Go to Dashboard → Content Calendar

2. Find the post (filter by "Pending Approval")

3. Review the content and click Approve if it's ready

4. Your team will then reschedule it for the next appropriate time

To avoid this in future: When your team submits content for review, you'll receive a notification. Aim to review pending content within 24–48 hours to avoid scheduling delays. You can adjust notification preferences in Account Settings → Notifications.

Cause 4: Platform-Side Technical Error

What you'll see: Status reason shows "Platform error" or "Temporary service unavailability."

What happened: The platform experienced a technical issue on their end (outage, API error, rate limiting) at the exact time the post was scheduled.

Fix: These errors are almost always temporary. Your Aibrify team monitors for these automatically and will reschedule the post within the same day when the platform recovers. No action is needed from you, but you'll receive a notification when the post is rescheduled.

Cause 5: Account Restrictions

What you'll see: Status reason shows "Account restricted" or "Publishing not permitted."

What happened: The social media account has been restricted or flagged by the platform. This can be due to platform policy violations unrelated to Aibrify, temporary account holds, or unpaid advertising balances (on some platforms, ad account debt can restrict organic publishing).

Fix:

1. Log into the affected social media platform directly and check for any alerts or restriction notices

2. Resolve the issue directly on the platform (this often requires submitting an appeal or clearing an outstanding balance)

3. Once the restriction is lifted, message your team to resume scheduling

Reviewing the Post History

Every post in your content calendar has a History tab in its detail panel. This shows a timestamped log of every status change — when it was drafted, submitted for review, approved, attempted for publishing, and the result. This is useful for understanding exactly when and why a post failed.

Frequently Asked Questions

Will my team automatically reschedule a post that failed to publish?

For platform technical errors, yes — your team reschedules automatically. For connection errors or posts awaiting approval, your team will notify you and may need your input before rescheduling. Check the Status Reason on the failed post for context.

Can I publish a post immediately after fixing a connection error?

Yes. After reconnecting the platform, find the failed post in the Content Calendar, open it, and click "Reschedule." You can choose a time as soon as 15 minutes from now. Your team will be notified and can also reschedule it on your behalf.

troubleshootingpost not publishedfailed postplatform errorcontent calendar

Was this article helpful?

Still have questions?

Our support team is here to help