8.11 Release notes
Release notes for new features included in the 8.11 minor release, including alpha feature releases.
8.11.0-alpha1
| Release date | Changelog(s) |
|---|---|
| 10 November 2026 |
APIs & tools
Read the engine clock and add time without pinning it
Use two new Orchestration Cluster REST API endpoints to read and move the engine clock without stopping it.
| Endpoint | Description | Required permission | Java client |
|---|---|---|---|
GET /v2/clock | Returns the current time of the engine clock. If the clock is pinned, it returns the pinned time. | READ on SYSTEM | newClockGetRequest() |
POST /v2/clock/add | Moves the clock forward or backward by an ISO 8601 duration, such as PT1H or -PT1H, and returns the new time. | UPDATE on SYSTEM | newAddClockCommand().offset(Duration) |
Both endpoints return the time as an ISO 8601 date-time, for example { "timestamp": "2025-01-01T12:00:00.000Z" }.
Unlike pinning, adding time keeps the clock running from the new time, so job timeouts and retry backoffs still run out in tests. If the clock is pinned, it stays pinned and moves to the pinned time plus the offset. To remove the added time, reset the clock with POST /v2/clock/reset.
Hub
Configurable session idle timeout
Camunda now supports configurable session idle timeout for SaaS and Self-Managed.
- Administrators can set an organization-wide default idle timeout and override it per cluster and connected IdP.
- Camunda automatically ends a user's session if it goes idle beyond the configured period, measured by keyboard and mouse inactivity rather than background application traffic. You can configure your organization's idle timeout policy in Hub Console.
This addresses a known compliance gap (such as PCI DSS 4.0 Requirement 8.2.8), and gives security and compliance administrators a verifiable, enforced control to reference in an audit.
Cluster configuration
- Idle timeout: Set
camunda.security.session.max-inactive-intervalto configure the idle timeout. The default is30m(30 minutes). - Timeout based on user activity: If you set
camunda.security.session.heartbeat.enabled=true, only keyboard and mouse activity in the browser keeps a session alive. Background polling no longer keeps a session alive. The Orchestration Cluster web application, Operate, Tasklist, and Admin all send this heartbeat. - Re-login after a timeout on SaaS: Camunda sends the timeout to Auth0 as
max_age, so an expired session asks the user to log in again instead of being silently renewed.
Console (SaaS)
- Per cluster: Set the idle timeout and heartbeat in Hub cluster settings. Applies to clusters on 8.10.0-alpha5 or later.
- Organization default: Set a default idle timeout for new clusters. The default applies only when you create a cluster. Existing clusters keep their own value, which you can still edit.
Modeler
Camunda Design System in Desktop Modeler
Desktop Modeler now uses the Camunda Design System. The application UI, the BPMN, DMN, and form editors, the properties panel, and side panels such as the variables outline and task testing all use Camunda Design System components and style.
Desktop Modeler no longer ships Carbon or its previous global styles. If your plugin relies on Carbon components, classes, or styles, replace them with Camunda Design System components and tokens, or remove them.
Orchestration Cluster
Evenly distributed record indices in Elasticsearch and OpenSearch
The Elasticsearch and OpenSearch exporters now spread Zeebe records more evenly across index shards. The zeebe-record-job and zeebe-record-process-instance indices default to 5 shards, up from 3. The zeebe-record-user-task index defaults to 1 shard, down from 3. With a three-partition cluster, the records of each partition land on a separate shard instead of two partitions sharing one shard.
Only newly created dated indices use the new defaults. An existing index keeps the shard count it was created with. If you set number-of-shards, it still overrides the template defaults for all indices.