Intermittent error: "Command failed because warehouse <<warehouse id>> was stopped."

[dbx_user]

The error "Command failed because warehouse <<warehouse id>> was stopped." has started popping up during deployment runs. Some times the error correlates with serverless warehouse cluster count reducing to zero while a query is running, sometimes it occurs while there is no change in active cluster count.

We have no logs to further investigate what is happening on the warehouse and why it is reporting as stopped when it is running, and why it is reducing cluster count to zero while there are active queries.

Is this a known issue?

[Walter_C]

How often does this issue occurs? Does this occurs with any type of query or with long running queries?

What is the Warehouse configuration?

[dbx_user2]

hi walter, thanks for the respone, i lost access to the first account i set up the below response from dbx_user2 is me, same user as dbx_user

[dbx_user2]

any update on this?

[dbx_user2]

We first noticed it this week, and have seen it occur intermittently about 10 times.

The warehouse is serverless compute, and the queries are being deployed from a dbt connection.

We have noticed the error pop up on queries that are being reported as running anywhere from 25 seconds up to ~9 minutes. But those query times for some of the queries are exception with standard times being in the order of seconds.

[Walter_C]

Are the queries showing as running or they are all queued when this happens? Does the warehouse has any termination timestamp set on the configuration?

[dbx_user2]

Uncertain if there is a termination timestamp set on the warehouse, and unable to say if the queries were running or queued before the event.

But there were occasions where we received this error when there were still running clusters and no cluster count  change.