Keboola Status

There is lot of sheduled jobs waiting in orchestrations queue, we are adding more workers to resolve this issue.

UPDATE 11:00 CET: Issue is resolved. All orchestrations should start immediately. Sorry for inconvience.

There was a bug in import to Storage API from transformations, it was present only in the following conditions:

• Redshift transformation with output to Redshift table
• Output was incremental
• Previously null value was changed to non null value

Null values were never updated in Storage API table. Bug is fixed now but the affected output tables have to recreated. The bug was present in Storage since the roll out of Redshift support.

Storage now supports snapshotting and creating tables from snapshots for Redshift backend. Snapshots are compatible between backends, so you can use snapshotting feature for migration of tables between backends.

Rollback is not supported for Redshift tables at the moment. 

As previously announced old Twitter extractor was shut down today.

Scheduled maintenance will start at 3:45 pm (GMT+1) and will take about 30 minutes.

During the maintenance, you can't access your data. All network connections will be terminated by "HTTP 503 - down for maintenance" status message.

UPDATE 4:30 pm: Maintenance is completed and all systems are back up and running. Few orchestrations were affected by maintenance and will be restarted by us.

The performance of Storage API was decreased between 11:30 - 12:30 CET. It affected also response time of  Keboola Connection user interface.

The issue is resolved now.

Several projects may have experienced errors in extractor jobs processing. Database, Zendesk, Google drive and some other extractors were affected. Issue is resolved now and we are investigation the cause of the issue.

We have restarted failed or waiting jobs. We're sorry for any inconvenience! 

Paymo, Facebook, Facebook Ads and Salesforce extractors were returning curl(60) error in orchestrations from 3 PM - 11PM PST November 6th. Error was caused by invalid SSL certificates.

To finish your tasks, just re-run your orchestrators. We're sorry for any inconvenience! 

Some files were not accessible between 7 PM - 10 PM PST November 4. It caused failures of loads to storage API tables and thus also orchestration failures.

Example of failed orchestration:

It was caused by failed Elasticsearch cluster node. We are still investigating the cause of this issue. However, our whole infrastructure works smoothly at this time. To finish your tasks, just re-run your orchestrators. We're sorry for any inconvenience!

Today, 30 October 2014, Keboola is announcing an End-of-Life date of January 31, 2015 for all instances of the Old Twitter Extractor.