A release led to dbt invocations using dbt Cloud CLI to err with a message of "Internal server error, please try again" and Test Connections for Development and Deployment Credentials to err with a message of "Something went wrong." This impacted the US Azure Cell 1 and EU Cell 1 instances between 06:17 PM UTC and 08:40 PM UTC. A fix was released and the impacted components have recovered. All affected systems are functioning normally. Please contact Support via email at support@getdbt.com if you continue to experience issues or have any follow up questions.
Resolved
A release led to dbt invocations using dbt Cloud CLI to err with a message of "Internal server error, please try again" and Test Connections for Development and Deployment Credentials to err with a message of "Something went wrong." This impacted the US Azure Cell 1 and EU Cell 1 instances between 06:17 PM UTC and 08:40 PM UTC. A fix was released and the impacted components have recovered. All affected systems are functioning normally. Please contact Support via email at support@getdbt.com if you continue to experience issues or have any follow up questions.
Monitoring
We deployed a fix for dbt Cloud CLI that caused dbt invocations in dbt Cloud CLI to err with a message of "Internal server error, please try again" and Test Connections for Development and Deployment Credentials to err with a message of "Something went wrong." dbt Cloud CLI has returned to its normal state and we are continuing to monitor.
