Sync Failure Due to Schema Changes Made During Ongoing Sync

Issue

The connector fails with an error such as:

"status": "FAILURE",
"reason": "Failed to sync endpoint(s) with error: {CONTACT=java.lang.NullPointerException, DEAL=java.lang.NullPointerException, LINE_ITEM=java.lang.NullPointerException, COMPANY=java.lang.NullPointerException}"

Multiple endpoints fail simultaneously, for example, CONTACT, DEAL, COMPANY, LINE_ITEM.

You may observe duplicate or conflicting columns for the same property in your destination tables.

Environment

Connector: HubSpot

Resolution

1. Allow the connector to complete the current sync before making schema or configuration changes.

2. If the connector is already failing:

   • Wait until the sync stops running.
   • Revert any mid-sync schema setting changes.
   • Re-sync the connector to let it reconcile the schema.

3. Once the sync completes successfully, schema settings can be safely adjusted again.

Cause

This issue can occur if schema changes are made while the connector is performing a sync (especially during the initial sync), or if schema change settings are altered.

When schema modifications are applied mid-sync, the connector's internal schema state can become inconsistent with the destination schema. As a result, Fivetran's safe type casting logic, for example, redshiftSafeTypeCasting, may encounter duplicate or conflicting columns for the same property, leading to sync failures.

Avoid modifying schema-related settings or making schema changes in your destination while a sync is in progress. Wait until the sync is complete to ensure schema integrity.