Post failures are rare but can happen due to platform API changes, expired tokens, or media format issues. Threadly handles failures gracefully so nothing is lost.
What causes post failures?
- Expired OAuth token — The most common cause. If you changed your password or the platform revoked access, Threadly can no longer publish on your behalf.
- Media format or size issue — The image or video exceeds a platform's size limit or is in an unsupported format (e.g., animated GIFs are not supported on LinkedIn).
- Character limit exceeded — Rare since Threadly's composer enforces platform limits, but can occur if copy was imported via CSV without validation.
- Platform API outage — Occasionally a social platform's publishing API is temporarily unavailable. Threadly retries automatically up to 3 times over 30 minutes before marking as failed.
- Content policy violation — The platform rejected the post due to its content policy.
What happens after failure
- Threadly sends an immediate email notification to the account owner with the specific error message.
- The post moves to a Failed state, visible with a red indicator in your Queue and Calendar.
- The post content is fully preserved — nothing is lost.
How to fix and re-publish
- Go to Queue → Filters → Failed to see all failed posts.
- Click the failed post to open it.
- Review the error message and fix the issue (usually reconnecting the account in Settings).
- Click Re-Publish to send it immediately or reschedule to a new time.