Störungsverlauf von Dbt Cloud

We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. **Workaround:** Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, `my_account` → `my-account`) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

We're investigating an issue with the Studio IDE that is causing the LSP Server connection to error. This is impacting server status and compilation in the Studio IDE anytime after June 18th around 2 PM Eastern. 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.

We have identified an issue with the Studio IDE that is causing the LSP Server connection to error. A fix is being implemented, and we will provide an update shortly.

We have deployed a fix with the Studio IDE that is causing the LSP Server connection to error. We are continuing to monitor.

The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We have Identified and deployed a fix for the global login service that was causing users not to be able to login. The global Login services has returned to its normal state and we are continuing to monitor.

The issue has been resolved, and all affected systems are functioning normally . Between 04:00 EST and 04:53 EST an issue with the Global Login Service resulted in customers unable to login. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience any issues regarding this.

We have identified an issue with user's access to dbt platform. This is causing customers to see an "Access denied" error when attempting to authenticate. A fix is being implemented, and we will provide an update shortly.

We have deployed a fix for the login issue that was causing users to encounter "Access denied" error. This has returned to its normal state and we are continuing to monitor.

The issue has been resolved, and all affected systems are now functioning normally. Between 19 Jun 00:00 - 06:50 UTC, an issue with login resulted in users receiving "Access denied" error at authentication. We have put measures in place to prevent a recurrence and all system has returned to normal. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

Between 14:11-14:18 UTC, we experienced a brief degraded performance that impacted API and dbt Cloud Platform. All impacted components have been operating as normally since and we have preventative measures in place. We apologise for the inconvenience caused. Please contact us at [email protected] with any questions or concerns.

Between the hours Jun 08, 2026 at 4:00:15.401 AM UTC and Jun 08, 2026 at 9:12:18.243 PM UTC we have seen some job runs and some commands in the IDE fail with the following: ERROR [SerializationError (dbt1013)]: Invalid seed definition ` .+copy_grants`:  invalid type: boolean `true`, expected struct ProjectSeedConfigERROR [SerializationError (dbt1013)]: Invalid seed definition ` .+snowflake_warehouse`:  invalid type: string "", expected struct ProjectSeedConfig The issue has since been resolved, and we have put preventative measures in place. We apologize for any inconveniences this has caused you. Please don't hesitate to contact us at [[email protected]](mailto:[email protected]) with any questions or concerns.

We're investigating an issue with the Discovery API that is causing stale data. This is impacting systems using metadata, such as dbt Catalog and dbt Mesh, in US MT anytime after 10:30 PM UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. All other systems are not impacted and should be running as expected.

The issue has been resolved, and all affected systems are now functioning normally as of 12:00 AM UTC. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

Between 00:11–00:12 UTC, we experienced a brief degraded performance that impacted API availability and had a potential impact on some job runs. All impacted components have been operating as normally since and we have preventative measures in place. We apologise for the inconvenience caused. Please contact us at [email protected] with any questions or concerns.

We're investigating an issue with the compile button on Fusion-Latest that is causing `dbt9002: Failed to find compiled SQL.` Compile is still working inline for builds and data preview. This is impacting the Studio IDE anytime after 2 PM Eastern. 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.

We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly.

We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out.

The issue has been resolved, and all affected systems are now functioning normally as of 7am UTC. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating an issue with incorrect logging that is causing `Warn dbt1410: dbt State service was requested but no validated client is available for node` to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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.

We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly.

We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor.

The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence and Scheduled Jobs have returned to normal. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected.

We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix.

A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved.

dbt Copilot and AI-powered features are operating normally. This incident is now resolved. We have put measures in place to prevent a recurrence and the dbt Copilot has returned to normal. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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.

We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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.

We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly.

We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor.

Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments.

Between May 24, 8:52 pm – May 24, 8:55 pm UTC, a small number of runs trying to retrieve publication artifacts experienced the following error: "Error retrieving publications: the Cloud Artifacts API is currently unavailable. Please try again later." The issue has since been resolved and we're continuing to monitor. Apologies for any inconveniences this has caused

The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating an issue with the dbt platform CLI Server that is causing elevated 5xx errors for Studio IDE sessions. This is impacting the dbt platform IDE in US Multi-Cell Azure. The team is working on a resolution as soon as new information becomes available. Job runs are not impacted and should be running as expected.

We have identified an issue with the dbt platform CLI Server that resulted in errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. A fix is being implemented, and we will provide an update shortly.

We have deployed a fix for the dbt platform CLI Server that was causing errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. The Studio IDE has returned to its normal state and we are continuing to monitor.

The issue has been resolved, and all affected systems are now functioning normally as of 3:22 PM Eastern. Between 2:53 PM Eastern and 3:22 PM Eastern an issue with the dbt platform CLI Server resulted in errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. The Studio IDE has returned to normal. Please contact Support via email [[email protected]](mailto:[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating an issue with the Snowflake adapter on the **Latest** release track that is causing some dbt jobs to fail when fetching large query result sets. The Snowflake connector is hitting a 7-second connection timeout while retrieving result data from Snowflake's internal storage, surfacing in run logs as: > Failed to fetch the large result set batch data_1 ... ConnectTimeoutError ... timed out (connect timeout=7) This is impacting jobs running on the **Latest** release track in deployments using Snowflake. The team is investigating the underlying cause and will provide updates at approximately 15-minute intervals as new information becomes available. **Workaround** Switching affected jobs to the **Compatible** or **Extended** release track resolves the failures immediately. For production workloads, we recommend **Extended** going forward as the most stable option.

We have identified an issue with a recent Snowflake adapter release that resulted in some dbt jobs failing when fetching large query result sets. A fix is being implemented, and we will provide an update shortly. **Workaround** Switching affected jobs to the **Compatible** or **Extended** release track resolves the failures immediately. For production workloads, we recommend **Extended** going forward as the most stable option.

We have deployed a fix for the Snowflake adapter that resulted in some dbt jobs failing when fetching large query result sets. We are continuing to monitor.

The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence and the Snowflake adapter has returned to normal. Please contact Support via email [[email protected]](mailto:[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [[email protected]](mailto:[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM Eastern. 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. Cron-scheduled jobs are not impacted and should be running as expected.

We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're investigating an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026\.5\.12+b52ab1d). The team is working on a resolution and we will provide updates as soon as new information becomes available.

We have identified an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026\.5\.12+b52ab1d). A fix is being implemented, and we will provide an update shortly.

We have deployed a fix for State Selector that is causing runtime errors when using the latest dbt version. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.

The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "**Failed to generate profile due to incorrect credentials. Please double check credentials and try again.**"

We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.

The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.

The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. Please contact Support via email [[email protected]](http://[email protected] "[email protected]") if you continue to experience delays and are unsure of the root cause.