Skip to main content

Upcoming Changes

This section lists planned feature releases as well as advance notices about updates that may impact existing functionality.

We recommend checking here regularly to stay ahead of any changes that could affect your setup.

Planned Releases

The features listed below are planned for release in the coming months. This information is provided to give you an early look at what’s coming. Release timelines may change, but we aim to keep them as accurate and up to date as possible, with regular updates.

November 10 2025

IMPROVED DATA INTEGRATION Change to data retention policy when monitoring your pipeline

Our data pipeline monitoring is changing to a one-year maximum data retention policy. Any stored data older than 365 days will be automatically deleted at the end of each active monitoring day. This update is to ensure consistent and optimal performance of the monitoring app, improving your monitoring experience more efficient.

By enabling custom monitoring, you can collect monitoring data in a dedicated data pool. This dedicated monitoring data pool allows you to leverage Studio views to monitor your data pipelines.

For a video overview of how you can set up custom monitoring for your data pipeline:

 

And to learn more, see: Setting up custom monitoring.

November 2025

IMPROVED PROCESS DESIGNER Canvas app updates

Exact release date still to be confirmed

We're aiming for this to be released in November and will confirm the exact release date soon.

We're continuing to add more functionalities to the Canvas app. This update includes:

  • Navigation for subprocesses or interfaces.

    canvas.png

  • Multi-select, allowing for bulk edits or mass deletion.

    canvas2.png

  • Improved SVG export, allowing for clearer text.

    canvas3.png

For more information, see Enabling Canvas app.

Breaking Changes

The following updates introduce changes that may not be fully compatible with previous versions.

We’re providing this information ahead of time to help you prepare and make any necessary adjustments before the updates roll out.

December 31, 2025

BREAKING ADMIN Decommissioning API and application keys: Action required before December 31, 2025

Important

These changes affect users who currently use API keys and/or application keys for the Audit Log, Platform Adoption and Team Login History APIs.

If you don’t use APIs or application keys in your applications or in third-party systems for these APIs, these changes will not affect you and no action is required.

Why we’re making these changes

We’re moving away from using API and application keys to the OAuth 2.0 authorization standard to provide a more secure, streamlined and efficient developer journey.

Users currently generate long-term API keys or application keys in the Celonis Platform. These keys are then embedded in applications and allow data to be requested or pushed using Celonis APIs. As these keys typically have a long life, cannot be rotated and their scope cannot be limited, any application with an embedded API or application key can access almost all Celonis APIs.

With OAuth 2.0, scoping means OAuth-enabled clients can access permitted APIs only. This follows the security principle of least privilege so an OAuth client only has the privileges required to perform a certain task.

Action required before December 31, 2025

  1. Identify any systems and/or applications that use API or application keys to call any of the following APIs:

    • Audit Log API.

    • Platform Adoption API.

    • Team Login History API.

  2. Migrate these systems and/or applications to OAuth 2.0.

For information on enabling OAuth 2.0 on the Celonis Platform, see Using an OAuth 2.0 token in Celonis.

Note

In future, we're aiming to move to OAuth 2.0 for all Celonis use cases. If you're using other Celonis APIs that already support OAuth 2.0, you can move to OAuth 2.0 for these APIs too. We’re also adding OAth 2.0 support for Action Flows and on-premise clients and will let you know when this is available

December 31, 2026

BREAKING DATA INTEGRATION Deprecating SAP on-prem extractor: Action required before December 31, 2026

Celonis is fully deprecating and discontinuing support for the SAP on-premise extractor (OPE) by the end of December 2026. All data pipelines currently relying on OPE will cease to function on this date.

Important

To ensure continuity of data flow, all customers using OPE must migrate to the modern On-Premise Client (OPC) by the end of December 2026.

This change is driven by a necessary update to our authentication security model. The outdated key-based authentication mechanism used in OPE is being replaced by the industry-standard OAuth protocol in OPC. To align with modern security requirements and maintain data pipelines, the entire legacy OPE framework will be shut down by the end of 2026. Any SAP Extractor running on the OPE after this date will stop working.

We recognize that some customers rely on specific OPE features which are not yet available in the OPC. These features are currently under development and we plan to deploy them in Q4 2025. We will communicate the exact release dates for these features in our Release Notes.

The following OPE features are currently not yet fully supported by the OPC:

  • Extraction via PI/PO

  • Extraction from legacy SAP versions 4.6 and 5.0

  • Column value filter functionality

  • Calculated columns