Threads reports most failures through the Meta Graph error format: a code, sometimes a subcode, and a message that rarely says what to change. This page lists the ones a scheduler meets when it publishes through the Threads API, what each means, and what fixes it. It is written from the code that publishes to Threads for Preflight, including an incident on 12 October 2026 where two accounts were refused while others posted normally, and it was checked on 20 October 2026.
Publishing on Threads is two steps. The tool creates a container (the post, with its text and media), then publishes it. A text post is ready in about two seconds; a video can take two minutes to transcode. Most failures fall into three groups: the token is no longer valid, the account the tool is posting as is no longer known, or the container fails while Threads processes its media.
The errors, and what they mean
| What you see | What it means | Retry? | What to change |
|---|---|---|---|
| Error code 190 | The token expired or was revoked. Threads tokens are long-lived and can be refreshed, but a revoked one cannot. | No | Reconnect Threads. |
| "The requested resource does not exist", subcode 33, when posting | The user id the channel was connected with is no longer known to Threads. | No | See the next section: it is not always a reconnect. |
| "Media processing failed" with a reason | The container went to ERROR and Threads named a cause. | No | The file is the problem: re-export or replace it. |
| "Media processing failed: no reason given", or the reason "UNKNOWN" | Meta's catch-all for a transcode its own pipeline dropped. | Twice | Often passes on a second attempt. If not, re-export the video. |
| Any other error with HTTP 400 | A request Threads will not accept as written. | No | Read the message; the content or an option is wrong. |
A 400 answer is treated as final, because the same request gets the same answer. Anything with another status is retried.
"The requested resource does not exist" when posting
On 12 October 2026 this message appeared on two accounts while other accounts on the same app posted fine. It looks like a missing post, and it told nobody to reconnect. What it meant was that Threads did not recognise the profile id the post was addressed to, for instance after a profile was deleted and set up again. Three situations hide behind it, and the right fix differs:
- The token now belongs to a different profile. The tool asks Threads who the token belongs to and, if the id differs from the stored one, posts as that profile and remembers it.
- The token is refused too. The connection really is gone. Reconnect Threads.
- The token says it is this very profile, but posting as it is refused. The profile may be restricted or inactive, or the publishing permission is gone. Open the profile in the Threads app to check, then reconnect so the permission is granted again. A reconnect alone does not always fix this one.
A reply is different: its missing resource is the post it answers, so the same message there means the original was deleted.
Media failures
Pictures, video and carousels pass through a container before they publish, and the container status says FINISHED, ERROR or still processing. A named error means the file will fail the same way later, so Preflight stops at once and shows the reason. The unnamed ones are worth one more try. A video that stays in processing is handed to a background job that asks once a minute, so a slow transcode does not hold a worker for minutes.
Most media errors can be avoided by checking the file before sending: the picture limits, up to 20 in a carousel, a 10:1 ratio ceiling, and the video rules are on the Threads limits page, and a file can be tested with the video checker.
Rules that look like errors
The 500-character limit counts bytes for emoji, so a smiley costs four and a flag eight; a post that looks short can be over. A post with more than five links is refused. Replies are posted as a chain under the first post. These are checked before a post leaves, with the character counter showing the count. For the walkthrough of scheduling to Threads, see how to schedule Threads posts, and for the integration itself Threads scheduler.
Questions people ask
- What does "The requested resource does not exist" mean when posting to Threads?
- Threads does not recognise the profile id the post was addressed to. It can happen after a profile was deleted and set up again, or when the profile is restricted. The tool should check who the token belongs to; if it is a different profile, post as that one, otherwise reconnect Threads.
- What is Threads error code 190?
- The access token is invalid: it expired or was revoked. Retrying will not help; reconnect the Threads account so a new token is issued.
- Why does a Threads video post fail with "Media processing failed"?
- Threads transcodes the video after it is uploaded and the container went to ERROR. If a reason is named, the file is the problem and needs re-exporting. If the reason is UNKNOWN or missing, it is Meta's catch-all and often passes on a second attempt.
- How long does a Threads post take to publish?
- About two seconds for text and a few for pictures. A video can take up to about two minutes while Threads transcodes it, so a tool should wait for the container to finish instead of publishing at once.
- Why is my short Threads post over the limit?
- Threads counts emoji as their UTF-8 bytes against the 500 limit, so a smiley costs four and a flag eight. A post with many emoji can be over although it looks short.