---
title: "Meta Ads error 1: An unknown error occurred"
description: "Meta's 'An unknown error occurred' (error 1 or 2) is usually a temporary fault on Meta's side. Wait a few minutes and retry. What to do if it keeps coming."
---

> For AI agents: the full docs index is at [https://useproxy.dev/docs/llms.txt](https://useproxy.dev/docs/llms.txt). Append `.md` to any docs URL for Markdown.

This one is usually not your fault and usually not serious. Meta describes error 1 as "possibly a temporary issue due to downtime" and error 2 as a temporary issue, and its advice for both is to wait and retry. Tools that publish ads through Meta report the same: one tool maker's guide says that for this error a "Retry usually succeeds" ([Ads Uploader](https://adsuploader.com/docs/support/troubleshooting-launching-ads)), and another calls it "most likely temporary" ([Birch](https://help.bir.ch/en/articles/8892485-an-unexpected-error-has-occurred-please-retry-your-request-later-what-does-it-mean)). Wait a minute or two, reload the page and try again.

Sources: Meta's developer docs and two ad tool help guides, checked November 2026.

## Try this, in order

1. Wait a minute or two. Ads Uploader's guide gives "Wait 1-2 minutes and retry" for errors like this.
2. Reload Ads Manager and repeat the action once.
3. Check [Meta's status page](https://metastatus.com/) for a current problem with Ads Manager or the Marketing API. If one is listed, wait for it to clear.
4. Try a private window or another browser. Guides to Facebook's general "Something went wrong" message list refreshing, clearing the cache and switching browser, in that order, as in [Lilach Bullock's guide](https://www.lilachbullock.com/why-does-facebook-say-something-went-wrong/).
5. Try again later.

## If that did not work

- **It fails through a tool (Shopify, a scheduler, a reporting app).** Try the same action directly in Ads Manager. If it works there, the tool's connection is the problem. Reconnect it. Birch's guide gives the same fix: log in to the Meta profile, then refresh the tool's connection.
- **You get it when pulling a report through the API.** Meta notes one specific cause: asking for the ad set level when the correct level is campaign (error 1, subcode 99).
- **The message says "Your account is experiencing some trouble. Please try again later."** That is error 3910001. Meta's own text tells you to try later.

## When to stop and contact Meta

If the same action still fails after a few hours with no incident on the status page, contact Meta support through the [Business Help Center](https://www.facebook.com/business/help). Give the exact error text, the time, and the `fbtrace_id` if the error shows one. Meta says that ID expires quickly, so send it soon.

## The detail

| Code | Meta's wording | Meta's advice |
| --- | --- | --- |
| 1 | "An unknown error occurred." | "Possibly a temporary issue due to downtime. Wait and retry the operation. If it occurs again, check that you are requesting an existing API." |
| 1, subcode 99 | "An unknown error occurred. This error may occur if you set `level` to `adset` but the correct value should be `campaign`." | Fix the level |
| 2 | Service error | "Temporary issue due to downtime. Wait and retry the operation." |
| 3910001 | "Your account is experiencing some trouble. Please try again later." | Try later |

From Meta's [Graph API error handling guide](https://developers.facebook.com/docs/graph-api/guides/error-handling/) and [Marketing API error reference](https://developers.facebook.com/docs/marketing-api/error-reference/).

Do not confuse this with [error 17](https://useproxy.dev/docs/troubleshooting/meta-error-17-user-request-limit-reached) (too many requests, also temporary) or [error 100](https://useproxy.dev/docs/troubleshooting/meta-error-100-invalid-parameter) (a wrong value, which retrying will never fix).

## Related

- [Meta API error 17: User request limit reached](https://useproxy.dev/docs/troubleshooting/meta-error-17-user-request-limit-reached)
- [Meta temporarily blocked: error 368](https://useproxy.dev/docs/troubleshooting/meta-temporarily-blocked-error-368)
- [All troubleshooting pages](https://useproxy.dev/docs/troubleshooting)

While this clears, you can still see what competitors are running. [Proxy](https://useproxy.dev/welcome) reads the public ad libraries from your AI assistant. It does not manage ad accounts and cannot fix this error.
