What Is LastSyncTime in Skyvia Replication?

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:

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

With LastSyncTime, only changed data is loaded, so:

  • Replications/Synchronizations run faster.
  • API and record limits are used efficiently.
  • 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 is 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 Is Used

  • Replication tasks — for keeping a local copy of cloud data up-to-date.
  • 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 is 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

      Overview When using Skyvia Data Integration, 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 ...

    • Skyvia Full (Initial) Replication

      Overview Full Replication creates a complete copy of your source data in the target database. Use it for the first replication run, after schema changes, when refreshing all data, or if you encounter duplicate records. Requirements Valid Source and ...

    • Advantages of the New Replication Runtime

      Overview The new Replication runtime introduces significant improvements over the old runtime in terms of performance, flexibility, and error handling. You can enable it by selecting Use new runtime in your Replication integration settings. Key ...

    • Replication creates extra tables in the database

      Overview 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 like: dbo.Account_2ade4447_5e11_4308_9e81_5eab62d9ed52 ...

    • Understanding Records in Skyvia Data Integration

      What Is a Record? A record in Skyvia Data Integration represents a single row in a database table or a single object in a cloud source (e.g., one contact in Salesforce, one row in a Google Sheet). Every integration operation - Import, Export, ...