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', 'FieldName2', ..." This occurs when fields Skyvia expects are missing, renamed, or deleted in the source system.
- Error: "Integration failed: Table 'TableName' schema validation failed: Redundant columns: 'FieldName1', 'FieldName2', ..." This happens when the target table has fields that no longer exist in the source system.
These errors are typical for replication scenarios, where Skyvia validates that the target table structure matches the source.
They can occur due to:
- Fields being added, renamed, or deleted in the source system.
- Insufficient permissions to access certain fields in the source.
- An outdated schema cached in Skyvia.
- A mismatch between the source and target table structures.
- Using an outdated Skyvia Agent for replication (if replication is executed via the agent).
Please follow these steps to resolve the error.
- Update the schema in the connection, clear the Metadata Cache, and reconnect to the source.
- Open the task and refresh/reselect the objects. Review field mappings: remove or remap columns that no longer exist.
- Resynchronize tables for replication tasks. Perform a full replication (Initial Run) to rebuild the schema.
Alternatively, run Resync for specific tables with a new runtime. If needed, enable Drop Tables and Create Tables to rebuild the affected target tables. - If replication runs via Agent, update to the latest Skyvia Agent version if an older version is currently in use.
Useful reference: Incremental Replication and Schema Updates
Related Articles
Mapping Multi-Select Fields
When working with Import, Synchronization, or Data Flow integrations and needing to map multi-select fields with different values between the source and target, you can use Expression Mapping. Expression mapping allows using simple and complex ...
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 ...
Salesforce Connect: Can't Sync the Schema Metadata for Your External System – Check That the Schema Metadata Is Valid. Error Code: Null
This error occurs because the object used in your endpoint does not have a primary key column. Salesforce requires a primary key for external objects, which is why you encounter an error when validating and syncing your External Data Source in ...
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 ...
Skyvia Backup Errors Caused by Salesforce API Requirements
Skyvia interacts with Salesforce via its API. During a backup operation, you may encounter errors due to certain limitations or behaviors specific to the Salesforce API. For example, when Skyvia performs a backup or replication, it queries all the ...