Publish & grow
Fix held, failed, and stuck publishing posts
Read a post's status, resolve connection and media failures, and retry safely without creating duplicate sends.
Updated
Start with the post, not a new copy
Open the post in the Review queue under the correct brand. Record its destination, status, scheduled time, and full error or hold message. A missing live link, an unfinished send, and a failed send are different situations.
| What you see | First action |
|---|---|
| Draft | Review and approve it if it is ready. |
| Approved or Scheduled | Check publish mode, due time, connection, and any hold reason. |
| Held | Resolve the reason shown; it is a pause, not a completed failed attempt. |
| Publishing | Wait for the attempt to finish and refresh its status before retrying. |
| Failed | Fix the cause, then use Retry publish or reschedule. |
| Published | Open the destination when a link is available and inspect the actual result. |
Resolve common holds
- Daily limit reached: wait for a later pass, adjust the cadence, or assign an explicit schedule if that is your intent.
- No account connected: reconnect the intended destination and confirm its brand assignment.
- Missing destination detail: choose the Pinterest board, community, channel, list, or other required field on the post.
- Missing explicit review choice: complete TikTok privacy and disclosure fields or the corresponding YouTube audience fields for an eligible preview account.
- Off publish mode: inspect the queue, then return the brand to Review when automatic publishing should resume.
Resolve common failures
| Error category | What to fix |
|---|---|
| Expired or revoked authorization | Reconnect the same account in Connections; include the required Page or permissions. |
| Too many media items | Reduce the actual set or choose a destination that supports its count. No pages are silently dropped. |
| Unsupported mixed media | Use images only for a multi-photo destination or send the video separately. |
| Video processing or duration | Inspect the source file, export a compatible version, and replace the attachment. |
| Provider permission or channel access | Restore bot, board, community, or account permissions at the destination. |
| Plan or storage limit | Inspect usage and the specific allowance; a preview restriction is not fixed by an ordinary upgrade. |
Retry and verify the outcome
Failed posts do not retry automatically. After correcting the cause, use Retry publish or schedule the existing post again. Watch the status until the attempt finishes. If a request was interrupted, check the existing post and destination before sending a new copy.
For an unresolved issue, keep the post link, destination name, approximate time and timezone, exact message, and the steps you already tried. Exclude passwords, API keys, and webhook secrets from screenshots. These details make the failure reproducible without exposing your credentials.
Frequently asked questions
Will reconnecting an account automatically resend failed posts?
No. Fix the connection, then use Retry publish or schedule the failed post again. Check the current status first if a send may still be in progress.