Snowflake dashboard query failed: warehouse suspended error in Tableau fix

TL;DR

Resume the Snowflake warehouse and turn on auto resume for the warehouse the Tableau connection uses. A suspended warehouse rejects or stalls the first queries until something resumes it, and Tableau connections do not always trigger the resume cleanly when the warehouse was suspended by an aggressive auto suspend setting or by an admin action. Checking the warehouse state in Snowflake is the fastest confirmation.

Snowflake dashboard query failed: warehouse suspended error in Tableau fix

Use this when

• Tableau views on Snowflake fail after idle periods and recover once someone runs a query in Snowflake directly.
• The Snowflake console shows the warehouse in a suspended state during the failures.
• The Tableau role can query when the warehouse is running but cannot start it.

Not for this skill when

• Queries fail with an object or schema permission error while the warehouse is running. Fix role grants instead.
• The warehouse is running but queries queue for a long time. That is a sizing or concurrency issue, not suspension.

Steps

1. Open the Snowflake console or run a warehouse status query and confirm the warehouse state during a failure window. Verify: the warehouse shows as suspended while Tableau views are failing
2. Resume the warehouse manually and immediately reload the Tableau dashboard. Verify: the views render data once the warehouse is running
3. Enable auto resume on the warehouse so future queries start it automatically. Verify: the warehouse properties show auto resume enabled
4. Confirm the role used by the Tableau connection holds the rights needed to use and resume the warehouse, and grant them if the resume test fails. Verify: a connection test as that role succeeds against a suspended warehouse
5. Review the auto suspend interval so the warehouse is not suspending between normal dashboard interactions. Verify: the suspend window is longer than the typical gap between viewer sessions
6. Reload the dashboard after an idle period without touching Snowflake first. Verify: the first viewer load succeeds because the query resumed the warehouse

Why it happens

Suspension is a cost feature working as designed, and the failure appears when the resume half of the contract is missing. Auto resume, role rights and a sane suspend interval are the three parts of that contract. Teams often find the issue after a cost saving pass tightened suspension without checking which BI connections depended on automatic resume.

Snowflake virtual warehouses suspend when idle to save credits, and they are expected to resume automatically when a query arrives if auto resume is enabled. When auto resume is off, or the Tableau role lacks the rights to resume the warehouse, dashboard queries fail with a warehouse suspended style error while the data itself is untouched. The pattern is worst on Monday mornings and after holidays, when the warehouse has been idle longest.

Field notes for the Snowflake side of this failure specifically. Warehouse state, auto suspend and auto resume settings, and the query history view in Snowflake give the ground truth that the BI tool error only hints at. The BI connection role is part of the configuration, not an afterthought, because resume and usage rights are granted to roles, and a connection that borrows a powerful personal role hides the problem until that person changes team. Test the connection with the actual service role the dashboard uses, from the actual tool, after any warehouse setting change.

Snowflake cost work and dashboard reliability pull in opposite directions here, and the resolution is scheduling rather than sacrifice. Warehouses serving interactive dashboards need resume behaviour that favours the first viewer of the day, while batch warehouses can suspend aggressively. Splitting dashboard traffic onto its own warehouse, sized for concurrency rather than raw speed, usually costs less than the incident time the shared arrangement produces. The query history makes the split easy to justify, because dashboard queries are recognisably short and frequent next to batch work.

Variants and edge cases

Snowflake warehouse suspended Tableau dashboard fails morning

The morning pattern phrasing for idle triggered suspension.

Tableau Snowflake warehouse is suspended auto resume fix

The setting-focused variant naming auto resume.

Snowflake warehouse suspended role cannot resume Tableau

The rights variant where the connection role cannot start the warehouse.

Provenance

Resolved from the public thread: https://vectle.com/posts/psthvHX2EfFXcwC0qg-DbGyQ