DBT jobs fail due to SQL warehouse stopping mid execution

Kutbuddin — Thu, 07 Aug 2025 06:24:29 GMT

+ dbt seed 15:49:17 Running with dbt=1.10.6 15:49:19 Registered adapter: databricks=1.10.8 15:49:20 Unable to do partial parsing because saved manifest not found. Starting full parse. 15:49:25 Found 27 models, 73 data tests, 1 seed, 7 sources, 686 macros 15:49:25 15:49:25 Concurrency: 8 threads (target='databricks_cluster') 15:49:25 + dbt seed 15:49:17 Running with dbt=1.10.6 15:49:19 Registered adapter: databricks=1.10.8 15:49:20 Unable to do partial parsing because saved manifest not found. Starting full parse. 15:49:25 Found 27 models, 73 data tests, 1 seed, 7 sources, 686 macros 15:49:25 15:49:25 Concurrency: 8 threads (target='databricks_cluster') 15:49:25 16:03:28 databricks-sql-connector adapter: ThriftBackend.attempt_request: Exception: %s ERROR:databricks.sql.thrift_backend:ThriftBackend.attempt_request: Exception: Retry request would exceed Retry policy max retry duration of 900.0 seconds 16:03:28 16:03:28 Finished running in 0 hours 14 minutes and 2.83 seconds (842.83s). 16:03:28 Encountered an error: Database Error Error during request to server. Retry request would exceed Retry policy max retry duration of 900.0 seconds

Subsequent retriggers fail as well failing jobs midway since the SQL warehouse goes down while the job is executing.

Setup is using both Serverless cluster and a Serverless SQL warehouse.

It is also to be noted this occurred across 4 different jobs on 6th Aug 2025 itself which is not a coincidence

Re: DBT jobs fail due to SQL warehouse stopping mid execution

SP_6721 — Fri, 08 Aug 2025 14:41:32 GMT

Hi @Kutbuddin ,

Looks like Databricks SQL Warehouse downtime. Are you still seeing failures on reruns or was it just on that day?

topic DBT jobs fail due to SQL warehouse stopping mid execution in Data Engineering

DBT jobs fail due to SQL warehouse stopping mid execution

Re: DBT jobs fail due to SQL warehouse stopping mid execution