What causes DbtRuntimeError: warehouse suspended?

The Snowflake virtual warehouse was manually suspended by an administrator or an automation script. The Snowflake account hit its credit limit and all warehouses were automatically suspended. The warehouse's auto-resume setting is disabled, preventing it from resuming when dbt attempts to use it. The dbt service role does not have USAGE or OPERATE privilege on the warehouse, causing a permissions-based suspension error. A Snowflake resource monitor threshold was crossed and the monitor policy suspended the warehouse

How do I fix DbtRuntimeError: warehouse suspended?

Log in to the Snowflake console and check the warehouse status: `SHOW WAREHOUSES;` — look for warehouses with STATE = SUSPENDED.. Resume the warehouse manually: `ALTER WAREHOUSE RESUME;`. Check resource monitors: `SHOW RESOURCE MONITORS;` — if a monitor triggered suspension, review the credit threshold and reset if appropriate.. Verify auto-resume is enabled for the warehouse: `ALTER WAREHOUSE SET AUTO_RESUME = TRUE;`. Confirm the dbt service role has USAGE and OPERATE on the warehouse: `GRANT USAGE ON WAREHOUSE TO ROLE ; GRANT OPERATE ON WAREHOUSE TO ROLE ;`

High severityinfrastructure

Power BI Refresh Error:
DbtRuntimeError: warehouse suspended

What does this error mean?

dbt connected to Snowflake successfully, but the virtual warehouse targeted by the dbt profile was suspended and could not be automatically resumed within the allowed window. All models fail at execution start with a runtime error referencing the suspended or unavailable warehouse.

Common causes

1The Snowflake virtual warehouse was manually suspended by an administrator or an automation script
2The Snowflake account hit its credit limit and all warehouses were automatically suspended
3The warehouse's auto-resume setting is disabled, preventing it from resuming when dbt attempts to use it
4The dbt service role does not have USAGE or OPERATE privilege on the warehouse, causing a permissions-based suspension error
5A Snowflake resource monitor threshold was crossed and the monitor policy suspended the warehouse

How to fix it

1Log in to the Snowflake console and check the warehouse status: `SHOW WAREHOUSES;` — look for warehouses with STATE = SUSPENDED.
2Resume the warehouse manually: `ALTER WAREHOUSE <warehouse_name> RESUME;`
3Check resource monitors: `SHOW RESOURCE MONITORS;` — if a monitor triggered suspension, review the credit threshold and reset if appropriate.
4Verify auto-resume is enabled for the warehouse: `ALTER WAREHOUSE <warehouse_name> SET AUTO_RESUME = TRUE;`
5Confirm the dbt service role has USAGE and OPERATE on the warehouse: `GRANT USAGE ON WAREHOUSE <warehouse_name> TO ROLE <dbt_role>; GRANT OPERATE ON WAREHOUSE <warehouse_name> TO ROLE <dbt_role>;`

Frequently asked questions

Why would a Snowflake warehouse suspend automatically?

Snowflake warehouses auto-suspend after a configured idle period (default: 10 minutes) to save credits. They auto-resume on next query — unless auto-resume is disabled or a resource monitor has suspended the warehouse due to credit limits.

How do I prevent this from happening again?

Ensure `AUTO_RESUME = TRUE` is set on the warehouse. If a resource monitor triggered the suspension, increase the credit quota or set the monitor action to NOTIFY instead of SUSPEND.