Social publishing
Troubleshooting publishing
Reading a failure, what each platform error means, and how to recover.
Start with the destination result
Open the post and read the result for the failed destination. In a multi-network post, the top-level status is only a summary. Another destination may already be live and should not be published again.
Processing
The upload was accepted but Systemly or the provider has not confirmed the final result.
Partially published
Some destinations are live. Fix and retry only those marked failed.
Failed
Read the provider message, correct the cause, then use Retry where available.
Expired account
Reconnect the account before retrying its destination.
Common errors and fixes
Permission, authentication, or expired token
Reconnect the account from Social Accounts and approve every requested permission. If the provider account lost access to a Page, board, or channel, restore that access first.
Unsupported media, too many files, or file too large
Compare the destination with the media requirements, then replace the platform's media override. Each file must be 200 MB or smaller.
Provider rate limit or temporary service error
Leave the post in place while Systemly performs its transient retries. If it eventually fails, wait before using Retry; repeatedly creating copies can produce duplicates.
Needs setup
The deployment is missing the provider app credentials. A Systemly administrator must configure that integration before workspace users can connect it.
Provider-specific checks
- TikTok: choose an audience offered for that account. Unaudited apps require a private account and Only me visibility; wait while accepted videos are processing.
- Instagram: use a professional account linked to a Facebook Page, approve all Meta permissions, and publish at least one supported media item.
- Facebook: confirm the connecting user still has management access to the destination Page.
- YouTube: use exactly one video and remember that an unverified Google API project can force new uploads to Private.
- Pinterest: use one image and confirm the connected destination is the intended board.
- X: shorten the post to 280 characters and use no more than four images.
Retry without duplicating posts
Retry from the existing post. Systemly skips destinations already marked Published and sends only eligible failed destinations. If a provider shows the post as live but Systemly still says Processing, wait and refresh before retrying; provider confirmation can arrive after the content becomes visible.
When reconnecting does not help
If the message refers to token decryption or an ENCRYPTION_KEY mismatch, stop retrying. A deployment administrator must restore the encryption key that protected the saved connections. Reconnecting individual accounts is not a reliable fix for a deployment-wide key mismatch.
Removing a published post
Provider deletion is supported for Facebook, LinkedIn, YouTube, X, and Pinterest. Instagram and TikTok posts must be removed in their own apps. Disconnecting an account never deletes content that has already been published.