“The source is temporarily unavailable. Try again in a moment.”

Error details

Message on screen

“The source is temporarily unavailable. Try again in a moment.”

Internal code

upstream

Where it appears

Extraction: X didn't answer in time, refused the request, or returned data we couldn't read

HTTP status

502 from /api/extract

Does retrying help?

Usually. Wait 30–60 seconds and try again.

How to fix it

1. Wait and retry. Give it 30–60 seconds and press Extract again. Most cases clear up on their own.
2. Check another post. If a different public video works, the problem is specific to that post or broadcast.
3. Check your connection. Reload the page; switching from Wi-Fi to mobile data can help.
4. Report persistent failures. If nothing works for an hour, tell us the time it happened (no need to send the link).

What this message means

Internally we record one of a few reasons: timeout (X took longer than about 12 seconds), network (the connection failed), guest_session (X refused the temporary session we need for broadcasts), parse (X returned data in a shape we didn't expect) or other. You see the same friendly message for all of them.

These reasons are logged without your link so we can spot when X changes something and fix the extractor.

Why it happens

• X is slow or rate-limiting. At busy moments X answers slowly or refuses some requests for a short while.
• Your connection dropped. If your device lost the connection mid-request, the browser reports a network failure and you get the same message.
• A change on X's side. When X changes its embed data, extraction can fail for everyone until we update the parser.
• Broadcast session refused. Live broadcasts need a short-lived guest session; when X won't issue one, broadcasts fail while normal posts may still work.

How long to wait, and when it isn't temporary

Most of these failures clear within a minute: X answered slowly, or one of our two public data sources refused a request. Wait 30–60 seconds and press Extract again. Retrying in a rapid loop doesn't help and can make the refusal last longer.

If the same post fails for more than an hour while other posts work, the problem is probably specific to that post's data (an unusual media type, for example). If every post fails, X probably changed something on its side and we need to update the extractor; that usually shows up in our error logs within hours.

Behind the scenes the message covers several distinct reasons: a timeout, a network failure, a refused guest session for broadcasts, or a response we couldn't parse. They all mean the same thing for you: wait briefly, then retry.

Questions people ask