Issues across all Azure stacks

We're investigating issues across all Azure stacks. Next update in 15 minutes or when new information is available.

UPDATE 14:35 CEST: The issue seems to be resolved, we're still evaluating the impact. Next update in 30 minutes or when new information is available.

UPDATE 14:55 CEST: The outage was caused by routine maintenace of databases in Auzure. All running jobs affected during this outage should restart automatically. Some of the affected Storage jobs may be executed twice and in very rare cases when using incremental load without a primary key this could lead to data duplication.

We're sorry for this inconvenience, we will be taking measures to decrease impact of future maintenance events. 

For any additional questions, please contact support.

New and improved Jobs API endpoint

We've introduced a new and improved Jobs API endpoint, /search/jobs, which replaces the current /jobs endpoint. 

The new endpoint should be near drop-in replacement, supporting the same parameters and the same results, but with improved performance, especially for larger projects and complex filters. 

The old endpoint is now considered deprecated and will be removed some time in the future (will be announced separately).  

A major difference is that the new endpoint returns results from a secondary database, which is synchronized with a slight delay. 

This means a new job may not be shown right away after it's created and job detail may contain slightly outdated data if it was updated recently. The delay should be couple seconds at max during normal operation. 

Other difference is the new endpoint will return maximum 500 items per page.

See the Job Queue API documentation for more details.

Sync actions on Azure stacks are failing

2024-08-19 08:05 - We are investigating an issue with synchronous action on connection.north-europe.azure.keboola.com stack

2024-08-19 08:30 - We are still investigating the issue, problem is on all Azure instances.

2024-08-19 09:00 - Issue is resolved, synchronous actions are operational on all azure stacks.

Unable to view the project consumption on AWS US stack

2024-08-13 11:02 UTC - We are experiencing a problem with the project consumption dashboard. Displaying the detail page ends with an error and the dashboard is not available. 

2024-08-13 11:32 UTC - Unfortunately, the problem still persists, and we have not been able to find the root cause. We are still actively solving the problem.

2024-08-13 11:51 UTC - The problem has been fixed and the consumption dashboard is available again. 

We are apologize for the inconvenience.

Stuck jobs in AWS EU stack

2024-08-13 09:06 UTC - We are investigating an issue where jobs are delayed, the problem has so far only affected the AWS EU stack https://connection.eu-central-1.keboola.com. 

2024-08-13 09:35 UTC - The problem still persists, we have not yet been able to determine the cause of the problem.

2024-08-13 09:48 UTC - We have managed to discover and fix the problem, the scheduled jobs are currently delayed, we are now stabilizing the problem and will give next update when the stack is stable.

2024-08-13 10:00 UTC - The problem is solved completely and the stack is fully stable. We are sorry for the inconvenience.

Issue with Restoring Typed Tables Using Time Travel

2024-08-09 12:05 UTC - We are currently investigating an issue affecting the "Restore Table Using Time Travel" feature in Snowflake projects with Typed Tables. When attempting to restore a table, it is created successfully but cannot be exported or previewed. We will provide further updates as more information becomes available.


2024-08-12 05:46 UTC - We have identified the root cause of the issue and have prepared a fix. The deployment is scheduled for today. We will provide an update once the fix has been released.

2024-08-13 13:54 UTC - The fix has been released. Now, when you create a new table using the Time Travel restore feature, it will function as expected.

Column mismatch for multiple components

2024-08-02 12:04 UTC: We're investigating an issue, where columns are getting mismatch for different components.

Next update in 1 hour.

2024-08-02 12:54 UTC: We have identified the root cause of the recent service disruption in the new manifest processor version released yesterday afternoon. We have now rolled back to the previous version to mitigate the issue.

Action Required:
If you have been impacted by this disruption, please delete any newly added columns and rerun your configuration. This should resolve the issue and allow your job to succeed.

If you continue to encounter problems, please do not hesitate to reach out to our support team for assistance.

We apologize for any inconvenience this may have caused and appreciate your understanding.