Snowflake backend is experiencing service stability issues which may manifest itself as failed queries or service unavailability. Snowflake engineers are working on fix.
Read more on Snowflake status page.
Update (11:34 PM PST) - Snowflake is still in a recovery process and don't have a defined ETA.
Update (12:38 AM PST) - Service is back online
There were jobs failures between 1:30 AM - 6:15 AM UTC caused by flooded disk on one of our servers. We are making steps to avoid this issue happening again.
We're sorry for this inconvenience.
Few orchestrations have failed around 13:20 CET. The problem was caused by temporarily unavailable jobs storage.
We're sorry for this inconvenience.
There were jobs failures between 10:30 AM - 12:50 PM caused by low disk space on one of the jobs workers.
We're sorry for this inconvenience.
Snowflake is experiencing service outage which impacts projects with Snowflake backend.
Snowflake team is working to restore services as quickly as possible.
https://support.snowflake.net/hc/en-us/articles/213508163-August-23-2016-Service-Disruption-Update
We are sorry for any inconvenience.
UPDATE 11:12am PST
Snowflake service is back up and running.
We are investigating connection errors in projects with Snowflake backend. It is related to today's snowflake maintenance, we are in contact with their support.
We will update this post when we have more information. Sorry for any inconvenience.
UPDATE 09:30 PM PDT Storage is fixed and failed orchestrations were restarted. We are working on Snowflake transformations fix.
UPDATE 10:15 PM PDT Snowflake transformations are also working. Snowflake did the rollback of release which caused problems.
We are investigating a problem with waiting orchestrations jobs.
We will update this post when we have more information.
UPDATE 12:02 AM PDT We have found and fixed the issue, waiting orchestrations are now starting.
UPDATE 12:26 AM PDT All waiting jobs were processed. Everything should now be working normally. If you encounter some problem, please let us know.
Sorry for any inconvenience.
Some of Good Data writer jobs have failed between 22:59 PDT and 23:44 PDT.
It was caused by incident in Keen.io service which Good Data writer uses.
We are sorry for any inconvenience.
UPDATE: this issue has been solved and one shall not encounter the problem described below.
We have encountered problem when running orchestration manually from the orchestration detail page:
error message detail: "Error. [Task 0] Job task is different from orchestration task"
We are working on the fix of the problem which should be released within a short while.
Temporal workaround: if you are experiencing such a problem, you can fix it by resaving the orchestration tasks(Edit Tasks->Save).
All other orchestration features are working normally. We are sorry for any inconvenience.