Connectors to Postgres destinations are failing with an Alert: Drop Deprecated Non-null Column

We have resolved this incident.

A fix has been implemented and we are monitoring the results.

We are progressively rolling out the clean-up task to remove the deprecated columns from the destination tables over the weekend. However, we have corner scenarios that we cannot cover.

For these corner scenarios, you will receive further communication, or you can reach out to Fivetran support via a support ticket to resolve any sync failures.

We are working on a fix to eliminate the need for manual intervention to drop deprecated columns, ensuring the alerts are cleared and downstream views have current data.

We are working on a fix to eliminate the need for manual intervention to drop deprecated columns, ensuring the alerts are cleared and downstream views have current data.

Our engineers identified a subset of connectors that were repeatedly running into "Drop Deprecated Non-null Column" alerts. They have reverted the issue and all connectors are now running on the most up-to-date code. To fully resolve the issue you will need to drop and re-create any downstream views for impacted tables.

The issue has been identified and we are working to resolve it.