8.10 Release notes
Release notes for new features included in the 8.10 minor release, including alpha feature releases.
| Minor release date | Scheduled end of maintenance | Changelog(s) | Upgrade guides |
|---|---|---|---|
| 13 October 2026 | 11 April 2028 | Patch Releases and Changelogs | 8.10 upgrade guides |
- See What's new in Camunda 8.10 for important changes to consider when planning your upgrade from Camunda 8.8.
- See release announcements to learn more about supported environment changes, breaking changes, and deprecations.
- Refer to the quality board for an overview of known bugs by component and severity.
Technical Changelogs for all 8.10.x releases
Overview of all patch releases and their Changelogs in GitHub
8.10.0-alpha1
| Release date | Changelog(s) | Blog |
|---|---|---|
| 13 May 2026 | - |
Agentic orchestration
AI Agent connector: Conversation storage SPI redesign
The conversation storage SPI used by custom AI Agent storage backends has been redesigned. Built-in stores are migrated transparently; custom ConversationStore implementations must be updated.
See the release announcement for more details.
Camunda-provided LLM for SaaS
You can now run any AI Agent on Camunda 8 SaaS in minutes using the Camunda-provided LLM, without wiring your own LLM credentials. Whether you start from a Camunda-provided agentic blueprint or build your own agent from scratch, the required credentials are populated automatically as cluster secrets, so there is little to no extra setup needed to get started.
The included budget is sufficient for hundreds or thousands of agent runs even on a trial account, depending on the model used. For enterprise organizations, AI features must be enabled first; after that, Camunda-provided LLM is enabled automatically.
This dramatically reduces time-to-first-running-agent by removing the need for external LLM infrastructure or credential setup on day one.
MCP start event element template
The MCP start event element template is now available in Web Modeler and Desktop Modeler. Apply it to a BPMN message start event to configure the process as an MCP tool with name, purpose, inputs, and usage guidance for LLMs.
See MCP start event for the full property reference.
Processes MCP Server
Camunda 8.10 introduces the Processes MCP Server, which enables AI agents to discover and call your deployed BPMN processes as Model Context Protocol (MCP) tools.
Deploy a process with an MCP start event and it is automatically registered as a callable tool. MCP clients connect to the /mcp/processes endpoint and can invoke any registered process, with the Orchestration Cluster starting a new process instance and returning the process instance key immediately.
The server also exposes static tools for inspecting running process instances, so agents can check variables, state, and incidents without switching servers.
Standalone evaluation assertions for judge and semantic similarity
Camunda Process Test now exposes judge-based evaluation and semantic similarity evaluation as standalone AssertJ assertions for arbitrary string values, without requiring process-variable assertions. Semantic similarity checks support configurable embedding models and thresholds, and both assertion types reuse the existing CamundaAssert configuration with optional local overrides.
Camunda Hub
Usage & billing metrics for 2025 enterprise license model
Camunda Hub and Accounts now support the 2025 enterprise license model.
- A new
licensing_modelattribute onOrganizationMetaDataidentifies if an enterprise organization is using the 2025 or legacy license model. If unset, it is treated as legacy. - If you are an organization with
licensing_model = 2025, your Usage and Billing views only show Process Instance (PI) metrics. Decision Instance (DI) and Unique Task User (TU) information is no longer shown. Legacy organizations continue to see the existing metric set. - For enterprise (
salesplantype = enterprise) organizations, the licensing model is shown in the organization details. Admins can edit this by selecting either legacy or 2025 via a modal action. - The enterprise onboarding wizard now includes a license selection step (defaults to 2025). The
ExternalOnboardingRouteraccepts an optional licensing model parameter (defaulting to 2025 if not provided).
Cluster version selection for SaaS orchestration clusters
You can now create new SaaS Orchestration Clusters on specific supported Camunda 8 minor and patch versions, including:
- The latest recommended versions (latest patch of each active minor)
- Other still-supported versions that you already run on existing clusters in the same organization.
Intelligent document processing (IDP)
Support for ABBYY as an IDP Provider
Camunda IDP now supports ABBYY as a document extraction provider.
Modeler
Support for configurable headers for execution listeners
Execution listeners now support configurable headers, aligned with service task job headers.
- In BPMN, execution listeners can define
<zeebe:taskHeaders>. The headers are passed to the listener’s job worker alongside any base-element headers, with listener headers overriding on key conflicts. - In Modeler, you can configure execution listener headers visually (name/value pairs) without editing BPMN XML.
- Listener workers can consume these headers as metadata and configuration parameters using the same patterns as service task job workers.
Integrations
Microsoft Teams routing and permission-aware task actions
Camunda for Microsoft Teams now supports routing incident and task collaboration to private channels, shared channels, and group chats. Notifications and task actions in Teams now align with Camunda assignment and access rules, ensuring that only eligible users are notified and allowed to act.
Operate
JSON display in Operate
Camunda 8.10 introduces an update to the JSON display functionality in Operate (SaaS).
You can now:
- Open JSON variables in a dedicated JSON viewer directly from the variables panel, without entering editing mode.
- View JSON values with consistent, easier to understand formatting.
- Copy full JSON variable values to the clipboard.
- Use the improved in-line variables display.
This change helps navigate more complex data during operations and troubleshooting.
Orchestration Cluster
Cancel execution listener
Execution listeners now support a cancel event type on the process element. Cancel listeners run when a process instance is terminated — useful for cleanup, audit logging, or notifying external systems.
For details, see cancel listeners.
Self-Managed
Host network support for orchestration cluster pods
The 8.10 Helm chart adds orchestration.hostNetwork (default: false), which lets orchestration cluster pods share the host node's network namespace. This is useful in bare-metal or restricted network environments where pods must be reachable directly via the node IP rather than a cluster overlay network.
When orchestration.hostNetwork is set to true and orchestration.dnsPolicy is not set, the chart automatically uses dnsPolicy: ClusterFirstWithHostNet to preserve in-cluster DNS resolution. You can override this by setting orchestration.dnsPolicy explicitly.
orchestration:
hostNetwork: true
For details, see configure pod networking.