Camunda Automation Platform 7.24.0-alpha1 is released

We are pleased to announce the next alpha release of Camunda Automation Runtime 7.24. This release features the following improvements:

  • Support for Spring Boot 3.5
  • New LegacyJobRetryBehaviorEnabled process engine flag
  • External task REST API and OpenAPI extended
  • 3 bug fixes

You can Download Camunda for free or Run it with Docker.

For a complete list of all improvements, take a look at the release notes. Please also see the list of known issues.

If you want to dig in deeper, you can find the source code on GitHub.

Support for Spring Boot 3.5

This alpha release features support for Spring Boot 3.5.0.

New LegacyJobRetryBehaviorEnabled process engine flag

Starting with versions 7.22.5, 7.23.2 and 7.24.0, the process engine introduces a new configuration flag: legacyJobRetryBehaviorEnabled.

By default, when a job is created, its retry count is determined based on the camunda:failedJobRetryTimeCycle expression defined in the BPMN model.

However, setting legacyJobRetryBehaviorEnabled to true enables the legacy behavior, where the job is initially assigned a fixed number of retries (typically 3), regardless of the retry configuration, and only after the first execution of a job the retry configuration will be taken into account.

In 7.22.5+ and in 7.23.2+ the default value is true for legacyJobRetryBehaviorEnabled. For 7.24.0+ the default value is false for legacyJobRetryBehaviorEnabled .

External task REST API and OpenAPI extended

Now the External task REST API is extended with the createTime field. OpenAPI is updated as well along with the extensionProperties for the LockedExternalTaskDto.

You can find the latest OpenAPI documentation here.

This is a community contribution, thanks to rohwerj! :tada:

Share Your Thoughts with Us!

Your feedback is really important to us, so please download Camunda Automation Platform 7.24.0-alpha1, try it out, and let us know what you think about it.

You can contact us in the forum, send a tweet to @Camunda, or file a bug in our issue tracker.