Zendesk is down, so our support system is inaccessible. Keboola Connection is unaffected, but if you run into anything critical, please reach us via email.

We'll update this post when we obtain more information.

Update 14:36 UTC - Looks like things are back to normal now.

New Features

• You can now schedule orchestrations by table events.  Do you want to run an orchestration as soon as a key table gets updated?  You can do that now!  Please refer to the documentation to help guide you through it.
  

  
  
  
  
• When creating a new token you can now restrict its access to the configuration trash bin
  

  

Improvements

Transformations

• Transformations can now be copied to the same bucket or an other transformation bucket
  
  
• Simplified version diffs for scripts
  

  
  
  
  
• You will now be given a warning if you cannot extend your sandbox because of required system upgrades
  

  
  
  
  

Orchestrations

• For notifications, you can now choose from any email of any user that has previously worked on the orchestration or of course enter one of your choosing

  
  
  
  
• On the orchestrations listing page it will show if the orchestrations were manually triggered, event triggered, or scheduled
  

  
  
  
  

SQL Server extractor

• Allows incremental fetching by timestamp data type columns
  
  
• A new option to disable use of the fallback driver on failure

Developers

• We are now always displaying the documentation link for components, so please make sure that your components have it filled in the Developer Portal.  If you have the documentation link then you can remove excess documentation from the long description.

Today, Thursday 20, 2019 from 02:02 CET, one of our job workers became unresponsive.

This resulted in some jobs taking longer to process as they had to wait for one of the other available workers whose workload had increased as a result.

The affected instance was replaced at 15:50 CET and we are working on improving the automated detection of such failures.

Thank you for your understanding.

Update 12:36 UTC:

Everything should be back to normal. We'll keep monitoring our systems.

Update 9:15 UTC:

You should not experience any more errors, but things are a bit overloaded so longer execution and waiting times are expected. Thank you for patience.

Update 7:52 UTC:

Snowflake services restored. We're resuming processing of jobs.

Update 6:23 UTC:

Snowflake services are still not restored. We're slowing down job processing, so you'll see a much larger amount of queued jobs. EU region is unaffected.

Original post:

Some Snowflake queries started failing around 03:14 UTC which is causing errors in job processing. Failures are caused by incident which is currently investigated by Snowflake https://status.snowflake.com/incidents/0sjfn3d5jq2q .

We will provide an update as soon as the issue is resolved.

Today, on April 13 2019 from 14:14 UTC to 14:15 there were some orchestration failures in the US region due to an internal system upgrade. Very few orchestrations were affected, please review your orchestration and restart if needed. This issue is not related to the issue with failing orchestrations happened previously today.

[2019-04-13 8:20 CET]

We are registering increased amount of failing orchestrations since 2:27 CET. We are investigating the issue now and will keep you updated.

[2019-04-13 8:45 CET]

We traced down the problem and fix it. Everything seems to be working now, we continue monitoring it. Please review your orchestrations and restart them if necessary

Updated Components

DB extractors:

• Source shows schema as well as table name in tables list. Also it's visible from first glance which tables are created from a storage table and which are from SQL. 

  

• Table schema is shown also in config rows detail sidebar

  

• When adding tables you can click the schema name and all tables in schema at once

  

  

Execution of some table import jobs scheduled after 07:42 UTC was delayed up to 30 minutes. The delay was caused by new platform release which was immediately rolled back. All systems are now operational.

Today, on March 15 2019 from 16:34:15 UTC to 16:35:12 UTC there were some orchestration failures in the US region due to an internal system upgrade.

There were not many failures (around 20, so very few are affected), but if you had an orchestration running at that time, please check to make sure that you were unaffected.

We are working on making sure that this will not happen again for any future upgrades.

We were affected by a brief outage of the EU region Snowflake database on Mar 07 between 17:45:00 UTC and 18:25:00 UTC in the EU region. The problem affected extractors and transformations. Please check your orchestrations and re-run them if necessary. Projects in the US region were unaffected. We apologise for the inconvenience caused.