Orchestration UI Update

We released a new version of Orchestration API and UI. The UI is completely rebuildm is lightning fast and everything can be now configured within a single UI. 

Here's a short list of the most exciting features:

  • orchestrations dashboard with the most important details about every orchestration
  • new orchestrations get a token and configuration table automatically (no more Storage Console)
  • orchestration tasks have a configuration UI, components are identified by names and icons instead of URLs

Happy orchestrating!

UPDATE: A short outage occurred while migrating Orchestrator configurations causing some of the orchestrations to fail to start on schedule. We restarted all failed orchestrations manually. We're sorry for this inconvenience.

SSL issues

We're experiencing some issues in our internal infrastructure. 

You can see following errors on affected orchestrations:

  • Error response from component
  • [curl] (#35)

We're working on a fix and restarting all failed orchestrations. We're sorry for this inconvenience.

Transformation MySQL server down

Our MySQL transformation server TAPI-A is down. We're offloading all work to the backup server, rerunning all failed orchestrations and restarting the TAPI-A server. 

We're sorry for this inconvenience, all operations should be back to normal soon and your transformations will switch to the restarted server automatically.

Provisioning API Update

We'll be updating Provisioning API today at 1:15 pm PST. This shouldn't take longer than 15 minutes. Transformations will be resumed, your credentials will still be valid, only creating of new sandboxes in the Transformation UI will be disabled during this period. 

1:30 pm PST: Migration completed. Thanks for your patience.

Randomly Failing Orchestrations

We're experiencing an AWS-wide DNS problem. Every 01 minute of each hour the DNS does not respond, which can cause failing attempts to connect between components in Keboola Connection. This will cause the running orchestration to fail.

It is reported all across AWS:


If your orchestration fails with an application error around 01 minute of an hour (it can propagate to the job a bit later, eg. at XX:02), you're most likely affected by this issue. Just re-running the orchestration will solve the problem. 

Please bear with us while we're trying to solve this issue with AWS Support. Here are some examples of failed orchestrations that might help you identify this issue.

Redshift Transformations: Input Mapping Enhancements

These options were turned off for VIEWs (input mappings from Redshift Storage to Redshift Transformation created as a VIEW):

  • Data Types (will inherit Storage data types in the future)
  • Sort Key
  • Dist Key

These options are still present for TABLE input mappings and for MySQL Storage or Transformation.

And on the other hand we turned on Days filter for all Input mapping (was previously turned off for all Redshift transformations). 

GoodData Maintenance Window

GoodData will be performing maintenance on our hardware on Saturday, September 13th around 1pm CET (4am PST). The expected length of the maintenance window is about 5 hours. Some of our client's GoodData projects will be inaccessible at that time. We apologize in advance for any inconvenience - the maintenance is necessary in order to prevent errors in near future. We will be monitoring all data load orchestrations and will restart them as needed.

Redshift Reboot

Due to peak load we had to reboot the main (shared) Redshift cluster. All transformation and sandboxes are stopped and purged, data stored on this cluster is temporarily unavailable. Will be back soon so you can resume your operations. 

We apologize for any inconvenience and kindly remind you, that you can have your own Redshift cluster. For more information get in touch with support@keboola.com.