---
schema_version: "1"
id: 5907f7c8afa036c39f451727299619a396d104c5b40fc165a1708ee64e6bb365
title: Mule Runtime Engine 4.11.0 Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/mule-runtime/mule-4.11.0-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/mule-runtime/mule-4.11.0-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 646e0e38961108d7dda4f78aca68a7288a9fc0e9ebab5fdb6a3e5475ee98a7c1
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# Mule Runtime Engine 4.11.0 Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Mule runtime engine (Mule) is a lightweight integration engine that runs Mule applications and
supports domains and policies.

This version of Mule provides important enhancements and fixes. Deploy all your new and existing
applications to the latest version to benefit from the improvements.

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## July 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.11.6 includes Runtime Manager agent 2.7.16. See
  [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16).

Feature Flagging Mechanism:

- Mule 4.11 incorporates new feature flags. See
  [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed
  description of each feature flag and configuration instructions.

General improvements:

- The Mule Troubleshooting plugin now includes additional diagnostic sections in the Diagnostic
  Information Analysis File (DIAF). See
  [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more
  information.

  - System Info: Reports host-level diagnostics including OS details, CPU metrics, memory, and disk
    input and output statistics.

  - JVM Agents: Lists agents attached at JVM startup via `-javaagent`, `-agentpath`, or `-agentlib`
    arguments.

  - Connectors State: Shows connector configuration states, connection pools, errors, and TLS
    details.

  - Cluster Info: Reports clustering configuration and distributed lock diagnostics.

### Fixed Issues

Patch release version: 4.11.6

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Cluster node IDs are no longer generated with negative values.</p></div></div></td><td><div><div><p>W-22294724</p></div></div></td></tr><tr><td><div><div><p>Graceful shutdown no longer times out when a global error handler runs for a flow.</p></div></div></td><td><div><div><p>W-22434375</p></div></div></td></tr><tr><td><div><div><p>Long-running internal tasks no longer use the shared <code>forkJoin</code> pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.</p></div></div></td><td><div><div><p>W-22279521</p></div></div></td></tr><tr><td><div><div><p>Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.</p></div></div></td><td><div><div><p>W-20824537</p></div></div></td></tr><tr><td><div><div><p>Shutdown validation for dynamic configurations can now be skipped by enabling the <code>mule.forcefulShutdown.dynamicConfig.disableStoppingCheck</code> system property.</p></div></div></td><td><div><div><p>W-22772644</p></div></div></td></tr><tr><td><div><div><p>Flows with a scheduler source are no longer left in an invalid state after a flow restart.</p></div></div></td><td><div><div><p>W-22918240</p></div></div></td></tr><tr><td><div><div><p>Stopping a flow no longer waits unnecessarily when no events are being processed.</p></div></div></td><td><div><div><p>W-22969411</p></div></div></td></tr><tr><td><div><div><p>Project versions defined with properties are now resolved recursively.</p></div></div></td><td><div><div><p>W-22845430</p></div></div></td></tr><tr><td><div><div><p>Extension packager validation no longer fails for operations annotated with <code>@Validator</code> that use a <code>CompletionCallback</code> operation.</p></div></div></td><td><div><div><p>W-22817376</p></div></div></td></tr><tr><td><div><div><p>Events that are dropped within a processing hook are now properly completed and terminated.</p></div></div></td><td><div><div><p>W-22470584</p></div></div></td></tr><tr><td><div><div><p>The Netty HTTP listener now rejects <code>HTTP/1.1</code> requests that have a missing or duplicate host header, in compliance with RFC 9112.</p></div></div></td><td><div><div><p>W-23052713</p></div></div></td></tr><tr><td><div><div><p>The maximum size of the dynamic <code>flow-ref</code> cache is now configurable through the <code>mule.flowRef.dynamicCacheMaxSize</code> system property, which defaults to 20.</p></div></div></td><td><div><div><p>W-22219018</p></div></div></td></tr><tr><td><div><div><p>API Gateway contract persistence can now be disabled by setting the <code>anypoint.platform.contracts_persistence_enabled</code> system property to <code>false</code>, avoiding errors when persisting large numbers of contracts.</p></div></div></td><td><div><div><p>W-22568982</p></div></div></td></tr><tr><td><div><div><p>The c3p0 library is upgraded to 0.14.1.</p></div></div></td><td><div><div><p>W-22990152</p></div></div></td></tr><tr><td><div><div><p>The Spring Framework is upgraded to 6.2.19.</p></div></div></td><td><div><div><p>W-3300013</p></div></div></td></tr><tr><td><div><div><p>The Bitronix Transaction Manager library is upgraded to 3.0.2.</p></div></div></td><td><div><div><p>W-22405007</p></div></div></td></tr><tr><td><div><div><p>The OpenTelemetry API library is upgraded to 1.62.0.</p></div></div></td><td><div><div><p>W-22806044</p></div></div></td></tr><tr><td><div><div><p>The Netty library is upgraded to 4.2.15.Final.</p></div></div></td><td><div><div><p>W-22888966</p></div></div></td></tr><tr><td><div><div><p>The Reactor Netty library is upgraded to 1.3.6.</p></div></div></td><td><div><div><p>W-22939412</p></div></div></td></tr></tbody></table>

DataWeave 2.11.5 is bundled with the Mule 4.11.6 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Scope resolution errors no longer occur when importing Java classes with self-referential array properties.</p></div></div></td><td><div><div><p>W-22914494</p></div></div></td></tr><tr><td><div><div><p><code>AvroReader</code> no longer causes memory leaks when processing Avro data in long-running flows.</p></div></div></td><td><div><div><p>W-22364385</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## June 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.11.5 includes Runtime Manager agent 2.7.15. See
  [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15).

### Fixed Issues

Patch release version: 4.11.5

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.</p></div></div></td><td><div><div><p>W-22248198</p></div></div></td></tr><tr><td><div><div><p>Fatal errors such as <code>StackOverflowError</code> are now logged instead of being consumed by internal error handling.</p></div></div></td><td><div><div><p>W-22496803</p></div></div></td></tr><tr><td><div><div><p>Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.</p></div></div></td><td><div><div><p>W-22248534</p></div></div></td></tr><tr><td><div><div><p>Race conditions in <code>outerFluxCompletionScheduler</code> no longer occur during graceful shutdown.</p></div></div></td><td><div><div><p>W-22343018</p></div></div></td></tr><tr><td><div><div><p>The ObjectStore retrieved from the Registry in <code>OAuthHandler</code> is now properly initialized and started.</p></div></div></td><td><div><div><p>W-22373641</p></div></div></td></tr><tr><td><div><div><p>SDK parameter validation errors now raise the <code>MULE:VALIDATION</code> error type instead of <code>MULE:UNKNOWN</code>.</p></div></div></td><td><div><div><p>W-22276522</p></div></div></td></tr><tr><td><div><div><p>Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.</p></div></div></td><td><div><div><p>W-22343705</p></div></div></td></tr><tr><td><div><div><p><code>ConcurrentModificationException</code> errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.</p></div></div></td><td><div><div><p>W-21193046</p></div></div></td></tr><tr><td><div><div><p>Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.</p></div></div></td><td><div><div><p>W-21666905</p></div></div></td></tr><tr><td><div><div><p>The error type in the EE Cache scope is now correctly reported as <code>MULE:RETRY_EXHAUSTED</code> instead of <code>EE:RETRY_EXHAUSTED</code> when until-successful exhausts its retries.</p></div></div></td><td><div><div><p>W-21525972</p></div></div></td></tr><tr><td><div><div><p>Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.</p></div></div></td><td><div><div><p>W-21882516</p></div></div></td></tr><tr><td><div><div><p>HTTP Server now supports Upgrade requests to h2c even when the request contains a non-empty body.</p></div></div></td><td><div><div><p>W-22506085</p></div></div></td></tr><tr><td><div><div><p>Test Connection for The HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the Host field.</p></div></div></td><td><div><div><p>W-21921687</p></div></div></td></tr><tr><td><div><div><p>The Spring Core library is upgraded to 6.2.18.</p></div></div></td><td><div><div><p>W-22169898</p></div></div></td></tr><tr><td><div><div><p>Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.</p></div></div></td><td><div><div><p>W-22623626</p></div></div></td></tr><tr><td><div><div><p><code>OutOfMemory</code> errors no longer occur when establishing SSL connections with HTTP endpoints.</p></div></div></td><td><div><div><p>W-22547971</p></div></div></td></tr></tbody></table>

DataWeave 2.11.4 is bundled with the Mule 4.11.5 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>StackOverflowError</code> errors no longer occur when computing or converting type metadata for self-referencing recursive types.</p></div></div></td><td><div><div><p>W-21712344</p></div></div></td></tr><tr><td><div><div><p>The Java bean metadata cache no longer performs unnecessary evictions when processing Java POJOs. A new per-app Java bean cache can be enabled with the <code>per_app_java_bean_cache</code> compatibility flag.</p></div></div></td><td><div><div><p>W-22417507</p></div></div></td></tr><tr><td><div><div><p>The Java module bean introspection cache no longer causes memory leaks.</p></div></div></td><td><div><div><p>W-22419118</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## May 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.11.4 includes Runtime Manager agent 2.7.13. See
  [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13).

FIPS 140-3 Compliance Support:

- You can now configure Mule runtime to operate in a FIPS 140-3-compliant environment using
  certified cryptography providers. See
  [FIPS 140-3 Compliance Support](https://docs.mulesoft.com/mule-runtime/latest/fips-140-3-compliance-support) for more
  information.

General improvements:

- The `diaf` Event Dump now includes two additional `eventContextState` values: `PENDING` and
  `WAITING_NON_BLOCKING`. See
  [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more
  information.

### Fixed Issues

Patch release version: 4.11.4

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.</p></div></div></td><td><div><div><p>W-11453332</p></div></div></td></tr><tr><td><div><div><p>Extension operations using <code>@Content</code> parameters with complex map structures no longer fail to deploy.</p></div></div></td><td><div><div><p>W-18034452</p></div></div></td></tr><tr><td><div><div><p>The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.</p></div></div></td><td><div><div><p>W-21337433</p></div></div></td></tr><tr><td><div><div><p>Netty HTTP client NTLM authentication no longer fails due to missing TCP connection affinity during the handshake.</p></div></div></td><td><div><div><p>W-21615520</p></div></div></td></tr><tr><td><div><div><p>The plexus-utils library is upgraded to 4.0.3.</p></div></div></td><td><div><div><p>W-21774430</p></div></div></td></tr><tr><td><div><div><p>The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie <code>Expires</code> attributes.</p></div></div></td><td><div><div><p>W-21860840</p></div></div></td></tr><tr><td><div><div><p>The Netty library is upgraded to 4.2.12.Final.</p></div></div></td><td><div><div><p>W-21913252</p></div></div></td></tr><tr><td><div><div><p>HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.</p></div></div></td><td><div><div><p>W-21632770</p></div></div></td></tr><tr><td><div><div><p>Netty HTTP client no longer sends an incorrect WWW-Authenticate header during the NTLM authentication handshake.</p></div></div></td><td><div><div><p>W-21762949</p></div></div></td></tr><tr><td><div><div><p>In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.</p></div></div></td><td><div><div><p>W-17714668</p></div></div></td></tr><tr><td><div><div><p>A memory leak in dynamic <code>flow-ref</code> resolution that could eventually lead to an <code>OutOfMemoryError</code> no longer occurs.</p></div></div></td><td><div><div><p>W-22013292</p></div></div></td></tr><tr><td><div><div><p>Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.</p></div></div></td><td><div><div><p>W-20880559</p></div></div></td></tr><tr><td><div><div><p>A serialization error that could occur when deserializing data after a Mule runtime upgrade no longer occurs.</p></div></div></td><td><div><div><p>W-21951097</p></div></div></td></tr><tr><td><div><div><p>API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.</p></div></div></td><td><div><div><p>W-21177224</p></div></div></td></tr><tr><td><div><div><p>The support-tools-installer is removed from the Mule runtime distribution.</p></div></div></td><td><div><div><p>W-21842339</p></div></div></td></tr></tbody></table>

DataWeave 2.11.3 is bundled with the Mule 4.11.4 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>atBeginningOfDay</code> now returns the midnight offset on DST days, instead of the input offset.</p></div></div></td><td><div><div><p>W-21614817</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## April 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.11.2 includes Runtime Manager agent 2.7.11. See
  [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11).

Feature Flagging Mechanism:

- Mule 4.11 incorporates new feature flags. See
  [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed
  description of each feature flag and configuration instructions.

### Fixed Issues

Patch release version: 4.11.3

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The c3p0 library is upgraded to 0.12.0.</p></div></div></td><td><div><div><p>W-21391116</p></div></div></td></tr><tr><td><div><div><p>The mchange-commons-java library is upgraded to 0.4.0.</p></div></div></td><td><div><div><p>W-21391115</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> errors no longer occur in the Log4j boot configuration during application shutdown when shutdown callbacks are canceled while the Log4j context factory is disposing, which previously caused failures due to concurrent execution of <code>dispose()</code> and <code>cancel()</code>.</p></div></div></td><td><div><div><p>W-20256082</p></div></div></td></tr><tr><td><div><div><p>Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.</p></div></div></td><td><div><div><p>W-20267296</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException: No Context at location</code> errors no longer occur when using operation policies with routers or scopes.</p></div></div></td><td><div><div><p>W-20791354</p></div></div></td></tr><tr><td><div><div><p>OAuth token storage now correctly uses custom <code>ObjectStores</code> (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the <code>ObjectStoreManager</code>.</p></div></div></td><td><div><div><p>W-19811593</p></div></div></td></tr><tr><td><div><div><p><code>Exception reached subscriber</code> errors no longer occur when combining interceptors and operation policies.</p></div></div></td><td><div><div><p>W-21250126</p></div></div></td></tr><tr><td><div><div><p>Scheduler jobs no longer deadlock during flow shutdown.</p></div></div></td><td><div><div><p>W-21263748</p></div></div></td></tr><tr><td><div><div><p>TLS Context can now be initialized during application deployment by using the <code>mule.enable.inline.tls.context.initialization</code> feature flag.</p></div></div></td><td><div><div><p>W-20038933</p></div></div></td></tr><tr><td><div><div><p>OpenTelemetry Direct streaming now supports FIPS-compatible keystore format.</p></div></div></td><td><div><div><p>W-20623905</p></div></div></td></tr><tr><td><div><div><p>A warning now appears when an OpenTelemetry property is incorrectly used as a deployment property.</p></div></div></td><td><div><div><p>W-21018072</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> errors no longer occur in message processor chain alerting when reporting dropped errors or events if alerting support isn’t found for the current classloader. When alerting support isn’t available, the hooks now skip the alert and log the condition instead of invoking it on a null reference.</p></div></div></td><td><div><div><p>W-20192960</p></div></div></td></tr><tr><td><div><div><p>Netty no longer attempts to send more bytes than specified in the Content-Length header.</p></div></div></td><td><div><div><p>W-21184863</p></div></div></td></tr><tr><td><div><div><p>Netty server read timeouts now consider requests being read instead of requests being processed.</p></div></div></td><td><div><div><p>W-21321115</p></div></div></td></tr><tr><td><div><div><p>Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.</p></div></div></td><td><div><div><p>W-21465366</p></div></div></td></tr><tr><td><div><div><p>Netty response timeout behavior is now consistent with Grizzly.</p></div></div></td><td><div><div><p>W-21547186</p></div></div></td></tr><tr><td><div><div><p>Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.</p></div></div></td><td><div><div><p>W-21428392</p></div></div></td></tr><tr><td><div><div><p>Netty HTTP Client now filters duplicate Content-Type headers.</p></div></div></td><td><div><div><p>W-21344116</p></div></div></td></tr><tr><td><div><div><p>The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.</p></div></div></td><td><div><div><p>W-21515340</p></div></div></td></tr><tr><td><div><div><p>HTTP Netty implementation performance is now improved.</p></div></div></td><td><div><div><p>W-20969515</p></div></div></td></tr><tr><td><div><div><p>HTTP Server no longer logs an error when a client closes an idle keep-alive connection.</p></div></div></td><td><div><div><p>W-21431822</p></div></div></td></tr></tbody></table>

DataWeave 2.11.2 is bundled with the Mule 4.11.3 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.</p></div></div></td><td><div><div><p>W-21415439</p></div></div></td></tr><tr><td><div><div><p>The Jakarta Mail library is upgraded to 2.1.5.</p></div></div></td><td><div><div><p>W-21320250</p></div></div></td></tr><tr><td><div><div><p>The range operator now returns null for invalid ranges.</p></div></div></td><td><div><div><p>W-21781423</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## March 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.11.2 includes Runtime Manager agent 2.7.10. See
  [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10).

Feature Flagging Mechanism:

- Mule 4.11 incorporates new feature flags. See
  [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed
  description of each feature flag and configuration instructions.

### Fixed Issues

Patch release version: 4.11.2

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When the <code>mule.forcefulShutdown.dynamicConfig.disableStoppingCheck</code> system property is enabled, the dynamic configuration check is disabled during graceful shutdown.</p></div></div></td><td><div><div><p>W-20890587</p></div></div></td></tr><tr><td><div><div><p>When the <code>mule.forcefulShutdown.raiseCancelledError</code> feature flag is enabled, Mule runtime now raises a <code>MULE:CANCELLED</code> error instead of a <code>MULE:UNKNOWN</code> error if it attempts to create a dynamic configuration during shutdown.</p></div></div></td><td><div><div><p>W-20890613</p></div></div></td></tr><tr><td><div><div><p>Extensions no longer export <code>mule-sdk-api</code> and <code>jakarta</code> dependencies in the <code>mule-artifact.json</code> file.</p></div></div></td><td><div><div><p>W-21001749</p></div></div></td></tr><tr><td><div><div><p>Client certificates (optional) are no longer requested when no trust store is configured.</p></div></div></td><td><div><div><p>W-21220031</p></div></div></td></tr><tr><td><div><div><p>Public flows now stop concurrently during graceful shutdown.</p></div></div></td><td><div><div><p>W-21228085</p></div></div></td></tr><tr><td><div><div><p>Deadlocks no longer occur during log reconfiguration when policies are applied.</p></div></div></td><td><div><div><p>W-21231834</p></div></div></td></tr><tr><td><div><div><p>When the <code>mule.enableLogEventDumpOnShutdown</code> system property is enabled, the event dump is now logged during application shutdown.</p></div></div></td><td><div><div><p>W-21232374</p></div></div></td></tr><tr><td><div><div><p>XSD validations are now enabled by default during deployment.</p></div></div></td><td><div><div><p>W-21139633</p></div></div></td></tr><tr><td><div><div><p>Errors that are not <code>MessagingException</code> errors are no longer silenced.</p></div></div></td><td><div><div><p>W-21043969</p></div></div></td></tr><tr><td><div><div><p>The reactor.netty.version library is upgraded to 1.3.2.</p></div></div></td><td><div><div><p>W-3300013</p></div></div></td></tr><tr><td><div><div><p>When the <code>mule.propagate.objectStore.customization.to.policies</code> feature flag is enabled, policies now respect their configured TTL when using Object Store v2.</p></div></div></td><td><div><div><p>W-21215761</p></div></div></td></tr><tr><td><div><div><p>The <code>"java.lang.IllegalStateException: The client must be started before use."</code> error no longer occurs when requesting an OAuth access token.</p></div></div></td><td><div><div><p>W-17689958</p></div></div></td></tr><tr><td><div><div><p>The <code>"API is blocked (unavailable)"</code> log message no longer appears during policy updates without a corresponding unblocked message.</p></div></div></td><td><div><div><p>W-20633888</p></div></div></td></tr><tr><td><div><div><p>APIkit flows that use non-default names and are mapped through the <code>flow-mapping</code> parameter on <code>apikit:config</code> are now correctly counted as public flows instead of being treated as private.</p></div></div></td><td><div><div><p>W-18668900</p></div></div></td></tr></tbody></table>

DataWeave 2.11.1 is bundled with the Mule 4.11.2 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Array range selector operator no longer experiences performance degradation.</p></div></div></td><td><div><div><p>W-20220578</p></div></div></td></tr><tr><td><div><div><p>Concurrent access to <code>KeyValuePairs</code> inside lazy materialized objects no longer causes unexpected behavior.</p></div></div></td><td><div><div><p>W-21045501</p></div></div></td></tr><tr><td><div><div><p>The Mapping Editor API now supports attributes in Anypoint Code Builder.</p></div></div></td><td><div><div><p>W-20662336</p></div></div></td></tr><tr><td><div><div><p>Updating the expression model in the Mapping Editor API now works correctly.</p></div></div></td><td><div><div><p>W-20611263</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## February 2026

### Patch 4.11.1

- This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990.

## February 4, 2026

### Patch 4.11.0

### What’s New

The 4.11.0 version of Mule runtime introduces these enhancements:

Batch Errors Handling:

- Mule 4.11 introduces a new way to handle batch errors. Batch processing now captures record-level
  failures as `BatchError` objects that provide structured access to error details through
  DataWeave. To access `BatchError` fields, your application must use `minMuleVersion` 4.10 or
  later, or you must set the `com.mulesoft.dw.java.enabled_class_definition_lookup=true` system
  property. See [Batch Errors](https://docs.mulesoft.com/mule-runtime/latest/batch-error-concept) for more information.

OpenTelemetry Direct Telemetry Stream:

- You can now export OpenTelemetry traces and logs directly from Mule runtime to a customer-managed
  OpenTelemetry collector by using the Direct Telemetry Stream. This feature enables standards-based
  observability outside Anypoint Monitoring, supports log and trace correlation, configurable
  sampling and backpressure strategies, and secure transmission with mTLS. See
  [OpenTelemetry Support in Mule Runtime](https://docs.mulesoft.com/mule-runtime/latest/otel-support) for more
  information.

Feature Flagging Mechanism:

- Mule 4.11 incorporates new feature flags. See
  [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed
  description of each feature flag and configuration instructions.

Runtime Manager agent:

- This release of Mule runtime 4.11.0 includes Runtime Manager agent 2.7.9. See
  [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9).

General improvements:

- Mule 4.11 upgrades the subset of libraries from included third-party software. See
  [Third-Party Software in Mule](https://docs.mulesoft.com/mule-runtime/latest/third-party-software-in-mule) for a
  detailed description.

- You can now view the OpenTelemetry export queue full alert in the `diaf` file. See
  [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more
  information.

- Mule runtime now uses NETTY as the default HTTP service implementation. To use the legacy GRIZZLY
  implementation, set the `mule.http.service.implementation` system property to `GRIZZLY`. See
  [Before you begin (HTTP/2 Support)](https://docs.mulesoft.com/http-connector/latest/http-2-support#before-you-begin)
  for requirements and configuration details for enabling HTTP/2 with NETTY.

## DataWeave Features

The 2.11.0 version of DataWeave introduces these new features and enhancements:

Streaming and Memory Efficiency:

- The [dw::core::Binaries::fromBase64](https://docs.mulesoft.com/dataweave/latest/dw-binaries-functions-frombase64) and
  [dw::core::Binaries::toBase64](https://docs.mulesoft.com/dataweave/latest/dw-binaries-functions-tobase64) functions
  now process input data in chunks instead of loading the entire String or Binary into memory. This
  improves scalability and helps prevent out-of-memory errors when working with large payloads.

Lazy Variable Materialization:

- [Variables](https://docs.mulesoft.com/dataweave/latest/dataweave-variables) are now materialized independently and
  only when needed. This reduces unnecessary memory usage and improves performance, especially in
  complex transformations with multiple variables.

Enhanced try Function Behavior:

- The [try](https://docs.mulesoft.com/dataweave/latest/dw-runtime-functions-try) function now performs eager
  materialization of its execution scope. This ensures that all expressions inside the try block are
  executed and that any errors are properly caught during execution.

General improvements:

- DataWeave libraries are now precompiled during service startup, reducing warm-up time and
  improving first-execution performance.

- Memory usage during DataWeave parsing and compilation is now optimized, resulting in a smaller
  overall memory footprint for applications using DataWeave.

- DataWeave incorporates new system properties. See
  [DataWeave System Properties](https://docs.mulesoft.com/dataweave/latest/dataweave-system-properties).

### Fixed Issues

The release addresses these Mule issues and incorporates all patch updates from the 4.10.0 Mule
release through January 2026:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>HTTP/2 connections now correctly multiplex when processing concurrent requests, reducing connection creation and latency.</p></div></div></td><td><div><div><p>W-19860076</p></div></div></td></tr><tr><td><div><div><p>The runtime now leverages the AST file for applications with the until-successful component instead of parsing configuration XML files.</p></div></div></td><td><div><div><p>W-20283146</p></div></div></td></tr><tr><td><div><div><p>Batch record deserialization no longer fails when a Netty exception occurs.</p></div></div></td><td><div><div><p>W-20552358</p></div></div></td></tr><tr><td><div><div><p>Inbound HTTP/2 header validation is now improved.</p></div></div></td><td><div><div><p>W-19873453</p></div></div></td></tr><tr><td><div><div><p>The org.apache.logging.log4j:log4j-core dependency is upgraded to 2.25.3.</p></div></div></td><td><div><div><p>W-20679050</p></div></div></td></tr></tbody></table>

DataWeave 2.11.0 is bundled with the Mule 4.11.0 release. This release addresses these DataWeave
issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>AST scope navigation now works correctly for cross-file references when using the Tooling API.</p></div></div></td><td><div><div><p>W-20212809</p></div></div></td></tr><tr><td><div><div><p>A specific overload for <code>isEmpty</code> on binaries is now available to prevent implicit coercion to other types.</p></div></div></td><td><div><div><p>W-20049958</p></div></div></td></tr><tr><td><div><div><p>Materialized Java values are now cached to allow multiple executions using the same value.</p></div></div></td><td><div><div><p>W-20091279</p></div></div></td></tr><tr><td><div><div><p>Semantic tokens are now supported in the Tooling API.</p></div></div></td><td><div><div><p>W-19846990</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> no longer occurs when handling annotation types.</p></div></div></td><td><div><div><p>W-19853000</p></div></div></td></tr><tr><td><div><div><p><code>LogLevel</code> documentation is now included directly in the code.</p></div></div></td><td><div><div><p>W-17800393</p></div></div></td></tr><tr><td><div><div><p>The commons-beanutils library is upgraded.</p></div></div></td><td><div><div><p>W-3300013</p></div></div></td></tr><tr><td><div><div><p>Base64 encoding and decoding now support payloads larger than memory.</p></div></div></td><td><div><div><p>W-18575719</p></div></div></td></tr><tr><td><div><div><p>Eager materialization is now supported on values, enabling caching of all exceptions inside the <code>try</code> function.</p></div></div></td><td><div><div><p>W-19717874</p></div></div></td></tr><tr><td><div><div><p>Avro <code>enum</code>, <code>map</code>, <code>union</code>, and <code>fixed</code> types are now supported as top-level elements.</p></div></div></td><td><div><div><p>W-19596039</p></div></div></td></tr><tr><td><div><div><p><code>WeaveCompiler</code> now allows precompiling mappings and modules without validation or type checking.</p></div></div></td><td><div><div><p>W-19667273</p></div></div></td></tr><tr><td><div><div><p>Type check errors are now correctly reported when resolving type checking on subgraphs.</p></div></div></td><td><div><div><p>W-19564697</p></div></div></td></tr><tr><td><div><div><p>Lazy loading of source files is now enabled during binary compilation, avoiding unnecessary memory usage.</p></div></div></td><td><div><div><p>W-19594703</p></div></div></td></tr><tr><td><div><div><p>Type inference now works correctly when using the <code>--</code> operator to subtract a key from an object.</p></div></div></td><td><div><div><p>W-19595907</p></div></div></td></tr><tr><td><div><div><p>Warning and error messages now propagate correctly between compilation phases.</p></div></div></td><td><div><div><p>W-19386849</p></div></div></td></tr><tr><td><div><div><p>Base types are now used to validate accepted values, preventing premature materialization.</p></div></div></td><td><div><div><p>W-18943395</p></div></div></td></tr><tr><td><div><div><p>Optional types now propagate correctly through chains of value selectors.</p></div></div></td><td><div><div><p>W-19272070</p></div></div></td></tr><tr><td><div><div><p>The syntax version is now added to <code>TypeGraph</code> and <code>WeaveTypeResolution</code>.</p></div></div></td><td><div><div><p>W-19271992</p></div></div></td></tr><tr><td><div><div><p>The classloader resource resolver now resolves paths correctly on Windows systems.</p></div></div></td><td><div><div><p>W-19407283</p></div></div></td></tr></tbody></table>

## Bundled Components

- DataWeave version 2.11.0

- Runtime Manager Agent plugin version 2.7.9

### Upgrade

If you’re upgrading to this version of Mule from an earlier Mule 4.x version, see
[Mule Upgrades and Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/mule-esb#mule-upgrades).

To ensure optimal performance with this version of Mule and avoid unexpected issues, update these
modules and extensions to their latest version at the time of this release:

<table><colgroup><col> <col></colgroup><thead><tr><th>Module or Extension</th><th>Version</th></tr></thead><tbody><tr><td><p>APIkit for Mule 4</p></td><td><p>1.11.10</p></td></tr><tr><td><p>APIkit for OData</p></td><td><p>2.3.4</p></td></tr><tr><td><p>APIkit for OData 4</p></td><td><p>1.5.4</p></td></tr><tr><td><p>APIkit for SOAP</p></td><td><p>1.6.7</p></td></tr><tr><td><p>APIkit for GraphQL</p></td><td><p>1.1.1</p></td></tr><tr><td><p>Spring module</p></td><td><p>2.1.1</p></td></tr><tr><td><p>MUnit plugin</p></td><td><p>3.6.3</p></td></tr></tbody></table>

## Considerations for Mule Extension Developers

When you build a Mule extension, if you update the version of your parent `pom.xml` file to 1.4.0 or
later, ensure that the dependencies in your `pom.xml` file don’t override dependencies in the parent
`pom.xml` file. Declare only the dependencies you need. If you declare a dependency that’s already
in the parent `pom.xml` file, don’t specify a version, so that it uses the version from the parent
`pom.xml` file.

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [MuleSoft Services](https://www.mulesoft.com/support-and-services)

- [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/4.11/mule-troubleshooting-plugin)

- [Known Issues](https://help.salesforce.com/s/issues)