Fix Skyvia Replication Schema Validation Failed Error

Replication: Schema Validation Failed (Absent Columns / Redundant Columns)

Overview

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:

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

Root Causes

  1. Fields being added, renamed, or deleted in the source system.
  2. Insufficient permissions to access certain fields in the source.
  3. An outdated schema cached in Skyvia.
  4. A mismatch between the source and target table structures.
  5. Using an outdated Skyvia Agent for replication (if replication is executed via the agent).

Resolution

  1. Update the schema in the connection, clear the Metadata Cache, and reconnect to the source.
  2. Open the task and refresh/reselect the objects. Review field mappings: remove or remap columns that no longer exist.
  3. 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.
  4. If replication runs via Agent, update to the latest Skyvia Agent version if an older version is currently in use.

Useful Links

    • Related Articles

    • Mapping Multi-Select Fields

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

    • Brevo Attributes Field: Mapping Rules and Override Behavior

      Overview When working with Brevo contacts, the fields Attributes_FirstName, Attributes_LastName, and Attributes_Phone are provided as standalone fields for convenience, as they are universal to all users. However, for adding or updating custom ...

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

    • BigCommerce: The value of the column Categories has incorrect JSON format

      Overview When working with the Categories field in the Product object within the BigCommerce API, it is important to format the data correctly to ensure a successful import. In the BigCommerce API, the Categories field is an array. For more ...

    • Salesforce Connect: Can't Sync Schema Metadata (Error Code: Null)

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