Why is my Meta account not connecting?

If uplads suddenly can't reach your Facebook or Instagram account — launches fail, ad accounts go missing, or you see an authentication error — it almost always comes down to the access token Meta issued. The good news: every fix below takes under a minute and lives on a single card in your settings.

Common causes

When the Meta connection breaks, it's usually one of three things:

• Expired token — Meta access tokens have a finite lifetime. Once the expiry date passes, every request uplads makes is rejected. The Meta Connection card shows Token expires: Expired in red when this happens.
• Revoked permissions — If you (or a Business admin) removed uplads from your Facebook Business Integrations, or changed your password, Meta invalidates the token even before its expiry date.
• Missing scopes — uplads requests a specific set of permissions during sign-in. If you unchecked any of them on Meta's consent screen, features that depend on them (ad creation, Page selection, Instagram, catalogs) will fail.

Reauthorizing from the Meta connection card

The fastest fix is to reauthorize, which sends you back through Meta's login and issues a fresh token.

1. Open Configuration and go to the Connections section.
2. Find the Meta Connection card. It shows your account name, when you connected, and the Token expires date.
3. If the token is expired you'll see the note "Your token has expired. Please reauthorize to continue using the platform."
4. Click Reauthorize. When the token is expired this button is highlighted as the primary action.
5. Complete Meta's login dialog and keep every requested permission checked. You'll land back on the connection card with a new expiry date.

Reauthorizing keeps your existing connection in place — you don't lose any saved Pages, ad accounts, or launch history.

Confirming the right business has granted access

If reauthorizing succeeds but your ad accounts or Pages still don't show up, you likely logged in with a Facebook profile that doesn't have access to the right Business Manager. On Meta's login dialog, make sure you:

• Sign in with the personal Facebook profile that's a member of the correct Business.
• Grant access to the ad accounts and Pages you intend to launch with — Meta lets you pick which assets to share.

If your agency or client owns the assets, ask the Business admin to add your profile as a partner or assign you the asset before you reauthorize.

Checking required scopes

uplads requests these permissions during sign-in, and each unlocks part of the product:

• ads_management and ads_read — create, edit, and read ads (required for any launch)
• pages_show_list and pages_read_engagement — list and use your Facebook Pages
• instagram_basic — place ads on Instagram
• business_management — see assets owned by your Business Manager
• read_insights — pull performance metrics into the ads manager
• catalog_management — use product catalogs for dynamic/advantage+ formats

The connection card stores the scopes Meta actually granted. If a feature is broken, the most common culprit is that one of these was unchecked on the consent screen. Reauthorize and leave them all enabled.

When to disconnect and reconnect cleanly

If reauthorizing doesn't clear the error — for example you connected the wrong profile, or the token stays stuck — do a clean reset:

1. On the Meta Connection card, click Disconnect, then Confirm Disconnect.
2. Connect again from scratch. See How to connect your Meta account for the full walkthrough.

A clean reconnect wipes the stored token and scopes, so it's the surest fix for a tangled connection. For more on the difference between reauthorizing and disconnecting, see How to reauthorize or disconnect your Meta account.

Still stuck after a clean reconnect? It may be a launch-side issue rather than the connection itself — see Why don't my launched ads appear in Meta Ads Manager? and Ad set limits and common Meta errors explained.