We have added new outbound IPs for connection.north-europe.azure.keboola.com stack.
Please make sure you have whitelisted all these IP addresses in your firewalls to allow Keboola Connection to successfully connect to your system:
For your convenience, you can process programmatically fetch and process the list of existing IP addresses in JSON format.
Read more about outbound IP addresses in documentation.
On 07 Oct 2021 we experienced failing Google Drive extractor jobs run between 12:22 UTC and 12:49 UTC in all regions. The issue is now resolved.
04 Oct 2021 07:27 UTC - We are investigating increased backlog of jobs in connection.eu-central-1.keboola.com stack. Next update in 60 minutes or as new information becomes available.
04 Oct 2021 07:45 UTC - We have temporarily boosted the Snowflake capacity and backlog is cleared. All operations are back to normal and everything is fully working.
2021-09-29 08:11 UTC - We are investigating higher error rate and increased latencies in https://connection.north-europe.azure.keboola.com stack. Next update when new information will be available or in hour.
2021-09-29 09:15 UTC - The error rate has dropped, but we are still investigating higher latencies in internal requests. Next update when new information will be available or in hour.
2021-09-29 10:12 UTC - We are still investigating higher latencies in internal requests. Next update when new information will be available or in hour.
2021-09-29 12:00 UTC - We have identified one of 3rd party services to be the possible root cause of this issue and we are working with support team of this service to fix it.
2021-09-29 13:15 UTC - Still working with 3rd party service support on a solution. Next update when new information will be available or in hour.
2021-09-29 14:15 UTC - Still working with 3rd party service support on a solution. Next update when new information will be available or in hour.
2021-09-29 16:15 UTC - Still working with 3rd party service support on a solution. Next update when new information will be available or tomorrow morning.
2021-09-29 19:05 UTC - Still working with 3rd party service support on a solution. Job execution times also might be longer due to this incident. Next update when new information will be available or tomorrow morning.
2021-09-29 22:01 UTC - We've applied a fix which reduced the latencies, job processing times should be back to normal. We are investigating occasional error responses and we are still working with 3rd party service support on a solution. Next update tomorrow morning.
2021-09-30 09:20 UTC - Platform is stabilized after yesterday's fix, however we still see occasional errors. We are still working with 3rd party service support on a solution. Next update when new information will be available or in four hours.
2021-09-30 17:57 UTC - We have implemented another fix which decreased the error rate. We continue to monitor the situation but unless the situation escalates we consider this incident resolved.
A maintenance of Azure EU Keboola Connection (connection.north-europe.azure.keboola.com) will take place on Saturday, Oct 9th, 2021 from 10:00 CET and should take less than two hours.
During the maintenance, you can't access your data and projects. All network connections will be terminated by "HTTP 503 - down for maintenance" status message.
Orchestrations and running component jobs should be generally delayed, but not interrupted. However, feel free to re-schedule your saturday orchestrations to avoid this maintenance window.
2021-09-21 08:27 UTC - We have noticed that emails from our platforms are being sent with empty body (email..title, email..body etc.). Next update in one hour.
2021-09-21 11:14 UTC - we successfully rolled back the previous working version.
We're sorry for this inconvenience.
2021-09-13 08:15:10 UTC: there was a release of the UI which broke the parsing of transformations into separate queries. Queries that were not edited this morning were not affected.
2021-09-13 11:48:29 UTC: We identified broken version and applied a fix
We advise all users to reload their browsers and resave any affected transformations
In order to provide a better experience and support we are taking over the maintenance of Salesforce components from the 3rd party developer. Due to this, the original Salesforce (Bulk API) extractor (htns.ex-salesforce component) is being deprecated and replaced with the new Keboola maintained Salesforce extractor.
The old extractor configuration will continue to work, however you won’t be able to create new configurations. It is highly recommended to migrate to the new extractor version. We have recently added an option to perform most of the migration process automatically.
The new extractor comes with improved functionality:
Improved dynamic UI
Incremental fetching and primary key support
Now you have a better control of how the data is loaded. In the previous version users only had option to switch the `incremental` flag which caused addition of a hardcoded primary key. This caused issues with incremental loading of objects like *History which do not have an Id column at all. Now it is possible to define the primary key manually (defaults to Id) and choose between several options:
Full Load: Overwrite all data at destination
Incremental: Upsert data in destination
Incremental with Incremental fetching: Bring in only data that have changed since previous execution. The date column used for this comparison can be specified. This allows you to use for instance CreatedDate for History objects where the LastModifiedDate is not available.
Fetch deleted records
Now it is possible to control whether to include also the deleted records
We have released a migration script that will help you migrate any existing configurations directly from the project.
Migration Behaviour:
Encrypted values (credentials) are NOT TRANSFERRED - because the component has a new ID users must set up credentials in the new configuration again manually.
Migration transfers component state so any incremental configurations will start from where they left off.
The output bucket is maintained - there is no need to change any downstream input mappings
Orchestrations are not updated - this step is left for the user so it can be done safely
Steps to migrate:
Each affected configuration will display the following message:
Click on the “PROCEED TO MIGRATION”
You’ll be displayed a list of affected configurations and orchestrations:
Click the “Migrate” button.
After successful migration you will find all new configurations in your project
Replace the credentials
Inspect configurations and test if needed.
Change affected Orchestrations manually and replace the old configuration with the new one.
2021-08-28 10:25 UTC - We have noticed increase rate of failed jobs when importing data into Storage. They are failing with user errors Some columns are missing in the csv file.
2021-08-28 10:50 UTC - We identified the problem and rolled back the previous version of our Storage.
2021-08-28 11:50 UTC - Failed jobs was related with minor Storage changes released on 2021-08-27 between 8-9 AM UTC.
Table imports started after that could finished with User Errors "Some columns are missing in the csv file." when columns names in the source file was ending with non-alphanumeric characters.
On 2021-08-17 since 7:30 UTC we are experiencing some Jupyter based workspaces failing to create or restore in all regions. We are now rolling back previous working version.
2021-08-17 9:35 UTC - we successfully rolled back the previous working version and creation/restore of Jupyter workspaces works now as expected. As a root cause we identified mishandled process when scaling up server instances, so only creation/restore that triggered instances scale up would fail. We work on the fix and will be released soon after.
