Which connector?:

NetSuite

Additional details:

When a source table is renamed or recased (e.g., NetSuite's "accountingperiod" → "AccountingPeriod"), Fivetran treats it as two separate events: the old table marked deleted, and the new table discovered. For customers with Schema Change Handling set to "Block all new data" — the standard setting for sources with thousands of tables where only a subset is synced — the "new" table is added in a disabled state.

The result: a cosmetic, no-op source change silently halts the sync indefinitely, with no notification to the customer. In our case this went undetected for several weeks on a NetSuite
table that feeds financial reporting.

Detect rename and recase as a distinct event type — the table is logically the same — and preserve sync continuity automatically, rather than handling it as drop + add. The destination table is unchanged, so no downstream impact; only the source-side mapping needs to follow the rename.