AWS us-east-1 internal job errors [resolved]

2022-08-04 12:05 UTC We are investigating internal job errors. Next update in 30 minutes.

2022-08-04 12:36 UTC We experienced two waves of internal errors, between 11:50-11:57 and 12:00-12:07 UTC. The root cause has been removed and I don't see any other errors in the reporting. We continue to monitoring the situation. Next update in 30 minutes.

2022-08-04 13:06 UTC All Keboola Connection services are running normally. The incident is resolved. 

We apologize for any inconvenience.

Tables with _tmp suffix might be dropped

We are experiencing an issue with possibility of tables with _tmp suffix might be dropped.

If you manipulate with a table <X> and there also exist a table with name <X>_tmp, the table <X>_tmp could be accidentally dropped.

These tables (<X> and <X>_tmp) have to be in the same bucket and your project has to have Snowflake backend. We found the root cause and fix will be deployed in 2 hours.

Affected tables will be restored.

2022-08-02 17:00 UTC - We have deployed the fix of this issue and fixed affected tables. The issue is now resolved. We contact affected customers directly.

We are sorry for the inconvenience.

Delayed orchestrations on Azure North Europe stack

2022-08-02 7:00 UTC We are investigating delayed orchestrations on Azure North Europe Keboola Connection stack (https://connection.north-europe.azure.keboola.com). Next update in 30 minutes.

2022-08-02 7:30 UTC  After our investigation, problem starts at 6:00 UTC. Orchestrations that should have be scheduled after this time, were delayed in the order of minutes or tens of minutes. Situation returned back to normal at 7:15 UTC and all orchestrations are scheduled properly.


We are sorry for the inconvenience.

Slower Snowflake transformation loads for dynamic backends

2022-07-27 11:12 UTC - Snowflake transformations does not respect selected warehouse size during input mapping which might lead to slower processing times. We are working on a  fix which might be deployed in 4 hours.

2022-07-27 14:59 UTC - The fix was not yet deployed due to unexpected complications. We are working on it and the fix should be deployed in 4 hours.

2022-07-27 17:34 UTC - The fix was deployed. All Snowflake transformations are now using correct Warehouse size for execution. The issue is now resolved.

Tables with _tmp suffix might be dropped

We are experiencing an issue with possibility of tables with _tmp suffix might be dropped. These tables have to be in the same bucket, and there have to exist a table with the same name, just without the _tmp suffix. We found the root cause and we are working on a fix which might be deployed in 4 hours.

2022-07-27 11:17 UTC - We have deployed the fix of this issue. Affected customers were contacted directly. We'll undrop affected tables.

2022-07-27 16:34 UTC - We have fixed affected tables. The issue is now resolved. We are sorry for the inconvenience.


Migration to the new Job Queue in North Europe (Continuation)

Starting on August 8th we will resume migrations to the new Job Queue in our Azure North Europe stack.

This is a follow up to the previous round of migration, and all relevant information can be found in our previous post.

If you're not sure if your project is already on the new Job Queue, go to orchestrations in your project and if the url ends with "orchestrations-v2" then your project is already on the new Job Queue.

If you have any questions regarding the migration, please contact us via support@keboola.com



PostgreSQL data destination writing no data

Today at 07:38 (UTC) a new version (1.9.1) of PostgreSQL data destination was released which introduced a bug causing some configurations to write no data. The component version was rolled back to 1.9.0 at 13:48 (UTC) and everything should work as expected.

If you still encounter similar symptoms please let us know.

We're sorry for this inconvenience. 

Stricter use of parameters in the Create File Resource API endpoint

We recently updated the API endpoint for Create File Resource to make the validation of the parameters stricter. In doing so, we discovered a misuse in our code examples (Python Example, Manually Uploading a File).

If your Create File Resource stops working, please modify the Create File Resource API endpoint call to insert the parameter federationToken=1 into the body of the API call.

If you need any more information, please visit our documentation.

We apologize for any inconvenience.