What causes 000603 (XX000)?

Query was explicitly cancelled by a user or by a SYSTEM$CANCEL_QUERY() call. Session or statement timeout (STATEMENT_TIMEOUT_IN_SECONDS) was reached. The virtual warehouse was suspended or restarted mid-query. A Snowflake warehouse auto-suspend occurred during a long-running query. Snowflake platform maintenance or internal resource reclamation aborted the query

How do I fix 000603 (XX000)?

Check query history for the query status — if marked 'cancelled' it was explicitly stopped. Increase STATEMENT_TIMEOUT_IN_SECONDS for long-running queries: ALTER SESSION SET STATEMENT_TIMEOUT_IN_SECONDS = 3600. Set AUTO_SUSPEND to a higher value on the warehouse so it does not suspend during active queries: ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = 600. For ETL jobs, configure retry logic to re-run aborted queries automatically. If aborts occur on a shared warehouse, consider a dedicated warehouse for long-running batch jobs

Medium severityexecution

Power BI Refresh Error:
000603 (XX000)

What does this error mean?

Snowflake aborted query processing before completion. This typically happens due to a user-initiated cancel, a session timeout, a warehouse restart, or an internal resource limit being reached.

Common causes

1Query was explicitly cancelled by a user or by a SYSTEM$CANCEL_QUERY() call
2Session or statement timeout (STATEMENT_TIMEOUT_IN_SECONDS) was reached
3The virtual warehouse was suspended or restarted mid-query
4A Snowflake warehouse auto-suspend occurred during a long-running query
5Snowflake platform maintenance or internal resource reclamation aborted the query

How to fix it

1Check query history for the query status — if marked 'cancelled' it was explicitly stopped
2Increase STATEMENT_TIMEOUT_IN_SECONDS for long-running queries: ALTER SESSION SET STATEMENT_TIMEOUT_IN_SECONDS = 3600
3Set AUTO_SUSPEND to a higher value on the warehouse so it does not suspend during active queries: ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = 600
4For ETL jobs, configure retry logic to re-run aborted queries automatically
5If aborts occur on a shared warehouse, consider a dedicated warehouse for long-running batch jobs

Frequently asked questions

Does STATEMENT_TIMEOUT_IN_SECONDS override the warehouse-level setting?

Session-level settings take precedence over warehouse defaults. Set the timeout at the session level in your connector or at the warehouse level with ALTER WAREHOUSE ... SET STATEMENT_TIMEOUT_IN_SECONDS.

Will increasing AUTO_SUSPEND cause higher Snowflake costs?

Yes — a warehouse that stays running longer consumes more credits. Balance this against the cost of re-running aborted jobs. For batch ETL, a dedicated warehouse with a longer auto-suspend is usually more cost-effective than retries.