dbt Studio error loop with restarting dbt Studio
dbt Cloud reported an error loop in dbt Studio that asked users to restart dbt Studio. The issue affected dbt Project Environments on versions 1.6 and 1.7. dbt Cloud resolved the issue after 86 minutes.
State
Resolved
Started
Lasted
1 h 26 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
22 min 26%
Identified
18 min 21%
Monitoring
46 min 53%
Updates
Times in UTCAs posted by dbt Cloud
The issue has been resolved, and all affected systems are now functioning. We have put measures in place to prevent a recurrence and the Studio IDE has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.
We have deployed a fix for Studio IDE that was causing a restart loop on dbt Project Environments utilizing dbt versions 1.6 and 1.7. Studio IDE has returned to its normal state and we are continuing to monitor.
We have identified an issue with recent release that resulted in the dbt Studio restart loop on dbt Project Environments running on version 1.6 and 1.7. A rollback of this release is being implemented, and we will provide an update shortly.
We're investigating reports of an issue with dbt Studio/IDE that is causing an error loop (dbt Studio prompts to be restarted, resulting in a loop). The currently identified scope of impact is Projects running on legacy v1.6 and 1.7 anytime after 1:00 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available.
We're investigating an issue with dbt Studio/IDE that is causing an error loop (restart dbt Studio). This is impacting projects running v1.6 and 1.7 in multi-tenant anytime after 1:00 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
25
Median duration
2 h 37 min
This incident
45% shorter than the median
Other dbt Cloud incidents
All incidentsdbt Cloud·Expired GitLab project access tokens not refreshing causing failures in posting commit statuses
dbt Cloud did not post GitLab CI job commit statuses for existing projects with expired GitLab project access tokens. This affected a small number of customers in the EU2 (Azure) region. dbt Cloud reports that the issue is resolved and that it lasted about 111 minutes.
dbt Cloud·dbt Wizard SQL execution failing
The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.
dbt Cloud·Degraded performance across dbt platform
The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. Between 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform has returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause
dbt Cloud·dbt deps failures in dbt job runs and Studio
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 [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.
dbt Cloud·Delayed and stuck job runs in EMEA
**Update posted at 15:05 UTC:** This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected. If you still see any issues, please contact support.
Follow dbt Cloud
Your coding agent knows when dbt Cloud is down, and tells you when a failure is theirs, not yours. You can also get dbt Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dbt" and tell me if dbt Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=dbt/feed subscribe https://outages.live/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane