There might be certain instances when you encounter errors while publishing a post from your RecurPost account to your Threads profile. There might be a few reasons behind such errors, which we’re going to discuss, along with their possible solutions.
Threads publishing runs on Meta’s Threads API, so most failures fall into one of three groups: the connection between RecurPost and your Threads profile, the media you attached, or a temporary problem on Meta’s end. Start with the checks below before working through the error messages.
Check the connection first
Is the Threads profile still connected?
Open the Social profiles page in RecurPost and look at your Threads profile. If it shows a Reconnect prompt, RecurPost no longer holds a valid authorisation for it and nothing can be published until you reconnect. Click Reconnect, sign in to Threads, and accept all the permissions you are asked for. Do not untick anything on the consent screen, because the permission that lets RecurPost publish on your behalf is granted there.
Is the Threads account active and unrestricted?
Log in to Threads directly in a browser or the app and try posting manually. If Threads blocks you there, or shows a restriction or security checkpoint, clear it on Threads first. RecurPost cannot publish to an account that Threads itself has restricted, deactivated, or put behind a checkpoint.
Have you published a lot today?
Meta allows a limited number of posts per Threads profile in a rolling 24-hour window for posts published through the API, and a carousel counts as one post no matter how many items it holds. If posts published normally earlier in the day and then started failing with a general error, this is worth ruling out before you look at the post itself.
If the profile is connected, active, and you are not publishing at unusual volume, work through the error messages below.
1. Character limit
Error message: Threads allows sharing posts with a maximum of 500 characters only.
Solution: Threads posts support up to 500 characters. Shorten the caption in the text field and try posting again. RecurPost shows a character count as you type, so you can see where the post stands before you schedule it.
2. Text missing
Error message: The parameter text is required
Solution: Meta rejected the post because it carried no text. A Threads post needs a caption, so add a message in the text field and try posting again. If you are sharing an image or video on its own, add at least a short line of text alongside it.
3. Media doesn’t follow Meta’s guidelines
Error message: Your post failed because your media does not follow Meta’s guidelines. Please check the guidelines and try again.
Solution: Meta rejected the image or video you attached. This one message covers every media problem Meta reports, so check your file against the Threads video sharing guidelines. The specifications that most often cause a rejection are:
- Duration: up to 5 minutes (300 seconds)
- File size: up to 1 GB
- Format: MP4 or MOV, with H.264 or HEVC video and AAC audio
- Frame rate: 23 to 60 FPS
- Resolution: maximum width of 1920 pixels
- Aspect ratio: between 0.01:1 and 10:1, with 9:16 recommended to avoid cropping
For images, Threads accepts JPEG and PNG up to 8 MB each, within the same 10:1 ratio limit. Fix the file against whichever specification it misses, upload it to your RecurPost library again, and reschedule the post.
4. Invalid link attachment
Error message: Invalid Link Attachment. The post you’re trying to publish has an invalid link attachment.
Solution: Meta could not accept the link in your post. Open the link in a browser to confirm it loads, and check it for a typo, a missing `https://`, or a trailing character picked up when it was pasted. Links behind a login, links that are already expired, and some third-party shortened links are all refused. Replace the link with a working direct URL and try posting again.
5. Request unsupported
Error message: We have received a message from Meta that the request is unsupported.
Solution: Meta refused the request outright, which almost always means the authorisation RecurPost holds is missing a permission it needs, or no longer covers this profile. Go to Social profiles, click Reconnect next to the Threads profile, and accept every permission request on the Threads consent screen. If the error continues after reconnecting, confirm you can post to the profile manually in Threads, since an account-level restriction produces the same refusal.
6. No response from Threads
Error message: There was no response from Threads while posting this update. Please try again later.
Solution: RecurPost sent the post, but Meta never replied, so there is no way to tell from RecurPost’s side whether it went through. Check your Threads profile before doing anything else, because the post has sometimes published despite the error. If it did not, reschedule it and try again later. Posting it again without checking is the one thing that can leave you with a duplicate.
7. Temporary error from Threads
Error message: An unexpected error has occurred. Please retry your request later.
Solution: Meta’s servers returned an error without saying what went wrong. Nothing on the post needs changing. Check your Threads profile in case the post published anyway, then reschedule it and try again later.
8. Unknown error
Error message: An unknown error occurred
or
Error message: Something went wrong in posting.
Solution: These are general failures that Meta reported without a reason, and they are handled the same way. Check your Threads profile first, because the post sometimes publishes despite the error. If it did not, reschedule it and try again later. If the same post keeps failing while others publish normally, the problem is usually in that post rather than on Meta’s end, so check its caption length against item 1, its media against item 3, and any link against item 4. If it still fails, contact us at support@recurpost.com with the post details so we can look at it.
Things that are not errors
The @mention is published as plain text. Threads has no search-as-you-type list inside the RecurPost composer, so the username has to be exact. Open the profile you want to tag on Threads, copy the username exactly as it appears, and type `@` followed by that username. A misspelled username publishes as plain text rather than as a tag.
The link preview shows a different image. When you add a link, RecurPost fetches a title, image, and description for the preview, but Meta decides which image is finally shown at the moment the post goes live, and RecurPost has no control over that choice. If the preview matters, attach your own image to the post instead of relying on the automatic preview.
In case of any queries, feel free to contact us at support@recurpost.com.