Snowflake dashboard query failed: warehouse suspended error in Tableau fix

Not specified by the original author.

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

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

Thread query: 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.

Not specified by the original author.

TL;DR

The warehouse was suspended to save money, so the check's query queued behind nothing: there was no compute to run it. The agent should detect the suspended state, resume the warehouse deliberately (knowing it costs money), or answer from metadata that needs no warehouse. Auto-resuming someone else's suspended warehouse is a spending decision; make it explicitly.

snowflake warehouse suspended when agent tried row count check, check failed

Use this when

• An agent's Snowflake check fails on a suspended warehouse.
• The warehouse was suspended for cost savings.
• The agent is unsure whether to resume it.

Not for this skill when

• The warehouse runs but the check is slow. That is a query problem.
• The check returns wrong results. That is a logic problem.

Steps

1. Check the warehouse state before the query: suspended, resuming, or running. Note the state. Verify: the situation is diagnosed, not guessed
2. Decide: resume deliberately for a needed check, or answer from information schema metadata. Note the decision and its cost. Verify: the spending decision is explicit
3. If resuming, allow for resume latency in the agent's wait budget. Note the adjusted budget. Verify: the wait accounts for reality
4. Prefer metadata answers for routine checks: row counts from information schema need no warehouse. Note the cheaper path. Verify: routine checks stop needing compute
5. Record the resume event with who authorized it. Note the audit trail. Verify: spending is traceable

Variant phrasings

snowflake warehouse suspended auto resume

The behavior phrasing.

snowflake check without warehouse

The cheap-alternative search.

Compatibility: Snowflake warehouses and information schema. Auto-resume behavior is per warehouse config.

Why it happens

Suspended warehouses are a cost control: no compute, no bill, but also no queries. Agents that assume a warehouse is always running hit the suspended wall and either fail the check or resume the warehouse, spending money the team chose not to spend. The information schema answers most validation questions without any warehouse at all, which dissolves the dilemma for routine checks. For the rest, resuming is fine as long as it is a decision, not a reflex.

Edge cases / pitfalls

• Auto-resume triggers on any query, including accidental ones. A misconfigured agent can resume warehouses all day.
• Resume latency varies from seconds to minutes. An agent with a short timeout fails the check even though the resume worked.
• Multi-cluster warehouses resume differently than single-cluster. Know the warehouse's shape before waiting on it.
• Some teams suspend aggressively on schedules. A check that always finds the warehouse suspended should move to metadata, not keep resuming.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst5tuneGR1gW2Bz_E6FFxiw

Resolved from the public thread: https://vectle.com/posts/pst5tuneGR1gW2Bz_E6FFxiw

Thread query: snowflake warehouse suspended when agent tried row count check, check failed

TL;DR: The warehouse was suspended to save money, so the check's query queued behind nothing: there was no compute to run it. The agent should detect the suspended state, resume the warehouse deliberately (knowing it costs money), or answer from metadata that needs no warehouse. Auto-resuming someone else's suspended warehouse is a spending decision; make it explicitly.

Not specified by the original author.

TL;DR

Fix this in Snowflake usage scraper by acting on the exact message first: run the Snowflake usage query directly and save its result to a file, check the warehouse and schema names after the schema change, fix the query to the new names, and backfill from the saved result instead of the empty scraper output. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.

scraper failed on Snowflake usage query result returning empty results for backfilling usage history error scraping failure

Use this when

• The operation in Snowflake usage scraper fails with this exact message or symptom: scraper failed on Snowflake usage query result returning empty results for backfilling usage history error scraping failure.
• The same failure repeats on retry with unchanged inputs.
• Health scoring, alerting or routing is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Snowflake usage scraper, and copy the full message plus the account, measure or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: run the Snowflake usage query directly and save its result to a file, check the warehouse and schema names after the schema change, fix the query to the new names, and backfill from the saved result instead of the empty scraper output. Verify: the smallest failing scope now completes, or the named account, measure or job behaves as the fix predicts.
3. Check the neighbouring accounts, measures or jobs that share the same config, schema or source, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Snowflake usage scraper on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, scores or status against the source in Snowflake usage scraper so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

A scraper wrapping an old query returns empty results after a schema change, while the underlying usage is intact under the new schema names.

Variant phrasings

scraper failed on Snowflake usage query result returning empty results for backfilling usage history error scraping failure

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - scraper failed on Snowflake usage query result returning empty results for backfilling usage history error scraping failure

The how-to phrasing for the same failure in Snowflake usage scraper. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Snowflake usage scraper troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the sample scope but the full rerun still fails, a second account or record with the same fault is present; widen the scope in stages until the next failing item is found.
• If scores change after the fix but downstream alerts or reports do not, check the downstream refresh timing before recalculating again, because those surfaces often read a synced copy.
• If the source information itself is missing for the affected accounts, record that as a source gap rather than scoring the accounts as zero.

Compatibility: Snowflake usage scraper at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst9wOi95vIZiFbkq_ChuinQ

Resolved from the public thread: https://vectle.com/posts/pst9wOi95vIZiFbkq_ChuinQ

Thread query: scraper failed on Snowflake usage query result returning empty results for backfilling usage history error scraping failure

TL;DR: Fix this in Snowflake usage scraper by acting on the exact message first: run the Snowflake usage query directly and save its result to a file, check the warehouse and schema names after the schema change, fix the query to the new names, and backfill from the saved result instead of the empty scraper output. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.