revoked_access_tokenReconnectThreads token access was revoked.
Reconnect Threads through the linked Instagram or Meta account.
refresh-token
Error reference
Threads API errors and troubleshooting
Troubleshoot Threads API errors around Meta authorization, linked Instagram account state, media processing, video format, duration, codecs, and app review. Use this guide to decide when to reconnect, wait for processing, replace media, or confirm production access.
Last updated: May 2026
7 documented error patterns across 3 categories
Clear guidance on reconnecting, retrying, replacing media, or changing content
Official platform references plus bundle.social production troubleshooting notes
Error categories
Find the failure type first
7 documented errors
All error codes
Codes, causes, and fixes
Authentication
3 mapped cases
token is invalidReconnectThreads rejected the token.
Reconnect the account and clear any Instagram security prompts.
refresh-token
session has been invalidatedReconnectThe Threads session expired.
Reconnect after password changes or security checks.
refresh-token
Media
1 mapped case
media processingRetry laterThreads is still processing uploaded media.
Retry with backoff and give larger videos more time to process.
retry
Video
3 mapped cases
video formatFix inputThreads rejected the video format.
Convert the video to MP4 with H.264 video and AAC audio.
user-error
video codecFix inputThreads rejected the video codec.
Avoid unsupported codecs and re-export with H.264/AAC.
user-error
duration exceedFix inputThe Threads video exceeds duration limits.
Trim the video to the supported duration before publishing.
user-error
Media fetch failed
Threads publishing uses Meta media-fetch behavior. Public URL access and platform crawler compatibility are required.
Account restricted
Threads or the linked Instagram account can be restricted by platform safety systems. The user must resolve that restriction natively.
Threads publishing shares Meta-style auth and media behavior
Threads errors often look similar to Instagram or Graph API failures. The connected Meta account, linked Instagram state, app-review status, media URL, video format, and processing stage can all affect publishing.
Fix media and app-review issues before retrying
If Threads rejects a video format, cannot fetch media, or blocks publishing because of app-review state, reconnecting the account will not solve the issue. Replace the media or confirm the app has the required production access.
How bundle.social helps
bundle.social separates Threads errors by Meta token, linked Instagram account, media fetch, processing, video validation, app-review state, and temporary platform behavior.
Retry safety
Retry only temporary platform failures, processing delays, timeouts, 5xx responses, and rate-limit errors after the platform allows it. Do not retry the same request when the failure is caused by expired tokens, missing permissions, unsupported media, invalid captions, duplicate content, account restrictions, or policy blocks. The same payload will usually fail again until the account, media, content, or platform-specific setting is fixed.
Official references
Platform APIs change. Use these links to confirm current error behavior and field support.
FAQ
Can Threads API error messages change over time?
Threads publishing shares parts of Meta's error model, so failures may look like Graph API auth, media, or app review issues. Confirm the linked Instagram account and media stage before retrying.
Should users reconnect the account for every failed post?
No. Reconnect Threads for invalid tokens, revoked access, or Meta session problems. For video codec, duration, media processing, or app review issues, fix the asset or app state first.
Does bundle.social hide the native platform error?
bundle.social keeps the Meta response attached to the failed Threads job and clarifies whether the next step is auth, media processing, app review, or content adjustment.
Related
Keep researching
Build with less platform drag