Priority-First Sync - Why Syncs Are Taking Longer Than Expected

Question

• Why is the initial historical sync or subsequent historical re-sync taking longer than expected to complete?
• Why are subsequent incremental syncs taking longer than expected?

Environment

Check our Priority-first Sync documentation for an up-to-date list of supported connectors.

Answer

• For slow historical syncs: Shorten the historical sync duration by adjusting the historical sync date range. Fivetran's Support team can adjust the backward sync date range for most connectors. This stops the connectors from syncing any historical data prior to the date set.

  NOTE: Some connectors' cursors cannot be changed due to how their date range is stored. For more information, contact our support team.

• For long incremental syncs: Allow the historical sync to finish. Once the backward cursor has synced all data, incremental syncs will shorten in duration, as we will only be pulling the most recent data.

Cause

During the initial sync, Fivetran updates the destination with the most recent data. In each subsequent sync, we continue to update the most recent data first as part of the forward sync, and then fetch historical data in small increments as part of the backward sync.