Orchestrations not starting on legacy job queue

2023-04-26 11:00 UTC - We have discovered a problem with orchestrations not starting on the legacy queue. We are currently investigating possible causes.

2023-04-26 11:30 UTC - The problem was caused by a release earlier today, and as a result, no orchestrations on the legacy queue were run since 08:10 UTC. We have done rollback of the release and orchestrations should be functioning properly again as of 11:30 UTC. We apologize for any inconvenience caused.

Limited service disruption for AWS US

A limited service disruption on AWS US stack will start at 09:00 a.m. UTC today, as announced earlier. Storage jobs processing will stop and new jobs will be delayed until the upgrade is completed. All running jobs will be cancelled, but will resume after the upgrade.

All APIs and other unaffected services, such as Workspaces and Jobs, will remain operational, though their operations may be delayed due to the Storage job delays. We will provide an update when the service disruption starts and ends. 

We apologize for any inconvenience caused and thank you for your understanding.

Update 08:50 a.m. UTC: The limited service disruption has begun.

Update 09:20 a.m. UTC: The service disruption has been resolved and the stack is now fully operational. 

Thank you for your patience.

Limited service disruption for AWS EU

A limited service disruption on AWS EU stack will start at 07:00 a.m. UTC today, as announced earlier. Storage jobs processing will stop and new jobs will be delayed until the upgrade is completed. All running jobs will be cancelled, but will resume after the upgrade.

All APIs and other unaffected services, such as Workspaces and Jobs, will remain operational, though their operations may be delayed due to the Storage job delays. We will provide an update when the service disruption starts and ends. 

We apologize for any inconvenience caused and thank you for your understanding.

Update 6:55 a.m. UTC: The limited service disruption has begun.

Update 07:45 a.m. UTC: The service disruption has been resolved and the stack is now fully operational. 

Thank you for your patience.

Python workspace can't be created from transformation

2023-04-13 07:40 UTC We are investigating failing workspace creation on EU stack (connection.eu-central-1.keboola.com). The issue is manifesting as Loading data to workspace failed: Client error:... when you try to create a workspace from python transformation. More information within the hour.

2023-04-13 08:40 UTC We are still investigating root cause. This issue happens only when creating new workspace from python transformation with empty input mapping on connection.eu-central-1.keboola.com. More information within the hour.

2023-04-13 09:15 UTC The service disruption has been resolved and the stack is now fully operational.

We are very sorry for the inconvenience.

Queue v1 table graph shows error

2023-04-12 09:50 UTC Table dependency graph shows error message on projects with queue v1.  More information within the hour.

Update 2023-04-12 10:43 UTC We have deployed the latest functional version, the problem should be solved by now. 

We apologize for the inconvenience.

Workspace creation failing (all stacks)

2023-04-06 12:45 UTC We are investigating failing workspace creation on all stacks. The issue is manifesting as na Application error when you try to create a workspace. The fix is already on the way, we expect the operations to resume in 20 minutes.

2023-04-06 13:05 UTC The service disruption has been resolved and the stack is now fully operational.


We're sorry for this inconvenience. 

Workspace table load fails (all stacks)

2023-03-31 09:50 We are investigating failing workspace (Python, R, SQL) loads on all stacks.

2023-03-31 09:58 Affected are all newly created user workspaces (Python, R, SQL,.. ).  A fix will be available soon. The next update will be provided in 30 minutes or as soon as new information becomes available.

2023-03-31 10:24 Problem occurred on when new table was added into workspace. This issue was resolved, we are now working to fix already corrupted workspaces. Workaround now is to remove tables from input mapping and add them again. The next update will be provided in 60 minutes or as soon as new information becomes available.

2023-03-31 11:00 We fixed remaining workspaces and preparing fix to prevent this problem in the future. If you encounter this issue please contact our support and mention this status post. 

We sincerely apologize for any inconvenience caused and appreciate your understanding.

Job start-up delays in Azure North Europe

2023-03-30 16:22 UTC - We are investigating the delays in job start-up within the https://connection.north-europe.azure.keboola.com stack. The next update will be provided in 30 minutes or as soon as new information becomes available.

2023-03-30 16:54 UTC - The investigation into the cause of the issue is still ongoing. The next update will be provided in 30 minutes or as soon as new information becomes available.

2023-03-30 17:56 UTC - The investigation into the cause of the issue is still ongoing. The next update will be provided in 30 minutes or as soon as new information becomes available.

2023-03-30 18:55 UTC - We have identified and fixed the root cause of the issue. The job backlog has now been cleared. We will continue to monitor the situation to ensure that everything remains stable.

2023-03-30 19:18 UTC - The service disruption has been resolved and the stack is now fully operational. 

Thank you for your patience.

Failing Facebook/instagram components on Azure North Europe stack

2023-03-14 14:15 UTC - Since Sunday, we have been experiencing component failures when communicating with the Facebook Graph API on our Azure North Europe stack https://connection.north-europe.azure.keboola.com

Following components failing with application error:

keboola.ex-facebook-ads
keboola.ex-facebook
keboola.ex-instagram

We believe that issue is related to following reported bug in Facebook API https://developers.facebook.com/support/bugs/737701844772490

We are monitoring situation.

2023-03-20 08:00 UTC -  We have not received any update from Meta, last error occurred more than 72 hours ago, we will monitor situation. For now the situation looks stable and we are considering issue as resolved.