MerchantFlowMerchantFlow Docs
Data Sync

Sync Troubleshooting - Fix Stale Data

Fix common MerchantFlow sync issues including stale data, failed jobs, expired tokens, and partial provider updates with this step-by-step checklist.

Sync Troubleshooting

Sync troubleshooting helps you diagnose and resolve issues when your MerchantFlow data looks stale, incomplete, or a sync request fails. Use this checklist to identify the root cause and apply the correct fix.

First Checks

  1. Confirm the workspace is not still in demo mode
  2. Confirm onboarding and billing approval are complete for the live workspace
  3. Open the Live indicator and check the current state
  4. Review Settings > Integrations for provider health
  5. Confirm the expected property, account, or site is still selected after any reconnect

How to Fix a Job Queued for a Long Time

  • Wait briefly in case workers are busy
  • Refresh the status view
  • Avoid submitting duplicate full syncs unless the previous request has cleared

If the queue clears and the same request never begins, review integration health before retrying.

How to Fix a Failed Sync Job

Common causes include:

  • disconnected or partially configured integrations
  • switching accounts without reconfiguring the selected property or ad account
  • provider-side permission changes
  • expired or revoked OAuth credentials
  • trying to sync after trial or subscription access expired

Run a targeted sync after fixing the connection. See Connect Integrations for reconnection steps.

How to Fix a Single Stale Provider

Use the Manual Sync Runner and rerun that provider only:

  • Google
  • Shopify
  • WooCommerce
  • Meta
  • Snapchat
  • TikTok
  • Speedfulfill

See Selective Sync for details on provider-specific syncs.

How to Fix Incomplete Data After a Successful Sync

Check whether:

  • the correct GA4 property, site, merchant account, or ad account was selected
  • the provider itself has reporting lag
  • the workspace recently changed integrations and needs a full sync rather than a standard one

Examples:

  • a Google reconnect without re-saving the property or site can leave the wrong resource selected
  • Search Console can lag behind real-time store activity
  • a commerce platform swap usually needs more than a quick incremental refresh

When to Contact Support

Contact [email protected] if:

  • the same job remains stuck after multiple attempts
  • a provider reconnects successfully but never resumes syncing
  • you need help identifying whether the issue is account setup or platform latency
  • the billing state looks correct but sync requests still say subscription access is blocked

When you contact support, include:

  • workspace name or owner email
  • which provider is failing
  • the last successful sync time if known
  • the exact error message or health warning you see in the UI

Frequently Asked Questions

Why does my sync keep failing after I reconnect an integration?

After reconnecting, you must re-select the correct property, site, or ad account. A Google reconnect that does not re-save the GA4 property or Search Console site can leave the wrong resource selected, causing the sync to fail.

How long should I wait before assuming a sync is stuck?

Wait at least 5 minutes for standard syncs and up to 30 minutes for full history syncs. If the job still shows as running after that time, review the integration health panel for error messages.

Can provider-side outages cause sync failures in MerchantFlow?

Yes. If Google, Shopify, Meta, or another platform experiences an outage or rate-limits API requests, MerchantFlow sync jobs may fail or return partial data. These issues typically resolve when the provider recovers.

Does MerchantFlow automatically retry failed syncs?

Yes. Failed sync jobs are retried during the next automatic background cycle. If the underlying issue persists (such as a revoked OAuth token), the retry will also fail until you fix the root cause.

Related Pages


Last updated: March 14, 2026