Publishing Failures

Occasionally, a scheduled post may fail to publish. SoSocial provides clear error information and automatic retry mechanisms to help resolve these issues.

Checking for Failed Posts

Go to Posts from the sidebar.
Look for posts with a Failed status badge.
Click on the post to see the error message explaining what went wrong.

Common Causes

Expired Access Token

Social platform tokens can expire, especially if you haven’t used the connection recently. Facebook and Instagram tokens may expire after extended periods of inactivity.

Fix: Go to Settings, disconnect the affected platform, and reconnect through OAuth to get a fresh token.

Media Issues

Posts can fail if the attached media doesn’t meet the platform’s requirements:

File too large — Each platform has its own size limits.
Unsupported format — Ensure you’re using supported formats (JPG, PNG, GIF, WebP for images; MP4, MOV for video).
Corrupt file — Try re-uploading the media.

Fix: Check the platform’s media requirements and re-upload compliant files.

Platform API Rate Limits

If you publish many posts in a short period, the platform’s API may temporarily throttle requests.

Fix: Wait a few minutes and the post will be retried automatically, or manually republish from the Posts page.

Network Issues

Temporary network problems between SoSocial and the platform’s API can cause transient failures.

Fix: These usually resolve on their own with automatic retries.

Automatic Retry System

SoSocial automatically retries failed posts up to 3 times with exponential backoff:

First retry: after 1 minute
Second retry: after 2 minutes
Third retry: after 4 minutes

If all three retries fail, the post is marked as Failed with the error message from the last attempt.

Safety Net

A background process runs every 5 minutes to catch any posts that were missed or stuck. If a post should have been published but wasn’t, this safety net picks it up and attempts publishing.

Still Failing?

If a post continues to fail after retries, check the Logs page for detailed server-side error information. If the issue persists, create a support ticket from Account > Support with the post details and error message.