Upgrade notes (3.3 to 3.4)

Heads Up!

To upgrade Optimize to version 3.4.0 please perform the following steps: Migration & Upgrade Instructions.

Here you will find information about:

  • limitations,
  • known issues,
  • changes in the supported environments,
  • any unexpected behavior of Optimize (e.g due to a new feature)

Breaking Changes


Optimize no longer supports Elasticsearch versions 7.3.x and 7.4.x as these reached their EOL. Furthermore 7.5.0 is not supported anymore as we encountered problems related to snapshotting that got fixed with 7.5.1, the minimum Elasticsearch version required for Optimize 3.4.0 is thus 7.5.1. See the Supported Environments sections for the full range of supported versions.

Camunda Platform

Optimize now requires at least Camunda Platform 7.13.5 and 7.12.x is not supported anymore. See the Supported Environments sections for the full range of supported versions.

Cannot use camunda as a source value for ingested events

When ingesting events using the Ingestion REST API, Optimize will now reject any events that use camunda (or are case variations of) as a value of the source field. Optimize will not change this for any previously ingested events. If you do have any previously ingested events with this value that are used in reports and notice any unexpected behaviour, please contact us for assistance in migrating these events to comply with this new restriction.

Unexpected behaviour

Flow Node Status is now a filter

With this version, the Flow Node status configuration option is changed into a Flow Node data filter. Therefore, If you previously changed the Flow Node status configuration in your report, your change will appear as a Flow Node data filter instead. There are also changes to the filter behaviour, which may affect your report result. For more information please see the Flow Node status filter documentation.

Changes in requirements

Number of shards per instance index

With Optimize 3.4 come some significant changes in the Elasticsearch schema: instead of storing the instance data for all definitions in one index, Optimize now creates one instance index per process and decision definition which stores all instances of this definition. Consequently, we have updated our default shard size per instance index to 1. If you have previously changed this configuration you may want to update it accordingly.

Hardware Recommendations

Due to the above described schema change for dedicated instance indices, Optimize hardware recommendations are now more directly linked to the amount of definitions and instances in your data sets. We recommend reading the updated hardware requirements section and adjusting your setup accordingly if required.