Planned Releases
The features listed below will be released in the coming months. The information provides advance notification about new features. The dates are subject to change. However, we strive to keep the date information as accurate as possible, giving daily updates.
You can find information about released features in our Release Notes and documentation.
Tip
Use CTRL+F or Command+F to search for specific terms.
DATA INTEGRATION Changes to Celonis IP addresses: Action required after 2025-09-17
Important
These changes affect the eu-2, eu-3, jp-1, uk-1 and us-2 realms only. If you're on any other realm and/or don't use IP allowlisting for Celonis-originating traffic, these changes will not affect you and no action is required.
Ensure all your system IP allowlists contain the IPs listed in Celonis IPs as origin.
Remove the following IPs from all allowlists in your realm(s).
Realm
IPs to be removed after 2025-09-17
eu-2
13.73.158.49
13.80.109.60
168.63.109.207
eu-3
20.218.91.128
20.218.105.182
jp-1
52.243.46.143
uk-1
51.132.48.184
us-2
20.187.3.129
52.183.80.180
40.65.121.189
MACHINE LEARNING Updated user interface for the Machine Learning Workbench (2025-05-15)
The user interface for the Machine Learning Workbench (MLWB) is being updated with a cleaner and more modern look that is more aligned with the rest of the Celonis platform. This new interface does not provide any additional functionality, so it will not change how users interact with their existing workbenches, but this update will make it easier for Celonis to release new MLWB features in the future. This new interface will be applied to all existing workbenches automatically, however, users will still be able to access the previous interface by clicking the Back to the old UI link in the upper right corner. Users can then click the Go to the new UI link in the older interface to return to the updated version.
![]() |
DATA INTEGRATION Parallel data job executions replaced by smart ETL schedules (2025-05)
This release will make smart ETL scheduling the default method for executing all data jobs. Based on historical extractions, an internal algorithm automatically calculates the optimal execution order based on the dependencies and relationships across all tasks. This means once a table has been extracted, the related transformations are then automatically started (while unrelated tables are being extracted). Previously, parallel data job executions performed this function, however they didn't take into account dependencies between the data jobs.
All data jobs will be automatically moved to smart scheduling and will continue to execute as scheduled. This means that there are no alterations or updates needed for your existing data job execution schedules.
For more information about extracting and transforming your data, see: Extracting and transforming data.