Snowflake Transformation Component Failure

2025-07-28 14:15 UTC

We are currently experiencing issues with the Snowflake Transformation component. Jobs are failing with the following error:

"Actual statement count X did not match the desired statement count Y."

The problem began occurring at approximately 11:00 UTC.

Our engineering team is actively investigating the issue. We will share more information and updates as soon as we have them.

Thank you for your patience and understanding.


2025-07-28 15:30 UTC

We’ve identified the root cause of the issue affecting the Snowflake Transformation component.

The problem was introduced by a bug in a release deployed today at 11:00 UTC. This release has since been rolled back, and new failures should no longer occur.

However, please note that any Snowflake Transformation configurations edited during the affected window may still be impacted and require manual correction. If you made any changes to Snowflake transformations between 11:00 and 15:00 UTC, we recommend reviewing them.


Fix Instructions

To resolve the issue caused by the bug, navigate to the affected transformation configuration detail, click the "EDIT ALL QUERIES" button and make a small change (e.g., add a space at the end of one of the queries) to re-save the entire configuration.


⚠️ Please note:
This action will only fix the query formatting issue introduced by the bug. If you made additional changes to the queries in the meantime—such as attempting to fix broken queries manually—you may still need to manually review and correct individual queries. In such cases, it may be easier to roll back to the last known working configuration version instead.


Thank you for your patience while we worked to resolve this.

Storage jobs slowdown on Snowflake Multitenant stacks

We are investigating issues with slowdown of Storage jobs on Multitenant stacks. There are affected projects which are using Snowflake (Bigquery not affected). Issue was firstly noted on 10.07.2025.

The issue has impact on transformations with bigger backend size than default. 

We are preparing fix so the jobs are running as before.

Update 18:45 18.07.2025 UTC - We have released fix, which seems to be working correctly. We will continue monitoring the situation that the performance of transformations is back on track as before.

Update 07:07 19.07.2025 UTC - The root cause is fixed and the transformations on different backend size than default and performance seems to be on track as it was before.

Support Widget Unavailable on GCP Pay-As-You-Go Projects

The support widget was unavailable on GCP Pay-As-You-Go projects from July 4th to July 14th 2025. The issue has now been resolved and the support widget is available for these projects once again.

This issue only affected the support and feedback button in the bottom-right corner of the project page. Support requests made from the Projects menu were not affected.

Jobs not starting on Azure North Europe stack

We're investigating an issue with jobs not starting on Azure North Europe stack (https://connection.north-europe.azure.keboola.com/).

Update 08:45 UTC - we've identified the root cause and are working on a fix. The jobs are unblocked for now, but some delays might still occur. 

Update 10:22 UTC - The root cause has been fixed. 

Job Listing Not Updating on connection.keboola.com

We are currently investigating a delay in the job listing updates on https://connection.keboola.com/. New jobs are not appearing in the job overview, and the statuses of existing jobs are not being refreshed.

This issue does not affect job processing or scheduling. Jobs are still running as expected.

We will provide the next update as soon as new information becomes available.

Update 13:15 UTC:
We have identified the root cause and resolved the issue. All jobs are now listed correctly, and their statuses are updating immediately.


Flows triggers are not possible to set trigger

We are investigating issue that flows generate new IDs which are not possible to set trigger with. It's currently affecting all stacks.

We will update this post as new information becomes available. If you have any questions or concerns, please reach out to our support team.

Update June 05 17:50 UTC We released fix which should solved the issue visually with 201 status response but still the schedule is not available in UI. We will investigate further where is the problem.

Update June 05 18:15 UTC We see things operating as usually. All flows configurations between 17:50 UTC and 18:15 UTC won't be properlly working with triggers. 

Also all flows created from ~June 03 15:00 UTC till June 05 17:50 UTC which were created with ULID identifiers remain unusable using table triggers. We will make sure that these will be able to be scheduled with tiggers subsequently. Current approach is to delete your flows with ULID identifiers and create new ones with integer identifiers.

We are sorry for this inconvenience.

Planned partial maintenance on Saturday, May 24, 2025 for all GCP stacks

The announced partial maintenance has just started. The platform has been scaled down and is no longer accepting new jobs. We expect a brief downtime in 15 minutes, around 06:00 UTC. We will update this post with the progress of the partial maintenance.

Update 06:00 UTC: The announced partial maintenance is ongoing, and we are expecting downtime to begin any minute now. We will continue to update this post as the maintenance progresses.

Update 06:11 UTC: The maintenance has been completed, and all services have been scaled back up. The platform is fully operational, and jobs are now being processed as usual. All delayed jobs will be processed shortly. Thank you for your patience.

Failing jobs of Legacy transformations

We are currently experiencing job failures related to the keboola.legacy-transformation component.

Our team is actively working on reverting to the previous stable release to resolve the issue.

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

Update 10:56 UTC: The issue has been fixed by reverting to previous release.


UI Rendering Issue in Transformations (fixed)

We’ve identified an issue in the Keboola UI where the list of tables in the transformation may render incorrectly after a table has been deleted from the list. This can result in visually corrupted table rows (e.g., mixed or misaligned entries).

This is a UI-only issue — data processing is not affected. Reloading the page restores the table view correctly.

We’ve successfully reproduced the problem and are working on a fix.

Update 13:50 UTC: the issue has been fixed.