What causes RESOURCE_MONITOR_SUSPEND?

A runaway query or a misconfigured pipeline consumed credits at an unexpectedly high rate and triggered the SUSPEND or SUSPEND_IMMEDIATE threshold. The resource monitor's credit quota was set for a monthly limit that was consumed faster than expected, for example due to increased report usage or a new data load. Multiple warehouses share a resource monitor with a single combined credit limit, and one warehouse consumed the budget allocated for all of them

How do I fix RESOURCE_MONITOR_SUSPEND?

Step 1: Identify which resource monitor triggered the suspension: SELECT * FROM SNOWFLAKE.ACCOUNT_USAGE.RESOURCE_MONITORS WHERE STATE = 'SUSPENDED'.. Step 2: If the credit limit overage is legitimate and expected, increase the monitor's credit quota: ALTER RESOURCE MONITOR SET CREDIT_QUOTA = .. Step 3: Resume the suspended warehouse: ALTER WAREHOUSE RESUME. Note: the warehouse will immediately re-suspend if the monitor limit is still exceeded.. Step 4: Investigate the root cause of the credit spike using QUERY_HISTORY to identify large or inefficient queries that ran before the suspension.

Critical severityresource

Power BI Refresh Error:
RESOURCE_MONITOR_SUSPEND

What does this error mean?

A Snowflake virtual warehouse was automatically suspended by a Resource Monitor after the monitor's credit consumption threshold was exceeded, causing all new queries to fail until the warehouse is resumed.

Common causes

1A runaway query or a misconfigured pipeline consumed credits at an unexpectedly high rate and triggered the SUSPEND or SUSPEND_IMMEDIATE threshold
2The resource monitor's credit quota was set for a monthly limit that was consumed faster than expected, for example due to increased report usage or a new data load
3Multiple warehouses share a resource monitor with a single combined credit limit, and one warehouse consumed the budget allocated for all of them

How to fix it

1Step 1: Identify which resource monitor triggered the suspension: SELECT * FROM SNOWFLAKE.ACCOUNT_USAGE.RESOURCE_MONITORS WHERE STATE = 'SUSPENDED'.
2Step 2: If the credit limit overage is legitimate and expected, increase the monitor's credit quota: ALTER RESOURCE MONITOR <name> SET CREDIT_QUOTA = <new_quota>.
3Step 3: Resume the suspended warehouse: ALTER WAREHOUSE <name> RESUME. Note: the warehouse will immediately re-suspend if the monitor limit is still exceeded.
4Step 4: Investigate the root cause of the credit spike using QUERY_HISTORY to identify large or inefficient queries that ran before the suspension.

Frequently asked questions

What is the difference between SUSPEND and SUSPEND_IMMEDIATE on a Resource Monitor?

SUSPEND waits for currently running queries to complete before suspending the warehouse, while SUSPEND_IMMEDIATE cancels all running queries and suspends the warehouse immediately.

Can a Resource Monitor notify before suspending?

Yes. Resource Monitors can be configured with multiple threshold levels — for example, NOTIFY at 75%, NOTIFY at 90%, and SUSPEND_IMMEDIATE at 100% — so you receive email warnings before the suspension occurs.