Signing into KBC with your Google account is not working presently.
We're investigating and hope to have it resolved shortly.
In the meantime, please sign in using the standard email and password method.

Sorry for this inconvenience,  this post will be updated when further information becomes available.

UPDATE 08:21 UTC We have identified the issue. The fix will be deployed in ASAP.

UPDATE 08:55 UTC Signing in with your Google account is again fully operational.

We've noticed some write jobs to GoodData have been failing since their most recent maintenance period.  

We're investigating the issue and will update here as soon as possible.

Update 11:30AM March 12, 2017

The failures were due to a breaking change update to the GoodData date dimension API during their last maintenance period.   It should only affect projects which are using custom date dimensions.  We are currently assessing options to remedy the situation.

Update 20:30 CET March 12, 2017

For any orchestration that failed to write to GoodData this weekend, in order to have it run correctly, please edit the task and change the action from `upload-project` to `load-data`.  It should then work correctly if you re-run it. 

Please note however that new writers with custom time dimensions, or changes to old configurations which had them, may still fail.

Update 13:20 CET March 13, 2017

GoodData has fixed the issue. All existing configurations should work now. The switch from `upload-project` to `load-data` is no longer required, but we still recommend it as best practice to prevent possible future issues.

Update 07:00 CET March 14, 2007

In some cases the GoodData writer jobs are still failing. Switching to `load-data` is the correct remedy. Read what GoodData has to say.

Update 15:47 CET March 14, 2007

The issue seems to have been completely resolved as per GoodData Support.  

Improvements

• Description of transformation configuration shows up in a preview

• Improved description of deprecated GoodData extractor migration 

• Goodata user role Keboola Editor Plus has been extended by the following permissions:

• canValidateProject
• canCreateFolder
• canManageAttribute
• canManageAttributeLabel

Fixes

• Maximum size of log file of docker based component has been limited to prevent flooded disks job failures such as http://status.keboola.com/failed-jobs-2 or http://status.keboola.com/job-failures-6

• Fixed Storage Api bug caused by unlinking a shared bucket from a project containing more shared buckets.

There were  jobs failures between 1:30 AM - 3:30 AM UTC caused by flooded disk on one of our servers. We are investigating the causes of the issue.

New features

• We have introduced new AWS S3 extractor
• RStudio and Jupyter Sandboxes are available for testing. If you are interested in playing with these Sandboxes please contact us at support@keboola.com. Thank you all for interest and feedback. 

Bugfixes and minor improvements

• Fixed setting of primary key on Redshift backed table when table contained column name row_number
• Invalid data type errors are propagated to user when loading data into sandboxes or transformations
  
• Access to snowflake sandbox https://keboola.snowflakecomputing.com/console sometimes didn't work. Fixed.
• Fixed frozen table selector in writers
• CSV import - gzipped files are supported
• It is now possible to select server version in SQL Server Database Writer:

Developers

• OAuth credentials injection - all required credential parameters in the configuration can be pasted directly.

In an effort to increase account sovereignty we've introduced a new feature that will give you more control over who can access your projects and for what purposes.   It is now possible to require that visiting support administrators have their access request approved by an existing project member in order to temporarily join a project.

The setting can be found in your Account settings at the organization level.  This setting will apply to all projects within the organization.

When the support user completes the request form, an email describing the access request is sent to each project member.  

The requested access will be listed in the project settings Users section and can be approved or rejected by any active project member.

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

A couple of months ago we launched a new version of Google Drive Extractor and promised to release a migration tool.

Well it took a bit more time then we expected, but as promised, here it is. This tool will help you migrate your configurations to the new version of the extractor.

How to

1. Click "Proceed to Migration" button in any configuration of the old Google Drive Extractor
2. A dialog window will open with a list of all configurations in the project
3. Click the "Migrate" button and a migration job will be created
4. You can watch the progress of the migration job either in the migration dialog window or in the Jobs list
5. When the job has finished, you can see the result of the migration for every configuration and also any affected orchestrations will be listed in the "Affected Orchestrations" tab

Backward compatibility

The much anticipated Snowflake Database Writer is now available!

Key features:

• container based architecture
• upload data to your own Snowflake database or use a Keboola provisioned database. 
  
• SSH tunnel
  
• incremental load
  

Provisioned database limits:

You can use a Snowflake database provisioned by us, and this database is included in the price of your Keboola Connection project.  Please note, however, that there is a 15 second timeout per query, and an additional fee will be required in order to increase this timeout.

If you have any questions or troubles setting up this writer, please contact our support at support@keboola.com.

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.