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.

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

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 if you are unsure whether your environment is impacted or have any questions.

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 if you are unsure whether your environment is impacted or have any questions.

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 if you are unsure of impact or have any questions.

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.