What is LastSyncTime in Skyvia

What is LastSyncTime in Skyvia

What is LastSyncTime?

LastSyncTime is the point when Skyvia last successfully transferred data during a Replication or Synchronization. It helps Skyvia remember what data has already been delivered, so next time, only new or updated records are processed.

Why it matters

Without LastSyncTime, Skyvia would reload all records on every run, which would:

  1. Greatly slow down Replication/Synchronization
  2. Increase load on the source system
  3. Consume more API calls and Skyvia record limits

With LastSyncTime, only changed data is loaded, so:

  1. Replications/Synchronization run faster
  2. API and record limits are used efficiently
  3. Source and target system load is reduced

How it works

  1. First Run – Skyvia loads all data from the source (Full or Initial Replication/Synchronization).
  2. After Completion – The current timestamp is saved as LastSyncTime.
  3. Next Runs – Skyvia retrieves only records modified after that timestamp.
This ensures Incremental Updates processing only what’s new or changed since the last successful run

When LastSyncTime is Updated

  • Updated only after a successful run

  • Not updated if the task fails

This ensures that no data is missed or skipped - if a run fails, Skyvia will attempt to reload all changes since the last successful sync.

Manual Reset

You can manually reset the LastSyncTime parameter when a full Replication is needed - for example, after schema changes or if incremental updates stop working.
Resetting LastSyncTime makes the next run perform a full reload of all selected data.


​Where It’s Used
  1. ​Replication tasks - for keeping a local copy of cloud data up-to-date.
  2. ​Synchronization tasks - for two-way data exchange between systems.
Both task types rely on LastSyncTime to identify which records to process, guaranteeing accuracy and efficiency.

Key Takeaways

  • LastSyncTime acts as a memory checkpoint for incremental data movement.

  • It’s updated only on success, ensuring data integrity.

  • It helps Skyvia optimize performance, reduce API calls, and prevent duplicate loads.

    • Related Articles

    • Integration Failure Types in Skyvia Data Integration

      When using Skyvia Data Integration product, you may encounter two distinct types of integration failures: 1. Record-Level Errors These occur when one or more individual records fail to process during an integration task. For example, in operations ...

    • Understanding Records in Skyvia Data Integration

      1.1 Understanding Records in Skyvia Data Integration A record in Data Integration represents a single row in a database table. Every integration process (Import, Replication, Export, Synchronization, etc.) handles individual records. Records also ...

    • Advantages of the New Replication Runtime Compared to the Old Runtime

      The new replication runtime offers several key advantages: • Object-level LastSyncTime, enabling incremental replication for each object • New runtime modes: Standard, Resync, and Resync on Demand • Improved performance by removing direct ID checks ...

    • Replication creates extra tables in the database

      In some cases, as a result of Replication, in addition to the main tables (for example, dbo.Account ), empty additional tables are created in the database with names of the following types: dbo.Account_2ade4447_5e11_4308_9e81_5eab62d9ed52 ...

    • Skyvia Query: Easily Verify Data in Your Connection!

      Please follow the steps below to query your data in Skyvia Query: Log in to Skyvia and navigate to + Create New → Query. Select an existing connection or establish a new one for your data source. Choose the desired table or object from the Connection ...