Every connected source shows a status on the Data sources screen. When something goes wrong, the status changes to Failed, Stale or Never synced, and Relator flags it in Performance, on Home and in notifications. This guide explains each status, the error messages you can get while authorizing, and the way back to syncing.
What each status means
Fresh
What's happening
Synced within your plan's expected window.
What to do
Nothing.
Syncing
What's happening
A sync is in progress.
What to do
Wait.
Never synced
What's happening
The source is connected but the first load hasn't finished.
What to do
Wait. If it takes long, use Resync.
Stale
What's happening
The last sync is past the window expected for your plan's frequency.
What to do
Use Resync.
Failed
What's happening
Syncing stopped. Hover over the status to see why.
What to do
Click Reconnect, right below the status.
Paused
What's happening
The source's sync is suspended.
What to do
Reconnect. If it persists, contact support.
Not syncing
What's happening
A BM or MCC account with no client assigned (agencies).
What to do
Pick the client under Assigned to.
N resources failing
What's happening
Part of the source's data failed; the rest keeps syncing.
What to do
Nothing: reprocessing is automatic.
Unknown
What's happening
Relator couldn't read the state right now.
What to do
Reload the page later.
Status
What's happening
What to do
Fresh
Synced within your plan's expected window.
Nothing.
Syncing
A sync is in progress.
Wait.
Never synced
The source is connected but the first load hasn't finished.
Wait. If it takes long, use Resync.
Stale
The last sync is past the window expected for your plan's frequency.
Use Resync.
Failed
Syncing stopped. Hover over the status to see why.
Click Reconnect, right below the status.
Paused
The source's sync is suspended.
Reconnect. If it persists, contact support.
Not syncing
A BM or MCC account with no client assigned (agencies).
Pick the client under Assigned to.
N resources failing
Part of the source's data failed; the rest keeps syncing.
Nothing: reprocessing is automatic.
Unknown
Relator couldn't read the state right now.
Reload the page later.
When you hover over Failed, Relator shows the reason and the consequence: Data from this source is stale in your reports — the history already synced stays safe. The possible reasons are:
Reconnect this source to renew provider access. Access expired or was revoked on the platform.
Review this connection's configuration. The selected account is no longer reachable or has changed.
The provider's rate limit delayed this connection. The platform throttled requests; Relator retries.
The provider is temporarily unavailable. The platform is having trouble; it usually comes back on its own.
In the sidebar, click Sources. On the Connected sources card, open the Status filter and pick Failed or Stale. In an agency, the consolidated view shows every client's connections; inside a client, only theirs.
2
Step 2
Read the reason and click Reconnect
Hover over the status to read the reason, then click Reconnect right below it. If the problem was access, Relator opens the platform's authorization again; otherwise it rebuilds the source's sync from scratch and data comes back in a few minutes.
Illustrative screen
Korra/Connections
Ask RelatorAIPT
Data sourcesThe sources that feed Bravo's reports.
2
Connected sources
Source
Currency
Status
Last sync
Meta Ads · Bravo Brasil
BRL
Fresh
Last success 1 h ago
Google Ads · Bravo Search
BRL
Failed · Reconnect
Last success 4 d ago
GA4 · bravo.com.br
BRL
Stale
Last success 9 h ago
1
1On the Failed row, the Reconnect link sits right below the status.
2The Status filter leaves only the sources that need attention.
3
Step 3
Sign in with a user who has access
On the platform's screen (Facebook, Google, HubSpot, RD Station), sign in with a user who still manages the account and accept every permission requested. If you uncheck a permission or an asset, the connection fails again.
Meta: in the Facebook dialog, click Edit and check the BM, the ad accounts and the Pages.
Google (Ads, GA4, Search Console): approve every permission on the consent screen.
4
Step 4
If it's only behind, use Resync
In the row's ⋯ menu, Resync requests a new sync. The reason shows below the item: Late by 9 h enables it; Synced 20 min ago keeps it locked because the source is up to date. Confirm in Resync {name}?.
Illustrative screen
Korra/Connections
Ask RelatorAIPT
Data sources
Connected sources
GA4 · bravo.com.brLast success 9 h ago
Stale
Resync GA4 · bravo.com.br?Syncing restarts from scratch and it may take a few minutes for data to return.
1
1Resync confirms. History already collected isn't deleted.
5
Step 5
Check the result
The Last sync column shows Last success and Next expected. Once the source is back to Fresh, the warning disappears from Performance and Home.
Why access expires
The person who connected left the company or lost access to the BM, MCC or property.
Someone removed Relator from the platform's integrations or revoked its permissions.
The account password changed or the platform asked for a new security check.
The ad account was moved to another BM or MCC.
In every case, the fix is to reconnect with a user who has admin access to the account. Prefer a company user that doesn't depend on a single person.
Errors while authorizing
OAuth was cancelled.
Cause
You closed or declined the platform's screen.
Fix
Start the connection again and accept the permissions.
OAuth failed.
Cause
The platform returned an error during authorization.
Fix
Try again. If it repeats, contact support.
The OAuth session expired.
Cause
You took too long choosing accounts and the session timed out.
Fix
Start again and finish the selection without a long pause.
No accounts are available to select.
Cause
The user doesn't have access to any account on that platform.
Fix
Sign in with a user who manages the account.
We couldn't find any Business Manager
Cause
The Facebook user isn't a BM admin or didn't share the assets.
Fix
Confirm you are a BM admin and, in the Facebook dialog, click Edit and check the BM.
No Facebook Pages or Instagram accounts found.
Cause
The user doesn't administer any Facebook Page.
Fix
Sign in with someone who administers the Page.
Google didn't return a refresh token.
Cause
A permission was left unchecked on the Google screen.
Fix
Reconnect and approve every permission.
Connection failed (RD Station, HubSpot)
Cause
The platform refused the authorization.
Fix
Try again with an admin user of the account.
Message
Cause
Fix
OAuth was cancelled.
You closed or declined the platform's screen.
Start the connection again and accept the permissions.
OAuth failed.
The platform returned an error during authorization.
Try again. If it repeats, contact support.
The OAuth session expired.
You took too long choosing accounts and the session timed out.
Start again and finish the selection without a long pause.
No accounts are available to select.
The user doesn't have access to any account on that platform.
Sign in with a user who manages the account.
We couldn't find any Business Manager
The Facebook user isn't a BM admin or didn't share the assets.
Confirm you are a BM admin and, in the Facebook dialog, click Edit and check the BM.
No Facebook Pages or Instagram accounts found.
The user doesn't administer any Facebook Page.
Sign in with someone who administers the Page.
Google didn't return a refresh token.
A permission was left unchecked on the Google screen.
Reconnect and approve every permission.
Connection failed (RD Station, HubSpot)
The platform refused the authorization.
Try again with an admin user of the account.
How to get notified next time
Sync failures alerts (after two consecutive sync errors) and Stale data alerts show up in Notifications and can also go out by email. Adjust them in the client’s Settings › Alerts (or Notifications, for the agency). See Notifications and alerts.
Frequently asked questions
Do I lose data if the connection fails?
No. History already synced stays saved. Only the days after the failure are missing until you reconnect; after that, Relator fetches the period it missed.
Why is the Resync button disabled?
Because the source is up to date (the reason shows as Synced … ago). It unlocks when the source falls behind or hasn't synced yet. On an agency connection, only the agency team can use it.
Can the agency's client reconnect?
No. In the portal, connections show as Via agency and are read-only. The agency reconnects.
I reconnected and it still says Failed. Now what?
Check that the user you used has admin access to the account and that every permission was accepted. If it persists, contact support with the source, the account and the message shown in the status.
What does “N resources failing” mean?
Part of that source's data didn't land, but the rest keeps syncing. Reprocessing is automatic and those resources come back on their own.
Data sourcesThe sources that feed Bravo's reports.Connected sources
GA4 · bravo.com.brLast success 9 h agoStale