Facebook Graph API errors: codes, causes, and fixes
Facebook Graph API errors use cryptic codes that do not explain what went wrong in plain English. This guide maps 15 documented Facebook Graph API publishing errors to their cause and the correct next step, so you can look up a code, identify the failure category, and apply a reconnect, rewrite, compression, pacing, or retry fix without guessing.
How to diagnose the failure category first
Before changing anything, classify the failure. Authentication failures mean the request cannot prove it may publish to the selected Page, so content edits will not help. Media and content failures mean the request reached the publishing path but the payload is malformed, oversized, or in the wrong format. Rate-limit failures mean the Page is being throttled for posting too fast. Policy failures mean automated checks flagged the content, link, or account state. Server failures mean the service was temporarily unavailable. That first classification determines whether the next step is reconnecting, rewriting, compressing, waiting, or retrying.
Authentication errors and reconnect fixes
INVALID_ACCESS_TOKEN means the token failed validation at Meta's auth layer, usually because it is malformed, expired, or signed against a client secret that has since rotated. The fix is to reconnect to mint a fresh long-lived page token. Error 490, returned with HTTP 401, means the Facebook session expired, which can happen when time-based expiry is reached or the user changed their password; reconnect the Page. REVOKED_ACCESS_TOKEN means the user revoked the token from Facebook Business Integrations, a common result when end users audit connected apps and remove old integrations; reconnect with the same user and page selection. Error 1404078 means the Page lacks the pages_manage_posts permission, usually because the user did not grant the page-management scope during the connect flow or selected a page they do not administer; reconnect, grant all requested scopes, and pick a page the user actually administers. Source-described handling includes storing long-lived 60-day page tokens and refreshing them on publish to extend their life, but that behavior is pending verified implementation evidence and should not be assumed as tested functionality.
Media errors: image size and format
Error 1366046 means the image is over 4MB or in an unsupported format. The Pages publish endpoint caps photos at 4MB and accepts only JPG or PNG, so compress or convert the file before retrying. Source-described handling includes auto-compressing on upload, pending verified implementation evidence.
Content errors: URL, structure, and length
Error 2061006 means the URL in the post is malformed, usually because the protocol prefix http:// or https:// is missing or the URL structure cannot be parsed; always include the protocol and URL-encode when needed. Error 1349125 means the post structure does not match the API contract, typically a wrong combination of message, link, media, and child_attachments; use the Graph API /me/feed documentation as the ground truth for the field combination. NAME_TOO_LONG means the post text exceeds the 63,206-character limit; split the text into multiple posts or trim it. These are payload problems, so fix the request body and resubmit rather than reconnecting the account.
Rate-limit and policy errors: pacing and Community Standards
Error 1390008, returned with HTTP 429, means the Page is posting too fast and is under a page-level throttle. Facebook throttles bursts to prevent automated spam, so space posts out by at least a few minutes instead of retrying immediately in a tight loop. Source-described handling includes pacing sends automatically when possible, pending verified implementation evidence. Policy errors need a different response: 1346003 means content was flagged as abusive or policy-violating by automated classifiers, so compare the flagged material with Facebook Community Standards and revise or remove that material. Error 1404006 means a security check is required before posting because the account or Page is under review; the user must log into Facebook directly and complete the prompted security challenge. Error 1404102 means the content violates Facebook Community Standards as a hard policy violation; rewrite to comply or skip the platform for that piece. Error 1609008 means a facebook.com link cannot be posted, a long-standing anti-spam measure against self-referential links; remove the facebook.com URL or replace it with a non-Facebook domain.
Server errors and retry decisions
Error 1363047, returned with HTTP 503, means the Facebook service was temporarily unavailable due to a transient outage in the publish path; retry, as it usually clears in minutes. Error 1609010, also HTTP 503, is a service disruption with the same shape from a different upstream; retry as well. Source-described handling includes auto-retrying these server errors, pending verified implementation evidence. Distinguish these from rate limits: a 503 server error calls for a short wait and retry, while 1390008 calls for slowing the posting pace.
Quick-reference table for all 15 codes
Use the quick-reference table below to find a code quickly, then use the failure matrix to confirm the fix type. The worked examples that follow show how the same decision process applies to four common codes.
Worked diagnostic examples
For INVALID_ACCESS_TOKEN, the symptom is a publish rejected at the auth layer even though the post content looks valid. Diagnose it by checking token age, recent client-secret rotation, and whether the token was minted for the selected Page; the fix is reconnecting to mint a fresh long-lived page token, not editing the message. For 1404078, the symptom is a permission-style rejection on a Page the user believes they manage. Diagnose it by confirming the user administers that exact Page and that pages_manage_posts was granted; the fix is reconnecting with all scopes and the correct Page. For 1390008, the symptom is a 429 after a burst of posts. Diagnose it by checking the interval between recent publishes; the fix is spacing posts by at least a few minutes and avoiding immediate retry loops. For 1363047, the symptom is a 503 with no payload problem. Diagnose it by confirming the same valid request fails transiently; the fix is waiting briefly and retrying rather than rewriting content or reconnecting.
| Code | Category | What it means | Fix action |
|---|---|---|---|
| INVALID_ACCESS_TOKEN | Authentication | Token failed validation at Meta's auth layer. | Reconnect to mint a fresh long-lived page token. |
| 490 | Authentication | Facebook session expired (HTTP 401). | Reconnect the Page. |
| REVOKED_ACCESS_TOKEN | Authentication | User revoked the token from Facebook Business Integrations. | Reconnect with the same user/page selection. |
| 1404078 | Authentication | Page lacks pages_manage_posts permission. | Reconnect, grant all scopes, pick a page the user administers. |
| 1366046 | Media | Image is over 4MB or in an unsupported format. | Compress or convert to JPG/PNG at or under 4MB. |
| 1390008 | Rate limit | You are posting too fast - page-level throttle (HTTP 429). | Space posts out by at least a few minutes. |
| 1346003 | Policy | Content flagged as abusive or policy-violating. | Compare flagged material with Facebook Community Standards; revise or remove that material. |
| 1404006 | Policy | Security check required before posting. | Complete the security challenge in the Facebook app. |
| 1404102 | Policy | Content violates Facebook Community Standards. | Rewrite to comply or skip the platform. |
| 1609008 | Policy | Cannot post a facebook.com link. | Remove the facebook.com URL or use a non-Facebook domain. |
| 2061006 | Content | URL in the post is malformed. | Include http:// or https://; URL-encode if needed. |
| 1349125 | Content | Post structure does not match the API contract. | Check message, link, media, and child_attachments against /me/feed documentation. |
| NAME_TOO_LONG | Content | Post text exceeds the 63,206-character limit. | Split into multiple posts or trim. |
| 1363047 | Server | Facebook service temporarily unavailable (HTTP 503). | Retry - usually clears in minutes. |
| 1609010 | Server | Service disruption (HTTP 503). | Retry. |
Documented codes from the captured source page; automatic handling behaviors are source-described and pending verified implementation evidence.
| Fix type | Codes | When to use it |
|---|---|---|
| Reconnect | INVALID_ACCESS_TOKEN, 490, REVOKED_ACCESS_TOKEN, 1404078 | Token expired, revoked, malformed, or missing pages_manage_posts permission. |
| Compress media | 1366046 | Image over 4MB or not JPG/PNG. |
| Space posts | 1390008 | Page-level throttle after posting too fast. |
| Rewrite content | 1346003, 1404102, 1609008, 2061006, 1349125, NAME_TOO_LONG | Policy flag, Community Standards violation, facebook.com link, malformed URL, wrong field combination, or text over 63,206 characters. |
| User action in Facebook app | 1404006 | Security check required before posting. |
| Retry | 1363047, 1609010 | Transient HTTP 503 service disruption. |
Grouping is an editorial diagnostic aid based on the documented causes and fixes in this reference.
Frequently asked questions
How do I decide whether to reconnect, rewrite, compress, space posts, or retry?
Start with the category. Authentication codes such as INVALID_ACCESS_TOKEN, 490, REVOKED_ACCESS_TOKEN, and 1404078 point to reconnecting and checking pages_manage_posts. Media code 1366046 points to image size or format. Rate-limit code 1390008 points to spacing posts. Policy codes point to revising content or completing a user security check. Server codes 1363047 and 1609010 point to retrying after a short wait.
What should I check first for error 1404078?
Check that the selected page is one the user actually administers, that pages_manage_posts was granted during the connect flow, and reconnect with all requested scopes. A missing scope or wrong page selection produces the same symptom as an expired token, so verify permissions before changing the post content.
How do I fix Facebook API error 1366046?
Compress or convert the image so it is JPG or PNG and no larger than 4MB, then retry the same post. The documented limits are size and format; if a compliant file still fails, preserve the file details and full response for further diagnosis.
What does error 1390008 mean and how should I respond?
Space posts out by at least a few minutes and avoid bursts. As general pacing advice, wait before retrying once rather than looping without delay, and reduce the sending rate if bursts recur.
When should I retry server errors 1363047 and 1609010?
Retry after a short wait, because these are documented as transient service disruptions that usually clear in minutes. If the same server code persists, preserve the request details and check for a wider outage before changing valid content.