Advantages of the New Replication Runtime Compared to the Old Runtime

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 and foreign key constraints
• Enhanced error isolation (errors are logged per object instead of halting the entire integration)
• Advanced features: History Mode, Nested Objects (stored as JSON or in separate tables), and Data Hashing

You can enable it by selecting Use new runtime in your Replication integration settings.

Also, more details are available at the links below in our Recent Releases section:

April 2020 Engine Improvements     
January 2024 New Runtime & Features

    • Related Articles

    • Replication: Table '...' Schema Validation Failed (Resolving 'Absent Columns' and 'Redundant Columns' Errors)

      If you encounter the following errors in an integration, it means the schema of your data source no longer matches the schema Skyvia has cached: Error: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...

    • 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 ...

    • Running Agent in Different Workspaces

      If you need to run agents in multiple workspaces, you do not need to install the agent again on your computer: 1) Simply create a new agent in the additional workspace. 2) Copy the key from the agent in the new workspace: 3) Paste the key from the ...

    • Salesforce: Expired access/refresh token

      If you see an "expired access/refresh token" error, your Salesforce OAuth connection is invalid due to token expiration or revocation. Please open your Salesforce connection, sign in again to get a new token, and save it. Click the Test Connection ...

    • HubSpot: 414 Request-URI Too Large & 400 Request Header or Cookie Too Large

      This error occurs when the object you are querying contains too many custom fields. To resolve this issue for ContactListContacts, Contacts, and Deals objects, enable the Column-wise chunking option in the HubSpot connection editor (located under ...