A practical reference for failed social media publishing jobs. Find the platform that failed, identify the error type, and decide whether the next step is reconnecting the account, fixing the payload, replacing media, or retrying later.
Last updated: July 2026
Platform-specific error references for publishing, scheduling, media, permissions, and rate limits
Troubleshooting paths for reconnect, fix input, retry later, and platform issue cases
Written for support teams, developers, and customer-facing publishing workflows
A failed Instagram post, TikTok video, Slack message, and Reddit submission can all look like a generic publishing error in a product UI, but the cause is usually platform-specific. Instagram failures often happen around media containers, TikTok can block privacy or spam-risk combinations, Slack can return ok false in the response body, and Reddit can reject posts because of community rules.
Most failed posts fall into one of four actions: reconnect the account, fix the input, retry later, or wait for the platform. Token, scope, revoked-access, and permission failures belong in the reconnect path. Caption limits, unsupported media, missing fields, duplicate content, and invalid URLs need a payload or content change. Rate limits, processing delays, timeouts, and 5xx responses need a delayed retry.
A reconnect is useful when the platform no longer trusts the token, the user changed permissions, a required scope is missing, or the account can no longer access the target page, channel, profile, or location. It will not fix an expired media URL, a rejected video format, a policy block, a duplicate post, a community rule, or a temporary platform outage.
Retry temporary platform failures, processing delays, timeouts, 5xx responses, and rate-limit errors after the platform allows it. Do not immediately retry validation, permissions, unsupported media, account restriction, or policy failures. The same payload usually needs to change before it can publish successfully.
Choose a platform below to search native error messages, normalized Bundle error keys, likely causes, and recommended retry behavior. Each page ties the failure to the account, publish stage, media requirement, permission state, and next user-facing action.
Complete reference
Looking for a specific Bundle error key or native platform code? Search the complete API error reference.
Search complete error referenceNo. Reconnect only for token, scope, account access, or permission failures. Most publishing failures need a media, content, payload, platform setting, or retry timing fix.
Each social network has different auth rules, media constraints, rate limits, policy checks, and response shapes. Platform-specific pages keep troubleshooting close to the native API behavior.
Yes. Treat exact platform wording as a signal, then confirm the failed stage, affected account, payload, media file, and platform state before choosing the next action.
Retry when the platform response is temporary, such as a timeout, processing delay, 429, or 5xx response. Do not retry unchanged payloads after validation, permission, account restriction, unsupported media, duplicate content, or policy failures.
Platform error pages
Privacy settings, spam risk, creator eligibility, media pulls, and posting volume limits.
Media containers, Graph API sessions, publishing limits, product tags, and account quality.
Page roles, Meta sessions, Business Manager rules, malformed links, and policy blocks.
Quota, channel permissions, upload processing, thumbnails, copyright checks, and Content ID.
Duplicate posts, usage caps, blocked URLs, API tier limits, credentials, and media duration.
Member tokens, organization roles, missing scopes, duplicate content, and media processing.
Location eligibility, field masks, read-only attributes, verification state, quota, and concurrency.
Meta tokens, linked Instagram state, app review, media fetch, video format, and processing.
Subreddit rules, flair requirements, account age, karma, spam filters, removals, and rate limits.
Board validation, media fetch, unsupported files, video cover images, processing, and rate limits.
PDS routing, sessions, record validation, blob uploads, moderation, and app-view propagation.
Webhook tokens, channel permissions, slowmode, missing guilds, attachments, and payload validation.
Instance availability, OAuth, account restrictions, validation, federation, media, and scheduled posts.
ok false responses, missing scopes, channel membership, archived channels, Retry-After, and payload limits.
Build with less platform drag