Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Re-Sync Immediately after warning for forced_table_resync

Justin Canney User

In the event that the source table has re-ordered columns there will be a warning for "forced_resync_table" similar to below: 

{"event" : "forced_resync_table","data" : {"schema" : "fundrise","table" : "investment_entity","reason" : "Alter table statements that re-order columns cannot be migrated automatically.","cause" : "STRATEGY"}

When this occurs Fivetran will not re-sync until the next scheduled run. For example, if you have the connector set to sync every 6 hours, you can expect the following

  • 04:44:03.850, The warning forced_resync_table occurred.
  • 10:44:07.655, Fivetran starts the re-sync.
This causes issues with any processes dependent on the data being synced. 

The idea behavior would be that in the event of a forced_resync_table warning, Fivetran immediately proceeds to start the re-sync process and does not wait until the next scheduled sync. 

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Lyndsey User

    Hi Justin, 

    Can you please tell me the connector that this occurred for so that I can pass it to the right team?

    Each of our services determines whether to defer or action the resync to the next sync, based on their knowledge of the source. 

    Best, 

    Lyndsey, Connector Experience PM

  • Justin Canney User

    Aurora MySQL connector