What causes Snowflake Budget Exceeded Notification?

A warehouse is running more than expected (long queries, missing auto-suspend, or a loop in a Snowflake Task). Automatic Clustering or Materialized View maintenance consumed more credits than budgeted. A data load pipeline ran longer than expected due to file volume growth. A runaway query or task loop consumed credits without a circuit breaker

How do I fix Snowflake Budget Exceeded Notification?

Check the budget alert in Snowsight under Admin → Cost Management → Budgets.. Identify the credit consumer: `SELECT * FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY WHERE START_TIME > DATEADD('hour',-24,CURRENT_TIMESTAMP()) ORDER BY CREDITS_USED DESC`.. For runaway tasks: `SELECT * FROM TABLE(INFORMATION_SCHEMA.TASK_HISTORY()) WHERE STATE = 'RUNNING' ORDER BY SCHEDULED_TIME DESC` to find long-running tasks.. Enable auto-suspend on all warehouses: `ALTER WAREHOUSE SET AUTO_SUSPEND = 60`.. Add a STATEMENT_TIMEOUT to long-running queries to prevent a single query from consuming excessive credits.

Medium severitycapacity

Power BI Refresh Error:
Snowflake Budget Exceeded Notification

What does this error mean?

A Snowflake Budget reached its configured spending threshold and triggered a notification or action. Depending on the budget configuration, warehouses may be suspended automatically when the credit limit is hit.

Common causes

1A warehouse is running more than expected (long queries, missing auto-suspend, or a loop in a Snowflake Task)
2Automatic Clustering or Materialized View maintenance consumed more credits than budgeted
3A data load pipeline ran longer than expected due to file volume growth
4A runaway query or task loop consumed credits without a circuit breaker

How to fix it

1Check the budget alert in Snowsight under Admin → Cost Management → Budgets.
2Identify the credit consumer: `SELECT * FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY WHERE START_TIME > DATEADD('hour',-24,CURRENT_TIMESTAMP()) ORDER BY CREDITS_USED DESC`.
3For runaway tasks: `SELECT * FROM TABLE(INFORMATION_SCHEMA.TASK_HISTORY()) WHERE STATE = 'RUNNING' ORDER BY SCHEDULED_TIME DESC` to find long-running tasks.
4Enable auto-suspend on all warehouses: `ALTER WAREHOUSE <wh> SET AUTO_SUSPEND = 60`.
5Add a STATEMENT_TIMEOUT to long-running queries to prevent a single query from consuming excessive credits.

Frequently asked questions

Can Snowflake Budgets automatically suspend warehouses when the limit is hit?

Budgets send notifications (email or Snowflake notification integration) but do not automatically suspend warehouses on their own. Resource Monitors can suspend warehouses at thresholds — use both together for cost control.