2024-08-27 06:25 - We are investigating an issue with restoration of Python workspaces
2024-08-27 07:50 - Issue is resolved, python workspaces are now working normally.
We are apologize for the inconvenience.
2024-08-27 06:25 - We are investigating an issue with restoration of Python workspaces
2024-08-27 07:50 - Issue is resolved, python workspaces are now working normally.
We are apologize for the inconvenience.
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.
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.
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.
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.
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-06 We have experienced some jobs stuck to continue and failed between 02:22 - 04:45 UTC. The root cause was invalid job node, we had to shut it down to prevent further issues.
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.
At 2024-07-31 12:05 UTC we've released a new version of "keboola.processor-create-manifest" processor, which introduced a bug resulting in following error message:
Sliced file "table_name" columns specification missing.We've reverted the processor to previous version. Please re-run your configurations if you've encountered this error.
We apologize for any inconvenience.
2024-07-31 12:15 UTC We have started an investigation into the Telemetry data extractor failures, which have been occurring for the last two days.
2024-07-31 17:15 UTC The telemetry extractor has been failing in projects with the native data types feature enabled. Columns set as non-nullable have their empty string records translated as NULLs, resulting in the error NULL result in a non-nullable column. We have decided to change all non-primary key columns to be nullable to mitigate this issue. To align the table column definitions in affected projects with the data source, we need to force a full load for all telemetry tables. The forced full load will be disabled on Tuesday, August 6th.