There is an issue which causes a 404 error (Page not found) to be displayed after login. We're working on a fix, which should be ready shortly.

The issue affects only log-in of certain users on the UI. Jobs running inside projects are unaffected.

Update 13:01 UTC: The problem is fixed. We apologize for the inconvenience, we'll share more details in a post-mortem.

Today, 30.7.2019, 18:30 CET we noticed errors when creating projects using promocodes via https://try.keboola.com. We rollbacked app to the previous version and everything is working now. Moreover we continue investigating the cause of the error.

We are investigating a Google Drive Extractor authorization verification issue in Keboola Connection EU.

Only creation of new configurations is affected.

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

Update 2019-08-14: The verification issue is resolved and new configuration are working again.

Updated Components

Event triggered orchestrations

Following writers now set data types based on metadata:

• Tableau TDE
• Impala
• Mssql
• Mysql
• Oracle
• PostgreSql
• Redshift
• Thoughspot
• BigQuery v2

You can read more about Storage data types in the docs.

Gooddata Writer v3

• Fact grain is no longer reset when switching from full to incremental load

Other components

• Our new FTP Extractor is out of beta
• AdForm Extractor is deprecated

New Features

Notification of concurrent editing

A warning message is displayed when you try to edit a configuration that's being edited by someone else at the same time. It also warns you if you are editing the same configuration in a different browser tab. 

CAPSLOCK notification for password field

When you focus the password field and your capslock is enabled, you'll see a notification. 

Keboola is hosting our inaugural Q3/2019 customer webinar and we want you there! If you haven’t done so already, please register now.  Learn about new features, functionalities, and components that we have built during the first half of the year.  Additionally, see the exciting plans that we have for Keboola over the next 3-12 months.

We hope you can join us!  The webinar will be available on video by request afterward as well.

Register here.

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.