RP
RevenueProven
All Help Articles
My sync is stuck or taking much longer than usual

My sync is stuck or taking much longer than usual

A sync job has been spinning for over an hour with no visible progress. This usually points to a very large first-time data pull, a temporary LinkedIn API slowdown, or a backed-up background job queue.

You triggered a sync and the progress indicator has been spinning for a long time without any update to your data or attribution numbers. The status may show Running but the sync phase has not advanced.

Sync status panel showing pipeline phases and progress
The sync status panel shows the active phase and elapsed time. A first-time sync on a large ad account can take up to 90 minutes.

Why this happens

Revenue Proven runs a multi-phase sync pipeline across five lookback windows: 7, 30, 60, 90, and 180 days. The first sync after connecting a large ad account with many campaigns and companies can take 30 to 90 minutes. Subsequent syncs are much faster because only new data is fetched. A sync can also appear stuck if LinkedIn's API is rate-limiting requests or if the background job queue has backed up under high load.

How to fix it

  • Allow at least 90 minutes for a first-time sync on a large ad account before assuming it is stuck.
  • Refresh the dashboard page to get the latest sync status. The status indicator polls on an interval and may be displaying a cached state.
  • If the sync has shown Running for more than two hours with zero data appearing, navigate away and back to the dashboard, then trigger a fresh manual sync.
  • Check that your LinkedIn connection is still Active under Settings and Connections. A disconnected LinkedIn integration causes all sync phases to fail silently.
  • Avoid triggering multiple manual syncs in quick succession. Queuing duplicate jobs extends the wait time rather than speeding things up.
  • If you recently changed your selected ad accounts in Settings, the first sync on the new account will start from scratch and take longer than usual.

Still stuck?

Contact support and include the approximate time the sync started. We can inspect the job queue and phase logs to identify exactly where it stalled and clear it if needed.