Social Hub has a known issue where failed scheduled posts generate no email or in-app notification, and posts that fail due to an expired or revoked account connection are never automatically retried. Check your Social Hub dashboard for any posts showing **FAILED** status and follow the steps below to republish them.

## What's Happening

Two related issues currently affect scheduled posts in Social Hub:

- **No failure notifications.** When a scheduled post fails to publish, Social Hub does not send any email, in-app, or push notification. The only way to discover a failed post is to open the Social Hub dashboard manually and look for posts marked **FAILED**.
- **Auth-related failures do not auto-retry.** If a post fails because your connected social media account has an expired or revoked token (an authentication error or refresh token error), the system permanently excludes that post from its automatic daily retry. The post remains in **FAILED** status indefinitely and will not publish until you take manual action.

Posts that fail for non-authentication reasons may be retried automatically by the system within two days. Auth-related failures will not retry until you reconnect the affected account.

## Workaround Steps

Follow these steps to identify and republish any stuck posts:

1. Open your **Social Hub** dashboard and look for any posts showing a **FAILED** status.
2. Click the failed post to review the failure details.
3. If the failure reason shows an authentication or token error, go to **Settings → Connected Accounts** and reconnect (re-authorize) the affected social media account.
4. Once the account is successfully reconnected, return to Social Hub and manually reschedule or republish the failed post.

After completing step 4, your post will be queued and published using the refreshed account credentials. Posts that failed for non-auth reasons and have not retried within two days should also be manually rescheduled to guarantee delivery.

## Engineering Status

Our engineering team is aware of both issues — missing failure notifications and the permanent exclusion of auth-related failures from automatic retry — and is actively working on a fix. This article will be updated as soon as a resolution is deployed. We apologize for any disruption to your publishing workflow.

## When to Contact Support

Reach out to Search Atlas Support if any of the following apply:

- You have reconnected your social media account but the post continues to fail after rescheduling.
- The failure details do not show an authentication error, and the post has not been automatically retried within two days.
- You are unable to reconnect the affected account through **Settings → Connected Accounts**.

## Related Issues

If you are experiencing related problems, please also review:

- **SHUB-40 (OAuth token handling)** – If your account shows "Not Connected" or you cannot authorize it, see the reconnection steps above.
- **SHUB-48 (Calendar visibility)** – If posts are not displaying in your calendar after publishing, check whether the account reconnection in this article resolves the display issue.

**Our engineering team is actively working to restore full notification and automatic retry functionality in Social Hub. In the meantime, reconnecting your social media account and manually rescheduling any **FAILED** posts will get your content published — and our support team is here if you need a hand.**