What causes 000606 (XX000)?

Rare edge-case bug in Snowflake's query execution engine triggered by a specific query shape. Corruption or inconsistency in a table's micropartition metadata (uncommon). Memory pressure on the virtual warehouse during a complex query. A known Snowflake bug that affects the current version of the account. Complex JOIN or window function shapes that hit an unhandled code path

How do I fix 000606 (XX000)?

Retry the query once — transient internal errors sometimes resolve on retry. Simplify the query: break complex CTEs or window functions into smaller steps to isolate which part triggers the error. Try running the same query on a differently-sized warehouse — memory pressure is sometimes the cause. Run SHOW PARAMETERS IN ACCOUNT to check if any session parameters are set unusually. Open a Snowflake Support ticket with the full Query ID (visible in query history) — Snowflake engineers can inspect internal execution state using the Query ID. Check Snowflake's status page (status.snowflake.com) for active incidents affecting your region

High severityexecution

Power BI Refresh Error:
000606 (XX000)

What does this error mean?

Snowflake encountered an unexpected internal error while executing the SQL statement. This is a server-side fault, not a user error, and usually requires Snowflake Support involvement.

Common causes

1Rare edge-case bug in Snowflake's query execution engine triggered by a specific query shape
2Corruption or inconsistency in a table's micropartition metadata (uncommon)
3Memory pressure on the virtual warehouse during a complex query
4A known Snowflake bug that affects the current version of the account
5Complex JOIN or window function shapes that hit an unhandled code path

How to fix it

1Retry the query once — transient internal errors sometimes resolve on retry
2Simplify the query: break complex CTEs or window functions into smaller steps to isolate which part triggers the error
3Try running the same query on a differently-sized warehouse — memory pressure is sometimes the cause
4Run SHOW PARAMETERS IN ACCOUNT to check if any session parameters are set unusually
5Open a Snowflake Support ticket with the full Query ID (visible in query history) — Snowflake engineers can inspect internal execution state using the Query ID
6Check Snowflake's status page (status.snowflake.com) for active incidents affecting your region

Frequently asked questions

Is 000606 always a Snowflake bug?

Usually yes — it is an unhandled condition in Snowflake's engine. However, extreme edge cases in query structure (e.g., recursive CTEs, very deep nesting) can reliably trigger it. Simplifying the query is always worth trying before escalating.

Where do I find the Query ID?

In Snowflake's web UI: Activity → Query History. In the Python connector or JDBC, the Query ID is returned in the exception's message or as a cursor attribute (cursor.sfqid).