Troubleshooting
Nothing is connecting
OAuth that will not complete, connections that keep lapsing, and the account-type requirements that cause most of it.
Connection problems are nearly always one of four things.
The connect button is not there
The platform has no live integration on your deployment, or it is not included in your plan. Both cases are set out in platform support.
The OAuth flow does not complete
You are sent to the platform, you approve, and you come back without a connection.
- Wrong account type. Meta publishing requires a business or creator account connected to a Page. A personal Instagram profile cannot be published to, by anyone, through any tool.
- The page was not selected. During the Meta flow you choose which pages and accounts to grant. Skipping that step grants nothing.
- "We could not see a Facebook Page to post to." Reconnect, choose Edit settings on Facebook's screen, pick Opt in to current Pages only and tick each Page. The all current and future Pages option hides Pages held in a business portfolio. If it still fails, your Facebook account needs a content role on the Page. See connecting a Facebook Page.
- A permission was declined. Declining one of the requested permissions can leave the connection unusable. Run it again and accept all of them.
- A blocked pop-up or a strict browser extension. Try again in a normal window.
Facebook connected the wrong Page, or a brand lost its Page
A Page belongs to one brand at a time, so connecting it to a second brand takes it off the first. Switch to the brand that should have it, connect Facebook again and pick that Page. Keep every Page ticked on Facebook's screen, or the ones you untick stop posting.
It keeps asking me to reconnect
The token cannot be renewed. Usual causes:
- The social account's password changed.
- Access was revoked in the platform's own app settings.
- The page's roles or permissions changed, and your user no longer has the access the connection was made with.
Reconnecting is the same flow as connecting and does not disturb scheduled posts.
It says connected, but posts still fail
The connection is live and the send is being refused. That is a different problem: see why a post failed to publish.
Comments or metrics are missing
Some capabilities sit behind separate platform permissions that are still in review, which is why metric coverage is partial today. This is documented honestly rather than hidden. See Performance.
Still stuck
Tell us the platform, the account type, and what the screen said. See getting help.
Last updated October 13, 2026