Changes / dbt Labs / Schema Hydration Panic
dbt Labs: Major incident: Schema Hydration Panic
Summary
Major outage: Fusion Stable scheduled jobs and Studio IDE encountered “No schema found for get columns in relation call” errors from 2026-09-18 23:31 UTC to 2026-09-19 14:30 UTC (14 h 58 min). A fix reached Latest and Stable release tracks; customers no longer needed the temporary Fusion Extended workaround.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Schema Hydration Panic
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-18 23:31 UTC
Before: not present
After: 2026-09-19 14:30 UTC
Before: not present
After: We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.
Before: not present
After: We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.
Before: not present
After: We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress.
Please reach out to Support at support@dbtlabs.com "support@dbtlabs.com": mailto:support@dbtlabs.com if you are unsure of impact or have any questions.
Before: not present
After: We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track.
Please reach out to Support at support@dbtlabs.com: mailto:support@dbtlabs.com if you are unsure whether your environment is impacted or have any questions.
Before: not present
After: We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track.
Please reach out to Support at support@dbtlabs.com: mailto:support@dbtlabs.com if you are unsure whether your environment is impacted or have any questions.
Before: not present
After: Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using support@dbtlabs.com
Before: not present
After: This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Schema Hydration Panic (this change) Major outage: Fusion Stable scheduled jobs and Studio IDE encountered “No schema found for get columns in relation call” errors from 2026-09-18 23:31 UTC to 2026-09-19 14:30 UTC (14 h 58 min). A fix reached Latest and Stable release tracks; customers no longer needed the temporary Fusion Extended workaround. | Major incident |