Fivetran: Issue Selecting Root Partitioned Tables in Connector Schema
View the provider incident record →Current answer
Fivetran experienced a minor incident: Fivetran: Issue Selecting Root Partitioned Tables in Connector Schema. Resolved on Sep 26, 2026.
The notice publication date does not establish the outage start. Provider resolved: .
Looking for an update now? Check the current status, or follow Fivetran for future changes.
Provider notice timeline
Affected Components
Amazon Aurora PostgreSQL
Amazon RDS for PostgreSQL
Azure Database for PostgreSQL
Google Cloud SQL for PostgreSQL
Heroku PostgreSQL
PostgreSQL
Incident Timeline
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description:
We were unable to select the root partitioned tables from the schema tab and saw the following message:
Cannot select - Table not included in publication <publication_name>. If you wish to sync it, please include the root partitioned table or all of its partitions in the publication.
Timeline:
This issue began on September 25, 2026 at 05:00 UTC and was resolved on September 25, 2026 at 20:00 UTC.
Cause:
A recent code change introduced stricter handling for partitioned table syncs, which caused some tables to be deselected.
Resolution:
We reverted the change, which restored the affected tables. Because the state had already been cleared, the tables were synced again as new tables.
Incident Summary
Description:
We were unable to select the root partitioned tables from the schema tab and saw the following message:
Cannot select - Table not included in publication <publication_name>. If you wish to sync it, please include the root partitioned table or all of its partitions in the publication.
Timeline:
This issue began on September 25, 2026 at 05:00 UTC and was resolved on September 25, 2026 at 20:00 UTC.
Cause:
A recent code change introduced stricter handling for partitioned table syncs, which caused some tables to be deselected.
Resolution:
We reverted the change, which restored the affected tables. Because the state had already been cleared, the tables were synced again as new tables.
Sep 26, 2026 at 4:44 AM UTC
Monitoring
We are continuing to monitor all affected connectors after the recent fix deployment.
Next Expected Update: 3 hours
Next Expected Update: 3 hours
Sep 26, 2026 at 12:04 AM UTC
Monitoring
We have deployed a Hotfix for this issue.
The affected tables will be re-added automatically and resynced by Fivetran.
Next Expected Update: 2 hours
The affected tables will be re-added automatically and resynced by Fivetran.
Next Expected Update: 2 hours
Sep 25, 2026 at 8:19 PM UTC
Identified
We identified an issue where certain Root Partitioned tables were unintentionally unselected or could not be selected for sync.
The root cause has been identified, and we are working to resolve the issue.
The root cause has been identified, and we are working to resolve the issue.
Sep 25, 2026 at 7:20 PM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.