Instagram Messaging API · error code

Instagram error -2: Media download took too long (2207003)

RetryableHTTP 400Content publishing (posts, reels, stories)

Last verified against Meta for Developers - Messenger Platform error codes

What Instagram returns
It takes too long to download the media.

What error -2 means

Subcode 2207003 comes with top-level code -2 and means Instagram gave up while downloading your media. Meta's recommended solution identifies it as a timeout during the download and says to try again.

The publishing API pulls media from the URL you supply rather than receiving the file in the request, so your server's response time is part of Meta's processing. A slow origin, a cold CDN cache, a server that throttles unknown user agents, or a very large video sent over a constrained link can each exceed Instagram's patience. The file itself may be perfectly valid; it just did not arrive in time.

That is what separates it from its neighbors. 9004/2207052 means the URL could not be fetched at all, and 36000/2207004 means the image was fetched but is too big. Here the fetch started and simply ran out of time. For large videos, Meta's resumable upload flow on rupload.facebook.com is the documented alternative to having Instagram download from your server.

What it looks like

{
  "error": {
    "type": "OAuthException",
    "code": -2,
    "error_subcode": 2207003,
    "error_user_msg": "It takes too long to download the media.",
    "fbtrace_id": "UwZ5mSx4CpFa9Gl"
  }
}

Why it happens

  • The origin server responds slowly or limits bandwidth for Meta's fetcher.
  • The CDN cache was cold, so the first request had to travel back to a slow origin.
  • A large video was hosted on infrastructure that cannot serve it quickly.
  • Network problems between Meta and your host during the download.

How to fix Instagram error -2

  1. 1Retry the request after a short delay, as Meta recommends.
  2. 2Time a download of the exact URL from outside your network to measure how long it really takes.
  3. 3Serve media from a fast CDN and warm the cache before creating the container.
  4. 4Reduce file size where possible, for example by compressing images or capping video bitrate.
  5. 5For large videos, switch to the resumable upload flow so the file is pushed rather than pulled.

How to stop it recurring

Host publishing media on a CDN close to Meta's fetchers, warm it before the scheduled publish, and keep files lean. Use resumable uploads for large reels so download speed stops mattering. Track 2207003 per host so a degrading origin shows up before every scheduled post fails.

Official reference: Meta for Developers - Messenger Platform error codes. See all Instagram error codes or the Instagram limits and quotas.

Related codes

Error -2 - quick answers

What does Instagram error -2 mean?

Subcode 2207003 comes with top-level code -2 and means Instagram gave up while downloading your media. Meta's recommended solution identifies it as a timeout during the download and says to try again. The publishing API pulls media from the URL you supply rather than receiving the file in the request, so your server's response time is part of Meta's processing.

How do I fix Instagram error -2?

1. Retry the request after a short delay, as Meta recommends. 2. Time a download of the exact URL from outside your network to measure how long it really takes. 3. Serve media from a fast CDN and warm the cache before creating the container. 4. Reduce file size where possible, for example by compressing images or capping video bitrate. 5. For large videos, switch to the resumable upload flow so the file is pushed rather than pulled.

Can I retry after error -2?

Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.

Stop debugging Instagram by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.