Instagram Messaging API · error code

Instagram error -1: Create media failed (2207032)

RetryableHTTP 400Content publishing (posts, reels, stories)

Last verified against Meta for Developers - Messenger Platform error codes

What Instagram returns
Create media fail, please try to re-create media

What error -1 means

Subcode 2207032, with top-level code -1, means Instagram failed to create the media container. Meta's recommended solution is to try again, and the user-facing message makes the same point: re-create the media. The failure is on the container step, POST /<IG_ID>/media, so no usable container ID came back and there is nothing to publish yet.

Meta gives no more detail than that, so treat it as a generic creation failure with two practical branches. If a retry with the same parameters succeeds, it was transient. If it fails again, the request itself is likely the problem even though the error does not say so: the media at the URL may be unusual, or the combination of parameters may be one the service cannot build. Re-checking the media against the published specs and simplifying optional parameters - collaborators, location, tags - is a reasonable way to isolate it.

Remember that each successful container creation counts toward the documented 400 containers per account per rolling 24 hours, so blind retry loops have a cost.

What it looks like

{
  "error": {
    "type": "OAuthException",
    "code": -1,
    "error_subcode": 2207032,
    "error_user_msg": "Create media fail, please try to re-create media",
    "fbtrace_id": "TvY2kRw8BoEz5Fk"
  }
}

Why it happens

  • A transient failure while Instagram was building the container.
  • Media that technically downloads but cannot be processed into a container.
  • An optional parameter, such as collaborators or user tags, that the service could not apply to this media.
  • Rapid repeated container creation for the same account.

How to fix Instagram error -1

  1. 1Retry the container creation once or twice after a short delay.
  2. 2If it keeps failing, re-validate the media against Meta's image or video specs and re-host it if needed.
  3. 3Strip optional fields and retry with only the media URL and caption to find the parameter that breaks creation.
  4. 4Add optional fields back one at a time, then publish the container that succeeds.
  5. 5Keep the fbtrace_id of repeated failures for a support report.

How to stop it recurring

Validate media and optional fields before calling the container endpoint, and bound retries so a stuck post cannot eat into the daily container allowance. Keep each post's last error and attempt count so operators can spot items that will never succeed. If the container is created but processing fails later, the error you see instead is 2207053.

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

Related codes

Error -1 - quick answers

What does Instagram error -1 mean?

Subcode 2207032, with top-level code -1 , means Instagram failed to create the media container. Meta's recommended solution is to try again, and the user-facing message makes the same point: re-create the media. The failure is on the container step, POST /<IG_ID>/media , so no usable container ID came back and there is nothing to publish yet.

How do I fix Instagram error -1?

1. Retry the container creation once or twice after a short delay. 2. If it keeps failing, re-validate the media against Meta's image or video specs and re-host it if needed. 3. Strip optional fields and retry with only the media URL and caption to find the parameter that breaks creation. 4. Add optional fields back one at a time, then publish the container that succeeds. 5. Keep the fbtrace_id of repeated failures for a support report.

Can I retry after error -1?

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.