MetricSign
EN|NLRequest Access
High severitytimeout

Power BI Refresh Error:
DbtAdapterTimeout

What does this error mean?

A dbt adapter call to the database warehouse timed out before receiving a response, causing the dbt run to fail.

Common causes

  • 1A dbt model's SQL query exceeded the warehouse query timeout setting
  • 2The warehouse was overloaded with concurrent queries and queued the dbt job past its connection timeout
  • 3A network interruption between dbt and the data warehouse caused the connection to hang
  • 4The dbt profile's connect_timeout setting is too low for the warehouse's startup time

How to fix it

  1. 1Step 1: Check the dbt run logs for which model timed out and the elapsed time before the error.
  2. 2Step 2: Increase the query timeout in the dbt profile: for Snowflake, set query_tag and increase the warehouse query_timeout; for BigQuery, set job_execution_timeout.
  3. 3Step 3: Optimize the timing-out model — add incremental logic, partitioning, or clustering to reduce query time.
  4. 4Step 4: Check warehouse resource utilization at the time of failure — scale up if the warehouse was at capacity.
  5. 5Step 5: Retry the failed model: dbt run --select failed_model_name --full-refresh.

Frequently asked questions

How do I set query timeout in dbt profiles for Snowflake?

Add query_tag to the Snowflake profile and use an ALTER SESSION SET STATEMENT_TIMEOUT_IN_SECONDS = N; pre-hook in the problematic model, or set it globally in the Snowflake user/role parameters.

Does dbt retry timed-out models automatically?

No — dbt does not retry failed models by default. Use dbt retry (dbt 1.6+) to re-run only the failed nodes from the previous invocation without re-running successful models.

Other timeout errors