dbt Jobs failing for some accounts with dbt State
dbt Cloud jobs that use dbt State failed for some accounts. Runs failed with the error "Cannot determine the account ID. Please make sure dbt State is enabled in your account." The incident is resolved. dbt Cloud reports the problem lasted from 20:41 UTC to 21:30 UTC.
State
Resolved
Started
Lasted
4 h 37 min
Worst impact
Partial outage
Timeline
4 updatesInvestigating
1 h 12 min 26%
Identified
1 h 45 min 38%
Monitoring
1 h 40 min 36%
Updates
Times in UTCAs posted by dbt Cloud
The issue has been resolved, and all affected systems have been functioning normally since 21:30 UTC. Between 20:41 UTC and 21:30 UTC, an issue with dbt State caused some scheduled jobs to fail with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.” We have put measures in place to prevent a recurrence, and jobs have returned to normal. If you disabled dbt State on your jobs as a workaround, you can re-enable it. If you continue to experience job failures and are unsure of the root cause, please contact Support at [support@getdbt.com](mailto:support@getdbt.com).
We have deployed a fix for dbt State that was causing jobs to fail. Affected runs were failing with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.” Runs on previously failing accounts are now completing successfully. We are continuing to monitor. If you disabled dbt State on your jobs as a workaround, you can re-enable it. If you still see this error after re-enabling, please contact support.
We have identified an issue causing some scheduled dbt jobs to fail for customers using dbt State. Affected runs fail with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.” Our team has been alerted and is actively working to resolve the issue. Users can resolve this issue by temporarily disabling dbt State on their jobs.
We are currently investigating an issue causing some scheduled dbt jobs to fail for customers using dbt State. Affected runs fail with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.” Our team has been alerted and is actively working to understand the scope and resolve the issue
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
32
Days with an incident
30
Median duration
1 h 46 min
This incident
2.6× the median
Other dbt Cloud incidents
All incidentsdbt Cloud·500 errors when attempting to access Studio and link Github account
dbt Cloud had 500 errors that stopped access to dbt Studio and the linking of GitHub accounts. dbt Cloud reports that the issue is resolved. The outage lasted 50 minutes.
dbt Cloud·Update to spark-utils package causing job run failures
dbt Cloud job runs failed with a compilation error for projects that use the spark-utils package on adapters other than Databricks/Spark. dbt Cloud released version 0.3.5 on the dbt Hub as a fix. The issue is resolved and lasted 58 minutes.
dbt Cloud·Wizard agent conversations returning errors
dbt Cloud Wizard agent conversations that use Anthropic models returned an error on every new message. dbt Cloud reports that the incident is resolved. The incident lasted about 102 minutes.
dbt Cloud·Wizard agent conversations returning errors
dbt Cloud Wizard agent conversations returned errors on new messages. The issue affected conversations that used Anthropic models. dbt Cloud resolved the incident after about 62 minutes. As a workaround, switching to an OpenAI model restored functionality.
dbt Cloud·Cloud IDE sessions failed to load
The issue has been resolved, and all affected systems are now functioning normally as of 17:47 UTC. Between 11:24 UTC and 17:47 UTC an issue with a long running CLI worker node resulted in indefinite load times in the IDE. We have put measures in place to prevent a recurrence and IDE behavior 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.
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