Instagram Messaging API · error code

Instagram error 1: Unknown error

RetryableGeneric & request errors

Last verified against Meta for Developers - Messenger Platform error codes

What Instagram returns
An unknown error occurred.

What error 1 means

Code 1 is the Graph API's catch-all failure - documented on the error-handling page as "possibly a temporary issue due to downtime" with the advice to wait and retry. The Messenger Platform error page adds a less obvious cause worth knowing: "Missing permissions can cause this issue. Your app may need Advanced Access, Business Verification, or permissions" (listed there with subcode 99). In other words, code 1 hedges between a transient platform problem and a request your app was never entitled to make, reported unspecifically.

The two are easy to tell apart in practice. Transient code 1s are bursty: a cluster of failures across different calls that clears in minutes with no change on your side. Entitlement-shaped code 1s are deterministic: the same call fails every time, typically an endpoint or field gated behind Advanced Access that your app holds at Standard, in which case the real fix lives with code 10 and code 200 remedies rather than retries.

Why it happens

  • A temporary problem or partial outage on Meta's side.
  • The call touches an endpoint or field requiring Advanced Access or Business Verification the app does not have (documented with subcode 99).
  • A structurally odd request that no specific validator claimed.
  • A platform incident coinciding with your traffic, making it look like your bug.

How to fix Instagram error 1

  1. 1Check the Meta platform status page (metastatus.com) before changing code.
  2. 2Retry with exponential backoff a bounded number of times; treat success as confirmation it was transient.
  3. 3If the same request fails deterministically, audit the permissions and access levels it requires against what your app holds.
  4. 4Escalate persistent, identical failures to Meta Direct Support with the fbtrace_id.

How to stop it recurring

Wrap sends in a retry policy that distinguishes bursty failures (retry, capped) from deterministic ones (stop and alert), and monitor the code-1 rate so an incident shows up as a spike rather than a mystery. Keep permission and access-level requirements documented per endpoint you call. Related generic failures are code 2 and the parameter family under code 100.

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?

Code 1 is the Graph API's catch-all failure - documented on the error-handling page as "possibly a temporary issue due to downtime" with the advice to wait and retry. The Messenger Platform error page adds a less obvious cause worth knowing: "Missing permissions can cause this issue. Your app may need Advanced Access, Business Verification, or permissions" (listed there with subcode 99).

How do I fix Instagram error 1?

1. Check the Meta platform status page (metastatus.com) before changing code. 2. Retry with exponential backoff a bounded number of times; treat success as confirmation it was transient. 3. If the same request fails deterministically, audit the permissions and access levels it requires against what your app holds. 4. Escalate persistent, identical failures to Meta Direct Support with the fbtrace_id.

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.