# mulesoft Release Notes - Full Documentation # \= APIkit for OData 2.0.2 Release Notes February 22, 2019 ## [](#compatibility)Compatibility - Mule 4.1.x+ - APIkit M4-1.2.x+ - Anypoint Studio 7.3.x+ ## [](#fixed-in-this-release)Fixed in this Release - Fixed 500 error caused by Header Accept:'Application/xml'. - Fixed Metadata URI. - Fixed error that caused to recieve an "application/xml" type while expecting an "application/atom+xml" when format is atom. - RAML `union` type is now supported. ## [](#links-to-legacy-odata-documentation)Links to Legacy OData Documentation - [OData Extension Studio Plugin 1.0.1 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-release-notes-101) - [OData Extension Studio Plugin 1.0.0 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-studio-plugin-release-notes) # A2A Agent Card The A2A Agent Card policy rewrites the Agent Card URL to match the public URL of the gateway. For configuration details, see [A2A Agent Card Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-agent-card). ## [](#june-11-2026)June 11, 2026 ### What’s New - A2A Agent Card policy implementation version 1.1.2 is now supported by Omni Gateway. - A2A Agent Card policy definition version 1.0.3 is now supported by Omni Gateway. # A2A Connector Release Notes Anypoint Connector for Agent2Agent (A2A) (A2A Connector) facilitates inter-agent communication for Large Language Model (LLM) agents and other applications by implementing the A2A protocol. This enables agents to interact and delegate specialized tasks to other agents. Guide: [A2A Connector User Guide](https://docs.mulesoft.com/a2a-connector/latest/) ## [](#2-0-0)2.0.0 **August 3, 2026** ### [](#whats-new)What’s New A2A Connector 2.0 uplifts the connector from A2A protocol 0.3.0 to A2A protocol 1.0.0. This is a breaking change: wire method names, transport configuration, client and listener elements, and the error palette all change. Review the changes and update your apps before upgrading. For more information about how to upgrade, see [Upgrading and Migrating A2A Connector to Version 2.x](https://docs.mulesoft.com/a2a-connector/latest/a2a-connector-upgrade-migrate). #### [](#protocol-and-transports)Protocol and Transports - A2A Connector now uses A2A protocol 1.0.0 instead of 0.3.0. Wire JSON-RPC method names change from slash-form to PascalCase. For example, `message/send` becomes `SendMessage`, `message/stream` becomes `SendStreamingMessage`, `tasks/get` becomes `GetTask`, `tasks/cancel` becomes `CancelTask`, and `tasks/resubscribe` becomes `SubscribeToTask`. Clients written against 0.3.0 must update their method strings. - An A2A Server can expose the same agent over both the JSON-RPC and the new HTTP+JSON transport bindings on a single connection (gRPC is out of scope for this release). - You can now send a non-blocking `SendMessage` request by setting `returnImmediately` to `true` in the request configuration. The A2A Server acknowledges the request with the initial `Task` and continues processing asynchronously, and the **A2A Server - On Async Request Listener** source authors that initial response. - At most one active `SendMessage` request (blocking, non-blocking, or streaming) can run against a given `taskId` at a time. A duplicate concurrent submission is rejected with `A2A:INVALID_REQUEST` ("Another SendMessage is already in flight for taskId {id}; retry once it completes."), which preserves the ordering of a task’s message history under concurrency. - Tasks in a terminal state (`TASK_STATE_COMPLETED`, `TASK_STATE_FAILED`, `TASK_STATE_CANCELED`, or `TASK_STATE_REJECTED`) are immutable. A `SendMessage` or `SendStreamingMessage` request against a terminal task is rejected with `A2A:UNSUPPORTED_OPERATION` ("Task has reached terminal state."). - Task states now use the `TASK_STATE_*` constants (for example, `TASK_STATE_WORKING`, `TASK_STATE_COMPLETED`) instead of the lowercase 0.3.0 states. - Streaming events use the A2A `StreamResponse` envelope shape with a single root key (`task`, `statusUpdate`, or `artifactUpdate`). There is no explicit `final` boolean. Finality is derived from `TaskStatus.state`. #### [](#server-configuration)Server Configuration - New required `` block on ``. One or more `` entries select the **Protocol** (`JSONRPC` or `HTTP_JSON`) and the **Path** segment appended to **Agent Path**. This is what enables multi-transport agents on a single connection. - **Agent Path** on `` is now the base HTTP path for both the agent card (served at `{agentPath}/.well-known/agent-card.json`) and every configured interface (`{agentPath}{interface.path}`), rather than a single fixed agent endpoint. - Startup validates a bijection between the configured `` entries and `agentCard.supportedInterfaces`. Mismatched `(protocol, path)` pairs fail initialization instead of surfacing as runtime 404s. - Multi-tenant support: A single connection can serve multiple tenants at the same `{agentPath}{interface.path}` surface. Each request’s tenant (the `params.tenant` field on the request body, or `?tenant=` on GET/DELETE) is validated against `agentCard.supportedInterfaces[].tenant` and surfaced to flows as `attributes.tenant`. #### [](#client-configuration)Client Configuration - The **Client Connection** provider is replaced by two transport-specific connection providers, **Jsonrpc Client Connection** and **Http Json Client Connection**, chosen via the **Connection** dropdown in Studio. The transport must match one of the entries in the target `agentCard.supportedInterfaces`. - The **Server Url** connection parameter is renamed to **Agent Url**, the base URL of the target A2A agent that the connector discovers via `{agentUrl}/.well-known/agent-card.json`. - Every outbound request now sends `A2A-Version: 1.0` as a default header unless you override it via ``. If overridden, the value is validated to be a `1.x` version. Agent-card discovery (both connect-time and the **A2A Client - Get Card** operation) is exempt from this header. #### [](#sources)Sources - The **A2A Server - Task Listener** source is now a unified listener. The same flow serves blocking `SendMessage`, non-blocking `SendMessage` (`returnImmediately=true`), and `SendStreamingMessage` over both JSON-RPC and HTTP+JSON, with no DSL change to distinguish the modes. The standalone **A2A Server - On Task Stream Listener** source is removed. - The new **A2A Server - On Async Request Listener** source lets the flow customize the initial `Task` response emitted for streaming and non-blocking `SendMessage` requests. The flow receives the incoming `MessageSendParams` as payload and must return a `Task` (or raise an error to reject the request, or return a terminal or interrupted-state `Task` to short-circuit and skip the **A2A Server - Task Listener** flow entirely). - The **A2A Server - Authorization Listener** source is replaced by the **A2A Server - Task Authorizer Listener** source, which uses a per-operation authorization contract and exposes the current operation name on `attributes.operationName`. - The **A2A Server - On Push Notification Set Listener** source output payload is now the resolved `TaskPushNotificationConfig` JSON rather than the raw request params. - SSE streams now close on terminal states (`TASK_STATE_COMPLETED`, `TASK_STATE_FAILED`, `TASK_STATE_CANCELED`, `TASK_STATE_REJECTED`) and on the interrupted state `TASK_STATE_INPUT_REQUIRED`. `TASK_STATE_AUTH_REQUIRED` does not close the stream. #### [](#operations)Operations - The new **A2A Client - List Tasks** operation is a client operation that returns the tasks from the target A2A server as a list (`Array of Any`) with a configurable streaming strategy, consumable from ``. - The new **A2A Server - Get Tasks** operation is a server-side batch read of stored tasks by ID. The flow supplies a **Task IDs** list and an optional **History Length** per task. - The new **A2A Server - Get Tasks By Context** operation is a server-side read of every stored task that belongs to a **Context Id**, returned oldest first. The flow supplies a **Context Id** and an optional **History Length** per task. - The new **A2A Server - Set Task Metadata** operation is a full-replace (no merge) of the persisted ``Task’s `metadata`` field. Pass `{}` to clear. It’s rejected for tasks in a terminal state. - The **Task Resubscribe** operation is renamed to **A2A Client - Subscribe To Task**. - The **A2A Client - Set Push Notification Config** operation is renamed to **A2A Client - Create Push Notification Config** (``). - The extended agent card is now fetched via a new **Use Extended Card** boolean parameter on the existing **A2A Client - Get Card** operation (defaults to `false`). No separate operation was added. - The **A2A Client - List Push Notification Configs** operation now returns its results as a list (`Array of Any`) with a configurable streaming strategy, also consumable from ``. - The **A2A Server - Send Push Notification** operation now accepts a full `StreamingMessageResponse` payload (Task, Message, `TaskStatusUpdateEvent`, or `TaskArtifactUpdateEvent`). - The **A2A Server - Update Task Status** and **A2A Server - Update Task Artifact** operations are uplifted to the A2A 1.0.0 event schemas, and each now declares only the concrete error types it raises. #### [](#errors)Errors - Added: `A2A:CONTENT_TYPE_UNSUPPORTED`, `A2A:INVALID_AGENT_RESPONSE`, `A2A:EXTENDED_CARD_UNCONFIGURED`, `A2A:EXTENSION_SUPPORT_REQUIRED`, and `A2A:VERSION_UNSUPPORTED`. - Updated: The `A2A:UNAUTHORIZED` JSON-RPC code moved from `-32005` to `-32099` (`-32005` is now the code for `CONTENT_TYPE_UNSUPPORTED`). Every error type now also carries a `google.rpc.ErrorInfo` reason string. - Dropped: `A2A:JSON_RPC_ERROR` (the umbrella parent type), `A2A:METHOD_NOT_FOUND`, and `A2A:REQUEST_TIMEOUT`. Each operation now declares only the concrete error types it actually raises, so verify your error handling after upgrading. ### Compatibility
Software Version

Mule

4.9.8 and later

OpenJDK

17

A2A protocol

1.0.0
## [](#1-1-1)1.1.1 **March 19, 2026** ### Compatibility
Software Version

Mule

4.9.8 and later

OpenJDK

17

A2A protocol

0.3.0
### Fixed Issues
Issue Resolution ID

The A2A server now validates that the generated task ID and context ID match the callback results from A2A Server - Task Listener for both Task and Message response types.

W-21503190
## [](#1-1-0)1.1.0 **March 2, 2026** ### Compatibility
Software Version

Mule

4.9.8 and later

OpenJDK

17

A2A protocol

0.3.0
### Fixed Issues
Issue Resolution ID

Use the new A2A Server - Authorization Listener source to add authoritative checks for implicit methods such as tasks/get, tasks/cancel, tasks/resubscribe, tasks/pushNotificationConfig/list, tasks/pushNotificationConfig/get, or tasks/pushNotificationConfig/delete. This is a critical security feature missing in earlier versions of the connector. For more information, see the A2A Connector Reference.

W-21227405

A2A Connector now removes the trailing / to the agent card path in the A2A Client. This change prevents 307 redirect issues that occurred in specific scenarios when the trailing / was present.

W-21341381
## [](#1-0-2)1.0.2 **February 24, 2026** ### Compatibility
Software Version

Mule

4.9.8 and later

OpenJDK

17

A2A protocol

0.3.0
### Fixed Issues
Issue Resolution ID

The A2A Server - Task Listener source now correctly returns an error when the Mule flow produces an unexpected response type instead of a valid Task or Message. Previously, an invalid response type could cause the flow to hang indefinitely.

W-20999176
## [](#1-0-1)1.0.1 **January 8, 2026** ### Compatibility
Software Version

Mule

4.9.8 and later

OpenJDK

17

A2A protocol

0.3.0
### Fixed Issues
Issue Resolution ID

DataSense is updated to suggest the structure of the payload emitted from the A2A Server - On Task Stream Listener source.

W-20657926
## [](#1-0-0)1.0.0 **December 17, 2025** ### What’s New - There is now a clear distinction in the naming between client and server operations/sources. - A2A Connector now supports the new **A2A Client - Send Stream Message**, **A2A Client - Task Resubscribe**, **A2A Server - Send Push Notification**, **A2A Server - Update Task Artifact**, and **A2A Server - Update Task Status** operations. - A2A Connector now supports the new **A2A Server - On Task Stream Listener** source. - In the **A2A Server - On Push Notification Set Listener** source, **Response Timeout** is now **Push notification request timeout**, and **Response Timeout Unit** is now **Request Timeout Unit**. - Push notifications on the A2A server side are no longer supported unless the **A2A Server - On Push Notification Set Listener** source is defined. - The server now performs out-of-the-box context ID and task ID validations for tasks associated with the application. - The server now supports task cancellation via the `tasks/cancel` method. - A2A Connector now includes the `A2A:TASK_NOT_CANCELABLE` and `A2A:UNSUPPORTED_OPERATION` errors for all operations. - A2A Connector no longer includes the `A2A:TASK_ALREADY_COMPLETED` error for all operations. - A2A Connector now uses the A2A Java SDK for request and response validations, which enhances reliability. - In the Server connection type, **Card** is replaced with either **Card Json** or **Card Path** to define the agent card. - The **Agent Card**, **Agent Skill**, **Agent Capabilities**, **Agent Extension**, **Agent Provider**, **Security Requirement**, **Http Security Scheme**, **Api Key Security Scheme**, **Oauth2 Security Scheme**, **Oauth2 Flows**, **Implicit Oauth2 Flows**, **Oauth2 Scope**, **Password Oauth2 Flows**, **Client Credentials Oauth2 Flows**, **Authorization Code Oauth2 Flows**, and **Open Id Connect Security Scheme** types are no longer supported. For more information, see [Upgrading and Migrating A2A Connector](https://docs.mulesoft.com/a2a-connector/latest/a2a-connector-upgrade-migrate) and [A2A Connector Reference](https://docs.mulesoft.com/a2a-connector/latest/a2a-connector-reference). ### Compatibility
Software Version

Mule

4.9.8 and later

OpenJDK

17

A2A protocol

0.3.0
## [](#0-4-0-beta)0.4.0-BETA **September 30, 2025** ### What’s New - A2A Connector now uses A2A protocol 0.3.0 instead of 0.2.3. - The connector now supports the new **Additional Properties** field for the **Cancel Task**, **Delete Push Notification Config**, **Get Card**, **Get Push Notification Config**, **Get Task**, **List Push Notification Configs**, **Send Message**, and **Set Push Notification Config** operations. Use this field to specify the type of client (such as an agent, a user, or others) that forwards the request to the agent for Agent Fabric. - The public endpoint to fetch the agent card is updated from `/.well-known/agent.json` to `/.well-known/agent-card.json`. - The Client connection type now supports the new **Get Push Notification Config**, **Set Push Notification Config**, **List Push Notification Configs**, and **Delete Push Notification Config** operations. - The Server connection type now supports the **On Push Notification Set Listener** source, to handle incoming requests with push notification configuration data. This source validates the push notification configuration before routing the request to the **Task Listener** source. - The Agent Card type now includes the new **Protocol Version** field to indicate the A2A specification version the agent is running on. - The connector no longer supports the **Send Task** operation. - The connector now includes the `A2A:PUSH_NOTIFICATION_UNSUPPORTED` error for **Delete Push Notification Config**, **Get Push Notification Config**, **List Push Notification Configs**, and **Set Push Notification Config** operations. - The Request Attributes type now includes the **Task Id**, and **Context Id** fields. For more information, see the [A2A Connector Reference](https://docs.mulesoft.com/a2a-connector/latest/a2a-connector-reference). ### Compatibility
Software Version

Mule

4.9.4 and later

OpenJDK

17

A2A protocol

0.3.0
### Fixed Issues
Issue Resolution ID

A2A Connector for Agent Conductor now uses the latest A2A protocol version’s type definitions to ensure proper functioning.

W-19128112
## [](#0-3-0-beta)0.3.0-BETA **August 6, 2025** ### What’s New - A2A Connector now supports distributed tracing. - These types are added: - Certificate Data - Certificate Extension - Alternative Name Data - Principal Data - X500 Principal Data - Public Key Data - Serial Number Data - The Request Attributes type now includes the **Version**, **Scheme**, **Method**, **Local Address**, **Remote Address**, and **Client Certificate** fields. For more information, see the [A2A Connector Reference](https://docs.mulesoft.com/a2a-connector/latest/a2a-connector-reference). ### Compatibility
Software Version

Mule

4.9.4 and later

OpenJDK

17

A2A protocol

0.2.3
### Fixed Issues
Issue Resolution ID

Task history exceptions no longer abort the correct execution of the flow. Task history failures are now logged but do not affect the A2A response sent to the client.

W-19127970

Disabling task history now properly bypasses task history processing. Task history processing no longer performs unnecessary serialization when disabled, improving performance and preventing serialization failures.

W-19128017
## [](#0-2-0-beta)0.2.0-BETA **July 29, 2025** ### What’s New - A2A Connector now uses A2A protocol 0.2.3 instead of 0.1.0. - The Client connection type now supports default headers. - The **Get Card** and **Send Message** operations are added. - A2A Connector now supports task history, and the `A2A:TASK_ALREADY_COMPLETED` and `A2A:TASK_NOT_FOUND` errors are included in all operations. - These types are added: - Agent Extension - Security Requirement - Http Security Scheme - Api Key Security Scheme - Oauth2 Security Scheme - Oauth2 Flows - Implicit Oauth2 Flows - Oauth2 Scope - Password Oauth2 Flows - Client Credentials Oauth2 Flows - Authorization Code Oauth2 Flows - Open Id Connect Security Scheme For more information, see the [A2A Connector Reference](https://docs.mulesoft.com/a2a-connector/latest/a2a-connector-reference). ### Compatibility
Software Version

Mule

4.9.4 and later

OpenJDK

17

A2A protocol

0.2.3
## [](#0-1-0-beta)0.1.0-BETA **May 27, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/a2a-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [A2A Connector User Guide](https://docs.mulesoft.com/a2a-connector/latest/). ### Compatibility
Software Version

Mule

4.9.4 and later

OpenJDK

17

A2A protocol

0.1.0
## [](#see-also)See Also - [A2A Connector User Guide](https://docs.mulesoft.com/a2a-connector/latest/) - [A2A Connector Reference](https://docs.mulesoft.com/a2a-connector/latest/a2a-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # A2A In-Task Authorization Code Policy The A2A In-Task Authorization Code Policy policy ensures secondary credentials are present for in-task authentication using OAuth 2.0 Authorization Code flow. For configuration details, see [A2A In-Task Authorization Code Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-a2a-intask-authorization-code). ## [](#june-08-2026)June 08, 2026 ### What’s New - A2A In-Task Authorization Code Policy policy implementation version 1.0.2 is now supported by Omni Gateway. ## [](#january-30-2026)January 30, 2026 ### What’s New - A2A In-Task Authorization Code Policy policy definition version 1.0.0 is now supported by Omni Gateway. # A2A OAuth2 OBO Credential Injection The A2A OAuth2 OBO Credential Injection policy exchanges incoming bearer tokens using OAuth 2.0 Token Exchange (RFC 8693), Microsoft Entra ID On-Behalf-Of, or OAuth 2.0 Token Exchange with CIBA. For configuration details, see [OAuth 2.0 OBO Credential Injection Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-oauth-obo). ## [](#april-30-2026)April 30, 2026 ### What’s New - A2A OAuth2 OBO Credential Injection policy implementation version 1.1.4 is now supported by Omni Gateway. - A2A OAuth2 OBO Credential Injection policy definition version 1.1.2 is now supported by Omni Gateway. # A2A PII Detector The A2A PII Detector policy detects personally identifiable information (PII) in A2A JSON-RPC traffic. For configuration details, see [A2A Personally Identifiable Information (PII) Detector Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-pii-detector). ## [](#june-05-2026)June 05, 2026 ### What’s New - A2A PII Detector policy implementation version 1.0.9 is now supported by Omni Gateway. ## [](#may-13-2026)May 13, 2026 ### What’s New - A2A PII Detector policy definition version 1.0.2 is now supported by Omni Gateway. # A2A Prompt Decorator The A2A Prompt Decorator policy decorates prompts with context information. For configuration details, see [A2A Prompt Decorator Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-prompt-decorator). ## [](#may-13-2026)May 13, 2026 ### What’s New - A2A Prompt Decorator policy implementation version 1.0.6 is now supported by Omni Gateway. ## [](#april-20-2026)April 20, 2026 ### What’s New - A2A Prompt Decorator policy definition version 1.0.2 is now supported by Omni Gateway. # A2A Quality Evaluation Policy The A2A Quality Evaluation policy evaluates completed A2A agent task responses using an LLM to score quality and completeness against the original user intent. For configuration details, see [A2A Quality Evaluation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-quality-evaluation). ## [](#august-3-2026)August 3, 2026 ### What’s New - A2A Quality Evaluation policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A Quality Evaluation policy definition version 1.0.0 is now supported by Omni Gateway. # A2A Schema Validation The A2A Schema Validation policy validates Agent requests to ensure they conform to the A2A specification. For configuration details, see [A2A Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-schema-validation). ## [](#may-13-2026)May 13, 2026 ### What’s New - A2A Schema Validation policy implementation version 1.0.6 is now supported by Omni Gateway. ## [](#april-20-2026)April 20, 2026 ### What’s New - A2A Schema Validation policy definition version 1.0.2 is now supported by Omni Gateway. # A2A Token Based Rate Limit The A2A Token Based Rate Limit policy rate limits agent usage of upstream resources. For configuration details, see [A2A Token Based Rate Limit Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-token-rate-limit). ## [](#june-10-2026)June 10, 2026 ### What’s New - A2A Token Based Rate Limit policy implementation version 1.0.4 is now supported by Omni Gateway. ## [](#april-20-2026)April 20, 2026 ### What’s New - A2A Token Based Rate Limit policy definition version 1.0.1 is now supported by Omni Gateway. # A2A v1 Agent Card Policy The A2A v1 Agent Card Policy policy rewrites interface URLs in the A2A v1.0 agent card to match the gateway’s public address For configuration details, see [A2A v1 Agent Card Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-v1-agent-card). ## [](#july-14-2026)July 14, 2026 ### What’s New - A2A v1 Agent Card policy implementation version 1.0.2 is now supported by Omni Gateway. - A2A v1 Agent Card policy definition version 1.0.1 is now supported by Omni Gateway. # A2A v1 Azure Content Guardrails Policy The A2A v1 Azure Content Guardrails Policy policy evaluates A2A v1 agent messages against Azure AI Content Safety for harmful content, jailbreak attempts, hallucinations, and copyrighted material. For configuration details, see [A2A v1 Azure Content Guardrails Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-v1-azure-guardrails). ## [](#aug-6-2026)Aug 6, 2026 ### What’s New - A2A v1 Azure Content Guardrails policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A v1 Azure Content Guardrails policy definition version 1.0.0 is now supported by Omni Gateway. # A2A v1 Bedrock Guardrails Policy The A2A v1 Bedrock Guardrails Policy policy evaluates A2A v1.0 agent requests and responses against Amazon Bedrock guardrails for content safety, PII detection, and contextual grounding. For configuration details, see [A2A v1 Bedrock Guardrails Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-v1-bedrock-guardrails). ## [](#aug-4-2026)Aug 4, 2026 ### What’s New - A2A v1 Bedrock Guardrails policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A v1 Bedrock Guardrails policy definition version 1.0.0 is now supported by Omni Gateway. # A2A v1 Personally Identifiable Information (PII) Detector Policy The A2A v1 Personally Identifiable Information (PII) Detector Policy policy detects personally identifiable information (PII) in A2A v1 requests across all transports. For configuration details, see [A2A v1 Personally Identifiable Information (PII) Detector Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-v1-pii-detector). ## [](#july-15-2026)July 15, 2026 ### What’s New - A2A v1 PII Detector policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A v1 PII Detector policy definition version 1.0.0 is now supported by Omni Gateway. # A2A v1 Prompt Decorator Policy The A2A v1 Prompt Decorator Policy policy decorates A2A v1 prompts with additional context information. For configuration details, see [A2A v1 Prompt Decorator Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-v1-prompt-decorator). ## [](#july-15-2026)July 15, 2026 ### What’s New - A2A v1 Prompt Decorator policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A v1 Prompt Decorator policy definition version 1.0.0 is now supported by Omni Gateway. # A2A v1 Schema Validation Policy The A2A v1 Schema Validation Policy policy verifies that requests to the agent are compliant with the A2A v1.0 specification. For configuration details, see [A2A v1 Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-v1-schema-validation). ## [](#july-15-2026)July 15, 2026 ### What’s New - A2A v1 Schema Validation policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A v1 Schema Validation policy definition version 1.0.0 is now supported by Omni Gateway. # A2A v1 to v0.3 Transcoder Policy The A2A v1 to v0.3 Transcoder Policy policy transcodes protocol messages bidirectionally between A2A v1.0 JSON-RPC clients and A2A v0.3 backend servers. For configuration details, see [A2A v1 to v0.3 Transcoder Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-a2a-v1-to-v03-transcoder). ## [](#july-15-2026)July 15, 2026 ### What’s New - A2A v1 to v0.3 Transcoder policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A v1 to v0.3 Transcoder policy definition version 1.0.0 is now supported by Omni Gateway. # A2A v1 Token Based Rate Limit Policy The A2A v1 Token Based Rate Limit Policy policy rate limits v1 A2A agent usage of upstream resources. For configuration details, see [A2A v1 Token Based Rate Limit Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-v1-token-rate-limit). ## [](#july-15-2026)July 15, 2026 ### What’s New - A2A v1 Token Based Rate Limit policy implementation version 1.0.0 is now supported by Omni Gateway. - A2A v1 Token Based Rate Limit policy definition version 1.0.0 is now supported by Omni Gateway. # Access Management Release Notes The following release notes detail new features and fixed issues in the Access Management section of Anypoint Platform: [Anypoint Access Management Release Notes](https://docs.mulesoft.com/jp/release-notes/access-management/access-management-release-notes) ## [](#see-also)See Also - [アクセス管理について](https://docs.mulesoft.com/jp/access-management/) - [Known Issues](https://help.salesforce.com/s/issues) # Agent Connection Telemetry The Agent Connection Telemetry policy tracks the number of requests made to agent or MCP server instances. For configuration details, see [Agent Connection Telemetry Policy](https://docs.mulesoft.com/gateway/latest/policies-included-agent-connection-telemetry). ## [](#june-11-2026)June 11, 2026 ### What’s New - Agent Connection Telemetry policy implementation version 1.0.4 is now supported by Omni Gateway. - Agent Connection Telemetry policy definition version 1.0.3 is now supported by Omni Gateway. # Agent Fabric Release Notes Agent Fabric is the AI control plane for AI agents, Model Context Protocol (MCP) servers, and APIs built across platforms. You can see all of your services, let agents take action in your existing tech stack, enforce open policies at runtime, and track and optimize the cost of your AI investments. ## [](#october-21-2026)October 21, 2026 ### What’s New - You can now deploy your agent network locally and test each broker through an Agent-to-Agent (A2A) chat interface directly from Anypoint Code Builder. Use local deployments to iterate on your agent network without publishing or deploying it. For more information, see [Deploy and Test Agent Networks Locally](https://docs.mulesoft.com/agent-network/latest/af-local-deploy-and-test). - You can now configure OAuth 2.0 client credentials authentication for LLMs in agent networks. For more information, see [Agent Network YAML Reference](https://docs.mulesoft.com/agent-network/latest/af-agent-network-yaml-reference). - You can now reuse existing MCP assets from Exchange that use SSE transport. - Agent networks now support Agent Script dialect version 1.4. - You can now configure authentication for agent cards that use dual egress upstreams. For more information, see [Agent Network YAML Reference](https://docs.mulesoft.com/agent-network/latest/af-agent-network-yaml-reference). - This release fixes an issue in which deployments failed when an agent network reused an existing asset from Exchange. ### Fixed Issues
Issue Resolution ID

Declared variables are now validated when you build an agent network.

W-24455489

Deployments now preserve the proxy-aware Axios agent.

W-24195003

Builds now fail with error code 1035 when a broker has pushNotifications enabled.

W-23930153

Metadata for version 1.0 agent networks now includes an applications entry.

W-24235374

Agent network builds now detect variable name collisions.

W-24335536
## [](#august-31-2026)August 31, 2026 ### What’s New - You can now deploy agent networks to Anypoint Runtime Fabric (RTF) targets. Your RTF deployment must be on version 3.0.277 or later. For more information, see [Deploy Agent Network Instances](https://docs.mulesoft.com/agent-network/latest/af-deploy-agent-network-targets). - You can now deploy agent networks that do not include a registry. - Agent networks now support the [Extended Agent Card](https://a2a-protocol.org/latest/specification/#3111-get-extended-agent-card) from the Agent2Agent (A2A) Protocol specification, enabling richer agent metadata and discovery capabilities. - You can now connect the enhanced experience to AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault so API keys and other credentials stay in your secrets manager. MuleSoft stores only metadata, such as secret names and paths, not the secret values. It reads the secret from your vault when a model proxy or other service needs it. For more information, see [general::exp-vaults-manage.adoc](#general::exp-vaults-manage.adoc). - You can now contain a rogue AI agent before it leaks data, takes unauthorized actions, or runs up costs. Stop that agent’s requests from reaching your models, then restore access if the containment was a false positive. For more information, see [general::exp-detect-and-contain-rogue-agents.adoc](#general::exp-detect-and-contain-rogue-agents.adoc). - Cost Management now includes budget management. Set spending budgets for your model wallets, track spend against each budget, and manage budgets across providers and models from the **Budgets** tab. For more information, see [Budgets Tab](#general::exp-governance-view-cost-and-token-usage.adoc#budgets-tab). - The Cost Management **Optimizations** page now includes an **Agents** tab, so you can review token usage and optimization opportunities for your agents alongside model proxies and MCP servers. For more information, see [Filter and Search](#general::exp-governance-view-cost-and-token-usage.adoc#filter-and-search). - You can now create, edit, delete, and list model wallets, which allocate token budgets that are granted only when a request’s claims match the wallet’s required claims. Manage model wallets from the UI or through the MuleSoft Agent. For more information, see [general::exp-model-wallets-manage.adoc](#general::exp-model-wallets-manage.adoc). - You can now edit instances for model proxies, APIs, agents, and MCP servers from the service detail page or the instance detail page, without switching to Anypoint Platform. - Model Proxy now supports semantic caching, TLS security for provider connections, external vault–based provider authentication, and the Model Proxy Request Compression policy. For more details about updates to model proxy, see [Model Proxy Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/model-proxy-release-notes). - MCP Bridge now exposes tool output schemas as part of the MCP specification, so you can connect servers built with MCP Bridge to Agentforce. - These SaaS connectors are now available in the Trusted MCP catalog: Wix, WordPress.com, Hootsuite, Descript, Intercom, Front, and LiveChat. - You can now create an A2A bridge to make a non-A2A agent A2A-compliant so that Agent Fabric can discover, govern, and orchestrate it alongside native A2A agents. For more information, see [general::exp-services-create-a2a-bridge.adoc](#general::exp-services-create-a2a-bridge.adoc) - You can now use OAuth 2.0 Authorization Code for Microsoft Copilot Studio scanners to create, authorize, and test the provider connection before you continue scanner setup. For more information, see [Microsoft Copilot Studio OAuth Authorization](#general::exp-scanners-add-from-providers.adoc#microsoft-copilot-studio-oauth-authorization). - You can now apply universal policies to your API instances and manage the resulting native policies. A universal policy is defined once and applied as the correct native policy on each supported gateway. For more information, see: - [general::exp-governance-policy-library-apply.adoc](#general::exp-governance-policy-library-apply.adoc) - [general::exp-instances-add.adoc](#general::exp-instances-add.adoc) - [general::exp-policies-apply-manage.adoc](#general::exp-policies-apply-manage.adoc) - API scanners now write policies from these provider platforms: Google Apigee, Azure API Management, and Kong Gateway. For these providers, policy results are visible from each discovered API in Portfolio > APIs > Policies. For more information, see: - [general::exp-overview.adoc](#general::exp-overview.adoc) - [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc) - [general::exp-scanners-add-from-providers.adoc](#general::exp-scanners-add-from-providers.adoc) - [general::exp-scanners-prerequisites-reference.adoc](#general::exp-scanners-prerequisites-reference.adoc) - [general::exp-scanners-view-details.adoc](#general::exp-scanners-view-details.adoc) - [general::exp-scanners-manage.adoc](#general::exp-scanners-manage.adoc) - [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc) - You can now track remediation and scan status in the **Akamai Security Findings** table on the **Conformance** tab. For more information, see [Track Remediation and Scan Status](#general::exp-akamai-risk-correlation.adoc#track-remediation-and-scan-status). ### Fixed Issues - Improved performance for agent network operations. - Fixed issues with LLM connectivity and Gemini 3 model integration. ## [](#august-24-2026)August 24, 2026 ### What’s New - Use MuleSoft Vibes, Anypoint Code Builder, or the Anypoint CLI to undeploy agent networks and unpublish Exchange assets associated with those networks. For more information, see [Deploy Agent Network Instances](https://docs.mulesoft.com/agent-network/latest/af-deploy-agent-network-targets) and [Publish Agent Network Assets](https://docs.mulesoft.com/agent-network/latest/af-publish-agent-network-assets) ## [](#august-6-2026)August 6, 2026 ### What’s New - Previously in agent network 2.0, connection and broker IDs were restricted to lowercase letters, numeric characters, and non-trailing underscores. You can now use standard naming conventions, such as upper case letters, dashes, and periods for these IDs. - To resolve common deployment errors, see [Resolve Agent Network Deployment Errors in Anypoint Code Builder](https://docs.mulesoft.com/agent-network/latest/af-deploy-agent-network-targets#resolve-issues). ## [](#july-14-2026)July 14, 2026 ### What’s New Build agent networks with predictable, governed orchestration using [Agent Script](https://developer.salesforce.com/docs/ai/agentforce/guide/agent-script.html) — a graph-based language that gives you explicit control over how brokers coordinate agents, tools, and LLMs. In Agent Network 2.0, agent brokers use guided determinism to separate LLM-powered reasoning from deterministic control flow. With guided determinism you get intelligent decision-making where you need it and guaranteed execution paths everywhere else: - Define broker orchestration as a graph of nodes, edges, and triggers in Agent Script (`.agent`) files. Each node performs a discrete step — either an LLM-powered action like classification or a deterministic action like routing — giving you full visibility and control over execution order. - Use probabilistic nodes for complex, open-ended decisions that require nuanced judgment, such as ticket severity classification or intent recognition. - Use deterministic nodes to enforce fixed execution paths once a key decision has been made, ensuring reliable, rule-based behavior across operational flows. - View a graph-based visual canvas alongside Agent Script code. - Organize projects with a dedicated `/brokers` directory containing `.agent` files alongside your `agent-network.yaml` registry and context definitions. - Communicate across agents using version 1.0 of the Agent2Agent (A2A) Protocol specification. - Create and configure agent networks using natural-language prompts in MuleSoft Vibes, including broker graph design, node configuration, and Exchange asset integration. - Build, publish, and deploy agent networks in CI/CD environments using the Anypoint CLI plugin. For more information, see [Building Agent Networks for Agent Fabric](https://docs.mulesoft.com/agent-network/latest/af-agent-networks). ## [](#april-29-2026)April 29, 2026 ### What’s New These Agent Fabric features are now available in Canada Cloud and Japan Cloud.
Category Feature

Discoverability

Agent Registry: Agent Assets

Agent Registry: MCP Assets (Including Public MCP Assets)

Agent Registry: LLM Assets

Agent Scanners

Governance

Agent, MCP, LLM instances in API Management

A2A, MCP, LLM Omni policies

Managed Omni Gateway in CloudHub 2.0

Managed Omni Gateway in Anypoint Runtime Fabric

Trusted Agent Identity

MCP Bridge

Orchestration

Agent Broker authoring with MuleSoft Vibes (Anypoint Code Builder)

Agent Broker authoring via YAML (Anypoint Code Builder)

Agent Broker deployment to CloudHub 2.0

Agent Broker deployment to Anypoint Runtime Fabric
For details, see [Hyperforce Release Notes](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes). ## [](#february-172026)February 17,2026 ### What’s New - Exchange now supports GoDaddy ANS agents. You can now add a scanner to automatically discover and register GoDaddy ANS agents. GoDaddy ANS agents are verified by GoDaddy to be safe and secure. Govern and consume the agents in other applications. For more information, see [exchange::adding-godaddy-scanner.adoc](#exchange::adding-godaddy-scanner.adoc). ## [](#february-9-2026)February 9, 2026 ### What’s New - Agent Visualizer now includes search and filtering capabilities and MCP server and tool insights. For more information, see [Agent Visualizer Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-visualizer/agent-visualizer-release-notes). ## [](#february-6-2026)February 6, 2026 ### What’s New - This release includes agent network project updates. See [Agent Network Project Updates](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#new-features-agent-networks-feb6-26). ## [](#january-30-2026)January 30, 2026 - In Anypoint Exchange, you can now add agent scanners to automatically discover and register AI agents across agent ecosystems on external platforms, which include Amazon Bedrock, Google Vertex AI, and Microsoft Azure Copilot. After the agents are registered, govern and consume them in other applications. For more information, see [exchange::discovering-and-importing-external-agents.adoc](#exchange::discovering-and-importing-external-agents.adoc). ## [](#january-23-2026)January 23, 2026 ### What’s New - Anypoint Exchange now includes an option to publish MCPs via URLs instead of uploading a schema file. For more information, see [Anypoint Exchange Release Notes](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes). - You can now create and manage instances for publicly available MCP servers in API Manager. For more information, see [API Manager Release Notes](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes). ## [](#january-15-2026)January 15, 2026 ### What’s New - This release includes agent network project updates and fixed issues. See [Agent Network Project Updates](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#new-features-agent-networks-jan15-26). ## [](#december-11-2025)December 11, 2025 ### What’s New - This release includes agent network project updates and fixed issues. See [Agent Network Project Updates](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#new-features-agent-networks-dec11-25). ## [](#november-4-2025)November 4, 2025 ### What’s New - This release includes updates to agent network projects. See [Agent Network Project Updates](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#agent-networks-nov-25). ## [](#october-3-2025)October 3, 2025 ### What’s New - Discover agents and MCP servers with Anypoint Exchange. For more information, see [Anypoint Exchange Release Notes](https://docs.mulesoft.com/jp/release-notes/exchange/exchange-release-notes). - Orchestrate agents across ecosystems with agent brokers, a context-aware routing service for agents and assets. For more information, see [Anypoint Code Builder Release Notes](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes). - Secure Omni Gateway Instances with Policies. For more information, see [API Manager 2.x Release Notes](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes). - Observe and visualize your agentic assets. - View metrics, logs, and traces for agentic assets in Anypoint Monitoring. For more information, see [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes). - Observe every agent interaction with Agent Visualizer, a visual map for your agent network. For more information, see [Agent Visualizer Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-visualizer/agent-visualizer-release-notes). ## [](#see-also)See Also - [general::learning-map-agent-fabric.adoc](#general::learning-map-agent-fabric.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # Agent Visualizer Release Notes Agent Visualizer provides a detailed visual graph so you can see, understand, and interact with your enterprise’s evolving network of agents, Model Context Protocol (MCP) servers, and LLMs. ## [](#april-29-2026)April 29, 2026 ### What’s New These Agent Visualizer features are now available in Canada Cloud and Japan Cloud.
Category Feature

Observability

Agent Visualizer nodes

Agent Visualizer runtime edges

Agent Visualizer: Agent Metrics
For details, see [Hyperforce Release Notes](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes). ## [](#february-9-2026)February 9, 2026 ### What’s New - MCP server and tool insights Visualize agent and MCP server relationships to identify active tools ordered by throughput and drill down into specific tools to review instance counts, total calls, and error rates. - Advanced search capabilities Locate specific nodes instantly using case-insensitive search by display name, asset type, or platform. - Granular network filtering Isolate specific traffic patterns by filtering your agent network view based on business groups, environments (Production or Sandbox), and activity periods. For more information, see [View and Navigate the Agent Network](https://docs.mulesoft.com/agent-visualizer/view-and-navigate-agent-network). ## [](#october-3-2025)October 3, 2025 ### What’s New - This is a new product that provides a visual map of your agent network. For more information, see [Agent Visualizer Overview](https://docs.mulesoft.com/agent-visualizer/). ## [](#see-also)See Also - [Agent Visualizer Overview](https://docs.mulesoft.com/agent-visualizer/) - [Troubleshooting Your Agent Network in Agent Visualizer](https://docs.mulesoft.com/agent-visualizer/troubleshoot-agent-network) - [Known Issues](https://help.salesforce.com/s/issues) # Agentforce Connector Release Notes Agentforce Connector provides MuleSoft developers with the ability to seamlessly integrate with AI agents running in Salesforce’s Agentforce platform. Guide: [Agentforce Connector User Guide](https://docs.mulesoft.com/agentforce-connector/latest/) ## [](#1-3-0)1.3.0 **April 2, 2026** ### What’s New - You can now use the new **Send Message (Sync)** operation instead of **Continue agent conversation** to return a structured JSON response that separates business data from metadata. The **Continue agent conversation** operation was deprecated because it supported a limited set of response types and returned only the text from the **Message** field. - The **Start agent conversation** and **Send Message (Sync)** operations now support the **Agent Variables** field. Use this field to pass agent variables that provide additional context to the agent during a request. - The connector now includes the `MS-AGENTFORCE:AGENT_API_ERROR` and `MS-AGENTFORCE:INVALID_CONNECTION` error types for all operations. For more information, see [Agentforce Connector Reference](https://docs.mulesoft.com/agentforce-connector/latest/agentforce-connector-reference). ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#1-2-0)1.2.0 **September 26, 2025** ### What’s New - The **Start agent conversation** and **Continue agent conversation** operations now return the new `collect` additional attribute in the response, providing access to more elements from the agent’s full payload. - The new **Bypass User** field in the **Start agent conversation** operation now provides a mechanism to override the logged-in user’s permissions, allowing agents linked to Data Cloud content to use their own assigned user to access these assets. For more information, see [Agentforce Connector Reference](https://docs.mulesoft.com/agentforce-connector/latest/agentforce-connector-reference). ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#1-1-0)1.1.0 **April 29, 2025** ### What’s New - Transport Layer Security (TLS) configuration support is added. - You can now configure an HTTP proxy for this connector. - The **Read Timeout** and **Read Timeout Unit** parameters are supported at both the configuration and operation levels. For more information, see [Agentforce Connector Reference](https://docs.mulesoft.com/agentforce-connector/latest/agentforce-connector-reference). ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#1-0-1)1.0.1 **March 10, 2025** ### What’s New - Enhanced connector filtering mechanism is added to filter out Agentforce (Default) as these agents aren’t accessible via the API. ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#1-0-0)1.0.0 **February 20, 2025** ### What’s New This is a new connector. For more information, see the [Agentforce Connector User Guide](https://docs.mulesoft.com/agentforce-connector/latest/). ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [Agentforce Connector User Guide](https://docs.mulesoft.com/agentforce-connector/latest/) - [Agentforce Connector Reference](https://docs.mulesoft.com/agentforce-connector/latest/agentforce-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Aggregators Module Release Notes Aggregators Module contains different types of aggregators that use a specified configuration to both store and release values. An _aggregator scope_ is a component that collects those values until a specified condition is met, when it then executes a processor’s chain of components, with the list of aggregated elements as the payload. Guide: [Aggregators Module User Guide](https://docs.mulesoft.com/jp/aggregators-module/latest/) Reference: [Aggregators Module Reference](https://docs.mulesoft.com/jp/aggregators-module/latest/aggregators-module-reference) ## [](#1-1-6)1.1.6 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-5)1.1.5 **August 3, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-4)1.1.4 **December 19, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer includes the Spring Framework dependency in its test suite to address the CVE-2025-41242 security vulnerability.

W-20381761
## [](#1-1-3)1.1.3 **July 9, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Aggregators Module no longer fails with ObjectStore exceptions that cause data loss during patch updates on CloudHub 2.0 when using the rolling updates deployment model.

W-18300854
## [](#1-1-2)1.1.2 **October 16, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The parent pom and internal dependencies are updated to fix vulnerabilities.

W-14499059, W-14499057
## [](#1-1-1)1.1.1 **July 5, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Spring Context and Spring Test are upgraded to 5.3.37.

W-15241724
## [](#1-1-0)1.1.0 **May 12, 2023** ### What’s New - The module now includes the new system properties `mule.aggregator.executor.delayForQuorum` and `mule.aggregator.executor.failOnStartIfNoQuorum`. For more information, refer to the [Aggregators Module Reference](https://docs.mulesoft.com/jp/aggregators-module/latest/aggregators-module-reference). ### Compatibility
Application/Service Version

Mule

4.1.1 and later
## [](#1-0-5)1.0.5 **September 13, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

When restarting an aggregator listener, the registered listener did not unregister at startup.

AMOD-11
## [](#1-0-4)1.0.4 **May 11, 2021** ### [](#fixed-issues-6)Fixed Issues - Fixed an issue that caused redeployments in CloudHub to show an `ObjectAlreadyExistsException` exception. (AMOD-8) - Fixed an issue introduced in Aggregators Module 1.0.3 that caused applications using a persistent object store to crash with a `ClassCastException` exception during the update of the module version. (AMOD-9) ### [](#compatibility-9)Compatibility Aggregators Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#1-0-3)1.0.3 **March 30, 2021** ### [](#fixed-issues-7)Fixed Issues Fixed an issue that caused the loss of messages when using the Aggregators Module inside of a Scatter-Gather or a For Each scope. (AMOD-5) ### [](#compatibility-10)Compatibility The Aggregators Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#1-0-2)1.0.2 **March 19, 2020** ### [](#fixed-issues-8)Fixed Issues Aggregators Module did not have the stereotype required to properly look up the relationship that an aggregator source has to the aggregator by name. (MULE-17242) ### [](#compatibility-11)Compatibility The Aggregators Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#1-0-1)1.0.1 **March 8, 2019** ### [](#fixed-issues-9)Fixed Issues - Timeout aggregation executed even if the maxSize was reached. (MULE-16539) ### [](#compatibility-12)Compatibility The Aggregators Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#1-0-0)1.0.0 **August 17, 2018** ### [](#compatibility-13)Compatibility The Aggregators Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon Bedrock Connector Release Notes Anypoint Connector for Amazon Bedrock (Amazon Bedrock Connector) provides seamless access to Amazon Bedrock, a fully managed service offering high-performing foundation models (FMs) from leading AI providers. The connector enables customers to invoke, evaluate, and integrate Bedrock models and operations within Mule flows, supporting use cases such as prompt-based inference, Retrieval-Augmented Generation (RAG), and agent-driven, multi-step workflows over enterprise data. While each model provider exposes different APIs and capabilities, the connector abstracts these differences and offers a unified, consistent interface to interact with all supported Bedrock models through MuleSoft. Guide: [Amazon Bedrock Connector User Guide](https://docs.mulesoft.com/amazon-bedrock-connector/latest/) ## [](#1-1-0)1.1.0 **September 4, 2026** ### What’s New - Amazon Bedrock Connector now supports Amazon Bedrock AgentCore, so you can build agentic AI applications with persistent memory and secure runtime invocation. For more information, see [Configuring AgentCore Operations](https://docs.mulesoft.com/amazon-bedrock-connector/latest/configuring-agentcore-operations). - You can now create, update, delete, retrieve, and list records in an AgentCore Memory resource by using the new [AgentCore - Batch Create Memory Records](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreBatchCreateMemoryRecords), [AgentCore - Batch Update Memory Records](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreBatchUpdateMemoryRecords), [AgentCore - Batch Delete Memory Records](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreBatchDeleteMemoryRecords), [AgentCore - Get Memory Record](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreGetMemoryRecord), [AgentCore - List Memory Records](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreListMemoryRecords), and [AgentCore - Retrieve Memory Records](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreRetrieveMemoryRecords) operations. - You can now invoke a deployed AgentCore agent runtime and manage its sessions and credentials by using the new [AgentCore - Invoke Agent Runtime (Streaming)](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreInvokeAgentRuntime), [AgentCore - Invoke Agent Runtime As Bytes (Non Streaming)](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreInvokeAgentRuntimeAsBytes), [AgentCore - Stop Runtime Session](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreStopRuntimeSession), [AgentCore - Get Workload Access Token](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreGetWorkloadAccessToken), and [AgentCore - Get Resource API Key](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentcoreGetResourceApiKey) operations. - The [CHAT Answer Prompt Streaming](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#ChatAnswerPromptStreaming) operation now supports the **Model Arn** field and [Attachments](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#ConverseAttachment). You can include images or documents with the text prompt. You can also supply a base-model, inference-profile, or application-inference-profile ARN in **Model Arn** instead of **Model Name**. For more information, see [Configuring Chat Operations](https://docs.mulesoft.com/amazon-bedrock-connector/latest/configuring-chat-operations). - The [AGENT Chat](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentChat) and [AGENT Chat Streaming (SSE)](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#AgentChatStreamingSse) operations now support the **Session Attributes** and **Prompt Session Attributes** fields. Use **Session Attributes** to pass key-value context that persists across the entire agent session. Use **Prompt Session Attributes** to pass key-value context that applies only to the current prompt and turn. For more information, see [Configuring Agent Operations](https://docs.mulesoft.com/amazon-bedrock-connector/latest/configuring-agent-operations). - The [EMBEDDING Adhoc Query](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference#EmbeddingAdhocQuery) operation now supports base64-encoded document content in the **Document Bytes** field. The **File Path** field is now optional. When both fields are set, **Document Bytes** takes precedence. For more information, see [Configuring Embedding Operations](https://docs.mulesoft.com/amazon-bedrock-connector/latest/configuring-embedding-operations). - The **Region** field is removed from the **AGENT Define Prompt Template**, **CHAT Answer Prompt**, **CHAT Answer Prompt Streaming**, and **SENTIMENT Analyze** operations. Configure the AWS region by using the connection-level **Region Endpoint** field instead. - The **Request Timeout Unit** field in the **AGENT Chat** and **AGENT Chat Streaming (SSE)** operations now also supports `NANOSECONDS`, `MICROSECONDS`, `HOURS`, and `DAYS`. ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.54.12.

  • The commons-io library is upgraded to version 2.22.0.

  • The log4j-slf4j-impl library is upgraded to version 2.26.1.

  • The tika-core library is upgraded to version 3.3.2.

  • The tika-parser-pdf-module library is upgraded to version 3.3.2.

  • The tika-parsers library is upgraded to version 3.3.2.

W-23885800
## [](#1-0-2)1.0.2 **May 5, 2026** ### What’s New - The **Model Name** field now supports all Claude 4 models, including `Claude 4 Opus`, `Claude 4 Sonnet`, `Claude 4 Haiku`, and `Claude Opus 4.7`. - The connector automatically routes requests through the inference-profile ARN path for all Claude 4 models. It resolves and applies the necessary geographical prefixes (us., eu., apac., jp., au., and global.) to ensure compatible cross-region communication. - The connector now automatically adjusts request payloads based on model requirements and filters restricted parameters for Claude Opus 4.7. - The connector now handles extended-thinking content blocks from Claude 4 models. It automatically skips these internal blocks to return the final answer text to your Mule application. ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
## [](#1-0-1)1.0.1 **March 12, 2026** ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The connector no longer causes Mule flows to hang indefinitely or slow down other flows in the same application when the AGENT Chat Streaming (SSE) operation processes multiple concurrent requests simultaneously. Previously, a high number of concurrent streaming requests caused thread exhaustion, which affected the AGENT Chat Streaming (SSE) operation and all flows running in the same Mule application.

W-21245099
## [](#1-0-0)1.0.0 **February 5, 2026** ### What’s New This is a new connector. For more information, see the [Amazon Bedrock Connector User Guide](https://docs.mulesoft.com/amazon-bedrock-connector/latest/). ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
## [](#see-also)See Also - [Amazon Bedrock Connector User Guide](https://docs.mulesoft.com/amazon-bedrock-connector/latest/) - [Amazon Bedrock Connector Reference](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon Bedrock Guardrails Policy The Amazon Bedrock Guardrails Policy policy evaluates LLM prompts and responses against Amazon Bedrock guardrails for content safety, PII detection, and contextual grounding. For configuration details, see [Amazon Bedrock Guardrails Policy](https://docs.mulesoft.com/gateway/latest/policies-included-bedrock-guardrails). ## [](#june-03-2026)June 03, 2026 ### What’s New - Amazon Bedrock Guardrails Policy policy implementation version 1.0.1 is now supported by Omni Gateway. ## [](#may-15-2026)May 15, 2026 ### What’s New - Amazon Bedrock Guardrails Policy policy definition version 1.0.0 is now supported by Omni Gateway. # Amazon DynamoDB Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Amazon DynamoDB (DynamoDB Connector) is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. DynamoDB Connector provides connectivity to the Amazon DynamoDB API, enabling interaction with Amazon DynamoDB to create a database table that can store and retrieve any amount of data, and serve any level of request traffic. This connector automatically balances data and traffic for the table over a sufficient number of servers to handle the request capacity specified by a customer and the amount of data stored, while maintaining consistent and fast performance. Starting with v.1.0.0, DynamoDB Connector is licensed commercially with Anypoint Platform. Guide: [Amazon DynamoDB Connector](https://docs.mulesoft.com/amazon-dynamodb-connector/latest/) Reference: [Amazon DynamoDB Connector Reference](https://docs.mulesoft.com/amazon-dynamodb-connector/latest/amazon-dynamodb-connector-reference) ## [](#1-6-8)1.6.8 **October 14, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.55.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

NoClassDefFoundError: jdk/net/Sockets errors no longer occur when you test the connection or use the connector on CloudHub 2.0 with Java 17. Apache HttpClient 4 is restored as the default synchronous HTTP client.

W-24331071
## [](#1-6-7)1.6.7 **September 29, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.55.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.55.2.

  • The Jackson library is upgraded to version 2.22.3.

  • The Netty library is upgraded to version 4.2.18.Final.

  • The groovy-json library is upgraded to version 4.0.33.

W-24311500, W-24311504, W-24311507, W-24311509, W-24311510
## [](#1-6-6)1.6.6 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.50.2

OpenJDK

8, 11, and 17
## [](#1-6-5)1.6.5 **August 5, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.50.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to version 2.50.2.

  • The Jackson library is upgraded to version 2.22.1.

  • The Netty library is upgraded to version 4.2.16.Final.

W-23657978
## [](#1-6-4)1.6.4 **June 22, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.46.13

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.46.13.

  • The Jackson library is upgraded to version 2.22.0.

  • The Netty library is upgraded to version 4.2.15.Final.

  • The modelmapper library is upgraded to version 3.2.6.

  • The commons-io library is upgraded to version 2.22.0.

W-22899762
## [](#1-6-3)1.6.3 **April 12, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.40.16

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly supports separate configuration of custom STS and custom service endpoints. This ensures that role-based authentication succeeds in private network environments and no longer fails with a 404 error when both endpoints are used.

W-21866216
## [](#1-6-2)1.6.2 **January 7, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.40.16

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.40.16.

  • The commons-lang3 library is upgraded to version 3.20.0.

W-19578820
## [](#1-6-1)1.6.1 **December 5, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.38.7

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

In the Role connection type, when Try Default AWSCredentials Provider Chain is set to true, the connector now honors the configured Role ARN field and executes AssumeRole.

W-20320475
## [](#1-6-0)1.6.0 **November 23, 2025** ### What’s New - Amazon DynamoDB Connector now supports passing an external ID in Role-based authentication. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.38.7

OpenJDK

8, 11, and 17
## [](#1-5-6)1.5.6 **October 24, 2025** ### What’s New - The AWS SDK is now upgraded to version 2.33.4. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v2.33.4

OpenJDK

8, 11, and 17
## [](#1-5-5)1.5.5 **May 18, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.12.717

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-io library is upgraded to version 2.19.0 to address reported security vulnerabilities.

W-18458341
## [](#1-5-4)1.5.4 **March 27, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.12.717

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The dozer mapper library is now replaced by the model mapper library.

W-17713377
## [](#1-5-3)1.5.3 **May 14, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.12.717

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.amazonaws:aws-java-sdk-dynamodb library is upgraded to version 1.12.717 to fix reported security vulnerabilities.

W-15640467
## [](#1-5-2)1.5.2 **January 18, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8, 11, and 17
## [](#1-5-1)1.5.1 **May 2, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.13.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665454
## [](#1-5-0)1.5.0 **February 23, 2023** ### What’s New - Amazon DynamoDB Connector has a new **Paginated Query** operation that finds items based on primary key values. You can query any table or secondary index that has a composite primary key, a partition key, and a sort key. The operation returns pages with a limit specified in the **Limit** field or the maximum amount of 1MB data. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
## [](#1-4-14)1.4.14 **December 15, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Amazon DynamoDB Connector now shows the correct condition, expression, and query parameter descriptions in the Anypoint Studio UI.

W-12144256
## [](#1-4-13)1.4.13 **October 27, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core : jackson-databind : 2.13.2.2 library is upgraded to com.fasterxml.jackson.core : jackson-databind : 2.13.4.2 to address reported security vulnerabilities.

W-11853407
## [](#1-4-12)1.4.12 **September 27, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The commons-io library is upgraded to version 2.11.0 to address reported security vulnerabilities.

W-11749435
## [](#1-4-11)1.4.11 **September 12, 2022** ### What’s New - The Dozer library is upgraded to version 6.5.2 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Dozer library is upgraded to version 6.5.2 to address reported security vulnerabilities.

W-11681385
## [](#1-4-10)1.4.10 **August 8, 2022** ### What’s New - The AWS S3 SDK library is upgraded to `1.12.261` to address a reported security vulnerability. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The AWS S3 SDK library is upgraded to 1.12.261 to address a reported security vulnerability.

W-11454664
## [](#1-4-9)1.4.9 **June 9, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Commons Beanutils library from commons-beanutils:commons-beanutils:1.9.1 to commons-beanutils:commons-beanutils:1.9.4.

W-11192906
## [](#1-4-8)1.4.8 **April 11, 2022** ### Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920458
## [](#1-4-7)1.4.7 **January 10, 2022** ### Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9814
## [](#1-4-6)1.4.6 **September 10, 2021** ### What’s New - Upgraded the Amazon SDK for Java dependency to version 1.11.969. ### Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for DynamoDB

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The exception handler incorrectly wrapped errors to the MULE:ANY error type. Now, errors occur without any modification or wrapping.

CONN-8787
## [](#1-4-5)1.4.5 **August 17, 2021** ### What’s New - Added support for the dynamic loading of table names. ### Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for DynamoDB

v1.11.946

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Deleting an item with a binary attribute threw a MULE:UNKNOWN error.

SE-22057
## [](#1-4-4)1.4.4 **June 15, 2021** ### [](#compatibility-27)Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for DynamoDB

v1.11.946

OpenJDK

8 and 11
### [](#new-features)New Features - Added support for resolving input metadata in item operations. (CONN-1121) ## [](#1-4-3)1.4.3 **February 10, 2021** ### [](#compatibility-28)Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for DynamoDB

v1.11.946

OpenJDK

8 and 11
### [](#features)Features - Upgraded the Amazon SDK for Java dependency to version 1.11.946. - Removed the vulnerabilities caused by the Jackson Dataformat: CBOR library. (CONN-7656) ### [](#fixed-issues-22)Fixed Issues - None ## [](#1-4-2)1.4.2 **October 22, 2020** ### [](#compatibility-29)Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for DynamoDB

v1.11.816

OpenJDK

8 and 11
### [](#features-2)Features Multiple libraries have been updated to the latest versions. ### [](#fixed-issues-23)Fixed Issues None ## [](#1-4-1)1.4.1 **July 9, 2020** ### [](#compatibility-30)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.816

OpenJDK

8 and 11
### [](#features-3)Features Upgraded the Amazon SDK for Java dependency to version 1.11.816. ### [](#fixed-issues-24)Fixed Issues None ## [](#1-4-0)1.4.0 **January 14, 2020** ### [](#compatibility-31)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.649

Java

1.8.0_x
### [](#features-4)Features Implemented support for TLS configuration. (CONN-3628) ### [](#fixed-issues-25)Fixed Issues Added missing sessionToken field into the configuration. (SE-14206) ## [](#1-3-1)1.3.1 **November 14, 2019** ### [](#compatibility-32)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.604

Java

1.8.0_x
### [](#features-5)Features None ### [](#fixed-issues-26)Fixed Issues DynamoDB Connector did not refresh the token when using a role-based connection. (CONN-4189) ## [](#1-3-0)1.3.0 **September 3, 2019** ### [](#compatibility-33)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.604

Java

1.8.0_x
### [](#features-6)Features Upgraded the Amazon SDK for Java dependency to version 1.11.604. ### [](#fixed-issues-27)Fixed Issues Error types included in the connector were not compatible with the error mapping format used by Mule. This caused a deployment failure. You can now use the connector’s error mapping. \[CONN-1247\] ## [](#1-2-0)1.2.0 **April 4, 2019** ### [](#compatibility-34)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for DynamoDB

v1.11.515

Java

1.8.0_x
### [](#features-7)Features Added support for new AWS region endpoints. ### [](#fixed-issues-28)Fixed Issues None ## [](#1-1-0)1.1.0 **February 21, 2018** ### [](#compatibility-35)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for DynamoDB

v1.11.247

Java

1.8.0_x
### [](#features-8)Features None ### [](#fixed-issues-29)Fixed Issues AWS connectors shared a common library for the supported region endpoints that caused an issue when two different AWS connectors were used in a Mule app. This version fixes this issue. ## [](#1-0-0)1.0.0 **January 5, 2018** ### [](#compatibility-36)Compatibility
Application/Service Version

Mule

4.0.0 and later

Amazon Java SDK for DynamoDB

v1.11.247

Java

1.8.0_x
### [](#features-9)Features - Built with Mule v4.0.0 - Built with AWS SDK v1.11.247 - Support for temporary credentials - A checkbox named **Try Default AWS Credentials Provider Chain** has been added to the Global Element configuration. If selected, the connector first tries to obtain the credentials from an AWS environment. - Support for Retry Policy - The connector performs a maximum of 10 retries when a request fails due to server-side throttling or dropped connection. The following operations are supported: Control Plane: - CreateTable - DeleteTable - ListTables - UpdateTable Data Plane: - PutItem - BatchWriteItem Reading Data: - GetItem - BatchGetItem - Query - Scan Updating Data: - Updating Data Deleting Data: - DeleteItem - BatchDeleteItem DynamoDB Streams: - ListStreams - DescribeStream - GetShardIterator - GetRecords ### [](#fixed-issues-30)Fixed Issues Initial version ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon EC2 Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Amazon Elastic Compute Cloud (Amazon EC2 Connector) provides scalable computing capacity in the Amazon Web Services (AWS) cloud. Amazon EC2 Connector provides connectivity to the Amazon EC2 API enabling you to interface with Amazon EC2 to launch as many virtual servers as you need, configure security and networking, and manage storage. Guide: [Amazon EC2 Connector](https://docs.mulesoft.com/amazon-ec2-connector/latest/) Reference: [Amazon EC2 Connector Reference](https://docs.mulesoft.com/amazon-ec2-connector/latest/amazon-ec2-connector-reference) ## [](#3-0-4)3.0.4 **September 30, 2026** ### Compatibility
Application/Service Version

Mule runtime

4.2.0 and later

AWS SDK for Java

v2.49.6

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Connections that use role authentication no longer leak internal AWS Security Token Service (STS) resources during connection, reconnection, or redeployment. Previously, these resources accumulated over repeated connection and redeployment cycles and could eventually exhaust threads and file descriptors in long-running deployments.

W-24148475
## [](#3-0-3)3.0.3 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule runtime

4.2.0 and later

AWS SDK for Java

v2.49.6

OpenJDK

8, 11, and 17
## [](#3-0-2)3.0.2 **August 5, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule runtime

4.2.0 and later

AWS SDK for Java

v2.49.6

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The AWS SDK for Java is upgraded to version 2.49.6 to address reported security vulnerabilities.

W-23657994
## [](#3-0-1)3.0.1 **March 8, 2026** ### Compatibility
Application/Service Version

Mule runtime

4.2.0 and later

AWS SDK for Java

v2.42.1

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • AWS SDK for Java is upgraded to version 2.42.1.

  • The commons-lang3 library is upgraded to version 3.20.0.

W-20597615
## [](#3-0-0)3.0.0 **December 18, 2025** ### What’s New - The AWS SDK version is upgraded to v2.x.x. The response is now aligned with the new SDK specifications. ### Compatibility
Application/Service Version

Mule runtime

4.2.0 and later

AWS SDK for Java

v2.35.3

OpenJDK

8, 11, and 17
## [](#2-5-8)2.5.8 **August 22, 2024** ### Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.969

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The response of the Describe instances operation is now populated with CPU instances details.

W-13218646
## [](#2-5-7)2.5.7 **April 19, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.969

OpenJDK

8, 11, and 17
## [](#2-5-6)2.5.6 **May 2, 2023** ### Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.13.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665445
## [](#2-5-5)2.5.5 **October 27, 2022** ### What’s New - The Jackson Databind library is updated to `com.fasterxml.jackson.core:jackson-databind:2.13.2.2`. ### Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Jackson Databind library is updated from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2 to fix reported security vulnerabilities.

W-11845801
## [](#2-5-4)2.5.4 This version was inadvertently skipped. ## [](#2-5-3)2.5.3 **April 11, 2022** ### Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920456
## [](#2-5-2)2.5.2 **January 11, 2022** ### Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9825
## [](#2-5-1)2.5.1 **September 10, 2021** ### What’s New - Upgraded the Amazon SDK for Java dependency to version 1.11.969. ### Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The exception handler incorrectly wrapped errors to the MULE:ANY error type. Now, errors occur without any modification or wrapping.

CONN-8787
## [](#2-5-0)2.5.0 **May 11, 2021** ### [](#compatibility-13)Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.946

OpenJDK

8 and 11
### [](#fixed-issues-10)Fixed Issues - Filtering did not work properly when using the **Edit inline** option for the **Name** field. A new field called **Filter Name** for the `Filter.class` resolves this issue. The **Name** field is deprecated. (SE-20391) ## [](#2-4-1)2.4.1 **February 11, 2021** ### [](#compatibility-14)Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.946

OpenJDK

8 and 11
### [](#features)Features - Upgraded the Amazon SDK for Java dependency to version 1.11.946. - Removed the vulnerabilities caused by the Jackson Dataformat: CBOR library (CONN-7656). ### [](#fixed-in-this-release)Fixed in this Release - None ## [](#2-4-0)2.4.0 **November 25, 2020** ### [](#compatibility-15)Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.816

OpenJDK

8 and 11
### [](#features-2)Features - Added the following new fields to the **Modify Image Attribute** operation: - **Description**, which describes the Amazon Machine Image (AMI) - **Launch Permissions**, which contains launch permissions for the AMI - **Product codes**, which contains DevPay product codes for the AMI For more information about these fields, see the Reference. - Updated multiple libraries to the latest versions. ### [](#fixed-in-this-release-2)Fixed in this Release None ## [](#2-3-2)2.3.2 **July 13, 2020** ### [](#compatibility-16)Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.816

OpenJDK

8 and 11
### [](#features-3)Features Upgraded the Amazon SDK for Java dependency to version 1.11.816. ### [](#fixed-in-this-release-3)Fixed in this Release None ## [](#2-3-1)2.3.1 **June 17, 2020** ### [](#compatibility-17)Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.799

Java

1.8.0_x
### [](#fixed-in-this-release-4)Fixed in this Release - The `Assign IPv6 Addresses` operation had both input parameters marked as optional (CONN-6208) - The `Describe image attribute` operation `Attribute` input parameter was not indicated as required (CONN-6211) - `Get console output` sometimes produced a `java.lang.NullPointerException` error when the EC2 instance was stopped (CONN-6212) ## [](#2-3-0)2.3.0 **January 30, 2020** ### [](#compatibility-18)Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.649

Java

1.8.0_x
### [](#features-4)Features - Support for a token refresh when using the Role connection type - Upgraded AWS SDK in aws-commons to version 1.11.649 ### [](#fixed-in-this-release-5)Fixed in this Release Added the missing **Session Token** field into the configuration (SE-14206) ## [](#2-2-0)2.2.0 **November 14, 2019** ### [](#compatibility-19)Compatibility
Application/Service Version

Mule Runtime

4.1.1 and later

AWS SDK for Java

v1.11.611

Java

1.8.0_x
### [](#features-5)Features Upgraded the Amazon SDK for Java dependency to version 1.11.611 ### [](#fixed-in-this-release-6)Fixed in this Release None ## [](#2-1-0)2.1.0 **February 21, 2018** ### [](#compatibility-20)Compatibility
Application/Service Version

Mule Runtime

4.1.0 and later

Amazon Java SDK for EC2

v1.11.134

Java

1.8.0_x
### [](#features-6)Features None ### [](#fixed-issues-11)Fixed Issues AWS connectors shared a common library for the supported Region Endpoints that caused an issue when two different AWS connectors were used in a Mule app. ## [](#2-0-0)2.0.0 **November 18, 2017** ### [](#compatibility-21)Compatibility

Application/Service

Version

Mule

4.1.0 and later

Amazon Java SDK for EC2

v1.11.134

Java

1.8.0_x
### [](#features-7)Features Migrated to Mule 4.0.0 runtime ### [](#fixed-issues-12)Fixed Issues None ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon Kinesis Connector Release Notes Anypoint Connector for Amazon Kinesis Data Streams (Amazon Kinesis Data Streams Connector) provides access to standard Amazon Kinesis Data Stream operations using Anypoint Platform. Guide: [Amazon Kinesis Connector User Guide](https://docs.mulesoft.com/amazon-kinesis-connector/latest/) ## [](#2-0-7)2.0.7 **October 15, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.4.3

Amazon-Kinesis-Producer

1.0.9

AWS SDK for Java

v2.55.12
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.55.12.

  • The kinesis-producer library is upgraded to version 1.0.9.

  • The netty library is upgraded to version 4.2.19.Final.

  • The guava library is upgraded to version 33.7.2-jre.

  • The commons-lang3 library is upgraded to version 3.21.0.

  • The lz4-java library is upgraded to version 1.12.0.

W-24453006
## [](#2-0-6)2.0.6 **October 1, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.4.3

Amazon-Kinesis-Producer

1.0.7

AWS SDK for Java

v2.55.6
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.55.6.

  • The jackson library is upgraded to version 2.22.3.

  • The netty library is upgraded to version 4.2.18.Final.

  • The guava library is upgraded to version 33.7.1-jre.

  • The protobuf-java library is upgraded to version 4.36.2.

  • The commons-codec library is upgraded to version 1.22.1.

  • The lz4-java library is upgraded to version 1.11.3.

  • The avro library is upgraded to version 1.12.2.

  • The wire-runtime library is upgraded to version 6.4.7 to address CVE-2026-45799.

  • The kafka-clients library version 3.6.1 is excluded.

W-24116041, W-24259063, W-24311535, W-24311537, W-24311542, W-24311539, W-24259070, W-23988548
## [](#2-0-5)2.0.5 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.4.3

Amazon-Kinesis-Producer

1.0.7

AWS SDK for Java

v2.51.2
## [](#2-0-4)2.0.4 **August 11, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.4.3

Amazon-Kinesis-Producer

1.0.7

AWS SDK for Java

v2.51.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.51.2.

  • The Amazon Kinesis Client Library is upgraded to version 3.4.3.

  • The jackson library is upgraded to version 2.22.1.

  • The netty library is upgraded to version 4.2.17.Final.

  • The guava library is upgraded to version 33.6.0-jre.

  • The protobuf-java library is upgraded to version 4.35.1.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-codec library is upgraded to version 1.22.0.

  • The kafka-clients library is upgraded to version 4.3.1.

  • The kotlin-stdlib library is upgraded to version 2.4.10.

  • The org.json library is upgraded to version 20260719.

W-23441645
## [](#2-0-3)2.0.3 **June 29, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.4.0

Amazon-Kinesis-Producer

1.0.7

AWS SDK for Java

v2.42.1
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The netty library is upgraded to version 4.2.15.Final.

  • The jackson library is upgraded to version 2.21.4.

W-22899565
## [](#2-0-2)2.0.2 **June 1, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.4.0

Amazon-Kinesis-Producer

1.0.7

AWS SDK for Java

v2.42.1
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-22339982
## [](#2-0-1)2.0.1 **March 10, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.4.0

Amazon-Kinesis-Producer

1.0.7

AWS SDK for Java

v2.42.1
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The avro library is upgraded to version 1.12.1.

  • AWS SDK for Java is upgraded to version 2.42.1.

  • The aws-sts library is upgraded to version 2.42.1.

  • The commons-codec library is upgraded to version 1.21.0.

  • The commons-io library is upgraded to version 2.21.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The guava library is upgraded to version 33.5.0-jre.

  • The jackson-core library is upgraded to version 2.21.1.

  • The jackson-databind library is upgraded to version 2.21.1.

  • The jackson-dataformat-cbor library is upgraded to version 2.21.1.

  • The json library is upgraded to version 20251224.

  • The kafka-clients library is upgraded to version 4.2.0.

  • The kafka-streams library is upgraded to version 4.2.0.

  • The kinesis-client library is upgraded to version 3.4.0.

  • The kinesis-producer library is upgraded to version 1.0.7.

  • The kotlin-scripting-jvm library is upgraded to version 2.2.21.

  • The kotlin-stdlib library is upgraded to version 2.2.21.

  • The netty-codec library is upgraded to version 4.2.10.Final.

  • The netty-codec-http library is upgraded to version 4.2.10.Final.

  • The netty-codec-http2 library is upgraded to version 4.2.10.Final.

  • The protobuf-java library is upgraded to version 4.33.5.

  • The snappy-java library is upgraded to version 1.1.10.8.

W-20579488
## [](#2-0-0)2.0.0 **November 22, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

3.2.0

Amazon-Kinesis-Producer

1.0.6
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The kinesis-client library is upgraded to version 3.2.0.

  • The kinesis-producer library is upgraded to version 1.0.6.

  • The aws-sts library is upgraded to version 2.38.3.

  • The aws-sdk library is upgraded to version 2.38.3.

  • The netty-codec-http library is upgraded to version 4.2.7.Final.

  • The netty-codec-http2 library is upgraded to version 4.2.7.Final.

  • The netty-codec library is upgraded to version 4.2.7.Final.

  • The kafka-clients library is upgraded to version 4.1.0.

  • The protobuf-java library is upgraded to version 4.33.0.

  • The commons-lang3 library is upgraded to version 3.19.0.

W-18514002
## [](#1-0-24)1.0.24 **November 13, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.15.10
### Fixed Issues
Issue Resolution ID

The Checkpoint On Complete field now works for the correct sequence number for more than one batch size.

W-17127106
## [](#1-0-23)1.0.23 **July 16, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.15.10
### Fixed Issues
Issue Resolution ID

The Checkpoint On Complete attribute action now occurs for the correct sequence number.

W-14633078
## [](#1-0-22)1.0.22 **May 9, 2024** # What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.15.10
## [](#1-0-21)1.0.21 **April 8, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.15.10
### Fixed Issues
Issue Resolution ID

The following libraries are upgraded to address reported security vulnerabilities:

  • The software.amazon.awssdk:sts library is upgraded to version 2.17.295.

  • The com.amazonaws:amazon-kinesis-producer library is upgraded to version 0.15.10.

  • The io.netty:netty-codec-http2 library is upgraded to version 4.1.108.Final.

  • The org.apache.commons:commons-compress library is upgraded to version 1.25.0.

  • The com.google.protobuf:protobuf-java library is upgraded to version 4.26.1.

  • The com.fasterxml.jackson.dataformat:jackson-dataformat-cbor library is upgraded to version 2.18.0.

  • The org.json:json library is upgraded to version 20240303.

  • The org.xerial.snappy:snappy-java library is upgraded to version 1.1.10.5.

W-15224652
## [](#1-0-20)1.0.20 **November 28, 2023** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue Resolution ID

Upgraded component io.netty : netty-codec-http2 from version 4.1.96.Final to 4.1.100.Final to address reported security vulnerabilities.

W-14462893

Upgraded component org.xerial.snappy : snappy-java from version 1.1.10.1 to 1.1.10.4 to address reported security vulnerabilities.

W-14462870

Upgraded component org.jetbrains.kotlin : kotlin-stdlib from version 1.3.50 to 1.6.0 to address reported security vulnerabilities.

W-14462891

Upgraded component org.apache.avro: avro from version 1.10.2 to 1.11.3 to address reported security vulnerabilities.

W-14462890

Upgraded component com.fasterxml.jackson.core : jackson-core to address reported security vulnerabilities.

W-14462884

Upgraded json library from version 20230227 to 20231013 to address reported security vulnerabilities.

W-14462877
## [](#1-0-19)1.0.19 **Aug 25, 2023** ### What’s New - Upgraded Guava version from 30.1.1-jre to 32.0.1-jre - Upgraded Snappy-java version to 1.1.10.1 - Upgraded Netty version from 4.1.91.Final to 4.1.96.Final - Upgraded Jackson Cbor version from 2.15.0 to 2.15.2 ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
## [](#1-0-18)1.0.18 **May 16, 2023** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.13.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665868
## [](#1-0-17)1.0.17 **April 18, 2023** ### What’s New - The org.json library is upgraded to version 20230227. - The io.netty library is upgraded to version 4.1.91.Final. - The org.apache.kafka library is upgraded to version 3.4.0. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
## [](#1-0-16)1.0.16 **December 13, 2022** ### What’s New - The com.google.protobuf library is upgraded to version 3.21.9. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue Resolution ID

The com.google.protobuf library is upgraded to version 3.21.9 to address reported security vulnerabilities.

W-12067085
## [](#1-0-15)1.0.15 **October 27, 2022** ### What’s New - The Jackson Databind library is updated to `com.fasterxml.jackson.core:jackson-databind:2.13.4.2`. - The `componentcom.google.protobuf : protobuf-java : 3.19.3` library is updated to `componentcom.google.protobuf : protobuf-java : 3.19.6`. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

Query parameters are no longer duplicated in the URL.

W-11851515

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.13.2.2 to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to fix reported security vulnerabilities.

W-11853413

The componentcom.google.protobuf : protobuf-java : 3.19.3 library is upgraded to componentcom.google.protobuf : protobuf-java : 3.19.6 to fix reported security vulnerabilities.

W-11872197
## [](#1-0-14)1.0.14 **September 27, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

The org.apache.kafka library is upgraded to version 2.8.2 to address reported security vulnerabilities.

W-11802570
## [](#1-0-13)1.0.13 **June 2, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Netty Common library from io.netty:netty-common:4.1.71.Final to io.netty:netty-common:4.1.77.Final.

W-11124602

Fixed reported security vulnerabilities by upgrading the JSON library from org.json:json:20160810 to org.json:json:20180130.

W-11202572
## [](#1-0-12)1.0.12 **May 4, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

The connector now automatically refreshes the role session when the role session expires.

W-10995998
## [](#1-0-11)1.0.11 **April 7, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920490
## [](#1-0-10)1.0.10 **January 31, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.10

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

Upgraded the protobuf-java library.

CONN-9911

Upgraded the jackson-databind library.

CONN-9819
## [](#1-0-9)1.0.9 **December 20, 2021** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.4

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

Upgraded the io.netty.codec library.

CONN-9551
## [](#1-0-8)1.0.8 **October 4, 2021** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.4

Amazon-Kinesis-Producer

0.14.6
### Fixed Issues
Issue ID

Removed the vulnerabilities caused by the Kafka library.

CONN-8944
## [](#1-0-7)1.0.7 **July 19, 2021** ### [](#compatibility-26)Compatibility Amazon Kinesis Data Streams Connector 1.0.7 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.4

Amazon-Kinesis-Producer

0.14.6
### [](#fixed-issues-22)Fixed Issues - Stopped using a vulnerable dependency. (CONN-8583) ## [](#1-0-6)1.0.6 **July 13, 2021** ### [](#compatibility-27)Compatibility Amazon Kinesis Data Streams Connector 1.0.6 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.4

Amazon-Kinesis-Producer

0.14.6
### [](#fixed-issues-23)Fixed Issues - Stopped using a vulnerable dependency. (CONN-8525) ## [](#1-0-5)1.0.5 **April 15, 2021** ### [](#compatibility-28)Compatibility Amazon Kinesis Data Streams Connector 1.0.5 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.4

Amazon-Kinesis-Producer

0.14.6
### [](#fixed-issues-24)Fixed Issues - Updated the versions of the netty-codec dependencies. ## [](#1-0-4)1.0.4 **March 17, 2021** ### [](#compatibility-29)Compatibility Amazon Kinesis Data Streams Connector 1.0.4 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.4

Amazon-Kinesis-Producer

0.14.6
### [](#fixed-issues-25)Fixed Issues - Removed vulnerable transitive dependencies. ## [](#1-0-3)1.0.3 **March 2, 2021** ### [](#compatibility-30)Compatibility Amazon Kinesis Data Streams Connector 1.0.3 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.3

Amazon-Kinesis-Producer

0.14.4
Amazon Kineses Data Streams Connector doesn’t support Windows because it uses the Kinesis Producer Library (KPL), which deprecated Windows support starting in version v0.14.0. ### [](#fixed-issues-26)Fixed Issues - An expired role session wasn’t automatically renewed. (SE-19719) ## [](#1-0-2)1.0.2 **February 16, 2021** ### [](#compatibility-31)Compatibility Amazon Kinesis Data Streams Connector 1.0.2 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11

Amazon-Kinesis-Client

2.3.3

Amazon-Kinesis-Producer

0.14.4
### [](#fixed-issues-27)Fixed Issues - Updated the versions of multiple dependencies. (CONN-7710, CONN-7713) ## [](#1-0-1)1.0.1 **February 11, 2021** ### [](#compatibility-32)Compatibility Amazon Kinesis Data Streams Connector 1.0.1 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11
### [](#fixed-issues-28)Fixed Issues - Removed the vulnerabilities caused by the Jackson Dataformat: CBOR library (CONN-7656). ## [](#1-0-0)1.0.0 **November 13, 2020** ### [](#compatibility-33)Compatibility Amazon Kinesis Data Streams Connector 1.0.0 is compatible with:
Software Version

Mule

4.3.0 and later

OpenJDK

8 or 11
### [](#features)Features New connector ### [](#known-issues)Known Issues - None ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon Lambda Connector Release Notes Support Category: Select Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) enables you to execute AWS Lambda operations within your Mule flows. You can then use the response of the Lambda operation to process another Mule flow as needed. Guide: [Amazon Lambda Connector User Guide](https://docs.mulesoft.com/amazon-lambda-connector/latest/) ## [](#1-2-4)1.2.4 **October 16, 2026** ### Compatibility
Software Version

Mule runtime

4.2.1 and later

OpenJDK

8, 11, and 17

AWS SDK for Java

2.55.2

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.55.2.

  • The netty library is upgraded to version 4.2.18.Final.

  • The commons-codec library is upgraded to version 1.23.0.

  • The jackson library is upgraded to version 2.22.3.

  • The guava library is upgraded to version 33.7.2-jre.

W-24116023
## [](#1-2-3)1.2.3 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime

4.2.1 and later

OpenJDK

8, 11, and 17

AWS SDK for Java

2.51.1

AWS Lambda API

2015-03-31
## [](#1-2-2)1.2.2 **August 10, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime

4.2.1 and later

OpenJDK

8, 11, and 17

AWS SDK for Java

2.51.1

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.51.1.

  • The json library is upgraded to version 20260719.

  • The Apache Commons Codec library is upgraded to version 1.22.1.

W-23441648
## [](#1-2-1)1.2.1 **May 25, 2026** ### Compatibility
Software Version

Mule runtime

4.2.1 and later

OpenJDK

8, 11, and 17

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

HTTP 403 InvalidSignatureException errors no longer occur when authenticating with AWS Lambda on Windows JVMs. AWS Signature Version 4 canonical requests now use specification-compliant line feeds (\n) across all operating systems.

W-22172040

AMAZON-LAMBDA:CONNECTIVITY errors no longer occur when you enable the Try Default AWSCredentials Provider Chain field while running applications on CloudHub 2.0. The default AWS credentials provider chain now automatically refreshes expired Web Identity-based credentials.

W-22444662

403 Forbidden errors no longer occur when you use the Try Default AWSCredentials Provider Chain field along with Role ARN. The default AWS credentials provider chain now correctly propagates the session token from temporary credentials when assuming a role.

W-22154803
## [](#1-2-0)1.2.0 **March 1, 2026** ### What’s New - Amazon Lambda Connector now supports passing an external ID in Role-based authentication. - Amazon Lambda Connector now includes the new **Try Default AWSCredentials Provider Chain** field to obtain credentials from the AWS environment. ### Compatibility
Software Version

Mule runtime

4.2.1 and later

OpenJDK

8, 11, and 17

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

These libraries are included to address reported security vulnerabilities:

  • The commons-codec library is added at version 1.21.0.

  • The commons-io library is added at version 2.21.0.

W-19965899
## [](#1-1-1)1.1.1 **July 2, 2024** ### What’s New - The connector can now set a custom service and STS role endpoint. For example, when using a VPC endpoint. ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8, 11, and 17

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

The connector no longer throws an error when used in conjunction with Stripe Connector.

W-15283306
## [](#1-0-8)1.0.8 **May 10, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8, 11, and 17

AWS Lambda API

2015-03-31
## [](#1-0-7)1.0.7 **November 3, 2023** ### What’s New - The org.json library is upgraded to version 20231013. ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 and 11

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

The org.json library is upgraded to version 20230227 to address reported security vulnerabilities.

W-12665446
## [](#1-0-6)1.0.6 **June 14, 2023** ### What’s New - The org.json library is upgraded to version 20230227. ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 and 11

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

The org.json library is upgraded to version 20230227 and the log4j dependency is upgraded to 2.17.1 to address reported security vulnerabilities.

W-14413948
## [](#1-0-5)1.0.5 **April 24, 2023** ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 and 11

AWS Lambda API

2015-03-31
### Fixed Issues
Issue Resolution ID

The connector no longer returns a request signature mismatch issue when using the full function ARN (Amazon Resource Name) when invoking a function.

W-12386452
## [](#1-0-4)1.0.4 **January 10, 2022** ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 and 11

AWS Lambda API

2015-03-31
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9879
## [](#1-0-3)1.0.3 **December 21, 2021** ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 and 11

AWS Lambda API

2015-03-31
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9657
## [](#1-0-2)1.0.2 **December 14, 2021** ### Compatibility
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 and 11

AWS Lambda API

2015-03-31
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9562

The connector returned an InvalidSignatureException error since the date value in X-Amz-Date accepted the UTC timezone while the date value in Credential scope accepted the application’s system date. Now, the date value in Credential scope accepts the UTC timezone.

SE-23669
## [](#1-0-1)1.0.1 **July 13, 2021** ### [](#compatibility-14)Compatibility Amazon Lambda Connector is compatible with these software versions:
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 or 11

AWS Lambda API

2015-03-31
### [](#fixed-issues-12)Fixed Issues - Added a missing region to the Amazon STS URL address. (SE-21780) ## [](#1-0-0)1.0.0 **June 3, 2021** ### [](#compatibility-15)Compatibility Amazon Lambda Connector is compatible with these software versions:
Software Version

Mule Runtime

4.2.1 and later

OpenJDK

8 or 11

AWS Lambda API

2015-03-31
### [](#features)Features New connector. For a list of supported configurations and operations, see the Amazon Lambda Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon RDS Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Amazon Relational Database Service (Amazon RDS Connector) makes it easy to set up, operate, and scale a relational database in the cloud. The Amazon RDS Connector provides connectivity to the Amazon Relational Database Service (Amazon RDS) API, enabling you to interface with Amazon RDS to provide cost-efficient and resizable capacity while automating time-consuming administration tasks such as hardware provisioning, database setup, patching, and backups. Starting with v.1.0.0, the RDS connector is licensed commercially with Anypoint Platform as with other Select connectors. Guide: [Amazon RDS Connector](https://docs.mulesoft.com/amazon-rds-connector/latest/) Reference: [Amazon RDS Connector Reference](https://docs.mulesoft.com/amazon-rds-connector/latest/amazon-rds-connector-reference) ## [](#1-4-3)1.4.3 **July 7, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v2.46.10

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-databind library is upgraded to version 2.22.0 to address reported security vulnerabilities.

W-23286191
## [](#1-4-2)1.4.2 **June 26, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v2.46.10

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.46.10.

  • The netty-codec, netty-codec-http, netty-codec-http2 and netty-handler libraries are upgraded to version 4.1.135.Final.

  • The jackson-databind library is upgraded to version 2.21.1.

  • The model.mapper library is upgraded to version 3.2.6.

W-22899692
## [](#1-4-1)1.4.1 **April 21, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v2.40.9

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly supports separate configuration of custom STS and custom service endpoints. This ensures that role-based authentication succeeds in private network environments and no longer fails with a 404 error when both endpoints are used.

W-22040640

The AWS SDK dependency now excludes the netty-codec-http and netty-codec-http2 libraries, and AWS STS dependency now excludes the jackson-core library to address reported security vulnerabilities.

W-21919400
## [](#1-4-0)1.4.0 **December 21, 2025** ### What’s New - Amazon RDS Connector now supports passing an external ID in Role-based authentication. - The AWS SDK version is upgraded from 2.33.4 to 2.40.9. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v2.40.9

OpenJDK

8, 11, and 17
## [](#1-3-12)1.3.12 **September 19, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v2.33.4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Dozer Mapper library is replaced by the Model Mapper library.

  • The Jackson library is upgraded to version 2.19.0.

  • The commons-lang3 library is upgraded to version 3.18.0.

W-19578770

The AWS SDK version is upgraded from 2.31.16 to 2.33.4.

W-19578770
## [](#1-3-11)1.3.11 **September 30, 2024** ### What’s New - The AWS SDK version is upgraded from 1.12.686 to 2.20.153. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v2.20.153

OpenJDK

8, 11, and 17
## [](#1-3-10)1.3.10 **May 8, 2024** ### What’s New - This release includes only non-user-impacting changes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.12.686

OpenJDK

8, 11, and 17
## [](#1-3-9)1.3.9 **April 29, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.12.686

OpenJDK

8, 11, and 17
## [](#1-3-8)1.3.8 **June 14, 2023** ### What’s New - The `com.fasterxml.jackson.core:jackson-databind:2.15.0` dependency is upgraded to `com.fasterxml.jackson.core:jackson-databind:2.15.0`. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.946

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core:jackson-databind:2.15.0 dependency is upgraded to com.fasterxml.jackson.core:jackson-databind:2.15.0 to fix a security vulnerability.

W-12665854
## [](#1-3-7)1.3.7 **October 28, 2022** ### What’s New - The `com.fasterxml.jackson.core:jackson-databind:2.13.2.2` dependency is upgraded to `com.fasterxml.jackson.core:jackson-databind:2.13.4.2`. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.946

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core:jackson-databind:2.13.2.2 dependency is upgraded to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to fix a security vulnerability.

W-11853418
## [](#1-3-6)1.3.6 **April 11, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.946

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920472
## [](#1-3-5)1.3.5 **January 10, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.946

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9807
## [](#1-3-4)1.3.4 **September 9, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.946

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The exception handler incorrectly wrapped errors to the MULE:ANY error type. Now, errors occur without any modification or wrapping.

CONN-8787
## [](#1-3-3)1.3.3 **February 11, 2021** ### [](#compatibility-14)Compatibility Amazon RDS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.946

OpenJDK

8 and 11
### [](#features)Features - Upgraded the Amazon SDK for Java dependency to version 1.11.946. ### [](#fixed-issues-10)Fixed Issues - Removed the vulnerabilities caused by the Jackson Dataformat: CBOR library (CONN-7656). ## [](#1-3-2)1.3.2 **October 23, 2020** ### [](#compatibility-15)Compatibility Amazon RDS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.816

OpenJDK

8 and 11
### [](#features-2)Features Multiple libraries have been updated to the latest version. ### [](#fixed-issues-11)Fixed Issues None ## [](#1-3-1)1.3.1 **July 23, 2020** ### [](#compatibility-16)Compatibility Amazon RDS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.816

OpenJDK

8 and 11
### [](#features-3)Features Upgraded AWS Java dependency to version 1.11.816. ### [](#fixed-issues-12)Fixed Issues None ## [](#1-3-0)1.3.0 **January 23, 2020** ### [](#compatibility-17)Compatibility The Amazon RDS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for RDS

v1.11.649

Java

1.8.0_x
### [](#features-4)Features Implemented support for TLS configuration. (CONN-3628) ### [](#fixed-issues-13)Fixed Issues Added missing sessionToken field into the configuration (SE-14206) ## [](#1-2-0)1.2.0 **April 16, 2019** Release notes for version 1.2.0 of the Amazon RDS connector. ### [](#compatibility-18)Compatibility The Amazon RDS Connector is compatible with:
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for RDS

v1.11.515

Java

1.8 and later
### [](#features-5)Features - Added support for connecting to new AWS region endpoints. ## [](#1-1-0)1.1.0 **February 21, 2018** Release notes for version 1.1.0 of the Amazon RDS connector. ### [](#compatibility-19)Compatibility The Amazon RDS Connector is compatible with:

Application/Service

Version

Mule

4.1.0 and later

Amazon Java SDK for RDS

v1.11.172

Java

1.8 or higher
### [](#fixed-issues-14)Fixed Issues AWS connectors shared a common library for the supported region endpoints that caused an issue when two different AWS connectors were used in a Mule app. This version fixes this issue. ## [](#1-0-0)1.0.0 **November 18, 2017** Release notes for version 1.0.0 of the Amazon RDS connector. ### [](#compatibility-20)Compatibility The Amazon RDS Connector is compatible with:

Application/Service

Version

Mule

4.0.0 and later

Amazon Java SDK for RDS

v1.11.172

Java

1.8 or higher
### [](#features-6)Features - Built with the new AnyPoint SDK (Extensions Framework) v1.0.0-rc-SNAPSHOT - Built with AWS SDK v1.11.172 - Support for Temporary Credentials - A checkbox named Try Default AWS Credentials Provider Chain has been added to the Global Configuration Elements. If selected, the connector will first try to obtain the credentials from an AWS environment. - Support for Retry Policy - The connector can be configured with a Reconnection strategy that is provided in the Advanced tab The following operations are supported: Database Instances: - CreateDBInstance - CreateDBInstanceReadReplica - DeleteDBInstance - DescribeDBInstances - ModifyDBInstance - RebootDBInstance - RestoreDBInstanceFromDBSnapshot - RestoreDBInstanceToPointInTime - StartDBInstance - StopDBInstance Database Snapshots: - CreateDBSnapshot - DeleteDBSnapshot - DescribeDBSnapshots - ModifyDBSnapshot Events: - DescribeEvents Reserved Database Instances: - DescribeReservedDBInstances - DescribeReservedDBInstancesOfferings - PurchaseReservedDBInstancesOffering ### [](#fixed-issues-15)Fixed Issues Initial version. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon Redshift Connector Release Notes Support Category: Select Amazon Redshift is a fast, fully managed cloud data warehouse that makes it simple and cost-effective to analyze all your data using standard SQL and your existing Business Intelligence (BI) tools. Anypoint Connector for Amazon Redshift enables you to securely read data from, or write data to Amazon Redshift. Amazon Redshift objects can be used as sources and targets in data synchronization tasks, mappings, and so on. The connector enables you to move data from any data source to Amazon Redshift. Guide: [Amazon Redshift Connector User Guide](https://docs.mulesoft.com/amazon-redshift-connector/latest/) ## [](#1-2-4)1.2.4 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.50.3

JDBC for Amazon Redshift

v2.2.7
## [](#1-2-3)1.2.3 **August 5, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.50.3

JDBC for Amazon Redshift

v2.2.7
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Amazon Java SDK is upgraded to version 2.50.3.

  • The jackson library is upgraded to version 2.22.1.

  • The netty library is upgraded to version 4.2.16.Final.

  • The log4j library is upgraded to version 2.26.1.

W-23657986
## [](#1-2-2)1.2.2 **June 28, 2026** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.40.16

JDBC for Amazon Redshift

v2.2.7
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities and improve stability:

  • The jackson and jackson-core libraries are upgraded to version 2.22.0.

  • The log4j library is upgraded to version 2.26.0.

  • The netty library is upgraded to version 4.2.15.Final.

  • The modelmapper library is upgraded to version 3.2.6.

  • Amazon Redshift JDBC driver version is upgraded from 2.1.0.8 to 2.2.7.

W-22899476
## [](#1-2-1)1.2.1 **April 19, 2026** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.40.16

JDBC for Amazon Redshift

v2.1.0.8
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The netty library is upgraded to version 4.2.12.Final.

  • The log4j library is upgraded to version 2.25.4.

W-21919400
## [](#1-2-0)1.2.0 **January 15, 2026** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.40.16

JDBC for Amazon Redshift

v2.1.0.8
### Fixed Issues
Issue Resolution ID

Added general security fixes.

W-20787440
## [](#1-1-2)1.1.2 **January 6, 2026** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.40.16

JDBC for Amazon Redshift

v2.1.0.8
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.40.16.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The netty library is upgraded to version 4.2.9.Final.

W-19578805
## [](#1-1-1)1.1.1 **May 13, 2025** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.31.16

JDBC for Amazon Redshift

v2.1.0.8
### Fixed Issues
Issue Resolution ID

The Amazon Java SDK is upgraded to version 2.31.16.

W-18242119

The mule-db-client dependency is upgraded to version 1.6.18 to address reported security vulnerabilities.

W-18366828
## [](#1-1-0)1.1.0 **February 18, 2025** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.16.44

JDBC for Amazon Redshift

v2.1.0.8
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-16957755

The IAM connection type now includes the optional Custom STS Endpoint field.

W-15672469
## [](#1-0-10)1.0.10 **March 21, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Amazon Java SDK for Redshift

v2.16.44

JDBC for Amazon Redshift

v2.1.0.26
### Fixed Issues
Issue Resolution ID

Amazon Redshift Connector now supports Java 17.

W-15194361

Amazon Redshift JDBC driver version is upgraded from 2.1.0.1 to 2.1.0.26.

W-15194361
## [](#1-0-9)1.0.9 **January 29, 2024** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11

Amazon Java SDK for Redshift

v2.16.44

JDBC for Amazon Redshift

v2.1.0.1
### Fixed Issues
Issue Resolution ID

The netty-codec-http2 library is upgraded to version 4.1.100.Final to address reported security vulnerabilities.

W-14462872

The jackson-core library is upgraded to version 2.15.2 to address reported security vulnerabilities.

W-14462878
## [](#1-0-8)1.0.8 **June 7, 2023** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11

Amazon Java SDK for Redshift

v2.16.44

JDBC for Amazon Redshift

v2.1.0.1
### Fixed Issues
Issue Resolution ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to com.fasterxml.jackson.core:jackson-databind:2.15.0.

W-12665858

The Netty Code library is upgraded from netty-codec:4.1.77.Final to netty-codec:4.1.92.Final.

W-12665453
## [](#1-0-7)1.0.7 **October 25, 2022** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11

Amazon Java SDK for redshift

v2.16.44

JDBC for Amazon redshift

v2.1.0.1
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.13.2.2 to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to fix reported security vulnerabilities.

W-11853411
## [](#1-0-6)1.0.6 **October 9, 2022** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### Fixed Issues
Issue ID

The domain name of the endpoint for available China regions is now correct.

W-11796745
## [](#1-0-5)1.0.5 **June 2, 2022** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Netty Common library from io.netty:netty-common:4.1.71.Final to io.netty:netty-common:4.1.77.Final.

W-11124603
## [](#1-0-4)1.0.4 **April 6, 2022** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920455
## [](#1-0-3)1.0.3 **January 11, 2022** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9811
## [](#1-0-2)1.0.2 **December 15, 2021** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### Fixed Issues
Issue ID

Upgraded the io.netty.codec library.

CONN-9556

Upgraded library dependencies.

N/A
## [](#1-0-1)1.0.1 **July 19, 2021** ### [](#compatibility-18)Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### [](#fixed-issues-17)Fixed Issues - Stopped using a vulnerable dependency. (CONN-8525) - Fixed a class loading issue. (CONN-8387) ## [](#1-0-0)1.0.0 **May 6, 2021** ### [](#compatibility-19)Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### [](#features)Features New connector. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon S3 Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Amazon S3 (S3 Connector) provides connectivity to the Amazon S3 API, enabling you to interface with Amazon S3 to store objects, download, use data with other AWS services, and to build applications that call for cloud storage. Instant access to the Amazon S3 API enables seamless integrations between Amazon S3 and other databases, CMS applications such as Drupal, and CRM applications such as Salesforce. Starting with v.4.0.0, the S3 Connector is licensed commercially with Anypoint Platform as with other Select connectors. Prior versions remain freely available to the community. Guide: [Amazon S3 Connector](https://docs.mulesoft.com/amazon-s3-connector/latest/) Reference: [Amazon S3 Connector Reference](https://docs.mulesoft.com/amazon-s3-connector/latest/amazon-s3-connector-reference) For migration information, see [Amazon S3 - Upgrade and Migrate](https://docs.mulesoft.com/amazon-s3-connector/latest/amazon-s3-connector-upgrade-migrate) ## [](#8-0-10)8.0.10 **September 29, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.55.6
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.55.6.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.3.

  • The io.netty libraries are upgraded to version 4.2.18.Final.

W-24259548, W-3300013
## [](#8-0-9)8.0.9 **September 25, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.53.2
### Fixed Issues
Issue Resolution ID

The connector no longer leaks AWS resources when an Amazon S3 connection is invalidated, the application is redeployed, or the configuration is reloaded. On long-running deployments, and on IRSA or EKS Web Identity workloads, credential resolution no longer degrades until the Mule worker is restarted.

W-23993014

The Get Object operation no longer logs Broken pipe warnings or stalls the application when a flow reads only object attributes and does not consume the payload.

W-24187876
## [](#8-0-8)8.0.8 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.53.2
## [](#8-0-7)8.0.7 **August 20, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.53.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.53.2.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.2.

  • The io.netty libraries are upgraded to version 4.2.17.Final.

  • The commons-io:commons-io library is upgraded to version 2.22.0.

  • The org.projectlombok:lombok library is upgraded to version 1.18.46.

W-23441606
## [](#8-0-6)8.0.6 **August 7, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.49.1
### Fixed Issues
Issue Resolution ID

S3:UNAUTHORIZED errors and NoClassDefFoundError: jdk/net/Sockets exceptions no longer occur on CloudHub 2.0 with Java 17 when using role-based IAM authentication. Apache HttpClient 4 is now restored as the default synchronous HTTP client.

W-23468996

The Put Object operation no longer fails intermittently with an S3:REQUEST_TIMEOUT error when the request payload is a deferred DataWeave value.

W-23406817

These libraries are upgraded:

  • The AWS SDK version is upgraded to 2.49.1.

  • The commons-codec library is upgraded to version 1.22.1.

W-3300013
## [](#8-0-5)8.0.5 **July 21, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.47.1
### Fixed Issues
Issue Resolution ID

The Select Object Content operation now correctly refreshes role-based credentials and retries the request upon STS session token expiry, and no longer fails with the S3:BAD_REQUEST error. The connector also no longer leaks temporary files and file descriptors on failed requests, which previously could cause resource exhaustion.

W-23168925

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to version 2.47.1.

  • The jackson-databind library is upgraded to version 2.22.1.

  • The netty library is upgraded to version 4.2.16-Final.

W-23168925
## [](#8-0-4)8.0.4 **June 30, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.46.17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to version 2.46.17.

  • The jackson-databind library is upgraded to version 2.22.0.

  • The model-mapper library is upgraded to 3.2.6.

  • The netty library is upgraded to version 4.2.15-Final.

W-22899430, W-22943408
## [](#8-0-3)8.0.3 **May 28, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.41.10
### Fixed Issues
Issue Resolution ID

The Head Object operation now correctly refreshes role-based credentials upon session token expiry. Previously, because Amazon S3 returns a body-less HTTP 400 Bad Request response for HEAD operations, the connector failed to recognize the token expiry, causing subsequent Head Object operations to continuously fail until a different operation triggered a refresh.

W-20190508

The connector now provides diagnostic logs for the credential refresh path and asynchronous execution paths. These logs allow you to monitor latency and retry behavior during security token updates in production environments.

W-18826515
## [](#8-0-2)8.0.2 **March 8, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.41.10
### Fixed Issues
Issue Resolution ID

The Get Object operation now prevents file descriptor leaks when Amazon S3 returns 404 (NoSuchKey) error responses. This fix ensures that resources are properly released during exception handling, preventing java.io.IOException: Too many open files errors under high request volumes.

W-21349199
## [](#8-0-1)8.0.1 **January 23, 2026** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.41.10
### Fixed Issues
Issue Resolution ID

The tooltip for the User metadatas field in the Put Object operation is now updated to clarify that the input for this field in Expression mode supports only inline DataWeave scripts and doesn’t support structured or multiline DataWeave scripts, because they cause XML parsing errors during deployment.

W-20954680

The AWS SDK version is upgraded to 2.41.10.

W-20954680
## [](#8-0-0)8.0.0 **November 15, 2025** ### What’s New - As per AWS updates, the **Display Name** field has been deprecated and is no longer supported in the **Owner** and **Grantee** object types. Review your flows for a dependency on **Display Name** in these object types and make updates if required. ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.35.3
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.35.3.

  • The netty-common library is upgraded to version 4.2.5-Final.

W-20170183
## [](#7-2-0)7.2.0 **September 4, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
### Fixed Issues
Issue Resolution ID

The List Multipart Parts operation response now includes the new E Tag and Last Modified fields, which return their respective values.

W-19455506
## [](#7-1-1)7.1.1 **August 15, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
### Fixed Issues
Issue Resolution ID

In the List Objects operation, the Owner field now returns the owner details instead of null.

W-17974123
## [](#7-1-0)7.1.0 **May 28, 2025** ### What’s New - Added the **Matching ETag** and **Not matching ETag** parameters to the **Complete Multipart Upload** and **Put Object** operations, which support conditional writes. ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
## [](#7-0-6)7.0.6 **May 13, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
### Fixed Issues
Issue Resolution ID

The Create Object Presigned Url operation now refreshes the token correctly before generating the presigned URL.

W-18232212
## [](#7-0-5)7.0.5 **April 22, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
### Fixed Issues
Issue Resolution ID

The Put Object operation now uploads the full payload with streaming on.

W-18313462
## [](#7-0-4)7.0.4 **April 13, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
### Fixed Issues
Issue Resolution ID

The AWS SDK is now upgraded to version 2.31.16.

W-18242119
## [](#7-0-3)7.0.3 **March 21, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.28.28
### Fixed Issues
Issue Resolution ID

Attributes from the model objects are now accessible in DataWeave expressions when running on Java 17.

W-17964937
## [](#7-0-2)7.0.2 **March 11, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.28.28
### Fixed Issues
Issue Resolution ID

The connector no longer throws a Read end dead error when downloading a large file or object.

W-17587788
## [](#7-0-1)7.0.1 **February 11, 2025** ### Compatibility
Software Version

Mule

4.1.1 or later

OpenJDK

8, 11, and 17

AWS SDK

2.28.28
### Fixed Issues
Issue Resolution ID

The Copy Object operation now contains the new Server Side Encryption, Sse Customer Key, Sse Kms Key Id, Sse Customer Key MD5, and Sse Customer Algorithm fields.

W-17036072

The f(x) function for the ARN and External ID fields in the Role configuration is now available.

W-17335242

Attributes from the response objects are now accessible in DataWeave expressions when running on Java 17.

W-17338643
## [](#7-0-0)7.0.0 **November 13, 2024** ### What’s New - The AWS SDK is now upgraded to version 2.28.28. ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.28.28
## [](#6-3-16)6.3.16 **October 15, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

Amazon S3 Connector now works correctly after the Mule app sits idle for a period of time on a 0.1 vCore machine on CloudHub 2.0.

W-16921672

The Amazon S3 token refresh now works as expected and the requests are no longer stuck.

W-16612349
## [](#6-3-15)6.3.15 **September 30, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

The connector now has the correct default SQS queue naming.

W-14549491

The connector performance is now improved for low-core machines.

W-16048632
## [](#6-3-14)6.3.14 **August 22, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

You can now create a Role-based connection with tags.

W-16468150
## [](#6-3-13)6.3.13 **August 13, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

All operations that use buckets now throw the NO_SUCH_BUCKET error when specifying a bucket that doesn’t exist.

W-14025894, W-15309594
## [](#6-3-12)6.3.12 **July 8, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

The Get Object operation response is now serialized.

W-15106813
## [](#6-3-11)6.3.11 **July 4, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

The ContentEncoding is now properly injected into the PUT object.

W-16109941

The Copy Object operation no longer faces metadata update issues.

W-15933607
## [](#6-3-10)6.3.10 **June 13, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

The connector now uses a custom AWS async thread pool to scale up and down dynamically based on the load.

W-15310212
## [](#6-3-9)6.3.9 **June 11, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

The connector now supports Content-MD5 and Content-Type headers for creating presigned URLs.

W-15549086

The connector now supports configuring maximum connections for S3 connection.

W-15859450

The token refresh now works correctly.

W-15689287
## [](#6-3-8)6.3.8 **January 31, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

Old Netty dependencies are excluded to address the CVE-2023-44487(7.5) and CVE-2022-41881(7.5) reported security vulnerabilities.

W-14756310
## [](#6-3-7)6.3.7 **January 17, 2024** ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

The connector now handles the exception The provided token is malformed or otherwise invalid and attempts to reconnect to the service.

W-14414108
## [](#6-3-6)6.3.6 **January 10, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.3.0 or later

OpenJDK

8, 11, and 17

AWS SDK

2.18.31
## [](#6-3-5)6.3.5 **January 4, 2024** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.18.31

OpenJDK

8 and 11

AWS SDK

2.18.31
### Fixed Issues
Issue Resolution ID

The Netty dependencies are upgraded to version 4.1.100.Final to address reported security vulnerabilities.

W-14625053
## [](#6-3-4)6.3.4 **November 28, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.18.31

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Get Object operation now returns response attributes.

W-14006215

Internal dependencies are upgraded.

W-14547619
## [](#6-3-3)6.3.3 **November 6, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.18.31

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now handles the invalid token exception correctly.

W-14414108
## [](#6-3-2)6.3.2 **September 20, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.18.31

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Put Object operation now uploads empty files or content with zero bytes.

W-13942501

The connector now handles the invalid token exception correctly.

W-14033096
## [](#6-3-1)6.3.1 **August 29, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.18.31

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Select Object Content operation now works correctly when the JSON field is empty.

W-12108071
## [](#6-3-0)6.3.0 **June 23, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.18.31

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Put Object operation now contains the new Server Side Encryption and Sse Kms Key Id fields.

W-13514438
## [](#6-2-1)6.2.1 **June 22, 2023**
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.18.31

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Upload part operation now uploads a part in a multipart upload correctly.

W-13533222
## [](#6-2-0)6.2.0 **June 1, 2023** ### What’s New - You can now use the new **Try Default AWSCredentials Provider Chain** field to obtain credentials from the AWS environment. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
## [](#6-1-4)6.1.4 **May 24, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.14.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665857

Upgraded the Netty Codec library from io.netty:netty-codec:4.1.72.Final to io.netty:netty-codec:4.1.92.Final.

W-12665444
## [](#6-1-3)6.1.3 **April 18, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Amazon S3 Connector no longer fails with Checksum error when downloading large files with low bandwidth.

W-12630308
## [](#6-1-2)6.1.2 **April 14, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Amazon S3 Connector no longer creates a build-up of threads.

W-12637960
## [](#6-1-1)6.1.1 **February 22, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Amazon S3 Connector incorrectly threw the MULE_UNKNOWN error type. Now, the connector throws the REQUEST_TIMEOUT error type.

W-12521306
## [](#6-1-0)6.1.0 **January 31, 2023** ### What’s New - The **Create Object Presigned Url** operation is once again available. - The **Content MD5** field is once again available for the **Put Object**, **Put Object ACL**, and **Upload Part** operations. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
## [](#6-0-3)6.0.3 **November 22, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Streaming capabilities for the Get Object and Put Object operations are now improved to avoid memory leaks with large files.

W-11900293
## [](#6-0-2)6.0.2 **October 26, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The On New Object and On Deleted Object sources now initialize as expected.

W-11697870

The connector no longer duplicates query parameters in HTTP requests to AWS.

W-11754732

The com.fasterxml.jackson.core:jackson-databind:2.13.2.2 is updated to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to address reported security vulnerabilities.

W-11853408
## [](#6-0-1)6.0.1 **August 10, 2022** ### What’s New - The netty-io:netty-handler dependency is now excluded to address a security vulnerability. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The netty-io:netty-handler dependency is now excluded to address a security vulnerability.

W-11515673
## [](#6-0-0)6.0.0 **August 1, 2022** ### What’s New - This connector is now migrated to AWS SDK for Java 2.x. For more information, refer to [Upgrading and Migrating Amazon S3 Connector to Version 6.x](https://docs.mulesoft.com/amazon-s3-connector/latest/amazon-s3-connector-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.3.0 or later

AWS SDK for Java

2.17.148

OpenJDK

8 and 11
## [](#5-8-4)5.8.4 **August 9, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.12.261

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Custom STS Endpoint field is now accessible in the UI and in the XML.

W-11507468
## [](#5-8-3)5.8.3 **August 4, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.12.261

OpenJDK

8 and 11
### What’s New - AWS SDK version is upgraded to `1.12.261` to address a reported security vulnerability. ### Fixed Issues
Issue ID

AWS SDK version is upgraded to 1.12.261 to address a reported security vulnerability.

W-11454665

The Get Object operation now processes large files successfully.

W-11469263

AWS error types with spaces in the name no longer cause MULE:UNKNOWN errors because they are now parsed correctly.

W-11538480
## [](#5-8-2)5.8.2 **July 13, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The On New Object source now works as expected when specifying Bucket Name as bucketname/foldername.

W-11307008
## [](#5-8-1)5.8.1 **April 7, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920484
## [](#5-8-0)5.8.0 **January 17, 2022** ### What’s New - Added the **Notification Queue Name** and **Notification Configuration Name** parameters in the **On Deleted Object** and **On New Object** sources, which support custom notification configuration specified in the S3 console. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
## [](#5-7-4)5.7.4 **January 11, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9809
## [](#5-7-3)5.7.3 **November 15, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9251
## [](#5-7-2)5.7.2 **September 9, 2021** ### Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The exception handler incorrectly wrapped errors to the MULE:ANY error type. Now, errors occur without any modification or wrapping.

CONN-8787
## [](#5-7-1)5.7.1 **August 10, 2021** ### [](#compatibility-57)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
### [](#fixed-issues-50)Fixed Issues - Using a bucket name with the `/` character on the **On New Object** source threw an error. (SE-22096) ## [](#5-7-0)5.7.0 **March 30, 2021** ### [](#compatibility-58)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.969

OpenJDK

8 and 11
### [](#features)Features - Added support for custom domain endpoints to provide Amazon Virtual Private Cloud (VPC) feature utilization. - Upgraded the Amazon SDK for Java dependency to version 1.11.969. ### [](#fixed-issues-51)Fixed Issues - None ### [](#known-issues)Known Issues - None ## [](#5-6-6)5.6.6 **February 11, 2021** ### [](#compatibility-59)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.946

OpenJDK

8 and 11
### [](#features-2)Features Upgraded the Amazon SDK for Java dependency to version 1.11.946. ### [](#fixed-issues-52)Fixed Issues - Fixed the issue that caused excessive warnings in logs about duplicate dependencies during connector initialization in Anypoint Studio. (SE-19197) - Removed the vulnerabilities caused by the Jackson Dataformat: CBOR library. (CONN-7656) ### [](#known-issues-2)Known Issues - None ## [](#5-6-5)5.6.5 **Januray 27, 2021** ### [](#compatibility-60)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.816

OpenJDK

8 and 11
### [](#features-3)Features - None ### [](#fixed-issues-53)Fixed Issues - The `Resetting to invalid mark` error message was not descriptive. (SE-19202) - The reconnection strategy did not work properly for some S3 operations. - The List Objects operation failed with an `AuthorizationHeaderMalformed` error. (SE-19271) ### [](#known-issues-3)Known Issues - None ## [](#5-6-4)5.6.4 **October 29, 2020** ### [](#compatibility-61)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.816

OpenJDK

8 and 11
### [](#features-4)Features - None ### [](#fixed-issues-54)Fixed Issues - When using the **Upload Part** operation, some of the uploads failed with the error `Resetting to invalid mark`. (SE-18217) ### [](#known-issues-4)Known Issues - The provided fix for SE-18217 might not work with all types of repeatable and non-repeatable streams. ## [](#5-6-3)5.6.3 **October 22, 2020** ### [](#compatibility-62)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.816

OpenJDK

8 and 11
### [](#features-5)Features - Multiple libraries have been updated to the latest versions. ### [](#fixed-issues-55)Fixed Issues - None ## [](#5-6-2)5.6.2 **September 10, 2020** ### [](#compatibility-63)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.816

OpenJDK

8 and 11
### [](#features-6)Features Upgraded the following dependencies to the latest version (SE-17545): - Apache Commons IO library dependency to 2.7 ### [](#fixed-issues-56)Fixed Issues - Exception `java.lang.IllegalStateException: Connection pool shut down` didn’t trigger a reconnection. This exception now triggers a reconnection as configured. (SE-17545) ## [](#5-6-1)5.6.1 July 10, 2020 ### [](#compatibility-64)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.816
### [](#features-7)Features - Upgraded the Amazon SDK for Java dependency to version 1.11.816. ### [](#fixed-issues-57)Fixed Issues - None. ## [](#5-6-0)5.6.0 February 20, 2020 ### [](#compatibility-65)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.649
### [](#features-8)Features - Added support for range headers. (CONN-4629) - Added support for all Amazon Web Services (AWS) regions. (CONN-4631) ### [](#fixed-issues-58)Fixed Issues - None ## [](#5-5-0)5.5.0 December 17, 2019 ### [](#compatibility-66)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.649
### [](#features-9)Features - Added the Session Token field to support the use of AWS temporary credentials. (SE-14206) ### [](#fixed-issues-59)Fixed Issues - None ## [](#5-4-0)5.4.0 **October 30, 2019** ### [](#compatibility-67)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.649
### [](#features-10)Features - Implemented support for TLS configuration. (CONN-3628) ### [](#fixed-issues-60)Fixed Issues - None ## [](#5-3-8)5.3.8 **October 24, 2019** ### [](#compatibility-68)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.649
### [](#features-11)Features - None ### [](#fixed-issues-61)Fixed Issues - Upgraded AWS SDK in `aws-commons` for the S3 Connector to 1.11.649. (CONN-3773) - S3 Connector proxy issue. (SE-13307) - Proxy configuration not honored in the S3 Connector. (SE-13567) ## [](#5-3-7)5.3.7 **September 5, 2019** ### [](#compatibility-69)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.604
### [](#features-12)Features - None ### [](#fixed-issues-62)Fixed Issues - Amazon S3 Connector did not refresh the token when using a role-based connection. (SE-12983) ## [](#5-3-6)5.3.6 **August 9, 2019** ### [](#compatibility-70)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.604
### [](#features-13)Features - Upgraded the Amazon SDK for Java dependency to version 1.11.604. ### [](#fixed-issues-63)Fixed Issues - None. ## [](#5-3-5)5.3.5 **July 31, 2019** ### [](#compatibility-71)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.594
### [](#features-14)Features - None. ### [](#fixed-issues-64)Fixed Issues - Error types included in the connector were not compatible with the error mapping format used by the Mule runtime engine. This caused a deployment failure. You can now use the connector’s error mapping. \[CONN-1247\] ## [](#5-3-4)5.3.4 **July 26, 2019** ### [](#compatibility-72)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.594
### [](#features-15)Features - None. ### [](#fixed-issues-65)Fixed Issues - Connector did not allow users to configure the URL for S3 compatible storage. Users can now use the new `S3 Compatible Storage URL` parameter to configure the URL for S3 compatible storage. \[SE-10846\] ## [](#5-3-3)5.3.3 **July 11, 2019** ### [](#compatibility-73)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.515
### [](#features-16)Features - None. ### [](#fixed-issues-66)Fixed Issues - Connector was not displaying tool tips for the parameters when configuring a connection. \[CONN-2685\] ## [](#5-3-2)5.3.2 **June 3, 2019** ### [](#compatibility-74)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.515
### [](#features-17)Features - None. ### [](#fixed-issues-67)Fixed Issues - Connector was unable to work with the lowercase region values or region values containing dashes. \[CONN-1942\] ## [](#5-3-1)5.3.1 **May 8, 2019** ### [](#compatibility-75)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.515
### [](#features-18)Features - None. ### [](#fixed-issues-68)Fixed Issues - Connection to S3 no longer requires `s3:ListAllMyBuckets` permission. \[SE-11434\] ## [](#5-3-0)5.3.0 **April 9, 2019** ### [](#compatibility-76)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.515
### [](#features-19)Features - Added support for connecting to new AWS region endpoints. - Connector now supports latest Amazon S3 storage classes: S3 Intelligent-Tiering, S3 Standard-IA, S3 One Zone-IA. (SE-11149) ### [](#fixed-issues-69)Fixed Issues - None. ## [](#5-2-1)5.2.1 **February 25, 2019** ### [](#compatibility-77)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.79
### [](#features-20)Features - None. ### [](#fixed-issues-70)Fixed Issues - The connector was unable to properly stream large files to DataWeave. By adding the content length value as a message attribute, this issue was fixed. - Test connection functionality did not work properly and is now fixed. ## [](#5-2-0)5.2.0 **August 16, 2018** ### [](#compatibility-78)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.79
### [](#features-21)Features - **Triggers** - You can now start a flow with the Amazon S3 Connector every time an object of a specific type is created, updated, or deleted. ### [](#fixed-issues-71)Fixed Issues - None. ## [](#5-1-1)5.1.1 **May 7, 2018** ### [](#compatibility-79)Compatibility
Application/Service Version

Mule

4.1.0 or later

AWS SDK for Java

1.11.79
### [](#features-22)Features - None. ### [](#fixed-issues-72)Fixed Issues The connector identified on the create object operation the content length of 0/null as the content having 0 as content length. It has now changed to have it as null. ## [](#5-1-0)5.1.0 **February 21, 2018** ### [](#compatibility-80)Compatibility
Application/Service Version

Mule

4.1.0 or later

AWS SDK for Java

1.11.79
### [](#features-23)Features - None. ### [](#fixed-issues-73)Fixed Issues AWS connectors shared a common library for the supported region endpoints that caused an issue when two different AWS connectors were used in a Mule app. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon Secrets Manager Properties Provider Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Amazon Secrets Manager Properties Provider is a configuration that enables you to retrieve your secrets from the Amazon Secrets Manager cloud service before your Mule app runs. Guide: [Amazon Secrets Manager Properties Provider Connector User Guide](https://docs.mulesoft.com/amazon-secrets-manager-properties-provider-connector/latest/) ## [](#1-2-1)1.2.1 **September 4, 2026** ### What’s New - This release includes general security fixes. - The AWS SDK version is upgraded to 2.54.11. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

AWS SDK

2.54.11
## [](#1-2-0)1.2.0 **September 2, 2026** ### What’s New - The AWS SDK version is upgraded to 2.54.10. - Amazon Secrets Manager Properties Provider now supports overriding the AWS Secrets Manager endpoint through the optional **Custom Endpoint URL** field in the basic connection. Use this field to route AWS Secrets Manager calls through an AWS VPC interface endpoint (AWS PrivateLink) for private connectivity, or to a local testing service such as LocalStack. - Amazon Secrets Manager Properties Provider now supports overriding the AWS Security Token Service (AWS STS) endpoint through the optional **STS Endpoint URL** field in the role connection. Use this field to route AWS STS calls through a separate endpoint when assuming a role, independently of the **Custom Endpoint URL** field. - The **AWS Access Key** and **AWS Secret Key** fields are now masked in the connector UI and excluded from DSL output, reducing accidental exposure of AWS credentials. For more information, see the [Amazon Secrets Manager Properties Provider Reference](https://docs.mulesoft.com/amazon-secrets-manager-properties-provider-connector/latest/amazon-secrets-manager-properties-provider-reference). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

AWS SDK

2.54.10
### Fixed Issues
Issue Resolution ID

Binary secrets are no longer decoded using the Java runtime’s default character set, which produced incorrect values for secrets containing non-ASCII characters on runtimes not configured for UTF-8. Binary secrets are now always decoded as UTF-8.

W-23823507
## [](#1-1-3)1.1.3 **August 12, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

AWS SDK

2.51.1
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.51.1.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The netty library is upgraded to version 4.2.17.Final.

  • The log4j library is upgraded to version 2.26.1.

W-23441652
## [](#1-1-2)1.1.2 **July 24, 2026** ### What’s New - The AWS SDK version is upgraded to 2.41.0. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

AWS SDK

2.41.0
### Fixed Issues
Issue Resolution ID

Amazon Secrets Manager Properties Provider now acquires AWS credentials and connects to Amazon Secrets Manager when a Mule flow first reads an ${aws-secrets::key} property, instead of during Mule app deployment. This change lets you deploy Mule apps and run MUnit tests without valid AWS credentials when your tests don’t require AWS connectivity. If you rely on deployment-time credential validation, invalid credentials or an unreachable role ARN now surface as an error at first read instead of at deployment.

W-23301017

Amazon Secrets Manager Properties Provider now returns an error when a retrieved secret contains neither a secret string nor a secret binary value, instead of returning no value.

W-23301017
## [](#1-1-1)1.1.1 **February 1, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

AWS SDK

2.35.3
### Fixed Issues
Issue Resolution ID

Amazon Secrets Manager Properties Provider now handles session token expiration by automatically fetching a new secret token.

W-20966019
## [](#1-1-0)1.1.0 **November 21, 2025** ### What’s New - Amazon Secrets Manager Properties Provider now supports passing an external ID in Role-based authentication. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

AWS SDK

2.35.3
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.35.3.

  • The commons-lang3 library is upgraded to version 3.18.0.

W-20218849
## [](#1-0-2)1.0.2 **June 24, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Amazon Secrets Manager Properties Provider now automatically fetches the secret token after the session token expires.

W-18382085
## [](#1-0-1)1.0.1 **March 25, 2024** ### What’s New - This property provider is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-0)1.0.0 **August 4, 2023** ### What’s New This is a new properties provider. For a list of supported configurations, refer to the Amazon Secrets Manager Properties Provider Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon SNS Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Amazon Simple Notification Service (SNS Connector) provides a hosted multi-protocol "push" messaging for applications. The Anypoint Connector for Amazon SNS allows Mule applications to interact with Amazon SNS. SNS Connector 3.0.0 and later is licensed commercially with Anypoint Platform as with other Select connectors. Earlier versions remain freely available to the community. Guide: [Amazon SNS Connector](https://docs.mulesoft.com/amazon-sns-connector/latest/) Reference: [Amazon SNS Connector Reference](https://docs.mulesoft.com/amazon-sns-connector/latest/amazon-sns-connector-reference) ## [](#4-8-5)4.8.5 **September 25, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.55.3

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Connections that use role authentication no longer leak internal AWS Security Token Service (STS) resources during connection, reconnection, or redeployment. Previously, these resources accumulated over repeated connection and redeployment cycles and could eventually exhaust threads and file descriptors in long-running deployments.

W-23993016

The AWS SDK is upgraded to version 2.55.3 to address CVE-2026-68498.

W-24277369

The Netty library is upgraded to version 4.2.18.Final to address reported security vulnerabilities.

W-24161111
## [](#4-8-4)4.8.4 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.51.1

OpenJDK

8, 11, and 17
## [](#4-8-3)4.8.3 **August 7, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.51.1

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.51.1.

  • The Apache Commons Lang library is upgraded to version 3.20.0.

  • The Netty library is upgraded to version 4.2.17.Final.

W-23441611
## [](#4-8-2)4.8.2 **May 27, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.40.16

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Publish operation now correctly encodes message attributes of type Binary. The operation writes values supplied as byte[], java.nio.ByteBuffer, or java.io.InputStream to the Amazon SNS request as binary payloads instead of serializing them through Object#toString, which previously caused Amazon SNS to reject the request with an InvalidParameterValue error.

W-19290033
## [](#4-8-1)4.8.1 **January 7, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.40.16

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The AWS SDK version is upgraded to 2.40.16 to address reported security vulnerabilities.

W-19578791
## [](#4-8-0)4.8.0 **October 24, 2025** ### What’s New - Amazon SNS Connector now supports passing an external ID in Role-based authentication. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.35.3

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.35.3.

  • The commons-lang3 library is upgraded to version 3.18.

  • The netty-codec library is upgraded to version 4.1.126.Final.

  • The netty-codec-http library is upgraded to version 4.1.126.Final.

  • The netty-codec-http2 library is upgraded to version 4.1.126.Final.

  • The netty-handler library is upgraded to version 4.1.126.Final.

W-19887714
## [](#4-7-12)4.7.12 **October 3, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Proxy configuration now works correctly when using the Try Default AWSCredentials Provider Chain field.

W-19061342
## [](#4-7-11)4.7.11 **March 19, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Role ARN configuration now works as intended when the Try Default AWSCredentials Provider Chain field is true.

W-17165979
## [](#4-7-10)4.7.10 **October 9, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Proxy config now works correctly when creating a connection.

W-16876377

You can now use Custom Service Endpoint or VPC endpoint in the SNS Connector after Java 17 AWS SDK 2.X.X upgrade.

W-16855646
## [](#4-7-9)4.7.9 **September 26, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now create a connection with the Try Default AWSCredentials Provider Chain field enabled.

W-16602012

In the Create platform application operation, the GCM API key is replaced with the token.

W-16840478
## [](#4-7-8)4.7.8 **August 13, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now create a connection with temporary credentials with a session key as intended.

W-16298901
## [](#4-7-7)4.7.7 **July 11, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Amazon SNS Connector no longer requires a valid access key and a secret key for role based authentication.

W-16090648
## [](#4-7-6)4.7.6 **June 14, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Amazon SNS Connector token no longer expires after one hour.

W-15046500
## [](#4-7-5)4.7.5 **January 17, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v2.20.153

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The AWS SDK version is upgraded from 1.12.418 to 2.20.153.

W-14145096
## [](#4-7-4)4.7.4 **April 28, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.1025

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.13.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665445
## [](#4-7-3)4.7.3 **October 25, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.1025

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core:jackson-databind:2.13.2.2 dependency is upgraded to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to fix a security vulnerability.

W-11853437
## [](#4-7-2)4.7.2 **April 5, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.1025

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920473
## [](#4-7-1)4.7.1 **January 13, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.1025

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated the componentcom.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9812
## [](#4-7-0)4.7.0 **September 24, 2021** ### What’s New - Added support for FIFO topics, which provide strict message ordering and message deduplication with Amazon SQS FIFO queues. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.1025

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The exception handler incorrectly wrapped errors of the MULE:ANY error type.

SE-22200
## [](#4-6-1)4.6.1 **June 23, 2021** ### [](#compatibility-20)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.1025

OpenJDK

8 and 11
### [](#fixed-issues-19)Fixed Issues - Added `String.Array`, which was a missing data type for message attributes. (SE-21377) ### [](#known-issues)Known Issues - Amazon SNS Connector does not currently support configuring FIFO topics. ## [](#4-6-0)4.6.0 **June 11, 2021** ### [](#compatibility-21)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.1025

OpenJDK

8 and 11
### [](#new-features)New Features - Added a new notification option. Use the **Phone number** parameter to send a text message to a specified phone number. This option is offered in addition to **Target Arn** and **Topic Arn**, which are the existing notification options. ### [](#known-issues-2)Known Issues - Amazon SNS Connector does not currently support configuring FIFO topics. ## [](#4-5-1)4.5.1 **April 15, 2021** ### [](#compatibility-22)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.969

OpenJDK

8 and 11
### [](#fixed-issues-20)Fixed Issues - The **Topic arn** and **Target arn** fields are now mutually exclusive. This enables users to publish messages to either the topic or the platform endpoint. (SE-20310) ### [](#known-issues-3)Known Issues - Amazon SNS Connector does not currently support configuring FIFO topics. ## [](#4-5-0)4.5.0 **March 18, 2021** ### [](#compatibility-23)Compatibility
Application/Service Version

Mule

4.1.1 and later

Amazon Java SDK for SNS

v1.11.969

OpenJDK

8 and 11
### [](#features)Features - Added the ability to set a custom service and STS role endpoint. For example, this is useful when using a VPC endpoint. (CONN-7716) - Upgraded the Amazon SDK for Java dependency to version 1.11.969. - Moved the Try Default AWS Credentials Provider Chain field to the Advanced tab. ### [](#known-issues-4)Known Issues - Amazon SNS Connector does not currently support configuring FIFO topics. ## [](#4-4-5)4.4.5 **February 10, 2021** ### [](#compatibility-24)Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for SNS

v1.11.946

OpenJDK

8 and 11
### [](#features-2)Features Upgraded the Amazon SDK for Java dependency to version 1.11.946. ### [](#fixed-issues-21)Fixed Issues - Fixed the issue that caused excessive warnings in logs about duplicate dependencies during connector initialization in Anypoint Studio. (SE-19197) - Removed the vulnerabilities caused by the Jackson Dataformat: CBOR library. (CONN-7656) ## [](#4-4-4)4.4.4 **October 22, 2020** ### [](#compatibility-25)Compatibility
Application/Service Version

Mule

4.1 and later

Amazon Java SDK for SNS

v1.11.816

OpenJDK

8 and 11
### [](#features-3)Features Multiple libraries have been updated to the latest versions. ### [](#fixed-issues-22)Fixed Issues None ## [](#4-4-3)4.4.3 **July 9, 2020** ### [](#compatibility-26)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for SNS

v1.11.816

OpenJDK

8 and 11
### [](#features-4)Features - Upgraded Amazon Java SDK dependency to version 1.11.816. ### [](#fixed-issues-23)Fixed Issues None ## [](#4-4-2)4.4.2 **February 21, 2020** ### [](#compatibility-27)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for RDS

v1.11.649

Java

1.8.0_x
### [](#features-5)Features None ### [](#fixed-issues-24)Fixed Issues - Publish operation’s messageStructure field is not mandatory anymore. (SE-14876) - Test connection was fixed. Now an appropriate error message is thrown in case of empty or invalid test topic. (CONN-4621) ## [](#4-4-1)4.4.1 **February 5, 2020** ### [](#compatibility-28)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for RDS

v1.11.649

Java

1.8.0_x
### [](#features-6)Features None ### [](#fixed-issues-25)Fixed Issues The List Topics operation returned plain text type. It now returns the application java type. (CONN-4807) ## [](#4-4-0)4.4.0 **January 14, 2020** ### [](#compatibility-29)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for RDS

v1.11.649

Java

1.8.0_x
### [](#features-7)Features - Implemented support for configuring TLS. (CONN-3628) ### [](#fixed-issues-26)Fixed Issues - Added the missing Session Token field into the configuration. (SE-14206) ## [](#4-3-1)4.3.1 **November 25, 2019** ### [](#compatibility-30)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for SNS

v1.11.611

Java

1.8.x
### [](#features-8)Features - Upgraded Amazon SDK dependencies to the latest version. ### [](#fixed-issue)Fixed Issue - When using a role connection, the connector was not refreshing the session token after it expired. This issue is now fixed. \[SE-14031\] ## [](#4-3-0)4.3.0 **August 22, 2019** ### [](#compatibility-31)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for SNS

v1.11.604

Java

1.8.x
### [](#features-9)Features - Upgraded Amazon SDK dependencies to the latest version. ### [](#fixed-issues-27)Fixed Issues - Error types included in the connector were not compatible with the error mapping format used by the Mule engine. This caused a deployment failure. You can now use the connector’s error mapping. \[CONN-1247\] ## [](#4-2-0)4.2.0 **April 16, 2019** ### [](#compatibility-32)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for SNS

v1.11.515

Java

1.8.x
### [](#features-10)Features - Added support for connecting to new AWS region endpoints. ### [](#fixed-issues-28)Fixed Issues - None ## [](#4-1-0)4.1.0 **February 21, 2018** ### [](#compatibility-33)Compatibility
Application/Service Version

Mule

4.1.0 and later

Amazon Java SDK for SNS

v1.11.79

Java

1.8.x
### [](#features-11)Features - None ### [](#fixed-issues-29)Fixed Issues AWS connectors shared a common library for the supported region endpoints that caused an issue when two different AWS connectors were used in a Mule app. This version fixes this issue. ## [](#4-0-0)4.0.0 **November 18, 2017** ### [](#compatibility-34)Compatibility
Application/Service Version

Mule

4.0.0 and later

Amazon Java SDK for SNS

v1.11.79

Java

1.8.x
### [](#features-12)Features - Upgraded to support AWS SDK v1.11.79 - Upgraded to Mule v4.0.0 ### [](#fixed-issues-30)Fixed Issues - None ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Amazon SQS Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Amazon SQS (SQS Connector) provides an easy way to interface with the Amazon SQS API, allowing users to manage SQS queueing services without having to interact with the API directly. Starting with SQS Connector v.4.0.0, the connector is licensed commercially with Anypoint Platform in the Select support category. Prior versions remain freely available to the community. Guide: [Amazon SQS Connector](https://docs.mulesoft.com/jp/amazon-sqs-connector/latest/) Reference: [Amazon SQS Connector Reference](https://docs.mulesoft.com/jp/amazon-sqs-connector/latest/amazon-sqs-connector-reference) ## [](#5-12-12)5.12.12 **September 30, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.55.6
### Fixed Issues
Issue Resolution ID

The AWS SDK version is upgraded to 2.55.6 to address reported security vulnerabilities.

W-24311855, W-24311853, W-24311856, W-24311857
## [](#5-12-11)5.12.11 **September 25, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.55.3
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.55.3.

  • The io.netty libraries are upgraded to version 4.2.18.Final.

  • The Jackson library is upgraded to version 2.22.3.

W-24161073, W-24277469
## [](#5-12-10)5.12.10 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.50.3
### Fixed Issues
Issue Resolution ID

The Receive messages source now resumes message consumption after a transient AWS outage, instead of remaining stopped with repeating IllegalStateException: Connection pool shut down errors until you restart the application.

W-22815847
## [](#5-12-9)5.12.9 **August 5, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.50.3
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK for Java v2 library is upgraded to version 2.50.3.

  • The Amazon SQS Java Extended Client Library is upgraded to version 2.1.3.

  • The Jackson library is upgraded to version 2.22.1.

  • The Apache Commons Codec library is upgraded to version 1.22.1.

W-23657991
## [](#5-12-8)5.12.8 **June 19, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.46.13
### Fixed Issues
Issue Resolution ID

The Receive messages source no longer dispatches messages after receiving a stop signal during graceful shutdown. This change prevents silent in-flight message loss when the source is stopped while actively processing messages.

W-22953753

The AWS SDK version is upgraded to 2.46.13.

W-22899717
## [](#5-12-7)5.12.7 **June 15, 2026** ### Compatibility
Software Version

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.46.8
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.46.8.

  • The commons-codec library is upgraded to version 1.22.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The jackson-core library is upgraded to version 2.22.0.

  • The jackson-databind library is upgraded to version 2.22.0.

  • The netty-handler, netty-codec, netty-codec-http, netty-codec-http2, netty-transport, netty-common, netty-buffer, netty-resolver, netty-transport-classes-epoll, and netty-transport-native-unix-common libraries are upgraded to version 4.1.135.Final.

W-22807398
## [](#5-12-6)5.12.6 **May 25, 2026** ### What’s New - The **Large Payload Support** object type now includes the new optional **S3 Key Prefix** field. You can set this field to propagate to the underlying extended SQS client and use it as a prefix for keys created in the configured S3 bucket. This allows you to isolate connector-managed payloads under a dedicated path within a shared bucket. For more information, refer to [Large Payload Support](https://docs.mulesoft.com/jp/amazon-sqs-connector/latest/amazon-sqs-connector-reference#LargePayloadSupport). ### Compatibility
Software Version

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.42.19
### Fixed Issues
Issue Resolution ID

The 403 Forbidden error no longer occurs when attempting to send data to specific S3 folder paths using AWS SDK v2.

W-22315198
## [](#5-12-5)5.12.5 **April 5, 2026** ### Compatibility
Software Version

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.42.19
### Fixed Issues
Issue Resolution ID

The Receive messages source now performs initial validation of the queue URL. If the validation fails, the source stops running. To enable queue URL validation, ensure that the IAM role includes an additional policy granting the sqs:GetQueueAttributes permission.

W-21227083

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.42.19.

  • The commons-codec library is upgraded to version 1.21.0.

  • The jackson-core library is upgraded to version 2.21.2.

  • The jackson-databind library is upgraded to version 2.21.2.

  • The jackson-dataformat-cbor library is upgraded to version 2.21.2.

  • The netty-codec-http library is upgraded to version 4.1.132.Final.

  • The netty-codec-http2 library is upgraded to version 4.1.132.Final.

  • The netty-handler library is upgraded to version 4.2.10.Final.

W-21227083
## [](#5-12-4)5.12.4 **January 6, 2026** ### Compatibility
Software Version

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.40.16
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.40.16.

  • The amazon-sqs-java-extended-client-lib library is upgraded to version 2.1.2.

W-19578816
## [](#5-12-3)5.12.3 **December 4, 2025** ### Compatibility
Software Version

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.35.3
### Fixed Issues
Issue Resolution ID

The Receive messages source now correctly consumes and processes messages present in the queue immediately after starting up.

W-20237992
## [](#5-12-2)5.12.2 **November 8, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.35.3
### Fixed Issues
Issue Resolution ID

In the Receive messages source, the Start delay time unit field is renamed to Time unit, and its default value is changed from SECONDS to MILLISECONDS.

W-20132431

These libraries are upgraded to address reported security vulnerabilities:

  • The AWS SDK version is upgraded to 2.35.3.

  • The netty-codec library is upgraded to version 4.1.126.Final.

  • The netty-codec-http library is upgraded to version 4.1.126.Final.

  • The netty-codec-http2 library is upgraded to version 4.1.126.Final.

  • The jackson-core library is upgraded to version 2.16.0.

  • The netty-handler library is upgraded to version 4.2.0.Final.

W-20133902
## [](#5-12-1)5.12.1 **August 24, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
### Fixed Issues
Issue Resolution ID

Amazon SQS Connector now includes new validation for the queue name in the Receive messages source.

W-19165767
## [](#5-12-0)5.12.0 **August 5, 2025** ### What’s New - Amazon SQS Connector now supports passing an external ID in Role-based authentication. - In the **Receive messages** source, the **Time unit** field is renamed to **Start delay time unit**, and its default value is changed from `MILLISECONDS` to `SECONDS`. ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
## [](#5-11-15)5.11.15 **April 13, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17

AWS SDK

2.31.16
### Fixed Issues
Issue Resolution ID

The AWS SDK is now upgraded to version 2.31.16.

W-18242119

The netty-common library is upgraded to version 4.1.118.Final to address reported security vulnerabilities.

W-17494482
## [](#5-11-14)5.11.14 **June 13, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Removed the MB and GB as options from the Message Size Threshold Unit field.

W-13709687
## [](#5-11-13)5.11.13 **January 17, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The netty-handler component is upgraded from version 4.1.94.Final to 5.0.0.Alpha1.

W-14462866

The DOS security vulnerability in the Netty Codec Http2 no longer occurs.

W-14462881

The Improper Certificate Validation security vulnerability in the Netty Handler component no longer occurs.

W-14462916

The software.amazon.awssdk module is upgraded from version 2.20.94 to 2.23.3.

W-14462881, W-14462866, W-14462916
## [](#5-11-12)5.11.12 **January 15, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2

OpenJDK

8, 11, and 17
## [](#5-11-11)5.11.11 **September 29, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

Amazon SQS REST API

v2
### Fixed Issues
Issue Resolution ID

The Jackson library is upgraded from version 2.15.0 to 2.15.2.

W-13844865

The com.fasterxml.jackson.core component is upgraded from version 2.14.2 to 2.15.2.

W-13844865

The Improper Certificate Validation security vulnerability in the Netty Handler 4.1.94.Final component is fixed.

W-13844851.
## [](#5-11-10)5.11.10 **July 12, 2023** ### What’s New - The connector now uses the version 2.x of the Java SDK for AWS. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

2.20.94

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector no longer performs operations on queues that are not in the regions for which the connector is configured.

W-12965299
## [](#5-11-9)5.11.9 **June 5, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.12.457

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

SQS Connector no longer lacks a proxy configuration when large payload support is enabled.

W-13314768
## [](#5-11-8)5.11.8 **April 28, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.12.457

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the following dependencies: jackson-databind and jackson-dataformat-cbor to 2.15.0, and AWS SDK to 1.12.457.

W-12669648
## [](#5-11-7)5.11.7 **October 25, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.12.261

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core:jackson-databind:2.13.2.2 dependency is upgraded to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to fix a security vulnerability.

W-11853419
## [](#5-11-6)5.11.6 **August 3, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.12.261

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.amazonaws:aws-java-sdk-s3 dependency is upgraded to com.amazonaws:aws-sdk (1.12.261) to fix a vulnerability.

W-11454663
## [](#5-11-5)5.11.5 **June 15, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.1019

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The deduplicationId field now works for the Send Message Batch operation.

W-11261736
## [](#5-11-4)5.11.4 **April 28, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.1019

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Test Connection functionality now shows a Test connection cannot be performed because the test queue arn parameter is not set error when the value for the Test Queue ARN field is unspecified.

W-10893914
## [](#5-11-3)5.11.3 **April 5, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.1019

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920483
## [](#5-11-2)5.11.2 **January 11, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.1019

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9805
## [](#5-11-1)5.11.1 **September 7, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.1019

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The exception handler incorrectly wrapped errors to the MULE:ANY error type. Now, errors occur without any modification or wrapping.

CONN-8787
## [](#5-11)5.11 **June 3, 2021** ### [](#compatibility-29)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.1019

OpenJDK

8 and 11
### [](#fixed-issues-27)Fixed Issues Amazon SQS Connector error types were not exported. (SE-19920) ## [](#5-10-1)5.10.1 **April 1, 2021** ### [](#compatibility-30)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.946

OpenJDK

8 and 11
### [](#fixed-issues-28)Fixed Issues Fixed the issues related to erratic reconnections that occurred after a message receiver failure. (SE-19965) ## [](#5-10-0)5.10.0 **March 1, 2021** ### [](#compatibility-31)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.946

OpenJDK

8 and 11
### [](#features)Features Added support for custom domain endpoints, such as S3, SQS, and STS, to provide Amazon Virtual Private Cloud (VPC) feature utilization. ## [](#5-9-1)5.9.1 **February 11, 2021** ### [](#compatibility-32)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.946

OpenJDK

8 and 11
### [](#features-2)Features Upgraded the Amazon SDK for Java dependency to version 1.11.946. ### [](#fixed-issues-29)Fixed Issues Removed the vulnerabilities caused by the Jackson Dataformat: CBOR library. (CONN-7656) ## [](#5-9-0)5.9.0 **January 14, 2021** ### [](#compatibility-33)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.816

OpenJDK

8 and 11
### [](#features-3)Features - Added the Default Wait time and Wait time fields, which enable you to a set a polling wait time for the Read operation and Receive messages source. This change enables you to use long polling, which is now enabled by default. - Added the Number of consuming threads field to the Receive messages source, which enables you to set the number of polling threads. - The Receive messages source now behaves like a standard polling source with start delay and polling frequency parameters. (SE-18866) ### [](#fixed-issues-30)Fixed Issues - None ## [](#5-8-1)5.8.1 **October 22, 2020** ### [](#compatibility-34)Compatibility
Application/Service Version

Mule

4.1 and later

AWS SDK for Java

1.11.816

OpenJDK

8 and 11
### [](#features-4)Features Upgraded Apache HttpClient to the latest version, 4.5.13. ### [](#fixed-issues-31)Fixed Issues - None ## [](#5-8-0)5.8.0 **September 17, 2020** ### [](#compatibility-35)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.816

OpenJDK

8 and 11
### [](#features-5)Features The connector now supports sending and receiving messages with payloads up to 2GB using the Amazon S3 service. ### [](#fixed-issues-32)Fixed Issues - None ## [](#5-7-0)5.7.0 **August 7, 2020** ### [](#compatibility-36)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.816

Java

11
### [](#features-6)Features - The connector now supports the deduplicationId attribute when sending messages to the FIFO queue. ### [](#fixed-issues-33)Fixed Issues - None ## [](#5-6-1)5.6.1 **July 28, 2020** ### [](#compatibility-37)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.816
### [](#fixed-issues-34)Fixed Issues - If you did not specify a value for the\`Test Queue Arn\` field when using the `Test Connection` functionality, the test connection failed and an error displayed in the console when the associated operation was invoked". (CONN-6570) Now, you still must specify a value for the `Test Queue Arn` field when you test the connection. However, if you don’t specify this value, the console displays a warning instead of an error when the associated operation is invoked, and the connection validation is not performed. - Some of the operations did not take into account the default global queue URL in the configuration. This is now fixed, and you can use the default global queue URL for all the operations. ## [](#5-6-0)5.6.0 **July 8, 2020** ### [](#compatibility-38)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.816
### [](#features-7)Features - The connector now supports running on all cluster nodes by default. This behavior was present in version 5.4.3, but it was accidentally removed in version 5.5.0. For this reason, version 5.5.0 is deprecated. (SE-16536) For information about how to run on the primary node only, see [Upgrade to Version 5.6](https://docs.mulesoft.com/jp/amazon-sqs-connector/latest/amazon-sqs-connector-upgrade-migrate). ### [](#fixed-issues-35)Fixed Issues - None. ## [](#5-5-0-deprecated)5.5.0 (Deprecated) **Janaury 28, 2020** ### [](#compatibility-39)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.649
### [](#features-8)Features - Added the Session Token field to support the use of Amazon AWS temporary credentials. (CONN-4525) ### [](#fixed-issues-36)Fixed Issues - None. ## [](#5-4-3)5.4.3 **November 25, 2019** ### [](#compatibility-40)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.649
### [](#features-9)Features - None. ### [](#fixed-issues-37)Fixed Issues - Metadata for the `Get queue attributes` operation returned plain text type. It now returns the application java type. (SE-13914) ## [](#5-4-2)5.4.2 **October 23, 2019** ### [](#compatibility-41)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.649
### [](#features-10)Features - Upgraded the Amazon SDK for Java dependency to version 1.11.649. ### [](#fixed-issues-38)Fixed Issues - None. ## [](#5-4-1)5.4.1 **October 2, 2019** ### [](#compatibility-42)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.604
### [](#features-11)Features - None. ### [](#fixed-issues-39)Fixed Issues - Changed the name of the `Receivemessages` operation to `Receive messages`. \[CONN-3394\] ## [](#5-4-0)5.4.0 **August 26, 2019** ### [](#compatibility-43)Compatibility
Application/Service Version

Mule

4.1.1 and later

AWS SDK for Java

1.11.604
### [](#features-12)Features - Upgraded Amazon SDK dependencies to the latest version. ### [](#fixed-issues-40)Fixed Issues - Error types included in the connector were not compatible with the error mapping format used by Mule. This caused a deployment failure. You can now use the connector’s error mapping. \[CONN-1247\] - **Test Connection** did not work when the correct SQS queue ARN was entered. \[CONN-2947\] ## [](#5-3-2)5.3.2 **July 30, 2019** ### [](#compatibility-44)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.515
### [](#features-13)Features - None. ### [](#fixed-issues-41)Fixed Issues - The test connection issue has been fixed. (CONN-923) ## [](#5-3-1)5.3.1 **June 21, 2019** ### [](#compatibility-45)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.515
### [](#features-14)Features - None. ### [](#fixed-issues-42)Fixed Issues - Receive message source did not use the default global queue URL when the queue URL was not specified. Therefore, an error was thrown after the application deployed. \[SE-12178\] ## [](#5-3-0)5.3.0 **April 16, 2019** ### [](#compatibility-46)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.515
### [](#features-15)Features - Added support for connecting to new AWS region endpoints. ### [](#fixed-issues-43)Fixed Issues - None. ## [](#5-2-1)5.2.1 **February 22, 2019** ### [](#compatibility-47)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.79
### [](#features-16)Features - None. ### [](#fixed-issues-44)Fixed Issues - In earlier versions, when Amazon SQS threw an error, SQS listener stopped working. Now the reconnect process for the listener is triggered in such case. ## [](#5-2-0)5.2.0 **August 28, 2018** ### [](#compatibility-48)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.79
### [](#features-17)Features - None. ### [](#fixed-issues-45)Fixed Issues - The issue where this connector threw java.lang.UnsupportedOperationException for sqs:delete-message-batch has been fixed. ## [](#5-1-1)5.1.1 **May 3, 2018** ### [](#compatibility-49)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.79
### [](#features-18)Features - None. ### [](#fixed-issues-46)Fixed Issues Receive Message Source was failing to retrieve the Messages on the Queue rendering it useless. This version fixes this by making it work using an asynchronous client. ## [](#5-1-0)5.1.0 **February 21, 2018** ### [](#compatibility-50)Compatibility
Application/Service Version

Mule

4.1.0 and later

AWS SDK for Java

1.11.79
### [](#features-19)Features - None. ### [](#fixed-issues-47)Fixed Issues AWS connectors shared a common library for the supported region endpoints that caused an issue when two different AWS connectors were used in a Mule app. This version fixes this issue. ## [](#5-0-0)5.0.0 **November 18, 2017** ### [](#compatibility-51)Compatibility
Application/Service Version

Mule

4.0.x and later

AWS SDK for Java

1.11.79
### [](#features-20)Features - Migrated to Mule 4. ### [](#fixed-issues-48)Fixed Issues - None. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # AMQP Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for AMQP (AMQP Connector) enables your application to publish and consume messages using an AMQP 0.9.1-compliant broker. Guide: [AMQP Connector User Guide](https://docs.mulesoft.com/amqp-connector/latest/) ## [](#1-9-5)1.9.5 **October 13, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ AMQP client library

5.37.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The RabbitMQ AMQP client library is upgraded to version 5.37.0 to address reported security vulnerabilities.

W-24409879
## [](#1-9-4)1.9.4 **September 18, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ AMQP client library

5.36.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The RabbitMQ AMQP client library is upgraded to version 5.36.0 to address reported security vulnerabilities.

W-24142423
## [](#1-9-3)1.9.3 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ Client Library

5.34.0

OpenJDK

8, 11, and 17
## [](#1-9-2)1.9.2 **August 10, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - The RabbitMQ AMQP client library is upgraded to 5.34.0. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ Client Library

5.34.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

AMQP Connector no longer leaks consumers on the message listener across broker reconnection cycles.

W-22860958

AMQP Connector now correctly verifies the broker hostname when using mutual TLS and maps oversized inbound messages to a connectivity error instead of failing unexpectedly.

W-23481127
## [](#1-9-1)1.9.1 **July 21, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ Client Library

5.31.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

AMQP Connector now raises the AMQP:EXCHANGE_NOT_FOUND error instead of silently dropping the message when the configured returned-message exchange doesn’t exist on the broker.

W-20742724
## [](#1-9-0)1.9.0 **November 14, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ Client Library

5.22.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

AMQP Connector now has the new Max Inbound Message Body Size field, which controls the maximum allowed message size processed.

W-17660592

AMQP Connector no longer fails with the Unable to Commit transaction, the TX Channel doesn’t exist error when mixing non-transactional and transactional flows when using the Publish operation.

W-20120112

AMQP Connector now properly handles null header transformation when running in Java 17.

W-19239339
## [](#1-8-3)1.8.3 **July 11, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ Client Library

5.22.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

AMQP Connector is now backward compatible with 1.7.x by parameter reordering.

W-18402047

AMQP Connector now properly disposes of idle channels.

W-18832287
## [](#1-8-2-deprecated)1.8.2 (Deprecated) **April 15, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ Client Library

5.22.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Improved the channel management logic in concurrent scenarios by introducing a ChannelPool mechanism. This resolves issues with requestBrokerConfirms="true" in Publish operations.

W-17035109

The AMQP Listener source no longer triggers an IllegalAccessException when trying to access certain message headers through an expression language, for example attributes.headers. The connector now safely accesses these values through supported APIs.

W-16433857
## [](#1-8-1-deprecated)1.8.1 (Deprecated) **October 2, 2024** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

RabbitMQ Client Library

5.22.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The RabbitMQ client library is upgraded to 5.22.0.

W-16732133
## [](#1-8-0-deprecated)1.8.0 (Deprecated) **May 31, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

RabbitMQ Client Library

5.18.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Use the new Skip exchange validation field in the Publish operation to skip the exchange validation. Additionally, the Publish operation now uses a single channel for each request, rather than creating a new channel each time.

W-15539673
## [](#1-7-7)1.7.7 **December 15, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

RabbitMQ Client Library

5.18.0

OpenJDK

8, 11, and 17
## [](#1-7-6)1.7.6 **December 5, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

RabbitMQ Client Library

5.18.0
### Fixed Issues
Issue Resolution ID

AMQP Connector now generates ACK IDs with a unique identifier to avoid collisions.

W-14210002
## [](#1-7-5)1.7.5 **November 14, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

RabbitMQ Client Library

5.16.0
### Fixed Issues
Issue Resolution ID

AMQP Connector no longer creates more than one channel or consumer in RabbitMQ when there is a force closed connection.

W-13862304
## [](#1-7-4)1.7.4 **April 19, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

RabbitMQ Client Library

5.16.0
### Fixed Issues
Issue ID

AMQP consumers now do not get disposed after a failed deployment when an AMQP Connector configuration is shared in a Mule domain.

W-10706136
## [](#1-7-3)1.7.3 **December 22, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The AMQP Listener source failed with the error TX Channel doesn’t exist when a transaction initiated from a message source was rolled back.

AMQPC-24
## [](#1-7-2)1.7.2 **August 31, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The Reject operation could not requeue messages.

AMQPC-22
## [](#1-7-1)1.7.1 **June 9, 2021** ### [](#new-features-and-enhancements)New Features and Enhancements None ### [](#fixed-issues-15)Fixed Issues - Fixed an issue in which the **Publish consume** operation leaked channels. (AMQPC-20) ## [](#1-7-0)1.7.0 **December 29, 2020** ### [](#new-features-and-enhancements-2)New Features and Enhancements None ### [](#fixed-issues-16)Fixed Issues - Added mTLS support. (AMQPC-14) ## [](#1-6-5)1.6.5 **December 15, 2020** ### [](#new-features-and-enhancements-3)New Features and Enhancements None ### [](#fixed-issues-17)Fixed Issues - Fixed the behavior that prevented the correct acknowledgment of processed messages when the application shut down. (AMQPC-12) ## [](#1-6-4)1.6.4 **September 21, 2020** ### [](#new-features-and-enhancements-4)New Features and Enhancements None ### [](#fixed-issues-18)Fixed Issues - Fixed an issue in which inflight messages were not acknowledged during the runtime shutdown. (AMQPC-12) ## [](#1-6-3)1.6.3 **August 6, 2020** ### [](#new-features-and-enhancements-5)New Features and Enhancements None ### [](#fixed-issues-19)Fixed Issues - Fixed an issue in which messages were lost due to channel reset when the max-retries limit was reached. (AMQPC-9) - Fixed an issue in which the Consume operation leaked channels, after performing consume and ack actions. (AMQPC-10) - Fixed an issue in which the Listener operation did not recover connection when a reconnection strategy was applied. (AMQPC-11) ## [](#1-6-2)1.6.2 **April 20, 2020** ### [](#new-features-and-enhancements-6)New Features and Enhancements None ### [](#fixed-issues-20)Fixed Issues Define queue bindings to an exchange in queue declarations, as in Mule 3. (AMQP-138) To define queue bindings, use the Binding Routing Key parameter in the Queue Definition. ## [](#1-6-1)1.6.1 This version was not released. ## [](#1-6-0)1.6.0 **February 26, 2020** ### [](#new-features-and-enhancements-7)New Features and Enhancements - The timestamp attribute is now in the `amqp:properties` element. - You can now set the `messageid` attribute in the publish-consume operation. ### [](#fixed-issues-21)Fixed Issues - AMQP Connector did not apply the expiration property value. (MULE-18012) - The timestamp attribute did not appear in the 'amqp:properties' element. - The `messageid` attribute could not be set in the publish-consume operation. (AMQP-158) ## [](#1-5-0)1.5.0 **December 18, 2019** ### [](#new-features-and-enhancements-8)New Features and Enhancements - Added a handshake configuration to configuration parameters (AMQP-157) - Added the ability to set socket attributes for AMQP (AMQP-156) ## [](#1-4-5)1.4.5 **September 3, 2019** ### [](#fixed-issues-22)Fixed Issues - Leak in dynamic config: AmqpConfig POJOs do not implement equals and hashcode. (AMQP-152) - `ConnectionException` is not thrown when the queue is not found. (AMQP-151) - Use `basicReject` or `basicAck` for cases where brokers are recovered and `recoverStrategy` is set to `NO_REQUEUE`. (AMQP-150) ## [](#1-4-4)1.4.4 **July 31, 2019** ### [](#fixed-issues-23)Fixed Issues - Channel leak in publish-consume operation. (AMQP-145) - Default TLS context should be available for a TLS connection. (AMQP-146) - AMQP Connector Publish operation incorrectly sets the delivery mode for sent messages. (AMQP-148) ## [](#1-4-3)1.4.3 **May 31, 2019** ### [](#fixed-issues-24)Fixed Issues - Consumer Manager does not stop consumers separately when configuring a domain. (AMQP-142) ## [](#1-4-2)1.4.2 **March 27, 2019** ### [](#fixed-issues-25)Fixed Issues - Race condition with consumer regeneration and Mule redeploy in domain. (AMQP-140) - Default Exchange is not taken into account in publish. (AMQP-141) ## [](#1-4-1)1.4.1 **March 14, 2019** ### [](#fixed-issues-26)Fixed Issues - Operations do not close channel on MANUAL ack mode. (AMQP-139) ## [](#1-4-0)1.4.0 **March 8, 2019** ### [](#new-features-and-enhancements-9)New Features and Enhancements - Defines queues bindings to exchange in queues declarations as in Mule 3. (AMQP-138) ## [](#1-3-4)1.3.4 **February 11, 2019** ### [](#fixed-issues-27)Fixed Issues - Enforce reconnection when an AlreadyClosed exception occurs and when the reason is not identified for a fallback address. (AMQP-133) ## [](#1-3-3)1.3.3 **February 5, 2019** ### [](#fixed-issues-28)Fixed Issues - Always enforce reconnection to be performed: guarantee reconnection when consumers are cancelled. (AMQP-132) ## [](#1-3-2)1.3.2 **January 30, 2019** ### [](#fixed-issues-29)Fixed Issues - Move Generic Connection Provider to AmqpConfig so that the connection is bound to the configuration. (AMQP-131) ## [](#1-3-1)1.3.1 **January 29, 2019** ### [](#fixed-issues-30)Fixed Issues - Disabling RabbitMQ NIO functionality. (AMQP-127) - Problem connecting to fallbackAddresses - always the last address was attempted. (AMQP-126) ## [](#1-3-0)1.3.0 **January 21, 2019** ### [](#new-features-and-enhancements-10)New Features and Enhancements - Reincorporate fallback addresses in AMQP 4 connector. (AMQP-115) ## [](#1-2-0)1.2.0 **January 8, 2019** ### [](#new-features-and-enhancements-11)New Features and Enhancements - User should be able to set the requestedHeartbeat in the connector. (AMQP-114) ## [](#1-1-3)1.1.3 **December 19, 2018** ### [](#fixed-issues-31)Fixed Issues - Consumers are not released when associated to a connector defined in a domain. (AMQP-113) ## [](#1-1-2)1.1.2 **November 27, 2018** ### [](#fixed-issues-32)Fixed Issues - AMQP client ShutdownSignalExceptions must be handled in listeners. (AMQP-107) ## [](#1-1-1)1.1.1 **October 29, 2018** ### [](#fixed-issues-33)Fixed Issues - Transformer service incorrectly transformed byte array. (AMQP-105) ## [](#1-1-0)1.1.0 **October 16, 2018** ### [](#new-features-and-enhancements-12)New Features and Enhancements - SNI Support. - Performance improvements. - Use of NIO RabbitMQ client API. ### [](#fixed-issues-34)Fixed Issues - AMQP module ignores quality of service in listener. (AMQP-102) ## [](#1-0-2)1.0.2 **October 29, 2018** ### [](#fixed-issues-35)Fixed Issues - transformer service incorrectly transforms byte array. (AMQP-105) ## [](#1-0-1)1.0.1 **October 16, 2018** ### [](#new-features-and-enhancements-13)New Features and Enhancements - Performance improvements. - Use of NIO rabbitmq client API. ### [](#fixed-issues-36)Fixed Issues - AMQP module ignores quality of service in listener. (AMQP-102) **May 2018** ## [](#1-0-0)1.0.0 **May 24, 2018** ### [](#new-features-and-enhancements-14)New Features and Enhancements Initial Release. ### [](#upgrade-requirements)Upgrade Requirements Mule 4.1 ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Access Management Release Notes ## [](#june-4-2026)June 4, 2026 ### What’s New - Client applications now include a `credentialsUpdatedAt` timestamp that records when the application’s client secret was last updated. This value updates only when the client secret changes, such as when you reset the secret, and not when you modify other application details such as the name or redirect URIs. Use this timestamp to accurately track credential rotation.
This field was added without a historical backfill, so it doesn’t reflect secret changes made before the field became available (June 4, 2026). Applications whose secret hasn’t been updated since then return the application’s creation date as an approximate earliest date, not an actual rotation timestamp.
## [](#april-21-2026)April 21, 2026 ### What’s New - Audit logs now include entries for heap dumps triggered by MuleSoft staff, providing full transparency for all administrative actions performed in your environment. This enhancement ensures that every internal diagnostic action is visible in your audit trail, meeting the compliance and security requirements of organizations managing sensitive data. This visibility is enabled by default, and no configuration is required. For more information, see [Runtime Manager Audit Logging](https://docs.mulesoft.com/jp/access-management/audit-logging#runtime-manager). ## [](#november-24-2025)November 24, 2025 ### What’s New - You can now enable Integration Intelligence (Beta) in Anypoint Platform. Use Integration Intelligence (Beta) to monitor, analyze, and troubleshoot your data by bringing your MuleSoft telemetry data into the Salesforce ecosystem, unlocking a new, unified observability experience. For more information, see [monitoring::integration-intelligence.adoc](#monitoring::integration-intelligence.adoc). ## [](#november-20-2025)November 20, 2025 ### What’s New - You can now enforce IP restrictions for signin to your Anypoint Platform organization. This feature helps protect your organization by restricting access to trusted networks only. This feature is available only for US and EU commercial clouds. For more information, see [Managing IP Restrictions](#access-management::managing-ip-allowlists.adoc). ## [](#may-12-2025)May 12, 2025 ### What’s New - In addition to Authorization Header, you can now use short-lived bearer access tokens when configuring an external OpenID Connect (OIDC) identity provider (IdP). This method enhances security by allowing you to control the token lifespan and restrict scopes to only those that are necessary. For more information, see [OpenID Connect クライアント管理の設定](https://docs.mulesoft.com/jp/access-management/configure-client-management-openid-task). ## [](#april-15-2025)April 15, 2025 ### What’s New - You can now choose the client secret expiration duration when you configure a Microsoft Entra ID client provider. For more information, see [access-management::configure-client-management-entra-id.adoc](#access-management::configure-client-management-entra-id.adoc). ## [](#november-4-2024)November 4, 2024 ### What’s New The new **Salesforce** page in Access Management enables you to: - Connect your Anypoint Platform organization with trusted Salesforce organizations. For more information, see [access-management::connecting-salesforce-orgs.adoc](#access-management::connecting-salesforce-orgs.adoc) - Enable, remove, and repair connections to Salesforce organizations. For more information, see [access-management::managing-connected-salesforce-orgs.adoc](#access-management::managing-connected-salesforce-orgs.adoc) - Enable Einstein for Anypoint Code Builder through a free, shared trial Salesforce organization. For more information, see [access-management::manage-capabilities.adoc](#access-management::manage-capabilities.adoc) - View capabilities, such as invocable actions and Einstein that are enabled for your Anypoint Platform organization through a connected Salesforce organization. ## [](#august-14-2024)August 14, 2024 ### What’s New - You can now access the Settings page tab for users in three different ways: - Click the user’s name in the **Name** column. - Click the username of the user in the **Username** column. - Click the More actions menu (…​) in the user’s row, and select **Manage User**. For more information, see [Access the User’s Settings Page](https://docs.mulesoft.com/jp/access-management/users#access-user-settings). ## [](#july-24-2024)July 24, 2024 ### What’s New - The ability to add new PingFederate client providers is deprecated. You can continue to use and manage existing PingFederate client providers. ## [](#may-30-2024)May 30, 2024 ### What’s New - The Audit Log Query API now returns versioned object information, which is captured at the time of log generation. Previously, queries returned only the latest object information, and you had to opt in to receive versioned information. This enhancement is now standard for query results. However, the data model for query results remains unchanged. ## [](#may-13-2024)May 13, 2024 ### What’s New - You can now update Azure AD Client secrets in Anypoint Platform access management. For more information, see [Client Secrets](https://docs.mulesoft.com/jp/access-management/configure-client-management-azure). ## [](#april-26-2024)April 26, 2024 ### What’s New - You can now manage connected apps at the business group level. Previously configured connected apps are automatically associated with your root organization. Note that users who have the Organization Administrator permission in a business group can manage only the connected apps that are configured within the respective business group. ## [](#april-15-2024)April 15, 2024 ### What’s New - The Audit Log Query API now enables you to specify a query parameter when you call the API. This opt-in feature enables API responses to include versioned object information that was captured when the audit log was generated. For more information, see the [Audit Log Query API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/audit-log-query-api) in Exchange. ## [](#february-29-2024)February 29, 2024 ### What’s New - The [Telemetry Exporter feature](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) in Anypoint Monitoring enables you to export [audit log](https://docs.mulesoft.com/jp/access-management/audit-logging) data to third-party analytics and observability apps. ## [](#january-26-2024)January 26, 2024 ### What’s New - The modern UI is now the only Access Management experience for all organizations. Organizations that had access to the legacy UI can no longer switch to this view. The modern UI includes the following enhancements: - The Teams feature for robust and scalable permissions management. Your root organization is automatically given an "Everyone at " team that enables you to provide a basic set of permissions for all users in your organization. - A polished business group interface featuring more details, including a broader look at membership, permissions, environments, and limits. This interface enables you to view and manage access to all of your business groups at once instead of having to switch between each business group. - Visual representations of feature consumption for business groups, users, teams, roles, and SAML identity providers - Custom confidentiality notifications - Configurable audit log retention period - Improved audit log query performance - Ability to sync your organization with MuleSoft Composer - As part of the modern UI adoption, the following features and functions have moved: - The list of environments is now accessible from the **Business Groups** section in Access Management. - Roles are now accessible from the **Business Groups** section in Access Management. - As part of the modern UI adoption, the following features have been deprecated: - The business group picker in the Anypoint Platform navigation bar is no longer available. Select a business group from the **Business Groups** section in Access Management. ## [](#january-9-2024)January 9, 2024 ### What’s New - The Anypoint Platform Sign Up page includes the following new fields: - Job Title - Country - State/Province - Number of Employees - Industry Additionally, the **Full Name** field has been changed to **First Name** and **Last Name** fields. ## [](#november-14-2023)November 14, 2023 ### What’s New - The connected app scope assignment, `Permission changes`, now logs audits together under a single entry with the corresponding sub-action (`Add assignments`, `Replace assignments`, and `Delete assignments`) instead of multiple entries for each assignment. ## [](#september-26-2023)September 26, 2023 ### What’s New - The modern UI is now the default Access Management experience for all organizations. The modern UI provides a more accessible and intuitive user experience while enabling you to use additional features, such as custom confidentiality notifications and limits pages across Access Management. Organizations that had access to the legacy UI can switch back to it using the **Hide New Features** button until January 26, 2024. ## [](#august-28-2023)August 28, 2023 ### What’s New - A new connected apps scope, `Create BGs under a given org`, enables you to use apps that have the `client_credentials` grant type to create business groups. ## [](#july-11-2023)July 11, 2023 ### What’s New - The interface that’s used to assign permissions to users, teams, and connected apps is enhanced for improved usability. ## [](#july-10-2023)July 10, 2023 ### What’s New - For newly created organizations, audit logs now have a default retention period of one year. If your organization was created before July 10, 2023 and you did not manually change the retention period, the default retention period is still six years. ## [](#july-6-2023)July 6, 2023 ### What’s New - When an organization administrator logs in to Anypoint Platform, they are prompted to verify that their organization is compliant with impending multi-factor authentication enforcement. ## [](#june-29-2023)June 29, 2023 ### What’s New - The modern user interface is now enabled for new organizations by default. ## [](#june-6-2023)June 6, 2023 ### What’s New - The usability of the Anypoint Platform **Sign in** screen is enhanced. ## [](#may-19-2023)May 19, 2023 ### What’s New - The profile linking capability is now available for all organizations globally. ## [](#may-2-2023)May 2, 2023 ### What’s New - The `openid:google_wif` scope is now available for use with connected apps. This scope enables you to configure Anypoint as an IdP for Google Cloud by providing an `id_token` and an access token during the OAuth2 token flow for `client_credentials` connected apps. ## [](#april-26-2023)April 26, 2023 ### What’s New - The Audit Log Query endpoint now applies rate limits (`requests per minute`) per IP address that vary depending on your control plane: - US: 700 - EU: 40 - Gov: 40 ## [](#april-21-2023)April 21, 2023 ### What’s New - You can now link your SSO login to other Anypoint Platform profiles that share the same email address. An organization administrator must enable this feature. Only identity providers that use OpenID Connect are supported. This feature is available only for organizations located in the EU control plane. ## [](#march-6-2023)March 6, 2023 ### What’s New - In the Connected Apps audit logs, the `Token Retrieval Success` and `Token Retrieval Failure` entries now have `clientIP` in their payloads. ## [](#march-1-2023)March 1, 2023 ## What’s New - Access Management’s modern UI is now enabled by default for new organizations. Organizations that still use the legacy UI can migrate to the modern UI using the [**Try New Features** dialog](https://docs.mulesoft.com/jp/access-management/teams#opt-in-to-teams) in the Access Management navigation menu. ## [](#february-21-2023)February 21, 2023 ### What’s New - To enhance accessibility and usability, the Connected Apps feature’s scope workflow has been polished. ## [](#january-18-2023)January 18, 2023 ### What’s New - The following pages now have sections showing limits imposed by Anypoint Platform: - Business groups (including the page for your root organization) - Users - Teams - Roles - SAML identity providers Note that this feature is available only if you have enabled the **New Features** Access Management user interface. ## [](#december-15-2022)December 15, 2022 ### What’s New - Organization administrators can now create a custom confidentiality notification that appears when users log in to their organization. ## [](#november-30-2022)November 30, 2022 ### What’s New - The Audit Log Query API now supports more efficient querying. For more information, see [the tutorial in the Audit Logs documentation](https://docs.mulesoft.com/jp/access-management/audit-logging#paginated-logs). - For improved loading times, the pagination on the Audit Logs page has changed to display `many` instead of listing the number of entries if that number exceeds 10,000. - If your organization has not opted in to the new and improved features, Access Management now prompts you to try the new features and offers UI prompts to enable smooth adoption. - Business group overviews now have the **Access Overview** section that enables you to view a list of users who have a specified permission across business groups. - When you select a business group in the **Business Groups** page, the **Settings** section for that business group opens by default. - Sliders for vCore allocations have been readded to the **Settings** section of business groups. - To enhance usability, the Teams feature and permissions workflows have been polished. ## [](#november-14-2022)November 14, 2022 ### What’s New - Audit logs now collect and display data for the connected apps `login` action via `token retrieval success` and `token retrieval failure`. ## [](#october-29-2022)October 29, 2022 ### What’s New - Multi-factor authentication (MFA) is now required for all non-SSO user accounts unless they are on their organization’s exemption list. At login, Anypoint Platform now prompts users to configure a verification method if they have not already. - You no longer have the option to make MFA optional across your entire organization. ## [](#october-10-2022)October 10, 2022 ### What’s New - For enhanced security, Anypoint Platform now prompts non-SSO user accounts to verify their email address. ## [](#september-6-2022)September 6, 2022 ### What’s New - You can now change the retention period for your organization’s audit logs. To change audit log retention periods, you must have the Audit Log Config Manager permission over your root organization. ## [](#august-20-2022)August 20, 2022 ### What’s New - The Connected Apps feature now includes generated documentation based on supported scopes and permissions. This documentation is accessible in **Access Management** > **Connected Apps** > **Scopes Documentation** tab. ## [](#july-23-2022)July 23, 2022 ### What’s New - For enhanced security, Access Management might ask users to re-authenticate before they can modify their email addresses. Similarly, Access Management might ask organization administrators to re-authenticate before they can modify their organization users’ email addresses. This change prevents bad actors from taking advantage of stale browser sessions. - User accounts that are added to an existing organization must configure multi-factor authentication (MFA). ## [](#april-29-2022)April 29, 2022 ### What’s New - When you create a new organization, multi-factor authentication (MFA) is enabled by default. While it is best to use the Connected Apps feature instead of service accounts, an organization administrator can add service accounts or other user accounts without MFA to an exemption list. - You can now check the retention period for your organization’s audit logs using the [Audit Logging API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/audit-log-query-api/minor/1.0/console/method/%23335/). ## [](#february-21-2022)February 21, 2022 ### What’s New - You can now configure Azure Active Directory (Azure AD) as a client provider. As your client provider, Azure AD provides a stateless microservice to convert OAuth 2.0 client application registration requests to requests supported by Azure AD. Additionally, configuring Azure AD as a client provider enables you to authenticate and authorize existing API consumers. ## [](#january-14-2022)January 14, 2022 ### What’s New - When you configure the **Issuer** field while adding a client provider, such as Okta, that is compatible with [this spec](https://datatracker.ietf.org/doc/id/draft-ietf-oauth-discovery-08.html), metadata from `$ISSUER/.well-known/oauth-authorization-server` is discovered and validated prior to merging. Once the validation is complete, a complete list of available grant types appears. If you want to fetch metadata for validation for an existing client provider, save that client provider again, and the validation occurs automatically. This change makes the client provider registration process smoother for Okta users. Additionally, this change also enables the use of the Client Credentials grant type. - When you use dynamic client registration to configure a client provider, you can now configure the length of time at which a client provider times out. The minimum timeout value is five seconds, and the maximum value is 20 seconds. ## [](#november-3-2021)November 3, 2021 ### What’s New - Organization administrators can now configure up to 25 SAML 2.0 or OpenID Connect identity providers (IdPs) for single sign-on. - To support multiple external IdPs, there are new endpoints available for the Access Management API; existing identity provider configurations are unaffected. ## [](#september-8-2021)September 8, 2021 ### What’s New - In Organization settings and Runtime Manager subscription information, the name of VPN counter is now **Network Connections**. The **Network Connections** setting enables you to allocate your VPN connections and AWS Transit Gateway attachments in your organization. ## [](#august-5-2021)August 5, 2021 ### What’s New - Users who have not enabled multi-factor authentication (MFA) will be prompted to enable MFA weekly until they enable it. While MuleSoft recommends enabling MFA on all user accounts (preferably by requiring it for the entire organization), using MFA is still optional. ## [](#june-10-2021)June 10, 2021 The Teams feature provides improved user and permission management. Teams provides user grouping mechanisms in Anypoint Platform, which streamlines collaboration, reuse, and scalability. Use teams to: - Manage users and permissions across multiple business groups - Define permissions and then assign them to multiple users in one click - Set global permissions (for example, give everyone in your organization the Exchange Viewer permission) - Share Exchange assets with a specific group of users Additionally, the Access Management navigation menu and user interface have been revamped to simplify navigation and permission management across business groups. Enhancements and updates are available on an opt-in basis. You can continue using old views after the Teams feature and user interface enhancement release. ## [](#january-20-2021)January 20, 2021 When you change your password, you can no longer reuse your previous three passwords. ## [](#december-15-2020)December 15, 2020 If you are using an external identity provider, such as Okta or Salesforce, you can now map users in a federated organization’s OpenID Connect (OIDC) groups to roles in Anypoint Platform. ## [](#october-29-2020)October 29, 2020 - You can now enable multi-factor authentication (MFA) as a sign-in requirement across your entire organization. MFA makes logging in to Anypoint Platform more secure. - You can now easily rotate SAML 2.0 SSO keys. You can generate a key or upload an existing public/private key pair. ## [](#june-29-2020)June 29, 2020 You can now import SAML 2.0 metadata to configure your identity provider with Anypoint Platform. ## [](#june-13-2020)June 13, 2020 You can now export service provider SAML 2.0 metadata to configure Anypoint Platform with your identity provider. ## [](#may-30-2020)May 30, 2020 These are the enhancements and new features for Access Management. - Organization administrators can configure whether SAML SSO can be initiated by Anypoint Platform (service provider-initiated SSO), their external identity provider (identity provider-initiated SSO), or both. - You can now log in using SSO from the Anypoint Platform login page via your organization’s domain. This domain is available on your user profile page. - When the permission scopes change for an approved connected app, an organization administrator must approve the new set of scopes. ## [](#january-24-2020)January 24, 2020 Anypoint Platform now includes an External Access feature that serves as the foundation for improved cross-organization collaboration such as the sharing of assets. ## [](#october-18-2019)October 18, 2019 This release of Access Management provides increased security and development capabilities via the Connected Apps feature. The Connected Apps feature enables you to delegate access to apps without sharing sensitive credentials or giving third parties full control of their accounts. You can audit the app’s use of data, and you can revoke access anytime. With this release, developers can create apps that use a **Sign in with Anypoint Platform** widget. When users interact with this widget, they can authorize apps to access their Anypoint Platform information. Actions taken by apps are audited. Note that some products do not currently include client IDs in this release of the Connected Apps feature. ## [](#april-20-2019)April 20, 2019 These are the enhancements and new features for Access Management: - A VPN counter is added under Business Group settings to allow a fine-grained allocation of purchased VPNs within your organizations. - Audit log dates now display a timestamp for a year. - When configuring an external identity provider, users can now disable server certificate validation. See [Configure OpenID Connect Client Management](https://docs.mulesoft.com/jp/access-management/configure-client-management-openid-task). - Enablement of non-SSO users for your organization allows organization administrators to invite and authenticate users outside of the external SSO configured for your organization. - Organization administrators can enable and disable automapper capability for Flow Designer under the organization settings in Access Manager. See the Flow Designer documentation for more information. - You can enable client deletion in Anypoint Platform, which allows deletions of clients within Anypoint Platform. See [Configure OpenID Connect Client Management](https://docs.mulesoft.com/jp/access-management/configure-client-management-openid-task). - You can enable client deletion and updates in IdP, which allows updates and deletions of external clients in the configured IdP through an outbound call made by Anypoint Platform. To use this feature, you should opt-in to client deletion within Anypoint Platform. - The Audit Log screen and a downloadable CSV file now include environment names for events from API Manager, Runtime Manager, CloudHub, Partner Manager, and MQ. ## [](#august-25-2018)August 25, 2018 **_Version 0.46.0_** MuleSoft supports using [Salesforce Identity](https://trailhead.salesforce.com/content/learn/modules/identity_basics) as a SSO (single sign-on) provider with the [OpenID Connect](https://openid.net/developers/how-connect-works/) protocol. Salesforce is a [certified OpenID Provider](https://openid.net/certification/). ### [](#deprecated-functionality)Deprecated Functionality - Deleted federated users are no longer able to sign in from the SSO login page. Organization administrators must re-enable deleted users before they can continue operations on Anypoint Platform. - You can’t create a Business Group name using special characters. Only the following characters are valid: - Letter - Number - Apostrophe - Space - Comma - Period - Hyphen - Underscore Existing Business Groups whose names contain special characters aren’t affected. ## [](#november-18-2017)November 18, 2017 **_Version 0.29.0_** Access Management v0.29.0 enables external Anypoint users to create client applications on public API portals. These external users will be shown under a New tab for external users in the Users section of the Access Management UI. This release also includes infrastructure changes that improve platform performance. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility NA ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ### [](#resolved-issues)Resolved Issues None. ### [](#migration-guidance)Migration Guidance No migration required. ## [](#october-7-2017)October 7, 2017 **_Version 0.27.0_** Access Management v0.27.0 supports identity providers, such as Okta, that are compliant with the OpenID Connect Dynamic Client Registration protocol for API Client Management. You can now use these providers to protect API Gateways through a generic access token enforcement policy. This release also includes infrastructure improvements to help with performance. For more information, see the [client management documentation](https://docs.mulesoft.com/jp/access-management/managing-api-clients). ## [](#june-24-2017)June 24, 2017 **_Version 0.23.1_** Access Management v0.23.1 enhances the user experience for configuring external identity forms through tooltips and form validation mechanisms. It provides several infrastructure improvements. MuleSoft has also validated our OpenID Connect SSO solution with Okta, OpenAM, and Ping Federate. ### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#compatibility-2)Compatibility NA ### [](#deprecated-features-or-functionality-2)Deprecated Features or Functionality None. ### [](#resolved-issues-2)Resolved Issues None. ### [](#migration-guidance-2)Migration Guidance No migration required. ## [](#may-6-2017)May 6, 2017 **_Version 0.22.0_** Access Management v0.22 supports OpenID Connect-compliant identity providers (IdPs) for Single Sign On to Anypoint Platform. Through a new UI for external identity configurations, this release also brings the client UI configuration forms for PingFederate and OpenAM into the platform. ### [](#hardware-and-software-requirements-3)Hardware and Software Requirements No change ### [](#compatibility-3)Compatibility N/A ### [](#deprecated-features-or-functionality-3)Deprecated Features or Functionality The process for OAuth client management configuration is now self-serve through forms made available in the External Identity section of Access Management. The google forms for OpenAM and PingFederate configuration are now deprecated. ### [](#resolved-issues-3)Resolved Issues None ### [](#migration-guidance-3)Migration Guidance No migration required ## [](#january-14-2017)January 14, 2017 **_Version 0.18.0_** Access Management v0.18 adds a [no CAPTCHA reCAPTCHA](https://cloud.google.com/security/products/recaptcha) verification step in our [sign up process](https://docs.mulesoft.com/jp/access-management/managing-your-account#how-to-create-your-account). ### [](#hardware-and-software-requirements-4)Hardware and Software Requirements No change. ### [](#compatibility-4)Compatibility NA ### [](#deprecated-features-or-functionality-4)Deprecated Features or Functionality None. ### [](#resolved-issues-4)Resolved Issues None. ### [](#migration-guidance-4)Migration Guidance No migration required. ## [](#november-19-2016)November 19, 2016 **_Version 0.17.0_** Access Management v0.17 is a minor release that addresses some marketing requirements in our platform. ### [](#hardware-and-software-requirements-5)Hardware and Software Requirements No change. ### [](#compatibility-5)Compatibility NA ### [](#deprecated-features-or-functionality-5)Deprecated Features or Functionality None. ### [](#resolved-issues-5)Resolved Issues None. ### [](#migration-guidance-5)Migration Guidance No migration required. ## [](#october-22-2016)October 22, 2016 **_Version 0.16.0_** Access Management v0.16 allows **Organization administrators** and **Audit Log Viewers** to view entitlement changes to their organization from the [Audit Logs UI](https://docs.mulesoft.com/jp/access-management/audit-logging). Additionally, Access Management now supports Ping Federate v8.2.1.1 for [External Identity](https://docs.mulesoft.com/jp/access-management/external-identity). ### [](#hardware-and-software-requirements-6)Hardware and Software Requirements No change. ### [](#compatibility-6)Compatibility NA ### [](#deprecated-features-or-functionality-6)Deprecated Features or Functionality None. ### [](#resolved-issues-6)Resolved Issues None. ### [](#migration-guidance-6)Migration Guidance No migration required. ## [](#september-24-2016)September 24, 2016 **_Version 0.15.0_** Access Management v0.15 improves the user invitation experience and allows users to accept organization invitations with an existing Anypoint username. If a user has different usernames associated with an email address and receives an invitation to a new organization, the user is now given the option to accept the invitation with any one of her existing accounts, thereby, associating the selected username with this new organization. If the selected username is already associated with another Anypoint organization, the user is then given the option to detach this username from the existing organization. If she is the only user in that org, she is also given the ability to delete that organization as usernames must remain unique across all Anypoint organizations. At any stage in the invite process, she can always chose to create a new username. ### [](#hardware-and-software-requirements-7)Hardware and Software Requirements No change. ### [](#compatibility-7)Compatibility NA ### [](#deprecated-features-or-functionality-7)Deprecated Features or Functionality None. ### [](#resolved-issues-7)Resolved Issues None. ### [](#migration-guidance-7)Migration Guidance No migration required. ## [](#august-27-2016)August 27, 2016 **_Version 0.14.0_** The Access Management V0.14.0 release makes minor improvements to Anypoint Platform’s notifications about your Trial subscription period. If you are in your 30 day trial period, you can see the expiration date under the **Subscription** section in the Access Management UI. After your trial period expires your account will be converted to a “Free” subscription tier where you will lose the ability to deploy apps and APIs along with other Enterprise functionality within Anypoint Platform. You will still be able to login to your account. ### [](#hardware-and-software-requirements-8)Hardware and Software Requirements No change. ### [](#compatibility-8)Compatibility NA ### [](#deprecated-features-or-functionality-8)Deprecated Features or Functionality None. ### [](#resolved-issues-8)Resolved Issues None. ### [](#migration-guidance-8)Migration Guidance No migration required. ## [](#june-25-2016-release)June 25, 2016 Release **_Version 0.13.0_** The Access Management V0.13.0, is a minor release that fixes a few bugs improving the platform’s performance. ### [](#hardware-and-software-requirements-9)Hardware and Software Requirements No change. ### [](#compatibility-9)Compatibility NA ### [](#deprecated-features-or-functionality-9)Deprecated Features or Functionality None. ### [](#resolved-issues-9)Resolved Issues None. ### [](#migration-guidance-9)Migration Guidance No migration required. ## [](#may-14-2016-release)May 14, 2016 Release **_Version 0.12.0_** The Access Management V0.12.0, is a minor release that makes the Audit Logs UI a GA functionality. Using this UI users can query and filter Audit logs. ### [](#hardware-and-software-requirements-10)Hardware and Software Requirements No change. ### [](#compatibility-10)Compatibility NA ### [](#features-and-functionality)Features and Functionality Audit Logs UI for Anypoint Platform: Changes made by users within an Anypoint Platform organization are logged through an audit logging service. You can now access the data logs through the Audit Logs UI under Access Management or by leveraging the Audit Logging Query API. See Audit Logs. ### [](#deprecated-features-or-functionality-10)Deprecated Features or Functionality None. ### [](#resolved-issues-10)Resolved Issues None. ### [](#migration-guidance-10)Migration Guidance No migration required. ## [](#see-also)See Also - [アクセス管理について](https://docs.mulesoft.com/jp/access-management/) - [アクセス管理をトラブルシューティングする](https://docs.mulesoft.com/jp/access-management/troubleshoot-access-management) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint API Community Manager Release Notes Use Anypoint API Community Manager to build and operate communities around your APIs for developers and partners, both inside and outside of your organization, who write applications that use your APIs. Update manually to version 2.2.0 or later to enable receiving automatic scheduled updates to the latest version. These dates are subject to change.
Release Version Sandbox Environment Auto-Update Production Environment Auto-Update

January 2026

2.31.0

January 5, 2026

January 10, 2026

June 2026

2.35.0

June 1, 2026

June 4, 2026
Because API Community Manager follows the standard support policy for MuleSoft cloud offerings, only the latest version of API Community Manager 2.x is supported. Additionally, API Community Manager 1.x reached End of Life (EOL) on August 14, 2021. ## [](#june-2026)June 2026 Anypoint API Community Manager Package Version: 2.35.0 Download the managed package for this release from this location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3cw](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3cw) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3cw](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3cw) ### What’s New - This release includes minor infrastructure and performance updates. ## [](#january-2026)January 2026 Anypoint API Community Manager Package Version: 2.31.0 Download the managed package for this release from this location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3OZ](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3OZ) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3OZ](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D3OZ) ### Fixed Issues
Issue Resolution ID

Workflow Rules and Process Builder are retired as of December 31, 2025. Migrate existing automation to Flow Builder.

W-19336473
## [](#october-2025)October 2025 Anypoint API Community Manager Package Version: 2.29.0 Download the managed package for this release from this location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq) ### Fixed Issues
Issue Resolution ID

Manual-approve contracts now create successfully without showing an error when you create a second contract in a different asset instance.

W-19594858
## [](#august-2025)August 2025 Anypoint API Community Manager Package Version: 2.29.0 Download the managed package for this release from this location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2eq) ### Fixed Issues
Issue Resolution ID

Asset icons now show as expected.

W-18706927 and W-19155848

In the API Console, specs no longer show duplicated back-slashes or quotes in examples.

W-18736958 and W-19012689
## [](#july-2025)July 2025 Anypoint API Community Manager Package Version: 2.28.0 Download the managed package for this release from this location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2bw](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2bw) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2bw](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2bw) ### What’s New - The API Header Lightning component has a new parameter. Administrators can now select the **Disable Request Access Anypoint Email** parameter to disable emails sent from Anypoint when a contract is approved or revoked. For more information, see [API Header](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#api-header). - You can now use the new Tab Layout Lightning component in place of the Tabs component for better performance. For more information, see [Tab Layout](https://help.salesforce.com/s/articleView?id=experience.rss_tabs.htm&type=5). ## [](#june-2025)June 2025 Anypoint API Community Manager Package Version: 2.27.0 Download the managed package for this release from this location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2MC](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2MC) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2MC](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2MC) ### Fixed Issues
Issue Resolution ID

Duplicate branded emails are no longer sent when contracts are approved or revoked.

W-18623114
## [](#april-2025)April 2025 Anypoint API Community Manager Package Version: 2.26.0 Download the managed package for this release from this location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2GYIA0](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2GYIA0) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2GYIA0](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D2GYIA0) ### Fixed Issues
Issue Resolution ID

The search now searches in HTTP and evented API documentation.

W-18097110

The search now has a feedback spinner when a search is in progress.

W-18218251
## [](#march-2025)March 2025 Download the managed package for this release from the following location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D23iIAC](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D23iIAC) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D23iIAC](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D23iIAC) ### Fixed Issues
Issue Resolution ID

The search box component now searches API documentation in child business groups.

W-17099315
## [](#december-2024)December 2024 ### What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) ## [](#october-2024)October 2024 Download the managed package for this release from the following location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D22BIAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D22BIAS) - For sandbox environments: - [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D1xaIAC](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D1xaIAC) ### What’s New - The self-registration approval process is updated to prevent automatic approval of new users. For more information, see [Require Admin Approval for Guest Registration](https://docs.mulesoft.com/jp/api-community-manager/create-community#require-admin-approval-for-guest-registration). - API Community Manager now includes the latest version of the API Console. - You can now view AsyncAPI 2.6 specifications with Avro schemas to share, discover, and reuse within your organization. To learn about the AsyncAPI journey, see [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). ### Fixed Issues
Issue Resolution ID

Self-registration no longer automatically approves new users if an admin’s approval is required.

W-16796717

When a request takes more time than other requests, the response for all requests are no longer delayed.

W-16606519
## [](#august-2024)August 2024 ### What’s New - The analytics tooling is changing to Anypoint Monitoring on September 25, 2024. To continue to view the metrics of an application from the **My Applications** details page, you must add the Monitoring Viewer permission from Access Management. For more information, see: - [インストールの前提条件](https://docs.mulesoft.com/jp/api-community-manager/installation-prerequisites) - [Managing Client Contracts](https://docs.mulesoft.com/jp/api-community-manager/client-apps-contracts#managing-client-apps-and-contracts) - [Application Analytics Graph](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#application-analytics-graph) - [アプリケーションのメトリクスが表示されない](https://docs.mulesoft.com/jp/api-community-manager/troubleshooting-metrics-not-showing-for-applications) ## [](#june-2024)June 2024 **Anypoint API Community Manager Package Version: 2.22.0** Download the managed package for this release from the following location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D1wNIAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D1wNIAS) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D1wNIAS](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKe000000D1wNIAS) ### What’s New - API Community Manager now includes the latest version of the API Console. - You can now view AsyncAPI 2.6 specifications to discover and reuse within your organization. To learn about the AsyncAPI journey, see [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). ### Fixed Issues
Issue Resolution ID

API Console mocking service now accepts certificates with any valid name.

W-15715586
### Known Issues
Known Issue Workaround ID

The guest and member user profiles contain the Exchange Viewer permission that gives access to all assets in Exchange with this visibility. An impersonated guest user can potentially exploit this visibility and access assets that are not intended for them.

For more information, see api-community-manager::troubleshooting-avoid-a-potential-security-vulnerability.adoc.

N/A

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#may-2024)May 2024 **Anypoint API Community Manager Package Version: 2.21.0** Download the managed package for this release from the following location: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKmwQAG](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKmwQAG) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKmwQAG](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKmwQAG) ### Fixed Issues
Issue Resolution ID

Diagnostic tools are updated to use the Salesforce v60 Metadata API.

W-15546944

In the API Console, the mocking URL now displays as expected when selecting different endpoints.

W-15125368
### Known Issues
Known Issue Workaround ID

The guest and member user profiles contain the Exchange Viewer permission that gives access to all assets in Exchange with this visibility. An impersonated guest user can potentially exploit this visibility and access assets that are not intended for them.

For more information, see api-community-manager::troubleshooting-avoid-a-potential-security-vulnerability.adoc.

N/A

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#march-2024)March 2024 **Anypoint API Community Manager Package Version: 2.20.0** Use these managed package links for downloads: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiZQAW](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiZQAW) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiZQAW](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiZQAW) ### Fixed Issues
Issue Resolution ID

Instances now display in the API Details page as expected.

W-15052796

In the API Catalog, selecting a filter option now works as expected.

W-15080316
### Known Issues
Known Issue Workaround ID

The guest and member user profiles contain the Exchange Viewer permission that gives access to all assets in Exchange with this visibility. An impersonated guest user can potentially exploit this visibility and access assets that are not intended for them.

For more information, see api-community-manager::troubleshooting-avoid-a-potential-security-vulnerability.adoc.

N/A

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#february-2024)February 2024 **Anypoint API Community Manager Package Version: 2.19.0** Use these managed package links for downloads: - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiAQAW](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiAQAW) - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiAQAW](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKiAQAW) ### Fixed Issues
Issue Resolution ID

The Scopes parameter in the payload is no longer missing when requesting access.

W-14795167

An error message now displays while adding an asset when the maximum storage limit is reached.

W-14722281

API Community Manager now includes the latest version of the API Console.

W-14979707

In the API Console, Design Center now generates JSON with nested objects for OAS 3.0.

W-14278539

AsyncAPI examples now appear in the API Console.

W-14588829

XML examples now show in REST APIs for OAS.

W-14651311
### Known Issues
Known Issue Workaround ID

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#january-2024)January 2024 **Anypoint API Community Manager Package Version: 2.18.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKgYQAW](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKgYQAW) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKgYQAW](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002GKgYQAW) ### Fixed Issues
Issue Resolution ID

API documentation now displays as expected.

W-12598552

The API Curator now contains a scroll bar when displaying an API with more than four versions.

W-14719778
### Known Issues
Known Issue Workaround ID

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#november-2023)November 2023 **Anypoint API Community Manager Package Version: 2.17.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/?ec=302&startURL=/packaging/installPackage.apexp?p0%3D04t4P000002GKfGQAW](https://test.salesforce.com/?ec=302&startURL=/packaging/installPackage.apexp?p0%3D04t4P000002GKfGQAW) - For production environments: [https://login.salesforce.com/?ec=302&startURL=%2Fpackaging%2FinstallPackage.apexp%3Fp0%3D04t4P000002GKfGQAW](https://login.salesforce.com/?ec=302&startURL=%2Fpackaging%2FinstallPackage.apexp%3Fp0%3D04t4P000002GKfGQAW) ### Fixed Issues
Issue Resolution ID

In the API Console, the example for an API is no longer missing.

W-14102462

In the API Console, an unexpected Content type header is no longer added to a GET request when a POST request was sent previously during the same browser session.

W-13959789

The Preview your Site button is now working properly.

W-14145755
### Known Issues
Known Issue Workaround ID

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

API documentation is not displayed.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#september-2023)September 2023 **Anypoint API Community Manager Package Version: 2.16.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPlwQAE](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPlwQAE) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPlwQAE](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPlwQAE) ### Fixed Issues
Issue Resolution ID

In the API Console, the child property no longer displays mandatory fields.

W-13772034

In the API Console, the query parameters are now rendering properly and the parameter value box is no longer hidden.

W-13813608

In the API Console, a new error message now displays for error code 0.

W-13957966
### Known Issues
Known Issue Workaround ID

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

API documentation does not display.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#august-2023)August 2023 **Anypoint API Community Manager Package Version: 2.15.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZMQAY](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZMQAY) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZMQAY](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZMQAY) ### Fixed Issues
Issue Resolution ID

In the API Console, the Authorization header is no longer missing from the request.

W-13755140
### Known Issues
Known Issue Workaround ID

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

API documentation does not display.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#july-2023)July 2023 **Anypoint API Community Manager Package Version: 2.14.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZ2QAI](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZ2QAI) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZ2QAI](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvZ2QAI) ### Fixed Issues
Issue Resolution ID

The API Console components now work as expected.

W-1346993

All the fields in RAML specifications no longer display as required.

W-13544586
### Known Issues
Known Issue Workaround ID

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

API documentation does not display.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#june-2023)June 2023 **Anypoint API Community Manager Package Version: 2.12.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvWSQAY](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvWSQAY) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvWSQAY](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvWSQAY) ### What’s New - The Salesforce metadata and enterprise JARs are updated using Salesforce Organization v57. ### Known Issues
Known Issue Workaround ID

The guest and member permission sets are automatically assigned and cannot be disabled.

W-13198180

API documentation does not display.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#may-2023)May 2023 **Anypoint API Community Manager Package Version: 2.11.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002OxwTQAS](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002OxwTQAS) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002OxwTQAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002OxwTQAS) ### Fixed Issues
Issue Resolution ID

The request handler for the API Console is behaving as expected. When the Browser Requests Enabled option is selected, access tokens and other requests go through the browser. When the option is not selected, the requests go through Apex.

W-12776683

You can now publish API groups as child APIs.

W-13088893 and W-13138467
### Known Issues
Known Issue Workaround ID

API documentation does not display.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#april-2023)April 2023 **Anypoint API Community Manager Package Version: 2.10.4** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPelQAE](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPelQAE) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPelQAE](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPelQAE) ### Fixed Issues
Issue Resolution ID

The request access token is now working as expected with an implicit OAuth 2.0 flow.

W-12227877
### Known Issues
Known Issue Workaround ID

API documentation does not display.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#march-2023)March 2023 **Anypoint API Community Manager Package Version: 2.10.3** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPeWQAU](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPeWQAU) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPeWQAU](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002bPeWQAU) ### Fixed Issues
Issue Resolution ID

The mocking service now receives the Content-Type as multipart/form-data when sending the request for the /storage/file/add endpoint.

W-12146715

An asset description that is longer than two lines now displays correctly.

W-12277575

The navigation panel of the API Console now displays correctly when the request panel is expanded or collapsed.

W-12280580

From the Request Access screen, selecting an SLA tier now works as expected.

W-12386522

The API Console is now updated to 6.6.27 to resolve an issue with Boundary missing from multipart content-type headers.

W-12473066
### Known Issues
Known Issue Workaround ID

API documentation does not display.

Go to Setup > Session Settings and uncheck Use Lightning Web Security for Lightning web components (GA) and Aura components (Beta).

W-12598552

The mocking service does not work when a multi-part request is sent.

W-12625052

Guest users cannot view Community APIs.

W-11178590
## [](#february-2023)February 2023 **Anypoint API Community Manager Package Version: 2.10.2** ### Fixed Issues
Issue Resolution ID

The mocking service now receives the Content-Type as multipart/form-data when sending the request for the /storage/file/add endpoint.

W-12146715

An asset description that is longer than two lines now displays correctly.

W-12277575

The navigation panel of the API Console now displays correctly when the request panel is expanded or collapsed.

W-12280580

From the Request Access screen, selecting a SLA tier now works as expected.

W-12386522

The API Console is now updated to 6.6.27 to resolve an issue with Boundary missing from multipart content-type headers.

W-12473066
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590
**Anypoint API Community Manager Package Version: 2.9.5** To download the managed package for sandbox environments, use this link: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A9JEQA0](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A9JEQA0) ### Fixed Issues
Issue Resolution ID

An asset description that is longer than two lines now displays correctly.

W-12277575

The navigation panel of the API Console now displays correctly when the request panel is expanded or collapsed.

W-12280580

From the Request Access screen, selecting a SLA tier now works as expected.

W-12386522

The API Console is now updated to 6.6.27 to resolve an issue with Boundary missing from multipart content-type headers.

W-12473066

The mocking service now receives the correct Content-Type as multipart/form-data when sending the request for the endpoint /storage/file/add.

W-12146715
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590
## [](#january-2023)January 2023 **Anypoint API Community Manager Package Version: 2.9.3** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A9DkQAK](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A9DkQAK) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A9DkQAK](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A9DkQAK) ### Fixed Issues
Issue Resolution ID

The API Console no longer gives an error when accessing an endpoint.

W-12126979

The API Console now shows all response objects.

W-12138301

The Request Access screen no longer scrolls up when clicking items from the screen.

W-12218778
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590
## [](#november-2022)November 2022 **Anypoint API Community Manager Package Version: 2.9.2** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A93YQAS](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A93YQAS) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A93YQAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A93YQAS) ### Fixed Issues
Issue Resolution ID

Client credentials can now be sent using Apex code.

W-11793957

You can now try out OAuth (Okta) enabled Anypoint APIs in the API Community Management portal.

W-11889482
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590
## [](#october-2022)October 2022 **Anypoint API Community Manager Package Version: 2.9.1** To download the managed package for production environments, use this link: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A93TQAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A93TQAS) ### Fixed Issues
Issue ID

Branded emails are now working for API Groups.

W-11785031

Changing the visibility of a group immediately after it is created is now working as expected.

W-10758951
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590
**Anypoint API Community Manager Package Version: 2.9.0** To download the managed package for sandbox environments, use this link: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002mcv6QAA](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002mcv6QAA) ### Fixed Issues
Issue ID

An error no longer displays in the Application Details page for a selected application.

W-11739869

Child APIs now display for API groups.

W-11797215
### Known Issues
Known Issue Workaround ID

Branded emails are not working for API Groups.

W-11785031

Guest users cannot view Community APIs.

W-11178590

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951
## [](#september-2022)September 2022 **Anypoint API Community Manager Package Version: 2.8.3** To download the managed package for production environments, use this link: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo4CQAQ](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo4CQAQ) ### Fixed Issues
Issue ID

After a new release, permission sets are no longer assigned automatically to an existing guest.

W-11644522

Contracts email notifications now send one mail per API application.

W-11606316
### Known Issues
Known Issue Workaround ID

Branded emails are not working for API Groups.

W-11785031

Guest users cannot view Community APIs.

W-11178590

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951
**Anypoint API Community Manager Package Version: 2.8.2** To download the managed package for sandbox environments, use this link: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo42QAA](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo42QAA) ### Fixed Issues
Issue ID

Salesforce owner no longer receives an email for an error tracking user login message.

W-1139855

The API Documentation Viewer is now displaying properly.

W-11637585
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951
## [](#august-2022)August 2022 **Anypoint API Community Manager Package Version: 2.8.1** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo3dQAA](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo3dQAA) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo3dQAA](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qo3dQAA) ### Fixed Issues
Issue ID

The behavior for downloading an API specification now works as expected.

W-11435372
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951
## [](#july-2022)July 2022 **Anypoint API Community Manager Package Version: 2.8.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002fQVSQA2](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002fQVSQA2) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002fQVSQA2](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002fQVSQA2) ### Fixed Issues
Issue ID

The Apex CPU time limit no longer exceeds when searching for APIs.

W-10910613
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951
## [](#june-2022)June 2022 **Anypoint API Community Manager Package Version: 2.7.2** - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002XGnSQAW](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002XGnSQAW) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002XGnSQAW](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002XGnSQAW) ### Fixed Issues
Issue ID

The error message was updated to specify more administrator permissions are necessary.

W-11096730

Branded emails no longer fail when the API Community Manager package is updated.

W-10831783

The administrator profile is now updated in the push upgrade process.

W-10521730
### Known Issues
Known Issue Workaround ID

Guest users cannot view Community APIs.

W-11178590

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951
## [](#may-2022)May 2022 **Anypoint API Community Manager Package Version: 2.7.1** Use this link to download the managed package of the production environment: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002XGnIQAW](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002XGnIQAW) ### Known Issues
Known Issue Workaround ID

When the API Community Manager package is updated, the AnyPointContracts entity is removed from the Salesforce change data capture functionality. Branded emails fail as a result.

Manually add the AnyPointContracts entity in the change data capture. See Configure Data Change Capture for more information.

W-10831783

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
**Anypoint API Community Manager Package Version: 2.7.0** Use this link to download the managed package of the sandbox environment: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002fQUAQA2](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002fQUAQA2) ### What’s New - API Console 6.6.13 - This release now uses the following permission sets to define visibility and access to the external objects part of the ACM package instead of using the user profiles. - ACM Administrator User - ACM Guest User - ACM Member User ### Fixed Issues
Issue ID

Markdown links work properly.

W-10866375

Asset versions with hyphens are working properly.

W-10915042

Creating an application for a group with an IDP now displays the grant types selection.

W-10964207

The View asset in Exchange button now displays.

W-11017253
### Known Issues
Known Issue Workaround ID

When the API Community Manager package is updated, the AnyPointContracts entity is removed from the Salesforce change data capture functionality. Branded emails fail as a result.

Manually add the AnyPointContracts entity in the change data capture. See Configure Data Change Capture for more information.

W-10831783

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
## [](#april-2022)April 2022 **Anypoint API Community Manager Package Version: 2.6.1** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8qyQAC](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8qyQAC) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8qyQAC](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8qyQAC) ### Known Issues
Known Issue Workaround ID

When the API Community Manager package is updated, the AnyPointContracts entity is removed from the Salesforce change data capture functionality. Branded emails fail as a result.

Manually add the AnyPointContracts entity in the change data capture. See Configure Data Change Capture for more information.

W-10831783

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
**Anypoint API Community Manager Package Version: 2.6.0** To download the managed package for sandbox environments, use this link: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002T7EAQA0](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002T7EAQA0) ### What’s New - API Console is updated to 6.6.10 - API Community Manager collects product metrics with the consent of the administrator ### Fixed Issues
Issue ID

SOQL query limit was reached error message requesting access no longer displays.

W-10802345
### Known Issues
Known Issue Workaround ID

When the API Community Manager package is updated, the AnyPointContracts entity is removed from the Salesforce change data capture functionality. Branded emails fail as a result.

Manually add the AnyPointContracts entity in the change data capture. See Configure Data Change Capture for more information.

W-10831783

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
## [](#march-2022)March 2022 **Anypoint API Community Manager Package Version: 2.5.3** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvCrQAI](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvCrQAI) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvCrQAI](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvCrQAI) ### Fixed Issues
Issue ID

Branded emails no longer fail when there are multiple communities with branded email configurations.

W-10721244

Email notifications are now sent using the HTML template when available.

W-10795587
### Known Issues
Known Issue Workaround ID

When the API Community Manager package is updated, the AnyPointContracts entity is removed from the Salesforce change data capture functionality. Branded emails fail as a result.

Manually add the AnyPointContracts entity in the change data capture. See Configure Data Change Capture for more information.

W-10831783

Changing the visibility of a group immediately after it is created might fail.

Wait a few seconds before editing the group and clicking Apply.

W-10758951

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
**Anypoint API Community Manager Package Version: 2.5.2** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvChQAI](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvChQAI) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvChQAI](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvChQAI) ### Known Issues
Known Issue Workaround ID

Branded emails fail when there are multiple communities with branded email configurations. Changing the visibility of a group immediately after it is created may not work successfully.

Wait a few seconds before editing the group and clicking Apply.

W-10721244

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
## [](#february-2022)February 2022 **Anypoint API Community Manager Package Version: 2.5.1** To download the managed package for sandbox environments, use this link: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvCXQAY](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002uvCXQAY) ### Fixed Issues
Issue ID

Requesting access for an API with non-managed instances does not produce an error.

W-10554322

Learn More option is now accessible.

W-10554372

Request Access button remains disabled until required fields are entered.

W10555732 and W-10554325
### Known Issues
Known Issue Workaround ID

Not receiving emails when request to access an API is approved and when a contract status changes.

W-10647533

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
## [](#january-2022)January 2022 **Anypoint API Community Manager Package Version: 2.5.0** To download the managed package for sandbox environments, use this link: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002T70kQAC](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002T70kQAC) ### What’s New - The API curator enables you to: - View APIs in your site and APIs in Exchange, with detailed information about each API and improved searching and filtering. - Add single APIs or multiple APIs from Exchange to your site. - Remove single APIs or multiple APIs from your site. - Edit the name, description, and visibility of APIs on your site, and the visibility of the instances in each API. - The member management interface shows: - A searchable list of current members, with the option to disable and enable their accounts. - A searchable list of requests for access submitted through the member sign-up form, with the options to approve a request, reject a request, show rejected requests, and undo a rejection by retrieving a rejected request. - The API Engagement component shows the number of likes and subscriptions for an API and enables users to like and subscribe to the API. - The User Subscriptions custom component shows users their API subscriptions and the option to unsubscribe from each API. - The User Settings custom component enables users to configure notification settings and control what emails they receive. - The API Header component shows an email address to contact with questions about the API. This contact email is set for each API in Anypoint Exchange. ### Known Issues
Known Issue Workaround ID

The administrator profile is not updated in the push upgrade process.

Manually update the administrator profile. See Upgrades for more information.

W-10521730
## [](#december-2021)December 2021 **Anypoint API Community Manager Package Version: 2.4.4** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eOQAS](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eOQAS) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eOQAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eOQAS) ### Fixed Issues
Issue ID

Client credential fields are preserved after you modify a header field.

AAP-2825

Selecting documentation pages in the API Console works correctly.

AAP-2824

Editing the API Console component works without errors.

AAP-2821

The Spec Downloader component displays the download button correctly when OAS3 is selected in the Download Spec Options menu.

AAP-2802
## [](#november-2021)November 2021 **Anypoint API Community Manager Package Version: 2.4.3** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eJQAS](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eJQAS) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eJQAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000000A8eJQAS) ### Fixed Issues
Issue ID

When no identity provider is defined in your Anypoint Platform organization, guided setup shows an improved error message.

AAP-2756
### Known Issues
Known Issue ID

After you select an operation and populate the credentials, clicking the same operation in the navigation resets the credentials.

AAP-2714

By default, each API displays all applications rather than only the applications that have contracts with that API’s instances.

AAP-2713
## [](#october-2021)October 2021 **Anypoint API Community Manager Package Version: 2.4.0** Use these managed package links for downloads: - For sandbox environments: [https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qnqYQAQ](https://test.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qnqYQAQ) - For production environments: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qnqYQAQ](https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4P000002qnqYQAQ) ### What’s New - API Console is updated from 6.6.1 to 6.6.5, including general bug fixes and improvements described in the [API Console release notes](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes). - When an application specification has annotations for the `clientId` and `clientSecret` credentials, the API Console request editor enables populating the credentials from the application. - When you select the option `Enable advance links` in the components `ACM Search Box` and `ACM Search Result`, and a user’s search results show a matching API endpoint, clicking the result opens the API details page with the API console tab selected and the matching endpoint expanded. ### Fixed Issues
Issue ID

Zip files from the component SpecDownloader include the folder exchange_modules.

AAP-2658

When some items fail in a search, the search still shows results from all available items without errors.

AAP-2647

When the latest version of an API does not match a search and an earlier version does, the search results link to the latest matching version.

AAP-2646

API details correctly highlight custom fields.

AAP-2645

Searches process and show custom field values but not custom field keys.

AAP-2644

Inline search supports the use of keyboard arrow keys to move between links.

AAP-2643

Notification emails with custom branding work correctly in current and previous versions of API Community Manager, including sending emails to more than 20 contacts without errors, and instantiating variables in email subjects.

AAP-2458, AAP-2639
### Known Issues
Known Issue ID

After you select an operation and populate the credentials, clicking the same operation in the navigation resets the credentials.

AAP-2714

By default, each API displays all applications rather than only the applications that have contracts with that API’s instances.

AAP-2713
## [](#september-2021)September 2021 ### [](#anypoint-api-community-manager-package-version-2-2-5)Anypoint API Community Manager Package Version: 2.2.5 There are no known issues in this release. #### [](#new-features)New Features - API Console is updated from 6.5.0 to 6.6.1, including general bug fixes and improvements described in the [API Console release notes](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes). - API Console supports non-managed instances. (AAP-2376) #### [](#fixed-issues-38)Fixed Issues - The diagnostics tool includes more properties and metadata types. (AAP-2480) - Values of `timePeriodInMilliseconds` larger than 2147483647 work correctly. (AAP-2450) - `AnypointApiPages` gets information from the latest patch version, so that documentation pages display correctly. (AAP-2427) - The request panel sends credential headers correctly regardless of endpoint changes. (AAP-2422) - API Catalog advanced search correctly applies complex filters such as filters with values for multiple categories. (AAP-2344) - Method calls executed in the API Console Documentation panel work correctly. (AAP-2518) - Business groups display correctly and not as "unknown" in current and previous versions of API Community Manager. (SE-23151) ## [](#august-2021)August 2021 ### [](#anypoint-api-community-manager-package-version-2-2-3)Anypoint API Community Manager Package Version: 2.2.3 There are no new features or known issues in this release. #### [](#fixed-issues-39)Fixed Issues - All community pages render correctly for guest users. ## [](#july-2021)July 2021 ### [](#anypoint-api-community-manager-package-version-2-2-2)Anypoint API Community Manager Package Version: 2.2.2 #### [](#new-features-2)New Features There are no new features in this release. #### [](#fixed-issues-40)Fixed Issues - The **Request Access** interface renders correctly regardless of client provider configuration errors. - Requests made in direct browser calls from the API console correctly include attached payloads. #### [](#known-issues-35)Known Issues There are no known issues in this release. ### [](#anypoint-api-community-manager-package-version-2-2-0)Anypoint API Community Manager Package Version: 2.2.0 #### [](#new-features-3)New Features - API Console is updated from 6.4.9 to 6.5.0, including general bug fixes and improvements described in the [API Console release notes](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes). - On a page with an API record ID in scope, such as an API details page, the Lightning component [Application Listing](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#application-listing) shows only the applications with access to the current version of that API. - The API Community Manager connection now supports selecting one of the multiple identity providers supported in Anypoint Platform. #### [](#fixed-issues-41)Fixed Issues - Creating a new community using an API Community Manager template succeeds without an error. - The documentation component correctly renders numbered lists and bulleted lists. - The filter in the Lightning component **API Catalog** shows the API display name and not the API ID. The parameter **Categories Filter (Advanced)** still uses the category ID. If you enter incorrect syntax in the filter, a message shows the correct category names and syntax. - The **Save to file** button works without errors. - When the API console displays a method in a version and you select another version that does not have the same method, the console displays the selected version with no errors. - Finding assets by custom fields works correctly. - The request access interface works correctly regardless of browser refreshes. #### [](#known-issues-36)Known Issues There are no known issues in this release. ## [](#june-2021)June 2021 ### [](#anypoint-api-community-manager-package-version-2-0)Anypoint API Community Manager Package Version: 2.0 #### [](#new-features-4)New Features - After the manual upgrade to version 2.0, all future upgrades are automatic. Upgrades with new features are applied to sandbox environments four weeks before they are applied to production environments. Upgrades with only bug fixes are applied to sandbox environments two weeks before they are applied to production environments. - The Lightning component **Application Details** includes the option **Enable Application Editing**, which enables users to edit application details and reset an application’s client credentials. #### [](#fixed-issues-42)Fixed Issues - The instance selector displays all of an asset’s instance versions, including the patch versions. - In the builder, when the Lightning component **API Catalog** shows an asset list of more than 100 assets, it successfully requests the categories of the assets from Anypoint Platform and displays them. #### [](#known-issues-37)Known Issues - Under very rare circumstances, creating a new community using an API Community Manager template fails, but using a different template works correctly. ### [](#anypoint-api-community-manager-package-version-1-82)Anypoint API Community Manager Package Version: 1.82 #### [](#new-features-5)New Features - The guided setup and diagnostics offer simpler and improved configuration of profile permissions. - The Lightning component **ACM Search Box** returns results found in API specifications, documentation pages, and custom fields. - The new Lightning components **Custom Fields Table** and **Custom Fields Pills** display the custom field values of APIs. - The Lightning component **Spec Downloader** includes the option to hide or show the warning message about possible inconsistencies in automatically generated API specifications. - API Console is updated from 6.3.7 to 6.4.9, including general bug fixes and improvements described in the [API Console release notes](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes). - The Lightning component **API Console** provides you with the ability to: - Make API calls either through Salesforce Experience Cloud or directly from the browser. - Supply credentials either automatically from a client application or manually. - Expand or hide the request panel. #### [](#fixed-issues-43)Fixed Issues - API Community Manager loads large asset lists from Exchange correctly. #### [](#known-issues-38)Known Issues - Under very rare circumstances, creating a new community using an API Community Manager template fails, but using another template works correctly. - Occasionally, the Lightning component **API Catalog** fails during a request for the categories of a large asset list. ## [](#march-2021)March 2021 ### [](#anypoint-api-community-manager-package-version-1-80-5)Anypoint API Community Manager Package Version: 1.80.5 #### [](#new-features-6)New Features There are no new features in this release. #### [](#fixed-issues-44)Fixed Issues - The API Detail component now always displays the latest patch version for the API. - Communities with more than 100 APIs operate correctly without generating errors on the control panel. - The API version selector now shows the version label correctly, without the `v` prefix. #### [](#known-issues-39)Known Issues - Under very rare circumstances, creating a new community using an API Community Manager template fails, but using another template works correctly. ## [](#february-2021)February 2021 ### [](#anypoint-api-community-manager-package-version-1-80-1)Anypoint API Community Manager Package Version: 1.80.1 #### [](#new-features-7)New Features - API Console is updated from 6.3.6 to 6.3.7, including general bug fixes and improvements described in the [API Console release notes](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes). - When publishing an API group to a community, administrators have the option to edit the APIs in the group. - The API Access Requester Lightning component includes grant type selection for client applications that have identity providers. #### [](#fixed-issues-45)Fixed Issues - On the **Manage APIs** page, administrators can search for APIs by business group by using the syntax `businessGroup:myGroup`. - Assets in API Community Manager without a corresponding asset in Exchange show an improved error message. - Administrator-only assets are visible only to administrators. - The **Request Access** button is not visible to guest users. #### [](#known-issues-40)Known Issues - Under very rare circumstances, creating a new community using an API Community Manager template fails, but using another template works correctly. ## [](#january-2021)January 2021 ### [](#anypoint-api-community-manager-package-version-1-79)Anypoint API Community Manager Package Version: 1.79 #### [](#new-features-8)New Features - API Community Manager supports MuleSoft Government Cloud. - API Console is updated from 6.3.5 to 6.3.6, including general bug fixes and improvements described in the [API Console release notes](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes). - When requesting access to an application, contract information is retrieved more quickly. #### [](#fixed-issues-46)Fixed Issues - Attempting to create a new client application with the same name as an existing client application shows a correct error message. - Using separate console components works correctly. - Deleting an asset that is in the community and is not in Exchange works without an error. - Resetting credentials and editing an application work correctly when the application uses an identity provider. #### [](#known-issues-41)Known Issues - Under very rare circumstances, creating a new community using an API Community Manager template fails, but using another template works correctly. ## [](#december-2020)December 2020 The December release is distributed in two packages. Version 1.77 includes bug fixes, corrections, and new features, and version 1.76 includes only the bug fixes and corrections. Version 1.77 includes all the changes in version 1.76 and other previous versions. **Please contact your customer success representative for guidance on adopting this release.** ### [](#anypoint-api-community-manager-package-version-1-77)Anypoint API Community Manager Package Version: 1.77 #### [](#new-features-9)New Features - API Community Manager Guided Setup makes installation and configuration faster, easier, and simpler. - API Community Manager Diagnostics show status information on your community to make identifying and resolving configuration problems faster, easier, and simpler. - Navigating APIs and publishing assets to the community use a new API model that groups all versions of an API or API Group together. - The **API Header** component shows an asset version selector. #### [](#fixed-issues-47)Fixed Issues - Version 1.77 includes all the bug fixes and corrections in package version 1.76. #### [](#known-issues-42)Known Issues - Version 1.77 includes the known issues of package version 1.76. - Upgrading requires permissions configuration. Follow the steps to ensure all permissions are correct during the [upgrade process](https://docs.mulesoft.com/jp/api-community-manager/update-acm). - After updating, uploading an API Group to the community may cause errors, until the group is removed from the community and published again. - Unpublishing an API from the community that does not exist in Exchange shows an error in the ACM administration interface until the page is refreshed. ### [](#anypoint-api-community-manager-package-version-1-76)Anypoint API Community Manager Package Version: 1.76 #### [](#new-features-10)New Features - None #### [](#fixed-issues-48)Fixed Issues - API Console is updated from 6.2.6 to 6.3.5, including general bug fixes described in the [API Console release notes](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes). - Caching improves the API console load time. - API Community Manager administration renders correctly when no APIs are available for publishing, such as when all APIs in Exchange are already published. - In the applications detail page, API contracts display only APIs published in the community. - CMS articles open correctly from the search results. #### [](#known-issues-43)Known Issues - Under very rare circumstances, opening a page with the API Console component displays the error `Cannot read property 'aml' of undefined`. - Under very rare circumstances, creating a new community using an ACM template fails, but using another template works correctly. ## [](#november-2020)November 2020 API Community Manager package version: 1.74 ### [](#new-features-11)New Features - The **Instances Viewer** component shows instances of an API. - Administrator search is enhanced. - The resources displayed in the **API Console** component can be filtered. - The **API Console** component is updated to version 6.2.6. ### [](#fixed-issues-49)Fixed Issues - Links from API documentation pages to headers within markdown pages work correctly. - The **Spec Downloader** component supports selection of download languages and has corrected labels. - The named credential is not distributed in the package, so the upgrade does not fail due to an attempt to modify a "managed element". - Wrapping console navigation item text is supported with a CSS variable. - When a user first accesses the API console, the summary section is selected by default. - The **API Console** component includes the following bug fixes: - For partial models, rendered examples show all properties, including properties with an empty string value, the integer value `0`, or the boolean value `false`. - In type documentation, enum array properties render correctly. - When the `queryString` node is defined on an operation, the **Try it** panel renders the query parameters. - XML example structures match the definition in the RAML type. - JSON schemas in RAML render completely. ### [](#known-issues-44)Known Issues - Using the `anypoint.mulesoft` named credential distributed with the package causes the installation error `(anypoint_mulesoft) Cannot Modify Managed Component`. To prevent this, do not use the `anypoint.mulesoft` named credential, and create a new named credential in the Salesforce organization when you [upgrade](https://docs.mulesoft.com/jp/api-community-manager/update-acm). - Under very rare circumstances, opening a page with the **API Console** component shows the error `Cannot read property 'aml' of undefined`. To remove this error, reload the page. - After installing this version, all instances of the **Spec Downloader** component on all pages stop rendering. To correct this, remove each instance of the component from each page, add the component again from the builder palette, and publish your community. ## [](#september-2020)September 2020 API Community Manager package version: 1.69 ### [](#new-feature)New Feature - Communities support linking to specific documentation pages, resources, and methods in the APIs in the **API Documentation Viewer**, **API Console**, and **API Console Navigation** components. ### [](#fixed-issues-50)Fixed Issues - APIs with no endpoints render correctly. - The **API Catalog** and **Search Results** components have a wait state that shows a spinner. - The **API Console** component displays the **Client ID** and **Client secret** fields in the correct order. - The **API Console** component does not generate duplicate examples for type elements. - The **API Console** component displays query string documentation correctly. - The **API Console** component shows the media types selector correctly on specs that define multiple media types. - The **API Console** component shows increased space between inputs, selectors, and labels. - The **API Console** component renders string examples correctly in table view. ### [](#known-issues-45)Known Issues - This release includes many security changes. After installing the new package, update the permissions of the member and guest profiles on the **SelfRegisterUserRequests** object, and carefully check all the permissions of all other object fields. Follow the steps to ensure all permissions are correct during the [upgrade process](https://docs.mulesoft.com/jp/api-community-manager/update-acm). - In an API documentation page, links to headers within the same page do not work. ## [](#august-2020)August 2020 API Community Manager package version: 1.66 ### [](#new-features-12)New Features - The `External Data Source` supports JSON Web Token (JWT) based authentication for simpler configuration, simpler maintenance, and improved security. - The API Header Lightning component optionally displays an API version number. - The API console optionally displays an API specification with all resources expanded. ### [](#updates)Updates There are no updates in this release. ### [](#fixed-issues-51)Fixed Issues - The API Catalog Lightning component has correct filter keywords. - The mocking service correctly handles OAuth request tokens. - The community page correctly displays icons. - A longer console timeout accommodates APIs with longer response times. - API Community Manager prevents some problems that cause the error message `Too many SOQL queries: 101`. - The API Documentation Viewer Lightning component correctly highlights selected pages and sections. - The Application Listing Lightning component has correct styling. - When the API Carousel Lightning component is set to show children, it correctly shows the APIs in the API group to registered users. - The API console shows only the API instances that have consumer endpoints. ### [](#known-issues-46)Known Issues - IMPORTANT: Both `Member` and `Guest` profiles must have field-level `Read` access to the `ParentId` field in the `CommunityAPI` object, so follow the steps to ensure this during the [upgrade process](https://docs.mulesoft.com/jp/api-community-manager/update-acm). - Your Salesforce organizations must have the "External Data Change Tracking for OData 4.0 Adapter" feature enabled, so follow the steps to ensure this during the [upgrade process](https://docs.mulesoft.com/jp/api-community-manager/update-acm). ## [](#july-2020)July 2020 API Community Manager package version: 1.62 ### [](#new-features-13)New Features - MuleSoft introduces OAS 3.0 support for design and discovery across API Designer, Anypoint Exchange, and Anypoint API Community Manager, so users can author, catalog, and showcase API specifications in the OAS 3 language throughout the platform. - Search results include articles in the content management system (CMS), also known as _managed content_. ### [](#updates-2)Updates There are no updates in this release. ### [](#fixed-issues-52)Fixed Issues There are no fixed issues in this release. ### [](#known-issues-47)Known Issues - Your Salesforce organizations must have the "External Data Change Tracking for OData 4.0 Adapter" feature enabled, so follow the steps to ensure this during the [upgrade process](https://docs.mulesoft.com/jp/api-community-manager/update-acm). ## [](#june-2020)June 2020 API Community Manager package version: 1.61 ### [](#new-features-14)New Features - Introducing platform-wide support for API Groups across API Manager, Exchange, and API Community Manager. API Groups enable combining multiple API instances into a cohesive unit to present to API consumers in Exchange and API Communities. - The Spec Downloader Lightning component enables developers to download specifications of APIs presented in communities. ### [](#updates-3)Updates There are no updates in this release. ### [](#fixed-issues-53)Fixed Issues There are no fixed issues in this release. ### [](#known-issues-48)Known Issues There are no known issues in this release. ## [](#may-2020)May 2020 API Community Manager package version: 1.56 ### [](#new-features-15)New Features - Email notifications for contract approval events support custom branding. - Contract approval events can trigger custom actions. ### [](#updates-4)Updates - Improved error and warning messages for end-users in all consumer-facing components. ### [](#fixed-issues-54)Fixed Issues There are no fixed issues in this release. ### [](#known-issues-49)Known Issues There are no known issues in this release. ## [](#march-2020)March 2020 API Community Manager package version: 1.53 ### [](#new-features-16)New Features - MuleSoft introduces platform-wide support across Access Management, API Manager, Exchange, and API Community Manager to support multiple identity providers for client management. Client applications created through the community are registered in the appropriate identity provider based on environment, business group, and API configuration. - Users can manage in the community all the client applications visible to them, including applications created in the community and applications created outside the community. - Standardized security credentials to OAuth 2.0 and standardized authentication provider for named credentials, removing the need to store Anypoint credentials. ### [](#fixed-issues-55)Fixed Issues - The API console correctly displays body examples and types of responses. - Links across API documentation pages in the same API work correctly in the API documentation viewer. - The API console handles mocking service paths without incorrect 404 errors. - Client apps without contracts render correctly. ### [](#known-issues-50)Known Issues - When an access request (contract) for a client application is approved, the client application owner receives a standard Anypoint Platform email notification instead of email customized with community branding. ## [](#february-2020)February 2020 API Community Manager package version: 1.46 ### [](#new-features-17)New Features There are no new features in this release. ### [](#updates-5)Updates There are no updates in this release. ### [](#fixed-issues-56)Fixed Issues - API tier limits use the correct large integer datatype. - The change SLA tier dialog honors fonts defined in the template and branding settings. - The platform cache includes API categories for improved API catalog performance. - API Console navigation works correctly. - Legacy mode includes the previous version of API Console (v5). - The reset credentials action works correctly. - The request access dialog presents multiple SLA tier limits. - API Community Manager components work as expected after object layout changes. - Client application analytics charts scale correctly. ### [](#known-issues-51)Known Issues - When an access request (contract) for a client application is approved, the client application owner receives a standard Anypoint Platform email notification instead of email customized with community branding. ## [](#january-2020)January 2020 API Community Manager package version: 1.42 ### [](#new-features-18)New Features - API Community Manager [supports Salesforce Platform Cache](https://docs.mulesoft.com/jp/api-community-manager/cache) for better performance and responsiveness of all pages and components. ### [](#updates-6)Updates - All components are now compliant with the WCAG 2.1 accessibility standard Level AA, and customers can certify their communities at this level of the standard. - Product documentation includes a section on how to [administer your API community](https://docs.mulesoft.com/jp/api-community-manager/administer-community). - API Console is upgraded to version 6. - The API Carousel and API Catalog Lightning components now support a [simplified syntax](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#filter-conditions) for advanced filter conditions. ### [](#fixed-issues-57)Fixed Issues - API specifications that include fragments render correctly in API Console. - Advanced filter conditions work as expected in all cases, including when the conditions use category names that contain spaces. - The API name in the cards of the API Carousel and API Catalog Lightning components has correct line height, and correctly renders characters with descenders: g, j, p, q, and y. - When permissions are incorrectly configured for categories in the API Catalog Lightning component, the community builder shows an improved and clearer error message. ### [](#known-issues-52)Known Issues - Upgrading from a package version before 1.26 requires additional steps during the [upgrade process](https://docs.mulesoft.com/jp/api-community-manager/update-acm). - When an access request (contract) for a client application is approved, the client application owner receives a standard Anypoint Platform email notification instead of email customized with community branding. ## [](#december-2019)December 2019 API Community Manager package version: 1.35 ### [](#new-features-19)New Features There are no new features in this release. ### [](#updates-7)Updates - API Community Manager introduces limited support of Microsoft Internet Explorer 11 for API discovery and displaying content components including API Carousel, API Catalog, and API Documentation Viewer. - Improved install process. ### [](#fixed-issues-58)Fixed Issues - Improved informative messages in the components and control panel when data is not available. - The API Carousel, API Catalog, and Search Results components sort APIs alphabetically. - Search operates on global and API-level forums and topics. - Corrected API Console navigation and display of request headers. - Images in API Exchange markdown pages render correctly in a community, including images from API assets that are not public in Exchange. - If the API Community Manager control panel is open in one browser tab, and the community is activated and published in a second browser tab or window, then the Open Community button in the control panel opens the community correctly. - If a client application has a contract with an API instance, and a new SLA tier is added after the client is created, then this client application can upgrade to the new tier. - Advanced filtering in the API Carousel and API Catalog components supports Exchange category names that contain spaces. ### [](#known-issues-53)Known Issues - Upgrading from a package version before 1.26 requires additional steps during the [upgrade process](https://docs.mulesoft.com/jp/api-community-manager/update-acm). - When an access request (contract) for a client application is approved, the client application owner receives a standard Anypoint Platform email notification instead of email customized with community branding. ## [](#november-2019)November 2019 API Community Manager package version: 1.26 ### [](#new-features-20)New Features - New [API Catalog](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#api-catalog) Lightning component enables discovering APIs by exploring interactively. - New [ACM Search Box](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#acm-search-box) and [ACM Search Results](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#acm-search-results) Lightning components enable integrated search across business-oriented and API-specific content. ### [](#updates-8)Updates - Performance is improved through usage of platform cache. - Lightning components are compliant with WCAG-2.1 (A-level). - Lightning components are updated to API version 45. - Exchange categories are supported for [advanced filtering](https://docs.mulesoft.com/jp/api-community-manager/acm-lightning-components#categories-filter) in the API Carousel and API Catalog components. ### [](#fixed-issues-59)Fixed Issues - No fixed issues in this release. ### [](#known-issues-54)Known Issues - Upgrading from a previous version of the package requires [additional steps](https://docs.mulesoft.com/jp/api-community-manager/update-acm). - Exchange categories with spaces are not supported for advanced filtering in the API Carousel and API Catalog components. - After activating and publishing a community in a different browser tab or window, the API Community Manager control panel must be refreshed (reloaded) for the Open Community button to correctly open the community. - Client applications that have an existing contract with an API instance can’t be upgraded to new SLA tiers added after the client was created. To use these new SLA tiers, you must create a new client application and request a new contract. - When an access request (contract) for a client application is approved, the client application owner receives a standard Anypoint Platform email notification instead of a customized email with the community branding. - Images in API Exchange markdown pages are not rendered correctly in a community unless the API asset is made public in Exchange. ## [](#august-2019)August 2019 API Community Manager package version: 1.16 ### [](#new-features-21)New Features There are no new features in this release. ### [](#updates-9)Updates - Support provided for multiple API Consoles in the same page. - New "Learn More" component provides direct access to the API business page from any other page. - New "API details" component provides direct access to the API details page from any other page. - Member lists allow refresh without reloading the complete control panel. - Confirmation requested when activating or deactivating a member. ### [](#fixed-issues-60)Fixed Issues - Corrected position of endpoint information in the API Console component. - Corrected spacing and tab highlighting on the API Console Try it now panel. - Corrected response preview rendering in the API Console Try it now panel. ### [](#known-issues-55)Known Issues - After activating and publishing a community in a different browser tab or window, the API Community Manager control panel must be refreshed (reloaded) for the Open Community button to correctly open the community. - Client applications that have an existing contract with an API instance can’t be upgraded to new SLA tiers added after the client was created. To use these new SLA tiers, you must create a new client application and request a new contract. - When an access request (contract) for a client application is approved, the client application owner receives a standard Anypoint Platform email notification instead of a customized email with the community branding. - Images in API Exchange markdown pages are not rendered correctly in a community unless the API asset is made public in Exchange. ## [](#july-2019)July 2019 Initial release of API Community Manager. API Community Manager package version: 1.14 ### [](#features)Features - Simple out-of-the-box API portal/API community template. - Point-and-click and code-based branding, look and feel, and customization of site structure. - Publishing of API specs, documentation pages and API Console from Exchange for selected APIs. - CMS content authoring and publication (news, articles, events, and blogs). - Salesforce Lightning components to interact with the Anypoint Platform from a community. - Discussion forums. - Member onboarding with approval process. - Client application onboarding, application credentials management, and consumption analytics view. - Extensibility through custom components. ### [](#known-issues-56)Known Issues - After activating and publishing a community in a different browser tab or window, the API Community Manager control panel must be refreshed (reloaded) for the Open Community button to correctly open the community. - Client applications that have an existing contract with an API instance can’t be upgraded to new SLA tiers added after the client was created. To use these new SLA tiers, you must create a new client application and request a new contract. - When an access request (contract) for a client application is approved, the client application owner receives a standard Anypoint Platform email notification instead of a customized email with the community branding. - Images in API Exchange markdown pages are not rendered correctly in a community unless the API asset is made public in Exchange. ## [](#see-also)See Also - [API Community Manager Documentation](https://docs.mulesoft.com/jp/api-community-manager/) - [Product Versioning and Back Support Policy](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) - [トラブルシューティング](https://docs.mulesoft.com/jp/api-community-manager/troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint API Experience Hub Release Notes
Starting October 2024, API Experience Hub enables testing managed package upgrades in sandbox environments before production.
The following table lists the release schedule for the API and UI, and the managed package. The API and UI release contains service updates affecting Anypoint APIs or the UI. The managed package includes updates to the components and data objects that interact with your Anypoint Platform organization. The API and UI release for EU occurs a day before the US release. The managed package is pushed to sandbox instances for testing for at least eight days before it’s pushed to production environments. If a service release or upgrade fails, customers receive an alert and another release or upgrade is manually pushed the next day. The latest version of the API Experience Hub managed package is used when API portals are created during the new connection process.
Release Version Managed Package Sandbox Push-Upgrade API/UI Production Services Release Managed Package Production Push-Upgrade

January 2026

No new version of the managed package

  • EU: January 8, 2026

  • US: January 9, 2026

No new version of the managed package

2.40.0

January 27, 2026

No update

January 31, 2026

May 2026

2.46.0

May 8, 2026

No update

May 11, 2026

2.48.0

May 21, 2026

  • CA: May 18, 2026

  • EU: May 19, 2026

  • JP: May 19, 2026

  • US: May 20, 2026

May 26, 2026

June 2026

2.50.0

June 19, 2026

  • CA: June 16, 2026

  • JP: June 17, 2026

  • EU: June 17, 2026

  • US: June 18, 2026

June 26, 2026

October 2026

2.54.0.1

October 6, 2026

  • CA: October 1, 2026

  • JP: October 2, 2026

  • EU: October 2, 2026

  • US: October 3, 2026

October 10, 2026
## [](#october-2026)October 2026 ### What’s New - OpenAPI Specification (OAS) 3.1 specifications are now supported. You can publish OAS 3.1 API specifications to your portal and view the specification documentation in the API Console. - You can now create a link to a page other than the main catalog with a category filter already applied. When you change the filters on that page, you see all the services and filter options available to you. For more information, see [API の検索](https://docs.mulesoft.com/jp/api-experience-hub/searching-for-apis). - When an error occurs in an interaction with Salesforce, the portal displays a clear message, a suggested next step, and a reference ID that you can share with support. - This release includes the following accessibility improvements: - The confirmation dialog for removing a service from the portal uses a red **Delete** button and no longer shows a warning icon. - A confirmation message appears after you delete an item. - Loading spinners appear when you click **Apply** or **Save**. - Loading animations for pages and tabs are smoother. - **Learn more** links are underlined, and the breadcrumb bar has a refreshed icon. ### Fixed Issues
Fixed Issues ID

The Member list no longer fails to load when the portal has more than 100 members. The list now supports up to 500 members.

W-23526766

The portal now shows managed API instances of a service from all business groups, such as a parent organization. Previously, it showed only the instances in the same business group as the published service.

W-23649716

The Anypoint_AEH connected app is now created with Require Secret for Web Server Flow and Require Secret for Refresh Token Flow enabled.

W-23396930
## [](#june-2026)June 2026 ### What’s New - The **My Applications** page and **Application Details** page now show the **Last updated** date and time when the application credentials were last modified, in your local timezone. For more information, see [My Applications (マイアプリケーション)](https://docs.mulesoft.com/jp/api-experience-hub/my-applications). ### Fixed Issues
Fixed Issues ID

The API Console mocking feature no longer fails with a 401 error on Hyperforce CA/JP environments.

W-22840808

Code blocks in the Asset Documentation Viewer now render in a monospace font on all platforms.

W-21653904

When editing a client application, OAuth 2.0 grant type changes now save correctly.

W-21228682
## [](#may-2026)May 2026 ### What’s New - Apollo support is now available for GraphQL services in the managed package. This enhancement improves GraphQL API integration and compatibility for portal users leveraging Apollo-based clients. - Portal administrators can now customize labels for newly introduced asset types, including agentic assets such as MCPs, agents, and LLMs, through the portal builder. - You can now publish agents, LLMs, MCP servers, GraphQL, and gRPC services to your portal alongside existing API types. The **Catalog management** page (formerly **API management**) and the **APIs** page surface all supported service types in a unified catalog. For more information, see: - [API の管理](https://docs.mulesoft.com/jp/api-experience-hub/managing-apis) - [API 詳細の表示](https://docs.mulesoft.com/jp/api-experience-hub/viewing-api-details) - [API の検出](https://docs.mulesoft.com/jp/api-experience-hub/discovering-apis) - All portals now scale to 7,000 assets by default. Opting in is no longer required. For more information, see [制限事項](https://docs.mulesoft.com/jp/api-experience-hub/limitations). - For portals configured before LLM support was available, Administrators can now add a page variation to show the **API Console** on the **Service Details** page for LLM services. For more information, see [Add Page Variation to Show the API Console for LLMs](https://docs.mulesoft.com/jp/api-experience-hub/common-builder-customizations#add-page-variation-to-show-the-api-console-for-llms). ### Fixed Issues
Fixed Issues ID

The request panel now works correctly when proxy mocking is enabled.

W-22282240

Consumer asset search requests now correctly route through ProjectView for organizations with ProjectView enabled.

W-22247758

The Summary page method badges now display at the correct size with proper styling.

W-22300166

Summary page links now function correctly when Lightning Web Security (LWS) is disabled.

W-22300570

The endpoint documentation page no longer shows bottom navigation links.

W-22300139

The Request Access button no longer returns a 401 Unauthorized error when tiered access (scalability) is enabled for an API instance.

W-20998827
## [](#january-2026)January 2026 ### What’s New - When configuring Single Sign-On (SSO) for your portal, you can now enable multi-valued SAML attributes to send multiple groups in the groups claim. Sending groups as a comma-separated list is no longer required. For more information, see [Create and Configure an Application for Okta SAML and Microsoft Entra ID SAML](#api-experience-hub::configuring-sso.adoc#step-1-enable-sso-for-your-portal). - The maximum limit of user groups is now increased from 20 to 100. For more information, see [制限事項](https://docs.mulesoft.com/jp/api-experience-hub/limitations). ## [](#november-2025)November 2025 ### What’s New - Administrators can now enable portal scalability to increase API capacity to 7,000. Portals previously opted in and all new portals scale to 7,000 APIs. For more information, see [Opt In to Increase the Number of APIs In the Portal](https://docs.mulesoft.com/jp/api-experience-hub/managing-apis#opt-in-to-increase-the-number-of-apis-in-the-portal). - API management now optimizes scrolling to support 7,000 APIs. ### Fixed Issues
Fixed Issues ID

In the API Console, Boolean query parameters set to false now appear correctly in API request URLs instead of being omitted.

W-19881903
## [](#june-2025)June 2025 ### What’s New - Admins can now enable Salesforce users to access a portal. For more information, see: - [api-experience-hub::enabling-salesforce-users-to-access-a-portal.adoc](#api-experience-hub::enabling-salesforce-users-to-access-a-portal.adoc) - [Existing User Request Access Lightning component](https://docs.mulesoft.com/jp/api-experience-hub/api-experience-hub-lightning-components#existing-user-request-access) - [api-experience-hub::requesting-access-to-a-portal.adoc](#api-experience-hub::requesting-access-to-a-portal.adoc) ### Fixed Issues
Fixed Issues ID

In the API Console, the Python requests examples from RAML files now display correctly.

W-1853152

The create connections endpoint is upgraded to make the connection more secure.

W-18717718
## [](#may-2025)May 2025 ### What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) ### Fixed Issues
Fixed Issues ID

In the API Console, specs with multipart requests now work as expected.

W-18328020

An issue with loading assets in the API carousel component is now resolved.

W-18380623
## [](#april-2025)April 2025 ### Fixed Issues
Fixed Issues ID

In the API Console, the multipart payload components now work as expected.

W-17986234 and W-17936498

The search component is now updated to prevent search failures.

W-18015093 and W-18088742

The UI in Anypoint Platform is now updated to prevent potential disruptions.

W-18121291

The search results are now sorted by relevance to the search term.

W-17898526

Tool tips now show as expected when scrolling.

W-17898560
## [](#march-2025)March 2025 ### Fixed Issues
Fixed Issues ID

In the API Console, the multipart form data is now working as expected when Lightning Web Security (LWS) is enabled in the Salesforce organization.

W-17349235

In the API Console, copying a response to the clipboard is now working as expected when LWS is enabled in the Salesforce organization.

W-17369541

In the API Console, the API specs for some endpoints now show as expected.

W-17351714

In the API Console, examples of anyOf types in OAS specifications now show as expected.

W-17413312

In the API Console, API type documentation now shows inherited properties when LWS is enabled in the Salesforce organization.

W-17883236
## [](#february-2025)February 2025 ### What’s New - Administrators can now enable portal scalability to increase the maximum number of APIs available in the portal to 1,000. For API portals created before this release, administrators must opt in. New portals automatically scale to 1,000 APIs. For more information, see [Opt In to Increase the Number of APIs In the Portal](https://docs.mulesoft.com/jp/api-experience-hub/managing-apis#opt-in-to-increase-the-number-of-apis-in-the-portal). - You can now refine search results by filtering APIs by tags and categories. For more information, see: - [API の管理](https://docs.mulesoft.com/jp/api-experience-hub/managing-apis) - [API の検索](https://docs.mulesoft.com/jp/api-experience-hub/searching-for-apis) - [Asset Catalog](https://docs.mulesoft.com/jp/api-experience-hub/api-experience-hub-lightning-components#assets-catalog) ## [](#january-2025)January 2025 ### What’s New - The documentation now includes instructions for configuring Single Sign-On (SSO) using Microsoft Entra ID for Security Assertion Markup Language (SAML). For more information, see [Enable SSO for Your Portal](#api-experience-hub::configuring-sso.adoc#step-1-enable-sso-for-your-portal.adoc). ## [](#october-2024)October 2024 ### What’s New - You can now create and manage groups of users who can see specific APIs in your portal. For more information, see [Manage User Groups](https://docs.mulesoft.com/jp/api-experience-hub/managing-users#manage-user-groups). - A new rate-limiting service now protects against potential distributed denial-of-service (DDoS) attacks. - API Console is now updated to 0.3.2. ### Fixed Issues
Fixed Issues ID

The Builder can now access the current asset library of uploaded images.

W-13514487

When Lightning Web Security (LWS) is disabled, the codemirror bundle now loads as expected.

W-16723030

In the API Console, code examples now update when navigating between endpoints.

W-16723085
For additional known issue information about this product, see [Known Issues](https://help.salesforce.com/s/issues). ## [](#august-2024)August 2024 ### What’s New - You can now assign a user the API Experience Hub Users Approver granular permission to approve or reject pending registration requests and enable or disable member users only. For more information, see: - [Granular Permissions and Permission Sets](https://docs.mulesoft.com/jp/api-experience-hub/user-roles-permissions-and-profiles#granular-permissions-and-permission-sets) - [Assign the API Experience Hub Users Approver Permission](https://docs.mulesoft.com/jp/api-experience-hub/assigning-permissions#assign-api-experience-hub-users-approver-permission) - This release contains accessibility improvements, including alternative text for images, more contrast for components, images, and text, and visible and persistent labels. - API Console is now updated to 0.3.1. ### Fixed Issues
Fixed Issues ID

The API Console no longer loops when the Lightning Web Security component is disabled.

W-16251757
### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder can’t access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

In the API Console, the following known issues occur using authentication credentials:

  • Using OAuth 2.0 without secure settings shows an error.

  • The Passthrough and Custom fields don’t clear when data is removed.

  • The endcode in the URL isn’t working as expected when using query parameters with spaces.

  • For OAuth 2.0, credentials aren’t cleared after changing an endpoint.

W-15184114
## [](#july-2024)July 2024 ### What’s New - You can now manage separate deployment environments for your API portal. You can connect to multiple Salesforce sandbox organizations and switch between them. Manage Salesforce organizations from the **Manage your API portal** page by selecting sandbox environments that are available in the current Salesforce connection. For more information, see [Sandbox の操作](https://docs.mulesoft.com/jp/api-experience-hub/working-with-sandboxes) - You can now view AsyncAPI 2.6 specifications to discover and reuse within your organization. To learn about the AsyncAPI journey, see [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). - This product has a refreshed UI. This new UI brings the product visually closer to the [new visual style of Salesforce](https://www.salesforce.com/blog/salesforce-cosmos-slds-2/) and enhances consistency, accessibility, and the user experience. Changes include a refreshed navigation, icons, and colors. ### Fixed Issues
Fixed Issues ID

In the API Console, examples display correctly when expanded in the Documentation panel.

W-14559605

In the API Console, the annotationTests label is no longer missing in the Documentation panel.

W-14560535

The color of the API Catalog description now displays correctly.

W-13570863
### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder can’t access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

In the API Console, the following known issues occur using authentication credentials:

  • Using OAuth 2.0 without secure settings shows an error.

  • The Passthrough and Custom fields don’t clear when data is removed.

  • The endcode in the URL isn’t working as expected when using query parameters with spaces.

  • For OAuth 2.0, credentials aren’t cleared after changing an endpoint.

W-15184114
### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder can’t access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

In the API Console, the following known issues occur using authentication credentials:

  • Using OAuth 2.0 without secure settings shows an error.

  • The Passthrough and Custom fields don’t clear when data is removed.

  • The endcode in the URL isn’t working as expected when using query parameters with spaces.

  • For OAuth 2.0, credentials aren’t cleared after changing an endpoint.

W-15184114
## [](#june-2024)June 2024 ### What’s New - You can now add Chatter Feed tracking to engage with your portal community. For more information, see: - [Chatter フィード追跡の設定](https://docs.mulesoft.com/jp/api-experience-hub/configuring-chatter-feed) - [Configure Feed Component](https://docs.mulesoft.com/jp/api-experience-hub/common-builder-customizations#configure-feed-component) - [Configure Feed Publisher Component](https://docs.mulesoft.com/jp/api-experience-hub/common-builder-customizations#configure-feed-publisher-component) - You can now add Google Analytics to gain valuable insights into how consumers are using your APIs and portal. For more information, see [ユーザー分析の設定](https://docs.mulesoft.com/jp/api-experience-hub/configuring-user-analytics) - The API Console now has expand and collapse buttons on the **Try It** and navigation panel. - The registration handler used in configuring single sign-on now includes default values for SAML attributes and OpenID Connect default claims for most common identity providers in `AttributeExtractor` for the following fields: - First Name - Last Name - Email - Username ### Fixed Issues
Fixed Issues ID

The search results no longer return duplicate APIs.

W-15665689
### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder can’t access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

In the API Console, the following known issues occur using authentication credentials:

  • Using OAuth 2.0 without secure settings shows an error.

  • The Passthrough and Custom fields don’t clear when data is removed.

  • The endcode in the URL isn’t working as expected when using query parameters with spaces.

  • For OAuth 2.0, credentials aren’t cleared after changing an endpoint.

W-15184114
## [](#may-2024)May 2024 ### What’s New - The maximum number of APIs in a portal is increased to 350. ### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

In the API Console, the following known issues occur using authentication credentials:

  • Using OAuth 2.0 without secure settings shows an error.

  • The Passthrough and Custom fields do not clear when data is removed.

  • The endcode in the URL is not working as expected when using query parameters with spaces.

  • For OAuth 2.0, credentials are not cleared after changing an endpoint.

W-15184114
## [](#april-2024)April 2024 ### What’s New - You can now test APIs using authorization credentials in the API console. ### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

In the API Console, the following known issues occur using authentication credentials:

  • Using OAuth 2.0 without secure settings shows an error.

  • The Passthrough and Custom fields do not clear when data is removed.

  • The endcode in the URL is not working as expected when using query parameters with spaces.

  • For OAuth 2.0, credentials are not cleared after changing an endpoint

W-15184114
### Fixed Issues
Fixed Issues ID

The registration handler no longer causes errors for single sign-on.

W-15203518

An error no longer occurs when loading the asset documentation.

W-15007406

The process of removing an API from the portal when the API does not exist in Exchange no longer fails.

W-15108878

The redirection of the self-registration component is now working as expected.

W-15244602
## [](#march-2024)March 2024 ### What’s New - A Salesforce user with the System Administrator profile can now create an AEH\_Anypoint permission set to configure only the minimum required permissions for the user who connects to Salesforce to link the Salesforce organization and Anypoint Platform organization. For more information, see [権限の割り当て](https://docs.mulesoft.com/jp/api-experience-hub/assigning-permissions) - The Experience Builder now has customizable properties for the following API Experience Hub Lightning components: - Asset Detail Header You can select properties to show the **Request access** button and lifecycle state in the **API Detail** page. - API Console You can now select the property to show the endpoints expanded. For more information, see [API Experience Hub Lightning コンポーネント](https://docs.mulesoft.com/jp/api-experience-hub/api-experience-hub-lightning-components). ### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487
### Fixed Issues
Fixed Issues ID

Request access now works as expected when the Client Credentials grant type is selected and the redirect URI is empty.

W-15007911

In the API Console, the filter text no longer overlaps in the Any type field.

W-13803914

When editing an SLA contract tier, the current SLA tier no longer displays as an option.

W-13803915

In the API Console, the response details view now works as expected.

W-14556777
## [](#january-2024)January 2024 ### What’s New - The Experience Builder now has customizable properties for the following API Experience Hub Lightning components: - API Carousel The title, subtitle, and the number of cards displayed in the API Carousel can now be changed. - Asset Detail Header You can select which properties to show in the API Details page. For more information, see [API Experience Hub Lightning コンポーネント](https://docs.mulesoft.com/jp/api-experience-hub/api-experience-hub-lightning-components). - The **Application details** page now shows the instance URL of an API. For more information, see [My Applications (マイアプリケーション)](https://docs.mulesoft.com/jp/api-experience-hub/my-applications). - The **API details** page now shows the tags and categories of an API. For more information, see [API 詳細の表示](https://docs.mulesoft.com/jp/api-experience-hub/viewing-api-details). - The API Console now enables you to test an API using an instance URL. For more information, see [API インスタンスを使用した API のテスト](https://docs.mulesoft.com/jp/api-experience-hub/testing-apis-using-an-api-instance). - Guest users are now prompted to log in or register when they request access to an API. ### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487
### Fixed Issues
Fixed Issues ID

The Got it and Dismiss buttons are now working properly.

W-14610136

The diagnostic tooling UI is now improved.

W-14610428

The revoked status is now showing for API instances in the Application details page and the API details page.

W-14580099

The search component for the API Catalog, search box, and applications now shows a message when more than 100 characters are entered.

W-13803905

The API Console has updated UI styling.

W-14782945

The API Console now displays the same order of payload examples as other Anypoint Platform products.

W-14651333

In the API Console, aborting a request is now working properly.

W-1450620
## [](#december-2023)December 2023 ### What’s New - Administrators and security teams can now implement an external identity provider (IdP) as a login option for an API Experience Hub portal. Single sign-on (SSO) authentication provides a seamless login experience for your customers with your organization’s unique branding. For more information, see [Managing Users](https://docs.mulesoft.com/jp/api-experience-hub/managing-users) and [Enabling Single Sign-On for Your Portal](https://docs.mulesoft.com/jp/api-experience-hub/enabling-sso-for-your-portal). - The **Manage your API portal** page now displays a banner when any detected issues occur during a diagnostic check. These checks help administrators identify error states and troubleshoot issues. For more information, see [Managing Your Portal](https://docs.mulesoft.com/jp/api-experience-hub/managing-your-portal) ### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487
### Fixed Issues
Fixed Issues ID

In the API Console, the asset version now has a scroll bar.

W-14486849

In the request panel, editing the request now functions properly.

W-14388490

The API Experience Hub UI no longer loops infinitely when a Salesforce token is invalid.

W-13601286

When an existing user tries to self-register, a message displays that the user already exists.

W-14320962

API instance URLs now display in the application details page.

W-14226773

In the API Console, the request tab now displays a message when an endpoint has no information defined in the request.

W-13813441

In the API Console, the response and request tab is now updated when navigating between endpoints.

W-13813442

In the API Console, the documentation and request panels now collapse when navigating between endpoints.

W-13813444

In the API Console, AsyncAPIs now display the security section as expected.

W-14147883

In the API Console, an error no longer occurs when accessing the API Console through the Builder.

W-14266801

In the API Console, the URI parameters now display as expected.

W-14391257
## [](#october-2023)October 2023 ### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487
### Fixed Issues
Fixed Issues ID

The Request Access modal is now working as expected.

W-14321558

In the API Console, the documentation is now showing.

W-14226433

In the API Console, the request for application/x-www-form-rlencoded type no longer fails.

W-14040586

In the API Console, disabling a query parameter now removes the parameter from the URL.

W-13813435

In the API Console, filtering the resource by displayName is now working properly.

W-13719806
## [](#september-2023)September 2023 ### Known Issues
Known Issue Workaround ID

In the API Console, errors occur when interacting with the Navigation page.

W-13661525

In the API Console, the endpoints are not sorting in the same order in the Navigation and Summary pages.

W-13661668

In the API Console, the Response details option is not functioning.

W-13674034

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

The API Console is not rendering APIs properly.

W-13565177, W-13570941, W-13570959 and W-13570967
### Fixed Issues
Issue Resolution ID

In Firefox and Safari, the asset cards no longer show NaN in the last updated field.

W-13803899

Validations are now triggered in the request access inputs.

W-13803904

In the API Console, an error was fixed that occurred in Salesforce 246.

W-14112563

An unexpected error no longer shows when interacting with the API Console.

W-13994257

In the API Console, you can now modify the content-type value that is sent in a request.

W-13949057

In the API Console, the example for the enum property is no longer missing.

W-13813445

In the API Console, the content type is no longer missing in the Headers sections.

W-13994271
## [](#august-2023)August 2023 ### What’s New - The API Details page now shows the count of instances and a link to the **Instances** screen where you can view the name and URL, and copy the URL if available. ### Known Issues
Known Issue Workaround ID

In the API Console, errors occur when interacting with the Navigation page.

W-13661525

In the API Console, the endpoints are not sorting in the same order in the Navigation and Summary pages.

W-13661668

In the API Console, the response details option is not functioning.

W-13674034

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions to add the asset library.

W-13514487

The API Console is not rendering APIs properly.

W-13565177, W-13570941, W-13570959 and W-13570967
### Fixed Issues
Issue Resolution ID

The portal no longer returns search results when no assets are published.

W-13639213

The connection no longer fails with an unexpected error when there is no Salesforce session.

W-13676586

The installation package no longer fails with an unexpected error when the Salesforce organization does not support the second generation packages.

W-13791676

The contract list no longer fails when there is a contract for an unaccessible API.

W-13798361

The application list no longer shows an error when searching for a term with more than 300 characters.

W-13803906

A collapse and expand icon now displays for long API names on the API details page.

The Delete and Edit buttons now display properly when application names are long.

W-13803907

The API Catalog no longer reloads when entering text in the search box.

W-13803913

In the API Console, the contact information now displays in the Summary panel.

W-13569134

In the API Console, the section headers now span the width of the endpoint Documentation panel.

W-13121768

In the API Console, tables and links now have the correct styles in the Summary panel.

W-13525191

In the API Console, the Documentation panel for the request example now displays properly.

W-13568832

In the API Console, the Body section now shows for the multipart/form-data media-type.

W-13611254

In the API Console, endpoints are no longer showing an empty response.

W-13661016

In the API Console, the response type now has the correct styles applied.

W-13674045

In the API Console, the Copy button now displays only in raw view.

W-13674015

In the API Console, headers no longer appear as required when they are not required.

W-13813437

In the API Console, the Media type is no longer empty.

W-13813438

In the API Console, the Copy button is no longer missing in the Body section.

W-13813446

In the API Console, several API components are updated to the latest version.

W-11470978

In the API Console, component documentation and migration guides are improved.

W-13661633

In the API Console, running the storybook no longer fails.

W-13739888
## [](#july-2023)July 2023 **July 22, 2023** ### Known Issues

Known Issue

Workaround

ID

In the API Console, the documentation does not show the contact information in the Summary page.

W-13569134

In the API Console, errors occur when interacting with the Navigation page.

W-13661525

In the API Console, the endpoints are not sorting in the same order in the Navigation and Summary pages.

W-13661668

In the API Console, the Response details option is not functioning.

W-13674034

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions.

W-13514487

The API Console is not rendering APIs properly.

W-13565177, W-13569134, W-13570941, W-13570959 and W-13570967
### Fixed Issues
Issue Resolution ID

Validating an application name is improved.

W-13209583

Links to other pages in the asset documentation are now working.

W-13471725

When requesting access to an API, an error message now displays if you try to create a new application with more than 150 characters.

W-13569048

Switching between versions no longer fails when the previous version does not have a documentation page.

W-13665874

In the API Console, the font of the Example label in the Payload section of the Documentation panel is the same size as the font of the request in the Try it panel.

W-13192142

The height of the API Console no longer resizes to accommodate the amount of content.

W-13119966

In the API Console, the documentation is no longer missing the Responses information.

W-13120027

In the API Console, the Documentation panel does not resize when interacting with it.

W-13120176

In the API Console, endpoints for API Specifications are now showing the same information as Exchange.

W-13122551

In the API Console, required fields cannot be deleted.

W-13503524

In the API Console, the Query parameters no longer lose focus when you try to add a value.

W-13513145

In the API Console, headers that are added no longer lose values.

W-13527312

In the API Console, endpoints now nest properly when sharing a prefix with methods defined.

W-13570851

In the API Console, long endpoint paths in the navigation panel now display with ellipses. Hover to show the full path.

W-13570887

In the API Console, the resource filter results no longer list values that are not resources.

W-13570903

In the API Console, the Query parameters field no longer overlaps the available space when values are long.

W-13570935

In the API Console, AsyncAPIs now shows the Channels section.

W-13570941

In the API Console, AsyncAPIs no longer show the Requests and Responses tabs in the Documentation panel.

W-13570959

In the API Console, AsyncAPIs no longer show the Headers and Payload sections in the Documentation panel.

W-13570967
### Known Issues
Known Issue Workaround ID

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions.

W-13514487

The API Console is not rendering APIs properly.

W-13565177, W-13569134, W-13570941, W-13570959 and W-13570967
### Fixed Issues

Issue Resolution

ID

When a portal is disconnected and the MuleSoft organization is linked again to the same Salesforce organization, the styling changes are now saved during the guided styling set up.

W-13505196

The search process is now improved when entering an API name in the search box.

W-13570503

An error message now displays when you try to change the Salesforce domain for a linked organization.

W-13580841

A user session now validates whether it is using the same Salesforce Organization ID that was used when connecting the portal.

W-13602052

An External Identity license check is now validated before the connection process.

W-13643584

An asset with an enumeration custom field no longer causes deserialization errors.

W-13717720
## [](#june-2023)June 2023 **June 13, 2023** MuleSoft announces the release of Anypoint API Experience Hub. API Experience Hub is an API management platform and digital experience that enables organizations to create vibrant API ecosystems within and outside the enterprise. API providers can share, promote, and engage with their developer community. Developers and partners can find, explore, and consume APIs designed anywhere from a single place. ### Known Issues

Known Issue

Workaround

ID

When a portal is disconnected and the MuleSoft organization is linked again to the same Salesforce organization, the styling changes are not saved during the guided styling set up.

W-13505196

In the Builder, an Insufficient Privileges Errors message displays when accessing the Administration > Login & Registration page.

Log in to the Salesforce organization as a System Administrator and confirm you can access the Administration > Login & Registration page.

W-13518741

The Builder cannot access the current asset library of uploaded images.

See Cannot See Images in the Builder Preview That Were Uploaded When Creating the Portal for instructions.

W-13514487

The API Console is not rendering APIs properly.

W-13565177

W-13569134

W-13570941

W-13570959

W-13570967
## [](#see-also)See Also - [API Experience Hub documentation](https://docs.mulesoft.com/jp/api-experience-hub/) - [トラブルシューティング](https://docs.mulesoft.com/jp/api-experience-hub/troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint API Governance Release Notes ## [](#august-2026)August 6, 2026 ### What’s New - Anypoint API Governance now governs a broader range of services, including APIs, agents, MCP servers, and gateways, so you can apply consistent standards across your entire service portfolio. For more information, see [Anypoint API Governance Overview](https://docs.mulesoft.com/api-governance/). - You can now use governance strategies to govern your services in the enhanced MuleSoft experience. For more information, see [general::exp-governance-work-with-strategies.adoc](#general::exp-governance-work-with-strategies.adoc). - You can now apply consistent governance across multiple gateway runtimes by creating governance strategies that target **Omni Gateways**, **Mule Gateways**, or all runtimes. This feature is available only in the enhanced MuleSoft experience. For more information, see [general::exp-governance-work-with-strategies.adoc](#general::exp-governance-work-with-strategies.adoc). - You can now connect third-party gateway providers and govern their APIs alongside your MuleSoft APIs. This feature is available only in the enhanced MuleSoft experience. For more information, see [general::exp-governance-govern-third-party-apis.adoc](#general::exp-governance-govern-third-party-apis.adoc). - You can now monitor conformance across all connected gateways and MuleSoft APIs in a single, unified report. This feature is available only in the enhanced MuleSoft experience. - You can now export a cross-gateway policy audit that consolidates policy application evidence across all connected providers and MuleSoft APIs to support compliance audits, such as SOC 2 and GDPR. This feature is available only in the enhanced MuleSoft experience. - The API Governance Dashboard now includes new metrics for your expanded service landscape, such as **Governance Coverage**, services governed by **Controls**, and services governed by **Automated Policies**. The distribution of services by type now includes MCP servers, LLM proxies, and gateways. For more information, see [Governance Dashboard Overview](https://docs.mulesoft.com/api-governance/dashboard-overview). - You can now generate and customize governance rulesets using natural language, empowering non-specialist teams to create governance without deep YAML expertise. For more information, see [Author a Governance Ruleset](https://dev-portal.mulesoft.com/skills/author-governance-ruleset.html). ## [](#march-2026)March 16, 2026 ### What’s New - Anypoint API Governance now supports gRPC. A new MuleSoft-provided gRPC Best Practices ruleset is available for governing gRPC APIs. For more information, see [GRPC Protobuf 3 Support](https://salesforce-misc.github.io/amf-docs/docs/related-docs/grpc_support). ## [](#november-2025)November 26, 2025 ### What’s New - This release adds support for MuleSoft Agent Fabric: Organizations can now ensure that agents are configured according to compliance specifications using the new MuleSoft-provided Agent Network Best Practices ruleset. This feature applies governance to both Agent and MCP assets. ## [](#june-2025)June 9, 2025 ### What’s New - This release introduces the Anypoint API Governance Dashboard, a pre-built tool designed to give you an overview of your API ecosystem and empower you to take actions that enhance governance and quality. The Dashboard consolidates essential out-of-the-box metrics in one place, enabling you to monitor the health and governance status of your API programs and respond directly to key insights. The Dashboard is the new API Governance landing page, and is available to all MuleSoft orgs out-of-the-box. Key features and benefits of the API Governance Dashboard include: - Organization-wide visibility: View a pre-built set of metrics for each of your organizations. - Clear status overview — The dashboard displays the current status of your APIs, such as: - **Unprotected APIs** (not currently managed in API Manager) - **Governed APIs** (under a governance profile) - **APIs in Exchange** (in the catalog) - **APIs in Production** (deployed in a production environment) - **APIs by Type** (REST API, AsyncAPI, and HTTP API) - Governance Dashboard Metrics — Gain visibility into your API governance posture with metrics like: - **Governance Usage by Profile Type** (active or draft profiles) - **Conformance Status** (conformant or not conformant API versions) - **Governance Usage by Profile Type** (high, medium, or low) - Take action directly — For metrics with associated actions, you can act directly from the Dashboard. For example, you can: - Create Governance Profiles to start governing unprotected APIs - View detailed lists of APIs based on metrics - Create Governance Profiles for APIs in Production For more information, see [Governance Dashboard Overview](https://docs.mulesoft.com/api-governance/dashboard-overview). ## [](#feb-2025)February 6, 2025 ### What’s New - This release adds support for MuleSoft for Agentforce: Topic Center to the Anypoint API Governance console. You can now view the auto-generated **SF API Topic Center** profile, and monitor the conformance of your topic and action-enabled APIs. See [トピックとエージェントアクションの API プロジェクトを有効化](https://docs.mulesoft.com/jp/anypoint-code-builder/ai-enabling-api-project-topic-center) and [Monitor Topic Center API Conformance in the Anypoint API Governance Console](https://docs.mulesoft.com/api-governance/monitor-api-conformance#gov-spec-topic-center). ## [](#sep-23-2024)September 23, 2024 ### What’s New - You can now govern HTTP APIs by selecting the **HTTP API** API type when creating governance profiles. - The `governance create profile` and `governance update profile` commands now support `http-api` for the `--criteria` option scope filter. See [List of Anypoint API Governance CLI Commands](https://docs.mulesoft.com/api-governance/cli-command-list). ## [](#jul-25-2024)July 25, 2024 (Reverted) This version is reverted. ## [](#may-29-2024)May 29, 2024 ### What’s New - You can now see the history of user actions related to Anypoint API Governance in the Anypoint Access Management audit logs. See [監査ログ](https://docs.mulesoft.com/jp/access-management/audit-logging). ## [](#apr-19-2024)April 19, 2024 ### What’s New - You can now use draft profiles to test settings before revealing their targeted APIs' conformance information across Anypoint Platform. See [Applying Rulesets to Identified APIs](https://docs.mulesoft.com/api-governance/create-profiles) and [Monitoring API Conformance](https://docs.mulesoft.com/api-governance/monitor-api-conformance). - You can now duplicate profiles to more quickly create profiles with similar settings. See [Duplicate a Governance Profile](https://docs.mulesoft.com/api-governance/create-profiles#duplicate-profile). ## [](#feb-5-2024)February 5, 2024 ### What’s New You can now use the MuleSoft-provided API Documentation Best Practices ruleset to apply governance to API documentation. See [Documentation Conformance](https://docs.mulesoft.com/api-governance/fix-documentation-conformance-issues). ### Fixed Issues
Issue Resolution ID

The conformance status information in the Notify Owner preview now matches that shown in the governance report.

W-14550668
## [](#nov-29-2023)November 29, 2023 ### What’s New - Administrators can now give users, such as developers, view-only access to the API Governance console so that they can: - View conformance information for their governed APIs. - Download conformance reports in CSV format. Governance administrators continue to have full access to API Governance. - Ruleset enhancements: - You can now use the MuleSoft-provided API Catalog Information Best Practices ruleset to apply governance to API catalog information. - You can now embed examples of valid and invalid code in rulesets to help developers understand conformance issues. For example, for the validation `operations-must-have-identifiers`: ```console examples: valid: | /events: get: displayName: get description: Gets a stream of results invalid: | /events: get: # missing displayName/identifier description: Gets a stream of results ``` - You can now add parameters to ruleset messages. When an API fails the validation, parameter values are resolved with contextual information. This makes messages more specific and easier to take action on. For example: ```console security-fields-operation-empty: message: | The security field of the operation {{core.name}} should not be empty. ``` See [Getting Started with Anypoint API Governance](https://docs.mulesoft.com/api-governance/get-started). ### Fixed Issues
Issue Resolution ID

Anypoint CLI now properly renders reports for legacy API projects.

W-14274588
## [](#oct-17-2023)October 17, 2023 ### What’s New - A new Mule API Management Best Practices ruleset provided by MuleSoft is published in Exchange. - New functionality is available to enable you to start governing instances by API version: - Organizations created after this release are automatically opted in. - For governance administrators: - If you don’t see an opt-in banner on the API Governance console, your organizations are already opted in. - If you see an opt-in banner, you can opt in to apply the new functionality to your organizations.
After you initiate the opt in, some profiles and APIs might show a status of In Validation until the update completes.
With the new functionality you can: - View specification and instance conformance in a single summary in Anypoint API Governance. - View governance conformance information in API Manager. - View comprehensive governance reports in Anypoint API Governance and API Manager. - Govern an entire API by API version, so that you can apply governance to all instances of all versions of an API. ### [](#limitations)Limitations - Anypoint CLI `governance` commands support validating API specifications only. - After opting in to use the new features: - When creating or updating a profile, you can no longer filter by lifecycle state. - In API Manager, the conformance status and report are shown only for REST APIs. See [Anypoint API Governance Overview](https://docs.mulesoft.com/api-governance/). ## [](#mar-4-2023)March 4, 2023 ### What’s New - You can now filter by **API Instance** information in your governance profiles. If you select the filter **Include only APIs with instances**, only specifications that have an instance in API Manager are included. You can then optionally filter by environment type and environment name. See [Create a Governance Profile Using the Anypoint API Governance Console](https://docs.mulesoft.com/api-governance/create-profiles#create-profile-in-console). - Rulesets now have a **Governed APIs** page where you can view the list of centrally-governed APIs to which the ruleset applies. See [Viewing Conformance Status in Exchange](https://docs.mulesoft.com/api-governance/find-and-fix-conformance-issues). - The Anypoint API Governance experience API is now published. Access the experience API in Exchange in your preferred Anypoint Platform control plane: - [US](https://anypoint.mulesoft.com/exchange/68ef9520-24e9-4cf2-b2f5-620025690913/api-governance-xapi) - [EU](https://eu1.anypoint.mulesoft.com/exchange/e0b4a150-f59b-46d4-ad25-5d98f9deb24a/api-governance-xapi) ### Fixed Issues
Issue Resolution ID

The Anypoint CLI 3.x command anypoint-cli governance api now successfully validates remote APIs and projects in folders when run in legacy mode.

W-12266732
## [](#dec-10-2022)December 10, 2022 ### What’s New - Your profiles can now be configured to automatically use the latest versions of rulesets in the console and through Anypoint CLI. - You can now search and filter to find specific rulesets when creating and updating profiles in the console. - You can now configure notifications using the CLI when creating and updating profiles. - The **Conformance Status** page for validated APIs in Exchange now shows the filter criteria that resulted in the API being validated against the listed rulesets. ## [](#oct-29-2022)October 29, 2022 ### What’s New - **New ruleset version selection in the console**: In the Anypoint API Governance console, you can now select ruleset versions while creating or updating a profile. - **Improved conformance assessment and remediation**: In Design Center, you can more easily add governance rulesets to an API project and create an editable branch of the API if there isn’t already one available. ### Fixed Issues
Issue Resolution ID

The Fix API definition button is replaced with visible links to improve navigation and visibility.

W-11551948, W-11764543

The CLI fix-me instructions page no longer has a code snippet that isn’t visible when the web browser page is sized to a narrow width.

W-11551279

The Best Practices ruleset’s wording is improved.

W-11801541

The search on the API Governance console is now case insensitive.

W-11861402

The anypoint-cli governance ruleset validate CLI command with a valid ruleset YAML file no longer fails on Windows 10.

W-11324475

Validation of an API definition with multiple rulesets now completes successfully.

W-11758147

The full API console is now visible or scrollable when the web browser page is sized to a narrow width.

W-11798282

The legends in the console cards no longer wrap into the second row when the web browser page is sized to a narrow width.

W-11798320
## [](#oct-01-2022)October 1, 2022 ### What’s New - You can now filter by lifecycle state in the API Governance profile wizard to more quickly select the APIs you want to govern. - You can now see the total governed APIs, total APIs, and subscription usage in one place in the API Governance dashboard. - The `anypoint cli governance` commands are enhanced to support ruleset customization. You can now: - Evaluate the rulesets that might apply to your API: `governance api evaluate` - Scaffold rules from data schemas: - `governance api inspect` - `governance ruleset init` - Customize individual rules by changing severity levels and enabling or disabling rules: - `governance ruleset info` - `governance ruleset clone` - The `governance create profile` and `governance update profile` commands now have the `--criteria` option, where you can specify filters for tags, categories, lifecycle states, and scope, such as API types `async-api` and `rest-api` - The `governance api validate` command now has the following options: - `--remote`, to enable you to validate APIs published in Exchange - `--remote-rulesets`, to enable you to validate APIs against rulesets published in Exchange See [List of Anypoint API Governance CLI Commands](https://docs.mulesoft.com/api-governance/cli-command-list). ## [](#sep-03-2022)September 3, 2022 ### What’s New ### [](#user-interface-improvements)User Interface Improvements - The **Conformance Status** page **Fix API Definition** menu selections more clearly indicate the subsequent action. - The instructions in the **Instructions for Anypoint CLI** page are easier to follow. ### Fixed Issues
Issue Resolution ID

A subscription limit alert now appears only when the number of governed APIs nears or exceeds the limit. Multiple versions of the same API in different profiles are counted as one governed API.

W-11611085

When you refresh the Conformance Status page, the conformance status shown on the page now immediately refreshes.

W-11565896
## [](#aug-20-2022)August 20, 2022 ### Fixed Issues
Issue Resolution ID

The rule provide-examples in the Anypoint Best Practices ruleset now properly validates API definitions that use !include or import fragment.

W-11324363

The description for the rule headers-must-have-descriptions in the Anypoint Best Practices ruleset is now "Provide descriptions for headers" rather than "Provide descriptions for request headers", because responses can also have headers.

W-11500353
## [](#aug-22)August 6, 2022 ### What’s New - A new **Conformance Status** page in Exchange enables API developers to see details about conformance of their validated API definitions to governance rulesets. For details, see [Viewing Conformance Status in Exchange](https://docs.mulesoft.com/api-governance/find-and-fix-conformance-issues). - You are now notified when your number of governed APIs nears or exceeds your subscription level. - You can now review your monthly usage of Anypoint API Governance in usage reports. For details, see [Viewing Usage Reports](https://docs.mulesoft.com/jp/general/usage-reports). ## [](#july-22)July 9, 2022 ### What’s New - You can now govern AsyncAPI APIs by selecting the **AsyncAPI** API type when creating governance profiles. - When you filter by categories while creating or updating a governance profile, you can now see information about categories applied to the filtered APIs. The number of categories applied to an API is denoted by **Categories** followed by a number in parenthesis. Hover over **Categories** to see more details. - Command enhancements: - `anypoint-cli governance api validate` This command now accepts an API project ZIP file or folder and downloads dependencies, including rulesets against which to validate. You can optionally use the `--rulesets` option to specify a comma-separated list of local rulesets. See [governance api validate](https://docs.mulesoft.com/api-governance/find-conformance-issues#governance-api-validate). - `anypoint-cli governance ruleset validate` This command now accepts the following as the ruleset definition parameter: - A ruleset definition YAML file - A ZIP file that contains an API project with an `exchange.json` file that specifies the ruleset as the main file - A folder that contains an API project with an `exchange.json` file that specifies the ruleset as the main file See [governance ruleset validate](https://docs.mulesoft.com/api-governance/custom-rulesets-validate-and-publish#governance-ruleset-validate). ## [](#june-22)June 11, 2022 ### What’s New - Anypoint API Governance now groups notifications by API so that only one email is sent if an API is validated by multiple rulesets - You can now select the following recipients for the automated conformance notifications: - **API Publisher**: Email the API publisher by using the email address specified in the listed Anypoint Platform account - **API Contact**: Email the contact specified in the asset in Exchange - **Others**: Email to a comma-separated list of email addresses - The UI is now reactive, more responsive, and more accessible ## [](#april-22)April 30, 2022 ### What’s New - In the new API Governance console: - Configure profiles to apply rulesets to specific sets of APIs - Monitor the conformance status of APIs that are validated as part of the profiles - Export reports of API conformance data in CSV format - Notify API owners to encourage them to make their APIs conformant to the profiles - In Design Center in API Designer: - Apply rulesets to your APIs to see what parts of the definitions are noncomformant - Update the APIs to be conformant and republish them to Exchange - In Exchange: - Discover and view the new governance rulesets provided by MuleSoft - View conformance status for governed API assets - Using the new Anypoint CLI governance commands: - Automate governance in your automation tools, such as CI/CD pipelines or scripts ## [](#see-also)See Also - [Anypoint API Governance documentation](https://docs.mulesoft.com/api-governance/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting Anypoint CLI](https://docs.mulesoft.com/api-governance/cli-commands-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint API Governance Release Notes Anypoint API Governance provides centralized governance to help you ensure your APIs follow best practices, industry regulations, and security standards. As API owners add, edit, and promote APIs, API Governance helps you monitor and address conformance across your organization. The following release notes are provided for API Governance: - [Anypoint API Governance Release Notes](https://docs.mulesoft.com/jp/release-notes/api-governance/api-governance-release-notes) ## [](#see-also)See Also - [Anypoint API Governance Overview](https://docs.mulesoft.com/api-governance/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Code Builder Release Notes **進行中のベータリリース**​: **クラウド IDE は進行中のベータリリースです**​。ベータ状態での Anypoint Code Builder の使用には、IDE で入手できる、該当するベータサービス契約条件が適用されます。 Use the Anypoint Code Builder integrated development environment (IDE) for your API designs, implementations, and integration development. Work locally with Anypoint Code Builder for Desktop on Microsoft Visual Studio Code (VS Code) or from your browser with Anypoint Code Builder on Anypoint Platform. The IDEs support the development lifecycle: - API specification design (AsyncAPI, gRPC, OAS, and RAML), a mocking service for testing, source control, and publication to Anypoint Exchange - API implementation features for importing supported API specifications (AsyncAPI, GraphQL, gRPC, OAS, and RAML) and autogenerating interfaces (scaffolding) for flows and error handlers within a Mule application - Integration development to connect systems, transform data to required formats, and provide business logic to manage messages and events programmatically within a Mule application ## [](#october-23-2026)October 23, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.28.1 To use this extension pack, see [Set up Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements, see [Anypoint Code Builder Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### Fixed Issues
Issue Resolution ID

Global Elements now shows required external libraries as expected when those libraries are defined on the connector configuration, such as Spring Config.

W-24612980

Anypoint Code Builder updates its OpenJDKs.

W-24630068
## [](#october-21-2026)October 21, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.28.0 To use this extension pack, see [Set up Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements, see [Anypoint Code Builder Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-october-21-2026)What’s New This release introduces these features. - [Support for Mule Runtime 4.13.0](#support-for-mule-runtime-4-13-october-21-2026) - [Support for Mule Maven Plugin 4.10.3](#support-for-mule-maven-plugin-4-10-3-october-21-2026) - [Support for Scaffolding OAS 3.1 API Specifications](#oas-3-1-scaffolding-october-21-2026) - [Support for Anypoint Platform Private Cloud Edition](#pce-support-october-21-2026) - [Support for Locally Added Mule Runtime Versions](#local-mule-runtime-october-21-2026) - [Support for Hyperforce in the UK Region](#support-for-uk-region-october-21-2026) - [Agent Network Improvements](#agent-network-improvements-october-21-2026) ### [](#support-for-mule-runtime-4-13-october-21-2026)Support for Mule Runtime 4.13.0 Anypoint Code Builder now supports Mule runtime version 4.13.0 for developing, running, and deploying Mule applications. Create new projects with Mule runtime 4.13.0 or update existing projects to use this runtime version in project properties. For more information, see [Bundled Mule Runtime Versions](https://docs.mulesoft.com/jp/anypoint-code-builder/int-versions#bundled-runtimes). ### [](#support-for-mule-maven-plugin-4-10-3-october-21-2026)Support for Mule Maven Plugin 4.10.3 Anypoint Code Builder now supports Mule Maven Plugin version 4.10.3 for developing, running, and deploying Mule applications. Create new projects with Mule Maven Plugin 4.10.3 or update existing projects to use this plugin version in the project POM. For more information, see [Mule Maven Plugin Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-release-notes). ### [](#oas-3-1-scaffolding-october-21-2026)Support for Scaffolding OAS 3.1 API Specifications Anypoint Code Builder now scaffolds Mule projects from OpenAPI Specification (OAS) 3.1 API specifications, in addition to the formats already supported. You can scaffold from JSON or YAML specifications and get structured diagnostics when a specification can’t be scaffolded. For more information, see [OAS、RAML、および GraphQL API の実装](https://docs.mulesoft.com/jp/anypoint-code-builder/imp-implement-api-specs). ### [](#pce-support-october-21-2026)Support for Anypoint Platform Private Cloud Edition Anypoint Code Builder now connects to Anypoint Platform Private Cloud Edition (PCE) instances hosted in your own data center, so you can design, develop, and deploy Mule applications against a private control plane. For more information, see [Cloud Hosts](https://docs.mulesoft.com/jp/anypoint-code-builder/#us-eu-clouds). ### [](#local-mule-runtime-october-21-2026)Support for Locally Added Mule Runtime Versions Anypoint Code Builder now lists a Mule runtime version that you copy into `${user.home}/AnypointCodeBuilder/runtimes/user-installed`. The version appears when you create a project and in **Project Properties**, so you can use a runtime version that Anypoint Code Builder does not include, such as a version for Private Cloud Edition. For more information, see [Add a Mule Runtime Version Locally](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#add-local-mule-runtime). ### [](#support-for-uk-region-october-21-2026)Support for Hyperforce in the UK Region Anypoint Code Builder now supports the [United Kingdom Cloud](https://gb1.platform.mulesoft.com) control plane of Anypoint Platform. For more information about Anypoint Platform availability on control planes, see [Cloud Hosts](https://docs.mulesoft.com/jp/anypoint-code-builder/#us-eu-clouds). ### [](#agent-network-improvements-october-21-2026)Agent Network Improvements This release includes improvements for authoring and deploying agent networks for Agent Fabric. For more information, see the [Agent Fabric Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes). ### Fixed Issues
Issue Resolution ID

MUnit tests now resolve BOM-managed dependency versions correctly when run from the Anypoint Code Builder UI.

W-23448108

The Transformation Builder now preserves namespaces when mapping input for services that expect XML.

W-23768550

The Transformation Builder now handles several mapping edge cases correctly.

W-23768451

Anypoint Code Builder no longer retries Mule framework instance creation repeatedly when a security key is invalid.

W-23864352

The debugger now visually indicates a pause after the Publish operation when using VM Pub/Sub.

W-23959396

FIPS configuration now references the generated java.fips.security file in the design service JVM launch command.

W-24176669

FIPS setup now applies the trust store password alongside a custom javax.net.ssl.trustStore path, so MAC verification succeeds on the generated BCFKS cacerts.

W-24176694

Anypoint Code Builder now keeps the Mule module metadata version and javaSpecificationVersions consistent automatically.

W-24192883

AccessDeniedException errors no longer recur in the logs on Windows.

W-24207276

Secure properties connections now resolve reliably instead of intermittently reporting an unknown connection type.

W-24220432

Anypoint Code Builder no longer deletes the shared JDK that the platform JVM is running on.

W-24236209

Canvas component icons now render correctly instead of showing as Unknown when connector types resolve after the first render.

W-24280838

Code search results now open directly in Code View.

W-24278214

The Error Type list is now contextual and no longer shows every error type.

W-24335809

Anypoint Code Builder desktop workspace settings no longer allow arbitrary JVM arguments that could lead to command execution.

W-24408390

Export Project now uses the current project’s name and saves the JAR to the selected folder.

W-24455874
## [](#september-22-2026)September 22, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.27.0 To use this extension pack, see [Set up Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements, see [Anypoint Code Builder Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-september-22-2026)What’s New This release introduces these features. - [Managing Global Elements](#managing-global-elements-september-22-2026) - [Upgrading All Connectors with One Click](#upgrade-all-connectors-september-22-2026) - [Viewing Project Dependencies](#viewing-project-dependencies-september-22-2026) - [Navigating to Flows That Reference a Subflow](#navigate-to-referencing-flows-september-22-2026) ### [](#managing-global-elements-september-22-2026)Managing Global Elements You can now add, edit, and delete global configurations directly from **Global Elements**, without editing XML. Click **New Configuration** to create connector configurations, TLS contexts, object stores, caching strategies, API Autodiscovery, global error handlers, import project references, and properties files, and encrypt secure property values from the same view. For more information, see [anypoint-code-builder::int-global-config-elements.adoc](#anypoint-code-builder::int-global-config-elements.adoc). ### [](#upgrade-all-connectors-september-22-2026)Upgrading All Connectors with One Click You can now upgrade every connector in a project to its latest version with a single action in **Project Properties**, so you no longer need to update connectors one at a time. For more information, see [Upgrade All Connectors in a Project](https://docs.mulesoft.com/jp/anypoint-code-builder/int-versions#upgrade-all-connectors). ### [](#viewing-project-dependencies-september-22-2026)Viewing Project Dependencies Anypoint Code Builder now provides a visual way to view the dependencies added to a project, so you no longer need to inspect the project’s POM file to see what a project depends on. For more information, see [anypoint-code-builder::start-view-project-dependencies.adoc](#anypoint-code-builder::start-view-project-dependencies.adoc). ### [](#navigate-to-referencing-flows-september-22-2026)Navigating to Flows That Reference a Subflow From the canvas context menu, you can now select a subflow and navigate to every flow that references it, making it easier to trace execution paths and assess the impact of changes across a project. For more information, see [Find Flows That Reference a Subflow](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components#find-referencing-flows). ### Fixed Issues
Issue Resolution ID

The Add Component (+) button now appears on hover in the descriptive UI as expected.

W-23437230

Bundled connectors now load reliably on startup and are no longer skipped due to a stale interrupt flag.

W-24014499

The design service now works as expected for projects using JDK 17 with Mule runtime 4.6.x.

W-24079635

The canvas now renders components correctly when the dynamic tooling cache file is truncated, instead of showing every component as Unknown.

W-24154114

FIPS trust store setup now succeeds with BCFKS source keystores when a custom Cacerts path is configured.

W-24152130

Loading the bundled connector cache no longer causes out-of-memory errors on low-resource machines.

W-24117873
## [](#september-4-2026)September 4, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.26.2 To use this extension pack, see [Set up Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements, see [Anypoint Code Builder Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-september-4-2026)What’s New This release introduces these features. - [Support for Mule Runtime 4.12](#support-for-mule-runtime-4-12-september-4-2026) - [Upgrade Mule Applications with the upgrade-mule-app Skill](#upgrade-mule-app-skill-september-4-2026) ### [](#support-for-mule-runtime-4-12-september-4-2026)Support for Mule Runtime 4.12 Anypoint Code Builder now supports Mule runtime version 4.12 for developing, running, and deploying Mule applications. Create new projects with Mule runtime 4.12.0 or update existing projects to use this runtime version in project properties. For more information, see [Bundled Mule Runtime Versions](https://docs.mulesoft.com/jp/anypoint-code-builder/int-versions#bundled-runtimes). ### [](#upgrade-mule-app-skill-september-4-2026)Upgrade Mule Applications with the upgrade-mule-app Skill MuleSoft Vibes now includes the `upgrade-mule-app` skill, which upgrades a Mule application to a later Mule runtime version and Java version. For more information, see [anypoint-code-builder::vibes-skills.adoc](#anypoint-code-builder::vibes-skills.adoc). ### Fixed Issues
Issue Resolution ID

Error handlers scaffolded from an API specification now map the Error Type correctly.

W-19987815

Running a Mule application on Windows no longer requires administrator permission.

W-23172858

The canvas now loads as expected when the project.json file is corrupted.

W-23846800

MCP server network requests now succeed when a proxy is configured.

W-23853401

The debugger’s Step Over action now pauses at the next step when Save & Hot Deploy is used.

W-23959338
## [](#august-24-2026)August 24, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.25.0 To use this extension pack, see [Set up Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements, see [Anypoint Code Builder Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-august-24-2026)What’s New This release introduces these features. - [Managing API Spec Versions](#managing-api-spec-versions-august-24-2026) - [Navigating to Flows in Reusable Libraries](#navigate-to-flows-in-reusable-libraries-august-24-2026) - [Triggering On-Demand Scheduler from the Canvas](#trigger-on-demand-scheduler-from-canvas-august-24-2026) - [Agent Network Improvements](#agent-network-improvements-august-24-2026) ### [](#managing-api-spec-versions-august-24-2026)Managing API Spec Versions Anypoint Code Builder now lets you view API specification details and change API dependency versions from **Project Properties**. When you update a version, the IDE re-scaffolds your project and notifies you about the result, including errors and incompatibilities. You can also manage API versions with MuleSoft Vibes. For more information, see [anypoint-code-builder::imp-manage-api-spec-versions.adoc](#anypoint-code-builder::imp-manage-api-spec-versions.adoc). ### [](#navigate-to-flows-in-reusable-libraries-august-24-2026)Navigating to Flows in Reusable Libraries Anypoint Code Builder now supports **Go to Flow** for flows imported from Mule project dependencies (reusable libraries). You can open those flows in a read-only canvas and view their read-only XML to inspect them at design time, and step into them while debugging a Flow Reference. For more information, see [Navigate to the Referenced Flow](https://docs.mulesoft.com/jp/anypoint-code-builder/acb-component-flow-ref#navigate-to-the-referenced-flow). ### [](#trigger-on-demand-scheduler-from-canvas-august-24-2026)Triggering On-Demand Scheduler from the Canvas During an active run or debug session, you can now trigger a scheduler flow on demand from a **Play** button on the scheduler source node, without waiting for the next scheduled run. The flow runs exactly as it would on a scheduled trigger, respecting your breakpoints and interceptors. For more information, see [Trigger a Scheduler On Demand](https://docs.mulesoft.com/jp/anypoint-code-builder/int-trigger-flows#trigger-scheduler-on-demand). ### [](#agent-network-improvements-august-24-2026)Agent Network Improvements This release includes improvements for authoring and deploying agent networks for Agent Fabric. For more information, see the [Agent Fabric Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes). ### Fixed Issues
Issue Resolution ID

Canceling the login process no longer displays an unexpected error.

W-20636555

The Problems tab no longer shows incorrect validation warnings for global configuration.

W-21322966

Opening a project no longer overwrites the maven-compiler-plugin source level to 1.8 when the project declares a different Java specification version.

W-23357940

The Re-scaffold this local API command is now available when you set up a multi-root workspace manually as expected.

W-23493499

The FIPS custom cacerts path setting now applies during FIPS conversion as expected.

W-23517641

Implement This Local API no longer fails intermittently on Windows with a Connection is closed error.

W-23546215

The IDE no longer rewrites pom.xml with identical content during DataSense tooling-cache sync.

W-23604327
## [](#august-6-2026)August 6, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.24.1 To use this extension pack, see [Set up Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements, see [Anypoint Code Builder Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-august-6-2026)What’s New This release introduces these features. - [Support for Hyperforce in the Australia Region](#support-for-hyperforce-australia-august-6-2026) - [Agent Network Improvements](#agent-network-improvements-august-6-2026) - [Cloud IDE (Beta) Retirement](#cloud-ide-retirement-august-6-2026) ### [](#support-for-hyperforce-australia-august-6-2026)Support for Hyperforce in the Australia Region Anypoint Code Builder now supports the [Australia Cloud](https://au1.platform.mulesoft.com) control plane of Anypoint Platform. For more information about Anypoint Platform availability on control planes, see [Cloud Hosts](https://docs.mulesoft.com/jp/anypoint-code-builder/#us-eu-clouds). ### [](#agent-network-improvements-august-6-2026)Agent Network Improvements This release includes improvements for authoring and deploying agent networks for Agent Fabric. For more information, see the [Agent Fabric Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes). ### [](#cloud-ide-retirement-august-6-2026)Cloud IDE (Beta) Retirement Cloud IDE (Beta) is scheduled for retirement on August 31, 2026. August 30, 2026 is the last day you can access Cloud IDE (Beta). Download your projects to work from Desktop IDE. Learn more in [Migrate a Project from Cloud IDE to Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/int-import-mule-project#migrate-cloud-to-desktop). ## [](#july-21-2026)July 21, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.24.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the Visual Studio Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-july-21-2026)What’s New This release introduces these features. - [FIPS-Compliant Security Support](#fips-support-in-dependencies-july-21-2026) - [Support for Scaffolding OAS 3.0 APIs That Reference Exchange Fragments](#oas-fragment-scaffolding-july-21-2026) ### [](#fips-support-in-dependencies-july-21-2026)FIPS-Compliant Security Support Anypoint Code Builder now provides FIPS 140-2 and FIPS 140-3 compliant support through updated dependencies and UI support in the desktop IDE. This helps teams configure and run secure development workflows more consistently in regulated environments. For more information, see [anypoint-code-builder::start-fips-compliance.adoc](#anypoint-code-builder::start-fips-compliance.adoc). ### [](#oas-fragment-scaffolding-july-21-2026)Support for Scaffolding OAS 3.0 APIs That Reference Exchange Fragments Anypoint Code Builder now scaffolds OAS 3.0 API specifications that use `$ref` to reference Anypoint Exchange fragments. For more information, see [API 仕様フラグメントの作成および使用](https://docs.mulesoft.com/jp/anypoint-code-builder/des-create-api-fragments). ### Fixed Issues
Issue Resolution ID

Runtime default arguments now parse correctly when you configure application run settings.

W-23122012

The Transformation Builder component now appears with a consistent display name across the UI as expected.

W-22775707

The Add Component button now behaves consistently when you add components to your flow.

W-22293870

Autocomplete now supports partial text matches so you can find items faster while typing.

W-22454656

API spec projects now appear correctly in the Project and Project Dependencies panels.

W-22715444

XML debugger launch configurations now accept the noDebug property in launch.json as expected.

W-23122632
## [](#july-14-2026)July 14, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.23.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-july-14-2026)What’s New This release introduces these features. - [Guided Determinism in Agent Broker and Agent Network 2.0](#support-mule-soft-agent-broker-july-14-2026) - [Improved Exchange Search Results](#improved-exchange-search-results-july-14-2026) - [Improved Java Detection with the Bundled JDK](#use-bundled-jdk-for-java-detection-july-14-2026) ### [](#support-mule-soft-agent-broker-july-14-2026)Guided Determinism in Agent Broker and Agent Network 2.0 Build agent and brokers and networks with predictable, governed orchestration using [Agent Script](https://developer.salesforce.com/docs/ai/agentforce/guide/agent-script.html)—a graph-based language that gives you explicit control over how brokers coordinate agents, tools, and LLMs. In Agent Network 2.0, agent brokers use guided determinism to separate LLM-powered reasoning from deterministic control flow, giving you intelligent decision-making where you need it and guaranteed execution paths everywhere else. For more information, see [Agent Fabric Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes) and [Building Agent Networks for Agent Fabric](https://docs.mulesoft.com/agent-network/latest/af-agent-networks). ### [](#improved-exchange-search-results-july-14-2026)Improved Exchange Search Results Anypoint Code Builder now uses platform search components for Exchange search experiences, which helps you find and select Exchange assets more consistently. This update improves search behavior across supported Exchange workflows. For more information, see [Exchange からのコネクタのインポート](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components-import-connector-exchange). ### [](#use-bundled-jdk-for-java-detection-july-14-2026)Improved Java Detection with the Bundled JDK Anypoint Code Builder now uses the JDK in the `AnypointCodeBuilder` folder as the Java instance for supported workflows. This reduces setup issues and helps projects open and run more reliably across environments. For more information, see [Mule Runtime の問題とエラー](https://docs.mulesoft.com/jp/anypoint-code-builder/troubleshoot-mule-runtime-errors). ### Fixed Issues
Issue Resolution ID

Mule language server operations now complete reliably without timing out during normal workflows.

W-23049419

MuleSoft Vibes requests now route through the proxy correctly.

W-23056251

The metadata tree now stays expanded when you open Transformation Builder with custom metadata.

W-23061578

Go To Flow now opens the referenced flow as expected.

W-23090107

Debugging now opens dependency flows referenced by flow-ref as expected.

W-23128325

Skill auto-update failures no longer display an error toast in the IDE.

W-23148357

Opening Mule projects on Windows now handles lowercase drive-letter paths correctly during Maven validation.

W-21968540

Uncommenting a component that Studio disabled now preserves valid Mule code.

W-22708555

The canvas now loads as expected when dependency resolution takes longer than usual.

W-23032933

DataWeave scripts now update correctly on Windows for array and nested mapping scenarios.

W-23122433

Anypoint Code Builder now connects reliably on slower computers during startup.

W-23232084

Projects that use CI-friendly ${revision} parent POM versions now load the flow canvas as expected.

W-23293643
## [](#june26-2026)June 26, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.22.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-June26-2026)What’s New This release introduces these features. - [Faster Startup on Windows](#faster-startup-on-windows-june-26-2026) - [Faster Extension Startup with Optimized Bundle Loading](#faster-extension-startup-with-optimized-bundle-loading-june-26-2026) - [Updated MCP Connector Support](#updated-mcp-connector-support-june-26-2026) ### [](#faster-startup-on-windows-june-26-2026)Faster Startup on Windows Anypoint Code Builder now starts faster on Windows by optimizing Maven bookkeeping and bundle-loading operations during initialization. This reduces startup overhead so you can open projects and begin development more quickly. For more information, see [Anypoint Code Builder Startup](https://docs.mulesoft.com/jp/anypoint-code-builder/#acb-startup). ### [](#faster-extension-startup-with-optimized-bundle-loading-june-26-2026)Faster Extension Startup with Optimized Bundle Loading Anypoint Code Builder now reads bundle directories directly from the extension path, improving how workspaces initialize extension assets. This streamlines startup behavior and reduces delays in project readiness. For more information, see [Anypoint Code Builder Startup](https://docs.mulesoft.com/jp/anypoint-code-builder/#acb-startup) ### [](#updated-mcp-connector-support-june-26-2026)Updated MCP Connector Support Anypoint Code Builder now uses an updated MCP connector version to improve compatibility with current MCP integrations. This helps keep tool-driven workflows reliable across supported scenarios. For more information, see [MCP Connector in Anypoint Code Builder](#anypoint-code-builder::vibes-get-started.adoc#mcp-connector-in-ACB). ### Fixed Issues
Issue Resolution ID

The configuration panel now loads as expected for connectors that use XML simple-content elements with attributes.

W-23048952

Local JSON-RPC socket connections now initialize more reliably on slower or constrained machines.

W-23156379

MuleSoft Vibes Anypoint Platform tools now fetch user profiles correctly in the India region when listing applications.

W-23008805

Language server requests now continue reliably in slower environments without timing out prematurely during startup.

W-23049419

Platform shutdown now handles failed JSON-RPC initialization without additional NullPointerException errors.

W-23049504

Custom connectors that define union-typed object parameters now load correctly.

W-22863083
## [](#june18-2026)June 18, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.22.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-June18-2026)What’s New This release introduces these features. - [Manage Global Elements from the UI](#global-elements-june-2026) - [Efficient Screen Space Usage in Transformation Builder](#efficient-screen-space-usage-in-transform-builder-june-2026) - [India Cloud Control Plane Region Support](#hyperforce-india-region-support-june-2026) ### [](#global-elements-june-2026)Manage Global Elements from the UI Anypoint Code Builder now provides a **Global Elements** panel for viewing and managing the shared configurations your Mule application depends on, including connector configurations, properties files, TLS contexts, and error handlers. Open the panel from the canvas toolbar or **Project Properties**, and add, edit, or remove configurations using the form editor, source editor, or MuleSoft Vibes. For more information, see [anypoint-code-builder::int-global-config-elements.adoc](#anypoint-code-builder::int-global-config-elements.adoc). ### [](#efficient-screen-space-usage-in-transform-builder-june-2026)Efficient Screen Space Usage in Transformation Builder **Transformation Builder** now provides enhanced workspace flexibility with improved screen real estate management. For more information, see [Customize the Transformation Builder Layout](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-dw-expressions#customize-transformation-builder-layout). ### [](#hyperforce-india-region-support-june-2026)India Cloud Control Plane Region Support Anypoint Code Builder is now available on the [India Cloud](https://in1.platform.mulesoft.com) control plane of Anypoint Platform. For more information about Anypoint Platform availability on control planes, see [Cloud Hosts](https://docs.mulesoft.com/jp/anypoint-code-builder/#us-eu-clouds). ### Fixed Issues
Issue Resolution ID

Transformation Builder source metadata now remains visible after mapping operations.

W-22767859

Implicit DataWeave variables, such as correlationId, now work as expected.

W-20610661

Auto-discovery now adds the required namespace information automatically.

W-22158386

Expression Builder now keeps the cursor position stable so functions insert in the expected location.

W-22154279

Namespace additions now apply correctly when editing configurations.

W-22941217

Mule runtime downloads from the CLI now complete successfully.

W-22432886

Mule runtime download authentication now works correctly in non-production environments.

W-22434986

Path handling on Windows now uses consistent separators during URI comparisons.

W-22770705
## [](#june11-2026)June 11, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.21.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### Fixed Issues
Issue Resolution ID

MCP tools now display correctly across supported IDEs. The connectivity MCP server can appear without registered tools in this release, which is the expected behavior.

W-22854860
## [](#May26-2026)May 26, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.20.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### Fixed Issues
Issue Resolution ID

Anypoint Code Builder no longer shows duplicate or triplicate items when selecting a project for testing.

W-22565928
## [](#May19-2026)May 19, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack. - Extension pack version: 1.19.2 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Compatibility](#compatibility). ### [](#features-May19-2026)What’s New This release introduces these features. - [Auto-Scroll Canvas During Debugging](#auto-scroll-canvas-debugging-may-2026) - [Enhanced Breakpoint Visualization](#breakpoint-highlighting-may-2026) - [MuleSoft Vibes Updates](#vibes-updates-may-2026) - [Deprecation of the Develop the American Flights App Tutorial](#american-flights-tutorial-deprecated-may-2026) ### [](#auto-scroll-canvas-debugging-may-2026)Auto-Scroll Canvas During Debugging The canvas now automatically scrolls to and centers the active component when you step through your application during debugging. For more information, see [Canvas Behavior While Debugging](https://docs.mulesoft.com/jp/anypoint-code-builder/int-debug-mule-apps#canvas-execution-indicators). ### [](#breakpoint-highlighting-may-2026)Enhanced Breakpoint Visualization Active breakpoints during debugging now display with a yellow outline on the canvas, making it easy to identify which component execution has paused at. For more information, see [Mule アプリケーションのデバッグ](https://docs.mulesoft.com/jp/anypoint-code-builder/int-debug-mule-apps). ### [](#vibes-updates-may-2026)MuleSoft Vibes Updates #### [](#manage-default-skills)Manage Default Skills Default Skills in MuleSoft Vibes give agents preloaded, reusable instructions for common Mule development tasks such as project work, connector setup, and dependency resolution. For more information, see [Manage Default Skills in MuleSoft Vibes](#anypoint-code-builder::vibes-skills.adoc#manage-default-skills). #### [](#run-multiple-integration-projects-locally)Run Multiple Integration Projects Locally Run multiple integration projects locally in one runtime to validate service-to-service behavior before deployment. Use MuleSoft Vibes to automatically create and run a reusable multi-project run configuration, including run and debug scenarios. You can also run saved configurations from the standard **Run and Debug** panel. For more information, see [anypoint-code-builder::vibes-run-multiple-integration-projects-locally.adoc](#anypoint-code-builder::vibes-run-multiple-integration-projects-locally.adoc). #### [](#modernize-development-with-the-new-descriptive-ui)Modernize Development with the New Descriptive UI MuleSoft Vibes now features a vertical canvas that uses AI to generate plain-language descriptions for every component in your flow. Build, modify, and document integrations using natural language commands or direct UI interactions. For more information, see [Descriptive UI in MuleSoft Vibes](#anypoint-code-builder::vibes-get-started.adoc#vibes-descriptive-ui). ### [](#american-flights-tutorial-deprecated-may-2026)Deprecation of the Develop the American Flights App Tutorial The **Develop the American Flights App** tutorial is deprecated. For an alternative tutorial, see [チュートリアル: API ビルドの最初から最後まで](https://docs.mulesoft.com/jp/general/api-led-overview). ### Fixed Issues
Issue Resolution ID

The debugger now focuses on the correct file as expected when debugging multiple files simultaneously.

W-20493459

Sample data specified in custom metadata examples now loads correctly in the transformation window.

W-21314835

Sample data displayed in Expression Builder now matches the persisted sample data as expected.

W-21319134

Type propagation now resolves correctly without unexpected failure errors.

W-21485471

The debugger now displays Mule Message component values correctly for non-Java data types.

W-21707026

Copying JSON from a Mule event in debug mode now works as expected without errors.

W-21707258

Type propagation no longer fails when component location returns null values.

W-21735935

Variable value updates in the debugger now work as expected during debugging sessions.

W-21936302

Error breakpoint exception messages now provide clearer and more actionable information.

W-21957772

Breakpoint icons on the canvas now correctly display their muted state.

W-21986288

Signing in now works as expected for all users.

W-22000712

Document identifiers now propagate correctly across all batch steps in the Batch Processing connector.

W-22002465

The Go To Flow navigation feature no longer has intermittent failures.

W-22043908

Error objects are now visible in the VARIABLES panel when debugging inside error handler scopes.

W-22099074

Mapping icons now work correctly when variables are present in scripts.

W-22100547

MuleSoft Vibes no longer shows ValidationException errors for large prompts or PII context window connection errors.

W-22107257

MuleSoft Vibes MCP server connections now succeed for servers that don’t support resources or prompts.

W-22116159

The MimeType attributes no longer incorrectly show expression mode as supported.

W-22164971

Project artifact IDs can now be directly inherited in parent POMs.

W-22166146

The undo command now executes on the first invocation instead of requiring two attempts.

W-22170160

The debugger can now introspect ImmutableBatchJobResult objects in the On Complete phase.

W-22177315

Token refresh no longer enters an infinite loop due to setTimeout overflow.

W-22251798

The Apply button in the HTTP Listener Global Element configuration now works as expected.

W-22321659

The debugger now processes files within nested folders when debugging as expected.

W-22349447
## [](#April27-2026)April 27, 2026 Anypoint Code Builder releases these patch versions in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.18.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn more about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). - Cloud IDE version: 1.18.3 This cloud IDE version runs the 1.18.3 extension pack. ### Fixed Issues
Issue Resolution ID

Applying policies with required schema properties that have default values in Agent Networks no longer causes failures.

W-22170170
## [](#April20-2026)April 20, 2026 Anypoint Code Builder releases these versions in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.18.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). To learn about hardware and storage requirements for the desktop IDE, see [Desktop IDE Hardware and Storage Requirements](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#hardware-storage-requirements). - Cloud IDE version: 1.18.1 This cloud IDE version runs the 1.18.0 extension pack. ### [](#features-April20-2026)What’s New This release introduces these features. - [Canvas Actions](#canvas-actions-april-2026) - [Namespaces in DataWeave Scripts](#namespaces-in-dw-scripts) - [MuleSoft Vibes Updates](#mulesoft-vibes-updates-april-20-2026) - [Centralized Errors and Warnings](#acb-logs-centralized-panel-april-2026) ### [](#canvas-actions-april-2026)Canvas Actions You can now refactor flows directly from the canvas, including moving, copying, and extracting components into new flows or subflows. Fore more information, see [Refactor Flows Using Canvas Actions](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components#canvas-actions). ### [](#namespaces-in-dw-scripts)Namespaces in DataWeave Scripts Anypoint Code Builder now supports metadata containing namespace URIs. For more information, see [Namespaces in Generated DataWeave](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-dw-expressions#namespaces-in-generated-dataweave). ### [](#mulesoft-vibes-updates-april-20-2026)MuleSoft Vibes Updates MuleSoft Vibes now supports custom metadata and reusable instructions with skills. #### [](#custom-metadata-full-support)Custom Metadata Full Support Create, delete, fetch, or edit custom metadata across these metadata types: csv, copybook, excel, fixed width, flat file, json, java, simple type, and xml. For more information, see [Custom metadata in MuleSoft Vibes](#anypoint-code-builder::int-manage-custom-metadata.adoc#custom-metadata-vibes). #### [](#reusable-instructions-with-skills)Reusable Instructions with Skills Create and reuse instructions with MuleSoft Vibes Skills. Save instructions as skills to easily apply them across multiple conversations and projects, ensuring consistency and efficiency in your interactions. For more information, see [anypoint-code-builder::vibes-skills.adoc](#anypoint-code-builder::vibes-skills.adoc). ### [](#acb-logs-centralized-panel-april-2026)Centralized Errors and Warnings The new **ACB Logs** tab provides a single, table-based view of warnings and errors from every Anypoint Code Builder extension, so you can scan, filter, and search without switching between channels. You can filter by log level, source extension, date range, and project name. Expand an entry for full details such as stack traces and include Anypoint Code Builder Logs automatically when you export troubleshooting information. For full raw log streams from one channel at a time, keep using the **Output** panel (for example, **Mule DX Server** or **Mule DX Server: Scaffolding**). For more information, see [出力パネルを開く](https://docs.mulesoft.com/jp/anypoint-code-builder/start-open-output-panel). ### Fixed Issues
Issue Resolution ID

Enum option lists now appear as expected inside arrays in the configuration UI.

W-20031362

Publishing a project to Anypoint Exchange no longer creates an example project unexpectedly.

W-20969183

Opening a project no longer takes more time than expected to load XML.

W-21154541

Opening a project or XML file again on Windows no longer takes an excessive amount of time.

W-21239937

Importing a project without sources no longer produces poor error handling.

W-21284401

Anypoint Code Builder AI no longer suggests an outdated Salesforce connector version.

W-21290906

The Transform Message component now shows the output tree for an inner field as expected.

W-21309692

Drag-and-drop mapping now works as expected for nested objects in flat file formats.

W-21310967

Metadata validation errors now work as expected for JMS and AS2 elements with Mule runtime 4.11.0.

W-21314344

DataWeave data preview works as expected on failure and shows log output.

W-21324741

The editor and workspace no longer show an unsaved file warning after saving all changes.

W-21327302

Importing a new API from Anypoint Exchange from the command palette no longer requires a reload to show changes.

W-21341100

Opening a file in a non-Mule project no longer raises nested project errors.

W-21341353

Field concatenation no longer fails across arrays and different sources in DataWeave.

W-21346401

Breakpoints in a source now stop execution as expected.

W-21352232

Sample generation no longer fails after changing custom metadata for the first time in the transformation window.

W-21421249

Progressive mapping now extends existing mappings as expected instead of replacing them.

W-21462334

The factory now handles the object-store-caching-strategy component as expected.

W-21467904

Large log files no longer slow down error logging.

W-21469432

The Mule::p function reference now resolves as expected.

W-21472817

Incorrect underline placement for DataWeave expressions in set-variable XML is fixed.

W-21473016

Verifying a test connection no longer randomly breaks.

W-21473880

A stack overflow in SimpleReferenceType.metadataConstraints in the DataWeave editor is fixed.

W-21485285

DataWeave editor no longer shows inconsistent counts of errors and warnings on the Problems tab.

W-21530956

The resolution of the p() function in DataWeave now works as expected.

W-21533179

Embedded documents now regenerate in DataWeave as expected.

W-21549247

The message reference now resolves in DataWeave as expected.

W-21550252

A StatusLogger format or conversion error in the design service is fixed.

W-21552602

Missing icons for date fields in DataWeave transforms are fixed.

W-21560510

Tests that affected reliability of the test suite are now stabilized and working as expected.

W-21575885

DataWeave syntax errors are now highlighted in configuration XML as expected.

W-21627864

POM.xml now resolves as expected when using a relative path.

W-21629880

An unexpected child element error in DefaultContainerProcessor in the DataWeave editor is fixed.

W-21631829

MUnit files now resolve in the workspace as expected.

W-21631910

Spacing around the Transform Message workspace in the DataWeave UI is tightened.

W-21638610

Saving files now persists changes as expected.

W-21642439

Clearing search on the Metadata tab now works as expected.

W-21642458

The canvas no longer fails to load.

W-21666326

Null pointer errors in the DataWeave virtual file system are fixed.

W-21667508 / W-21770880

The HTTP port is released as expected after use.

W-21706607

The restarts now pick up your latest changes as expected.

W-21706655

New components are no longer occasionally inserted inside a nested body instead of after it on the canvas.

W-21707238

Error messages now appear in the Mule event view as expected.

W-21707484

Intermittent socket timeout errors from Anypoint Exchange search are fixed.

W-21709965

A stack overflow in SimpleReferenceType.metadataConstraints caused by a self-referencing variable is fixed.

W-21712344

Contained element content now overrides the parent operation’s general content on the canvas as expected.

W-21712983

The first multi-selected canvas node (Shift+click) no longer opens the configuration UI unexpectedly.

W-21780098

The Project Properties header now shows the project name instead of the path.

W-21804043

Mapping editor errors caused by VFS initialization failures are fixed.

W-21809434

Corrupted JDK downloads no longer report success.

W-21841815

Autocompletion now works as expected in customer projects.

W-21850315

The Extract To form now shows the correct project’s file name in the drop-down.

W-21869137

The Extract To form now hides non-extractable nodes when multiple nodes are selected.

W-21869146

The Extract To form no longer appears for nodes that can’t be extracted.

W-21869157

The Extract To form now selects the current file by default as the extraction target.

W-21873522

Transform mapping data is no longer overwritten when variables are declared in the header.

W-21886152

Signing out of Anypoint Code Builder now works as expected.

W-21892267

Creating MUnit tests from a flow now works as expected.

W-21950086

Library configuration changes are now saved as expected when a shared library already exists in the POM.

W-21966352

Log files no longer use an incorrect file extension.

W-21978917
## [](#March20-2026)March 20, 2026 Anypoint Code Builder releases these patch versions in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.17.2 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.17.3 This cloud IDE version runs the 1.17.3 extension pack. ### Fixed Issues
Issue Resolution ID

Opening multiple projects no longer causes errors during the initialization of the embedded DataWeave language server.

W-21618731

The file picker for DataWeave transformation configurations now opens as expected on Windows.

W-21651056

API governance validations no longer fail and display a "Validation failed: try again later" error message on Windows.

W-21568869
## [](#March16-2026)March 16, 2026 Anypoint Code Builder releases these versions in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.17.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.17.2 This cloud IDE version runs the 1.17.2 extension pack. ### [](#whats-new)What’s New This release introduces these features. - [Anypoint Code Builder Support for gRPC](#anypoint-code-builder-grpc-support) - [Use More MIME Types in the DataWeave Transformer](#more-mime-types-dataweave-transformer) - [Export Mule Project Enhancements](#export-mule-project-unified) - [MuleSoft Vibes Updates](#mulesoft-vibes-updates-march-16-2026) - [MuleSoft MCP Server Project Updates](#mulesoft-mcp-server-project-updates) - [Expanded MIME Type Support in DataWeave Transform](#dataweave-transform-mime-type) - [Removal of Code Snippets Feature](#code-snippets-removal) ### [](#anypoint-code-builder-grpc-support)Anypoint Code Builder Support for gRPC Anypoint Code Builder now supports gRPC for API specification design, scaffolding, and implementation. Create and import gRPC API specifications in Protocol Buffers (proto) format, scaffold Mule projects based on those specifications, and implement the generated flows using the Anypoint Code Builder. For more information, see [anypoint-code-builder::des-design-grpc-api-spec.adoc](#anypoint-code-builder::des-design-grpc-api-spec.adoc). ### [](#more-mime-types-dataweave-transformer)Use More MIME Types in the DataWeave Transformer Map and transform data using any MIME type supported by the Mule platform. The **DataWeave Transformer** component now supports all Mule runtime MIME types, moving beyond the previous JSON-only limitation. These improvements ensure parity with the Mule runtime and enable you to build diverse integrations without workarounds. ### [](#export-mule-project-unified)Export Mule Project Enhancements Export a Mule project as a shareable or deployable JAR using a single action in the context menu and command palette. You can optionally include project sources for deployable JARs so the JAR can be opened in the IDE and used for deployment. For more information, see [Exporting Mule Projects](https://docs.mulesoft.com/jp/anypoint-code-builder/int-export-mule-project). ### [](#mulesoft-vibes-updates-march-16-2026)MuleSoft Vibes Updates Build and manage integrations more efficiently with support for adding images to your conversation, using templates, and generating applications that include your private Exchange assets. These updates allow you to use a wider variety of assets for application generation while tracking your resource usage. #### [](#add-files-to-prompts-with-multi-modal-support)Add Files to Prompts with Multi-modal Support Drag and drop images directly into the prompt window to provide context for your tasks. You can add up to 10 files per conversation to help MuleSoft Vibes understand your specific requirements. For more information, see [Add Files to Messages with Multi-Modal Support](#anypoint-code-builder::vibes-get-started.adoc#vibes-multimodal-file-prompts). #### [](#generate-applications-from-templates)Generate Applications from Templates Use local templates from Anypoint Exchange as the foundation for your generated applications. This ensures that new integrations follow your organization’s established patterns and best practices. For more information, see [Generate Applications from Exchange Templates](#anypoint-code-builder::vibes-create-integrations.adoc#vibes-generate-apps-from-templates). #### [](#include-custom-connectors-in-generated-applications)Include Custom Connectors in Generated Applications Generate applications that use custom connectors published to your private Anypoint Exchange. This update allows you to integrate with internal or specialized systems during the automated generation process. For more information, see [Include Custom Connectors in Generated Applications](#anypoint-code-builder::vibes-create-integrations.adoc#vibes-custom-connectors-generated-apps). #### [](#invoke-exchange-apis-using-rest-connectors)Invoke Exchange APIs Using REST Connectors Generate applications that call APIs published to Anypoint Exchange. MuleSoft Vibes now uses REST connectors to invoke these APIs, making it easier to reuse existing assets across your landscape. For more information, see [Invoke Exchange APIs Using REST Connectors](#anypoint-code-builder::vibes-create-integrations.adoc#vibes-exchange-apis-rest-connectors). #### [](#monitor-token-consumption-in-mulesoft-vibes)Monitor Token Consumption in MuleSoft Vibes Track the number of tokens consumed for each request and task directly within the Vibes window. This visibility helps you manage your usage and understand the resource cost of your generation tasks. For more information, see [Monitor Token Consumption in MuleSoft Vibes](#anypoint-code-builder::vibes-get-started.adoc#vibes-token-consumption-monitoring). ### [](#mulesoft-mcp-server-project-updates)MuleSoft MCP Server Project Updates MuleSoft MCP Server includes tool updates. For more information, see [MuleSoft MCP Server Release Notes](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-mar16-26). ### [](#dataweave-transform-mime-type)Expanded MIME Type Support in DataWeave Transform DataWeave Transform in Anypoint Code Builder now expands support for MIME types across the Transform mapper. The component automatically adjusts DataWeave script headers based on the selected metadata and improves preview capabilities across additional formats, including Excel (XLSX) and CSV files with custom separators. These improvements help ensure that generated transformations remain consistent with Mule runtime behavior across a wider range of data formats. ### [](#code-snippets-removal)Removal of Code Snippets Feature Anypoint Code Builder deprecates the code snippets feature. ### Fixed Issues
Issue Resolution ID

The Open Project tool no longer closes the current workspace when opening a project folder during application generation.

W-21351774

Core models for the Mule runtime are now correctly cached. This change prevents the design service from starting unnecessarily and improves startup performance.

W-21354463

Workspaces now open correctly when you create an integration project from a template.

W-21414040

Integration projects created from a template now correctly include JavaSpecifications in the mule-artifact.json file.

W-21439730

Project Properties now correctly reflect the JDK version immediately after it is downloaded.

W-21514611

Login now works as expected on VDI machines after a previous logout.

W-21145337

Applications now correctly inherit characteristics from the parent pom file.

W-21368450

Instantiate a Mule framework instance using plugins without encountering NoSuchMethodException.

W-20922748

Project-specific connector operations now display correctly in the canvas without requiring you to reopen the file.

W-21582912
## [](#Feb24-2026)February 24, 2026 Anypoint Code Builder releases these patch versions in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.16.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.16.2 This cloud IDE version runs the 1.16.2 extension pack. ### Fixed Issues
Issue Resolution ID

The bundled Mule runtime is no longer copied empty in the Web IDE.

W-21314634

Mule projects located outside of the Anypoint Studio workspace folder now import correctly into the Anypoint Code Builder workspace.

W-21294903

Fixed an issue where project deployment to CloudHub 2.0 failed because the system looked for an incorrect JAR file name after a successful package operation.

W-21304545

The custom metadata UI now loads correctly for projects with paths that contain spaces.

W-21308475
## [](#Feb17-2026)February 17, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.16.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.16.0 This cloud IDE version runs the 1.16.0 extension pack. ### [](#features-Feb17-2026)What’s New This release introduces these features. - [External Library Configuration for Mule Projects](#external-libraries-mule-projects-feb17-26) - [Custom Metadata Support](#custom-metadata-support-feb17-26) - [AI-Powered Auto Mapping with Enhanced Error Feedback](#ai-powered-auto-mapping-feb17-26) - [Bundled Runtimes for Instant Project Editing](#bundled-runtimes-feb17-26) - [Workspace Validation for Mule Projects](#workspace-validation-feb17-26) ### [](#external-libraries-mule-projects-feb17-26)External Library Configuration for Mule Projects You can now add and manage external libraries for Mule projects directly from Anypoint Code Builder. This lets you configure project-level dependencies using recommended libraries, Maven dependencies, or local files. Configured libraries are added to the project POM and applied to all components that require them. You can also edit or remove libraries from the same configuration interface. ### [](#custom-metadata-support-feb17-26)Custom Metadata Support You can now define and assign your own custom metadata within the canvas UI to accurately visualize and test your organization’s data structures for your integration projects. By using a dedicated tab in the configuration panel, you can create metadata for inputs and outputs using common formats like CSV, JSON, and XML to make sure your data transformations are accurate. For more information see [Managing Custom Metadata](#anypoint-code-builder::int-manage-custom-metadata.adoc). ### [](#ai-powered-auto-mapping-feb17-26)AI-Powered Auto Mapping with Enhanced Error Feedback You can now better debug your transformations with comprehensive error feedback for GenAI actions—including authorization, metadata, and request limits—ensuring a more reliable and guided mapping experience. The **Transformation Builder** now provides categorized error guidance to help you troubleshoot authorization issues, metadata problems, and request limit errors, making it easier to diagnose and resolve issues when using AI-assisted transformations and mapping features. ### [](#bundled-runtimes-feb17-26)Bundled Runtimes for Instant Project Editing You can now open and edit projects instantly without downloading separate Mule runtime versions. Anypoint Code Builder now ships bundled runtimes used for editing and metadata discovery (DataSense). You must download the exact runtime versions if running or debugging your app. ### [](#workspace-validation-feb17-26)Workspace Validation for Mule Projects Anypoint Code Builder now validates your project structure and provides guidance when a Mule project isn’t configured correctly. When creating new projects, you can select **Create in workspace** to organize multiple projects in a multi-root workspace. You can also import and validate existing Anypoint Studio workspaces and use MuleSoft Vibes to switch between workspaces using natural language. For more information, see [Working with Workspaces](#anypoint-code-builder::start-workspaces.adoc). ### [](#mulesoft-mcp-server-project-updates-2)MuleSoft MCP Server Project Updates MuleSoft MCP Server includes tool updates. For more information, see [MuleSoft MCP Server Release Notes](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-feb17-26). ### Fixed Issues
Issue Resolution ID

Duplicate runtime arguments from run and debug commands are removed, and arguments are now passed correctly without redundancy in the execution string.

W-20293482

Standalone DataWeave library projects in Anypoint Code Builder now execute correctly across all workspace configurations.

W-20334373

Error handling logic now works as expected and provides uniform behavior and messaging consistency across the IDE.

W-20364853

Project properties and connection lists now display correctly and are no longer hidden or empty.

W-20531631

Mule Maven plugin dependencies now resolve correctly in clean .m2 repositories without manual intervention.

W-20825706

Processors can now be added as expected to the beginning of existing components within the Process Record section of a Batch Job component.

W-20926265

Components are now placed in the correct location during drag operations on the UI canvas.

W-20926514

The Transform Message component content is now visible without the requirement of CDATA tags.

W-21146025

Database connection configurations in the global configuration page now update the XML source correctly.

W-21147450

Socket timeout exceptions no longer occur when loading connector operators.

W-20201721
## [](#Feb06-2026)February 6, 2026 Anypoint Code Builder releases this version in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.15.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.15.0 This cloud IDE version runs the 1.15.0 extension pack. ### [](#features-Feb06-2026)What’s New This release introduces these features. ### [](#mule-runtime-4-11-0-support)Support for Mule Runtime 4.11.0 Anypoint Code Builder now supports Mule runtime 4.11.0 for creating and managing Mule projects. Create new projects with Mule runtime 4.11.0 or update existing projects to use this runtime version in project properties. ### [](#new-features-agent-networks-feb6-26)Agent Network Project Updates Agent networks now support these authentication types: - OAuth 2.0 OBO Credential Injection using OAuth 2.0 Token Exchange or Microsoft Entra ID On-Behalf-Of protocols - In-Task Authorization Code For more information about these types, see the [Agent Network YAML File Reference](https://docs.mulesoft.com/agent-network/latest/af-project-files#authentication-types). ### [](#mulesoft-mcp-server-project-updates-3)MuleSoft MCP Server Project Updates MuleSoft MCP Server includes tool updates. For more information, see [MuleSoft MCP Server Release Notes](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-feb6-26). ### [](#scaffold-and-implement-apis-with-vibes)Scaffold and Implement APIs with Vibes MuleSoft Vibes can now scaffold and implement API specifications on your local machine or from Anypoint Exchange. This ensures accurate project structures and a seamless transition from scaffolding to adding application logic, reducing manual configuration and preventing project errors. ### Fixed Issues
Issue Resolution ID

The command 'mule-dx-mule-dev.runMuleProject' error no longer occurs when selecting Run Mule Project in the Mule option.

W-20978630

You can now edit nested connections from different XML files as expected.

W-20898437

The Exchange search filter is no longer breaking search results.

W-21018002
## [](#Jan15-2026)January 15, 2026 Anypoint Code Builder releases this patch version in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.14.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.14.1 This cloud IDE version runs the 1.14.1 extension pack. ### [](#features-Jan15-2026)What’s New This release introduces these features. ### [](#dataweave-mapping-enhancements)DataWeave Mapping Enhancements - **Advanced nested array mapping**: **DataWeave Transform** now supports dragging fields within nested objects and arrays more intuitively. When mapping fields into an existing `map` function, the UI automatically resolves the correct scope and variables to generate accurate DataWeave scripts. - **Automated hierarchical array mapping**: **DataWeave Transform** now intelligently handles mapping between different array levels. When dragging a top-level source array to a nested target array, the tool automatically generates the required parent-to-child wrapping and map functions to maintain the correct output structure. - **Intelligent scalar-to-object refactoring**: **DataWeave Transform** now automatically handles the transition from scalar assignments to nested object structures. When you map nested fields within an object node, Anypoint Code Builder refactors the script to ensure a valid hierarchy without requiring manual code cleanup. ### [](#canvas-loading-status-indicator)Canvas Loading Status Indicator A loading status indicator now shows while the canvas initializes. This enhancement provides more visible and integrated feedback during project loading and synchronization tasks, improving the overall responsiveness of the design experience. ### [](#optimized-canvas-connectors)Optimized Canvas Connectors The design of flow edges and connectors is improved to increase visual density. This update allows for a more compact representation of integration flows, enabling users to view more content and steps within the canvas. #### [](#agent-network-project-creation)Agent Network Project Creation You can now create Agent Network projects directly from the project creation flow. The project creation interface includes Agent Network configurations for setting up advanced project environments within the Anypoint Code Builder workspace. #### [](#refined-api-specification-selection)Refined API Specification Selection The project creation form is now clearer and more intuitive when starting new Mule projects based on existing API definitions. #### [](#centralized-dependency-error-reporting)Centralized Dependency Error Reporting The dependency-related errors are now shown in the **PROBLEMS** tab so that you can identify and resolve Maven resolution or library conflicts more efficiently without searching through background logs. #### [](#mulesoft-mcp-server-project-updates-4)MuleSoft MCP Server Project Updates MuleSoft MCP Server includes three new tools: - `implement_api_spec` - `generate_munit_test` - `modify_munit_test` For more information about these tools, see [MuleSoft MCP Server Release Notes](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-jan15-26). #### [](#new-features-agent-networks-jan15-26)Agent Network Project Updates - Agent network now supports Gemini models. Specify these parameters in the LLM section of the `agent-network.yml` file. - `thinkingBudget`: Sets a token budget for the reasoning phase. (Applies only to Gemini 2.5 series.) - `thinkingLevel`: Controls the depth of the reasoning process. (Applies only to Gemini 3 series.) - `temperature`: Controls randomness. - `topP`: Nucleus sampling parameter. - `responseLogprobs`: Whether to return log probabilities. - `maxOutputTokens`: Maximum number of tokens that can be generated in the response. For more information about these parameters, see the [Agent Network YAML File Reference](https://docs.mulesoft.com/agent-network/latest/af-project-files#agent-network-yaml). - The agent broker is now aware of which LLM model you select and uses the appropriate API. For example, if you’re using an OpenAI model, the broker now uses function calling rather than sending the system prompt, broker instructions, tools, and history as one prompt. ### [](#cleaner-project-context-menus)Cleaner Project Context Menus Project context menus are now consistent across root and multi-root workspaces for supported Mule project types. Anypoint Code Builder actions are shown only when they apply to the selected project or folder, and related actions are grouped more clearly to improve discoverability. ### [](#cleaner-command-palette-actions)Cleaner Command Palette Actions The Command Palette now shows a cleaner and more consistent set of Anypoint Code Builder commands across single-root and multi-root workspaces. Commands are clearly named, consistently prefixed with MuleSoft, and organized using descriptive categories such as API, Mule, and Agent Network. Only actions that initiate complete workflows appear in the Command Palette. Context-specific commands are available only when the required project context is active. ### Fixed Issues
Issue Resolution ID

Fixed an issue where switching between factory configurations in a JMS publish component caused XML corruption.

W-20159060

Fixed an issue in the Java module New operation where the error icon remained visible after the Constructor value is successfully configured. The UI now correctly clears the error state after valid configuration data is provided.

W-20117914

Fixed an issue in DataWeave Transform where mapping fields from a nested source to a nested target sometimes resulted in incorrect script nesting. The UI now accurately maintains the nested structure and context when multiple fields are mapped to the same target path.

W-20208318

Fixed an issue where creating a new API project inside a nested workspace folder prevented the project from opening or being added to the current workspace. Projects now open correctly regardless of their folder depth within the workspace.

W-20212604

Drag actions in Transformation Builder no longer occasionally result in a UI error state.

W-20222649

Anypoint Code Builder now correctly shows an error message when you open a project located outside the root folder or within the current workspace.

W-20249789

The canvas now accurately identifies and displays synthetic routes within connectors.

W-20332947

Anypoint Code Builder now displays an error related to project properties when your project fails to initialize correctly.

W-20481957

The editor now correctly uses UTF-8 encoding across all platforms to ensure that consistent data is displayed in the Transformation Builder input and output windows.

W-20494670

Fixed an issue with MCP tools that took no input arguments.

W-20474172

The DataWeave editor no longer becomes slow or unresponsive when working with large transformations, including freezes triggered by auto-save.

W-19966256

DataWeave scripts no longer lose their formatting or collapse into a single line when you edit connection configurations or make unrelated project changes.

W-20082580

The canvas no longer gets stuck in an infinite loading state.

W-20214677

The HTTP Request component no longer reverts header or body values back to payload when editing them in the canvas UI.

W-20581927

DataWeave mappings no longer drop type casting when concatenating expressions.

W-20582971
## [](#Dec18-2025)December 18, 2025 Anypoint Code Builder releases this patch version in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.13.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.13.1 This cloud IDE version runs the 1.13.1 extension pack. ### Fixed Issues
Issue Resolution ID

CLI for Agent Fabric Plugin is updated to the latest version to address reported security vulnerabilities.

W-20573569
## [](#Dec12-2025)December 12, 2025 Anypoint Code Builder releases this version in the Cloud IDE. - Cloud IDE version: 1.13.0 This cloud IDE version runs the 1.13.0 extension pack. For a complete list of the features and fixed issues included in this release, see the [December 11, 2025](#Dec11-2025), Anypoint Code Builder release notes. ## [](#Dec11-2025)December 11, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack. - Extension pack version: 1.13.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). ### [](#features-Dec11-2025)What’s New This release introduces these features. #### [](#new-enhancements-to-the-dataweave-transform-component)New Enhancements to the DataWeave Transform Component This update includes several improvements to UI stability and the generative AI experience, such as optimized behavior in the **Transform Message** component UI and more responsive error handling for AI-powered actions. #### [](#stability-enhancements)Stability Enhancements ##### [](#improved-mcp-config-reference-editing)Improved MCP Config Reference Editing The Inference Connector configuration panel now reliably allows the added client to be edited when configuring an MCP config reference field. ##### [](#stabilized-audience-settings-for-mcp-listener)Stabilized Audience Settings for MCP Listener Configuration of the audience field within the responses group of the MCP Tool Listener is now reliable and consistent, ensuring that the field appears correctly, even when imported from an XML file. #### [](#new-features-agent-networks-dec11-25)Agent Network Project Updates - The [Agent Network YAML File Reference](https://docs.mulesoft.com/agent-network/latest/af-project-files#agent-network-yaml) now includes all available parameters for each section. - The `agent-network.yml` file now exposes new parameters from OpenAI. Specify these parameters in the `llm` section settings for OpenAI. - `reasoningEffort`: Constrains reasoning effort for reasoning models. - `temperature`: Controls randomness in the output. - `topP`: Nucleus sampling parameter. - `topLogprobs`: Number of most likely tokens to return at each position. - `maxOutputTokens`: Maximum number of tokens to generate. For more information about these parameters, see the [Agent Network YAML File Reference](https://docs.mulesoft.com/agent-network/latest/af-project-files#agent-network-yaml) and [OpenAI Platform API Reference](https://platform.openai.com/docs/api-reference/introduction). - These agent network dependencies are updated: - OpenAI SDK version is updated to 4.8.0. - Mule HTTP Connector version is updated to 1.11.0. - A2A Connector version is updated to 0.4.0-BETA. - A2A SDK version is updated to 0.3.3-final. - MCP Connector version is updated to 1.3.0. - Caffeine version is updated to 3.2.3. - JaCoCo version is updated to 0.8.11. - `aspectj` version is updated to 1.9.22.1. - Common text version is updated to 1.14.0. #### [](#git-installation-no-longer-required)Git Installation No Longer Required - You no longer need to install git as part of the Anypoint Code Builder installation process. ### Fixed Issues
Issue Resolution ID

The Autodiscovery element no longer appears in the Add Component panel.

W-16891052

Users now receive a notification after successful deployment to CloudHub as expected.

W-18079627

DataWeave output metadata is now correct in component fields.

W-18553945

The canvas now correctly reflects unsaved changes.

W-18657386

CloudHub redeployment no longer fails intermittently.

W-18727013

The Transformation Builder window for DataWeave no longer shows an error in the input sample on Windows systems.

W-18911593

The flow configuration UI attribute for enabling default events is now correctly written in the XML file.

W-19117758

The configuration UI no longer shows a default value for data types when no default value exists in the metadata.

W-19175333

Errors updating XML no longer occur on the canvas when updating auto closed tags.

W-19211738

Editing metadata in the Transform Message component now works correctly if the source is a DataWeave file.

W-19273485

The M2_REPO variable is now used to populate the repository at startup.

W-19476167

The debugger now correctly pauses in the main flow and sub-flow after using Step into.

W-19547488

Toggling between INLINE or Bean mode to None now works correctly in the configuration panel.

W-19623905

You can now input text for Operations in MuleSoft Vectors Connector as expected.

W-19637694

Validation now shows errors as expected for missing fields in the Database component.

W-19679369

The debugger now shows the breakpoint information as expected if Step into is used on a flow reference pointing to a flow in the configuration of a sub-folder.

W-19679780

Unauthorized errors no longer occur when the token expires.

W-19971283

A2A Connector configurations now appear in version 0.4.0-BETA as expected.

W-20004568

If deployment to CloudHub 2.0 fails, the user now gets an error notification.

W-20030018

Transformation Builder no longer closes unexpectedly on Windows systems when pressing Ctrl+Backspace.

W-20031151

Error messages no longer repeatedly pop up for the same error during dependency resolution.

W-20036183

A path traversal vulnerability in MuleSoft MCP Server tools is now fixed.

W-20039005

Intermittent corruption of the JDK installation no longer occurs.

W-20052935

A server-side template injection vulnerability in MCP flow generation tools is now fixed.

W-20053148

The Dev Agent web fetch tool timeout is increased from 10 to 30 seconds to support slow-loading URLs.

W-20084547

Expression Builder no longer breaks or displays incorrectly if the DataWeave transformation contains a long script.

W-20086693

The configuration UI in the Java module now successfully loads the Method field values.

W-20112957

Misleading stack traces from the Design Service logs that appeared when loading custom connectors are removed.

W-20131222

The HTTP Listener component now secures the password during TLS setup as expected.

W-20135822

The Anypoint Code Builder Integration Extension now uses the correct version of org.mule.weave dependencies instead of using the 2.6.1. version.

W-20159499

The Anypoint Code Builder Platform Extension version 5.9.7 no longer breaks in Windows systems.

W-20192341

The Expression Builder gear icon is now clickable as expected.

W-20203410

The Audience field in the MCP tool listener configuration no longer intermittently fails to display.

W-19127724

The MCP configuration reference field in the Inference Connector can now be edited as expected.

W-20018055

The internal platform jar socket is now restricted to listening on localhost only, mitigating a potential Remote Code Execution (RCE) vulnerability.

W-20194553

Object group element attributes now update correctly in the UI, and inconsistent behavior related to empty element deletion in the Transform script field no longer occurs.

W-20244840

Custom metadata now shows as expected in the Output column of the mapping window for transform components.

W-20062856

SAP Connector test connection no longer fails.

W-19124681

The scaffolding process no longer fails when the project ID used for scaffolding doesn’t match the project ID that was created.

W-20201660

Projects that are inherited from a Parent POM that use Maven’s CI-friendly version properties no longer incorrectly report that the parent POM can’t be found.

W-20272484

The Connectors tab in Project Properties no longer fails to load when an incompatible connector version causes the Mule framework introspection to fail.

W-19284941

The code editor of a component is now resizable and shows line numbers.

W-20060203

The drag and drop action for simple Transform components no longer breaks the canvas view and flow XML on Windows systems.

W-20439430

The MuleSoft Dev Agent stream no longer intermittently throws an incorrect ValidationException error embedded within stream chunks.

W-20068043

MuleSoft Dev Agent no longer fails due to streaming errors or server timeouts during operations.

W-20023190

MuleSoft Dev Agent no longer experiences a five-second delay before making the first API call after being opened.

W-20077965

The Map with AI feature in Transformation Builder now correctly displays user access errors when they occur.

W-20276613

The Edit Sample Data File icon is no longer disabled in the Map with AI feature in Transformation Builder. Also, the default call when opening the Transform UI is removed, and the UI now shows a message instead of a spinning icon when the GenAI API call fails.

W-20276613

Anypoint Code Builder no longer fails to render all configuration parameters, such as the HTTP Requestor parameter, for the RosettaNet Connector in the Configuration UI.

W-20190237

Anypoint Code Builder no longer displays an incorrect compatibility error message when a project dependency is missing in the current Exchange environment.

W-19750194

The Import global element now recognizes flows defined within the imported plugin as expected.

W-19986168

The Visual Designer no longer fails to show and recognize shared configuration components when they’re inherited from a Parent POM.

W-20178132

Keyboard shortcuts, such as Command+C and Command+V, now work as expected when selecting and editing text in the DataWeave Editor.

W-20162326
This release addresses the following issue with agent network projects:
Issue Resolution ID

The distributed trace now correctly includes LLM calls for an agent broker.

W-19825674
## [](#Nov12-2025)November 12, 2025 Anypoint Code Builder releases this patch version in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.12.2 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.12.2 This cloud IDE version runs the 1.12.2 extension pack. ### Fixed Issues
Issue Resolution ID

Anypoint Code Builder Platform Extension no longer fails on Windows systems.

W-20192341
## [](#Nov10-2025)November 10, 2025 Anypoint Code Builder releases this patch version in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.12.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.12.1 This cloud IDE version runs the 1.12.1 extension pack. ### Fixed Issues
Issue Resolution ID

Some dependencies are updated to address reported vulnerabilities.

W-20115973
## [](#Nov4-2025)November 4, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack. - Extension pack version: 1.12.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.12.0 This cloud IDE version runs the 1.12.0 extension pack. For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Nov25)What’s New This release introduces these features: - [Support for Maven Multi-Module Projects and Parent POM Files](#multi-module) - [Map with AI Now Detects and Applies Existing Metadata MIME Types](#dw-metadata-mime-types) - [Agent Network Project Updates](#agent-networks-nov-25) - [Support for Connection Configurations Defined in Dependencies](#dependency-connection-configs) #### [](#multi-module)Support for Maven Multi-Module Projects and Parent POM Files Anypoint Code Builder now supports Maven multi-module projects and parent POM file functionality. Define properties, dependencies, and versions once and share them across multiple projects, guaranteeing consistency and eliminating version drift. For more information, see [IDE へのプロジェクトのインポート](https://docs.mulesoft.com/jp/anypoint-code-builder/int-import-mule-project). #### [](#dw-metadata-mime-types)Map with AI Now Detects and Applies Existing Metadata MIME Types The **Map with AI** tool is now enhanced to automatically detect and apply the existing metadata MIME types (such as `application/json`, `application/xml`, and `application/java`) defined in your project’s flow. When generating a DataWeave script, **Map with AI** now reads the input and output formats from the surrounding connectors and correctly applies those types to the generated script’s directives. #### [](#agent-networks-nov-25)Agent Network Project Updates The agent broker now dynamically adapts when any downstream AI asset changes its contract because the MCP and A2A metadata automatically refreshes every hour. #### [](#dependency-connection-configs)Support for Connection Configurations Defined in Dependencies Anypoint Code Builder now detects and loads connection configurations that are defined in external project dependencies. The tool scans all import statements in your Mule flows, locates the related files inside dependency JARs, and extracts the connection configurations they define. These configurations appear in both the XML view and the canvas view. ### Fixed Issues
Issue Resolution ID

Anypoint Code Builder now correctly resolves Maven settings and configurations against the settings.xml file and no longer creates a temporary acb_settings.xml file.

W-19128433

The canvas now refreshes automatically after updating the runtime version in project properties.

W-19285759

Pasting a component after a disabled component no longer breaks the canvas UI or prevents the flow from rendering.

W-19719169

The Error Handler configuration now displays all applicable error types based on the components used in the flow as expected.

W-19788055

The Agent Fabric flag is now correctly enabled when switching from the Control Plane to EU Cloud in the desktop IDE.

W-19810833

The context menu no longer appears for nodes in the read-only Agent Fabric Authoring canvas.

W-19840137

The auto approval for tool execution in the Dev Agent chat window now works as expected.

W-19842516

Java processes no longer remain active after closing Anypoint Code Builder.

W-19849557

The local .m2 repository is now populated correctly at startup.

W-19860834

Dev Agent no longer becomes unresponsive.

W-20051611

Validation decorators now appear correctly in the canvas after adding a new connector or updating dependencies in the project pom.xml file.

W-18741926

The Java debug server that started automatically when running Mule apps is now disabled by default to prevent unauthorized access.

W-18968450

Anypoint Code Builder now loads the Maven settings.xml file at startup to correctly generate the acb_settings.xml file with the user’s configuration.

W-19128433

MUnit configurations defined in the parent pom.xml file are now correctly inherited by child projects.

W-19284704

The minMuleVersion value in the mule-artifact.json file is no longer overwritten by Anypoint Code Builder. Runtime feature toggles are now decoupled from this property.

W-19374653

Anypoint Code Builder no longer becomes unresponsive or stuck on the loading screen when adding components to a flow in customer projects.

W-19525162

The canvas now opens the correct configuration panel when selecting components.

W-19687980

Disabled components can now be copied and pasted successfully without triggering errors during node duplication.

W-19760175

DataWeave actions now appear in the correct position within the context menu.

W-19883653

Anypoint Code Builder now defaults to the US production environment when the ANYPOINT_ENV variable is set to an unrecognized value.

W-20003674

Exchange search now correctly returns the Inference connector when using Mule runtime 4.9.10 or later.

W-20054759

The correct message is now displayed when attribute and variable samples are empty in the configuration panel.

W-20057018

Error messages related to connector dependencies now include a clickable pom.xml link.

W-15813306
This release addresses the following issues with agent network projects:
Issue Resolution ID

Agent brokers now maintain conversation context during multi-turn interactions.

W-19825674

Agent brokers now return properly formatted text content in input-required responses instead of empty strings.

W-19880599
## [](#oct24-2025)October 24, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack. - Extension pack version: 1.11.6 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.11.5 This cloud IDE version runs the 1.11.6 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### Fixed Issues
Issue Resolution ID

Auto-approval for safe commands is now disabled in MuleSoft Dev Agent. Command execution now always requires explicit user approval, unless Execute all commands is enabled, preventing potential prompt injection exploits.

W-19853225

Editing VS Code configuration files (.vscode/ and *.code-workspace) now requires explicit approval.

W-19853255

Editing the MCP configuration file (a4d_mcp_settings.json) now requires explicit approval in MuleSoft Dev Agent.

W-19853247
## [](#oct14-2025)October 14, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack. - Extension pack version: 1.11.5 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### Fixed Issues
Issue Resolution ID

Core capabilities in the Design Service, including Test Connection and Run and Debug, function as expected on slow machines.

W-19864902

Data streaming issues are fixed now and responses from Model API no longer fail.

W-19845839
## [](#oct8-2025)October 8, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.11.4 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.11.4 This cloud IDE version runs the 1.11.4 extension pack. For extension versions, see the [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-10-08-25)What’s New This version contains internal bug fixes and performance improvements. ## [](#oct-2025)October 3, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.11.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.11.0 This cloud IDE version runs the 1.11.0 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Oct25)What’s New This release introduces these features: - [Agent Fabric](#agent-fabric) - [MuleSoft Dev Agent](#dev-agent) - [Batch Processing Support](#batch-process-support) - [Duplicate Flows in Canvas](#duplicate-flows) - [Copy and Paste Components in Canvas](#copy-paste-components) - [Stability and Usability enhancements](#stability-usability-enhancements) - [Mule Runtime Support](#mule-runtime-4-10-0-support) - [Einstein Features and Free Trial Orgs](#einstein-and-free-trials) - [More Agentic Integration Development with the Embedded MuleSoft Model Context Protocol (MCP) Server](#mcp-server) #### [](#agent-fabric)Agent Fabric Use Anypoint Code Builder to create, publish, and deploy agent networks as part of the Agent Fabric solution. Agent Fabric is a unified solution for governing and monitoring AI agents built anywhere, making it possible to build a collaborative digital workforce across any system or app. For more information, see [Building Agent Networks for Agent Fabric](https://docs.mulesoft.com/agent-network/latest/af-agent-networks). #### [](#dev-agent)MuleSoft Dev Agent The Agentforce panel in Anypoint Code Builder has been updated with MuleSoft Dev Agent. MuleSoft Dev Agent is an integrated assistant that enables developers to use natural language prompts to design, develop, and manage applications directly within Anypoint Code Builder. Dev Agent unifies all generative AI capabilities into a single experience: - Create and edit flows - Generate and refine API specifications - Configure connections and projects - Deploy applications Dev Agent can read and write directly to project files, and supports tools provided by embedded MCP servers. For more information, see: - [AI を使用した API 仕様の作成](https://docs.mulesoft.com/jp/anypoint-code-builder/api-ai-create-spec) - [Agentforce を使用したインテグレーションの開発](https://docs.mulesoft.com/jp/anypoint-code-builder/int-ai-developing-integrations) #### [](#batch-process-support)Batch Processing Support Create and configure batch jobs for processing large volumes of records asynchronously, in parallel, and in chunks to optimize performance and resource utilization. For more information, see [anypoint-code-builder::acb-component-batch.adoc](#anypoint-code-builder::acb-component-batch.adoc). #### [](#duplicate-flows)Duplicate Flows in Canvas Duplicate flows in the canvas to create copies of existing flows with their components and configurations. For more information, see [Duplicate a Flow](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components#duplicate-a-flow). #### [](#copy-paste-components)Copy and Paste Components in Canvas You can now copy components in your flow and paste them in the same or a different flow, while retaining their configuration. For more information, see [Copy Components](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components#copy-components). #### [](#stability-usability-enhancements)Stability and Usability enhancements ##### [](#object-store-in-global-configuration)Object Store in Global Configuration Streamline your development with an improved visual and guided experience for configuring object stores in any component and reduce the need for manual XML coding. ##### [](#special-characters-support)Special Characters Support You can now use special characters in flow names, password fields, connection configurations, and global elements. ##### [](#multiple-versions-of-a-connector-within-a-project)Multiple Versions of a Connector Within a Project You can now use multiple versions of a connector in your projects. ##### [](#multi-level-connection-configurations)Multi level Connection Configurations Easily manage and structure complex connection setups by layering connection configurations within each other directly from the UI. ##### [](#flow-error-handler-configuration)Flow Error Handler Configuration New configuration options for handling errors in your Mule project flow. ##### [](#go-to-flow-keyboard-shortcut)Go to Flow Keyboard Shortcut You can now quickly open a referenced flow by pressing Ctrl+Alt+g (Windows) or Cmd+Option+g (macOS) while the `Flow ref` component is selected. For more information, see [Navigate to Referenced Flows](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components#navigate-to-referenced-flows). ##### [](#notifications-with-project-context)Notifications with Project Context Notifications now provide specific context about which projects are causing errors within a workspace. ##### [](#design-service-connection-on-non-english-computers)Design Service Connection on Non-English Computers Users can now connect to the design service on a computer with a non-English language setting. ##### [](#initial-pom-xml-template-update)Initial pom.xml Template Update The initial **pom.xml** template is updated to use HTTPS for Maven XSD to enhance its security. ##### [](#projects-open-in-current-window)Projects Open in Current Window Projects created using the **Implement an API** option now open in the current window instead of a new one. ##### [](#map-and-transform-with-ai-improvements)Map and Transform with AI Improvements The **Map and Transform with AI** feature now shows specific messaging when there is an error. Input and output metadata is no longer required for this feature. ##### [](#variable-and-attribute-configuration-in-transformations)Variable and Attribute Configuration in Transformations You can now edit and configure variables and attributes within transformations from the UI. #### [](#mule-runtime-4-10-0-support)Mule Runtime Support Support for Mule runtime engine version 4.10.0 Edge with Java version 17. See [Compatibility](#compatibility). #### [](#einstein-and-free-trials)Einstein Features and Free Trial Orgs Einstein features are no longer be available on free trial Salesforce orgs. Users must link to their own Salesforce org to use these features. For more information, see [Anypoint Platform アカウントの管理](https://docs.mulesoft.com/jp/access-management/managing-your-account). #### [](#mcp-server)More Agentic Integration Development with the Embedded MuleSoft Model Context Protocol (MCP) Server Use natural language interaction to build Agent Fabric agent networks, manage governance rulesets, and more. Any agent can execute MuleSoft MCP Server tools. MCP provides extensibility for a wide array of agent types. For more information, see [MuleSoft MCP Server Release Notes](https://docs.mulesoft.com/mulesoft-mcp-server/mulesoft-mcp-server-release-notes). ### Fixed Issues
Issue Resolution ID

When setting up HTTP request headers, the IDE no longer incorrectly adds an empty array symbol #[] in the headers expression section of the flow XML code.

W-19152657

The inference connector no longer fails to retrieve and show dynamic data for the value provider field.

W-19084301

The IDE now correctly generates the default XML code snippets for nested fields, including arrays, objects, and unions.

W-19144806

In the Salesforce Connector, the parameters for the "Salesforce - Query" connector no longer disappear after clicking on it from the "Set variable" connector.

W-18836813

The Agent Conductor module now displays correctly.

W-19094498

The paths for certain container route types, such as scatter-gather and first successful, no longer overlap with each other.

W-19094528

The connection test for the Kafka connector is now working as expected.

W-12553536

The XML code is now generated in the correct order in the A2A Connector.

W-19105944

The MIME type parameters are shown as expected in the user interface.

W-18106124

DataWeave data and functions no longer return empty if adding a new project to an existing workspace.

W-18824864

The agent conductor data now loads properly in the user interface.

W-19154866

Setting breakpoints on flow control nodes is now working as expected.

W-18838355

The debugger tool no longer disappears unexpectedly.

W-19145809

The flow name updates as expected if you close the panel right after changing the flow name.

W-19147834

The error message java.lang.NoClassDefFoundError: org/mule.apikit.ApiParser no longer appears when the design service starts.

W-18195261

The output of a DataWeave mapping for non-transform components is no longer incorrect.

W-18566031

The startup error no longer occurs in specific customer project.

W-19337637

The output variable of a DataWeave mapping is now correct.

W-18566025

Dynamic control data is no longer overridden if you switch nodes.

W-19280291

Adding a Raise error component no longer breaks DataSense for the entire flow.

W-19404195

Validation issues in the XML file are fixed when using the batch component.

W-19136911

DataSense resolution errors no longer occur with certain components.

W-19367638

Sample data persistence calls for some nodes no longer fail.

W-19145325

Debug sessions are no longer killed on slower machines.

W-19183938

The Flow Ref component now correctly gets the flow list even if a flow is disabled.

W-19248177

Breakpoints set in one file are no longer incorrectly shown in another file’s canvas.

W-19302452

DataWeave expressions used within a variable of a Transform Message component are no longer lost.

W-19336241

Custom names for flows and error handlers are now correctly updated in the flow canvas.

W-19121648

The error state for connector routes is now displayed correctly.

W-19388454

The Export Shareable Jar command on Windows no longer includes unwanted folders.

W-19461974

NullPointerException no longer occurs if invoking 'getElementName().

W-18727157

The Go to Flow command now correctly finds a sub-flow in a second file.

W-19013755

The Map and Transform with AI feature is now working as expected.

W-19134821
## [](#sep-2025)September 3, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.10.2 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.10.2 This cloud IDE version runs the 1.10.2 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Sep25)What’s New - Support for Mule runtime engine version 4.9.9 LTS with Java version 17. See [Compatibility](#compatibility). ### Fixed Issues
Issue Resolution ID

The platform extension pack is updated to version 5.7.2 to fix a compatibility issue with Intel Mac machines.

W-19359467
## [](#aug-2025)August 19, 2025 Anypoint Code Builder releases this patch version in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.10.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.10.1 This cloud IDE version runs the 1.10.1 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ## [](#august-11-2025)August 11, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.10.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.10.0 This cloud IDE version runs the 1.10.0 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Aug25)What’s New This release introduces this feature: - Agentic Integration Development with the Embedded MuleSoft Model Context Protocol (MCP) Server With agentic integration development, build and manage your integration with natural language interaction, not code. Any agent can execute MuleSoft MCP Server tools to create, test, debug, and deploy Mule applications. MCP provides extensibility for a wide array of agent types. For more information, see [MuleSoft MCP Server Overview](https://docs.mulesoft.com/mulesoft-mcp-server/). ## [](#july-2025)July 21, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.9.2 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.9.2 This cloud IDE version runs the 1.9.2 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the Visual Studio Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Jul21)What’s New - Support for Mule runtime engine version 4.9.7 LTS with Java version 17. See [Compatibility](#compatibility). ## [](#july-4-2025)July 4, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.9.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.9.0 This cloud IDE version runs the 1.9.0 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the Visual Studio Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-jul-2025)What’s New This release introduces these features: - [Map Fields in DataWeave Expressions with AI](#dataweave-transform-map) - [Generate DataWeave Transformations with AI](#dataweave-transform-map-transform) - [Design API Specs with AI](#api-design) - [Use A2A Connector (Beta) with Anypoint Code Builder](#a2a-connector) - [Use MCP Connector 1.0 (Generally Available) with Anypoint Code Builder](#mcp-connector) - [Create MUnit Test from Flow](#munit-flow) - [Scope MUnit Tests to Specific Processors from UI](#munit-processor) - [Comment Out Components in Canvas](#comment-out-canvas) - [Navigate to Flows from Connectors](#navigate-to-flows) - [Review Scaffolding Errors in Output Panel](#scaffolding-errors) - [Open Projects in Canvas by Default](#canvas-default) - [Enter Properties as Values in Fields in UI](#properties-in-fields) - [Check Java and Mule Runtime Compatibility for All Connectors in Your Project](#connector-compatibility) - [Use Anypoint Code Builder with Windows 11](#windows-11) - [Agentforce Command Removed](#command-removed) - [Fixed Issues](#july-25-fixed-issues) #### [](#dataweave-transform-map)Map Fields in DataWeave Expressions with AI Automatically generate field-to-field mappings based on input and output metadata with the assistance of AI. For more information, see [Map with AI](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-dw-expressions#map-with-ai). #### [](#dataweave-transform-map-transform)Generate DataWeave Transformations with AI Generate full DataWeave transformations from input and output sample data with the assistance of AI. For more information, see [Map and Transform with AI](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-dw-expressions#map-and-transform-with-ai). #### [](#api-design)Design API Specs with AI Use Einstein generative AI to generate API specs from a conversation. For more information, see [Designing API Specs with AI](https://docs.mulesoft.com/jp/anypoint-code-builder/api-ai-design-spec). #### [](#a2a-connector)Use A2A Connector (Beta) with Anypoint Code Builder This release introduces support for Anypoint Connector for Agent2Agent (A2A Connector) (beta). A2A Connector (beta) facilitates inter-agent communication for Large Language Model (LLM) agents and other applications by implementing the A2A protocol. This enables agents to interact and delegate specialized tasks to other agents. See [組み込みコネクタ](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-connectors). _A2A Connector is a beta connector that is subject to the Beta Services Terms at [Agreements - Salesforce.com](https://www.salesforce.com/company/legal/agreements/) or a written Unified Pilot Agreement if executed by Customer, and the Non-GA Gen AI and Non-GA Credit Consumption terms in the [Product Terms Directory](https://ptd.salesforce.com/?_ga=2.247987783.1372150065.1709219475-629000709.1639001992). Use of this beta connector with external systems or services consumes Mule messages and is at the Customer’s sole discretion._ #### [](#mcp-connector)Use MCP Connector 1.0 (Generally Available) with Anypoint Code Builder This release introduces support for the generally available version of Anypoint Connector for MCP (MCP Connector). Previously, Anypoint Code Builder supported the beta version of MCP Connector. If you used the beta version of MCP Connector, remove `-Dmule.http.service.implementation=NETTY` from Runtime: Default Arguments in MuleSoft Settings. Also, the Design Service: System Properties setting is removed from MuleSoft Settings. MCP Connector helps you expose your Mule application as a tool that any AI client supporting Model Context Protocol (MCP) can use to perform real-world actions. See [組み込みコネクタ](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-connectors). #### [](#munit-flow)Create MUnit Test from Flow Create MUnit tests for your Mule project directly from the context menu of a flow. For more information, see [Create a Test from a Flow](https://docs.mulesoft.com/jp/anypoint-code-builder/int-test-munit#create-test-from-flow). #### [](#munit-processor)Scope MUnit Tests to Specific Processors from UI Select the processors and attributes in a Mule flow from the UI for testing to i​ncrease precision, identify issues faster, and create tests more efficiently. For more information, see [Targeting Specific Processors and Attributes in Your Test](https://docs.mulesoft.com/jp/anypoint-code-builder/int-test-munit#targeting-specific-processors-and-attributes-in-your-test). #### [](#comment-out-canvas)Comment Out Components in Canvas Comment out components directly in Anypoint Code Builder canvas. Disabled components can also be deleted in bulk for cleanup purposes. #### [](#navigate-to-flows)Navigate to Flows from Connectors You can now open the target flow referenced by a connector, using the **Go to Flow** option in the context menu for application flows and MUnit test flows to trace and manage application logic across modular flows. #### [](#scaffolding-errors)Review Scaffolding Errors in Output Panel Now it’s even easier to troubleshoot errors when creating a project. In the Output panel, there’s a new **MuleDX Server - Scaffolding** option. Select that option to show the MuleDX Server log content that’s related to scaffolding only. ![Output panel with Mule DX Server: Scaffolding selected](/mulesoft/current/ja-jp/release-notes/_images/code-builder/scaffolding.png) For more information, see [出力パネルを開く](https://docs.mulesoft.com/jp/anypoint-code-builder/start-open-output-panel). #### [](#canvas-default)Open Projects in Canvas by Default Anypoint Code Builder now opens projects in the canvas by default. You can save and debug your applications directly from the UI without switching views, streamlining your low-code experience. #### [](#properties-in-fields)Enter Properties as Values in Fields in UI Property mode `{}` now makes it possible to enter properties in number and boolean fields in the UI. Previously, it was possible only in the code editor. ![Create parent directories field with Property mode enabled](/mulesoft/current/ja-jp/release-notes/_images/code-builder/bracket.png) #### [](#connector-compatibility)Check Java and Mule Runtime Compatibility for All Connectors in Your Project Verify that your local and Anypoint Exchange connectors are compatible with your Java and Mule runtime version for your projects. Project Properties now tells you about incompatible versions and lets you fix them right away, accelerating development and reducing blockers, especially when importing projects. Previously, Project Properties verified compatibility of Anypoint Exchange connectors only. For more information, see [Mule、Java、コネクタのバージョン設定](https://docs.mulesoft.com/jp/anypoint-code-builder/int-versions). #### [](#windows-11)Use Anypoint Code Builder with Windows 11 Anypoint Code Builder Desktop IDE now supports Windows 11. For more information, see [Compatibility](#compatibility). #### [](#command-removed)Agentforce Command Removed The **MuleSoft: Open Agentforce** command is removed from the Command Palette. You can use the toolbar button to access the Agentforce panel when available. ### Fixed Issues
Issue Resolution ID

When you define a DataWeave multiline expression, code highlighting now works as expected.

W-11492623
## [](#may-2025)May 27, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.8.2 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.8.3 This cloud IDE version runs the 1.8.2 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-May25)What’s New - Authentication support for Cursor, Trae, and Windsurf. - Support for Mule runtime engine version 4.9.4 LTS with Java version 17. See [Compatibility](#compatibility). ## [](#apr-2025)April 29, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.8.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.8.3 This cloud IDE version runs the 1.8.1 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Apr25)What’s New This release introduces support for Anypoint Connector for MCP (MCP Connector) (beta). MCP Connector (beta) helps you expose your Mule application as a tool that any AI client supporting Model Context Protocol (MCP) can use to perform real-world actions. For example, your MCP client can trigger a process, look up data, or transform records. See [組み込みコネクタ](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-connectors). _MCP Connector is a beta connector that is subject to the Beta Services Terms at [Agreements - Salesforce.com](https://www.salesforce.com/company/legal/agreements/) or a written Unified Pilot Agreement if executed by Customer, and the Non-GA Gen AI and Non-GA Credit Consumption terms in the [Product Terms Directory](https://ptd.salesforce.com/?_ga=2.247987783.1372150065.1709219475-629000709.1639001992). Use of this beta connector with external systems or services consumes Mule messages and is at the Customer’s sole discretion._ ## [](#mar-2025)March 21, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.8.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.8.0 This cloud IDE version runs the 1.8.0 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Mar25)What’s New This release introduces these features: - New DataWeave Transformation Builder Tool. Transform your message payload, attributes, and variables to the required output format and data structure with DataWeave Transformation Builder. See [Open Transformation Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-dw-expressions#open-transformation-builder). - Refine your flows through natural language interactions. Anypoint Code Builder dynamically updates your flow code based on your latest instructions, ensuring an easy and efficient workflow. Plus, access your chat history to track changes. - Validate and publish your API project to Anypoint Exchange through a new intuitive user interface. See [Exchange への API プロジェクトのパブリッシュ](https://docs.mulesoft.com/jp/anypoint-code-builder/des-publish-api-spec-to-exchange). - Build Agentforce integrations using Agentforce Connector 1.0.1 and Einstein AI Connector 1.1.1. See [組み込みコネクタ](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-connectors). - Agentforce for Anypoint Code Builder Generative Flows is now available on these Anypoint Platform control plane regions : [Canada Cloud](https://ca1.platform.mulesoft.com) and [Japan Cloud](https://jp1.platform.mulesoft.com). - New documentation to help you migrate your Anypoint Studio Mule projects to Anypoint Code Builder. Learn how to import your Mule projects into Anypoint Code Builder to unlock a modern development experience with faster startup times, streamlined collaboration, and the integration of MuleSoft for Agentforce: Topic Center to enable API projects for topics and agents. See [Migrate Your Mule Project from Anypoint Studio to Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/int-migrate-studio-to-acb). - The Einstein generative flow feature is now called the Agentforce generative flow feature. ### Fixed Issues
Issue Resolution ID

DataSense now works as expected when a tag spans multiple lines.

W-12482310

DataSense now works as expected when you create a project with Mule runtime version 4.4 and no other runtime versions are downloaded.

W-16117373
## [](#feb-2025)February 6, 2025 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE. - Extension pack version: 1.7.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.7.1 This cloud IDE version runs the 1.7.0 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-Feb25)What’s New This release introduces these features: - Support for [MuleSoft for Agentforce: Topic Center](https://docs.mulesoft.com/jp/anypoint-code-builder/ai-enabling-api-project-topic-center). - Use the visual editor when you design an API to enable your API specifications for topics and agents. - Make your topic and action-enabled APIs available in Salesforce using Salesforce API Catalog. - Augment agent functionality by assigning topics to Agentforce agents in Agent Builder. - Use the provided governance rules to validate that your API is ready to generate agent actions and topics in Salesforce. - Run MUnit tests from the canvas. See [Testing Projects with MUnit](https://docs.mulesoft.com/jp/anypoint-code-builder/int-test-munit#run-tests-from-the-canvas). - Configure proxy settings. See [Using a Proxy in Anypoint Code Builder](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-proxy-settings). - Streamline productivity with performance enhancements for DataSense, flow canvas rendering, and connector configuration testing. - Support for Mule runtime engine version 4.9 LTS with Java version 17. See [Compatibility](#compatibility). ### Fixed Issues
Issue Resolution ID

A notification now appears after you change the region in the settings.json file.

W-13184670

XML formatting is no longer corrupted when you add or update a connection configuration, or when you use the Format Document menu option.

W-16850099

Avro suggestions now appear when you define an Avro schema and declare a record inside a record property.

W-16814386

Correct suggestions now display for inline Avro schema payloads. The issue occurred inside maps that contained arrays.

W-16809972

Correct suggestions now display for values in fields of type map.

W-16814887

Syntax errors in DataWeave expressions in projects imported from Studio no longer occur. Anypoint Code Builder now automatically fetches the required dependencies when the project loads.

W-14037343

When you use a proxy, the Mule runtime options now appear in the UI form for creating a new integration project. You can click Create Project to create the project.

None
## [](#dec-2024)December 9, 2024 Anypoint Code Builder releases a new feature in the Anypoint Extension Pack. - Extension pack version: 1.6.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-dec24)What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) Exceptions: - Einstein for Anypoint Code Builder Generative Flows is available only on US and EU cloud hosts. Canada and Japan cloud hosts are currently not supported. - Cloud IDE is available only on US and EU cloud hosts. Canada and Japan cloud hosts are currently not supported. - “Design Center” UI labels are renamed to “MuleSoft VCS”. ### Fixed Issues
Issue Resolution ID

Anypoint Connector for Zoom (Zoom Connector) component configuration view now correctly displays relevant options.

W-17148078

Adding a transform connector no longer incorrectly inserts #[] in script fields.

Previous: <![CDATA[#["test"]]]>

New: <![CDATA["test"]]>

W-17199037
## [](#nov-2024)November 4, 2024 Anypoint Code Builder releases a new feature in the Anypoint Extension Pack and the cloud IDE. - Extension pack version: 1.5.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.5.0 This cloud IDE version runs the 1.5.0 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-nov24)What’s New The release introduces the following feature: - The Einstein for Anypoint Code Builder Generative Flows feature is now enabled and managed in Anypoint Platform Access Management. For more information, see [Enabling Einstein for Anypoint Platform](#access-management::enabling-einstein.adoc). ### Fixed Issues
Issue Resolution ID

JMS Connector connections can now be validated with the Test Connection button.

W-16983063
## [](#oct-2024)October 8, 2024 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE. - Extension pack version: 1.4.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.4.6 This cloud IDE version runs the 1.4.1 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-oct24)What’s New This release introduces these features: - [Advanced Data Types](#data-types-advanced) - [Connection Configurations from the UI](#connection-configurations) - [Code Coverage Reports](#code-coverage-munit) - [Deploy to CloudHub 2.0](#cloudhub-2-deployments) - [Publish Mule Projects to Anypoint Exchange](#app-publish-exchange) - [AsyncAPI Specification Design and Governance](#asyncapi-design) - [AsyncAPI Support for Avro Schema Fragments](#asyncapi-avro) - [AsyncAPI Implementation Support for Solace PubSub+ and Salesforce Platform Events Connectors](#solace-platform-support) - [Support for Mule Version 4.8](#runtime-version-support) - [Enhanced API Auto-Completion](#api-autocompletion) - [API Autodiscovery](#api-autodiscovery) - [Enhanced Debugging](#visual-debugger) - [Custom Connector Support](#custom-connector-support) #### [](#data-types-advanced)Advanced Data Types The connection configuration panel in the canvas UI adds support for configuring connections, objects, arrays of non-primitive types, and multi-level dynamic lists. In the previous release, the configuration panel supported unions, arrays of primitive types, file selectors, and password fields. For more information, see [Adding a Component to Your Project](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components-add). #### [](#connection-configurations)Connection Configurations from the UI Connection configurations are global configurations that more than one component in a project can use. Anypoint Code Builder improves workflow by enabling you to check for components that use the connection through the UI. For more information, see [Adding a Component to Your Project](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-components-add). #### [](#code-coverage-munit)Code Coverage Reports Anypoint Code Builder adds code coverage reports for testing integration and implementation projects with MUnit. For more information, see [Running MUnit Tests with Coverage](https://docs.mulesoft.com/jp/anypoint-code-builder/int-test-munit#run-coverage). Additionally, you can now run MUnit tests in Anypoint Code Builder without setting your credentials in Maven. #### [](#cloudhub-2-deployments)Deploy to CloudHub 2.0 In addition to supporting deployments of your integrations to CloudHub, Anypoint Code Builder adds support for deployments to CloudHub 2.0. For more information, see [Mule アプリケーションの CloudHub および CloudHub 2.0 へのデプロイ](https://docs.mulesoft.com/jp/anypoint-code-builder/int-deploy-mule-apps). #### [](#app-publish-exchange)Publish Mule Projects to Anypoint Exchange Anypoint Code Builder adds functionality for publishing project templates and project examples to Anypoint Exchange. Publishing to Exchange enables your team to reuse your applications. For more information, see [Publishing a Mule Project to Exchange](https://docs.mulesoft.com/jp/anypoint-code-builder/int-export-mule-project#publishable). #### [](#asyncapi-design)AsyncAPI Specification Design and Governance Anypoint Code Builder now supports creating, designing, and governing AsyncAPI 2.6 specifications. For more information, see: - [Creating and Importing AsyncAPI API Specifications](https://docs.mulesoft.com/jp/anypoint-code-builder/des-create-asyncapi-api-specs) - [Validating API Specifications Against Governance Rulesets](https://docs.mulesoft.com/jp/anypoint-code-builder/des-govern-api) #### [](#asyncapi-avro)AsyncAPI Support for Avro Schema Fragments Anypoint Code Builder adds support for creating and designing Apache Avro schema fragments. Ensure data consistency and interoperability in distributed systems by defining Avro schemas with structured data, including data types and fields. For more information, see [Creating and Using API Spec Fragments](https://docs.mulesoft.com/jp/anypoint-code-builder/des-create-api-fragments) #### [](#solace-platform-support)AsyncAPI Implementation Support for Solace PubSub+ and Salesforce Platform Events Connectors Anypoint Code Builder adds support for Solace PubSub+ and Salesforce platform events connectors. Expand your integration capabilities and streamline event-driven architectures. For more information, see [Supported Message Brokers](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-module-reference#supported-message-brokers). Implementing AsyncAPI specifications using DataSense for Avro schemas requires Mule 4.8 or later. #### [](#runtime-version-support)Support for Mule Version 4.8 Anypoint Code Builder adds support for Mule version 4.8 with Java versions 11 and 17. For more information, see [Mule and Java version support](#versions-mule-jdk). #### [](#api-autocompletion)Enhanced API Auto-Completion Anypoint Code Builder introduces enhanced API auto-completion. Instead of typing Ctrl+Space to activate the auto-completion menu in your API spec, you can place your cursor at the location in your API spec file where you require suggestions. If the line has some content, press Tab, press Space, or start typing after the content on the line to launch the menu. To close the auto-completion menu, press Escape. - [Mule > Editor > Auto-completion: Enablement](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-mule-settings#setting-auto-complete) This setting is disabled by default. - [Mule > Editor > Auto-completion: Trigger Delay](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-mule-settings#setting-auto-complete) For more information on using auto-complete, see [Use Auto-Complete in the Editors](https://docs.mulesoft.com/jp/anypoint-code-builder/start-discover-ui#use-autocomplete). #### [](#api-autodiscovery)API Autodiscovery Anypoint Code Builder supports configuring Mule apps for tracking requests with Autodiscovery. Configure a Mule app to send request data to an API running on a Mule Gateway runtime in API Manager. The API tracks this data in charts in API Manager. For more information, see [Tracking Requests with Autodiscovery](https://docs.mulesoft.com/jp/anypoint-code-builder/int-autodiscovery-config). #### [](#visual-debugger)Enhanced Debugging Anypoint Code Builder adds breakpoint indicators in the canvas UI for components that have one or more breakpoints in the configuration XML. Indicators also display when stepping through a flow while debugging. Additionally, you can add and remove breakpoints on components in the canvas UI. For more information, see [Debugging Mule Applications](https://docs.mulesoft.com/jp/anypoint-code-builder/int-debug-mule-apps). #### [](#custom-connector-support)Custom Connector Support Anypoint Code Builder now supports custom connectors that are locally bundled or published to Exchange. For locally bundled connectors, add the dependency to your integration project by referencing the Maven dependency in your `pom.xml` file. For connectors published to Exchange, add the component from the **Add Component** panel using the **Search in Exchange** toggle. ### Fixed Issues
Issue Resolution ID

The Governance Rulesets and Governance Results panels now update as expected when more than one project folder is open in a VS Code workspace.

W-15677742

After iteratively scaffolding an API spec into an implementation project, the Data and Functions tabs in the expression builder no longer display the "loading" animation.

W-15828343
## [](#aug-2024)August 17, 2024 Anypoint Code Builder releases a new feature in the Anypoint Extension Pack and the cloud IDE. - Extension pack version: 1.3.0 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.3.0 This cloud IDE version runs the 1.3.0 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ### [](#features-august-2024)What’s New The release introduces the following feature: - You can now use the Einstein for Anypoint Code Builder Generative Flows feature to jumpstart your integration development by generating flows for you. For more information about this feature, see [Agentforce を使用したインテグレーションの開発](https://docs.mulesoft.com/jp/anypoint-code-builder/int-ai-developing-integrations). ### Fixed Issues
Issue Resolution ID

The Governance Rulesets and Governance Results now update as expected when more than one folder is open in a VS Code workspace.

W-15677742

The Preview tab in the expression builder UI no longer produces an Internal Error message when you configure an attribute of a component’s child element in the XML editor and that attribute accepts DataWeave expressions. This issue affected all components with child attributes that accept expressions. The following example displays a child element with an attribute that contains a DataWeave expression:

Attribute with an expression in nested element of a component

W-15906886
## [](#jul-2024)July 2, 2024 This patch release addresses Anypoint Code Builder issues. ### Fixed Issues
Issue Resolution ID

You no longer have to update the runtime version when deploying a Mule application with Mule runtime version 4.6 or 4.7. This issue occurred when deploying to CloudHub from the IDE.

W-15902597

A tooling client error no longer appears after creating a Java class, adding a New operation from the Java Module to a flow, selecting the class, and then refreshing Constructor.

W-15877062

The XML now reflects changes after configuring the Send operation of Anypoint Connector for Email (Email Connector) from the component configuration panel.

W-15906937

After changing the class setting in the Class field, you no longer have to refresh the Method field before selecting from the list of methods in the class. This issue occurred when updating the Invoke, Invoke Static, or New operations from the Java Module in the configuration panel.

W-15111695

To import DataWeave libraries when using functions outside of the Core library, you no longer have to use the Quick Fix option. The DataWeave libraries are now imported automatically.

W-15673127

The feedback button for the open beta of AsyncAPI support to implement event-driven architecture now consistently appears in the canvas.

W-16084084
Patching the desktop IDE extensions requires a manual update or installation of the Anypoint Extension Pack. The cloud IDE is updated automatically. - Extension pack version: 1.2.2 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.2.4 This cloud IDE version runs the 1.2.2 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ## [](#jun-24-2024)June 24, 2024 AsyncAPI Beta: AsyncAPI 2.6 and 2.0 implementation features are now available for use in Anypoint Code Builder. The minimum Mule runtime engine requirement for this feature is Mule 4.6. Before you can use these features, your Anypoint Platform organization administrator must accept the Beta terms and conditions from the Anypoint Code Builder landing page in Anypoint Platform. For guidance, see [AsyncAPI 仕様の実装](https://docs.mulesoft.com/jp/anypoint-code-builder/imp-asyncapi). Anypoint Extension Pack has not changed since the [June 4, 2024 release](#jun-2024). If you installed or upgraded your extensions on the desktop IDE in that release, no installation or upgrade is required. The cloud IDE was updated automatically in that release. To learn about the AsyncAPI journey, see [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ## [](#jun-2024)June 4, 2024 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE. - Extension pack version: 1.2.1 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.2.1 This cloud IDE version runs the 1.2.1 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. ### [](#features-jun24)What’s New The release introduces the following features: - [DataWeave Expression Builder](#dw-expression-builder) - [Component Configuration Enhancements](#component-config-ui) - [Support for Multiple Mule Runtime Versions with Java 17 or 11](#multiruntime) - [Custom Java Classes and Code](#java-custom) - [Maven Settings](#maven) - [MUnit Support](#munit) - [API Governance for REST APIs](#governance) For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). #### [](#dw-expression-builder)DataWeave Expression Builder Use the DataWeave expression builder when configuring your integrations and implementations from the UI. DataWeave is a programming language designed for transforming data. Most components in Mule application flows use DataWeave expressions to select and transform messages (payload and attributes) or Mule variables. The DataWeave expression builder helps you configure fields of components that accept expressions (**fx** fields). For each expression field, the feature provides an extra panel with the following tabs: - **Data** for selecting a value (payload, attributes, or a Mule variables) - **Functions** for selecting DataWeave functions to use in your expressions Function documentation is available from this tab by mousing over a function and getting details, including parameter descriptions and examples. - **Preview** for running the expression on sample data In addition, you can use autocomplete from an expression (**fx**) field for a component to select DataWeave functions from the Core module and other values accepted in this field. For details, see [Anypoint Code Builder での DataWeave 式と変換の使用](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-dw-expressions). For more information about DataWeave and the Mule event structure, see [DataWeave Overview](https://docs.mulesoft.com/dataweave/latest/) and [Mule Event Structure](https://docs.mulesoft.com/mule-runtime/latest/about-mule-event). #### [](#component-config-ui)Component Configuration Enhancements Configure more of your integrations and implementations from the canvas UI. The configuration panel for components adds: - An **Input/Output** tab to existing tabs (**General**, **Advanced**, and **Notes**) for Mule event metadata from the payload, attributes, Mule variables - Support for additional data types in the configuration fields: - File selectors - Passwords - Array (primitive types only) - Union for some configurable data sets For examples, see [Anypoint Code Builder での DataWeave 式と変換の使用](https://docs.mulesoft.com/jp/anypoint-code-builder/int-configure-dw-expressions). #### [](#multiruntime)Support for Multiple Mule Runtime Versions with Java 17 or 11 Anypoint Code Builder now supports Mule runtime versions 4.4, 4.6, and 4.7 and compatible Java versions (Java 11 or Java 17) to run Mule apps for your implementation and integration projects (see [supported Mule and Java versions](#versions-mule-jdk)). In addition, when you create an integration project from a template or example project in Anypoint Exchange, the asset search displays assets set to use Mule 4.4 or higher, instead of 4.4 only. Select the versions to run when creating or importing Mule applications in Anypoint Code Builder and when scaffolding an API specification into an implementation project. The following settings are new in this release: - **Mule > Application: Default Mule Runtime And Java Versions**: Sets default Mule and Java versions for all projects. - **Project Properties** tabs for setting and changing Mule runtime, Java, and connector versions in an implementation or integration project. This feature is useful for updating to the latest minor version or when importing projects that use unsupported versions. - **Mule: Home Directory**: Set the home directory for Mule runtime and Java downloads. This setting replaces the runtime settings **Mule > Runtime: Mule Home** and **Mule > Runtime: Mule Runtimes Directory**, which are no longer present in the **Settings** tab. In addition, the IDE no longer uses the directory `${user.home}/muleRuntimes/` to store Mule runtime versions. Anypoint Code Builder - Mule Runtime Extension (`salesforce.mule-dx-mule-runtime`) is removed from Anypoint Extension Pack in this release. Instead of supplying a bundled runtime, the IDE provides an interface for downloading and installing runtime versions to use in your projects. To remove the runtime extension from VS Code, open the **Extensions** panel, click **Anypoint Code Builder - Mule Runtime Extension**, and select **Uninstall**. See [Mule、Java、コネクタのバージョン設定](https://docs.mulesoft.com/jp/anypoint-code-builder/int-versions) for project and default version settings. #### [](#java-custom)Custom Java Classes and Code The Java module is now bundled into Anypoint Code Builder. When you create a new Java class in a project, Anypoint Code Builder automatically adds the necessary dependencies to the project’s `pom.xml` and the namespace and schema locations to the configuration XML for the project. New integration and implementation projects now add the directories `src/main/java` and `/src/test/java` for your custom Java work. For documentation, see [Anypoint Code Builder を使用した Java Module の設定](https://docs.mulesoft.com/jp/java-module/latest/configure-java-module-acb). To use auto-complete from the application XML to find module configuration options and to display lists of available Java classes and methods in a selected class, install [Extension Pack for Java](https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack) from Microsoft to the IDE. #### [](#maven)Maven Settings To avoid changing any of your preferred Maven settings in `settings.xml`, Anypoint Code Builder now creates a separate settings file, `acb_settings.xml`. The setting **Mule: Home Directory**, in the **Settings** tab, configures the location of this file. By default, the full path to the file is `{user.home}/AnypointCodeBuilder/maven/acb_settings.xml`. For details, see [Anypoint Code Builder の Maven 設定ファイル](https://docs.mulesoft.com/jp/anypoint-code-builder/ref-acb-maven). #### [](#munit)MUnit Support Anypoint Code Builder introduces limited support for testing with MUnit. Run, modify, and create MUnit tests for your implementation and integration projects in Anypoint Code Builder. Import projects that contain MUnit test files. Test configuration is supported through the XML editor only at this time. For more information, see [MUnit を使用したプロジェクトのテスト](https://docs.mulesoft.com/jp/anypoint-code-builder/int-test-munit). Some MUnit features supported by Anypoint Studio are not supported by Anypoint Code Builder in this release. #### [](#governance)API Governance for REST APIs Anypoint Code Builder now supports API Governance for REST APIs: - Check conformance status of a project. - Add rulesets to your project. You can also remove rulesets, change ruleset versions, and review ruleset configurations. - Run and re-run validations against your API specifications. For supported specifications, see [Compatibility](#compatibility). - Monitor the progress of a validation. - Fix conformance issues. See [ガバナンスルールセットに対する API 仕様の検証](https://docs.mulesoft.com/jp/anypoint-code-builder/des-govern-api). ## [](#apr-2024)April 19, 2024 Anypoint Code Builder updates the built-in Mule runtime engine to patch version `4.4.0-20240408`. The Mule version is updated automatically in the cloud IDE but requires a manual update or installation of the Anypoint Extension Pack in the desktop IDE. - Extension pack version: 1.0.8 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.1.4 This cloud IDE version runs the 1.0.8 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ## [](#feb-2024)February 14, 2024 Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE. - Extension pack version: 1.0.7 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.1.3 This cloud IDE version runs the 1.0.7 extension pack. For extension versions, see [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog) in the VS Code Marketplace. ### [](#features-feb24)What’s New The release introduces the following features: - [Component Configuration Panel in the UI](#component-ui) - [Integration Project Creation from Templates and Examples](#project-import) - [API Design Project Improvements](#api-design-change) - [Configuration XML File Creation Enhancement](#config-xml-creation) #### [](#component-ui)Component Configuration Panel in the UI Anypoint Code Builder introduces a configuration panel in the UI for components, such as connector operations, within integration and implementation projects. This feature simplifies component configuration. The component configuration panel provides configuration options that are also available through the configuration XML files for your projects. Some components and fields continue to require configuration through the XML in this release. Continue to use XML for complex fields, identified as read-only fields in the UI, and for global configurations, such as connection configurations. You can open the configuration panel from the canvas or from a configuration XML file within your project. See [Add a Component to Your Project](https://docs.mulesoft.com/jp/anypoint-code-builder/int-create-integrations#add-components) and [Open a Component in the Canvas from the XML Editors](https://docs.mulesoft.com/jp/anypoint-code-builder/int-create-integrations#open-component-from-xml). #### [](#project-import)Integration Project Creation from Templates and Examples Anypoint Code Builder adds the ability to import a template or example from Anypoint Exchange into an integration project within Anypoint Code Builder. After importing, you can continue to develop your integration. For information about templates and examples in Exchange, see [アセットタイプ](https://docs.mulesoft.com/jp/exchange/asset-types). For guidance with importing from Exchange, click the tab **Start with a Project Template or Example** in the procedure [Create an Integration Project](https://docs.mulesoft.com/jp/anypoint-code-builder/int-create-integrations#anchor-for-rns). #### [](#api-design-change)API Design Project Improvements This release introduces improvements and simplifications to the design process: - Import API design projects from Design Center into Anypoint Code Builder. For details, see [Import an API Specification from Design Center](https://docs.mulesoft.com/jp/anypoint-code-builder/des-create-api-specs#import-spec). - Publish your API specifications and fragments to Anypoint Exchange without first syncing your code changes with the Anypoint source control management (SCM) system. Creating an API design project from scratch in Anypoint Code Builder no longer spawns a corresponding design project in Design Center or creates a connection to the Anypoint SCM. For details, see [Source Control for API Design Projects](https://docs.mulesoft.com/jp/anypoint-code-builder/des-designing-api-specs#anypoint-scm). - Set a business group for your API design project when you publish to Exchange instead of when you create the design project. For example, see the steps in [Publish an API Spec to Exchange](https://docs.mulesoft.com/jp/anypoint-code-builder/des-publish-api-spec-to-exchange#publish-spec). #### [](#config-xml-creation)Configuration XML File Creation Enhancement Anypoint Code Builder enables you to create one or more additional configuration XML files from within your integration or implementation projects. This feature is useful for adding an implementation for an interface. The feature also enables you to split complex project code into more manageable pieces. For more information, see [Create an Additional Configuration XML File](https://docs.mulesoft.com/jp/anypoint-code-builder/int-create-integrations#create-new-config). For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ## [](#dec-2023)December 6, 2023 Anypoint Code Builder releases a patch to Anypoint Extension Pack and the cloud IDE. - Extension pack version: 1.0.6 To use this extension pack in the desktop IDE, see [Set up the Desktop IDE](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb#set-up-desktop). - Cloud IDE version: 1.0.3 This cloud IDE version runs on the 1.0.6 extension pack. The patch addresses the following issues:
Description Issue

When you open the IDE, the exception dw-lang-server-language-0" java.lang.NoClassDefFoundError: org/jboss/shrinkwrap/resolver/api/maven/Maven in the Mule DX Server logs no longer occurs because of an open workspace that contains a non-Mule project, such as an API spec project or other folders or files.

W-14268344

The issue java.io.FileNotFoundException no longer occurs due to attempted parsing of files that do not exist.

W-14254505

After scaffolding an API spec into an interface within an implementation project, the IDE no longer produces the syntax validation issue Configuration type reference is not compatible (INVALID_CONFIG_REFERENCE) within the configuration XML for config-ref attribute-value pairs. Previously affected components include <http:listener/>, <apikit:router/>, and <apikit:console/>.

W-14243529

A test connection no longer fails with the error 'Invalid Connection ElementDeclaration is declaring an extension: 'HTTP' that is not part of the session: '[]' after you copy and paste an HTTP Listener configuration (<http:listener-config/>) into a new project.

W-14252415
For more information, see [Known Issues](#known-issues) and [Compatibility](#compatibility). ## [](#oct-19-2023)October 19, 2023 Anypoint Code Builder releases a patch to the cloud IDE: - 1.0.2 (Cloud IDE): The cloud IDE removes the proxy for security purposes. URLs that trigger flows in the cloud IDE through the proxy no longer work. To trigger locally hosted flows that use an HTTP listener, see [開発環境でのフローのトリガー](https://docs.mulesoft.com/jp/anypoint-code-builder/int-trigger-flows). There are no changes to the desktop IDE, which remains version 1.0.5. ## [](#oct-16-2023)October 16, 2023 Anypoint Code Builder releases these versions: - 1.0.5 (Desktop IDE): Anypoint Code Builder for Desktop (desktop IDE) is generally available (GA) in this release. - 1.0.1 (Cloud IDE): The cloud IDE for Anypoint Code Builder remains in open beta:
Any use of an Anypoint Code Builder IDE in its beta state is subject to the applicable beta services terms and conditions, available from the cloud IDE.
The desktop IDE version 1.0.5 and cloud IDE version 1.0.1 both run on the same versions of the Anypoint Code Builder extensions, described in [Change Log](https://marketplace.visualstudio.com/items/salesforce.mule-dx-extension-pack/changelog), and provide the same features. To set up and gain access to the IDEs, see [Anypoint Code Builder 入門](https://docs.mulesoft.com/jp/anypoint-code-builder/start-acb). ### [](#whats-new-2)What’s New This release introduces: - Anypoint Extension Pack version 1.0.5 for the desktop IDE on [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=salesforce.mule-dx-extension-pack) - API fragment support for JSON Schema See [Supported Specification Languages for API Fragments](https://docs.mulesoft.com/jp/anypoint-code-builder/des-designing-api-specs#supported-fragment-languages). ## [](#open-beta)Open Beta Prior to the Oct 16, 2023 release, MuleSoft released these open beta versions of Anypoint Code Builder: - [September 2023 (Open Beta)](#sept-2023) - [August 2023 (Open Beta)](#aug-2023) - [June 2023 (Open Beta)](#june-2023) - [April 24, 2023 (Open Beta)](#april-24-2023) - [April 2023 (Open Beta)](#april-2023) ### [](#sept-2023)September 2023 (Open Beta) This update to the open beta introduces Anypoint Code Builder for Desktop on Windows and new features for desktop and cloud IDEs. - Windows support on the desktop IDE. See [Compatibility](#compatibility). - Hot deployments are supported for debugging Mule applications. See [Hot Deploy When Debugging](#anypoint-code-builder::debug-a-mule-application.adoc#hot-deploy). - New export commands for packaging Mule applications within shareable and deployable JAR files. See [anypoint-code-builder::package-mule-application.adoc](#anypoint-code-builder::package-mule-application.adoc). ### [](#aug-2023)August 2023 (Open Beta) This update to the open beta introduces Anypoint Code Builder for Desktop on MacOS and a new feature for desktop and cloud IDEs. - Anypoint Extension Pack on [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=salesforce.mule-dx-extension-pack) to support API specification design (OAS 3 and RAML), API implementation, and integration development Install the _pre-release\_version. Attempting to install the \_release_ version produces an error. - Support for the Mac operating system running on Intel or ARM processors (see [Compatibility](#compatibility)) - Desktop and cloud IDE support for the following features: - Secure configuration properties in your integrations and API implementations (see [Mule アプリケーションのプロパティの定義および保護](https://docs.mulesoft.com/jp/anypoint-code-builder/int-create-secure-configs)) - Improvements to avoid reloading the IDE when unpacking the runtime for the first time ### [](#june-2023)June 2023 (Open Beta) The update to the open beta for the web-based IDE introduces these features and improvements: - Support for EU Cloud: EU Cloud users of Anypoint Platform can now use Anypoint Code Builder from their management plane. See [anypoint-code-builder::connect-eu-cloud.adoc](#anypoint-code-builder::connect-eu-cloud.adoc) for more information. - Synchronization between a local API specification and Mule project: You can now work on your API specification and its Mule project implementation simultaneously. Anypoint Code Builder enables you to scaffold your API specification into a Mule project without publishing it to Exchange. You can work on your Mule project, then edit the API specification, and re-scaffold it to reflect your new changes. Both API design and API implementation tasks are now synchronized. You can then publish your API specification and deploy your Mule project from there. See [anypoint-code-builder::local-api-specification-tutorial.adoc](#anypoint-code-builder::local-api-specification-tutorial.adoc) for more information. - Updated UI canvas and code snippet support: - Directly import connectors from the canvas instead of using the dedicated command. - Use code snippets. See [anypoint-code-builder::work-with-code-snippets.adoc](#anypoint-code-builder::work-with-code-snippets.adoc) for more information. ### [](#april-24-2023)April 24, 2023 (Open Beta) The update to the open beta for the cloud IDE introduces a number of features and improvements: - Anypoint Code Builder migrated to a new underlying architecture. - The URL for your cloud IDE instance changed. You can get the new URL by launching the cloud IDE from the central page or checking the IDE details. - Your session cookie changed, so you must update it when [pinging a locally deployed application](#anypoint-code-builder::ping-locally-deployed-app.adoc) from a REST client. ### [](#april-2023)April 2023 (Open Beta) The update to the open beta for the cloud IDE introduces these features and improvements: - Business group support enables you to control access to resources when working with assets from Anypoint Exchange. - Search filters enable you to refine your search results when looking for an API asset from Anypoint Exchange. See [検索結果の絞り込み](https://docs.mulesoft.com/jp/anypoint-code-builder/imp-filter-search-results) for more information. - The canvas UI enables you to add components to flows in your integration. ## Compatibility
Application/Service Version

Anypoint Platform

US Cloud, EU Cloud, and these Anypoint Platform control plane regions: Australia Cloud, Canada Cloud, Japan Cloud, and United Kingdom Cloud. Anypoint Code Builder also connects to Anypoint Platform Private Cloud Edition (PCE). (Not supported by MuleSoft Government Cloud)

API Governance

Validations for REST API and AsyncAPI specs

CloudHub

1.0 and 2.0 (for deployments to the Sandbox environment)

DataWeave

Bundled with Mule runtime engine (built-in)

Java

Multiple versions supported. See supported Mule and Java versions.

Maven

3.9.4 (built-in)

Mule runtime engine

Multiple versions supported. See supported Mule and Java versions.

Operating system

Windows 11, Windows 10, macOS Intel and ARM (M1 or M2)

Visual Studio Code

Minimum version: 1.99.3
Tested versions:

  • 1.99.3 or later (macOS)

  • 1.99.3 or later (Windows)

Web browser

Anypoint Platform のブラウザーサポート
In Anypoint Code Builder, Mule applications for your implementation and integration projects are compatible with the following Mule runtime engine (Mule) and Java versions: Supported Mule and Java versions:
Mule runtime version Java version

Mule 4.13.x Edge

Java 17

Mule 4.12.x Edge

Java 17

Mule 4.11.x Edge

Java 17

Mule 4.10.x Edge

Java 17

Mule 4.9.x LTS

Java 17

Mule 4.8 Edge

Java 11, Java 17

Mule 4.6.x LTS

Java 11, Java 17

Mule 4.4

Java 11
Minor and major version changes to Mule require a manual update to your projects. Periodic Mule patch updates (such as from Mule 4.8.2 to 4.8.3) to Mule versions already downloaded to your IDE occur automatically when you log in to Anypoint Platform from the IDE.

Starting May 18, 2026, publishing connectors and Mule plugins to Exchange requires mule-extension-plugin 1.9.0 or later. Update your plugin version before publishing new connector versions.
## Known Issues For new known issues and workarounds for the February 6, 2025 release and later, see [Salesforce Known Issues](https://help.salesforce.com/s/issues). These known issues and workarounds from the December 9, 2024 release still apply to this release:
Limitation ID

When the Anypoint Code Builder launches for the first time, a corrupted dependency (.m2\repository\net\minidev\accessors-smart\1.2\accessors-smart-1.2.pom) can block the Anypoint Code Builder - Integration Extension when extracting the Mule runtime operation.

Workaround: Delete the dependency from .m2\repository\net\minidev\accessors-smart, and re-launch the IDE.

W-14047707

Previously configured sample data is overridden when selecting a component in the canvas UI.

W-16270847

There is no command to delete dependencies related to assets that you import from Exchange to an API design project.

Workaround: Remove the dependency from the dependencies node in the exchange.json file.

W-13822075

Moving the editors while searching for components from the UI canvas causes your search to be canceled.

Workaround:
Avoid rearranging your editors when using the component palette in the canvas.

W-13172200

Using autocompletion to create a parameter for the value field in the XML adds an extra #[] statement.

W-12444650

Autocompletion does not work properly when more than one connector has the same prefix.

W-10667510

Anypoint Connector for Apache Kafka (Apache Kafka Connector) does not display the Test Connection option.

W-12553536

DataSense doesn’t identify functions provided by a connector.

W-12448776

DataSense doesn’t reflect array structures at the payload’s root level.

W-12263085

DataWeave doesn’t recognize the larger context to which samples belong. So DataWeave requests sample data for all scripts within a single component.

None

DataWeave validations to produce Invalid input errors on some multiline scripts because Anypoint Code Builder does not decode Unicode characters for new lines in XML (&#10;). This limitation does not interrupt the correct execution of your Mule application.

W-11750473

Updates to metadata in one component don’t trigger metadata validation in subsequent components. This issue causes Anypoint Code Builder to display potential issues in the subsequent components.

W-12215165

The Batch Job processor is not supported by the UI canvas or through auto-complete in the configuration XML.

None

When scaffolding a GraphQL or AsyncAPI specification on Windows, an empty Mule configuration file with the name of the project is created in addition to the flows.xml file.

Workaround: Delete the empty file.

W-15757808

When source validation is enabled, AsyncAPI messages are invalid if mediaType doesn’t match the specification.

W-16663560

When source validation is disabled, AsyncAPI messages are sent downstream without transforming mediaType.

W-16663585

Source validation is not working with the Salesforce platform events application/xml content type.

W-16756836
## [](#see-also)See Also - [CloudHub](https://docs.mulesoft.com/cloudhub/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Product Versioning and Back Support Policy](https://www.mulesoft.com/legal/versioning-back-support-policy) - [トラブルシューティング](https://docs.mulesoft.com/jp/anypoint-code-builder/troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Connectors Release Notes Anypoint Connectors facilitate easy integration of your Mule applications with third-party APIs and standard integration protocols. Use them within your application’s flows to send and receive data via a protocol or specific API. The following release notes are provided for Anypoint Connectors: ## [](#mule_4)Connector Release Notes for Mule 4 - [A2A Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4) - [Adobe Marketo Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/marketo-connector-release-notes-mule-4) - [Agentforce Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/agentforce-connector-release-notes-mule-4) - [Aggregators Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/aggregators-module-release-notes) - [Amazon Bedrock Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-bedrock-connector-release-notes-mule-4) - [Amazon DynamoDB Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4) - [Amazon EC2 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-ec2-connector-release-notes-mule-4) - [Amazon Kinesis Data Streams Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4) - [Amazon Lambda Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-lambda-connector-release-notes-mule-4) - [Amazon RDS Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-rds-connector-release-notes-mule-4) - [Amazon Redshift Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-redshift-connector-release-notes-mule-4) - [Amazon S3 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4) - [Amazon Secrets Manager Properties Provider Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-secrets-manager-properties-provider-release-notes-mule-4) - [Amazon SNS Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4) - [Amazon SQS Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4) - [AMQP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-amqp) - [Anypoint MQ Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4) - [Apache Cassandra Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/cassandra-connector-release-notes-mule-4) - [Apache Kafka Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4) - [AS2 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/as2-connector-release-notes-mule-4) - [Asana Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/asana-connector-release-notes-mule-4) - [Azure Cosmos DB Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/azure-cosmos-db-connector-release-notes-mule-4) - [Azure Data Lake Storage Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/azure-data-lake-connector-release-notes-mule-4) - [Azure Event Hubs Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/azure-event-hubs-connector-release-notes) - [Azure Key Vault Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4) - [Azure Key Vault Properties Provider Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4) - [Azure Service Bus Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4) - [Azure Service Bus Management Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-mgmt-connector-release-notes-mule-4) - [Bird Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/bird-connector-release-notes-mule-4) - [Blackboard Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/blackboard-connector-release-notes-mule-4) - [Box Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/box-connector-release-notes-mule-4) - [Canvas Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/canvas-connector-release-notes-mule-4) - [CAQH Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/caqh-connector-release-notes-mule-4) - [CloudHub Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/cloudhub-connector-release-notes-mule-4) - [Coda Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/coda-connector-release-notes-mule-4) - [Compression Module Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-compression) - [Confluent Schema Registry Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4) - [Cryptography Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes) - [D2L Brightspace Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/d2l-brightspace-connector-release-notes-mule-4) - [Database Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-db) - [DHL Tracking Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/dhl-tracking-connector-release-notes-mule-4) - [DocuSign Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/docusign-connector-release-notes-mule-4) - [Dropbox Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/dropbox-connector-release-notes-mule-4) - [EDIFACT EDI Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/edifact-edi-connector-release-notes) - [Einstein AI Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/einstein-ai-connector-release-notes-mule-4) - [Email Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-email) - [File Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-file) - [FTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftp) - [FTPS Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftps) - [Gmail Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/gmail-connector-release-notes-mule-4) - [Google BigQuery Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/google-bigquery-connector-release-notes-mule-4) - [Google Calendar Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/google-calendar-connector-release-notes-mule-4) - [Google Drive Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/google-drive-connector-release-notes-mule-4) - [Google Gemini Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/google-gemini-connector-release-notes-mule-4) - [Google Pub/Sub Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/google-pubsub-connector-release-notes-mule-4) - [Google Sheets Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/google-sheets-connector-release-notes-mule-4) - [gRPC Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4) - [Hadoop (HDFS) Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4) - [HL7 EDI Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/hl7-connector-release-notes-mule-4) - [HL7 MLLP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/hl7-mllp-connector-release-notes-mule-4) - [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http) - [HTTP Service Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/service-http-release-notes) - [IBM CTG Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/ibm-ctg-connector-release-notes-mule-4) - [IBM MQ Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq) - [Informatica Business 360 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/informatica-b360-connector-release-notes-mule-4) - [Intercom Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/intercom-connector-release-notes-mule-4) - [Java Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/java-module) - [Jira Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/jira-connector-release-notes-mule-4) - [JMS Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms) - [JSON Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes) - [Kerberos Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/kerberos-module) - [LDAP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/ldap-connector-release-notes-mule-4) - [Mailchimp Marketing Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mailchimp-marketing-connector-release-notes-mule-4) - [MCP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4) - [Microsoft .NET Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dotnet-connector-release-notes-mule-4) - [Microsoft Dynamics 365 Business Central Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-365-business-central-connector-release-notes-mule-4) - [Microsoft Dynamics 365 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-365-connector-release-notes-mule-4) - [Microsoft Dynamics 365 for Finance and Operations Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-365-ops-connector-release-notes-mule-4) - [Microsoft Dynamics AX 2012 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-ax-connector-release-notes-mule-4) - [Microsoft Dynamics CRM Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-crm-connector-release-notes-mule-4) - [Microsoft Dynamics GP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-gp-connector-release-notes-mule-4) - [Microsoft Dynamics NAV Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4) - [Microsoft Excel Online Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-excel-online-connector-release-notes-mule-4) - [Microsoft MSMQ Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/msmq-connector-release-notes-mule-4) - [Microsoft OneDrive Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-onedrive-connector-release-notes-mule-4) - [Microsoft Outlook 365 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-outlook-365-connector-release-notes-mule-4) - [Microsoft Power BI Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-power-bi-connector-release-notes-mule-4) - [Microsoft Service Bus Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/ms-service-bus-connector-release-notes-mule-4) - [Microsoft SharePoint Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4) - [Microsoft Teams Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-teams-connector-release-notes-mule-4) - [Microsoft Windows PowerShell Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-powershell-connector-release-notes-mule-4) - [MongoDB Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4) - [Moodle Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/moodle-connector-release-notes-mule-4) - [MQTT Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mqtt3-connector-release-notes) - [MuleSoft AI Chain Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-ai-chain-connector-release-notes-mule-4) - [MuleSoft Inference Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-inference-connector-release-notes-mule-4) - [MuleSoft Vectors Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-vectors-connector-release-notes-mule-4) - [MuleSoft WebCrawler Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-webcrawler-connector-release-notes-mule-4) - [Neo4J Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4) - [NetSuite Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4) - [NetSuite OpenAir Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-openair-connector-release-notes-mule-4) - [NetSuite REST Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-rest-connector-release-notes-mule-4) - [NetSuite Restlet Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-restlet-connector-release-notes-mule-4) - [Notion Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/notion-connector-release-notes-mule-4) - [OAuth Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/oauth-module-release-notes) - [OAuth2 Provider Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/oauth2-provider-release-notes) - [Object Store Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4) - [OpenAI Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/openai-connector-release-notes-mule-4) - [OpenWeatherMap Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/openweathermap-connector-release-notes-mule-4) - [Oracle EBS 12.1 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-connector-release-notes-mule-4) - [Oracle EBS 12.2 Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-122-connector-release-notes-mule-4) - [Oracle PeopleSoft Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/peoplesoft-connector-release-notes-mule-4) - [Oracle Siebel Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/siebel-connector-release-notes-mule-4) - [PagerDuty Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/pagerduty-connector-release-notes-mule-4) - [QuickBooks Online Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/quickbooks-online-connector-release-notes-mule-4) - [Redis Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/redis-connector-release-notes-mule-4) - [Roostify Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/roostify-connector-release-notes-mule-4) - [RosettaNet Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/rosettanet-connector-release-notes-mule-4) - [Salesforce Commerce Cloud B2C Data Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/commerce-cloud-b2c-data-connector-release-notes-mule-4) - [Salesforce Commerce Cloud Shop API Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/shop-api-connector-release-notes-mule-4) - [Salesforce Composite Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4) - [Salesforce Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4) - [Salesforce Data Cloud Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-data-cloud-connector-release-notes-mule-4) - [Salesforce Einstein Analytics Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-analytics-connector-release-notes-mule-4) - [Salesforce Marketing Cloud Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4) - [Salesforce Marketing Cloud REST Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-marketing-cloud-rest-connector-release-notes-mule-4) - [Salesforce Pub/Sub Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4) - [SAP Concur Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/sap-concur-connector-release-notes-mule-4) - [SAP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/sap-connector-release-notes-mule-4) - [SAP S/4HANA OData Cloud Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/sap-s4-hana-connector-release-notes-mule-4) - [SAP S/4HANA SOAP Cloud Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/sap-s4-hana-soap-cloud-connector-release-notes-mule-4) - [SAP SuccessFactors Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/sap-successfactors-connector-release-notes-mule-4) - [Scripting Module Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-scripting) - [Secure Configuration Properties Extension Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/secure-properties) - [ServiceNow Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4) - [SFTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp) - [Shippo Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/shippo-connector-release-notes-mule-4) - [ShipStation Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/shipstation-connector-release-notes-mule-4) - [Shopify Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/shopify-connector-release-notes-mule-4) - [Slack Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/slack-connector-release-notes-mule-4) - [Smartsheet Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/smartsheet-connector-release-notes-mule-4) - [Snowflake Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/snowflake-connector-release-notes-mule-4) - [Sockets Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-sockets) - [Spring Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes) - [Stripe Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/stripe-connector-release-notes-mule-4) - [Tableau Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/tableau-specialist-connector-release-notes-mule-4) - [Teamwork Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/teamwork-connector-release-notes-mule-4) - [Tracing Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/tracing-module-release-notes) - [TRADACOMS EDI Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/tradacoms-edi-connector-release-notes-mule-4) - [Trello Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/trello-connector-release-notes-mule-4) - [Twilio Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/twilio-connector-release-notes-mule-4) - [Validation Module Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-validation) - [Veeva Vault Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/veeva-vault-release-notes-mule-4) - [VM Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-vm) - [Web Service Consumer Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc) - [WebSockets Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/websockets-connector-release-notes-mule-4) - [Workable Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/workable-connector-release-notes-mule-4) - [Workday Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/workday-connector-release-notes-mule-4) - [WSS Module Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4) - [X12 EDI Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/x12-edi-connector-release-notes-mule-4) - [Xero Accounting Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/xero-accounting-connector-release-notes-mule-4) - [XML Module Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-xml) - [Zendesk Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/zendesk-connector-release-notes-mule-4) - [Zoom Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/zoom-connector-release-notes-mule-4) - [Zuora AQuA Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4) - [Zuora Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint DataGraph Release Notes ## [](#january-24-2024)January 24, 2024 ### Fixed Issues
Issue Resolution ID

The user-defined mapping between source fields and target fields is now adhered to when using links with compound keys (keys with more than one value).

W-14695101

Customizations for types and methods are renamed correctly regardless of their order.

W-14712796
## [](#november-8-2023)November 8, 2023 ### What’s New - The DataGraph widget is removed from the Anypoint Platform landing page. - Output, error handling, and performance are improved for the `Delete Source` implementation. ### Fixed Issues
Issue Resolution ID

Orphan deployments no longer remain when an environment is deleted.

W-13798949

The user’s role validation is now added to the API Scaling endpoints.

W-14397779
## [](#july-20-2023)July 20, 2023 ### Fixed Issues
Issue Resolution ID

Capacity update (Scaling API calls) functionality now works correctly for every scenario (including corner cases).

W-12778347, W-13579357

The insufficient capacity warning is now displayed under the right circumstances.

W-11026609
## [](#june-27-2023)June 27, 2023 ### Fixed Issues
Issue Resolution ID

You can now disable collaboration on a Level-1 object type that contains a linked field.

W-11485830

The custom memory threshold check is now disabled to prevent false positive HTTP 429 errors.

W-13157746

When you make any change in DataGraph, the redeploy is now performed with the correct worker and vCore values.

W-13562746
## [](#april-27-2023)April 27, 2023 ### Fixed Issues
Issue Resolution ID

Users with the contributor role can no longer add or edit Exchange assets fields and descriptions.

W-11604013

You can now enable Collaboration on Level 1 object types that are returned as a single object by a query method.

W-11501282

You can now run operations through the UI after configuring a load balancer with the CLI.

W-11825355

When multiple APIs are created in API Manager, the deploy service now selects the correct API.

W-11909192

vCores are now freed up when an environment or organization is deleted.

W-12204967

You can now serialize the model successfully when an object is not present in the dialect cache.

W-12212178

The path for a single-source API in the UI is now API list / <Source API Name>.

W-12248127

When adding or upgrading sources through the CLI, additional validations now prevent merge conflicts.

W-12166528

Error logging now includes improvements to facilitate diagnosis.

W-12399713

Case management of the PassThrough authentication functionality now works correctly.

W-12415120

Inbound and outbound throttling strategy is now improved.

W-12411841, W-12513865

Link fields no longer incorrectly appear as candidates for primary keys.

W-12482623

Customer-facing application log functionality now includes fixes and improvements.

W-12451404, W-11586988

When sent as part of the request, the x-correlation-id header handling is now improved to avoid duplicated headers.

W-12068923

The DataGraph editor now recovers and displays correctly when the DataGraph model fails.

W-12451137

The DataGraph application version is updated to take advantage of the latest fixes and functionalities of Mule runtime engine.

W-12697790, W-12696055

The DataGraph UI now uses system fonts, which improves legibility, adds native support for localization and character subsets at the operating-system level, and increases performance because the browser no longer has to download custom fonts.

W-12705930, W-12695274

DataGraph policies selection is now retained on schema update.

W-11461565
## [](#november-3-2022)November 3, 2022 ### Fixed Issues
Issue ID

Links and merges now display correctly when the source APIs are added through the CLI or the UI.

W-11899204, W-11234435
## [](#september-26-2022)September 26, 2022 ### Fixed Issues
Issue ID

Using the DataGraph CLI datagraph load-balancer-config add command, you can now add a load balancer for a DataGraph application.

W-11584882, W-11637288

The datagraph load-balancer-config describe command now displays a table containing DLBs for Datagraph application.

W-11637288, W-11586296

The datagraph load-balancer-config remove command now points to the correct endpoint.

W-11586296

The CLI now correctly displays command error responses.

W-11741214
## [](#july-29-2022)July 29, 2022 ### What’s New - You can now use the DataGraph best practices ruleset in API Designer to help you ensure your API project adheres to DataGraph best practices. The ruleset is a collection of governance rules you can add as a dependency to any API project you want to use in DataGraph. See [the documentation](https://docs.mulesoft.com/jp/datagraph/ruleset) for more details. - This release increases the timeout per API call.
Issue ID

When editing an API, the Apply Changes button is enabled only when there are changes to be saved.

W-11093376

Source APIs with unions in the RAML are now transformed into the correct GraphQL type.

W-11350037

Auto generated types are now aligned with RAML definition.

W-10916247
## [](#june-1-2022)June 1, 2022 ### What’s New - You can use the `datagraph` commands on version 3.x of the Anypoint CLI to add and edit API sources in DataGraph. To do so, you must first add the appropriate DataGraph API extensions to the API sources. See [Using Anypoint Platform DataGraph CLI and API Extensions](https://docs.mulesoft.com/jp/datagraph/overview-cli-extensions) for more information. - You can now download diagnostic data from the **List of APIs added** page in DataGraph. See [Download Diagnostic Data](https://docs.mulesoft.com/jp/datagraph/retrieve-unified-schema#download-diagnostic-data) for instructions. - This release contains accessibility improvements in the UI, including the addition of alternative texts for images and alternative visual and non-visual indicators. This release also adds improvements to ensure that the product is operable with the keyboard. ### Fixed Issues
Issue ID

When changing the API URL without applying changes, navigation to the API Details page now works as expected.

W-10704011

Deployments no longer fail with a The application name is already used by other application error.

W-10678209

This release improves deployment error handling for expired accounts.

W-11043255

If a call to API Manager returns a new policy that is not compatible, the deployment now works as expected.

W-11043253

You can now add OAuth protected APIs with non-TLS endpoints to the unified schema.

W-10696989

API updates no longer fail with a HTTP 400 error when the API version is missing.

W-11138046

DataGraph now aborts deployments if the deployment environment does not exist.

W-11017379

A job that deletes organizations and environments no longer fails with a connection timeout when calling DataGraph core services.

W-11173125
## [](#april-18-2022)April 18, 2022 ### What’s New - After you’ve added an API schema to DataGraph, you can now update the version of the API source any time you like. Refer to [Update an API Version](https://docs.mulesoft.com/jp/datagraph/add-api-to-unified-schema#upate-an-api-version). ### Fixed Issues
Issue ID

DataGraph now mentions composite keys in UI messaging when you enable collaboration on an object type.

W-10739624

When configuring security, keystore state is persisted as expected.

W-10883804
## [](#march-21-2022)March 21, 2022 ### What’s New - DataGraph now supports GraphQL mutations and input types. See [Mutations and Input Types](https://docs.mulesoft.com/jp/datagraph/schemas#mutations-and-input-types) and [Write a Mutation](https://docs.mulesoft.com/jp/datagraph/write-queries-tutorial#write-a-mutation) for more information. - DataGraph now supports automatic persisted queries and query syncing from DataGraph to content delivery networks (CDNs). See [Using Persisted Queries and CDNs](https://docs.mulesoft.com/jp/datagraph/configure-apq-cdn) for instructions. ### Fixed Issues
Issue ID

DataGraph now displays an error message when you try to use special characters in a field name.

W-10594175

DataGraph now validates GraphQL allowed characters.

W-10594134

This release includes improvements in deployment error handling.

W-10594133

DataGraph now sends the certificate authority (CA) as a truststore.

W-10735331

This release includes new supported scenarios for hiding fields and methods.

W-10746617

This release includes improvements in collaboration functionality.

W-10674744, W-10660008

All re-nameable fields now contain tooltips.

W-10758463

Pass-through authentication now accepts default values as valid.

W-10810657
## [](#february-14-2022)February 14, 2022 ### What’s New - DataGraph now supports authentication with OAuth 2.0 Client Credentials. See [Supported Authentication Methods](https://docs.mulesoft.com/jp/datagraph/security#supported-authentication-methods). - DataGraph now supports mutual authentication (mTLS) to ensure that DataGraph and the underlying APIs in your unified schema can create secure, verified connections. See [Configuring Mutual Authentication in DataGraph](https://docs.mulesoft.com/jp/datagraph/security#configuring-mutual-authentication-in-datagraph). ### Fixed Issues
Issue ID

Revised the product language in DataGraph repositories for inclusivity.

W-10594346

Deployments no longer fail with unexpected HTTP 500 errors or other error types.

W-10594316, W-10594447

The DataGraph Federation service no longer fails with HTTP 500 errors on deployment startups.

W-10594266

Improved error handling for API requests when grant types are not provided.

W-10594195

When new applications are created, DataGraph now handles naming conflicts correctly.

W-10594270

Users with an Organization Owner role now have permissions to access the availability endpoint.

W-10594274
## [](#december-13-2021)December 13, 2021 ### What’s New - DataGraph now supports query methods that use composite keys. ### Fixed Issues
Issue ID

Fixed an issue in which an attacker could inject HTML in the SLA approval email template.

AQ-3763
## [](#december-6-2021)December 6, 2021 ### What’s New - When you add or edit an API in DataGraph, the status update is improved to show the progress of the update. - This DataGraph release contains accessibility improvements in the UI, including changes to color contrast and the addition of landmarks, labels, alt text, and accessible names. ### Fixed Issues
Issue ID

When you deploy changes, the status update component now works as intended and no longer shows out-of-date changes.

AQ-3836

If you edit the authentication method for an API, the UI now enables the Save button.

AQ-3856
## [](#october-2021)October 2021 ### What’s New - DataGraph now supports pass-through authentication. Refer to [Supported Authentication Methods](https://docs.mulesoft.com/jp/datagraph/security) for details. - DataGraph provides you the option to configure the number of API calls permitted for a unified schema. Increasing or decreasing API calls enables you to process higher workloads and optimize your consumption when needed. Refer to [API Call Scaling in Anypoint DataGraph](https://docs.mulesoft.com/jp/datagraph/api-call-scaling) for instructions. - The query editor contains a new actions menu for accessing response logs, query traces, and sharing the endpoint for a unified schema, as well as a button to prettify queries. - This update includes improved error handling. See [Exception While Fetching Data Error](https://docs.mulesoft.com/jp/datagraph/troubleshoot-schemas-queries#exception-while-fetching-data-error) for details. ### Fixed Issues
Issue ID

When merging types, the preview images now display correctly.

AQ-3755

When promoting an API, you can choose Sandbox and Production environments only.

AQ-3733

Users with DataGraph Admin and Organization permissions have access to retry a deployment after adding vCores.

AQ-3683

This release contains error handling improvements when switching between environments.

AQ-3677

This release contains error handling improvements when a user without permissions navigates to DataGraph.

AQ-3599

Button icons now display correctly.

AQ-3656

The query editor autocomplete shortcut help text is now compliant with Mac and Windows.

AQ-3565
## [](#september-2021)September 2021 ### What’s New - DataGraph automatically updates all applications to use the latest runtime. ### Fixed Issues
Issue ID

If you have configured no policies in API Manager, the schema explorer now loads successfully.

AQ-3563

When scrolling on the Edit Link page, the header remains fixed as intended.

AQ-3448

If you delete an asset in Exchange and then re-publish it with the same version, DataGraph now updates the API’s schema.

AQ-3264

If you try to add a new API with the same GroupId and AssetId as another API, DataGraph displays an API Already exists error.

AQ-2681
## [](#august-2021)August 2021 ### What’s New - Anypoint DataGraph now enables you to track metrics so you’re always aware of your usage relative to the limits specified for your business groups. Use these metrics to track the total number of downstream API calls made for each of the environments in which you’ve deployed a unified schema. Refer to [Track Usage Metrics for Anypoint Datagraph](https://docs.mulesoft.com/jp/datagraph/usage-metrics) for more information. - DataGraph now indicates API and unified schema modification dates: - The DataGraph overview page shows when the unified schema was last updated. (Not available to users with the consumer or operator permissions.) - The **List of APIs added** page shows when an API was added. - The **API details** page shows when an API was added and last modified. - You can now download a copy of the unified schema directly from the DataGraph query editor. ### Fixed Issues
Issue ID

When resizing the Edit method settings pane, the child elements now display inside the container.

AQ-3238

When searching logs, date ranges are validated.

AQ-3032

If you click the Last hour filter, logs no longer disappear.

AQ-3272

When editing an API schema in a Firefox browser, filtering now works as intended.

AQ-3411

You can now edit API URLs after adding an API to the unified schema.

AQ-3408

The Add link button no longer remains enabled after hiding a type.

AQ-2220
## [](#july-2021)July 2021 ### [](#whats-new-12)What’s New - The Anypoint DataGraph UI now raises error messages if you haven’t allocated the correct number of vCores to the environment in which you’re attempting to add an API. The UI enables you to reapply the same changes after allocating the correct number of vCores. - Anypoint DataGraph now supports Union type discriminators. ### [](#fixed-issues-17)Fixed Issues
Issue Number

When scrolling in the unified schema, the screen no longer abruptly scrolls up and down.

AQ-3504

Anypoint DataGraph now correctly throws HTTP 405 errors for non-supported methods instead of HTTP 500 errors.

AQ-3476

If a call to API Manager fails with a ReadTimeout error, the API deployment process now stops.

AQ-3468

The scroll button on query tracing now works as expected.

AQ-3427

Error messages no longer reveal backend implementation data.

AQ-3423, AQ-3400
## [](#june-2021)June 2021 MuleSoft announces the release of Anypoint DataGraph. Anypoint DataGraph enables you to leverage the existing capabilities of your application network by unifying all your existing data in a unified schema to create new connected experiences. Using Anypoint DataGraph, you can: - Dynamically query data from a unified schema that runs as a single SaaS GraphQL endpoint - Explore data from your application network from a single UI - Discover, reuse, and serve information from your application network without writing new code To learn more about Anypoint DataGraph, see the [Anypoint DataGraph overview](https://docs.mulesoft.com/jp/datagraph/). ## [](#see-also)See Also - [Anypoint DataGraph のトラブルシューティング](https://docs.mulesoft.com/jp/datagraph/troubleshoot-schemas-queries) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint DataGraph Release Notes Anypoint DataGraph enables you to unify all the data within your application network in a unified schema. The following release notes are provided for Anypoint DataGraph: - [Anypoint DataGraph Release Notes](https://docs.mulesoft.com/jp/release-notes/datagraph/anypoint-datagraph-release-notes) ## [](#see-also)See Also - [Anypoint DataGraph の概要](https://docs.mulesoft.com/jp/datagraph/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Exchange 2 Release Notes Moved topic: - [Anypoint Exchange Release Notes](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes) ## [](#see-also)See Also - [Anypoint Exchange Documentation](https://docs.mulesoft.com/jp/exchange/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Exchange Release Notes Anypoint Exchange is a curated catalog of reusable assets such as agents, APIs, API groups, API spec fragments, brokers, custom assets, examples, large language models (LLMs), Model Context Protocol (MCP) servers, policies, templates, integration assets such as connectors. You can catalog (publish), share, discover, learn about, and reuse assets within your organization to facilitate collaboration, boost productivity, and promote standards. ## [](#october-21-2026)October 21, 2026 ### What’s New - Exchange now supports OpenAPI Specification (OAS) 3.1. You can upload OAS 3.1 API specifications in YAML or JSON format, publish them as REST API assets, and view the specification documentation. Exchange generates a RAML version of each OAS 3.1 asset. When you download an OAS 3.1 asset as OAS, you get the original OAS 3.1 specification. Exchange doesn’t resolve dynamic references (`$dynamicRef` and `$dynamicAnchor`) and doesn’t apply custom `$schema` dialects in OAS 3.1 API specifications. ## [](#october-14-2026)October 14, 2026 ### What’s New - You can now add a scanner to discover, import, and sync MCP servers from Kong Gateway into Exchange. After the MCP servers are in Exchange, you can govern them and consume them in other applications. For more information, see [exchange::adding-kong-mcp-server-scanner.adoc](#exchange::adding-kong-mcp-server-scanner.adoc). - You can now add a scanner to discover, import, and sync agents from ServiceNow AI Agents into Exchange. The scanner imports agents created in ServiceNow AI Agent Studio. After the agents are in Exchange, you can govern them and consume them in other applications. For more information, see [exchange::adding-servicenow-scanner.adoc](#exchange::adding-servicenow-scanner.adoc). - You can now make your MCP server and agent assets public in Exchange, the same way you do for API assets. Exchange administrators can publish an asset version to the organization’s public portal from the Share dialog, and set instance visibility to public or private. The asset stays available inside your organization. Consumers can then add public MCP servers to API Manager. See, see, [api-manager::create-instance-public-exchange.adoc](#api-manager::create-instance-public-exchange.adoc). For more information, see [公開ポータルへの API のパブリッシュ](https://docs.mulesoft.com/jp/exchange/to-share-api-asset-to-portal). ## [](#september-4-2026)September 4, 2026 ### What’s New - When the scanner discovers an API in Kong Gateway, it assigns an asset type in Exchange based on the API’s Kong protocol and plugins. For more information, see [Protocol to Asset Type Mapping](#exchange::adding-kong-gateway-scanner.adoc#protocol-to-asset-type-mapping). ### Fixed Issues
Issue Resolution ID

Agent retrieval response times are now faster.

W-21922690

The Kong API Gateway scanner no longer publishes the same asset as new on every scan run.

W-23420989

The Microsoft Azure AI Foundry scanner now captures the full agent responses endpoint URL instead of the project URL.

W-23542862

The Snowflake scanner now includes Comment and Profile in metadata fields.

W-23599680
## [](#august-28-2026)August 28, 2026 ### What’s New - The Kong Gateway scanner now detects gRPC and GraphQL protocols and assigns the correct asset type in Exchange and Omni Gateway for these APIs. APIs that use other protocols are registered as asset type REST for now. MuleSoft plans to support more protocols in a future release. For more information, see [exchange::adding-kong-gateway-scanner.adoc](#exchange::adding-kong-gateway-scanner.adoc). - Agent scanners now deliver a consistent set of metadata across every provider. Whether you scan Amazon Bedrock and AgentCore, Azure AI Foundry, Microsoft Copilot, Google Vertex, Snowflake, Databricks, or GoDaddy ANS, each scanner captures the same core fields for agent identity, lifecycle and ownership, and the agent’s model and instructions. This gives you a uniform view of each agent, where it lives, and what powers it, regardless of the platform it runs on. Standardized metadata makes it easier to compare, govern, and discover agents from different providers in one place. ## [](#august-10-2026)August 10, 2026 ### Fixed Issues
Issue Resolution ID

Agent retrieval response times are now faster.

W-21922690

The Kong Gateway scanner no longer publishes the same asset as new on every scan run.

W-23420989

The Microsoft Azure AI Foundry scanner now captures the full agent responses endpoint URL instead of the project URL.

W-23542862

The Snowflake scanner now includes Comment and Profile in metadata fields.

W-23599680

Creating and testing Databricks scanner connections now works for Databricks workspaces on Azure.

W-23255193

The list of scanner providers now displays a complete list of providers.

W-23432675

Agent scanners can now be deleted from the Scanners page.

W-23464071

Creating an Amazon Bedrock agent scanner no longer fails.

W-23464715
## [](#august-6-2026)August 6, 2026 ### What’s New - API scanners now read policies from these provider platforms: Amazon API Gateway, Google Apigee, Azure API Management, and Kong Gateway. For more information, see: - [exchange::adding-amazon-gateway-scanner.adoc](#exchange::adding-amazon-gateway-scanner.adoc) - [exchange::adding-apigee-scanner.adoc](#exchange::adding-apigee-scanner.adoc) - [exchange::adding-azure-api-management-scanner.adoc](#exchange::adding-azure-api-management-scanner.adoc) - [exchange::adding-kong-gateway-scanner.adoc](#exchange::adding-kong-gateway-scanner.adoc) ## [](#july-2026)July 2026 ### What’s New - Publishing custom connectors and Mule plugins to Exchange now requires Java compatibility metadata in `mule-artifact.json` for new versions that change supported Java compatibility. To avoid publishing failures, update your connector build configuration to a supported supported Mule SDK or plugin configuration that writes Java compatibility metadata before publishing new versions. This change doesn’t affect connectors already published to Exchange or running applications. For configuration steps and troubleshooting, see [Publishing Connectors to Exchange](https://docs.mulesoft.com/mule-sdk/latest/publishing-connectors-exchange). - Exchange now supports publishing A2A Protocol v1.0 agent cards. When you create an agent asset, you can select **A2A v1.0 card** as the protocol type to publish a v1.0-compliant Agent Card. The v1.0 card supports the `supportedInterfaces` field for declaring transport bindings and optional card signatures. A2A v0.3 cards remain available as a separate protocol option (**A2A v0.3 card**). A single asset version can carry both a v0.3 card and a v1.0 card under separate classifiers. There is no automatic conversion between versions. For more information, see [Create an Agent](https://docs.mulesoft.com/jp/exchange/to-create-an-asset#create-agent). - The card details page for A2A v1.0 agents now displays: - Supported interfaces (protocol binding, URL, protocol version, and tenant) - Signature indicator (shown only for signed cards) - Provider information - Security schemes - Capabilities (streaming, push notifications, state transition history) - Skills (with descriptions, input/output modes, and examples) - Exchange now includes Agent Network as a supported asset type. An agent network is a coordinated group of agents, brokers, LLMs, and MCP servers that acts as a central hub for defining, validating, and executing agentic processes across your enterprise. This asset is published to Exchange from Anypoint Code Builder and is read-only. For more information, see [アセットタイプ](https://docs.mulesoft.com/jp/exchange/asset-types). - You can now use the Agentforce scanner to import Agentforce agents into Exchange. For more information, see [exchange::adding-agentforce-scanner.adoc](#exchange::adding-agentforce-scanner.adoc). - You can now add scanners to automatically discover and catalog MCP servers from these external providers: - Microsoft Azure API Management MCP Server - Databricks Agent Bricks MCP Server For more information, see: - [exchange::adding-agentforce-scanner.adoc](#exchange::adding-agentforce-scanner.adoc) - [exchange::adding-azure-apim-mcp-scanner.adoc](#exchange::adding-azure-apim-mcp-scanner.adoc) - [exchange::adding-databricks-mcp-scanner.adoc](#exchange::adding-databricks-mcp-scanner.adoc) - The Amazon Bedrock AgentCore Runtime scanner now adds richer metadata to Exchange agent cards and documentation, helping users evaluate agents faster. The Exchange details page for scanned agents now shows: - Created At - Updated At - Foundation Model - Skills - Collaboration Model - Importing Agentforce agents from **Settings** is deprecated. To import Agentforce agents, create an Agentforce scanner. For more information, see [exchange::adding-agentforce-scanner.adoc](#exchange::adding-agentforce-scanner.adoc). ### Fixed Issues
Issue Resolution ID

The Databricks scanner now correctly authenticates on Azure-hosted Databricks workspaces using OAuth Machine-to-Machine (M2M) authentication and no longer returns an invalid_client error.

W-23255193

When a new scheduled scanner run starts, any existing manual run in PENDING_REVIEW status is now fully cancelled, including termination of its associated Temporal workflow, so subsequent manual runs no longer fail with a 409 conflict.

W-22735433

The Salesforce Agentforce scanner now supports non-root business groups, enabling discovery and scanning of Agentforce assets across all business groups in an organization.

W-23293582
## [](#june-2026)June 2026 ### What’s New The required scope URL to retrieve agent metadata for the Microsoft Copilot scanner is updated to `[https://.api.crm.dynamics.com](https://\.api.crm.dynamics.com)`. For more information see, [exchange::adding-microsoft-copilot-scanner.adoc](#exchange::adding-microsoft-copilot-scanner.adoc). ### Fixed Issues
Issue Resolution ID

The scope URL validation for the Microsoft Copilot scanner is now updated and no longer fails to retrieve agents during a scan.

W-22550680

Agent cards for agents added in Exchange from Anthropic Claude, Databricks Agent Bricks, and Snowflake Cortex AI now display the protocol type as Other instead of A2A.

W-22493536, W-22493540, and W-22493542
### What’s New - Administrators can now add scanners to automatically discover and catalog services for these external providers: - Anthropic Claude (agents) - Databricks Agent Bricks (agents) - LangChain LangSmith (agents) - Snowflake Cortex AI (agents) - Snowflake MCP (MCP servers) For more information, see: - [exchange::adding-claude-scanner.adoc](#exchange::adding-claude-scanner.adoc) - [exchange::adding-databricks-agent-bricks-scanner.adoc](#exchange::adding-databricks-agent-bricks-scanner.adoc) - [exchange::adding-langsmith-scanner.adoc](#exchange::adding-langsmith-scanner.adoc) - [exchange::adding-snowflake-cortex-ai-scanner.adoc](#exchange::adding-snowflake-cortex-ai-scanner.adoc) - [exchange::adding-snowflake-mcp-scanner.adoc](#exchange::adding-snowflake-mcp-scanner.adoc) ## [](#may-2026)May 2026 ### What’s New - Generative AI documentation now supports gRPC APIs, MCP servers, and agents, in addition to REST, SOAP, AsyncAPI, and GraphQL APIs. For more information, see [exchange::generating-documentation-with-ai.adoc](#exchange::generating-documentation-with-ai.adoc). - You can now add a scanner to discover, import, and sync APIs from external providers into Exchange. Once imported, you can apply governance rulesets and publish these services to a developer portal. Supported gateways are Amazon API Gateway, Azure API Management, Kong API Gateway, and Google Apigee. For more information, see: - [exchange::adding-amazon-gateway-scanner.adoc](#exchange::adding-amazon-gateway-scanner.adoc) - [exchange::adding-azure-api-management-scanner.adoc](#exchange::adding-azure-api-management-scanner.adoc) - [exchange::adding-kong-gateway-scanner.adoc](#exchange::adding-kong-gateway-scanner.adoc) - [exchange::adding-apigee-scanner.adoc](#exchange::adding-apigee-scanner.adoc) - The Amazon AgentCore scanner has been enhanced to now support the automatic discovery and cataloging of MCP servers. After the MCP servers are registered, you can govern and consume them in other applications. For more information, see [exchange::adding-agentcore-mcp-scanner.adoc](#exchange::adding-agentcore-mcp-scanner.adoc). - You can now review and approve scan results before they’re imported into Exchange, giving you control over which external services are added to your catalog. When you configure a scanner to **Ask to review**, its status changes to **Pending review** after the scan completes. Open the scan to choose which services to import. Services you don’t import remain pending and reappear in the next scan. To permanently exclude a service from future scans, use the action menu to add it to the **Skipped** list. To enable manual review, set the scheduled run configuration to **Ask to review** when you add or edit a scanner. For more information, see [Review Scan Results Manually](#exchange::managing-scanners.adoc#review-scan-results-manually). - The **Agent Scanners** page in the Exchange sidebar has been renamed to Scanners, where you can now access all scanners regardless of service type from a single page. For more information, see [exchange::discovering-and-importing-external-agents.adoc](#exchange::discovering-and-importing-external-agents.adoc). ## [](#april-2026)April 2026 ### What’s New - Exchange now supports SHA-256 checksums for all assets, providing higher security standards for verifying asset integrity during download and distribution. - In addition to REST APIs, generative AI now supports expanded API documentation generation for SOAP APIs, AsyncAPI, and GraphQL. You can now generate documentation for API assets published using either single-file or multi-file specifications. For more information, see [exchange::generating-documentation-with-ai.adoc](#exchange::generating-documentation-with-ai.adoc). - Agents verified by GoDaddy agent network service (ANS) in API Management now display a verified badge in the Exchange catalog and on asset detail pages, helping you quickly identify trusted assets. Instances also show whether managed instances are verified. For more information, see: - [Agent Fabric Assets](https://docs.mulesoft.com/jp/exchange/#agent-fabric-assets.adoc) - [View Instances](https://docs.mulesoft.com/jp/exchange/asset-details#view-instance.adoc) - [API インスタンスの設定](https://docs.mulesoft.com/jp/exchange/to-configure-api-settings) - You can now add a scanner to automatically discover and catalog Amazon Bedrock AgentCore and Microsoft Foundry agents. This lets you govern and consume the agents in other applications. For more information, see: - [exchange::adding-bedrock-agentcore-scanner.adoc](#exchange::adding-bedrock-agentcore-scanner.adoc) - [exchange::adding-microsoft-foundry-scanner.adoc](#exchange::adding-microsoft-foundry-scanner.adoc) - Permissions for configuring a Microsoft Copilot Studio scanner now include read-only access for scanning Microsoft Copilot Studio agent metadata. For more information, see [exchange::adding-microsoft-copilot-scanner.adoc](#exchange::adding-microsoft-copilot-scanner.adoc). ## [](#march-2026)March 2026 ### What’s New - You can now use the Exchange MCP server endpoint to retrieve asset and instance metadata from Exchange for your AI agents, without requiring Omni Gateway. For more information, see [exchange::retrieve-asset-metadata-using-mcp.adoc](#exchange::retrieve-asset-metadata-using-mcp.adoc). - Informatica’s CDGC Metadata Search MCP server and Cloud Address Verification MCP server are now available in Exchange. These assets are published to Exchange under **Provided by MuleSoft** and are maintained by Informatica. For more information about publicly hosted MCP servers, see [MuleSoft Assets](https://docs.mulesoft.com/jp/exchange/#mulesoft-assets). - Exchange now supports gRPC APIs. You can now publish and consume gRPC APIs in Exchange. A gRPC API is specified in a Protocol Buffers (.proto) file that declares services and message contracts. For more information, see: - [アセットタイプ](https://docs.mulesoft.com/jp/exchange/asset-types) - [アセットの作成](https://docs.mulesoft.com/jp/exchange/to-create-an-asset) ## [](#february-2026)February 2026 ### What’s New - You can now add a scanner to automatically discover and register GoDaddy ANS agents. GoDaddy ANS agents are verified by GoDaddy to be safe and secure. Govern and consume the agents in other applications. For more information, see: - [exchange::discovering-and-importing-external-agents.adoc](#exchange::discovering-and-importing-external-agents.adoc) - [exchange::adding-godaddy-scanner.adoc](#exchange::adding-godaddy-scanner.adoc) ## [](#january-2026)January 2026 ### What’s New - You can now add agent scanners to automatically discover and register AI agents across agent ecosystems on external platforms, which include Amazon Bedrock, Google Vertex AI, and Microsoft Azure Copilot. After the agents are registered, govern and consume them in other applications. For more information, see [exchange::discovering-and-importing-external-agents.adoc](#exchange::discovering-and-importing-external-agents.adoc). - You can now use an MCP server URL to add the server’s metadata when publishing it to the registry in Exchange. For more information, see [Create an MCP Server](https://docs.mulesoft.com/jp/exchange/to-create-an-asset#create-mcp). - Exchange now syncs public MCP servers from the official MCP registry to **Provided by MuleSoft**. These public MCP servers are maintained by the original providers and not MuleSoft. - You can now create and manage instances for publicly available MCP servers in API Manager to govern and monitor public assets. These assets are published to Exchange under **Provided by MuleSoft** and are maintained by their original providers, not by MuleSoft. When you create an instance from a publicly available asset, the instance is created within your private organization in Exchange and managed like any other instance in API Manager. For more information see, [api-manager::create-instance-public-exchange.adoc](#api-manager::create-instance-public-exchange.adoc). - You can now request access to running instances from publicly available assets. Instances for MCP servers published in **Provided by MuleSoft** are created within your private organization. ## [](#november-2025)November 2025 ### What’s New - API Notebook reached End of Life on November 28, 2025. ## [](#october-2025)October 2025 ### What’s New - API Notebook is scheduled for End of Life on November 28, 2025. - Exchange now supports agent, broker, large language model (LLM), and Model Context Protocol (MCP) server asset types and Agentforce agents for Agent Fabric. For more information, see: - [Agent Fabric](#general::learning-map-agent-fabric.adoc). - [アセットタイプ](https://docs.mulesoft.com/jp/exchange/asset-types) - [exchange::importing-agentforce-agents.adoc](#exchange::importing-agentforce-agents.adoc) - [Create an agent asset](https://docs.mulesoft.com/jp/exchange/to-create-an-asset#create-agent) - [Create an MCP server asset](https://docs.mulesoft.com/jp/exchange/to-create-an-asset#create-mcp-server) - [Create an LLM asset](https://docs.mulesoft.com/jp/exchange/to-create-an-asset#create-a-large-language-model) ## [](#july-2025)July 2025 ### What’s New - Admins can choose how asset owners can dte asset versions in Exchange. They can enable or disable the ability to permanently delete an asset to reuse the GAV (group ID, asset ID, and version) for a new asset. It doesn’t matter when the asset version was created. When enabled, asset owners see an option to allow the GAV to be reused when deleting an asset version. When disabled, the GAV can’t be reused after deleting the asset version. For more information, see [exchange::managing-asset-deletion.adoc](#exchange::managing-asset-deletion.adoc). - Admins can control whether or not to assign owner roles when creating assets using a connected app. When enabled, when creating new assets using a connected app, roles aren’t assigned to connected app owners. When disabled, roles are assigned by default. For more information, see [exchange::managing-connected-apps.adoc](#exchange::managing-connected-apps.adoc). ## [](#june-2025)June 2025 ### What’s New - Users can now generate comprehensive and standardized API documentation for REST APIs from Exchange. This feature uses Einstein generative AI to analyze and create documentation, saving time and effort and ensuring high quality API creation. Users can focus on developing APIs while Einstein handles the documentation. For more information, see [exchange::generating-documentation-with-ai.adoc](#exchange::generating-documentation-with-ai.adoc). - Client application owners can now add multiple individual users or teams as additional owners, granting them management capabilities for the client application. For more information, see [Add Users as Client Application Owners](https://docs.mulesoft.com/jp/exchange/about-my-applications#add-users-as-client-application-owners). ## [](#december-2024)December 2024 ### What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) For more information, see [Anypoint Exchange on Control Planes](https://docs.mulesoft.com/jp/exchange/#exchange-on-control-planes). ## [](#october-2024)October 2024 ### What’s New - You can now publish AsyncAPI 2.6 specifications with Avro schemas to share, discover, and reuse within your organization. To learn about the AsyncAPI journey, see [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). ## [](#september-2024)September 2024 ### What’s New - The Exchange Maven Facade API version 3 now supports dynamic parameters for `artifactId` and `version` fields. For more information, see [Maven を使用したアセットのパブリッシュ](https://docs.mulesoft.com/jp/exchange/to-publish-assets-maven). ## [](#june-2024)June 2024 ### What’s New - You can now publish AsyncAPI 2.6 specifications to share, discover, and reuse within your organization. To learn about the AsyncAPI journey, see [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). ## [](#april-2024)April 2024 ### What’s New App developers can now view GraphQL schemas and write, run, and test GraphQL APIs using the GraphQL console from the asset details page. For more information, see [exchange::view-graphql-api-schemas-and-run-queries.adoc](#exchange::view-graphql-api-schemas-and-run-queries.adoc). ## [](#february-2024)February 2024 ### What’s New You can now see the compatible Java versions for a connector by clicking **View version** in the asset details page. ## [](#october-2023)October 2023 ### What’s New You can now find and discover assets using the **Custom field** filter in the enhanced search experience. For more information about the custom field filter, see [Filter By Custom Fields](https://docs.mulesoft.com/jp/exchange/to-find-info#filter-by-custom-fields). ## [](#july-2023)July 2023 ### What’s New Exchange now provides asset usage and engagement metrics for administrators and asset owners to gain insight into the consumption and user engagement of their API specification fragments and REST APIs. The usage metrics measure how many times those assets are downloaded from Exchange, imported from API Designer, imported from Anypoint Studio, and the number of dependents and contracts for the asset. The asset engagement score is a composite metric that administrators and asset owners can use to measure the usage of the assets in Exchange. ## [](#may-2023)May 2023 ### What’s New The assets details page lets you find specific information within the API specification and pages of an asset using the CTRL+F or the command+F keyboard shortcut. In Exchange, this enhanced shortcut overrides the native browser shortcut, which searches only for words and phrases on the current page. ## [](#april-2023)April 2023 ### What’s New Exchange now includes the following RPA template asset types: - RPA Activity templates Activity templates are reusable code within RPA to standardize the most used activity steps and make them available to other developers in the organization. These templates are `.cawl` files that are imported in the RPA Activity library for developers to use as part of their RPA processes. - RPA Process templates Templates for RPA processes are imported into RPA Builder as projects and are customizable before deploying to RPA bots. Process templates are built on common patterns for RPA to build automation faster. These templates are `.crpa` files that are exported from RPA Builder to share with other developers. ## [](#february-2023)February 2023 ### What’s New - The enhanced search is now the default search experience for users logging into Exchange. Using the enhanced experience, you can: - Filter assets by type, organization, category, tag, and lifecycle state - See which API Spec properties and page text matched the search term - Save shortcuts to filters you have applied - Sort search results by relevance, name, last modified date, or rating For more details about the enhanced search, see [Search for Assets](https://docs.mulesoft.com/jp/exchange/to-find-info). The legacy search experience is still available by clicking **Back to legacy search** from the Exchange landing page. - Exchange now supports JSON Schema and OAS 3.0 components as sub-types for the API Fragments asset type. ## [](#january-2023)January 2023 ### What’s New - The documentation now uses more inclusive language. - The product now uses more inclusive language. - Exchange now includes the GraphQL API asset type. A GraphQL API allows a client to fetch only the object types and fields needed instead of fetching a fixed response like in a REST API. - A new Creator permission gives users the Asset Administrator role for the assets they create but restricts modifying assets or asset versions created by other users in the business group. For details, see [Set User Access Permissions](https://docs.mulesoft.com/jp/exchange/to-set-permissions). ## [](#august-2022)August 2022 ### What’s New A new **Conformance Status** page enables API developers to see details about conformance of their validated API definitions to governance rulesets. For details, see [View Conformance Status](https://docs.mulesoft.com/jp/exchange/asset-details#view-conformance-status). ## [](#july-2022)July 2022 ### What’s New - The search functionality has the following enhancements: - Improved sorting and synchronization between filters and the sidebar - Results display in list view when a search query is executed - Advanced search experience is enabled when searching for assets within the **shared with me** tab ## [](#april-2022)April 2022 ### What’s New Exchange now includes the following asset types: - Policy definition - Policies enforce regulations to help manage security, control traffic, and improve API adoption. Create a policy definition based on your specific business requirements and apply them to APIs to extend existing functionality or define new ones. - Ruleset - Rulesets are a group of rules or guidelines that define an application, for example, best practices or industry-specific standards. Add a ZIP file with multiple YAML files that describe the new ruleset. ## [](#march-2022)March 2022 ### [](#new-features)New Features Exchange now supports asset lifecycle states of development, stable, and deprecated to track the progress of assets as they move through the software development lifecycle. We intuitively redesigned the asset details page and added the following capabilities: - Affinity grouping - Asset information is now intuitively organized. - Patch versions - New Manage versions table to quickly view version details, add and delete a version, and change the lifecycle state for a version. - Lifecycle states - View the lifecycle state of an asset. - Last modified date - See when an asset was changed. - Collapsible metadata - Hide and expand metadata such as version, last published, categories, and tags. ## [](#september-2021)September 2021 ### [](#new-features-2)New Features - The Exchange API enables you to update asset metadata, including categories, custom fields, tags, and documentation pages, without needing to create a new asset version. ### [](#fixed-in-this-release)Fixed in This Release - The **API is behind firewall** setting persists across page refreshes and different browser sessions in the same browser. - Search results display correct asset names. ## [](#august-2021)August 2021 ### [](#new-features-3)New Features - The Exchange GraphQL API version 2 exposes the `status` and `contractsCount` properties for the API instances related to an API asset. - The Exchange GraphQL API version 2 exposes the `apiGroupInstances` property with information from the API group instances related to an API group asset. - The Exchange API, Exchange GraphQL API version 2, and Exchange Maven Facade API support connected application authentication, which can execute Exchange requests without sending a token by using the client application credentials of the client ID and client secret. - The Exchange form to publish assets has an optimized user experience. - Exchange supports resizing the portal sidebar to improve the readability of long API console endpoint labels. - The Exchange API portal includes an example `curl` request to add resources. - The API console supports options to sort endpoints alphabetically and to show full endpoint paths. - Exchange validates tag length. ### [](#fixed-in-this-release-2)Fixed in This Release - The delete version button works correctly for policy assets. - Selecting a section in the portal sidebar does not close API console dropdown menus. - Canceling changes on the asset sharing page works correctly. - After deleting a category, search results display the correct assets. ## [](#july-2021)July 2021 ### [](#new-features-4)New Features - Each asset has the optional properties `contactName` and `contactEmail` to record the name and email address of a person to contact about the asset. - Audit logs record creating a public portal and discarding a public portal draft. - Exchange API version 2, Exchange Maven Facade API, and Anypoint CLI enable you to use a single request to both create an asset and set mutable asset data including tags, categories, custom fields, and documentation pages. ### [](#fixed-in-this-release-3)Fixed in This Release - For users who are not logged in, public portals display a disabled request access button with a tooltip explaining that the user must log in to make a request. - Exchange prevents creating a category with an invalid value for the field `assetTypeRestrictions`. ## [](#june-2021)June 2021 ### [](#new-features-5)New Features - Exchange administrators and asset administrators can share an asset with a team in their organization. - The Exchange interface implements improved accessibility standards, including: - Colors with better contrast for button hover states, links to rate and review assets, and search fields - Typeahead styles - Focus states for certain menus and buttons - Dropdown menu styles - Page title field styles - The Anypoint CLI `asset list` command accepts an optional `organization` argument. - Exchange security sanitizes asset information to plain text for asset-sharing notification emails. - The Anypoint CLI supports managing asset portal resources such as images with the `exchange asset resource` commands. ### [](#fixed-in-this-release-4)Fixed in This Release - The **View Code** action correctly links to Anypoint Design Center for API assets. - The **Open Flow** action correctly links to Anypoint Flow Designer for template assets. - Audit logs record adding assets to and removing assets from a public portal. - Exchange prevents changing instance visibility while the instance is loading. ## [](#may-2021)May 2021 ### [](#new-features-6)New Features - Exchange relocated interface elements to prevent confusion, including the search bar and the button to publish assets. - On macOS, you can save the asset name with the Command+Return keyboard combination. ### [](#fixed-in-this-release-5)Fixed in This Release - Exchange security prevents certain types of cross-site scripting attacks that exploit remote image headers. - Exchange security prevents certain types of path traversal attacks that attempt to expose authorization tokens. - Deleted minor versions of assets do not appear in menus or cause "Resource not found" errors. - You can assign new values to variables defined in previous executions of API notebooks. - Search results correctly display titles of terms and conditions pages. - The API instances list displays with correct alignment when showing errors. - Files upload correctly after a failed previous upload attempt. ## [](#april-2021)April 2021 ### [](#new-features-7)New Features - Exchange cookie consent management provides public portal website visitors with full documentation and control of all cookies, in compliance with marketing and privacy regulations. ### [](#fixed-in-this-release-6)Fixed in This Release - The version menu is visible when a video is included in the asset description. - When you apply a change to a category, the Exchange interface shows an animation while the change is applied. - Exchange API requires authorization to rate or review assets. - When you add an asset type restriction to a managed category, the value for that category is removed from each asset whose type is not allowed by the restriction. - Portal editing works correctly with the Apple Safari browser. - Deleting a category removes it from all assets. - Exchange shows only relevant warning messages. - Exchange verifies that asset type restrictions for tags use valid asset types. ## [](#march-2021)March 2021 ### [](#new-features-8)New Features - Exchange API v2 offers several new features: - Share assets with users and organizations. - Edit the version-agnostic properties of an asset: name, description, and icon. - Request access to API Groups. - Add resources such as images to the asset documentation and the public portal. - Publish assets asynchronously. - Publish and consume any asset type supported by Exchange, including connectors, examples, templates, Mule applications, and policies. - Exchange Maven Facade API v3 includes improved error messages, publication feedback, and the capability to publish custom assets. Using Maven Facade API v3 to publish assets to Exchange requires the Mule Maven plugin version 3.5.0 or later. For examples and details, see the [New Features](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/exchange-maven-facade-api-http/minor/3.0/pages/New%20Features/) section of the API documentation on Exchange. - Exchange star ratings have enhanced design for improved accessibility. (EXC-7286) - When you share an asset and search for users, Exchange uses enhanced highlighting on the search results as you type. (EXC-5434) - Exchange does not require you to scroll to read long tag names. (EXC-4261) ### [](#fixed-in-this-release-7)Fixed in This Release - To ensure that assets use semantic versioning, Exchange prevents you from creating an asset with a version that starts with `v`. (EXC-7210, EXC-7292) The Exchange user interface supports accessing and deleting existing assets with versions that start with `v`. - When you change an API to private or public, Exchange immediately shows the update. (EXC-6871) - When you add a category value to an asset, Exchange shows newly created values. (EXC-6822) - Exchange supports listing and downloading asset portal pages using Anypoint CLI. (EXC-5362) - When you add or delete a review, Exchange immediately shows the update. (EXC-3022) ## [](#february-2021)February 2021 ### [](#fixed-in-this-release-8)Fixed in This Release - Exchange graph search returns results correctly and without errors. (EXC-3769) - The Markdown editor visual mode does not escape underscores when it is not necessary. (EXC-4564) - After you create a new application on the request access page, the application menu shows all available API instances. (EXC-6398) ## [](#january-2021)January 2021 ### [](#fixed-in-this-release-9)Fixed in This Release - Deleting a review of a previous patch version of an asset works correctly. (EXC-7020) - Minor version selection on the API instances page works correctly and does not leave the page. (EXC-7068) - The sidebar shows correct highlighting when an account has only one organization. (EXC-7037) - The `exchange asset copy` command of `anypoint-cli` correctly copies the specified asset. (EXC-7086) - When you change the business group scope in the navigation bar, the business group section in the sidebar shows the correct business group. (EXC-7105) ## [](#december-2020)December 2020 ### [](#new-features-9)New Features - The request access panel correctly filters API instances and does not show deprecated instances. (EXC-3044) - Audit logs record changing an asset name, description, or icon. (EXC-6975) - The portal of an asset with an unsupported type displays correctly without a 500 error. (EXC-7007) ### [](#fixed-in-this-release-10)Fixed in This Release - Exchange documentation pages support links to other documentation pages such as `[the home page](https://docs.mulesoft.com/jp/release-notes/exchange/pages/Home)`. (EXC-6778) - Public portals correctly show only public API instances. (EXC-6969) - Deleting a terms and conditions page works correctly. (EXC-6983) - In a client applications page, the button to download charts downloads the CSV file correctly. (EXC-7062) ## [](#november-2020)November 2020 ### [](#new-features-10)New Features - The new Exchange search experience shows more than 20 results. - The new Exchange search experience offers multiple [search result relevance](https://docs.mulesoft.com/jp/exchange/to-find-info) options. - The Exchange API version 1 documentation on Exchange is edited and updated. ### [](#fixed-in-this-release-11)Fixed in This Release - In asset portals, long category names display correctly and wrap correctly. (EXC-3023) - When searching all types in a public portal, the asset type filter correctly shows **All types**. (EXC-6370) - Opening Exchange in Anypoint Studio does not display an incorrect message about temporarily disabled search features. (EXC-6723) - The API instances page for API groups shows the sidebar. (EXC-6868) ## [](#october-2020)October 2020 ### [](#new-features-11)New Features - Attempting to publish an asset with a changed API version but without an increased asset major version shows an improved error message. (EXC-4989) - The asset creation page shows information about the `groupId` field. (EXC-5326) - The version field shows help text about Semantic Versioning and a link for more details. (EXC-5423) - The title of the page for adding a new version correctly reads **Add a new version**. (EXC-5424) ### [](#fixed-in-this-release-12)Fixed in This Release - Links to Exchange documentation page headers work correctly. (EXC-6413) - Public portals consistently show the API console. (EXC-6526) - Removing all asset type restrictions from a category’s configuration does not change the categories assigned to an asset. (EXC-6592) - When you log in to Anypoint, the sidebar correctly highlights the selected section. (EXC-6618) - After you create a new asset version, Exchange correctly renders the public portal. (EXC-6650) - Exchange prevents users from navigating from a portal draft to the group instances page. (EXC-6675) - When requesting access to an API group, the preview of the terms and conditions renders correctly. (EXC-6672) - The search field **Clear** button has accessibility text. (EXC-6776) - Exchange correctly encodes login redirection URIs without 404 errors. (EXC-6840) ## [](#september-2020)September 2020 ### [](#new-features-12)New Features - Asset portals validate images and discard corrupted files. (EXC-6619, EXC-6643) ### [](#fixed-in-this-release-13)Fixed in This Release - Asset creation works in all cases when publishing from Anypoint Studio. (EXC-6400) - The API console renders endpoints in the correct order. (EXC-6445) - A saved search without an organization filter returns results correctly. (EXC-6553) - Exchange has improved session cookie security. (EXC-6656) ## [](#august-2020)August 2020 ### [](#fixed-in-this-release-14)Fixed in This Release - Exchange prevents inconsistently sharing an asset with the same API version in a different asset major version. (EXC-6517) - Deleting an asset with a dependency loop works correctly. (EXC-6554) - Anypoint Studio correctly shows the public portal for a custom asset. (EXC-6599) ## [](#july-2020)July 2020 ### [](#new-features-13)New Features - An error in a field of the advanced section expands the section to make it visible. (EXC-4263, EXC-6056) - Exchange shows loading states when editing an asset name or asset description. (EXC-6091) - Changing or removing an icon from an Exchange asset also changes or removes the icon from automatically generated assets such as Mule connectors and plugins. (EXC-6356, EXC-4421) ### [](#fixed-in-this-release-15)Fixed in This Release - Creating an asset with a connected application token works correctly and without authorization errors. (EXC-6198) - The request access page correctly shows API instance environment names. (EXC-6264) - An asset’s public portal prevents users from performing private portal actions such as share and edit. (EXC-6281) - On the asset creation page, if the `assetId` field shows an error message, modifying the field correctly updates the message. (EXC-6302) - Public portals correctly render custom favicons. (EXC-6359) ## [](#june-2020)June 2020 ### [](#new-features-14)New Features - Exchange supports OpenAPI Specification (OAS) 3.0 APIs. - Exchange includes new API console version 6.2, including support for OAS 3 specifications. - Public portals prompt external users for read-only access to their basic profile information when they log in for the first time. (EXC-4846) This change applies to all Anypoint Platform instances hosted in the EU control plane, in the US control plane, or in MuleSoft Government Cloud. - Exchange shows a descriptive error message when an asset ID field is not unique. (EXC-5328) ### [](#fixed-in-this-release-16)Fixed in This Release - Images render correctly when changing versions on an asset portal. (EXC-4677) - The Exchange public portal prompt ensures user approval for all user information access. (EXC-4846) - Exchange prevents errors by correctly distinguishing session management between private Exchange instances and public portals. (EXC-4891) - Public assets provided by the MuleSoft organization do not include the redundant `visibility` attribute. (EXC-4892) - A proxy serves external images so that image servers cannot read user IP addresses. (EXC-5361) - Exchange GraphQL v2 API calls return only successfully generated connectors. (EXC-5413) - Intermittent issues preventing public Exchange from rendering correctly are fixed. (EXC-5419) - Mocking service instances in API portals display the correct public or private visibility status. (EXC-5939) - Exchange prevents users from navigating to an inconsistent editing state. (EXC-5943) - Exchange returns correct `customFields` objects and no empty objects for all API queries. (EXC-6016) - The **API instances** section of an API specification asset portal renders correctly when the API version contains non-ASCII characters. (EXC-6057) - The API console renders correctly after leaving edit mode in a portal. (EXC-6058) - The mocking service accepts calls with a `baseUriParameter` value. (EXC-6061) - Asset type icons render correctly in the overview panel of asset detail pages. (EXC-6082) - Exchange security prevents users from including remote HTML files. (EXC-6101) ## [](#may-2020)May 2020 ### [](#new-features-15)New Features - Graph search provides enhanced search capability powered by the application network graph. - For Anypoint Platform instances hosted in the EU control plane, public portals prompt external users for read-only access to their basic profile information when they log in for the first time. This change is not yet released to the Anypoint Platform instances hosted in the US control plane or MuleSoft Government Cloud. - API Groups enable organizations to publish related APIs bundled into a single unit, and enable developers to learn about and request access to groups of related APIs as a single unit. - Exchange supports saving the asset description by using the Command+Return or Control+Enter keyboard combination. (EXC-3762) - Uploading an image with a file extension that does not match the file’s actual type shows a more descriptive error message. (EXC-5902) ### [](#fixed-in-this-release-17)Fixed in This Release - Exchange prevents using invalid sessions in private portals. (EXC-4828) - The **External** indicator displays with improved visibility when a user shares assets with an external organization. (EXC-5250) - Public portals correctly display asset icons to users who are not logged in. (EXC-5293) - Users see a warning if a public API’s instances are all private. (EXC-5367) - Saving a public portal customization draft works correctly in all cases. (EXC-5383) - Version groups with spaces or special characters work correctly in asset URLs. (EXC-5418) - In Anypoint Studio 6, Exchange correctly shows the status of installed connectors. (EXC-5445) - Exchange security prevents errors when using fetch manual redirection inside API notebooks. (EXC-5937) - The **Policies** asset type in the type filter no longer shows the label **New**. (EXC-6050) ## [](#april-2020)April 2020 ### [](#new-features-16)New Features - Client credentials are segregated across multiple identity providers (IdPs). In the Request Access dialog in Exchange, users select an API instance and then select or create a client application for the identity provider to which the instance belongs. - Exchange asset portals support WebP images. (EXC-3337) - Anypoint API Designer correctly publishes an asset to Exchange when the asset’s version group contains an underscore. (EXC-5927) ### [](#fixed-in-this-release-18)Fixed in This Release - Client management works correctly for organizations without a defined client management type. (EXC-3011) - In a public portal, changing the version group of an asset works correctly. (EXC-4009) - Publishing an asset version works correctly after a failed previous attempt. (EXC-5214) - The asset portal for an asset with the "SNAPSHOT" suffix on every version loads correctly. (EXC-5349) - Publishing a new asset using a token that belongs to a connected application works correctly. (EXC-5357) ## [](#march-2020)March 2020 ### [](#new-features-17)New Features - The Markdown editor toolbar’s header button supports multiple header sizes. (EXC-3033) - Users can perform a single step to create a new application, request access to an API instance for that application, and select a service level agreement (SLA) tier for that access. (EXC-5251) - All assets have consistent navigation by minor version, and asset properties such as tags, categories, custom fields, and Markdown content pages are consistent for each minor version. (EXC-5180) ### [](#fixed-in-this-release-19)Fixed in This Release - The API console renders endpoints in the correct order. (EXC-5308) - When the public portal login page background color is white, the **Sign up** button displays correctly. (EXC-4864) ## [](#february-2020)February 2020 ### [](#new-features-18)New Features - When users update the asset name, description, labels, or categories of a REST API, these properties are updated in the generated connectors. (EXC-4699) ### [](#fixed-in-this-release-20)Fixed in This Release - Exchange security prevents specific types of cross-site scripting attacks in the API console for OAS specifications by correctly escaping malicious user input. (APIC-361) - The request access feature prevents errors by ensuring a user selects an API instance before creating a new application. (EXC-5181) - Users can always log out without errors from an Exchange portal with a vanity domain. (EXC-4693) ## [](#january-2020)January 2020 ### [](#new-features-19)New Features - Cross-organization sharing enables a user to share an asset with their organization or an external organization and make the asset’s details viewable by all users of that organization. - Improved accessibility including keyboard accessibility for menus, filters, and other UI controls, and improved usability of API instances, sharing, deleting assets, and other application controls on screens with small resolutions. - Improved interface to request API access by showing the API instance selection menu and then the application selection menu, and showing the link to create a new application on the application selection menu. (EXC-4856) - The interactive API console is updated to include: - Latest web standards - WCAG 2.1 AA accessibility - New console elements for examples and annotations in documentation - Endpoints ordered in the UI, even when they are not ordered in the spec - Reduced time to initialize application - Request editor panel that only renders headers that are defined in the spec - Optimized performance for complex APIs ### [](#fixed-in-this-release-21)Fixed in This Release - Multiple issues in the interactive API console were fixed in this release. - Markdown pages display correctly for all content. (EXC-4950) - Exchange shows a message about the current search results only when search terms have been entered. (EXC-4848) - Exchange security prevents specific types of cross-site scripting attacks in API notebooks by correctly escaping malicious user input. (EXC-4781) ## [](#november-2019)November 2019 ### [](#new-features-20)New Features - Exchange public portal login pages reflect the public portal custom colors and logo and offer both standard Anypoint Platform login and optional single sign-on using a third-party identity provider. (EXC-4176) - Exchange supports terms and conditions pages for HTTP and SOAP API asset types. (EXC-3967) - Exchange shows that the review field is actionable, so a user can start a new review. (EXC-3962) ### [](#fixed-in-this-release-22)Fixed in This Release - Category values containing spaces work correctly in GraphQL queries. (EXC-4610) - Users can make requests to endpoints other than the mocking service in public portals that have custom non-MuleSoft domains, also known as vanity domains. (EXC-4617) - Public portals that use vanity domains correctly show customer favicons. (EXC-4577) - Exchange wraps long custom field values to display the complete value. (EXC-4573) - Requesting access to an API redirects the user to the correct login page, either the organization login or the Anypoint Platform login, as configured by the organization administrator. (EXC-4557) - Users can edit pages that were created before Exchange validated page names and that have page names containing restricted characters. (EXC-4259) - Categories with names containing `/` or `\` can be deleted. (EXC-3791) ## [](#october-2019)October 2019 ### [](#new-features-21)New Features - Exchange enhanced layout and readability for long names, page titles, API versions, organization names, and usernames in the asset portal. (EXC-4067, EXC-4068, EXC-4070, EXC-4071, EXC-4072) - The left navigation bar refers to the home page of the asset portal as "Home" and not as the asset name. (EXC-4069) - Exchange orders the HTML headers of the asset portal into correct document hierarchy for better accessibility. (EXC-3961) ### [](#fixed-in-this-release-23)Fixed in This Release - The request access modal displays the correct SLA tier for each API instance. (EXC-4389) - Exchange prevents UI crashes when customizing colors for public portals. (EXC-4386) - API access requests work correctly for all API version names. (EXC-4345) ## [](#september-2019)September 2019 ### [](#new-features-22)New Features - General accessibility is improved in several ways throughout the Exchange UI. (API Console is not changed, and will have accessibility improvements in a later release.) (EX-R-105) - Exchange provides enhanced site semantics and Accessible Rich Internet Applications (ARIA) attributes. - Exchange has skip links for users navigating the site with a screen reader and easier design for users navigating the site with a keyboard. - Exchange pages have better indicators of which page element has focus, and better keyboard controls for focus. - Exchange messages and dialogs about user errors are clearer and do not rely on color as the sole means of communicating information. - Users can publish new versions of Mule 3 connectors as Mule 4 extensions. (EXC-4227) - Improved placement of the **Publish new asset** button helps users to avoid publishing a new asset when searching for an asset. (EXC-3965) - The page editor expands to fit the browser window. (EXC-3964) - Exchange enforces consistency across all versions of the asset in the three version-agnostic properties of name, icon, and description. (EXC-3391) ### [](#fixed-in-this-release-24)Fixed in This Release - When a user is not logged in and requests access to an API from a public portal that has a vanity domain, Exchange directs the user to log in and does not show an error message. (EXC-4197) - Users are limited to writing only one review for each asset version so that they cannot manipulate the average ratings of assets by writing multiple reviews. (EXC-4179) - When Exchange loads images from external sites, the referrer headers do not reveal authorization codes. (EXC-4133) - Users can access and delete APIs that have API versions containing non-ASCII characters. (EXC-4130) - Exchange security prevents specific types of cross-site scripting attacks in API notebooks by disabling certain JavaScript functionality as described in [Document an Asset Using API Notebook](https://docs.mulesoft.com/jp/exchange/to-use-api-notebook). (EXC-4056) - Users can run the `exchange asset describe` command in the Anypoint CLI on all asset types. (EXC-4052) - Exchange security prevents certain types of cross-site scripting attacks on the public Exchange portal. (EXC-3727) ## [](#august-2019)August 2019 ### [](#new-features-23)New Features - The maximum number of values for each category increased from 200 to 500. (EXC-4066) - Exchange supports custom policies and enables users to browse, search, and filter policies. (EXC-3163) - Exchange prevents resource exhaustion attacks by limiting the number of asset versions that can be published. (INFOSEC-9354) ### [](#fixed-in-this-release-25)Fixed in This Release - Users can successfully import all API connectors to Anypoint Studio. (EXC-4075) - When a user deletes and re-uploads an API, the user sees the correct API console. (EXC-4073) - Anypoint Exchange prevents disclosure of an asset creator’s personal information. (EXC-4063) - Corrected permissions prevent Asset Contributors from deprecating an asset, which is allowed only for an Organization Administrator, Exchange Administrator, or Asset Administrator. (EXC-3980) - Logging in to a federated organization that uses an external client identity provider opens the organization’s private Exchange portal and not the public portal. (EXC-3959) ## [](#july-2019)July 2019 ### [](#fixed-in-this-release-26)Fixed in This Release - If your session expires, you can log back in with no authorization errors and no need to refresh the page. (EXC-3904) - You can delete assets that have many versions. (EXC-3850) - You can delete assets that have long API versions. (EXC-3849) - When you use Maven to request the latest version of an asset, Exchange returns the asset with correct metadata. (EXC-3580) - Exchange prevents you from uploading a file whose type is not allowed, even if its file extension is incorrect. (EXC-3399) ## [](#june-2019)June 2019 ### [](#new-features-24)New Features - Markdown editor supports toggling bold text. (EXC-3825) - Validation of user input in API Instances table improved. (EXC-3809) - Studio experience interface simplified to show only applicable links. (EXC-3759) - Both markdown editor and visual editor provide full control of heading levels. (EXC-3643) - Permissions errors prevented by making only viewable assets clickable in the asset dependencies table. (EXC-3607) - When you view assets by business group and select a different business group, you see the new group and not the root organization. (EXC-3430) - Validation of user tag entry improved. (EXC-3414) - When you click a category or tag, you see matching assets from all business groups and assets provided by MuleSoft. (EXC-3219) - If the server is at capacity and unavailable when you try to use an API, you see a descriptive error message. (EXC-2991) ### [](#fixed-in-this-release-27)Fixed in this Release - Edit mode does not show incorrect "Loading API" message. (EXC-3810) - Images uploaded after May 31, 2019 render correctly on the MuleSoft public portal. (EXC-3793) - Short and wide icons representing assets are correctly rendered in the UI. (EXC-3792) - Sharing an asset with a user while related assets are being generated shares the related assets as well. (EXC-3719) - When you use the mocking service through Exchange, it correctly recognizes headers and security schemas. (EXC-3711) - All users can always view images on custom pages in a public portal. (EXC-3669) - When you are editing one page, you can discard those changes and create a second page. (EXC-3642) - You receive an improved error message when you attempt to use Maven to publish a new version of a REST API created in Exchange with a different asset type, which is forbidden. (EXC-3511) - Exchange automatically revalidates the file when you upload a file to create a new asset and change the asset type. (EXC-3503) - Publishing through Maven correctly validates `groupId` and `assetId` values. (EXC-3361) - APIs published in the Public Exchange portal display the full RAML and OAS code. (EXC-3254) - Exchange preserves user input entered while the API Console is loading. (EXC-3024) - You can install the SSH connector when using Anypoint Studio 6. (EXC-3014) ## [](#may-2019)May 2019 ### [](#new-features-25)New Features - Improved readability of API instances when requesting API access, especially for long API instance names. (EXC-3636) - When using direct upload, provide relevant information about the files that should be uploaded for each asset type. (EXC-3427) - Users can now customize the order of the user-generated pages in the public portal. (EXC-3405) - Users can now add SVG images as resources for asset portals and public portal customization. (EXC-3350) - Exchange now [searches](https://docs.mulesoft.com/jp/exchange/to-find-info) properties defined in RAML and OAS API specifications and the full text of asset portal page content. Users no longer need to create complex tags and categories to enable finding assets, since they can now search the API docs and API specs in addition to name, categories, and tags. (EXC-2967) ### [](#fixed-in-this-release-28)Fixed in this Release - When creating a SOAP API, the "File URL" link is now validated. File URLs entered with no protocol before validation was enabled will be updated to default to `http`. (EXC-3641) - Users can use the mocking service to try the APIs available in public portals with branded domain names. (EXC-3585) - Prevent Exchange contributors and Exchange admins from changing the API name in the public portal, which should be a read-only view of the asset. (EXC-3568) - When accessing MuleSoft public assets, provide correct error information (401 instead of 404) to the Maven CLI so that Maven can retry the request with proper credentials instead of failing. (EXC-3520) - When an API version is made public, the visibility indicator in the API version drop-down in the asset portal reflects the correct state. (EXC-3513) - Remove orphan connectors when an API asset version is deleted. (EXC-3510) - Improve readability of portal page tables with long words. (EXC-3495) - Generate the correct mocking service URL for OAS API specifications. (EXC-3478) - Custom icons for an asset’s portal are now used in the dependencies table. (EXC-3471) - Tags are no longer overwritten with the previous asset version’s tags when updating the asset name. (EXC-3442) - Users can now upload assets using relative file paths in an `anypoint-cli` interactive session. (EXC-3423) - Unauthenticated access to portal images is disabled for images uploaded after this update. To disable unauthenticated access to an image uploaded before this update, download it, remove it, and [upload it again](https://docs.mulesoft.com/jp/exchange/to-describe-an-asset#add-an-image). (EXC-3394) - Prevent inconsistent asset type across multiple versions of an asset. (EXC-3392) - Making a version of an API public now depends on validation of that version and not on validation of uncompleted versions. (EXC-3336) - The browser back button now displays the correct pages in all cases. (EXC-3334) - Improve validation of the request body when creating contracts using the Experience API. (A contract is the link between a client application and an API instance.) (EXC-3021) ## [](#april-2019)April 2019 ### [](#new-features-26)New Features - Adding multiple tags to an asset is now easier. After a user types the tag and presses enter, a new tag is automatically started. (EXC-3431) - Exchange events, such as the most recent asset details page visited in Exchange, are now shown in the Recent Items list in the common Anypoint Platform navigation bar. (EXC-3264) - Users can now delete a draft of portal documentation. Previously users could only delete by editing the draft, removing all new edits, and publishing. When there were multiple changes in the draft, it could be difficult to tell which edits belonged to the draft and which to the old version. With the new option to delete a draft, users can have confidence that the right changes will be discarded automatically, preserving the original documentation content. (EXC-3116) - Added information messages when trying to create a page with an invalid name in the Asset Detail Page to explain why the validation failed and how the user can make the page name valid. (EXC-3041) - All policy URLs now have MuleSoft domains, so allowlists for API policies now require only MuleSoft URLs. No need to also add Amazon S3 URLs. (EXC-2680) - Users can now automate the publishing process by using the Command Line Interface (CLI) to upload RAML and OAS specifications to Exchange. (EXC-2539) ### [](#fixed-in-this-release-29)Fixed in this Release - Exchange now generates the correct representation of mocking service URLs for OAS specifications. (EXC-3478) - To prevent hackers from accessing the authorization token from the request header, the authorization token is no longer included in the request header in each request made with API Console. (EXC-3416) - Enabled filtering by asset type in the public portal. (EXC-3400, EXC-3390) - If the user creates a Terms and Conditions page to supplement their asset documentation page, the Terms and Conditions page is now visible at all times. (EXC-3383) - Added `jpeg` to the list of supported extensions for portal resources (`bmp`, `gif`, `ico`, `jpe`, `jpeg`, `jpg`, `png`, `svg`, `tif`, `tiff`, `webp`). (EXC-3351) - If the user selects the **API is behind firewall** option, navigates away, and returns, the selection is now remembered. (EXC-3335) - Provided guardrails to prevent users from creating more than 50 pages in the documentation of a single asset. This prevents wasting unnecessary resources to support an unlimited number of pages. (EXC-3157) - Prevented users from creating portal contents without an associated file when publishing API specifications. (EXC-2541) ## [](#march-2019)March 2019 ### [](#new-features-27)New Features - Enable customers to use the Try It panel for API instances that are behind their firewall. (EXC-3117) ### [](#fixed-in-this-release-30)Fixed in this Release - Links to websites outside the MuleSoft Public Exchange no longer show a blank page. (EXC-3172) - Dependency snippet in Public Exchange now shows up in focus, so users don’t have to scroll down and don’t fail to see the snippet dialog at the bottom of the page. (EXC-3166) - Accurate warning and error displayed when the user has reached the Maximum Page limit of 10 pages per portal in Public Portal. (EXC-3054) - There is no limit on the number of client applications or contracts visible to the user when the user tries to request access for an API or browses the client applications in the "My Applications" page. Previous limit was 200. (EXC-3017) - Enable customers to add custom headers in the Try It panel in the Exchange Portal API Console. (EXC-3008) - Maven dependencies for the test scope are no longer visible in the dependencies section in Exchange. (EXC-2624) - Correct error message when trying to publish an OAS 3 specification, since OAS 3 is not supported. (EXC-2552) - New error message reflects the correct information when an attempt is made to create a new asset with the same GroupID-AssetID-Version (GAV) as an asset deleted within the past 7 days. Error message changed from "Asset already exists. Choose another asset name or version." to "There is a deleted asset with the same version number. Try creating your new asset with a higher version number." (EXC-2484) - Validate that a published WSDL has either a WSDL file or a URL for a WSDL file, and not both. (EXC-2354) ## [](#february-2019)February 2019 ### [](#new-features-28)New Features - Syntax highlighting in asset description markdown content. (EXC-3226) - Faster contextual navigation with clickable tags and categories in asset details page. By clicking on a tag or category, Exchange triggers a search of all of the assets that contain that tag or category. (EXC-3227) - Easy drag and drop image upload on Exchange’s markdown editor. (EXC-3228) ### [](#fixed-in-this-release-31)Fixed in this Release - The organizationId field is mandatory when publishing assets through Exchange xAPIs. Previously not sending organizationId returned a misleading 404 (Not Found) error. Now not sending organizationId returns an accurate 400 (Bad Request) error. (EXC-3168) - Public portals that use vanity domains to promote their company domain name can now render the API Console. API Console enables users to explore the API spec and try it out. (EXC-3143) - When a user goes to edit mode from a page that does not exist in the draft, Exchange now opens the home page in edit mode without an error. (EXC-2992) - Maven Facade now returns user-friendly and relevant error message text and code when internal services fail to validate a Mule asset. (EXC-2911) - Previously exceeding the rate limit for the underlying authentication service returned a misleading 401 (Unauthorized) error. Now exceeding the rate limit for the underlying authentication service returns an accurate 429 (Too Many Requests) error. (EXC-2900) - Exchange now prevents users from uploading compressed (zip) files whose uncompressed contents will exceed the maximum allowed size limit. Users will receive a 413 (Payload Too Large) HTTP error. (EXC-2527) - Allow Cyrillic text in category names. (EXC-2461) ## [](#january-2019)January 2019 ### [](#new-features-29)New Features - Conversion from RAML to OAS 2.0 and from OAS 2.0 to RAML in the publication process. - Ability to download a REST API specification in either RAML or OAS 2.0 with identification of the "Generated" specification. - Direct upload of RAML and RAML fragments. - New API console experience. - Consistent API specification publication user interface between Exchange and API Manager. - Contextual view of RAML versions of API specifications and fragments in API designer from Exchange. ### [](#version-note)Version Note The Exchange versions have changed from version numbers to date versioning by year and month. ## [](#2-7)2.7 **October 2018** ### [](#new-features-30)New Features - Exchange provides root organization scope search and browse for all assets in a root organization, irrespective of which business groups users belong to. Users are no longer limited to finding assets within their own business group. - Vanity domain for public portals - Customers can now set their own domain name for their developer portal. This enables a more personalized and consistent branding experience, where you can use your own domain names. This also improves your search engine optimization(SEO) when your customers and users are searching for APIs that are specific to your domain. See [Public Portal Vanity Domain](https://docs.mulesoft.com/jp/exchange/portal-vanity-domain). - Limits on Custom asset files - Prevents users from uploading malicious file contents as Custom types. See [Create a Custom Asset](https://docs.mulesoft.com/jp/exchange/to-create-an-asset#create-a-custom-asset). ### [](#fixed-in-this-release-32)Fixed in this Release - (Asset Manager) When recalculating latest version, check if uncompleted versions are considered. (EXC-2749) - (Asset Reviews) Some ratings table columns have incorrect length. (EXC-2776) - (Exchange UI) Incorrect asset id placeholder in Exchange Manual Publication. (EXC-2731) - (Studio 6 and 7) Logout of Exchange shows "Session Expired". (EXC-2774) - Cannot customize Public portal with images that have names longer than 64 characters. (EXCP-753) - Customer bearer token is shared with Marketo API while navigating to Exchange. (EXCP-768) - Empty reply from server uploading large VDP file. (EXC-2748) - Enable Spec download in public portals for unauthorized users. (EXCP-745) - Exchange 1 vulnerability. (EXCP-758) - Exchange asset tile list not rendering well in IE. (EXCP-748) - Exchange repository is not referenced in API POM files. (EXC-2723) - Hide save search for public portals. (EXCP-744) - Mocking service URL is incorrect when baseUri in RAML points to a mocking service instance. (EXCP-774) - New REST API with invalid RAML shows `The uploaded file does not have a valid RAML format`. (EXC-2759) - Resolution of SE-9079. (EXCP-757) - Unrestricted upload of dangerous file types in `Creating an asset`. (EXC-2729) ### [](#version-note-2)Version Note The Exchange versions have changed from the 2.2.x to 2.x versions. ## [](#2-2-2)2.2.2 **September 2018** ### [](#new-features-31)New Features - REST Connect combines Mule 3 and Mule 4 connectors into one Exchange asset. As a result, all previous Mule 3 and Mule 4 RAML REST API Exchange assets now appear in a single REST API Exchange asset for the RAML specification. For more information, see [Converting a RAML to a Connector Using REST Connect](https://docs.mulesoft.com/jp/exchange/to-deploy-using-rest-connect). - Categories are available. Search lets you search for Categories. You can set Category values in the Settings menu in the left navigation area. See [To Manage Categories](https://docs.mulesoft.com/jp/exchange/to-manage-categories). - The Markdown editor supports HTML 5 tags. See the [Markdown Notes](https://docs.mulesoft.com/jp/exchange/to-describe-an-asset#_markdown_notes). ## [](#2-2-1)2.2.1 **April 2018** We are pleased to announce the general availability of the latest release of Anypoint Exchange. This release provides structured and flexible mechanisms to enable precise searching and categorization of assets, content in EU region, and many product improvements. ### [](#new-features-32)New Features - Managed categories to allow Exchange administrators and Organizations owners to create categories and group Exchange assets. - Exchange contributors can now organize assets into different groups to improve asset browsing and discovery. - Custom fields allow Exchange administrators and contributors to extend existing asset attributes through the API. - Ability to reorder pages on asset detail page. - Public content including Anypoint Connectors, Templates, and Examples is now available in Exchange EU. ### [](#fixed-in-this-release-33)Fixed in This Release - Add not null constraint to tag\_type in asset\_manager.asset\_tags. (EXCP-505) - API Console no longer throws XML parsing error while retrieving data. (EXCP-486) - API Console now handles special characters in resource names. (EXCP-474) - API Console now shows status code RAML example blocks. (EXCP-407) - APIs: Client ID no longer changes after updating an application. (EXCP-401) - APIs: Deleting the last version no longer causes errors in the API Summary page. (EXC-2339) - APIs: Download as RAML now downloads all versions of an API. (EXCP-453) - APIs: Exchange Experience API (xAPI) categories are now ordered by displayName. (EXCP-512) - APIs: Exchange Experience API (xAPI) no longer returns 404 when hard deleting a previously soft deleted asset. (EXC-2329) - APIs: Exchange now lists whether an API is public or private in the version drop-down menu. (EXCP-297) - APIs: GET now correctly retrieves configurations from the root organization using an OAuth token from a business group. This allows `GET /organizations/${notAMasterOrgId}/tags/categories/` configurations and returns the configurations from the corresponding root org. (EXCP-507) - APIs: Mocked RAML published to Exchange no longer causes errors. (EXCP-397) - APIs: PATCH - If fields don’t change, don’t display an error that existing tags use this configuration. (EXCP-528) - APIs: POST managed tags configuration now returns 409 for a wrong constraint name in the configuration. (EXCP-468) - APIs: PUT request responses are no longer duplicated. (EXC-2368) - APIs: RAML v0.8 dependencies now work correctly. (EXC-2213) - APIs: Safari browser use of the API Console now works correctly. (EXCP-428) - APIs: SOAP WSDL files opened in Anypoint Studio 7 now work correctly. (EXCP-136) - APIs: Visibility label in the right side details menu shows whether an API is Private or Public. (EXCP-169) - Business Groups: Renaming or deleting business groups now works correctly with Exchange. (EXC-2292 and EXC-2325) - Categories now works correctly for All Types. (EXCP-521) - Categories UI improvements. (EXCP-532) - Create Client Application no longer fails when an organization has client management and the user is not an admin. (EXCP-460) - Creating an Asset - Information menu typos are fixed. (EXCP-143) - Date now updates after modifying the asset\_mappings table in Asset Manager. (EXC-2206) - Delete: Exchange contributors can now delete draft pages they create. (EXCP-387) - Exchange logo: Clicking the Exchange logo in top navigation bar now redirects to the Exchange home page. (EXCP-133) - IE 11 no longer displays a big check mark over a drop-down menu such as in the Settings > Categories > Asset Types menu. (EXCP-523) - Managed tags by assets feature in the Exchange Experience API (xAPI). - Managed tags configuration UI service. (EXCP-508) - Managed tags now look up the tag configurations from the root organization. (EXCP-498) - Managed tags with list types that already exist had repeating elements. (EXCP-504) - Marketo secret key no longer displays. (EXCP-461) - OpenAM: Updating an application no longer creates new OpenAM OAuth client applications. (EXCP-402) - Pages: Page name input field position appears consistently. (EXCP-239) - Pages: Page order can now be changed. (EXC-2322) - PCE audit logs now handle HTTPS correctly. (EXC-2312) - Portals: Customization navbar now displays published pages only. (EXCP-138) - Portals: Editor buttons now work correctly in Markdown view. (EXCP-140) - Portals: Editor icons now display correctly in Firefox. (EXCP-145) - Portals: Empty display name in a tag configuration no longer throws an error. (EXCP-511) - Portals: Exchange Portals now correctly renders the HTML image tag in a table. (EXCP-436) - Portals: Login button now displays correctly in customized Public Portals. (EXCP-127) - Ratings: Exchange now shows the version of the asset you are reviewing. (EXC-812) - REST Connect now sends failure email messages to the correct region in which the error occurred. (EXC-2369) - Search by query now strips out the slash ('/') character in a text search, and indexes search terms for `or`, `and`, and `what`. (EXC-2233) - Version: Add runtime version in asset details. (EXCP-390) - Version: Exchange now displays the Mule Runtime version so that Anypoint Studio 7 users can choose only Mule 4 assets. (EXCP-130) ## [](#2-1-1)2.1.1 **January 2018** This release introduces an easy way to share searches across Business Group users and personalized saved searches for each Exchange user. We have also made various UI improvements and several bug fixes. ### [](#new-features-33)New Features - Saved search for organizations provides consistent search navigation to all business group users. - Personalized saved searches enables users to save their own frequently used searches. - Ability to copy images into the Exchange visual editor eliminates the need to serve images from outside Exchange. ### [](#compatibility)Compatibility Exchange 2.1.1 is compatible with Anypoint Studio version 6.4 and later. ### [](#fixed-in-this-release-34)Fixed in This Release - Add terms and conditions link doesn’t look good on low resolutions. (EXC-1841) - API Console cannot read property endpointUri of undefined error. (EXC-2190) - API Notebook doesn’t run in sequence. (EXC-2185) - API Notebook creating clients when in Markdown doesn’t work. (EXCP-129) - API Settings is not displaying the instances URLs. (EXC-2127) - Asset Admin sees the make asset public option. (EXCP-141) - Asset Manager tsquery operator characters cause a 502 if used in text search. (EXC-1479) - Asset-Manager the SQL query for the GET by :groupId: and :assetId: endpoint is slow for assets with approximately 27 versions. (EXC-2067) - Asset-Manager when an asset publication fails, but dependencies were saved, it ends up in an inconsistent state. (EXC-1993) - Asset-Manager when deleting an asset version, all asset permissions are removed. (EXC-1572) - Can delete an asset with contracts and instances. (EXCP-308) - Can’t create a new version of a WSDL. (EXC-2019) - Can’t delete Asset Version when API version is changed. (EXCP-325) - Can’t upload WSDLs with other files in the zip. (EXC-1865) - Change rate to review. (EXC-1847) - Console behavior of default values for query parameters. (EXCP-139) - Console error when authorizing for client credentials grant type. (EXCP-231) - Customization is not sending audit logs. (EXC-2089) - Customize navigation bar toggle icon. (EXCP-124) - Delete dialog shouldn’t allow send two DELETE requests to Exchange API. (EXCP-336) - Delete message doesn’t show dependents. (EXC-2040) - Dependency Resolver is not properly returning the list of assets that failed to be resolved. (EXC-2248) - Documentation files are not displaying in the console. (EXCP-123) - EU - Cannot create asset with files. (EXC-2211) - Exchange editor generates garbage characters if the text is enclosed in angle brackets. (EXCP-125) - Fix multi-line logs seen in Sumologic. (EXC-2234) - Go to existing application is not working. (EXC-2016) - GraphAPI - Getting only the last public version retrieves several assets. (EXC-2117) - Handle deleted user scenario. (EXC-2048) - IE-11 - Add image or link popup shows "undefined". (EXCP-128) - Knex throws error obtaining connections from pool in Asset Reviews Service. (EXC-2147) - Maven Facade returns some 403 from Asset Manager as 502 errors. (EXC-1576) - Maven Facade - 403 errors are always turned into 404. (EXC-1598) - Mocking Service is not working if baseURI has the old mocking service. (EXCP-331) - Optimize RAML parsing for API console. (EXCP-134) - Portal trying to load deleted API version. (EXC-2201) - Private instance is displayed in API Summary on public portal. (EXCP-335) - Query parameter limit with value 250 is ignored when retrieving applications from APIM. (EXCP-132) - RAML is downloaded twice to render API Console. (EXCP-313) - RAML Parser Error: Unable to parse RAML data. (EXCP-309) - RAML request panel shows incorrect URI parameter field. (EXCP-323) - Rating score is not recalculated when older version’s rating changes. (EXCP-137) - Request API Access Modal window looks weird in IE11. (EXCP-142) - Studio 7 examples import not working. (EXC-2225) - Update Tooltip in manual publication typo and new asset type. (EXC-1206) - Users with permissions across organizations are failing to authorize. (EXC-1610) - View mode changes when you select a saved search. (EXCP-384) - Visibility status is not refreshed after making an API public. (EXCP-333) - When Publishing to Exchange via Maven, if publication fails with Forbidden, an incorrect entry is created in the database. (EXC-1935) - when token expires before smart connector generation finishes, then the error can’t be sent. (EXC-1528) ## [](#2-1-0)2.1.0 **November 2017** We are pleased to announce the general availability of the latest release of Anypoint Exchange. This release enables Anypoint Platform users to publish and share APIs with developers inside and outside of their organizations. ### [](#new-features-34)New Features - Unification of Anypoint Exchange and API portals. Now all assets can be managed and shared through a single location. - Ability to create public portals for any APIs in Anypoint Exchange. - Rich documentation automatically generated for RAML or OAS specifications. - Interactive API use case validation through API Notebook. - Mocking service, which can be used to test API calls without implementing the API. - Ability to register clients and request access for APIs managed by Anypoint Platform. - Automatic indexing of API instances and endpoints via Exchange. - Sharing of APIs externally using Exchange portal. - Customization and branding features of Exchange portal. - HTML support for content inserted to a Markdown editor (limitations apply). ### [](#compatibility-2)Compatibility Exchange 2.1.0 is compatible with Anypoint Studio version 6.4 and later. ### [](#known-issues)Known Issues - EXC-2191: Unable to use API notebook button in the WYSIWYG mode. Click on the editor window first, and then press the Notebook button. - EXC-2188: API notebook creators are not able to specify the API endpoint when configuring a client. Update RAML base URI to update the endpoint used by API Notebook. - EXC-1510: My application page is not responsive. ## [](#2-0-0)2.0.0 **July 29, 2017** We are pleased to announce the general availability of the latest release of Anypoint Exchange. This product enables Anypoint Platform users to publish and access Mule-related content within their own organization increasing visibility and reuse. ### [](#compatibility-3)Compatibility Exchange 2.0.0 is compatible with Anypoint Studio version 6.3 and later. The new Anypoint Exchange 2 in Anypoint Platform offers a complete rework of Exchange with support for OAS and RAML 1.0 specifications, an improved user interface, a new editor supporting both Visual and Markdown text creation, and the ability to rate assets. ### [](#new-features-35)New Features Anypoint Exchange lets you: - Store all integration assets in one place in Exchange, such as best practices, integration patterns, API fragments, API specifications, examples, templates, and connectors. - Enrich portal content using the Visual editor and Markdown editor. - Quickly upload Open API specifications (Swagger) in Exchange which automatically converts to RAML for use across the Anypoint toolset. - Quickly upload WSDLs (SOAP APIs) in Exchange. - Consume and reuse all existing MuleSoft public content in Anypoint Studio and Design Center. - Collaborate with API owners and designers including the ability to comment and write reviews, ask questions, and provide feedback on each asset. - Share an asset within a business group with users outside of the business group to drive cross business organization collaboration. - Auto-generate a Mule 4.0 Design Center connector (using REST Connect) for any valid API specification for use within Design Center. - View a list of dependencies (API Fragments) for any API specification. - Version any asset published to Exchange. - View Dependency Snippet for connectors for use in Maven, Gradle, SBT, and Ivy. - Publish examples and templates using Studio 6.3 and later. ### [](#migration)Migration Exchange 1.7 is still accessible and will remain available for 90 days (as of July 29). None of the content on this old version of Exchange has been deleted. The URL for old Exchange is now [https://anypoint.mulesoft.com/exchange1/](https://anypoint.mulesoft.com/exchange1/). Existing customers with content on Private Exchange can also access the old Exchange using a link available on the Exchange 2.0 site. You can migrate the content to Exchange 2.0 using [migration instructions](https://docs.mulesoft.com/jp/exchange/migrate). ### [](#known-issues-and-limitations)Known Issues and Limitations - EXC-1140: Unable to type anything below an image in the Visual editor. Switch to Markdown editor to continue editing. - EXC-1253: Visual editor is not supported for use with Internet Explorer 11. Use the Markdown editor instead. - Searching by tag at the user interface only works for the latest asset version. - Admin user cannot delete reviews created by other users. - Rating is not refreshed when a version is deleted. - Unable to deprecate an asset. - EXC-1522: Incorrect error message when a user without Exchange Contributor permission within a Business Group tries to create an asset. - EXC-1269: In Firefox, when a token is expired and user tries to publish to exchange, it throws a 403 error page. Clear cookies for Anypoint Platform and try again. ## [](#1-7-1-private-cloud-edition)1.7.1 Private Cloud Edition **October 2016** This release provides new features and bug fixes for the Anypoint Exchange on-premises release. ### [](#features)Features These feature changes occurred between the previous Anypoint Exchange On-Premises version 1.4.1 (May 2015) and the current release: 1. Content ratings 2. Objects can now have the author’s name and photo 3. SOAP API (WSDL) support 4. Item type colors 5. Auto populating URI for new items 6. Auto resizing description container for editing 7. Access Management Organization ID 8. Business groups 9. Artifact states 10. Transition flows 11. Exchange roles 12. Private Exchange connectors can be installed in Studio 13. Audit log of all actions in a private Exchange 14. The RAMLs label was changed to REST APIs 15. The WSDLs label was changed to SOAP APIs 16. Requires Studio 4.2.0 and newer ### [](#changed-features)Changed Features The following features changed between versions 1.4.1 and 1.7.1: 1. Removed video caption field until a video URL is added. 2. Removed `/mulesoft` from a path. 3. Removed object amount limitation for private Exchanges. 4. Removed editing types within an organization. 5. Editing terms are now only available to Admin roles. ### [](#current-differences-with-the-cloud-version)Current Differences with the Cloud Version At the time of this release, the Anypoint Exchange cloud version is at 1.7.0. The only changes in the on-premises beta are the new REST APIs and SOAP APIs labels. ### [](#known-issues-2)Known Issues None. ## [](#1-7-1)1.7.1 **September 2016** This version of Anypoint Exchange fixes internal issues and provides these two updates: - The **RAMLs** label is changed to **REST APIs** - The **WSDLs** label is changed to **SOAP APIs** ## [](#1-7-0)1.7.0 **July 2016** This version of Anypoint Exchange provides new features and fixes. ### [](#features-2)Features - Connectors linked to from a private Exchange can now be installed in Anypoint Studio. - Audit Logs now provide Exchange Administrators with a log of all actions that occur in a private Exchange. ### [](#fixed-issues-5)Fixed Issues
Issue Description

EXCHANGE-1126

Scope drop-down now shows the Business Group Hierarchy on search and in publish/republish drop-down.

EXCHANGE-1125

Fix a bug on missing buttons when editing versions.

EXCHANGE-1115

Improve error messages and avoid data lost during validations.

EXCHANGE-1099

Scope drop-down now shows the Business Group Hierarchy on search and in publish/republish drop-down.

EXCHANGE-1073

Fix a bug showing the version header without data and saving an empty version.

EXCHANGE-1072

Changes the place of back to the list button.

EXCHANGE-1063

Fix the item and name inputs on IE when Create/Clone Artifact.

EXCHANGE-1006

Improve error messages and avoid data lost during validations.

EXCHANGE-872

Fix a bug showing the version header without data and saving an empty version.

EXCHANGE-809

Disables the video caption field until you add a video URL.

EXCHANGE-779

Add a ? next to itemID with more information.

EXCHANGE-778

Ad a ? next to itemID with more information.
## [](#1-6-2)1.6.2 **June 2016** This version of Anypoint Exchange provides bug fixes and improvements. ### [](#fixed-issues-6)Fixed Issues
Issue Description

EXCHANGE-869

Hide non-relevant calls to actions in Exchange UI when the user launches it from Studio

EXCHANGE-1038

Download and docs icons should match the 2.2.1 MuleSoft styles

EXCHANGE-1096

Fix issue with removing filter terms (tags) from search results when the tag filter is launched from the item detail page

EXCHANGE-1106

All link versions wrongly point to only to the first version of the artifact

EXCHANGE-1112

User needs to update page to see the download icon when adding versions on an artifact
### [](#improvements)Improvements
Issue Description

EXCHANGE-553

Simplify the artifact’s share URL by removing "/mulesoft" from the path

EXCHANGE-1086

MuleSoft tag should not be displayed for anonymous users

EXCHANGE-1087

The focus should return to the beginning of the list when the user returns to search results from the detail page

EXCHANGE-1088

Remove Exchange settings from Anypoint Platform Access Management

EXCHANGE-1094

Instead of displaying the main organization name, display "Master Organization" in the Publish/Republish dropdown

EXCHANGE-1104

Refactor how pre-defined search terms are treated in the backend to improve performance
## [](#may-2016)May 2016 This new version of Anypoint Exchange includes new features & functionality for addressing the viewing and publishing of artifacts across a hierarchical organization structure. Also within this version of Exchange aligns with the Anypoint Platform Styles and use of the new Nav Bar. ### [](#features-and-functionality)Features and Functionality The following sections describe the new features in this release. #### [](#visual-enhancements)Visual Enhancements Alignment with the Anypoint Platforms Styles and Integration with the latest Anypoint Platform Navigation Bar. #### [](#roles-for-exchange)Roles for Exchange Besides the existing Organization Owner, Contributor and Administrator Roles, a separate Viewer role was created. #### [](#new-state-and-flow-transition-of-an-artifact)New State and Flow Transition of an Artifact To address the movement of an artifact across a hierarchical structure, Exchange now provides new states for an artifact and also specific actions to be performed on them. #### [](#business-groups)Business Groups Business Groups are being incorporated in Exchange . This feature across with the Exchange Roles and the new state transition flow of an artifact provides: - Ability of Central IT (maybe the root organization) to create artifacts and make them available to all Lines of Businesses (business groups) - Ability of Central IT to locate artifacts published in a business group and make it available to the rest of the business - Ability of an LOB to publish artifacts for internal (to that business group) consumption #### [](#ui-and-ux-improvements)UI and UX Improvements New Filters and actions now support the new Business Groups, Artifacts States, and Transition Flows functionalities. #### [](#edit-types-removal)Edit Types Removal Edit Terms only available on root Organization for Admin and Owner Organization #### [](#api-changes)API Changes Before this release, Exchange used an internal Organization ID in the API resource, but this organization ID is replaced with the Access Management Organization ID to allow Business Groups. New endpoints are being incorporated in Exchange to work with Business Groups. New permissions are applied using the Business Groups hierarchy. #### [](#avoid-losing-user-data)Avoid Losing User Data When a session expires, Exchange prompts for credentials and completes the action. Exchange now displays a warning when a user tries to leave the edit page if there are unsaved changes. ### [](#removed-features)Removed Features - The object amount limitation for private tenants has been removed. The possibility to request to increase the object amount limit it’s already removed from the Exchange configuration in Anypoint Platform access management. - The possibility to edit types was removed, all organizations now share the same types. - The feature to edit terms can now only be enabled for users with Admin roles in root organizations. ### [](#architecture-changes)Architecture Changes - Split UI from backend in different servers and all the related changes to fulfill this Architecture change. - Update Node.js version to v4. ## [](#dec-2015)Dec 2015 ### [](#features-and-functionality-2)Features and Functionality This Anypoint Exchange release includes the following new features and functionality: - WSDL Support: At the moment WSDL type does not have a Studio integration, however WSDLs can be added and managed via web UI. - Visual enhancements such as new colors for item types and UX improvements. - Auto-populated URI when creating new items. - Automatically resizable description container when editing content. - Firefox and Internet Explore 11 bugs fixed. ### [](#dec-2015-known-limitations)Dec 2015 Known Limitations The version of the exchange available with the on-premises installation of the Anypoint Platform comes with an empty library of content, you must populate it with your own content. ## [](#may-2015)May 2015 ### [](#features-and-functionality-3)Features and Functionality This Anypoint Exchange release includes the following new features and functionality: - Ratings: All content has a rating associated to it. Users can rate only from Exchange in Anypoint Studio (Connectors need to be installed in Studio in order to rate them). Objects have their rating displayed only when they have two ratings or more. - Author: Objects can have the author’s name and photo. This can be used for partners or community contributors. This section is hidden if not filled out. - UI Refresh: Object type indicators have been improved . Text areas and button sizes have changed to improve readability ### [](#known-limitations)Known Limitations To access private content from Anypoint Studio, version 4.2.0 or newer must be used. ## [](#may-2015-private-cloud-edition)May 2015 Private Cloud Edition Version: 1.4.1 This Anypoint Exchange release includes these new features and functionality: - Create and publish private content: Choose between a variety of content types (templates, examples, connectors, and more) to add, describe your asset, and publish it in your organization’s exchange. Only the people you choose may have access to create and publish new content. - Search for content: Users within your organization can find the internally published content (as well as MuleSoft’s public content), increasing reuse and avoiding redundant work. Exchange Admins can customize search filters to make internal content easier to find. ### [](#known-issues-3)Known Issues Accessing private content from Anypoint Studio requires version 4.2.0 or newer. ## [](#february-2015)February 2015 ### [](#features-and-functionality-4)Features and Functionality This Anypoint Exchange release includes the following new features and functionality: - Create and Publish private content: Choose between a variety of content types (templates, examples, connectors, etc) to add, describe your asset and publish it in your organization’s exchange. Only the people you choose may have access to create and publish new content. - Search for Content: Users within your organization can find the internally published content (as well as MuleSoft’s public content), increasing the chance of reuse and avoiding redundant work. Exchange Admins can customize search filters to make internal content easier to find. - Seamless Anypoint Studio Integration: Access your private content seamlessly from Anypoint Studio. You can open templates or install connectors by opening Anypoint Exchange from Studio and logging into your Anypoint Platform account. ### [](#known-limitations-2)Known Limitations To access private content from Anypoint Studio, version 4.2.0 or newer must be used. ## [](#support)Support If you need help using the product, refer to the documentation for the [Anypoint Exchange](https://docs.mulesoft.com/jp/exchange/). If you have additional questions or want to report a problem, Contact MuleSoft. ## [](#see-also)See Also - [Anypoint Exchange](https://www.anypoint.mulesoft.com/exchange/) - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Exchange Release Notes Anypoint Exchange provides a user interface consisting of asset cards that you can filter and click to provide information on connectors, APIs, examples, templates, and custom assets. - [Exchange Release Notes](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes) - [Exchange 2 REST Connect Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/rest-connect-release-notes) ## [](#see-also)See Also - [Anypoint Exchange Guide](https://docs.mulesoft.com/jp/exchange/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Exchange Release Notes Anypoint Exchange provides a user interface consisting of asset cards that you can filter and click to provide information on connectors, APIs, examples, templates, and custom assets. The following release notes are provided for Exchange: - [Exchange Release Notes](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes) - [Exchange 2 REST Connect Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/rest-connect-release-notes) ## [](#see-also)See Also - [Anypoint Exchange Overview](https://docs.mulesoft.com/jp/exchange/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Monitoring Agent Installer Release Notes These release notes are for patches made to the Anypoint Monitoring agent installer.
If you update the Runtime Manager agent, you must execute the Anypoint Monitoring agent uninstall script and then re-install the Anypoint Monitoring agent.
## [](#august-19-2026)August 19, 2026 **Version 3.2.18.11** This 3.x version of the Anypoint Monitoring agent supports connections from apps in new cloud regions. To observe data from apps deployed to these regions, you must start with this version of the agent: - [Australia](https://au1.platform.mulesoft.com/monitoring) Cloud - [Canada](https://ca1.platform.mulesoft.com/monitoring) Cloud - [India](https://in1.platform.mulesoft.com/monitoring) Cloud - [Japan](https://jp1.platform.mulesoft.com/monitoring) Cloud For setup instructions, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). ## [](#june-26-2026)June 26, 2026 **Version 3.2.18.3** The 3.x version of the Anypoint Monitoring agent fixes an issue. Use of this version of the agent requires your apps to run on Mule runtime version `>=` 4.4.0-20230522.
Issue Resolution ID

Counts of inbound request metrics in Anypoint Monitoring custom dashboards and exported CSV data (AnypointMonitoringExport.csv) are now accurate.

W-22254890

For security purposes, this release updates SnakeYAML to version 2.0.

W-22933436
For information about the agent, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). ## [](#june-23-2026)June 23, 2026 **Version 3.2.16.3** The 3.x version of the Anypoint Monitoring agent fixes an issue.
Issue Resolution ID

The Failed to scrape Prometheus endpoint message no longer appears in logs for hybrid standalone deployments on Linux.

W-22798371, W-22508168
For information about the agent, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). ## [](#may-14-2026)May 14, 2026 **Version 3.2.16.2** The 3.x version of the Anypoint Monitoring agent fixes an issue.
Issue Resolution ID

Fixed an issue in Linux environments where strict requiretty policies caused a service restart loop that made sudo commands fail during background execution with root privileges. This update improves process ID (PID) operations and service management under systemd.

W-22437518, W-22358399
For information about the agent, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). ## [](#may-5-2026)May 5, 2026 **Version 3.2.16.0** The 3.x version of the Anypoint Monitoring agent fixes these issues:
Issue Resolution ID

Fixed a parsing issue where Anypoint Monitoring agent installer 3.x versions failed to recognize legacy Mule 3 default log patterns. The correlationID is now correctly extracted as a structured field.

W-20202127

Resolved an issue that broke Monitoring and Usage-Based Pricing (UBP) metrics when CloudHub reserved properties were incorrectly configured in customer applications.

W-15609934
For information about the agent, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). ## [](#march-5-2026)March 5, 2026 **Version 3.2.14.0** ### What’s New The 3.x version of the Anypoint Monitoring agent introduces: - Support for configuring the OTel collector’s internal telemetry log level during installation using the `-l` parameter. This feature is available on supported Linux and Windows operating systems. Accepted values are `info` (default), `debug`, `warn`, `error`, and `off`. Example (Linux): `# am/bin/install -l error` - Support for enabling tracing during installation using the `-g` parameter. This feature is available on supported Linux and Windows operating systems. Sets the port for tracing data that comes from Mule runtime (see [OpenTelemetry Support in Mule Runtime](https://docs.mulesoft.com/mule-runtime/latest/otel-support)). This parameter is disabled by default. Example (Linux): `# am/bin/install -g 4317` For information about the agent, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). ## [](#february-10-2026)February 10, 2026 **Version 3.2.12.5** ### What’s New The 3.x version of the Anypoint Monitoring agent introduces: - Support for multiple installations of the agent to a single Linux host - Updated service templates to support the new port configuration This release also includes a security update.
Issue Resolution ID

To address vulnerabilities reported in version 3.2.12.1, this release updates io.netty libraries to version 4.1.125.

W-20516811
For guidance, see [Install Multiple Agents to a Linux Host](https://docs.mulesoft.com/jp/monitoring/am-installing#install-multiple-agents). ## [](#november-6-2025)November 6, 2025 **Version 3.2.12.1** ### What’s New The 3.x version of the Anypoint Monitoring agent introduces these changes: - `sudo` access is no longer required to install Anypoint Monitoring agent _unless_ you’re installing the agent as a service. Installing as a service always requires `sudo` access. - The telemetry listening port is now configurable from the Anypoint Monitoring agent installer through a `-t` parameter. Example: `$ ./install -t 8889` (defaults to port `8888`) ## [](#september-3-2025)September 3, 2025 **Version 3.1.1.13** The 3.x version of the Anypoint Monitoring agent introduces an enhancement.
Issue Resolution ID

With the new anypoint.platform.config.analytics.endpoint.patterns property, define patterns for your dynamic endpoints, ensuring consistent normalization and clean, actionable analytics data.

W-15668536
For more information, see [Normalize API Paths for hybrid deployments](https://docs.mulesoft.com/jp/monitoring/am-installing#normalize-path) and [Normalize API Paths for CloudHub and CloudHub 2.0 deployments](https://docs.mulesoft.com/jp/monitoring/configure-monitoring-cloudhub#normalize-path). ## [](#august-20-2025)August 20, 2025 **Version 3.1.1.12** The 3.x version of the Anypoint Monitoring agent fixes these issues:
Issue Resolution ID

To improve the OTel collector’s functionality when running in service mode, Anypoint Monitoring now registers an internal DirectoryWatcher component as a service.

W-19256238

Anypoint Monitoring agent now supports encrypted passwords.

W-19016971
For more information, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). See also, [Related Documentation](#related-docs). ## [](#july-1-2025)July 1, 2025 **Version 3.1.1.10** The 3.x version of the Anypoint Monitoring agent fixes an issue:
Issue Resolution ID

The agent no longer throws this NullPointerException error: Cannot invoke "java.lang.Boolean.booleanValue()" because the return value of "com.mulesoft.dias.mule.agent.MuleAgentConfig.isTrafficInspectionEnabled()" is null."

W-18900814
For more information, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). See also, [Related Documentation](#related-docs). ## [](#may-16-2025)May 16, 2025 **Version 3.1.1.5** The 3.x version of the Anypoint Monitoring agent now supports Windows Server 2019. For more information, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). See also, [Related Documentation](#related-docs). ## [](#april-1-2025)April 1, 2025 **Version 3.1.1.0** The 3.x version Anypoint Monitoring agent is now available for supported operating systems. To enhance performance, security, and usability, the agent supports HTTP/HTTPS (instead of SOCKS5) and the OpenTelemetry (OTEL) standard (instead of Filebeat). Supported operating systems: - RedHat Enterprise Linux 9 - Ubuntu 20.04 Windows isn’t supported at this time. Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) and MuleSoft Government Cloud don’t support the agent for this version of the installer. For more information, see [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). See also, [Related Documentation](#related-docs). ## [](#september-19-2023)September 19, 2023 **Version 2.5.11.2** ## Fixed Issues
Issue Resolution ID

The log4j version is updated.

W-14089178
See also, [Related Documentation](#related-docs). ## [](#earlier-versions)Earlier Versions ### [](#june-13-2022)June 13, 2022 **Version 2.5.11.1** ## Fixed Issues
Issue ID

The Anypoint Monitoring agent now supports FIPS installation.

W-10973459
### [](#february-1-2022)February 1, 2022 **Version 2.5.11.0** ## Fixed Issues
Issue ID

Custom and inbound metrics stop updating after app redeployment to on-premises 3.9.x.

SE-23396
### [](#version-2-5-10-0-october-27-2021)Version 2.5.10.0 October 27, 2021 #### [](#whats-new-4)What’s New - You can now disable application log forwarding. ### [](#version-2-5-4-0-june-1-2021)Version 2.5.4.0 June 1, 2021 #### [](#fixed-issues-4)Fixed Issues - Fixed install script issues when two options are passed together, such as SOCKS proxy and skip agent installation. (SE-19554) - Fixed an issue in which inbound metrics did not appear in Anypoint Monitoring for applications deployed in a cluster. (SE-20977) ### [](#version-2-4-2-0-november-19-2020)Version 2.4.2.0 November 19, 2020 #### [](#enhancement)Enhancement Anypoint Monitoring now supports PCE 3.0. #### [](#fixed-issues-5)Fixed Issues - In the Anypoint Monitoring **Inbound Dashboards** page, the Response Time by Endpoint chart showed X instead of the resource URI. (SE-17307) - App logs were not sent to Log Search when the app was using an incompatible version of the commons-lang3 library. (SE-18329) - You could not install Anypoint Monitoring on hot-fix runtimes. - The enhanced API metrics were not sent to Anypoint Monitoring. ### [](#version-2-3-0-0-july-20-2020)Version 2.3.0.0 July 20, 2020 This release contains the following fixed issues: - Fixed an issue in which metrics were not recorded for a period of time after restarting app on UI in Server Group. (SE-16753) - Fixed an issue in which `filebeat.exe` locked log files, which prevented log files from being rotated. (SE-16160) - Added support for `RollingRandomAccessFileAppender` for Log4j. (SE-16003) - Fixed an issue in which the **Application Process CPU Load** graph displayed incorrect values. (SE-15911) ### [](#version-2-2-3-0-april-27-2020)Version 2.2.3.0 April 27, 2020 This release contains the following fixed issues: - Added support for Anypoint Visualizer properties configured from Runtime Manager Properties tab for Mule 4. (SE-14999) - Fixed the issue of not picking the modification for property values unless Mule Runtime is restarted. (SE-15543) ### [](#version-2-2-2-0-april-6-2020)Version 2.2.2.0 April 6, 2020 This release includes the following update: Header injection for Anypoint Visualizer is enabled by default for Mule 4. This release contains the following fixed issues: - Fixed a download connection error when the server is behind a proxy. (SE-15234) - Fixed an error about am module directory not found. (SE-15374) ### [](#version-2-2-1-0-february-10-2020)Version 2.2.1.0 February 10, 2020 This release contains the following fixed issues: - On Mule 4.x, JMX Publisher stopped creating JVM metrics after running for some time. (SE-14730) - This fix requires Runtime Manager agent 2.4.5+. - Outbound metrics erroneously included some internal calls. (SE-14055) - Some outbound metrics showed an incorrect response time of 24 hours. (SE-13973) - Improved endpoint normalization. (SE-12965) - Fixed error on deleting file after copy. (SE-14578) ### [](#version-2-2-0-0-december-19-2019)Version 2.2.0.0 December 19, 2019 This release contains the following fixed issues: - Metric logs stopped updating JVM and OS metrics on deployment failure. (SE-13917) - The Anypoint Monitoring agent was blocking threads. (SE-14121) ### [](#version-2-1-7-0-august-28-2019)Version 2.1.7.0 August 28, 2019 This release contains the following fixed issues: - Anypoint Visualizer is not showing inbound connections. (SE-12476) - Anypoint Monitoring `am` folder is recreated after uninstall. (SE-12769) - Inbound Metrics are missing for app in Anypoint Monitoring. (SE-12832) ### [](#version-2-1-6-0-august-6-2019)Version 2.1.6.0 August 6, 2019 This release contains the following fixed issues: - Log forwarding does not work for newly deployed app without Mule runtime restart. (SE-12605) - Uninstall script not removing files properly. (SE-12599) - No infrastructure metrics for certain applications. (SE-12473) - Analytics collector doesn’t allow to access message. (SE-12446) ### [](#version-2-1-5-0-july-15-2019)Version 2.1.5.0 July 15, 2019 This release includes the following update: - Install script no longer requires `-s ` parameter. This release contains the following fixed issue: - Log forwarding does not work with Anypoint Monitoring agent 2.1.4.0 in hybrid runtime. (SE-12410) ### [](#version-2-1-4-0-june-7-2019)Version 2.1.4.0 June 7, 2019 This release contains the following fixed issue: - High thread count in a clustered environment (SE-11772) ### [](#version-2-1-2-0-may-17-2019)Version 2.1.2.0 May 17, 2019 This release includes the following updates: - Added support for Mule 4.2.x and Runtime Manager agent 2.3.x. - Added support for Filebeat restart if configuration or certificates have changed. This release includes the following fixed issues: - Anypoint Monitoring with Multicast Cluster Setup (SE-11657) - Layer when deploying app from RM (SE-10374) - Fix NPE reported in Mule log at startup (SE-11483) - Some inbound request failures are not taken into account in Monitoring dashboards. (SE-10544) ### [](#version-2-1-0-0-march-26-2019)Version 2.1.0.0 March 26, 2019 This release includes support for the SOCKS5 proxy. For more information, see [Install the Anypoint Monitoring Agent](https://docs.mulesoft.com/jp/monitoring/am-installing). You can download the Anypoint Monitoring agent installer from [Anypoint Monitoring Agent Installer 2.1.0.0](https://s3.amazonaws.com/cdn-anypoint-prod/artifacts/monitoring-center-ui/app/hybrid/am-2.1.0.0.zip) or from the Anypoint Monitoring **Settings > Hybrid** page. ### [](#version-2-0-5-0-february-13-2019)Version 2.0.5.0 February 13, 2019 This release includes the following updates: - Added metrics for operating system - Added support for the following versions of Mule Runtime Manager agent: - 1.11.x - 1.12.x - 2.2.x You can download the Anypoint Monitoring agent installer from [Anypoint Monitoring Agent Installer 2.0.5.0](https://s3.amazonaws.com/cdn-anypoint-prod/artifacts/monitoring-center-ui/app/hybrid/am-2.0.5.0.zip) ### [](#version-2-0-4-0-february-11-2019)Version 2.0.4.0 February 11, 2019 This release includes the following updates: - Added support for Mule Runtime Manager agent version 2.1.8. - Added support for Mule runtime engine version 4.1.5. ## [](#related-docs)Related Documentation In addition to these release notes, see: - [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes) - [Update the Monitoring Agent](https://docs.mulesoft.com/jp/monitoring/am-installing#update-the-monitoring-agent.adoc) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/monitoring/) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Monitoring Release Notes ## [](#october-1-2026)October 1, 2026 Built-in dashboards in EU and US Clouds are now retired and replaced by [Anypoint Insights](https://docs.mulesoft.com/jp/monitoring/anypoint-insights). The **Classic Monitoring** sidebar in Anypoint Monitoring, which provided links to built-in dashboards and Anypoint Monitoring features that were also available from the enhanced view, is also retired. For mappings from built-in dashboards to Anypoint Insights, see [Chart Mapping from Built-in Dashboards](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#dashboard-chart-mapping). For more information, see [How long does Anypoint Monitoring retain application metrics?](#monitoring::am-faq.adoc#application-metrics-retention). ## [](#september-30-2026)September 30, 2026 Anypoint Monitoring introduces features on the new UK Cloud instance of Anypoint Platform. [UK](https://gb1.platform.mulesoft.com) Cloud: - **Insights**: [Anypoint Insights](https://docs.mulesoft.com/jp/monitoring/anypoint-insights) dashboards with metrics on apps and APIs [**Integration Intelligence**](#monitoring::integration-intelligence.adoc) is also accessible from Anypoint Insights. - [**Telemetry Exporter**](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) (Exports for third-party observability platforms) - [**Alerts**](#monitoring::alerts-hf.adoc) (Basic alert notifications) - [**Reports**](https://docs.mulesoft.com/jp/monitoring/reports) (Mule app performance and behavior) - **Log Management**: - [**Log Search**](#monitoring::logs-search-hf.adoc) (Mule app logs) - [**Log Points**](https://docs.mulesoft.com/jp/monitoring/log-points) (Real-time logs) - [**Raw Data**](https://docs.mulesoft.com/jp/monitoring/raw-data) (Downloads of archived log data) - **Others**: - [**Tools**](https://docs.mulesoft.com/jp/monitoring/tools) (Links to connectors on Anypoint Exchange that deliver notifications to external systems from Mule apps) - **Settings** (Setup pages for connecting apps deployed to [**CloudHub**](https://docs.mulesoft.com/jp/monitoring/configure-monitoring-cloudhub) and [**Hybrid**](https://docs.mulesoft.com/jp/monitoring/am-installing), on-premise deployments to Anypoint Monitoring) - **Quick Links** - [Functional Monitoring](https://docs.mulesoft.com/jp/api-functional-monitoring/) (API Functional Monitoring) ## [](#august-5-2026)August 5, 2026 Anypoint Monitoring introduces features on the new Australia Cloud instance of Anypoint Platform and other clouds. - [US](https://anypoint.mulesoft.com/monitoring) and [EU](https://eu1.anypoint.mulesoft.com/monitoring) Clouds: - [Raw Data](https://docs.mulesoft.com/jp/monitoring/raw-data) for downloading archived log data - [Australia](https://au1.platform.mulesoft.com/monitoring) Cloud - [Basic alerts](#monitoring::alerts-hf.adoc) - [Log search](#monitoring::logs-search-hf.adoc) - [Raw data downloads](https://docs.mulesoft.com/jp/monitoring/raw-data) - [Reports](https://docs.mulesoft.com/jp/monitoring/reports) - [Anypoint Insights](https://docs.mulesoft.com/jp/monitoring/anypoint-insights) - [Telemetry Exporter](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) ## [](#july-24-2026)July 24, 2026 Anypoint Monitoring enhances the Log Search experience across all Anypoint Platform clouds. ### What’s New [Log Search](#monitoring::logs-search-hf.adoc) now supports: - Viewing the top five values in each field - Adding or removing the field from the **Results** table - Filtering by any of the displayed values or, if the field contains more than five values, creating a search filter using **See More** On EU and US Clouds, Log Search has fully rolled out. The previous Log Search experience is no longer available from **Classic Monitoring** in Anypoint Monitoring. ## [](#july-10-2026)July 10, 2026 On US and EU Clouds, Anypoint Monitoring updates basic alerts. ### What’s New This update brings [Alerts](#monitoring::alerts-hf.adoc) into alignment on all clouds. ## [](#june-30-2026)June 30, 2026 Anypoint Monitoring releases new and updated features in all clouds. ### What’s New Anypoint Monitoring continues to bring features into alignment globally.
Feature US and EU Clouds Canada, Japan, and India Clouds

Log Points for generating logs for apps and APIs in real time without writing code

Updated

New

Raw Data for downloading archived log data

Not Updated

New

Tools for links to connectors on Anypoint Exchange that you can incorporate into a Mule app to deliver notifications to external systems

Updated

New

Settings pages for Mule apps running on supported hosts

Updated

New (CloudHub 2.0 and Runtime Fabric only at this time; both are enabled by default)
## [](#june-29-2026)June 29, 2026 On Canada and Japan Clouds, Log Search is now generally available (GA). ### What’s New - [Log Search](#monitoring::logs-jp-ca.adoc): This GA release enhances existing features and adds new ones, such as autorefresh, saved searches, and CSV downloads. ## [](#june-26-2026)June 26, 2026 On Canada and Japan Clouds, alerts are now generally available (GA). ### What’s New - [Alerts](#monitoring::alerts-jp-ca.adoc): This GA release adds filters by alert status, severity, and name. ## [](#june-17-2026)June 17, 2026 Anypoint Monitoring updates Telemetry Exporter on US and EU clouds. ### What’s New - [Telemetry Exporter](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter): In the EU and US clouds, Telemetry Exporter now aligns with the look and feel of Telemetry Exporter on other Anypoint Platform clouds. ## [](#june-15-2026)June 15, 2026 Anypoint Monitoring is thrilled to introduce features on the new India Cloud instance of Anypoint Platform and the addition of Integration Intelligence to more clouds. ### What’s New [India Cloud](https://in1.platform.mulesoft.com/login/) provides these Anypoint Monitoring features: - [Anypoint Insights](https://docs.mulesoft.com/jp/monitoring/anypoint-insights) dashboards for monitoring performance data and issues across your deployed Mule apps and API implementations - [Telemetry Exporter](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) for exporting telemetry data to third-party observability platforms like Azure Monitor, Splunk HEC, and OpenTelemetry-compliant tools - [Alerts](#monitoring::alerts-hf.adoc) for indicating whether your apps and APIs are behaving as expected or exceeding a defined threshold - [Reports](https://docs.mulesoft.com/jp/monitoring/reports) on app requests, performance, failures, CPU usage, and memory use - [Log Search](#monitoring::logs-search-hf-india.adoc) across your deployed apps [Integration Intelligence](#monitoring::integration-intelligence.adoc) is now available on India, Japan, and Canada clouds. You can also navigate to [Functional Monitoring](https://docs.mulesoft.com/jp/api-functional-monitoring/) (API Functional Monitoring) from Anypoint Monitoring on India cloud. For more information, see [Anypoint Monitoring の概要](https://docs.mulesoft.com/jp/monitoring/). ## [](#june-3-2026)June 3, 2026 Anypoint Monitoring releases enhancements to features in US, EU, Canada, and Japan cloud instances of Anypoint Platform. ### What’s New For Canada and Japan clouds, we’re excited to introduce an advanced monitoring capability: - [Reports](https://docs.mulesoft.com/jp/monitoring/reports): You can now review and export reports to track system metrics and performance over time. For US and EU clouds, we’ve updated features to optimize performance and align capabilities globally: - [Custom dashboard performance improvements](https://docs.mulesoft.com/jp/monitoring/dashboard-custom-config): Experience faster load times when configuring charts. To avoid lag time, a new **Refresh** feature loads long resource lists (such as application lists) on demand. - [Reports](https://docs.mulesoft.com/jp/monitoring/reports): This update ensures complete feature and parity with Reports in the Canada and Japan clouds. ## [](#may-22-2026)May 22, 2026 From May through June 2026, Anypoint Monitoring is rolling out an enhanced Log Search experience in US and EU instances of Anypoint Platform. This version replaces the traditional Log Search. For more information, see [monitoring::logs-search-hf.adoc](#monitoring::logs-search-hf.adoc). ## [](#march-31-2026)March 31, 2026 ### What’s New - Integration Intelligence now supports: - Logs on CloudHub deployments - Custom data spaces when setting up Integration Intelligence - Flex Gateway visualizations for dashboards For more information, see [monitoring::integration-intelligence.adoc](#monitoring::integration-intelligence.adoc). ## Fixed Issues
Issue Resolution ID

Now, only Salesforce administrators can turn on telemetry data ingestion for Integration Intelligence.

W-21436342
## [](#march-30-2026)March 30, 2026 ### What’s New Anypoint Insights dashboards introduce new charts and visualizations of metrics in EU, US, Japan (JP), and Canada (CA) cloud instances of Anypoint Platform. These app and API metrics bring Anypoint Insights dashboards into near parity with metrics displayed through the built-in dashboards in Anypoint Monitoring. - [New Application Metrics in Anypoint Insights](#app-visualizations) - [New API Metrics in Anypoint Insights](#api-visualizations) To compare built-in dashboard charts and visualizations with those now in Anypoint Insights, see [API Chart Mapping](#monitoring::api-dashboard.adoc#api-chart-parity) and [App Chart Mapping](https://docs.mulesoft.com/jp/monitoring/app-dashboards#app-chart-parity). For descriptions of Anypoint Insights charts and visualizations in app and API details pages, see: - [**Application Details**](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-apps) in Anypoint Insights - [**API Details**](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-apis) in Anypoint Insights ### [](#app-visualizations)New Application Metrics in Anypoint Insights Anypoint Insights adds charts and visualizations of application metrics in **Application Details** tabs: - App **Overview** tab: - No new charts or visualizations in this release - App **Request** tab: - **Inbound - Maximum Response Time by Endpoint** - **Request Volume by Protocol** - **Request Volume by HTTP Endpoint** - **Outbound Request Volume by Port** - **Outbound Request Volume by Remote Host** - **Outbound Request Latency** - **Outbound Request Volume by Operation** For more information, see [Request Metrics for a Mule Application](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-app-requests). - App **Errors** tab: - **Inbound - Response Time by Endpoint**, **Outbound - Response Time by Endpoint** - **Inbound - Request Count by Endpoint**, **Outbound - Request Count by Endpoint** - **Failed Mule Messages** For more information, see [Error Metrics for a Mule Application](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-app-errors). - App **Flows** tab (new in this release): - **Inbound - Response Time by Flow**, **Outbound - Response Time by Flow** - **Inbound - Requests by Flow**, **Outbound - Requests by Flow** - **Inbound - Response Time by Flow**, **Outbound - Response Time by Flow** - **Inbound - Requests by Flow**, **Outbound - Requests by Flow** - **Failures by Flow** For more information, see [Flow Metrics for a Mule Application](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-app-flows). - App **Connectors** tab (new in this release): - **Connector Message Volume** - **Response Time by Connector** - **Salesforce Requests**, **Salesforce Response Time**, **Salesforce Failures** - **Database Requests**, **Database Response Time**, **Database Failures** - **HTTP Requests**, **HTTP Response Time**, **HTTP Failures** - **Web Service Requests**, **Web Service Response Time**, **Web Service Failures** - **FTP Requests**, **FTP Response Time**, **FTP Failures** - **SFTP Requests**, **SFTP Response Time**, **SFTP Failures** - **SMTP Requests**, **SMTP Response Time**, **SMTP Failures** - **Object Store Requests**, **Object Store Response Time**, **Object Store Failures** - **Anypoint MQ Operations - Inbound**, **Anypoint MQ Response Time - Inbound**, **Anypoint MQ Failures - Inbound** - **Anypoint MQ Operations - Outbound**, **Anypoint MQ Response Time - Outbound**, **Anypoint MQ Failures - Outbound** - **Other Connector Requests**, **Other Connector Response Time**, **Other Connector Failures** For more information, see [Connector Metrics for a Mule Application](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-app-connectors). - App **JVM** tab: - **Classes Loaded**, **Classes Loaded Total**, **Classes Unloaded** - **JVM Uptime** - **Par Eden Space** , **G1 Eden Space** - **Par Survivor Space**, **G1 Survivor Space** - **Metaspace** - **Compressed Class Space** - **JVM Memory Code Cache**, **Code Cache** - **Tenured Gen**, **G1 Old Gen** For more information, see [JVM Metrics for a Mule Application](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-app-jvm). - App **Custom Metrics** tab: Monitor apps that use your organization’s custom metrics for a Mule application. Adjust settings of the charts that use your custom metrics. The **Custom Metrics** tab for an application appears in Anypoint Insights only if your organization has the Anypoint Integration Advanced package or a Titanium subscription to Anypoint Platform and the application you selected from Anypoint Insights is running on a supported version of Mule. For more information, see [Custom Metrics for a Mule Application](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-app-custom-metrics). ### [](#api-visualizations)New API Metrics in Anypoint Insights Anypoint Insights adds charts and visualizations of API metrics in **API Details** tabs: - API **Overview** tab: - **Total 4xx Errors** - **Total 5xx Errors** For more information, see [Overview Metrics for an API](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-api-overview). - API **Requests** tab: - No new charts or visualizations in this release For more information, see [Request Metrics for an API](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-api-requests). - API **Errors** tab: - No new charts or visualizations in this release For more information, see [Error Metrics for an API](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-api-errors). - API **Polices** tab (new in this release): - **Policy Violations by Path** - **Policy Violations by Outcome** - **Policy Violations by Policy** For more information, see [Policy Metrics for an API](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-api-policies). - API **Performance** tab: - **Request Latency by Endpoint** For more information, see [Performance Metrics for an API](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-api-performance). - API **Client Applications** tab: - **Request Volume by Location** For more information, see [Client Application Metrics for an API](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#entity-metrics-api-client-apps). ## [](#march-23-2026)March 23, 2026 ### What’s New Use Integration Intelligence to monitor, analyze, and troubleshoot your MuleSoft telemetry data directly in the Salesforce ecosystem and unlock the analytics engine for modern integration. Integration Intelligence, which is now generally available in the US and EU cloud regions only, includes enhancements since the beta release in November 2025: - Create custom dashboards in Integration Intelligence to monitor metrics for your Mule apps and APIs. Pinpoint inefficiencies, benchmark performance, and drive smarter optimization decisions. - Create custom visualizations from metrics belonging to the MuleSoft semantic model. - View app and API performance metrics in the built-in dashboards. - Select a time range for data displayed in the built-in dashboards and logs. - Get data from more deployment types (in addition to CloudHub 2.0 and Runtime Fabric): - CloudHub (dashboard metrics only) - Set up Integration Intelligence in a _default_ data space (not a custom data space at this time). Unsupported in this release: - Canada and Japan cloud regions - CloudHub deployments for logs - Flex Gateway visualizations for dashboards - Agentic assets (brokers, agents, and MCP servers) - Custom data spaces when setting up Integration Intelligence See [monitoring::integration-intelligence.adoc](#monitoring::integration-intelligence.adoc). ## [](#january-30-2026)January 30, 2026 ### What’s New In Canada Cloud and Japan Cloud instances of Anypoint Platform, Telemetry Exporter is now available to organizations with the Advanced subscription tier. Centralize observability with Telemetry Exporter by exporting audit log and trace data to your third-party monitoring ecosystem. Telemetry Exporter: [サードパーティ監視システムへのテレメトリーデータのエクスポート](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter). For information about subscription tiers, see [Anypoint Platform Packages and Plans](https://docs.mulesoft.com/jp/monitoring/#billing). ## [](#november-24-2025)November 24, 2025 ### What’s New Use Integration Intelligence (Beta) to efficiently monitor, analyze, and troubleshoot your data by bringing your MuleSoft telemetry data into the Salesforce ecosystem, unlocking the analytics engine for modern integrations. - Monitor metrics for your Mule apps and APIs in Integration Intelligence dashboards. - Troubleshoot Mule apps and APIs with Integration Intelligence logs. This Beta release supports **WARN**, **ERROR**, and **FATAL** log levels. - Get business insights into usage, flows, request volume, and policy violations in an Integration Intelligence dashboard. This Beta release supports these deployment hosts: - CloudHub 2.0 - Runtime Fabric Unsupported in this release: - CloudHub deployments - Flex Gateway APIs - Agentic assets (brokers, agents, and MCP servers) See [monitoring::integration-intelligence.adoc](#monitoring::integration-intelligence.adoc). ## [](#october-3-2025)October 3, 2025 ### What’s New As part of the Agent Fabric initiative on US and EU Clouds, Anypoint Monitoring now supports data from agentic assets (agent, broker, and MCP server instances) in these features: - Log Search adds support for logs from agentic assets. For more information, see [Get Logs for Agentic Assets](#monitoring::logs-search-hf.adoc#search-agentic). - Traces (Beta) now includes traces with spans for agentic assets. For more information, see [monitoring::traces.adoc](#monitoring::traces.adoc). - Metrics on agentic assets accessible from Agent Visualizer nodes are available in Anypoint Monitoring. For more information, see [monitoring::anypoint-insights-agentic.adoc](#monitoring::anypoint-insights-agentic.adoc). See [Agent Fabric](#general::learning-map-agent-fabric.adoc). ## [](#october-1-2025)October 1, 2025 ### What’s New In Canada Cloud and Japan Cloud instances of Anypoint Platform, Logs and Alerts are now available as an open beta release in the Advanced subscription tier. Any use of Anypoint Monitoring features in the beta state is subject to the applicable beta services terms and conditions. - Logs: [monitoring::logs-jp-ca.adoc](#monitoring::logs-jp-ca.adoc) - Alerts: [monitoring::alerts-jp-ca.adoc](#monitoring::alerts-jp-ca.adoc) Alerts configurations support Mule application and API metrics. For information about subscription tiers, see [Anypoint Platform Packages and Plans](https://docs.mulesoft.com/jp/monitoring/#billing). ## [](#april-30-2025)April 30, 2025 ### What’s New Anypoint Insights is now generally available (GA) in the US Cloud and EU Cloud instances of Anypoint Platform. Support for Anypoint Insights is available at these subscription tiers: - All subscription tiers in the US Cloud and EU Cloud instances of Anypoint Platform - Starter tier in the Canada Cloud and Japan Cloud (Hyperforce) instances For information about subscription tiers, see [Anypoint Platform Packages and Plans](https://docs.mulesoft.com/jp/monitoring/#billing). ## [](#march-18-2025)March 18, 2025 ### What’s New The Beta version of Anypoint Insights is now available to all subscription tiers in the US Cloud and EU Cloud instances of Anypoint Platform. From the list of entities in Anypoint Insights, you can open detailed metrics on specific deployments in Anypoint Insights dashboards instead of **Built-in dashboards**. Tiers that now include Anypoint Insights: - Starter usage-based tier - Gold and Platinum core-based tiers Support for Anypoint Insights continues at these tiers: - Advanced and Titanium tiers in the US Cloud and EU Cloud instances of Anypoint Platform - Starter tier in the Canada Cloud and Japan Cloud (Hyperforce) instances For information about subscription tiers, see [Anypoint Platform Packages and Plans](https://docs.mulesoft.com/jp/monitoring/#billing). ## [](#march-7-2025)March 7, 2025 ### What’s New The [Metrics API](https://docs.mulesoft.com/jp/monitoring/anypoint-insights#metrics-api) is available in this release. This API supports access to metrics displayed in Anypoint Insights charts. ## [](#december-9-2024)December 9, 2024 ### What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) - [Anypoint Insights](https://docs.mulesoft.com/jp/monitoring/anypoint-insights) is available for monitoring high-level performance metrics across your deployed Mule app and API implementations (_entities_) and for getting detailed metrics on specific entities. This feature is available in the Starter package tier on Canada Cloud and Japan Cloud. For US and EU clouds, this feature remains a Beta release available in the Advanced and Titanium tiers at this time. See [Anypoint Monitoring Packages and Plans](https://docs.mulesoft.com/jp/monitoring/#billing). - API Functional Monitoring is available from Anypoint Monitoring on Canada Cloud and Japan Cloud. For more information, see [Monitoring Features by Control Plane](https://docs.mulesoft.com/jp/monitoring/#features). ## [](#august-21-2024)August 21, 2024 ### What’s New - The basic view in the API analytics dashboard is deprecated. Use the default (enhanced) view to see detailed information about your APIs. - The **Inbound - Total Slow Requests by Endpoint** chart in built-in dashboards is deprecated. ## [](#may-30-2024)May 30, 2024 ## Fixed Issues
Issue Resolution ID

The data for the table that renders Average, Min, and Max Response Times by HTTP Endpoint (Inbound and Outbound) is now properly computed.

R-1160926

The data for Inbound and Outbound Average Response Time chart is now properly computed.

R-1160926
## [](#may-22-2024)May 22, 2024 ### What’s New - The Telemetry Exporter feature now supports [exporting traces](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) from Runtime Fabric apps to third-party observability and analytics apps. ## [](#march-6-2024)March 6, 2024 ### What’s New - The Telemetry Exporter feature now supports [exporting traces](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) from CloudHub 2.0 apps to third-party observability and analytics apps. ## [](#february-29-2024)February 29, 2024 ### What’s New - The [Telemetry Exporter](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) for [audit logs](https://docs.mulesoft.com/jp/access-management/audit-logging) enables you to export audit log data to third-party analytics and observability apps, such as Splunk HEC or Azure Monitor. The Telemetry Exporter is available only for organizations that have the Anypoint Integration Advanced package or a Titanium subscription to Anypoint Platform. - To enable Telemetry Exporter, two new [permissions](https://docs.mulesoft.com/jp/access-management/permissions-by-product#monitoring) are available: - Telemetry Exporter Administrator - Telemetry Exporter Configurations Manager ## [](#february-6-2024)February 6, 2024 ### What’s New - When you monitor a [connector that is compatible with Java 17](https://help.salesforce.com/s/articleView?language=en_US&id=000782248&type=1), you must specify the Java version. - Mule runtime engine 4.6.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ### Known Issues - The following charts in **Built-in Dashboards** for apps are currently unavailable for apps using Java 17: - Garbage Collection Count (CloudHub deployments only) - Garbage Collection Time (CloudHub deployments only) - ParNew Collection Count - ParNew Collection Time - Par Eden Space (Used, Maxed, Init, Committed) - Par Survivor Space (Used, Maxed, Init, Committed) - Code Cache (Used, Maxed, Init, Committed) ## [](#october-31-2022)October 31, 2022 - The Log Points and Reports features in Anypoint Monitoring are now supported for CloudHub 2.0. ## [](#july-28-2022)July 28, 2022 ### What’s New - Basic alerts for APIs are now available in MuleSoft Government Cloud. ## [](#april-28-2022)April 28, 2022 ### What’s New - Anypoint Monitoring supports built-in dashboards and alerting for APIs deployed through Flex Gateway. - Organizations with a Titanium subscription can use log management in Anypoint Monitoring for APIs deployed through Flex Gateway. - You can create basic alerts for APIs. Organizations that have a Gold or Platinum subscription can have up to six active API alerts per API instance. Organizations with a Titanium subscription can have up to ten active API alerts per API instance. ## [](#april-5-2022)April 5, 2022 ### What’s New - A Platinum subscription to Anypoint Monitoring is available in Mulesoft Government Cloud. For a complete list of supported Anypoint Monitoring features, see the **Platinum Subscription for Mulesoft Government Cloud Features** column in the [**Anypoint Monitoring Features** table](https://docs.mulesoft.com/jp/monitoring/#anypoint-monitoring-features). ## [](#december-7-2021)December 7, 2021 ## What’s New - In **Custom Dashboards**, advanced mode has two new metrics: - `disk_stats` - `operatingsystem` ## [](#november-9-2021)November 9, 2021 ## What’s New - The world map chart is now available for built-in dashboards with enhanced API metrics. In the **Client Application** section, the **Requests by Location** chart displays a world map that shows the number of requests per geographic location. ## [](#september-13-2021)September 13, 2021 ## What’s New - Anypoint Monitoring now has two product-specific permissions: Anypoint Monitoring Viewer and Anypoint Monitoring Administrator. - The Anypoint Monitoring Viewer permission enables a user only to view assets in Anypoint Monitoring. - The Anypoint Monitoring Administrator permission enables a user to view, create, modify, and delete assets in Anypoint Monitoring. - The **Overview** section of built-in API dashboards for enhanced metrics has two new charts. The **Total 4xx Errors** and **Total 5xx Errors** charts show the sum of all 400- and 500-errors respectively. ## Fixed Issues
Issue ID

In built-in dashboards, URLs previously contained an extra https.

MONITORING-4881

When creating alerts, servers had metrics but deployed apps did not appear in the list of servers, so you could not create alerts on these servers.

MONITORING-4839

Sorting alerts using the Name column was not working properly.

MONITORING-4850

Users could previously intercept an alert, modify the alert ID, and send it to other users.

MONITORING-4756, INFOSEC-17438

When you used an email link from a basic alert to access a dashboard or alert from an organization that was different than the organization you were logged in to, you were redirected to your own organization’s alert page. You are now prompted to log in to an account that is associated with the organization that sent the alert.

MONITORING-4662

When creating alerts, you could circumvent validation in the Recipient field and paste invalid emails.

MONITORING-4614

When you configured a custom dashboard and tried to select an API instance, a 408 error occurred.

SE-21708

When you configured a custom dashboard while using an on-premises deployment, available servers and applications did not load.

SE-22074
## [](#june-16-2021)June 16, 2021 ### [](#enhancements)Enhancements - Reports have a new column that specifies the `target name`, or location where the target is deployed, of the resource for which you are viewing a report. - The following charts were renamed: - **Inbound - Total Requests by Endpoint** is now **Inbound - Total Requests by HTTP Endpoint**. - **Outbound - Total Requests by Endpoint** is now **Outbound - Total Requests by HTTP Endpoint**. - Previously, in the **Custom Dashboards** API panel, APIs that did not support enhanced metrics did not appear. For enhanced usability, these APIs now appear in the API panel but are disabled. - The `${timestamp}` variable is now available in alert email templates. ### [](#fixed-issues-4)Fixed Issues - If you had previously chosen an environment when you accessed the **Reports** page, an error occurred when you tried to click **View**. - When you accessed the **Custom Dashboards** page and clicked **Configure**, the **Save** button appeared before you made any changes. - In **Custom Dashboards**, when you selected everything for an API Panel and changed to API Analytics Panel (deprecated), an error occured and your selections remained in each field. Because the metrics between API panels are different, your selections are now reset when you switch between API panel types. - Fixed an issue related to the `group by` for the **Inbound - HTTP Endpoints** chart. - Fixed an issue in which the **Inbound - Total Requests by HTTP Endpoint** and **Outbound - Total Requests by HTTP Endpoint** charts had empty cells. (SE-20663) - In the **Built-in Dashboards** page, when you viewed an API that supported both basic and enhanced metrics and then clicked the **Switch to basic metrics** link, the **Switch to basic metrics** link did not work. (SE-19796) - When you created a server alert, servers did not load automatically. - When you created an API panel in **Custom Dashboards**, if you selected everything, changed to advanced mode, and then switched back to simple mode, API selector tried to load indefinitely. - In **Custom Dashboards**, if you had two Runtime Fabric apps available that had the same name, there was an issue selecting the second one. (SE-20637) - When you used Safari to access built-in dashboards, the date picker did not work properly. (SE-20203) - When you used a link to **Log Search** that was shared by another user in the same organization, an error occurred if the query parameter in the URL was encoded: `The sharer organization is not the same as the active one.` You can now access log search after encoding query parameters in URLs. (SE-20282) - When you had multiple hybrid apps deployed to the same server, created a custom dashboard, and then selected the second app out of the hybrid apps deployed to that server as the **Resource**, your selection changed to the first app deployed to that server whenever you tried to reconfigure the panel. (SE-20453) ## [](#march-16-2021)March 16, 2021 ### [](#enhancements-2)Enhancements - Basic alerts now support email templates. You can populate the subject and message body of basic alert emails to include variables for the alert metric, condition, severity, and more. For a complete list of available variables, refer to the [basic alerts documentation](https://docs.mulesoft.com/jp/monitoring/basic-alerts#alert-variables). - The **Alerts** page now sorts alerts by the most recently updated. - When you use the Log Search feature, the logs that appear alongside the target log entry now load more quickly. SE-17024 - The **Connector Message Volume** chart tooltip has been enhanced to read **Number of outbound requests, grouped by connector type**. - The following charts have been renamed: - **Inbound - Response Time by Endpoint** is now **Inbound - Response Time by HTTP Endpoint**. - **Inbound - Endpoints** is now **Inbound - HTTP Endpoints**. - **Outbound - Ports** is now **Outbound - HTTP Ports**. - **Outbound - Protocols** is now **Outbound - HTTP Protocols**. SE-18756, SE-18909 - The following charts include enhanced queries for more accurate metrics reporting: - Inbound - Response Time by HTTP Endpoint - Inbound - HTTP Endpoints - Outbound - HTTP Ports - Outbound - HTTP Protocols - Outbound - Operations SE-18756, SE-18909 ### [](#fixed-issues-5)Fixed Issues - Fixed an issue related to timeouts while searching for surrounding logs. SE-17024 - Fixed an issue in which multiline logs in log searches resulted in multiple events. SE-18091 - In basic mode of custom dashboards for hybrid apps, you could not select applications other than the first application that appeared when you accessed the resource selector. SE-19604 - Fixed an issue related to ordering applications by name when you clicked the **Application Name** column in reports. - Fixed an issue related to deleting alerts while filters were enabled. ## [](#january-27-2021)January 27, 2021 ### [](#enhancements-3)Enhancements - Basic and advanced alerts now include a selection for user-defined severity. Note that when you modify existing alerts, you must assign a severity to that alert before you can save changes. - You can now sort and filter alerts by severity in the **Alerts** page. - When you create an alert and begin entering a value in the **Recipients** field, user emails associated with your organization that match the value you entered appear. ### [](#fixed-issues-6)Fixed Issues - When you had apps with the same name deployed to multiple Anypoint Runtime Fabric clusters: - Regardless of which instance of the app you selected, the same one always appeared. - The metrics associated with that app were combined. To accommodate this fix, built-in dashboard URLs have been enhanced to use the app’s ID to differentiate between instances of deployed apps. If you reload the page using the previous URL, the page will not load. (SE-19017) - The Inbound - Response Time by Flow chart erroneously displayed the same value for average, minimum, and maximum columns. (SE-19048) - The **Raw Data** page did not load for some Runtime Fabric users. (SE-18626, SE-19093) - The data for Inbound - Requests by Flow and Inbound - Response Time by Flow charts were swapped. (SE-18786, SE-19048) - In built-in API analytics charts, the following charts erroneously showed sums, instead of averages: - Average Response Time - Requests by Performance - Slow Requests (SE-17969) - General bug fixes and security enhancements. ## [](#december-14-2020)December 14, 2020 ### [](#fixed-issues-7)Fixed Issues Your environment now loads correctly during custom dashboard creation. ## [](#november-12-2020)November 12, 2020 ### [](#fixed-issues-8)Fixed Issues - If you had the same API deployed in two or more environments, the corresponding API widget label continued to show the first environment the API instance was deployed to, even after saving and reconfiguring the graph. - Infinite scrolling did not work in the list of alerts. - When using Anypoint Monitoring, the **Sign Out** button did not log you out of Anypoint Platform. - When you clicked a link in an alert email, some redirects did not work as expected. The link in the alert email now directs you to an error page if that link goes to: - A deleted dashboard - A dashboard that cannot be found - A dashboard that is in a different organization than the current active organization. ## [](#october-26-2020)October 26, 2020 ### [](#enhancement)Enhancement The resource and version selectors in the **Built-in Dashboards**, **Custom Dashboards**, **Alerts**, and **Log Points** pages contain information about the target and deployment type, if available. ### [](#fixed-issues-9)Fixed Issues - If you had two APIs with the same name but different targets, you could not differentiate which API was related to which cluster. The API names appeared without additional information. SE-15782. - When you searched for an API instance or version, the search feature did not suggest results based on the version. - When selecting assets to view in built-in dashboards, the supported runtime versions tooltip erroneously stated `Version 3.8.7-AM is supported for log search only`. All -AM runtime versions are deprecated. - In **Built-in Dashboards**, the **Inbound - Maximum Response Time** chart used the wrong query to populate the chart. ## [](#september-17-2020)September 17, 2020 ### [](#fixed-issues-10)Fixed Issues - Because of time zone conflicts, the selected date sometimes did not match the dates in the charts. - When you reconfigured a graph in custom dashboards, some of the application panel metrics changed to the first metric in the **Metrics** list. - You could not edit some basic alerts. ## [](#september-3-2020)September 3, 2020 ### [](#enhancements-4)Enhancements - You can now enable Anypoint Monitoring automatically for new applications that you deploy to CloudHub. This feature is enabled automatically for Titanium users. ## [](#july-30-2020)July 30, 2020 ### [](#enhancements-5)Enhancements - Anypoint Monitoring now supports Mule runtime versions 3.8.7 and newer. SE-16739 ### [](#fixed-issues-11)Fixed Issues - Searches for alerts by name were case-sensitive. - In the Custom Dashboards page, the tooltips for histogram charts did not display totals. SE-15270 - Email addresses were formatted incorrectly for alerts that had multiple email recipients. ## [](#july-7-2020)July 7, 2020 ### [](#fixed-issues-12)Fixed Issues - In custom dashboards, metrics changed when you edited content in the **General** tab. - In custom dashboards, adding widgets to a new chart cleared existing charts. - In built-in dashboards, the **JVM - Memory Utilization** chart is now named **JVM - Heap Total Memory**. - In built-in dashboards, the **Application Process CPU Load** chart is now named **System CPU % Utilization**. - In built-in dashboards, the **Application Process CPU Minutes** chart is now named **JVM CPU Time**. ## [](#june-29-2020)June 29, 2020 ### [](#new-feature)New Feature
This feature is currently available only for certain customers.
You can now quickly and seamlessly create basic alerts for app and server metrics. Basic alerts are available for the following metrics for servers or Mule apps: - For on-premises servers and CloudHub apps: - CPU utilization - Memory utilization - Thread count - For on-premises, Runtime Fabric, and CloudHub apps: - Message count - Message error count - Message response time ## [](#may-20-2020)May 20, 2020 ### [](#new-feature-2)New Feature You can now access the Anypoint Visualizer Troubleshooting visualization for an app in the **Application Network** section of the **Built-In Dashboards** page in Anypoint Monitoring. The **Application Network** section enables you to view direct callers and callees for a single app for the most recent seven days. ## [](#may-4-2020)May 4, 2020 ### [](#enhancements-6)Enhancements A new version of the Anypoint Monitoring Archive API is available. The Anypoint Monitoring Archive API allows you to retrieve API metrics that Anypoint Monitoring stores. You can [download this API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/) using Anypoint Exchange. This API is available only for users who have a Titanium subscription. ## [](#april-15-2020)April 15, 2020
IE 11 is not supported in Anypoint Monitoring.
### [](#enhancements-7)Enhancements - In the **Log Search** feature, you can now view how to correctly format a date with clickable examples. - The **Information** section of the built-in dashboards pages has word wrapping and hover text. - When you share a log by copying the URL, a message appears instead of a countdown. - Improved performance when switching between built-in dashboards, applications, or APIs. ### [](#fixed-issues-13)Fixed Issues - The **CPU Utilization** and **Memory Utilization** tabs of the Reports feature no longer include Cloudhub or hybrid deployments. - You could not add pre-Crowd APIs to built-in dashboards. - The **Requests by HTTP Policy Violation** chart did not display a name or ID. ## [](#march-26-2020)March 26, 2020 ### [](#enhancements-8)Enhancements - The **Log Search** page now has a refresh button. - New API metrics are provided: The **Built-in dashboards** page for APIs now has multiple tabs to show more information and enhance the root cause analysis for APIs. The new tabs include: **Overview**, **Requests**, **Failures**, **Performance**, and **Clients**. The user can switch between enhanced and basic metrics. ### [](#fixed-issues-14)Fixed Issues - A legend for built-in API dashboards was incorrect. ## [](#february-18-2020)February 18, 2020 ### [](#enhancements-9)Enhancements - For smoother navigation, the tabs on the **Built-in Dashboards** page appear in the same order whether the window is collapsed or expanded. - The built-in dashboard chart called **Total Requests by Type** is now **Total Requests by Response Type**. ### [](#fixed-issues-15)Fixed Issues - Using the Export CSV feature for a chart resulted in CSVs containing fractional values, which caused incorrect sums of metrics. SE-14652 - Using the `is between` and `is not between` operations with a timestamp filter did not work. - In advanced mode for custom dashboards, the API ID and API version ID were repeated. - If you clicked a URL in an email report from API Functional Monitoring to view the result of a test and you were not logged in to Anypoint Platform, the URL would open the login page. After you logged in, Anypoint Platform did not redirect you to the page you tried to access. - The notification switcher broke full-page scrolling. - The built-in dashboards refresh rate allowed you to refresh in increments smaller than one minute. - There was an invalid API instance value in the log-points selector. - The following API charts did not show correct data: - Requests (Avg) - Average Size of Requests - Average Size of Responses - When a query had one tag, aliases did not work correctly. ## [](#february-6-2020)February 6, 2020 ### [](#new-features)New Features The Log Points feature for apps, which requires a Titanium subscription, enables you to generate logs for apps and connectors without having to write code or redeploy the app. ### [](#enhancements-10)Enhancements To enhance readability, when you use the **View Surrounding Logs** feature in a log search, only five logs appear before and after the log you selected. ### [](#fixed-issues-16)Fixed Issues - When you used the same instance label on two or more APIs in different environments, the **api-version-id** list did not clarify which API resided in which environment. Now, the **api-version-id** list also shows the environment name. SE-14062 - The list of APIs in advanced mode on the **Custom Dashboards** page did not include all the available APIs. This issue has been resolved. SE-12532 ## [](#january-23-2020)January 23, 2020 ### [](#enhancements-11)Enhancements - When you search for logs, the **Quick Filter** section has an option called **See More** that further filters your search results. - If you are using an -AM runtime, the built-in dashboards page displays a deprecation notice. ### [](#fixed-issues-17)Fixed Issues - You could not delete saved searches in Log search. SE-13734 - When a long API instance name appeared on built-in dashboards, it exceeded the length of the selector and prevented you from clicking the underlying **View** button. - The organization name was missing in alert notification emails. - In the **Custom Dashboards** page, it was not possible to move charts using the mouse. - A typo was corrected on the **Log Points** page. - In the **Custom Dashboards** page, deleting a chart left an empty state image. - In the **Advanced Mode** section of the **Custom Dashboards** page, there is now a label indicating that it is not possible to add alerts in advanced mode charts. - Although users who do not have a paid subscription cannot export charts as CSVs, an **Export CSV** button appeared in chart options. - Nongraph charts in advanced mode showed a label stating that alerts were not supported. ## [](#december-7-2019)December 7, 2019 ### [](#enhancements-12)Enhancements To enhance usability, the following built-in dashboards have renamed charts: - Overview - Inbound - Outbound - Performance - Failures ### [](#fixed-issues-18)Fixed Issues - API built-in dashboards showed "No data points" despite API Manager showing incoming requests. SE-13181 - In the **Custom Dashboards** page, the **Advanced query options** menu did not populate with a complete list of APIs. SE-12532 - When you tried to view a log, an error would sometimes appear. SE-13931 - When you added a link with the `absolute` type to a custom dashboard, the link did not open. - When you added a link in a new or existing custom dashboard, the link redirected back to the dashboard until you refreshed the page. - When you tried to navigate from the **Reports** page to a hybrid app, the link for the hybrid app did not resolve. - In the **Built-In Dashboards** page, links on some charts did not resolve. ## [](#october-7-2019)October 7, 2019 This release contains the following new features for users who have a Titanium subscription: - The **Flows** built-in dashboard tab shows detailed information about each flow in a Mule application. - The **Connectors** built-in dashboard tab shows summary usage and performance information across all connector types. - The **Inbound** and **Outbound** built-in dashboard tabs contain new charts. This release also contains the following enhancements: - The Alert Email template includes additional contextual information. - The `Share` command in log search has been enhanced. This feature requires a Titanium subscription. - Log-point configuration feedback is improved. ## [](#june-18-2019)June 18, 2019 This release contains the following enhancement: The retention period for Anypoint Monitoring API analytics increased to 90 days for Gold and Platinum subscriptions. ## [](#june-12-2019)June 12, 2019 Anypoint Monitoring support for Mule 3.9.x-AM and Mule 4.x-AM is being deprecated. Update your applications to run on Mule versions 3.9.x and 4.x for better functionality and improved performance, and to receive the latest patch updates as soon as they are available. If you currently have Anypoint Monitoring enabled for applications running Mule 3.9.x-AM or 4.x-AM, monitoring continues to work, but you will not receive important patch updates. For information about setting the runtime version for your Mule app and enabling monitoring, see [Configure and Enable Anypoint Monitoring for Mule Apps](https://docs.mulesoft.com/jp/monitoring/configure-monitoring-cloudhub). ## [](#may-4-2019)May 4, 2019 This release contains the following new features and enhancements: - Support for hybrid and CloudHub apps running on Mule 4.2.0 - A **Custom Metrics** page from which you can easily access the [custom metrics connectors](https://docs.mulesoft.com/jp/monitoring/anypoint-custom-metrics-connector) for Mule 3 and 4 - Support for these [connector metrics](https://docs.mulesoft.com/jp/monitoring/monitor-connectors): - FTP - SFTP - SMTP - Object Store - Anypoint MQ - Metrics for inbound Mule messages on the **Overview** and **Performance** tabs ## [](#april-30-2019)April 30, 2019 Anypoint Monitoring for applications deployed to Runtime Fabric is now supported. Monitoring is enabled by default, so you don’t need to set anything up in Anypoint Monitoring. For more information, see [Monitoring Applications Deployed to Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-monitor-applications). ## [](#april-6-2019)April 6, 2019 An enhanced Monitoring agent is now included in CloudHub runtime versions 3.9.0, 3.9.1, and 3.9.2. ## [](#march-27-2019)March 27, 2019 The following features now support CloudHub apps running on Mule 4.1.x: - Custom Metrics - Connector monitoring ## [](#march-23-2019)March 23, 2019 ### [](#new-features-2)New Features This release contains the following new features: 1. You can save built-in dashboards as custom dashboards, which simplifies the process of building custom dashboards and allows you to leverage the features and flexibility available in custom dashboards. For more information, see [Save a Built-in Dashboard as a Custom Dashboard](https://docs.mulesoft.com/jp/monitoring/save-builtin-dashboard-as-custom). 2. In built-in and custom dashboards, you can export data for an app into a CSV file. For more information, see [Export App Data to a CSV File](https://docs.mulesoft.com/jp/monitoring/export-app-data-to-csv). ### [](#enhancements-13)Enhancements This release contains the following enhancements: - In addition to enabling monitoring for apps deployed to CloudHub and running on Mule 3.9.2, you can enable monitoring for apps running on the following Mule versions: - 4.1.5 - 4.1.4 - 4.1.3 - 4.1.2 - 4.1.1 - 3.9.1 - 3.9.0 For more information, see [Enable Monitoring for Mule Apps Deployed to CloudHub](https://docs.mulesoft.com/jp/monitoring/configure-monitoring-cloudhub) - The sidebar menu in Anypoint Monitoring is restyled to make navigation more intuitive. ### [](#fixed-issues-19)Fixed Issues - General bug fixes. ## [](#february-22-2019)February 22, 2019 The following new charts are available in the built-in dashboards: - Inbound - Maximum Response Time - Infrastructure - System Memory - Application Process CPU Load - Application Process CPU Minutes - Operating System Swap Space - JVM - Committed Virtual Memory For more information about built-in dashboards, see [Built-in Application Dashboards](https://docs.mulesoft.com/jp/monitoring/app-dashboards). ## [](#february-16-2019)February 16, 2019 - You can now monitor Web Services connectors in the **Connectors** tab. For more information about monitoring connectors, see [Monitor Connectors](https://docs.mulesoft.com/jp/monitoring/monitor-connectors). - You can now visualize custom metrics in real time using the built-in **Custom metrics** dashboard. For more information, see [Anypoint Custom Metrics Connector](https://docs.mulesoft.com/jp/monitoring/anypoint-custom-metrics-connector). ## [](#february-7-2019)February 7, 2019 The Anypoint Monitoring log points feature now supports the following API types and versions: - Basic endpoint APIs (CloudHub and hybrid) - CloudHub - Hybrid - Endpoint with Proxy APIs - CloudHub proxy - Hybrid proxy - Mule 3 versions 3.8.5 and later - Mule 4 versions 4.1.1 and later See [Log Points](https://docs.mulesoft.com/jp/monitoring/log-points) ## [](#january-12-2019)January 12, 2019 This release contains the following new features: - **Custom Dashboard API Support** - When you configure a custom dashboard and then work in Basic Mode, you can choose between an Application Panel and an API Panel to create dashboards to visualize API metrics. - In Advanced Mode you can add queries based on API metrics. ## [](#december-15-2018)December 15, 2018 This release contains the following new features: - **API Analytics** - API Analytics is now available in Anypoint Monitoring. See [Builtin API Analytics Dashboard](https://docs.mulesoft.com/jp/monitoring/api-analytics-dashboard). - **Anypoint Custom Metrics Connector** - (Requires a Titanium subscription) The Anypoint Custom Metrics connector enables sending metric values with dimensions to Anypoint Monitoring, where they can be visualized in real time using Custom Dashboards. See [Custom Metrics Connector](https://docs.mulesoft.com/jp/custom-metrics-connector/latest/). ## [](#december-8-2018)December 8, 2018 This release contains the following new features: - **Log Points** - (Requires Titanium subscription) You can generate logs for a running API without writing any code or redeploying your application. You can select specific parameters within the API for which to generate logs, for example, the request header `host` parameter. For more information about log points, see [Anypoint Monitoring Log Points](https://docs.mulesoft.com/jp/monitoring/log-points) - **Connector-level Flow Analysis** - (Requires Titanium subscription) You can now monitor the performance for connectors. For more information about monitoring connectors, see [Monitor Connectors](https://docs.mulesoft.com/jp/monitoring/monitor-connectors) ### [](#known-issues-2)Known Issues The Anypoint Monitoring log points feature is only supported on Mule runtime engine version 3.8.5-AM or later. For APIs not running on Mule runtime engine 3.8.5-AM or later, the log points feature does not appear for the API. Because you can’t select the runtime version when you deploy an API from API Manager, you must navigate to Runtime Manager, select the runtime version (3.8.5-AM or later), then redeploy the API.
Mule runtime engine versions appended with -AM are listed in Runtime Manager, in the Runtime Version menu under Show old patch releases.
### [](#fixed-issues-20)Fixed Issues - General bug fixes. ## [](#version-1-05)Version 1.05 ### [](#new-features-and-enhancements)New Features and Enhancements - Environment-wide reporting on application performance, including requests, failures, CPU and memory utilization. (Requires a Titanium subscription) - Performance Improvements - All static resources are stored on a content delivery network (CDN). - Resources are prefetched on page load. - Changes to built-in dashboards load more quickly. - Extended connection pools life before timeout. - Improvements to Deployment and Management: - New capabilities to associate an Organization with an environment so that you can build proofs of concept (POCs) without relying on engineering work. - Provisioning Configuration Management: Allows for changes to the data sources without requiring a new deployment. Versioning to allow controlled roll out. - Log Orchestration Service updates periodically from the Provisioning System: allows the creation of an Organization log index without requiring a deployment. - Admin console now exposes data from Provisioning: it allows easier visualization and editing of the environment properties. - Minor user experience (UX) improvements. - Log search share URL. ### [](#fixed-issues-21)Fixed Issues - General bug fixes. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Monitoring Release Notes - [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes) - [Anypoint Monitoring Agent Installer Release Notes](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes) ## [](#see-also)See Also - [Anypoint Monitoring Documentation](https://docs.mulesoft.com/jp/monitoring/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint MQ Connector Release Notes for Mule 4 Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Anypoint MQ (Anypoint MQ Connector) enables you to add messaging access to Anypoint MQ queues and exchanges from Anypoint Studio applications. Anypoint MQ Connector versions 4.x, 3.x, and 2.x work only with Mule 4.x and Studio 7.x.
Anypoint MQ Connector version 3.x receives updates for bug fixes and security patches only. For the latest features and enhancements, upgrade your connector to the latest 4.x version.
Guide: [Anypoint MQ Connector User Guide](https://docs.mulesoft.com/jp/anypoint-mq-connector/latest/) ## [](#4-0-23)4.0.23 **August 26, 2026** ### What’s New - The Anypoint MQ subscriber now recovers automatically from a broker connectivity loss. Previously, if connectivity dropped during message acknowledgement, the subscriber could stop consuming and remain stopped until the Mule application was restarted. The subscriber now implements the runtime’s reconnection contract and re-establishes its connection per the configured reconnection strategy, resuming consumption without manual intervention. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-22)4.0.22 **August 17, 2026** ### What’s New - The internal Anypoint MQ REST client is upgraded to a build that declares its Apache-2.0 license in the artifact POM. Earlier builds published without a license declaration, which caused some dependency scanners (for example, JFrog Xray) to quarantine the artifact as unknown license. There is no functional or behavioral change to the connector. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-21)4.0.21 **July 21, 2026** ### What’s New - The internal Anypoint MQ REST client is upgraded to a spring-core-free build to address reported security vulnerabilities (CVE-2025-41249 and CVE-2024-38816). Retry and backoff behavior is unchanged. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-20)4.0.20 **July 8, 2026** ### What’s New - The polling strategy for the Subscriber source now supports backpressure, which paces message retrieval to match your flow’s processing capacity. When enabled, the Subscriber source fetches new messages only when capacity is available and releases capacity when a message finishes processing. Backpressure is opt-in and disabled by default. To enable it, set the `anypoint.mq.subscriber.backpressure.enabled` system property to `true`. For more information, see [Backpressure and Max Concurrency](https://docs.mulesoft.com/jp/anypoint-mq-connector/latest/anypoint-mq-listener#backpressure-and-max-concurrency). ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-16)4.0.16 **May 20, 2026** ### Fixed Issues
Issue Resolution ID

A packaging defect introduced in 4.0.15 that caused applications to fail to deploy with a class loader error is now resolved. This version includes the same vulnerability fixes as 4.0.15.

W-22553120
### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-15-deprecated)4.0.15 (Deprecated) **May 19, 2026** This version is deprecated. Upgrade to 4.0.16. ### Known Issues
Known Issue Workaround ID

Applications fail to deploy with java.lang.IllegalStateException and NoSuchFileException: …​/META-INF/maven. The consumable artifact published to Exchange contains a malformed pom.xml. The source in Nexus isn’t affected.

Upgrade to 4.0.16.

W-22553120
## [](#4-0-14)4.0.14 **October 20, 2025** ### What’s New - Anypoint MQ Connector and MQ REST client licensing information is updated to CPAL v2.0. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-13)4.0.13 **May 29, 2025** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Anypoint MQ Connector upgrades dependencies to address reported security vulnerabilities (CVE-2024-38808 and CVE-2023-20863).

W-17873558

OAuth token calls now include a requestId to improve tracking and debugging of authentication requests.

W-18343528

Buffer is full, skipping message fetch errors no longer occur when using the Anypoint MQ Connector with prefetch=1 and maxConcurrency=1. Previously, these settings caused message consumption to stop until the application restarted, because competing processes held the buffer resource without releasing it.

W-15572531

Anypoint MQ subscriber throughput now improves when using prefetch=1 and maxConcurrency=1. Previously, message consumption slowed under these settings, reducing overall processing performance.

W-15513498
## [](#4-0-12)4.0.12 **November 13, 2024** ### What’s New - The `commons-io` library is upgraded to version 2.14.0 to address reported security vulnerabilities (CVE-2024-47554). ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

To facilitate troubleshooting, Anypoint MQ Connector now logs the lock ID by default when receiving messages.

W-16770759

The commons-io library is upgraded to version 2.14.0 to address reported security vulnerabilities (CVE-2024-47554).

W-16984485
## [](#4-0-11)4.0.11 **September 20, 2024** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

A concurrency issue that sometimes caused the Subscriber to throw a NullPointerException error while calling the Destination.getName() method no longer occurs.

W-16600995
## [](#4-0-10)4.0.10 **August 16, 2024** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues This release includes only non-user-impacting changes. ## [](#4-0-9)4.0.9 **August 12, 2024** ### What’s New - Anypoint MQ Subscriber performance is improved. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-8)4.0.8 **June 10, 2024** ### What’s New - The com.google.guava:guava 30.0-jre library is upgraded to version 32.0.1-jre to address reported security vulnerabilities (CVE-2023-2976). ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.google.guava:guava 30.0-jre library is upgraded to version 32.0.1-jre to address reported security vulnerabilities (CVE-2023-2976).

W-15695673
## [](#4-0-7)4.0.7 **May 10, 2024** ### What’s New - Anypoint MQ Connector 4.0.7 supports cross-region failover for standard queues. For information, see: - [mq::mq-failover.adoc](#mq::mq-failover.adoc) - [アプリケーションでのクロスリージョンフェールオーバーの設定](https://docs.mulesoft.com/jp/anypoint-mq-connector/latest/anypoint-mq-failover) ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
## [](#4-0-6)4.0.6 **February 5, 2024** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This connector is now compatible with Java 11.

W-14954942
## [](#4-0-5)4.0.5 **February 1, 2024** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 17
### Known Issues
Known Issue Workaround ID

Beginning with Anypoint MQ Connector version 4.0.4, Anypoint Studio versions (for example, v7.16) configured with Java 11 as the default report that the connector doesn’t support Java 11.

Update the connector to version 4.0.6 or later if you need Java 11 support.

W-14954942
For additional known issue information about this product, see [Known Issues](https://help.salesforce.com/s/issues). ## [](#4-0-4)4.0.4 **January 23, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 17
### Fixed Issues
Issue Resolution ID

The consumer/subscriber no longer recasts integer values to double values when it retrieves the message.

W-13721361
### Known Issues
Known Issue Workaround ID

Beginning with Anypoint MQ Connector version 4.0.4, Anypoint Studio versions (for example, v7.16) configured with Java 11 as the default report that the connector doesn’t support Java 11.

Update the connector to version 4.0.6 or later if you need Java 11 support.

W-14954942
For additional known issue information about this product, see [Known Issues](https://help.salesforce.com/s/issues). ## [](#4-0-3)4.0.3 **April 19, 2023** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Spring Framework dependency is updated to 5.0.10 to fix reported security vulnerabilities (CVE-2018-15756).

The com.google.code.gson:gson dependency is updated to 2.8.9 to fix reported security vulnerabilities (CVE-2022-25647).

W-12717888
## [](#4-0-2)4.0.2 **February 27, 2023** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now correctly supports the / character in messageId.

W-12004936
## [](#4-0-1)4.0.1 **February 7, 2023** ### What’s New - Anypoint MQ Connector version 4.x supports the Connected Apps feature. For information, see: - [接続アプリケーションの設定](https://docs.mulesoft.com/jp/mq/mq-connected-apps) - [Anypoint MQ Connector のアップグレードおよび移行](https://docs.mulesoft.com/jp/anypoint-mq-connector/latest/anypoint-mq-connector-upgrade-migrate) ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11
## [](#4-0-0)4.0.0 This version is deprecated. The new features for this version are in version [4.0.1](#4-0-1). ## [](#3-2-6)3.2.6 **February 6, 2024** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This connector is now compatible with Java 11.

W-14954942
## [](#3-2-5)3.2.5 **January 23, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 17
### Fixed Issues
Issue Resolution ID

The consumer/subscriber no longer recasts integer values to double values when it retrieves the message.

W-13721361
### Known Issues
Known Issue Workaround ID

Beginning with Anypoint Connector version 3.2.5, Anypoint Studio versions (for example, v7.16) configured with Java 11 as the default report that the connector doesn’t support Java 11.

Update the connector to version 3.2.6 or later if you need Java 11 support.

W-14954942
For additional known issue information about this product, see [Known Issues](https://help.salesforce.com/s/issues). ## [](#3-2-4)3.2.4 **April 19, 2023** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Spring Framework dependency is updated to 5.0.10 to fix reported security vulnerabilities (CVE-2018-15756).

The com.google.code.gson:gson dependency is updated to 2.8.9 to fix reported security vulnerabilities (CVE-2022-25647).

W-12717888
## [](#3-2-3)3.2.3 **February 27, 2023** ### Compatibility
Software Version

Mule

4.1.0 and later
### Fixed Issues
Issue Resolution ID

The connector now correctly supports the / character in messageId.

W-12004936
## [](#3-2-2-deprecated)3.2.2 (Deprecated) This version is deprecated. The fixed issues for this version are in version [3.2.3](#3-2-3). ## [](#3-2-1-deprecated)3.2.1 (Deprecated) This version is deprecated. The fixed issues for this version are in version [3.2.3](#3-2-3). ## [](#3-2-0)3.2.0 **October 12, 2022** ### What’s New - Anypoint MQ Connector now supports numeric values for user properties. If you plan to create _intelligent message routing rules_ on numeric properties, upgrade to this version of Anypoint MQ Connector. For information, see [メッセージエクスチェンジに対するルールを設定することによるメッセージの転送](https://docs.mulesoft.com/jp/mq/mq-routing-rules). ### Compatibility
Software Version

Mule

4.1.0 and later
## [](#3-1-7)3.1.7 **May 3, 2022** ### What’s New - This release includes security and performance improvements. ### Compatibility
Software Version

Mule

4.1.0 and later
## [](#3-1-6)3.1.6 **January 10, 2022** ### Compatibility
Software Version

Mule

4.1.0 and later
### Fixed Issues
Issue Resolution ID

Message Group ID now correctly supports alphanumeric characters (a-z, A-Z, 0-9) and punctuation (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ] \ ^ _ ` { } | ~).

SE-23324
## [](#3-1-5)3.1.5 **August 11, 2021** ### Compatibility
Software Version

Mule

4.1.0 and later
### Fixed Issues
Issue Resolution ID

Upgraded the following library dependencies to address security vulnerabilities:

  • com.google.guava:guava upgraded to 30.0-jre.

  • commons-io:commons-io upgraded to 2.7.

  • org.springframework:spring-core upgraded to 5.0.6.RELEASE.
## [](#3-1-4)3.1.4 **June 14, 2021** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.0 and later
### [](#fixed-issues-17)Fixed Issues - Improved performance by reusing the same connections when all the parameters in dynamic configuration remain the same. (SE-16909) ## [](#3-1-3)3.1.3 **April 29, 2021** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.0 and later
### [](#fixed-issues-18)Fixed Issues - Fixed an issue with the Anypoint MQ Connector retry and backoff mechanisms. (MQ-2282) ## [](#3-1-2)3.1.2 **January 21, 2021** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.1.0 and later
### [](#fixed-issues-19)Fixed Issues - Fixed an issue in which the Anypoint MQ Connector 3.1.1 Subscriber source with a circuit breaker and custom error prevented the app from consuming or processing messages. (SE-18045) ## [](#3-1-1)3.1.1 **September 11, 2020** ### [](#compatibility-31)Compatibility
Software Version

Mule

4.1.0 and later
### [](#fixed-issues-20)Fixed Issues - Fixed an issue in which the Anypoint MQ Connector 3.1.0 Subscriber source didn’t consume messages after a network outage. (SE-16793, SE-17007, SE-17206) ## [](#3-1-0)3.1.0 **October 2, 2019** ### [](#compatibility-32)Compatibility
Software Version

Mule

4.1.0 and later
### [](#new-features)New Features - Added message group ID support for FIFO queues. (MQ-1669) - Added support for Delay Queues and Delay Messages. (MQ-1594) ### [](#fixed-issues-21)Fixed Issues - Resolved an issue that caused a `StackOverflowError` error when using the connector in a `for-each` loop to process large amounts of data. ## [](#3-0-0)3.0.0 **July 29, 2019** ### [](#compatibility-33)Compatibility
Software Version

Mule

4.1.0 and later
### [](#new-features-2)New Features Version 3.0 includes an improved user experience and these new features: - All operations are nonblocking. - Subscriber source supports Mule Scheduler configurations natively. - Polling subscriber type supports throttling. - Java 11 is supported. - Circuit breaker configuration is simplified. - Subscriber source always uses long polling when fetching new messages. ### [](#fixed-issues-22)Fixed Issues This release fixes these issues: - Connection validation is ignored. (MQ-1521) - Avoid thread starvation on HTTP failures. (MQ-1522) - Change all payloads to IS instead of byte\[\]. (MQ-1394) - Consume operation should throw a TIMEOUT error when no message is present. (MQ-1280) - Avoid overlapping polls on Subscriber operation with fixed frequency. (MQ-1360) ## [](#2-1-0)2.1.0 **December 14, 2018** ### [](#compatibility-34)Compatibility
Software Version

Mule

4.0.0 and later
### [](#fixed-issues-23)Fixed Issues - Duplicated ACK when using IMMEDIATE mode. (MQ-1381) - Avoid overlapping polls on fixed-frequency subscriber. (MQ-1360) - Use long polling with maximum timeout in the fixed-frequency subscriber. (MQ-1359) - Add version information in User-Agent header. (MQ-1339) ### [](#new-features-3)New Features - Add circuit breaker capabilities to the MQ Subscriber. (MQ-1343) ## [](#2-0-5)2.0.5 **November 2, 2018** ### [](#compatibility-35)Compatibility
Software Version

Mule

4.0.0 and later
### [](#fixed-issues-24)Fixed Issues - Update reference docs for Subscriber parameters. (MQ-1340) - MQ Subscriber: Needs to shut down gracefully when stopped. (MQ-1338) - Anypoint MQ Connector does not remove expired messages from a preserved buffer. (MQ-1333) - Anypoint MQ Connector blocks all app I/O threads when invoked concurrently. (MQ-1324) - Anypoint MQ Connector prefetch limit is ignored. (MQ-1323) - The Subscriber picks up messages very slowly from a queue. (MQ-1322) - Messages are being read twice by Anypoint MQ Connector. (MQ-1320) - PollingTime is not used by the Subscriber. (MQ-1277) - Subscriber prefetch cannot be disabled. (MQ-1276) ## [](#2-0-4)2.0.4 **September 19, 2018** ### [](#compatibility-36)Compatibility
Software Version

Mule

4.0.0 and later
### [](#new-features-4)New Features This release of Anypoint MQ Connector implements retry logic with exponential backoff. ### [](#fixed-issues-25)Fixed Issues - Improves logger precision to avoid issues during transaction tracing. - Allows Subscriber prefetch to be disabled for predictability on API calls (see Known Issues). ### [](#known-issues-5)Known Issues Using prefetch can result in the loss of predictability of API calls. If prefetch is used, Anypoint MQ Connector aggressively tries to fetch messages, which results in increased API calls. If predictability and control on API requests is important, use the following steps to disable prefetch and strictly follow the polling time.
Only disable prefetch if predictability on API calls is more important than performance. Maximum possible performance is only available when prefetch is enabled.
To disable prefetch: 1. Access a new or existing connector configuration of the MQ Subscriber component. 2. Navigate to the Prefetch tab. 3. Specify a Fetch size of 0. This disables prefetch. 4. In the Studio General tab, specify a **Polling time** in milliseconds. This time interval is strictly adhered to when making API calls. Polling time defaults to 10 seconds if an explicit configuration is not present. If there are no messages in the queue, each poll that a subscriber makes waits for the duration of exactly half of the **Polling time** specified in the General tab. Polling time has a maximum value of 20000 milliseconds. **Note:** Versions 2.0.2 - 2.0.3 were internal releases only without changes to the user interface or product usage. For additional known issue information about this product, see [Known Issues](https://help.salesforce.com/s/issues). ## [](#2-0-1)2.0.1 **July 4, 2018** ### [](#compatibility-37)Compatibility
Software Version

Mule

4.0.0 and later
### [](#fixed-issues-26)Fixed Issues - Internal fix only. No change to the user interface or product usage. ## [](#2-0-0)2.0.0 **November 17, 2017** ### [](#new-features-5)New Features Anypoint MQ Connector adds support for Mule4 and Anypoint Studio 7. ### [](#compatibility-38)Compatibility
Software Version

Mule

4.0.0 and later
### [](#known-issues-6)Known Issues - Anypoint MQ Connector doesn’t support tracking. Example with tracking: ```xml ``` Example without tracking: ```xml ``` For additional known issue information about this product, see [Known Issues](https://help.salesforce.com/s/issues). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint MQ Release Notes Anypoint MQ is a multi-tenant, cloud messaging service that enables you to perform advanced asynchronous messaging scenarios between your applications. Anypoint MQ is fully integrated with Anypoint Platform, offering role based access control, client application management, and connectors. The following release notes are provided for Anypoint MQ: - [Anypoint MQ Release Notes](https://docs.mulesoft.com/jp/release-notes/mq/mq-release-notes) - [Anypoint MQ Connector Release Notes for Mule 4](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4) ## [](#see-also)See Also - [Anypoint MQ の概要](https://docs.mulesoft.com/jp/mq/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint MQ Release Notes ## [](#2-18-0)2.18.0 **April 21, 2026** ### What’s New - Anypoint MQ now supports FIFO message exchanges. You can now send messages to multiple FIFO queues by binding those FIFO queues to a FIFO message exchange. This functionality is available using: - Anypoint MQ UI For information, see [メッセージエクスチェンジを使用した複数のキューへのメッセージの送信](https://docs.mulesoft.com/jp/mq/mq-exchanges). - Anypoint MQ Admin API For information, see [Anypoint MQ Admin API](https://docs.mulesoft.com/jp/mq/mq-apis#mq-admin-api). - For standard message exchanges, you can bind up to 25 queues when using message routing rules. ## [](#2-17-0)2.17.0 **December 9, 2024** ### What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) For more information, see [Anypoint MQ on Hyperforce](https://docs.mulesoft.com/jp/mq/#mq-on-hyperforce) and [Salesforce Hyperforce Overview](https://docs.mulesoft.com/hyperforce/). ## [](#2-16-0)2.16.0 **October 17, 2024** ### What’s New - The **MQ Usage** page in access management now shows usage stats for the current and previous month. This change aligns with an initiative to adopt the new [使用状況レポート](https://docs.mulesoft.com/jp/general/usage-reports), which enhances the user experience, provides clearer usage insights, and enables more queries for data analysis. For information, see [Access Anypoint MQ Usage](https://docs.mulesoft.com/jp/mq/mq-usage#access-anypoint-mq-usage). Although the UI shows only two months of data, you can query up to two years of usage data by calling the [Anypoint MQ Statistics API](https://dev-portal.mulesoft.com/apis/anypoint-mq-stats.html) directly. For information, see [Anypoint MQ の REST API](https://docs.mulesoft.com/jp/mq/mq-apis). ## [](#2-15-0)2.15.0 **October 7, 2024** ### What’s New - When creating queues with the Anypoint MQ UI, the **Encryption** option is now selected by default, providing enhanced security for new queues. For information, see [Encrypted Queue](https://docs.mulesoft.com/jp/mq/mq-glossary#encrypt-queue). ## [](#2-14-0)2.14.0 **May 10, 2024** ### What’s New - Anypoint MQ supports cross-region failover for standard queues. To use this feature, you must upgrade Anypoint Connector for Anypoint MQ (Anypoint MQ Connector) to version 4.0.7. For information, see: - [mq::mq-failover.adoc](#mq::mq-failover.adoc) - [アプリケーションでのクロスリージョンフェールオーバーの設定](https://docs.mulesoft.com/jp/anypoint-mq-connector/latest/anypoint-mq-failover) - [Anypoint MQ Connector 4.0.7](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4#4-0-7) Release Notes ## [](#2-13-0)2.13.0 **June 28, 2023** ### What’s New - Anypoint MQ is now available in MuleSoft Government Cloud. クライアントアプリケーションや暗号化されないキューなど、一部の Anypoint MQ 機能はアクセスまたは設定ができません。 詳細は、​[「Anypoint MQ in MuleSoft Government Cloud (MuleSoft Government Cloud の Anypoint MQ)」](https://docs.mulesoft.com/jp/mq/#mq-in-govcloud)​を参照してください。 ## [](#2-12-1)2.12.1 **March 31, 2023** ### What’s New - Anypoint Platform and this product now use system fonts, which improves legibility, adds native support for localization and character subsets at the operating-system level, and increases performance because the browser no longer has to download custom fonts. ## [](#2-12-0)2.12.0 **February 7, 2023** ### What’s New - The **Destinations** page in Anypoint MQ now includes the ability to select the version of Anypoint Connector for MQ (Anypoint MQ Connector): ![Copy button in the Destinations page](/mulesoft/current/ja-jp/mq/_images/mq-tutorial-url.png) This feature enables you to use Anypoint MQ Connector version 4.x, which supports Connected Apps. For more information, see: - [Anypoint MQ Connector 4.x for Mule 4](https://docs.mulesoft.com/jp/anypoint-mq-connector/latest/) - [接続アプリケーションの設定](https://docs.mulesoft.com/jp/mq/mq-connected-apps) - [Create and Connect a Mule 4 App to Anypoint MQ in Anypoint Studio 7](https://docs.mulesoft.com/jp/mq/mq-tutorial#configure-mule-4-studio) ## [](#2-11-9)2.11.9 **October 18, 2022** ### What’s New - The Anypoint MQ Stats API now limits retrieving stats for the [`/organizations/{ORGANIZATION_ID}`](https://dev-portal.mulesoft.com/apis/anypoint-mq-stats.html) and [`/organizations/{ORGANIZATION_ID}/environments/{ENVIRONMENT_ID}`](https://dev-portal.mulesoft.com/apis/anypoint-mq-stats.html) endpoints to 10 transactions per minute (TPM). If requests exceed this limit, the Anypoint MQ Stats API returns an HTTP 429 status code. For all other [Anypoint MQ Statistics API](https://dev-portal.mulesoft.com/apis/anypoint-mq-stats.html) endpoints, the limit is 200 TPM. ## [](#2-11-8)2.11.8 **October 14, 2022** - Anypoint MQ now includes the ability to create intelligent message routing rules to route a subset of the messages published to an exchange to a specific queue. For information, see [メッセージエクスチェンジに対するルールを設定することによるメッセージの転送](https://docs.mulesoft.com/jp/mq/mq-routing-rules).
数値プロパティ値に基づくルーティングルールを作成し、Anypoint MQ Connector を使用してメッセージをパブリッシュする場合、Anypoint MQ Connector バージョン 3.2.0 以降にアップグレードする必要があります。 これより前のバージョンのコネクタでは、すべてのプロパティ値が文字列として送信されるため、メッセージは数値プロパティに基づくルーティングルールに一致しません。
- Anypoint MQ now supports the Connected Apps feature. For information, see [接続アプリケーションの設定](https://docs.mulesoft.com/jp/mq/mq-connected-apps). - Anypoint MQ includes two new permissions: - **Administer destinations** - **Destination subscriber for given environment** - **Destination publisher for given environment** The **Manage destinations** permission is deprecated. For more information, see [Anypoint MQ Permissions](https://docs.mulesoft.com/jp/mq/mq-access-management#anypoint-mq-permissions). ## [](#2-11-7)2.11.7 **June 13, 2022** ### What’s New - Anypoint MQ now limits the number of queues that you can bind to a message exchange to 450. ## [](#2-11-6)2.11.6 **April 22, 2022** ### What’s New - The UI now includes updated components, which look slightly different. ## [](#2-11-5)2.11.5 **April 18, 2022** ### What’s New - Added Ohio (`us-east-2`) as a new region to the US control plane. ## [](#2-11-4)2.11.4 **December 14, 2021** ### Fixed Issues
Issue ID

The MQ UI now displays the correct error message if a message deletion fails when the TTL expired: Message cannot be deleted.

SE-16922/MQ-2726

Added a fix to prevent a potential security vulnerability.

MQ-2786
## [](#2-11-3)2.11.3 **June 28, 2021** ### [](#new-features)New Features - Added APAC Tokyo (`ap-northeast-1`) as a new region to the US control plane. ## [](#2-11-2)2.11.2 **June 15, 2021** ### [](#fixed-issues-2)Fixed Issues - The **Message Browser** page now retrieves the specified number of messages from the queue and correctly displays the retrieval progress. (SE-16922) ## [](#2-11-1)2.11.1 **May 12, 2021** ### [](#fixed-issues-3)Fixed Issues - Fixed issues with styles in the Anypoint MQ user interface. (MQ-2418) - Fixed an issue that displayed both a success and error message when successfully creating an exchange with no queues. (MQ-2390) ## [](#2-11-0)2.11.0 **April 26, 2021** ### [](#new-features-2)New Features - Added the optional `payloadVisibility` parameter to the Anypoint MQ Broker API. (SE-18968/MQ-2303/MQ-2304) By default, the Anypoint MQ Broker API `messages` endpoint displays the message payload in the response, regardless of the payload size. You can control whether to show the message payload in the response by setting the `payloadVisibility` query parameter to one of: - `full`: Shows the message payload in the response. This option is the default. - `none`: Hides the message payload in the response. - `conditional`: Hides the message payload if the payload size is larger than 1 MB. For more information, see [Example: Retrieve a Message](https://docs.mulesoft.com/jp/mq/mq-apis#example-retrieve-a-message). - Changed the message retrieval on the **Message Browser** page to display the payload only if the payload size is smaller than 1 MB. (SE-18968/MQ-2303/MQ-2304) If the payload size is 1 MB or larger, the **Message Browser** page displays an error. ### [](#fixed-issues-4)Fixed Issues - Fixed an issue in which refreshing the **Message Browser** page caused it to incorrectly display `50` for the number of messages to retrieve for FIFO queues. (MQ-2348) - Fixed a potential security vulnerability. (MQ-2244) ## [](#2-10-3)2.10.3 **March 23, 2021** ### [](#fixed-issues-5)Fixed Issues - Internal bug fixes ## [](#2-10-2)2.10.2 **December 23, 2020** ### [](#new-feature)New Feature - User property names can now contain the colon (:) character. (MQ-2211) ### [](#changed-feature)Changed Feature - In the **Message Browser** page, the date format for the **Date Created** column has changed. (MQ-2222) - In the **Payload** details pane, the **Sent** field has been renamed to **Date Created** to match the **Date Created** column in the **Message Browser** page. (MQ-2222) ### [](#fixed-issues-6)Fixed Issues - In the **Message Browser** page, you can now sort messages by the **Date Created** column. (MQ-2222) ## [](#2-10-1)2.10.1 **September 15, 2020** ### [](#new-feature-2)New Feature - Improved security encryption for queues and exchanges that have the **Encryption** option selected. (MQ-2001) ### [](#fixed-issues-7)Fixed Issues - Internal bug fixes ## [](#2-10-0)2.10.0 **July 22, 2020** ### [](#new-feature-3)New Feature - Added the ability to include user properties when sending a message to a queue and view those properties in the **Message Browser** page. (MQ-1887) ### [](#fixed-issue)Fixed Issue - Fixed an issue in the **Get Messages** page in which an error popup persisted, requiring a page refresh. (MQ-1916) ## [](#2-9-0)2.9.0 **February 26, 2020** ### [](#fixed-issues-8)Fixed Issues - Fixed an issue in which duplicate messages were incorrectly displayed in the **Message Browser**. (MQ-1825) ## [](#2-8-0)2.8.0 **January 22, 2020** ### [](#fixed-issues-9)Fixed Issues - Fixed an issue in which the **Return Messages** mouseover label persisted even after cursor was removed. (MQ-1726) ### [](#new-features-3)New Features - Added **X** icon to close the details pane. (MQ-1790) ## [](#2-7-0)2.7.0 **December 7, 2019** ### [](#new-features-4)New Features - Added **Full Screen** icon for viewing the message payload in a new window. (MQ-1763) - Added X icon to close toast notifications. (MQ-1769) ## [](#2-6-0)2.6.0 **November 8, 2019** ### [](#new-features-and-updates)New Features and Updates - Updated DLQ description in **Create Queue** form (MQ-1728) - Added support for **esc** key for closing modal popups (MQ-1727) - Added **Copy** button for Anypoint MQ region URL (MQ-1319) - Changed label from **Message Lock Default TTL** to **Default Acknowledgment Timeout** (MQ-1733) - Implemented hover tooltip for **Default Acknowledgment Timeout** (MQ-1741) - Added Anypoint MQ to the **Recently Visited** list (MQ-1746) - Updated **Destinations** page empty state (MQ-1754) - Added user properties to message details pane (MQ-1762) - Added highlight to selected message in the browser list (MQ-1764) ### [](#fixed-issues-10)Fixed Issues - None ## [](#2-5-0)2.5.0 **September 21, 2019** ### [](#new-features-and-updates-2)New Features and Updates - Added message group ID support for FIFO queues (MQ-1639) - Added destination type filter for destination list (MQ-1717) - Added payload snippet and creation date to message list (MQ-1715) - Removed unused millisecond option for time picker (MQ-1656) ### [](#fixed-issues-11)Fixed Issues - Fixed message browser not clearing previous messages. (MQ-1665) ## [](#2-4-0)2.4.0 **August 10, 2019** ### [](#new-features-5)New Features - Added support for Delay Queues and Delay Messages. (MQ-1213) ### [](#fixed-issues-12)Fixed Issues - Fixed Message Sender payload text area that overlapped the Submit button. (MQ-1555) ## [](#2-3-0)2.3.0 **June 29, 2019** ### [](#new-features-and-updates-3)New Features and Updates - FIFO queues are now available in all regions where Anypoint MQ is available. - Enhanced MQ error response codes and messages with more clearly defined details when API calls fail. ### [](#fixed-issues-13)Fixed Issues - Fixed a bug in the reporting of historical queue usage metrics. ## [](#2-2-0)2.2.0 **May 30, 2019** ### [](#updates)Updates - Anypoint MQ user interface has been re-engineered and optimized for smaller bundle sizes and faster page loads. - Deep linking lets each resource within Anypoint MQ have a unique URL for easier navigation and sharing. ## [](#2-1-1)2.1.1 **April 4, 2019** ### [](#updates-2)Updates - Backend and user interface improvements. ### [](#fixed-issues-14)Fixed Issues - Audit all auditable actions even if they fail or are invalid. (MQ-629) - Fixed an exception when a user tries to delete a queue multiple times. (MQ-726) - Deleting an environment fails when there are a lot of destinations to delete. (MQ-736) - Destination names now render properly when the name is very long. (MQ-1487) - Organizations that use OKTA external identity management can now create MQ clients. (MQ-1499) ## [](#2-1-0)2.1.0 **March 23, 2019** ### [](#updates-3)Updates - User interface improvements ### [](#fixed-issues-15)Fixed Issues - Change message sender layout. (MQ-1437) - Change ordering of edit form to match create form. (MQ-1426) - Change UI details header hover state. (MQ-1435) (UI) - Fixed MQ queues, clients, message list was "jumpy". (MW-1478) - MQ Console: Update TTL label for creating and updating a queue. (MW-1335) - Update destinations and client empty state. (MQ-1440) - Update message toast UI. (MQ-1427) - Update queue and message exchange create or update UI. (MQ-1418) ## [](#2-0-6)2.0.6 **February 8, 2019** ### [](#fixed-issues-16)Fixed Issues - Fixed a bug where sending batched messages to FIFO queues could allow more than 10 messages at a time to be retrieved. - Fixed a race condition bug when trying to bind a message queue to an exchange that was recently deleted. ## [](#2-0-5)2.0.5 **December 14, 2018** ### [](#new-features-6)New Features - FIFO support in Sydney. (MQ-1358) - Added message time-to-live information to message headers. Message JSON example: ```json [ { "properties" : { "contentType" : "text/plain; charset=UTF-8" }, "headers" : { "messageId" : "ad9010c1-cf08-4d57-8195-60d1e4cbd371", "lockId" : "abcs1234123", "ttl" : "120000", "created" : "Fri, 14 Dec 2018 20:23:50 GMT", "deliveryCount" : "1" }, "body" : "message body here" } ] ``` ### [](#fixed-issues-17)Fixed Issues - UI message payload view does not respect newlines or whitespace properly. (MQ-1364) - Fix to Dead Letter Queue assignment. (MQ-1379) - Error 500 when creating queue in invalid region. (MQ-1384) ## [](#2-0-4)2.0.4 **October 4, 2018** ### [](#fixed-issues-18)Fixed Issues - Can’t create client app in Anypoint MQ even permissions are correct. (SE-7939) - Anypoint MQ message queues do not honor default lock TTL. (SE-9085) ## [](#2-0-3)2.0.3 **April 20, 2018** ### [](#new-features-7)New Features Anypoint MQ has added EU Ireland as a new region to the EU Control Plane. ## [](#2-0-2)2.0.2 **April 4, 2018** ### [](#fixed-issues-19)Fixed Issues The names for queues, message exchanges, and client applications can now contain one or more dot characters. (MQ-1118) ## [](#2-0-1)2.0.1 **March 24, 2018** ### [](#new-features-8)New Features This release adds access to London (eu-west-2) and Central Canada (ca-central-1). ## [](#2-0-0)2.0.0 **February 24, 2018** ### [](#new-features-9)New Features This release provides a new user interface backend implementation along with a suite of other major internal implementation changes. ### [](#fixed-issues-20)Fixed Issues - Anypoint MQ Message Browser does not display all messages. (SE-6899) - Anypoint MQ statistics are not updated. (SE-6607) - Unable to update MQ settings. (SE-6180) - MQ UI is not refreshing in-flight messages correctly. (SE-4654) - Disable submit button while pending request. (MQ-1024) - Cannot create a client app name with the maximum length characters allowed. (MQ-993) - Switching environments from Client Apps redirects to Destinations. (MQ-992) - Inconsistent chart rendering. (MQ-913) - Stats: data points are not shown on mouseover if values appear at the top of the chart. (MQ-332) - Statistics tooltip doesn’t disappear on mouse left. (MQ-321) - Ellipsis is not part of the link. (MQ-320) - When you want to create a queue or message exchange and click on the corresponding option when the dialog modal is open, you need to click again on the Name field to start creating the destination. (MQ-305) ## [](#1-7-4)1.7.4 **September 23, 2017** ### [](#new-features-10)New Features - The Statistics API provides these new metrics that apply to both FIFO and non-FIFO queues: (MQ-748) - messagesVisible - The number of messages that can be retrieved from a queue. - messagesSent - The number of messages added to a queue. - messagesReceived - The number of messages received in a queue. - messagesAcked - The number of messages ACKed or deleted in the UI. ### [](#fixed-issues-21)Fixed Issues - Can now send messages to FIFO DLQs correctly. (MQ-706) ## [](#1-7-1)1.7.1 **July 15, 2017** ### [](#new-features-11)New Features - FIFO access is now available in Oregon (us-west-2), Northern Virginia (us-east-1), and Ireland (eu-west-1). ## [](#1-6-1)1.6.1 **May 20, 2017** ### [](#new-features-12)New Features - Added MQ access to Singapore (ap-southeast-1). ## [](#1-6-0)1.6.0 **March 25, 2017** ### [](#new-features-13)New Features - [Audit Logging for Anypoint MQ](https://docs.mulesoft.com/jp/access-management/audit-logging#to-query-audit-logging-for-anypoint-mq). ## [](#1-5-0)1.5.0 **January 28, 2017** ### [](#new-features-14)New Features - [FIFO queues](https://docs.mulesoft.com/jp/mq/mq-queues#fifoqueues) - [Exactly once delivery](https://docs.mulesoft.com/jp/mq/mq-queues#about-fifo-exactly-once-delivery) - Rollout of Anypoint MQ to US-West (Oregon) region - Enables encoding and support for UTF-8/non-Ascii characters ## [](#1-4-0)1.4.0 **November 5, 2016** ### [](#fixed-issues-22)Fixed Issues This release of Anypoint MQ fixes issues with Analytics usage and with OAuth.
Issue Description

MQ-572

Modify startDate and endDate in metrics to use a standard date format, such as 2016-11-01T19:00Z. This change preserves both the old format and the new format for backward compatibility.

MQ-556

Fixed memory leak that occurred when reporting usage metrics

MQ-548

Created support for sending a message without a body

MQ-543

When sending an Ack without bearer token, report 401 error instead of 500

MQ-535

Report 500 error when trying to create a queue with the same name as the dead letter queue

MQ-534

Return a 400 error if user tries to configure the DLQ of a queue as itself
## [](#1-3-0)1.3.0 **August 27, 2016** ### [](#new-features-15)New Features - [Dead Letter Queue (DLQ)](https://docs.mulesoft.com/jp/mq/mq-queues#about-dead-letter-queues) feature enables a queue to receive undeliverable messages. - Bug fixes and UI improvements.

The Anypoint MQ API lets you configure a queue to be its own dead letter queue; however, the MQ user interface does not let a queue to be its own DLQ, only the REST API permits this. MuleSoft recommends that you do not do this except for testing purposes because if left in production, this can result in infinite retries thus causing a client application to burn through its monthly usage quota quickly.
### [](#fixed-issues-23)Fixed Issues
Issue Description

MQ-339

Ability to use Dead Letter Queues

MQ-488

Correction to encoding logic when sending messages between 200-300KB

MQ-489

Add a new header to messages specifying the encoding

MQ-493

Dead Letter Queue UI

MQ-507

Return the error status when creating a queue with no body

MQ-511

Usage of correct property attributes for retry policy

MQ-531

Dead Letter Queue UI state updates
## [](#1-2-0)1.2.0 **June 25, 2016** ### [](#new-features-16)New Features - Improved Usage Tracking UI. For more information, see [Anypoint MQ Usage Information](https://docs.mulesoft.com/jp/mq/mq-usage) - Metrics and usage tracking API - MQ billing management ### [](#fixed-issues-24)Fixed Issues
Issue Description

MQ-391

UI for usage tracking

MQ-394

Metrics Query API

MQ-404

MQ detailed usage pane and improvements to other UI screens

MQ-411

Stats API - Standardize the date format we use for the different calls

MQ-412

Cannot get statistics of queues

MQ-413

Broker API - Cannot get message

MQ-416

Admin API - Operations are not being counted in analytics in the apiRequestCount field

MQ-420

Better error messages and logging for stats/analytics requests

MQ-434

Support histograms of message sizes per queue

MQ-442

Support MQ billing management

MQ-444

MQ UI should not be displayed if the organization doesn’t have it enabled

MQ-445

Some components doesn’t look properly

MQ-446

Several errors in modal to create a queue

MQ-449

When deleting a queue, displays "Deletion Fail" message even when there’s no failure
## [](#1-1-2)1.1.2 **May 14, 2016** ### [](#updates-4)Updates This release provides user interface updates. ### [](#fixed-issues-25)Fixed Issues
Issue Description

MQ-327

Message browser list should not be ordered by message ID

MQ-357

Add IDs to HTML elements for test automation

MQ-374

[UI] Exchange Settings are not visible as soon as the user access to the details

MQ-385

Integrate notifications with analytics for billing

MQ-388

[UI][Chrome] unreadable list of queues during the creation of an exchange
## [](#1-1-0)1.1.0 **May 5, 2016** This release is the General Availability release for Anypoint MQ. ### [](#new-features-17)New Features - Users can view and track their MQ usage. - 10 MB maximum message size limitation is now enforced. - Updated API error and return codes reflect the proper status. ### [](#fixed-issues-26)Fixed Issues
Issue Description

MQ-201

(Admin API) The system returns 204 ok even when the org ID doesn’t exist

MQ-205

Enforced maximum message size limit to 10 MB

MQ-241

Exchange historical statistics as delta from 0

MQ-301

Ability to count delivered/received messages

MQ-306

Request to non-existing API returns bad error message
## [](#1-0-1)1.0.1 **January 23, 2016** ### [](#new-features-18)New Features - Anypoint MQ now supports Internet Explorer 11. ## [](#1-0-0)1.0.0 **December 21, 2015** ### [](#new-features-19)New Features - Queues and Message Exchanges Send messages to queues, pull messages from queues, create a message exchange to perform pub/sub scenarios and send a message to multiple queues. Management console: monitor queue statistics, purge queues, and see how many messages are in flight via the management console. - Anypoint MQ connector Send/receive messages from any Mule application, whether it’s deployed in CloudHub or used in a hybrid scenario and deployed on-premises. - Client management Create client applications tokens. - Large payloads Anypoint MQ supports payloads up to 10 MB in size. - Disaster recovery and multi-data center availability: Anypoint MQ provides persistent data storage across multiple data centers, ensuring that it can handle data center outages and have full disaster recovery. - Encrypted queues Queue data can optionally be encrypted, ensuring that companies can be compliant with their data at rest policies. ## [](#see-also)See Also - [Anypoint MQ Connector Release Notes for Mule 4](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4) - [Anypoint MQ Documentation](https://docs.mulesoft.com/jp/mq/) - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Partner Manager Release Notes These release notes are provided for Anypoint Partner Manager: - [Anypoint Partner Manager Release Notes](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes) ## [](#see-also)See Also - [Anypoint Partner Manager の概要](https://docs.mulesoft.com/jp/partner-manager/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Partner Manager Release Notes ## [](#2-27-1)2.27.1 **August 12, 2026** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.18.7

API Replication service

1.27.0

Endpoint services

3.18.3
### [](#dependent-components-used)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.2 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.11.1 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.14 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.7.2 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

Upgrades to CloudHub 2.0 applications no longer fail due to naming collisions across environments.

W-23687405

SFTP Java 17 endpoint templates now use SFTP Connector version 2.7.2 to prevent stale heartbeat connections from accumulating on servers.

W-23744879
## [](#2-27-0)2.27.0 **June 26, 2026** This version requires a runtime template update. ### What’s New - You can now configure lookup tables to standardize how B2B message payloads are mapped between partner and internal data models. You can create composite key and cross-reference lookup tables, with integrity definitions, including key and mandatory, for business users to manage, and access the lookup data entries from your B2B data mappings in the runtime. For more information about configuring and managing lookup tables, see [partner-manager::lookup-tables-overview.adoc](#partner-manager::lookup-tables-overview.adoc). ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.18.7

API Replication service

1.27.0

Endpoint services

3.18.2
### [](#dependent-components-used-2)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.2 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.11.1 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.14 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.6.5 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

PDF generation quality for AI summaries of B2B data payloads is improved.

W-21744792

AI summaries of B2B data payloads are improved to prevent text from being cut off.

W-21684725

AI summaries of B2B data payloads now generate correctly regardless of the user’s organization permissions.

W-22969312

Message flow links are now uniquely labeled per partner for screen readers.

W-15464206

The Activity page now prevents pagination inconsistencies by ensuring new messages and transmissions aren’t loaded unless you explicitly refresh the results.

W-21320963

Custom message attributes are now shown correctly for transmission scenarios that end in a failed state.

W-22242884

RTFs clusters associated with all environments are now listed in the selection dropdown.

W-21614334

Tracking updates are now reported correctly after a failure to sign an MDN response in certain compression scenarios.

W-21615522

The Repetition Separator option is now available when configuring EDI versions later than 4010.

W-21357023

Creating an EDI configuration with an ID that already exists now returns a 409 Conflict response instead of a 500 Internal Server Error.

W-22043583

Outbound message mapping errors are now displayed correctly even when the mapping doesn’t output the expected content type.

W-20984628

Adaptive compression now works correctly for CloudHub 2.0 inbound endpoints under certain conditions that previously caused failures.

W-22819794

Adaptive compression now compresses messages correctly when the message sent to the queue is large.

W-23018476

The Manage Deployments process now detects failures and reports issues correctly in migration rollback scenarios.

W-21525836

Large replay batches no longer trigger Anypoint MQ rate limits.

W-21764442

Connected app names for Anypoint MQ now include the environment ID, preventing naming collisions across environments.

W-21782746

Internal transmission reporting tasks are now recovered correctly in scenarios that previously caused them to hang.

W-20834743

New features that require a Mule runtime engine upgrade are now grayed out rather than hidden, so you can see what requires an upgrade.

W-22863183

Users with only the View Activity permission can now successfully navigate the Activity page.

W-21723489
## [](#2-26-0)2.26.0 **March 17, 2026** This version requires a runtime template update. ### What’s New - You can now use AI to generate a summary of the message payload. Enable Einstein in your CloudHub or Runtime Fabric deployment settings to use this feature. For more information on using the AI summary feature, see [個別メッセージの追跡](https://docs.mulesoft.com/jp/partner-manager/latest/activity-message-tracking). For more information on enabling Einstein, see [CloudHub 1.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub-deployment-settings), [CloudHub 2.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub2-deployment-settings), and [Runtime Fabric デプロイメントの設定](https://docs.mulesoft.com/jp/partner-manager/latest/rtf-deployment-settings). ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.17.0

API Replication service

1.26.0

Endpoint services

3.17.0
### [](#dependent-components-used-3)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.1 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

The Document Processing Service (DPS) runtime application is no longer deleted during specific migration scenarios, ensuring the service remains active if a deployment fails.

W-21139063

The search filter on the Maps page now correctly shows all matching results.

W-21105459

The AS2 inbound application no longer redeploys unnecessarily during map changes, target endpoint updates, or when redeploying an outbound message flow whose expected acknowledgment uses an AS2 endpoint.

W-21195421

Updating environment settings no longer resets a remapped MQ region, preventing subsequent deployment failures.

W-21042258

The View Payload button in outbound transmission details now correctly opens the payload content when a Payload view URL is configured.

W-21313286

Audit log payloads are now reduced when creating entities.

W-21077016

Target payloads are no longer saved as compressed to content storage in CloudHub 2.0 environments.

W-21448452
## [](#2-25-0)2.25.0 **January 29, 2026** This version requires a runtime template update. ### What’s New - Partner Manager now features a centralized Maps page where you can import, manage, and version DataWeave (.dwl) translation maps. This update allows you to apply mapping changes across deployed message flows by setting new versions as active without needing to upload the updated file to each message flow and redeploy. For more information, see [partner-manager::maps-overview.adoc](#partner-manager::maps-overview.adoc). - You can now adaptively compress message payloads before they’re sent to Anypoint MQ to prevent processing failures. This optimization addresses scenarios where large XML files (near the 10 MB limit) expand due to encoding. For more information, see [CloudHub 1.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub-deployment-settings), [CloudHub 2.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub2-deployment-settings), and [Runtime Fabric デプロイメントの設定](https://docs.mulesoft.com/jp/partner-manager/latest/rtf-deployment-settings). - You can now configure FTP and SFTP receive endpoints to skip empty files during processing. For more information, see [FTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-ftp-receive) and [SFTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-sftp-receive-target). ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.16.1

API Replication service

1.25.0

Endpoint services

3.16.5
### [](#dependent-components-used-4)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.1 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

Updating an X12 configuration in the UI no longer causes an error when the configuration was originally created via an API without a partner ID.

W-19135979

Renaming an inbound message flow using a third-party AS2 connection no longer causes an invalid flow configuration error during deployment.

W-20231427

The application ingress URL displayed on HTTP and AS2 endpoints in CloudHub 2.0 now matches the deployment URL in Runtime Manager.

W-19639638

Accessing a new environment without deployment settings in Partner Manager or Access Management no longer causes an internal server error.

W-20219817

Deploying a new inbound message flow using an existing third-party AS2 connection no longer causes the AS2 inbound application to redeploy unnecessarily.

W-20231483

Configuring an HTTPS endpoint with the default port 443 no longer results in an incorrect base path or a missing URL in the UI.

W-19768952

Messages with outbound delivery errors are now successfully stored in payload storage.

W-19639785

A mismatch between the content type and payload in outbound messages no longer causes the message to get stuck in a processing loop.

W-20091731

Detailed logs are now generated when custom EDI schema validation fails and the file is not written to disk.

W-19630808

Outbound templates for AS2, FTP, and SFTP now display specific failure reasons instead of generic error messages.

W-19581703

Partner Manager now preserves custom URL path rewrites configured in Runtime Manager when the Preserve Public URL option is selected.

W-20838447

Users with the appropriate role can now create endpoints that contain certificates.

W-20896207

Endpoint settings are now applied correctly and applications are recreated for all deployments, even when obsolete templates are present during upgrades or migrations.

W-20812761

Outbound message attributes are now shown when mapping errors occur.

W-19812476

When an SFTP server issues frequent connection resets, the CloudHub 2.0 outbound SFTP runtime application now reliably processes messages.

W-21077401
## [](#2-24-5)2.24.5 **January 15, 2026** This version doesn’t require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.15.2

API Replication service

1.24.0

Endpoint services

3.15.2
### [](#dependent-components-used-5)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.1 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

AS2 endpoints configured with the HTTP protocol now deploy correctly after CloudHub 1.0 to CloudHub 2.0 migration.

W-20391091

Navigating to messages related to a transmission now works as expected and no longer results in an Unable to load the content error.

W-20684714

The Host field for CloudHub 2.0 environment settings no longer includes options for CloudHub 1.0 domains.

W-19812847

Message flow deployments no longer fail when a large number of applications are present in CloudHub 2.0 environments.

W-20833834
## [](#2-24-4)2.24.4 **December 18, 2025** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.15.2

API Replication service

1.24.0

Endpoint services

3.15.2
### [](#dependent-components-used-6)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.1 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

Partner Manager now preserves user-defined public URLs for AS2 or HTTP inbound endpoints in CloudHub 2.0 via an endpoint option.

W-20017417

Custom message attributes for inbound transactions are now visible even when there is a mapping error.

W-19812476

The default search window for the Activity page is now set to the past three hours.

W-20517517
## [](#2-24-3)2.24.3 **November 11, 2025** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.15.1

API Replication service

1.24.0

Endpoint services

3.15.2
### [](#dependent-components-used-7)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.1 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

CloudHub 1.0 inbound templates are now working correctly with API Manager in Mule runtime 4.9.

W-20159059
## [](#2-24-2)2.24.2 **November 11, 2025** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.15.1

API Replication service

1.24.0

Endpoint services

3.15.1
### [](#dependent-components-used-8)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.1 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

Partner Manager no longer generates duplicate ISA and GS Control Numbers in CloudHub 2.0 deployments using multiple replicas.

W-20091679
## [](#2-24-1)2.24.1 **October 28, 2025** This version doesn’t require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.15.0

API Replication service

1.24.0

Endpoint services

3.15.1
### [](#dependent-components-used-9)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.1 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

FTP Connector is updated to version 2.0.1 and now ignores blank folder names for more stable processing.

W-19774360, W-19774360
## [](#2-24-0)2.24.0 **October 1, 2025** This version requires a runtime template update. ### What’s New - You can now select the domain when configuring Runtime Fabric deployment settings in Access Management. For more information, see [Runtime Fabric デプロイメントの設定](https://docs.mulesoft.com/jp/partner-manager/latest/rtf-deployment-settings). - You can now set a specific deployment path by selecting the app name substitution for AS2, HTTP, and HTTPS receive endpoints when deploying to Runtime Fabric. For more information, see [AS2 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-as2-receive) and [HTTP および HTTPS 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-https-receive). - EDIFACT global control numbers now support up to 14 characters. For more information, see [Global Control Numbers](https://docs.mulesoft.com/jp/partner-manager/latest/edifact-send-settings#global-control-numbers). - You can now configure the base path for inbound AS2 endpoints when deploying to Runtime Fabric. As part of this feature, existing AS2 inbound endpoints are automatically migrated to the default `receive-as2` base path. For more information, see [AS2 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-as2-receive).
To avoid conflicts, make sure you don’t have multiple HTTP inbound endpoints with the same base path and the Use base path as the ingress path checkbox enabled.
- CloudHub 1.0 to CloudHub 2.0 migration is now supported. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.15.0

API Replication service

1.24.0

Endpoint services

3.15.0
### [](#dependent-components-used-10)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.1 - Anypoint Connector for FTP Connector (FTP Connector) 2.0.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.7 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.3 with Java 8 and 2.4.3 with Java 17 - Anypoint Connector for X12 (X12 Connector) 2.17.2 ### Fixed Issues
Issue Resolution ID

Message flows now show as expected in the message flows popup.

W-19484400

You can now see the payload for failed transmission steps, which simplifies debugging and helps you pinpoint the exact cause of an error.

W-17487158

Outbound HTTP messages now show the failure reason at the message level.

W-19250288

Error messages are now clearer for payload storage configuration issues and other errors across Partner Manager.

W-19455311

Failed payloads are now logged and persisted when XML or JSON schema validation fails.

W-19438092

Transmission statuses now accurately update to Error and no longer get stuck in the Processing state after multiple inbound X12 or EDIFACT validation failures.

W-19312257

The trash can icon in the Schema field no longer hides the first character of the schema file name when configuring a JSON or XML Target at Host message.

W-18895852
## [](#2-23-0)2.23.0 **August 19, 2025** This version requires a runtime template update. ### What’s New - Support for Mule runtime 4.9 Partner Manager now supports Mule runtime 4.9, which uses Java 17 only. Proactive testing of your existing environments is needed to make sure they work as expected with Java 17. - Test your component versions to make sure they exhibit the same behavior with Java 17. - Test your existing SFTP connections that rely on insecure ciphers to make sure they work as expected with Java 17. The SFTP connector now supports a different list of ciphers compared to its Java 8 counterpart. Mule runtime 4.6 remains available, and Mule 4.6 templates continue to use SFTP Connector 1.x, providing a rollback option if needed. By testing your applications on Mule 4.9 now, you can identify and resolve potential issues ahead of the end of standard support. See [CloudHub 1.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub-deployment-settings), [CloudHub 2.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub2-deployment-settings), and [Runtime Fabric デプロイメントの設定](https://docs.mulesoft.com/jp/partner-manager/latest/rtf-deployment-settings). - CloudHub 2.0 deployments now support multiple replicas per Mule Application. - You can now specify the scope for OAuth 2.0 authentication in HTTP send endpoints and the Payload Storage API. See [HTTP および HTTPS 送信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-https-send) and [ペイロードストレージ API の設定](https://docs.mulesoft.com/jp/partner-manager/latest/setup-payload-storage-API). - You can now use a URL as the query parameter value for HTTP send endpoints. See [HTTP および HTTPS 送信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-https-send). - You can now configure the retry count and interval for SFTP and FTP send endpoints. See [SFTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-sftp-receive-target) and [FTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-ftp-receive). - Partner Manager now allows you to use a hyphen as the secondary file name delimiter for AS2, SFTP, and FTP receive endpoints. - Several libraries and connectors are updated across applications in the Mule runtime engine (Mule). ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8, 4.9 with Java 17
Runtime service Version

Document processing service

3.14.0

API Replication service

1.23.0

Endpoint services

3.14.2
### [](#dependent-components-used-11)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.17.1 ### Fixed Issues
Issue Resolution ID

Paths can now be reused across HTTP inbound endpoints.

W-18722293

You can now change the deployment target from CloudHub 1.0 to CloudHub 2.0 for organizations created before Partner Manager version 2.18.0.

W-18715090

CloudHub 1.0 entitlements are no longer required for CloudHub 2.0 in Runtime Fabric settings.

W-18572633

CloudHub 2.0 vCore validation now works as expected during deployments.

W-18395858

The HTTPS option is now hidden in Partner Manager when creating AS2 Receive from Partners endpoints with CloudHub 2.0 because the option is now configured directly in CloudHub 2.0 instead of in Partner Manager.

W-18169399

Partner Manager no longer attempts to send data to the VM for recovery when Anypoint MQ returns a 413 - Payload Too Large error.

W-16895010

AccessGrant is no longer removed when editing an inbound SFTP endpoint that uses Basic or Identity key authentication.

W-18811033

Deployments no longer time out under certain circumstances.

W-18507276
## [](#2-22-3)2.22.3 **July 15, 2025** This version doesn’t require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8
Runtime service Version

Document processing service

3.13.0

API Replication service

1.22.0

Endpoint services

3.13.5
### [](#dependent-components-used-12)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.17.1 ### Fixed Issues
Issue Resolution ID

Partner Manager now allows you to create message flows with different custom schemas of the same EDI message type even if the message flows are configured with different third-party partners.

W-18892873
## [](#2-22-2)2.22.2 **June 5, 2025** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8
Runtime service Version

Document processing service

3.13.0

API Replication service

1.22.0

Endpoint services

3.13.5
### [](#dependent-components-used-13)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.17.1 ### Fixed Issues
Issue Resolution ID

All supported X12 version 4030 message types now show in the Message type dropdown.

W-18347930

Inbound AS2 messages with signatures that contain a non-standard carriage return no longer fail.

W-18489908

Apply settings now work correctly for CloudHub 2.0 environments.

W-18438558

Environment upgrades no longer fail in the first attempt due to Anypoint MQ queues.

W-18367471

The replay and acknowledgment reconciliation task performance is improved.

W-18559313
## [](#2-22-1)2.22.1 **May 12, 2025** This version doesn’t require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8
Runtime service Version

Document processing service

3.13.0

API Replication service

1.22.0

Endpoint services

3.13.0
### [](#dependent-components-used-14)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.17.1 ### Fixed Issues
Issue Resolution ID

Issues preventing deployments to some CloudHub 2.0 regions are now resolved.

W-18380406

Payload view now works as expected in EU control plane environments for newly created payload storage configurations.

W-18382545

The issue with creating AS2 and HTTPS send endpoints with port numbers from the partner profile page since the 2.22.0 release is now resolved.

W-18403689
## [](#2-22-0)2.22.0 **April 25, 2025** This version requires a runtime template update. ### What’s New - CloudHub 2.0 support You can now select a CloudHub 2.0 private or a shared space as a deployment target type for Partner Manager runtime services. See [CloudHub 2.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub2-deployment-settings). - Minimum Mule version You can now process cXML messages by setting the **Min Mule Version override** to 4.5.0 when configuring Partner Manager deployment settings in Access Management. The new option also unlocks runtime and DataWeave features in newer runtime versions via a feature flagging mechanism. See [CloudHub 1.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub-deployment-settings), [CloudHub 2.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub2-deployment-settings), and [Runtime Fabric デプロイメントの設定](https://docs.mulesoft.com/jp/partner-manager/latest/rtf-deployment-settings). - Manage deployments You can now apply changes to your Partner Manager environment settings, like Mule runtime version, minimum Mule version, and Application capacity allocation, to all of your runtime applications by using **Manage deployments** on the Message Flows page. See [メッセージフローランタイムテンプレートのアップグレード](https://docs.mulesoft.com/jp/partner-manager/latest/upgrade-message-flows). - Optionally skip source file deletion for FTP and SFTP inbound endpoints You can now skip source file deletion from FTP and SFTP endpoints when you connect with external servers that mark files as `read` after the first successful read and don’t allow clients to explicitly delete files. See [FTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-ftp-receive) and [SFTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-sftp-receive-target). - Archive file deletion after three attempts To prevent duplicate file processing, the inbound FTP and SFTP runtime application now skips the archival steps after three failed attempts. Partner Manager logs the issue in the runtime application. See [FTP 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-ftp-receive) and [SFTP 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-sftp-receive-target). - You can now include static query parameters in the URL of AS2 and HTTP send endpoints. - Additional X12 message validation rules You can now configure these X12 receive validation settings on partner profiles: - Report non-fatal errors in acknowledgments - Report segment details - Truncate values exceeding the length limits - Include trailer segment details - Include ignored segments See [インバウンド X12 メッセージの受信設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/x12-receive-read-settings). ### Compatibility
Application or Service Version

Mule

4.6.0 with Java 8
Runtime service Version

Document processing service

3.13.0

API Replication service

1.22.0

Endpoint services

3.13.0
### [](#dependent-components-used-15)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for Anypoint MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.17.1 ### Fixed Issues
Issue Resolution ID

You can now navigate to the messages list as expected when viewing transmission details for 997 acknowledgments.

W-17709667

Nonsearchable custom message attributes are no longer included in the Message attribute dropdown.

W-16799143

Inbound AS2 messages now deploy as expected for message flows with acknowledgments enabled.

W-17065605

The Date Range filter no longer fails to display all transmissions in the selected date range in some scenarios.

W-17395944

The Custom message attributes section no longer indicates there are no attributes when the section is collapsed, and attribute values are no longer truncated.

W-17654456

Messages no longer fail with message flow routing errors when associated message flows involving third-party connections are created via the Partner Manager platform API.

W-17114370

The API response performance for deployments is now improved.

W-17067909

Inbound flows for CSV Target at Host message types no longer add extra columns for items in a list that use non-comma separators.

W-18191895
## [](#2-21-1)2.21.1 **February 25, 2025** This version requires a runtime template update. ### What’s New - Anypoint MQ Connector is upgraded to version 4.0.12. - The regular expression pattern for FTP and SFTP source paths now supports additional characters. See [FTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-ftp-receive) and [SFTP Receive Endpoint Settings](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-sftp-receive-target) for more information. - UI improvements are made to the **Custom message attributes** section of the message details page. See [Tracking Individual Messages](https://docs.mulesoft.com/jp/partner-manager/latest/activity-message-tracking) for more information. ### Compatibility
Application or Service Version

Mule

4.6.0
Runtime service Version

Document processing service

3.12.2

API Replication service

1.21.1

Endpoint services

3.12.1
### [](#dependent-components-used-16)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for MQ (MQ Connector) 4.0.12 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.17.1 ## [](#2-21-0)2.21.0 **January 30, 2025** This version requires a runtime template update. ### What’s New - Identifier-based inbound routing You can now configure inbound message flows to route messages based on partner identifiers. See [Configure the Source Message Type](https://docs.mulesoft.com/jp/partner-manager/latest/create-inbound-message-flow#source-message-type) on the Creating Inbound Message Flows page for more information. - API management for AS2 receive endpoints You can now use API Manager to manage AS2 receive endpoints and apply security, rate limiting, and policies to AS2 messages received from partners. See [AS2 送信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-as2-send) for more information. - AS2 send endpoint transfer mode You can now configure the transfer mode in AS2 send endpoint settings. See [Transfer Mode](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-as2-send#transfer-mode) on the AS2 Send Endpoint Settings page for more information. - Support for additional EDI X12 versions You can now configure X12 message types with versions 2001, 2002, 2003, 2040, 8050. - Support for EDIFACT syntax version 1 You can now configure inbound and outbound EDIFACT messages with syntax **VERSION1**. - Collapse custom attributes in outbound message details Custom message attributes that contain multiple values are now collapsed when viewing outbound message details. Click **Show attributes** to view the values. See [トランスミッションの追跡](https://docs.mulesoft.com/jp/partner-manager/latest/activity-tracking) for more information. - UI improvements The Partner Manager UI is updated with improved accessibility features. ### Compatibility
Application or Service Version

Mule

4.6.0
Runtime service Version

Document processing service

3.12.1

API Replication service

1.21.0

Endpoint services

3.12.0
### [](#dependent-components-used-17)Dependent Components Used Partner Manager uses these dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.10.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.17.1 ### Fixed Issues
Issue Resolution ID

If validation fails for an incoming X12 payload, the AK4-04 or IK4-04 Copy of Data Element is now truncated in the acknowledgment when the element exceeds the length limit.

W-17015642

Technical contact details in partner profiles now appear correctly when expanded.

W-16916534

Temporary files created while processing inbound AS2 messages are now deleted in all scenarios.

W-17216717

Outbound EDIFACT transmissions are now updated to an Overdue acknowledgement status when a CONTRL acknowledgement isn’t received in the configured timeframe.

W-15805308

You can no longer create more than one message flow with different custom schemas of the same EDI message type for the same partner and receive endpoint.

W-16910795

To prevent inconsistencies in runtime application deployment, you can no longer deploy new message flows while another message flow is being deployed.

W-16225937

The Partner Manager v2 Partners API now validates the message type’s usage type when creating or updating message flows.

W-16222975

You can no longer delete a Send to Partners endpoint that’s referenced in partner-level acknowledgement settings but isn’t used in a message flow.

W-12151754

Message flow change history and audit logs now show changes that have been made to a map in a message flow.

W-16904850

Deployment issues caused by service name collisions are now resolved.

W-16686850

Inbound FTP and SFTP applications are no longer duplicated under certain circumstances.

W-16217615

The Partner Manager Tracking API now returns the correct response code when request payload or query parameter values are malformed.

W-17322625

Changes made to the retry count and retry interval settings in the Payload Storage API now persist and deploy to the runtime applications.

W-14026725

The passing of date filter selection is improved when navigating between transmission and message list screens.

W-16769220

The UI now updates the identifier for an outbound message flow when the message flow is created via an API that doesn’t have an identifier.

W-16892409

You can no longer initiate a deployment via a modified endpoint configuration when an active deployment is in progress through a certificate assignment.

W-16241955

When redeploying inbound SFTP or FTP applications, endpoints are no longer polled at the same time that the application workers are switched.

W-16953183
## [](#2-20-7)2.20.7 **November 6, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.6.0
Runtime service Version

Document processing service

3.11.9

API Replication service

1.20.3

Endpoint services

3.11.8
### [](#dependent-components-used-18)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.9.6 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

Basic auth credentials are no longer removed from AS2 send endpoint configurations when onboarding a new AS2 partner without basic auth.

W-17063147

OAuth authentication for the payload storage API now works as expected from API replication service, document processing service, and payload view from the UI.

W-16888673

Partner Manager now supports managing Message disposition notifications (MDNs) without using the carriage return and line feed (CRLF) line ending option after the end MIME part.

W-16699708
## [](#2-20-6)2.20.6 **October 8, 2024** This version doesn’t require a runtime template update. ### What’s New - All new and existing runtime template application deployments now use Mule runtime version 4.6 (Long-Term Support, Java-8). For more information, see [Runtime Fabric デプロイメントの設定](https://docs.mulesoft.com/jp/partner-manager/latest/rtf-deployment-settings) and [CloudHub 1.0 デプロイメント設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/cloudhub-deployment-settings). ### Compatibility
Application or Service Version

Mule

4.6.0
Runtime service Version

Document processing service

3.11.5

API Replication service

1.20.0

Endpoint services

3.11.2
### [](#dependent-components-used-19)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.8.8 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

You can no longer delete Payload Storage API configuration via Partner Manager platform APIs.

W-16854909
## [](#2-20-5)2.20.5 **September 25, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0, 4.6.0
Runtime service Version

Document processing service

3.11.6

API Replication service

1.20.0

Endpoint services

3.11.4
### [](#dependent-components-used-20)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.8.8 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

Non-EDI files of different message types received via SFTP and FTP endpoints within close proximity of each other no longer fail to process.

W-16664082

When you deploy changes to the Username and Password fields in SFTP send endpoints, the runtime now reflects the changes.

W-16433704

The Partner Manager v2 Partners API now validates the endpoint usage type when creating or updating message flows.

W-16561479

Custom EDI X12 and EDIFACT schemas for multiple message types, which multiple partners use to send data via a common third-party connection, now reflect correctly.

W-16588387

Custom TLS certificate validation is now applied to AS2 send endpoints that use basic authentication.

W-16634965

Partner Manager no longer references endpoints that are deleted from Partner-level acknowledgment settings.

W-12151754

Partner Manager environments that use Runtime Fabric as the deployment target can now deploy to Mule runtime 4.6.0.

W-16597601
## [](#2-20-4)2.20.4 **September 9, 2024** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0, 4.6.0
Runtime service Version

Document processing service

3.11.5

API Replication service

1.20.0

Endpoint services

3.11.2
### [](#dependent-components-used-21)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.8.8 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

Deployment of new flows and modifications to existing flows no longer time out when certain conditions are present.

W-16675205
### Known Issues
Known Issue Workaround ID

Runtime template applications fail to deploy on Mule runtime 4.6 in Runtime Fabric environments.

None

W-16597601

When you deploy changes to the Username and Password fields in SFTP send endpoints, the runtime does not reflect the changes.

Create a new send endpoint with the correct username and password and update the message flows to use the new endpoint configuration.

W-16433704
## [](#2-20-3)2.20.3 **August 27, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0, 4.6.0
Runtime service Version

Document processing service

3.11.5

API Replication service

1.20.0

Endpoint services

3.11.2
### [](#dependent-components-used-22)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.8.8 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0
You must upgrade the runtime templates of your environment to 2.20.3 before you can begin using the new features in this release.
### Fixed Issues
Issue Resolution ID

Sporadic issues that were causing acknowledgments not to be sent when duplicate checks occurred when having 997 and TA1 configured are now fixed.

W-16565659

Multiple custom schemas for different base types within the same partner or third-party are now working correctly for EDIFACT and X12 message formats.

W-16553196
### Known Issues
Known Issue Workaround ID

Mule runtime 4.6 deployments are not deploying successfully in Runtime Fabric.

None

W-16597601
## [](#2-20-2)2.20.2 **August 22, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0, 4.6.0
Runtime service Version

Document processing service

3.11.1

API Replication service

1.20.0

Endpoint services

3.11.1
### [](#dependent-components-used-23)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.8.8 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### What’s New
You must upgrade the runtime templates of your environment to 2.20.2 before you can begin using the new features in this release.
- Support for Mule 4.6.0 Partner Manager runtime template applications now support Mule runtime version 4.6.0 via the Long-term Support (LTS) release channel. - While Mule runtime version 4.4.0 is under Standard Support, you can update the environment’s deployment settings manually on the **Partner Manager Settings** page in Access Management by setting the runtime version to **4.6 (LTS)**. After the update, apply the upgrade from the Message Flows page in Partner Manager to update your runtime applications to Mule 4.6.0. See [Runtime Fabric デプロイメントの設定](https://docs.mulesoft.com/jp/partner-manager/latest/rtf-deployment-settings) for more information about updating deployment settings in Access Management. - After Mule runtime version 4.4.0 reaches the end of Standard Support, all new Partner Manager runtime application deployments and upgrades will default to Mule 4.6.0. ### Known Issues
Known Issue Workaround ID

Mule runtime 4.6 deployments are not deploying successfully in Runtime Fabric.

None

W-16597601
## [](#2-20-1)2.20.1 **August 20, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.11.1

API Replication service

1.20.0

Endpoint services

3.11.1
### [](#dependent-components-used-24)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.8.8 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

Anypoint MQ Broker URLs are now correctly mapped for all regions in the runtime application templates.

W-16428708
## [](#2-20-0)2.20.0 **July 24, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.11.1

API Replication service

1.20.0

Endpoint services

3.11.1
### [](#dependent-components-used-25)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.9.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.9.0 - Anypoint Connector for JMS (JMS Connector) 1.8.8 - Anypoint Connector for MQ (MQ Connector) 4.0.6 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### What’s New
You must upgrade the runtime templates of your environment to 2.20.0 before you can begin using the new features in this release.
- This product has a refreshed UI. This new UI brings the product visually closer to the [new visual style of Salesforce](https://www.salesforce.com/blog/salesforce-cosmos-slds-2/) and enhances consistency, accessibility, and the user experience. Changes include a refreshed navigation, icons, and colors. - Support for additional EDI X12 versions You can now configure X12 message types with versions 7060, 8010, 8020, 8030, and 8040. - Character encoding override configuration You can now configure character encoding override for the following endpoints: - FTP and SFTP source endpoints that are configured on the page. For more information, see [FTP 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-ftp-receive) and [SFTP 受信エンドポイント設定](https://docs.mulesoft.com/jp/partner-manager/latest/endpoint-sftp-receive-target). - AS2 inbound endpoints that are configured on a partner’s profile. For more information, see [AS2 インバウンドメッセージの受信設定の定義](https://docs.mulesoft.com/jp/partner-manager/latest/as2-encoding). For messages received via HTTP/s endpoints, the charset parameter in the HTTP request’s `Content-Type` header is now applied as the inbound document’s default encoding. - Custom application properties Custom application properties configured in Runtime Manager for applications deployed via Runtime Fabric are now retained when upgrading or redeploying. - Transaction updates performance The performance of transaction updates is improved. ### Fixed Issues
Issue Resolution ID

The Business Document Key field extracted from the reference mapping execution is now included in target files delivered to FTP and SFTP Target at host endpoints with a file name pattern containing the BusKey property.

W-13729500

You can no longer select latest when configuring the runtime version for Partner Manager in Access Management, but you can select a specific runtime version.

W-14497416

The value in the Custom message attribute field is now truncated after 199 characters.

W-14793863

When Custom X12 settings is selected in the X12 Settings section of an outbound message flow, Partner Manager now respects the value in the Substitution character field in the X12 Connector configuration. If the field is blank on the X12 Connector, then Partner Manager applies the substitution character configured on the partner profile.

W-14875596

You can no longer modify the CloudHub deployment region for environments that contain active message flow deployments.

W-14990783

The Runtime Fabric deployment settings in Access Management now show the same application size parameters that are configured in the Runtime Manager UI for Runtime Fabric deployments.

W-14406928

The Runtime Fabric deployment settings in Access Management now show only the Runtime Fabric targets that are available for the selected environment.

W-14794249

The Message flows page now loads successfully if the deployment settings for the environment in Access Management aren’t configured.

W-14970387
## [](#2-19-7)2.19.7 **June 14, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.10.3

API Replication service

1.19.0

Endpoint services

3.10.2
### [](#dependent-components-used-26)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

The ISA11 repetition separator in the outbound functional acknowledgment is now mapped from the original inbound X12 data payload.

W-15962484
## [](#2-19-6)2.19.6 **May 30, 2024** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.10.2

API Replication service

1.19.0

Endpoint services

3.10.2
### [](#dependent-components-used-27)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

Partner Manager now supports additional X12-ISA identifier qualifiers.

W-15762564

Styling changes are made to dropdown lists to improve the look and feel of long descriptions.

W-15804911
## [](#2-19-5)2.19.5 **May 16, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.10.2

API Replication service

1.19.0

Endpoint services

3.10.2
### [](#dependent-components-used-28)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

AS2 outbound messages no longer send an additional subject header with a null value.

W-15727463
## [](#2-19-4)2.19.4 **May 7, 2024** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.10.2

API Replication service

1.19.0

Endpoint services

3.10.1
### [](#dependent-components-used-29)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

The accessibility standards for screen readers in the Partner Manager interface are now improved.

W-15534717
## [](#2-19-3)2.19.3 **April 10, 2024** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.10.2

API Replication service

1.19.0

Endpoint services

3.10.1
### [](#dependent-components-used-30)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

Outbound EDI transmissions with multiple transactions now create multiple message records.

W-15270165

The acknowledgement reconciliation process now waits for 35 minutes instead of 6 minutes for the corresponding outbound transmission record to be created before failing.

W-15306986
## [](#2-19-2)2.19.2 **March 11, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Starting with this version, the runtime version configuration in the Access Management settings for Partner Manager is updated to Mule 4.4.0. This defaults all Partner Manager deployments to that runtime version.
Runtime service Version

Document processing service

3.10.2

API Replication service

1.19.0

Endpoint services

3.10.1
### [](#dependent-components-used-31)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

The UI styles for the Select and View payload buttons are now fixed.

W-14746447

The batch reporting performance for outbound transmission messages is now improved.

W-14801233

Substitution characters configured in custom validation settings for outbound X12 message flows are now honored.

W-14875596

The Payload view now works when the storage API uses a self-signed certificate for the TLS context.

W-14921046

The handling of transmission recoveries for XML and JSON formats is now improved.

W-15159433
## [](#2-19-1)2.19.1 **February 6, 2024** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.10.1

API Replication service

1.19.0

Endpoint services

3.10.1
### [](#dependent-components-used-32)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

The configuration for RTF application sizing is now consistent between Partner Manager and Runtime Manager.

W-14406928

RTF configuration settings now show only those Runtime Fabrics that are associated with the selected environment.

W-14659614

Editing SFTP endpoints that use Basic and Identity Key authentication now works as expected.

W-14838612

Searching Partner Manager public APIs by using spaces and date filtering now works as expected.

W-14872922
## [](#2-19-0)2.19.0 **January 25, 2024** ### What’s New You must upgrade the runtime templates of your environment to 2.19.0 before you can begin using the new features in this release. - Improved certificate management You can now select the type of certificate (private keypair, public certificate, or identity key) to add to the host, partner, or third-party connection profiles with a consistent experience. - SSH identity-key-based authentication for SFTP endpoints You can now select the additional authentication types identity key and basic + identity key, to connect with internal and external SFTP servers that require SSH-key-based authentication. Previously, Partner Manager supported only basic (username, password) authentication for SFTP endpoints. You can also update identity keys and trigger the redeployment of the endpoints that use them. - Improved TLS context for outbound AS2 endpoints You can now configure the TLS context in outbound AS2 endpoint configurations to use a self-signed SSL certificate or allow an insecure connection (recommended only for testing purposes). Previously, you could configure only CA-signed certificates for outbound AS2 endpoints. - Support for additional EDIFACT versions You can now configure EDIFACT message types with versions s93a, d16a, d16b, d17a, d17b, d18a, and d18b. - New **About** section for the host profile You can now add additional information such as your company’s logo, contact information, and more to your organization’s host profile. - Custom application properties configured in Runtime Manager for CloudHub-deployed applications are now retained during upgrades and redeployments. - You can now configure a substitution character in X12 **Send** settings to replace any characters in the outbound data payload that are used as other delimiter characters. - You can now have multiple SFTP send endpoints with the same host, credentials, and path, but with different file naming patterns. - Performance is improved for runtime applications deployed to Runtime Fabric. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.10.1

API Replication service

1.19.0

Endpoint services

3.10.1
### [](#dependent-components-used-33)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.8.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for JMS (JMS Connector) 1.8.7 - Anypoint Connector for MQ (MQ Connector) 4.0.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.13.0 ### Fixed Issues
Issue Resolution ID

Deployment failures no longer occur due to an incorrect vCore balance check.

W-10551147

You can no longer delete endpoints that are used only in the X12 or EDIFACT acknowledgment settings in a partner profile. This change prevents data processing issues.

W-13833027

The transmissions search filter for the acknowledgment status Sent now shows matching search results.

W-13835609

Self-signed certificates associated with payload storage endpoint configurations no longer remain linked to the endpoint after the certificate type is changed to a CA-signed certificate or insecure connection.

W-13875923

The delete button is no longer enabled when search filters are applied in the Message Types section of the host profile.

W-14080953

Transmission recovery is no longer retried indefinitely when outbound AS2 transmissions fail.

W-14330423

Search filters on the host page now handle spaces correctly.

W-14397901

The management of basic authentication credentials for outbound AS2 endpoints on Anypoint Platform is now improved.

W-14575004

SFTP inbound endpoint polling no longer hangs when JMS (ActiveMQ) connectivity is lost.

W-14765379
### Known Issues
Known Issue Workaround ID

You must reenter the password when editing an SFTP endpoint that has the basic and identity key authentication type. Saving the changes with the password field left blank results in a deployment failure.

None

W-14838612
## [](#2-18-7)2.18.7 **January 16, 2024** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.5

API Replication service

1.18.4

Endpoint services

3.9.2
### [](#dependent-components-used-34)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

The runtime service now has an extended timeout for Tracking API calls.

W-14801162
## [](#2-18-6)2.18.6 **December 11, 2023** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.5

API Replication service

1.18.3

Endpoint services

3.9.2
### [](#dependent-components-used-35)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

Outbound transmissions with multiple messages now process correctly when custom message attributes are defined in the message type.

W-14534597
## [](#2-18-5)2.18.5 **December 4, 2023** This version requires a runtime template update if you deploy Partner Manager runtime applications to Anypoint Runtime Fabric. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.3

API Replication service

1.18.3

Endpoint services

3.9.2
### [](#dependent-components-used-36)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

The Partner Manager runtime templates now use active-mq 5.15.16 because of security vulnerabilities with active-mq 5.15.15.

W-14495961
## [](#2-18-4)2.18.4 **November 6, 2023** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.2

API Replication service

1.18.1

Endpoint services

3.9.1
### [](#dependent-components-used-37)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

The Partner Manager upgrade process no longer erroneously starts unrelated applications based on certain naming conventions.

W-14315662

The Private port (when deploying to Anypoint VPC) checkbox now appears in the New Endpoint dialog when creating AS2, HTTP, and HTTPS receive endpoints. This issue was introduced accidentally in v2.18.2.

W-14426229
## [](#2-18-3)2.18.3 **November 1, 2023** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.2

API Replication service

1.18.1

Endpoint services

3.9.1
### [](#dependent-components-used-38)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

Message flow deployments that reference the same endpoints are no longer left in a locked state, which prevented them from being deployed.

W-14316022

Some organizations that were previously unable to access Partner Manager under MuleSoft’s new usage-based pricing and packaging can now access it.

W-14406061
## [](#2-18-2)2.18.2 **October 24, 2023** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.2

API Replication service

1.18.1

Endpoint services

3.9.1
### [](#dependent-components-used-39)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

Anypoint MQ regions are now set correctly when configuring new environments.

W-14352365
## [](#2-18-1)2.18.1 **October 17, 2023** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.2

API Replication service

1.18.1

Endpoint services

3.9.1
### [](#dependent-components-used-40)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

When saving environment-level deployment settings for older business groups, you no longer receive an error.

W-14286942

Partner Manager now applies custom EDI schemas to validations for messages sent to partners if the partners have multiple outbound message flows that use both custom and standard schemas.

W-14309676
## [](#2-18-0)2.18.0 **October 10, 2023** ### What’s New This version requires a runtime template update.
Starting with this version, on-premises standalone deployments are no longer supported.
### [](#enhanced-partner-manager-deployment-options)Enhanced Partner Manager Deployment Options This release contains enhanced Partner Manager deployment options. #### [](#runtime-fabric-deployment)Runtime Fabric Deployment You can now configure Anypoint Runtime Fabric as a deployment target for Partner Manager. This enables you to execute B2B transaction-processing workloads in a Kubernetes cluster that you create, configure, and manage. To leverage this new deployment option, you must set up an ActiveMQ messaging broker on your preferred infrastructure and configure the connection parameters in Partner Manager’s deployment settings. The Runtime Fabric deployment option was validated on Amazon Elastic Kubernetes Service (EKS). Deploying Partner Manager runtime applications on other Runtime Fabric infrastructure is currently not supported.
When deploying Partner Manager runtime applications to Anypoint Runtime Fabric, the length of the AS2 keystore can’t exceed 1024 characters, which limits the algorithm option to SHA1.
#### [](#environment-level-deployment-settings)Environment-level Deployment Settings You can now configure Partner Manager deployment settings such as the deployment target, runtime version, deployment region, and runtime capacity allocation at the individual environment level. In previous releases, you could configure deployment settings only at the business-group level. #### [](#new-ui-for-configuring-deployment-settings)New UI for Configuring Deployment Settings You now configure Partner Manager deployment settings in a new Access Management UI. #### [](#more-information)More Information For more information about Partner Manager deployment options, see [Deploying Partner Manager Runtime Apps](https://docs.mulesoft.com/jp/partner-manager/latest/deploy-partner-manager). ### [](#other-enhancements)Other Enhancements - The deployment of each environment is now shown on the Partner Manager page. - You can now remove schema files that are attached to previously-configured JSON and XML message types if you don’t need schema validation on payloads. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.9.1

API Replication service

1.18.1

Endpoint services

3.9.1
### [](#dependent-components-used-41)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

You can no longer use the same character for more than one purpose when configuring inbound CSV message types.

W-13577974

View payload links in the message details view are now easy to click, even when the corresponding file name is very long.

W-13695625

The error response code when Access Management authentication is down is now correct.

W-13806543

Partner Manager now applies schema validation to transactions in outbound message flows with JSON or XML as the target message format when a schema file is attached to the message type definition.

Because this type of validation did not happen in earlier releases, the transactions in existing message flows of this type might fail if the message payload fails during schema validation. If you believe that this could happen, consider removing the schema file association in the message type definition.

W-13915947

The outbound AS2 runtime application is now updated when you deploy a message flow after a host AS2 keystore update.

W-13968139

Functional Acknowledgements (997) generated in response to inbound EDI X12 interchanges with more than one functional group are no longer duplicated.

W-13993209

Outbound messages no longer get stuck in the Processing status after they are delivered successfully to the target endpoint.

W-14049820
## [](#2-17-0)2.17.0 **July 27, 2023** ### What’s New You must upgrade the runtime templates of your environment to 2.17.0 before you can begin using the new features in this release. These features are available only for CloudHub runtime deployments. ### [](#transmission-replay)Transmission replay - You can now replay failed or successfully-delivered B2B transmissions. When you replay a transmission, Partner Manager reprocesses the source payload as if it was received from the source again. The transmission goes through the validation, acknowledgement, transformation, and routing steps configured in the message flow at the time of replay. - Original transmissions that were replayed at least once and transmissions and messages that were created due to a transmission replay have indicators to help you understand the user actions performed on the transmissions. - You can navigate between the original transmission record and its associated replayed transmission records. - You can filter the transmission search results to show only the transmissions that contain at least one replay. - Platform administrators can see the history of user actions related to repalying transmissions in the Anypoint Access Management audit logs. ### [](#csv-delimited-file-support)CSV (Delimited) File Support - You can now configure CSV as the message format for all usage types: Receive from partners, Target at host, Source at host, and Send to partners. ### [](#acknowledgement-status-enhancements)Acknowledgement Status Enhancements - When a functional acknowledgement received from a partner contains the error code `E`, the corresponding outbound transmission’s ack status is set to `Accepted with errors`. - When a functional acknowledgement received from a partner contains the error code `P`, the corresponding outbound transmission’s ack status is set to `Partially accepted`. - When Partner Manager can’t deliver the functional acknowledgement for an inbound transmission, the ack status of the transmission is set to `Failed to send`. ### [](#other-enhancements-2)Other Enhancements - You can now configure hex codes as separator characters for outbound EDIFACT and X12 messages. You do this either from the partner’s profile or via custom settings in outbound message flows. - You can now configure JSON and XML message types without an associated schema. When processing message payloads for message types that don’t have an associated schema, no schema validation is performed. - Partner Manager now streams the data when it loads large message payloads to the payload view of the UI. - Partner certificate statuses and related color coding are improved. ### Compatibility
Application or Service Version

Mule

4.4.0
Runtime service Version

Document processing service

3.8.0

API Replication service

1.17.0

Endpoint services

3.8.0
### [](#dependent-components-used-42)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.2.0 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

The runtime template upgrade process no longer involves multiple redeployments of the same endpoint application. This results in faster upgrade completions.

W-10550475

You can no longer use spaces when configuring the base path of HTTP receive endpoints because the use of spaces in this context can cause errors.

W-12276497

Endpoints that were just edited no longer disappear from the current list view.

W-11866200

Partner Manager now validates the formatting of host names specified in SFTP and FTP endpoint configurations.

W-12731777

Partner Manager now persists a payload received via FTP as a failed transmission if the filename prefix doesn’t match a configured message type.

W-13081180

Partner Manager now compresses schema files when storing them in an object store. This enables the support of large schemas.

W-13536066
## [](#2-16-2)2.16.2 **July 5, 2023** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3.0, 4.4.0
Runtime service Version

Document processing service

3.7.3

API Replication service

1.16.1

Endpoint services

3.7.0
### [](#dependent-components-used-43)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

Partner Manager now generates a valid functional acknowledgement for an EDI v003010 transaction.

W-12776825
## [](#2-16-1)2.16.1 **June 27, 2023** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3.0, 4.4.0
Runtime service Version

Document processing service

3.7.2

API Replication service

1.16.1

Endpoint services

3.7.0
### [](#dependent-components-used-44)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.11.0 ### Fixed Issues
Issue Resolution ID

When reconciling an inbound 997 functional acknowledgment, Partner Manager now uses the function group ID to match the corresponding outbound transaction.

W-12776539

When deploying an inbound message flow for a new partner with an AS2 receive endpoint, the AS2 inbound runtime application is now updated with the certificate of the partner or third-party connection.

W-13085911

The date picker now works in the Firefox browser.

W-13204965

The message type filtering on modal selections now works as expected.

W-13608847

The segment line ending field for an Edifact outbound configuration now works as expected.

W-13609095
## [](#2-16-0)2.16.0 **May 2, 2023** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3.0, 4.4.0
Runtime service Version

Document processing service

3.7.0

API Replication service

1.16.1

Endpoint services

3.7.0
### [](#dependent-components-used-45)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.3.2 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### What’s New ### [](#search-filter-enhancements)Search Filter Enhancements - You can now search by either transmission ID or message ID in the messages search page. - You can now search by transmission ID in the transmissions search page. - You can now navigate from the transmissions list and transmission details pages to the messages list page to view the list of messages contained within the same transmission. ### [](#source-message-attributes)Source Message Attributes Attributes such as the source file name, protocol, size, and headers, along with the transmission ID and message ID are now available in a predefined variable named `b2bMessageContext`. The attributes in `b2bMessageContext` are accessible during the execution of the message type reference mapping and the transformation mapping within the message flow execution. ### [](#other-enhancements-3)Other Enhancements - The new **Associated reference identifier** field on the New Endpoint dialog enables you to associate a partner reference ID with SFTP and FTP Receive from Partners endpoints that receive non-EDI messages. If configured, the partner reference ID is available in the `b2bMessageContext` variable. Partner Manager uses the ID to route the message via the appropriate message flow when it executes the message type reference mapping. - The new **Associated message type** field on the New Endpoint dialog enables you to associate a static message type with SFTP and FTP Receive from Partners endpoints that receive non-EDI messages. Specifying an associated message type overrides the need to prefix the file names with the message type ID. All files received via the endpoint are treated as the configured message type, regardless of the file name prefix. - The activity search time period selection now has a new date-time picker. - The new **Retry interval** and **Maximum retry attempts** fields on the New Endpoint dialog enable you to configure the retry interval and count for HTTP and HTTPS Send to Partners endpoints. - The new **Acknowlege every transaction** field in the X12 receive settings on the partner page enables you to configure a validation rule that requires Partner Manager to generate detailed acknowledgements. These acknowledgements include a separate AK2/AK5 (997) segment for every received transaction set, even when all transactions are accepted. - The new `expandCustomAttributes` query parameter is now available to use when calling the Partner Manager Tracking API messages resource. Set the parameter to `true` to receive the custom message attributes within the API response. - Performance in JSON and XML message processing and schema validation steps is now improved. ### Fixed Issues
Issue Resolution ID

Sporadic JSON and XML schema validation errors no longer occur.

W-10735624

Partner Manager now creates message records when outbound transactions fail in validation.

W-11294561

The AS2 certificate expiry date is now enforced when processing inbound and outbound AS2 messages so that Partner Manager rejects transmissions after the certificates expire.

You can disable the Enforce AS2 certificate expiration date field in the global AS2 receive and send settings in the host profile if your organization doesn’t need to enforce the expiry date.

W-11764062

You can now select HTTPS send endpoints with self-signed SSL certificates when editing an existing message flow.

W-12214761

The Technical Acknowledgement (TA1) section no longer shows as Processing when there is no actual TA1 sent in response to inbound EDI X12 transactions.

W-12266629

Changes to certificate configurations in the payload storage API configuration now take effect in the runtime services.

W-12500180

The character encoding override in EDIFACT receive settings now enables the processing of inbound data payloads with certain non-printable characters.

W-12659240

The Receive from Partners endpoint name is now displayed even when there are errors processing the received data payload.

W-12685704
## [](#2-15-3)2.15.3 **April 13, 2023** This version does not require a runtime template update. ### [](#compatibility-46)Compatibility
Application or Service Version

Mule

4.3, 4.4
Runtime service Version

Document processing service

3.6.2

API Replication service

1.15.0

Endpoint services

3.6.2
### [](#dependent-components-used-46)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### Fixed Issues
Issue Resolution ID

The performance of tracking updates is improved.

W-12733721

The default connection timeout values for FTP and SFTP receive endpoints is increased.

W-13004882
## [](#2-15-2)2.15.2 **March 22, 2023** This version requires a runtime template update. ### [](#compatibility-47)Compatibility
Application or Service Version

Mule

4.3, 4.4
Runtime service Version

Document processing service

3.6.2

API Replication service

1.15.0

Endpoint services

3.6.2
### [](#dependent-components-used-47)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### What’s New - Fonts in the GUI are updated to improve legibility, localization, and site performance. ## [](#2-15-1)2.15.1 **March 6, 2023** This version requires a runtime template update. ### [](#compatibility-48)Compatibility
Application or Service Version

Mule

4.3, 4.4
Runtime service Version

Document processing service

3.6.2

API Replication service

1.15.0

Endpoint services

3.6.1
### [](#dependent-components-used-48)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### Fixed Issues
Issue Resolution ID

The Deploy button is no longer enabled for endpoints with no updates.

W-12450398

Upgrading from versions older than 2.15 no longer results in sporadic partner identification errors during the upgrade.

W-12461023

Translated payloads with SFTP, FTP, HTTP, and HTTPS target endpoints are now visible even when there are failures in delivering the files to the endpoint.

W-12486096

Changes in the certificate settings of the payload storage API configuration now get deployed to the runtime service when a message flow is deployed.

W-12500162, W-12500180

Clicking the browser’s Back button after switching from the Transmissions view to the Messages view no longer causes an error.

W-12556405

Changes made to the Deploy HTTP/AS2 apps to private port option on the Partner Manager Settings page in Access Management are now saved.

W-12588215
## [](#2-15-0)2.15.0 **January 24, 2023** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3, 4.4
Runtime service Version

Document processing service

3.6.0

API Replication service

1.15.0

Endpoint services

3.6.0
### [](#dependent-components-used-49)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.1 - Anypoint Connector for FTP Connector (FTP Connector) 1.8.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.7.1 - Anypoint Connector for MQ (MQ Connector) 3.1.7 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.6.0 - Anypoint Connector for X12 (X12 Connector) 2.9.1 ### What’s New - You can now update endpoint configurations and deploy the changes with simple steps. Note: Before making endpoint updates, you must upgrade your runtime templates to the latest version. - Inbound HTTP endpoint applications now return the unique Partner Manager transmission ID in the HTTP response header, `x-apm-trx-id`. - Partner Manager is now compatible with Mule runtime 4.4. Note: To deploy your applications with Mule runtime 4.4, you must explicitly select Mule runtime 4.4 in the **Use latest version** option in the Partner Manager Settings page. - Seconds are now shown in transmission and message views. - Improvements in overall UI and cache performance in runtime applications for environments with a high volume of partners. ### [](#upgrading-to-mule-runtime-4-4)Upgrading to Mule Runtime 4.4 Partner Manager 2.15.0 is compatible with Mule 4.4. To take advantage of the new features and fixed issues, upgrade to the latest Partner Manager templates, and deploy runtime applications with Mule 4.4: 1. In Access Management, go to **Partner Manager Settings** and select either **Use latest version** or **4.4.0**. 2. In Partner Manager, from a non-production environment, in the **Message Flows** page, click **Upgrade deployments** to upgrade to the latest templates. 3. Run the necessary validation tests for your apps. 4. Repeat Step 2 in the production environment to deploy your runtime apps to production. If you don’t want to move your apps to Mule 4.4 at this time, you can follow the previous steps 2-4 to upgrade the runtime templates only and stay on Mule 4.3. Then, when you are ready to deploy your apps on Mule 4.4: 1. In Runtime Manager, individually update each application to 4.4 in a non-production environment. 2. Run the necessary validation tests for your apps. 3. After the tests complete successfully, in Runtime Manager, individually update each runtime application to 4.4 in the production environment. 4. In Access Management, go to **Partner Manager Settings** and select either **Use latest version** or **4.4.0**. ### Fixed Issues
Issue Resolution ID

EDIFACT Write errors now display in the Activity view.

W-10979350

The HTTP outbound endpoint now sets the proper EDI content-type for acknowledgements.

W-11625856

DPS now successfully processes message flows for message types that contain many message flows.

W-12353584

API /endpoints operation now works as expected when sending the id field in the request body.

W-11762359

Pagination headers in endpoints are now forwarded as expected.

W-11836174

You can now open activities and endpoint details in orgs that contain many transmissions and endpoints.

W-12390876

New endpoints are now shown on the partners view without having to refresh the window.

W-12276355

Incremental numbers for keystore names are now displayed correctly.

W-12273189

Message types with empty mappings can no longer be created.

W-11989574

Granular permissions are now handled properly in the UI.

W-10728666 / W-10550424
## [](#2-14-3)2.14.3 **November 29, 2022** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
Runtime service Version

Document processing service

3.5.2

API Replication service

1.14.0

Endpoint services

3.5.1
### [](#dependent-components-used-50)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues
Issue Resolution ID

When you select an AS2 receive endpoint for an inbound message flow, third-party names now load faster than previously.

W-10550219

The Partners and Message Flow pages now load faster than previously.

W-11954939
## [](#2-14-2)2.14.2 **October 17, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
Runtime service Version

Document processing service

3.5.2

API Replication service

1.14.0

Endpoint services

3.5.1
### [](#dependent-components-used-51)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues
Issue ID

The View Host, Partners and Message Flows user permission now works as expected.

W-11801440

The performance of partner profile retrieval for AS2 endpoints has improved to prevent timeouts.

W-11810082

Inbound functional acknowledgements now get reconciled with the corresponding outbound messages.

W-11831508

Message flows with HTTP Send endpoints no longer have issues deploying to the EU control plane.

W-11894143
## [](#2-14-1)2.14.1 **October 3, 2022** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
Runtime service Version

Document processing service

3.5.1

API Replication service

1.14.0

Endpoint services

3.5.0
### [](#dependent-components-used-52)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues
Issue ID

The performance for retrieving message types in large environments is now improved.

W-11766796
## [](#2-14-0)2.14.0 **September 12, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
Runtime service Version

Document processing service

3.5.1

API Replication service

1.14.0

Endpoint services

3.5.0
### [](#dependent-components-used-53)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.7.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New You can now use the following EDI versions when configuring partner message types: - **X12 UCS**: 003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS - **X12 VICS**: 003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS - **EDIFACT**: D96B ### Fixed Issues
Issue ID

Users can now use the greater-than sign character (>) as a data element separator.

W-11102644

Users can now consistently select values from the AS2 Sender drop-down menu.

W-11606268
## [](#2-13-1)2.13.1 **August 16, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-54)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues
Issue ID

You can now configure an EDIFACT identifier without an associated qualifier by selecting NONE: Not used in the Qualifier field.

W-11032400

The Content-Type header on an outbound HTTP call is now sent with the correct values.

W-11386502, W-11437993

Inbound EDIFACT messages received via FTP in on-premises runtimes are now processed correctly.

W-11529737
## [](#2-13-0)2.13.0 **July 20, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-55)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New You can now update your organization’s AS2 keystore with a new certificate and private key pair when the certificate is about to expire. ### Fixed Issues
Issue ID

The status of inbound EDI messages that fail to parse is now set to Failed.

W-10550091

Users can now create an outbound message flow when the message flow’s reference ID stops being used in another message flow. Partner Manager previously rejected outbound message flows under these circumstances.

W-10550390

In customer-hosted Mule runtimes, the content type is now sent on outbound HTTPS calls.

W-11330247

The status of outbound transmissions that failed due to connectivity issues no longer shows as Processing in the messages view.

W-11302565, W-11352396

Clicking Source payload and Target payload on the message details page now opens the payload in a separate browser tab when a payload view URL is configured in the payload storage settings.

W-11367736
## [](#2-12-0)2.12.0 **June 22, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-56)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New #### [](#custom-message-attributes)Custom Message Attributes You can extract key fields from messages processed by Partner Manager in Mule runtime engine and define them as custom message attributes that users can search. For example, you can extract order numbers and invoice numbers from transactions and define them as custom message attributes. You can upload a DataWeave file that maps custom attributes when defining the Receive from Partners and Source at Host message types. #### [](#messages-view)Messages View The **Activity** page now provides a message-level view that displays individual transactions contained within the same X12 or EDIFACT interchange as separate records in a tabular format. The message-level view enables you to view the post-translated payloads of the inbound messages in the message details page. The view includes a filter that enables you to search for a specific custom message attribute label and value, such as an order number or an invoice number. The search results include all of the messages that contain attributes that match the search criteria. ### Fixed Issues
Issue ID

Sporadic issues in which AS2 inbound messages fail in customer-hosted Mule runtimes no longer occur.

W-10936394

Selecting a valid value for the Test Indicator field in the EDIFACT send settings no longer causes transactions to fail in Mule runtime.

W-11019452

The load times of partners, message flows, and activity pages are now improved.

W-11208963

The activity status no longer shows an unknown error when every transaction in an incoming EDI interchange fails validation.

W-11233322

Sporadic issues when processing files from FTP receive endpoints in customer-hosted runtime environments no longer occur.

W-11308281
## [](#2-11-1)2.11.1 **May 23, 2022** This version requires a runtime template update for customer-hosted runtime environments. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-57)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### Fixed Issues
Issue ID

XML messages received via HTTP endpoints in customer-hosted runtimes no longer fail in the schema validation step.

W-10962247 and W-11092812
## [](#2-11-0)2.11.0 **April 21, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-58)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.6.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.8.2 ### What’s New - You can now enable code set validations for inbound and outbound EDI X12 and EDIFACT messages exchanged with partners. - When viewing raw EDI message payloads without line breaks between segments, you can now wrap the payload by specifying the segment delimiter character. - You can now configure a segment line ending character to apply to the last segment of outbound X12 and EDIFACT payloads. - You can now change the number of results shown per page on the following pages: - Activity - Partners - Message flows - You can now use the **Back** button to navigate from the transmission details page back to the search results page without losing the search context. - The unique transmission ID of Partner Manager is now visible on the transmission details page. ### Fixed Issues
Issue ID

When calling the payload storage API from Mule runtime engine, local retries are now more reliable.

W-10883633

Improved navigation between pages in the transaction activity screen.

W-10550023

Original name of the reference mapping file in the message type definition is now retained.

W-10550162

Transaction activity search performance is now improved.

W-10809387

Transmission steps are now displayed in the correct order.

W-10550336

Security level configurations are now enforced when creating AS2 receive endpoints.

W-10550076

AS2 endpoint URLs are now consistent.

W-10550112

Message type names are now validated correctly.

W-10550396

Pagination under high load now works correctly.

W-10550023
## [](#2-10-4)2.10.4 **March 23, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-59)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues
Issue ID

Changes in Payload Storage API configurations now take effect when a message flow is deployed successfully.

B2BSOLUT-3940

Runtime applications are now redeployed only when the referenced AS2 endpoint has a dependency on a new certificate that is not in the runtime application. Previously, inbound and outbound AS2 runtime applications were redeployed with the deployment of every message flow that referenced AS2 endpoints.

B2BSOLUT-6050

Improved the ability of the message flow deployment service to detect possible issues with incomplete build files.

B2BSOLUT-6186

Validation errors that occur in the X12 Write operation are now shown in the Activity screen.

B2BSOLUT-6298

Endpoint names are now included in the runtime application logs for FTP Receive endpoints.

B2BSOLUT-6337

Filters no longer get lost when you navigate between pages in the Activity screen.

W-10782902

Functional acknowledgements (997) generated for inbound X12 messages now use the delimiter characters configured in the partner’s X12 send settings.

W-10842929
## [](#2-10-3)2.10.3 **February 16, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-60)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues
Issue ID

Sporadic issues no longer occur with transmission status updates in the control plane or with the API replication service when there are high message volumes.

W-10668852
## [](#2-10-2)2.10.2 **February 11, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-61)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues
Issue ID

Some MDNs with binary encoding failed to process and did not properly persist in payload storage.

B2BSOLUT-6345 and B2BSOLUT-6384
## [](#2-10-1)2.10.1 **January 7, 2022** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3
### [](#dependent-components-used-62)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.5.2 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.7.3 ### Fixed Issues
Issue ID

Partner-specific endpoints did not always appear in the endpoint selector window due to caching issues.

B2BSOLUT-6107

Binary message disposition notifications (MDNs) received by AS2 send endpoints were not persisted in payload storage.

B2BSOLUT-6199

SFTP and FTP send endpoint apps failed when writing files to the root directory.

B2BSOLUT-6295

When navigating to the Message flows page by clicking a message flow count link on the Partners page, the Message flows page listed the message flows for all partners. It should have only listed the message flows for the partner associated with the link.

B2BSOLUT-6304

Upgraded library dependencies for EDIFACT EDI Connector and the X12 EDI Connector.

B2BSOLUT-6315
## [](#2-10-0)2.10.0 **December 17, 2021** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-63)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### What’s New - Partner Manager now paginates lists on the following pages, making it easier to navigate across all transactions, partner configurations, and message flow configurations: - **Activity** page - **Partners** page - **Message flows** page - You can now configure basic (username and password) authentication on AS2 send endpoints to meet partner requirements. - You can now configure AS2 receive endpoints with the HTTP protocol for deploying to CloudHub. ### Fixed Issues
Issue ID

Improved the integration with Anypoint Security secrets manager for storing secured configurations and certificates.

B2BSOLUT-6146

Improved the circuit breaker mechanism in the API replication service template to support longer downtimes.

B2BSOLUT-6256

Improved the runtime templates for on-premises deployments.
## [](#2-9-2)2.9.2 **November 12, 2021** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-64)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### Fixed Issues
Issue ID

In some cases, the X12 functional acknowledgement reconciliation used the interchange control number instead of a group control number to match outbound messages.

B2BSOLUT-5902

Partner Manager sent sync message disposition notifications (MDNS) and async MDNs when the sender explicitly requested async MDNs for AS2 inbound messages.

B2BSOLUT-6054

Partner Manager did not send EDIFACT CONTRL acknowledgements when received messages failed in validation.

B2BSOLUT-6106

AS2 outbound messages that did not request receipts expected MDNs in response.

B2BSOLUT-6151

Partner Manager did not set security level requirements for AS2 receive endpoints created prior to release 2.9.0.

B2BSOLUT-6212

The Activity page hung when selecting a From Date value seven days before the daylight savings time change date.

B2BSOLUT-6222
## [](#2-9-1)2.9.1 **November 2, 2021** This version requires a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-65)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### Fixed Issues
Issue ID

Some partners were unable to process AS2 messages sent from Partner Manager.

B2BSOLUT-6194
## [](#2-9-0)2.9.0 **October 28, 2021** This version requires a runtime template update. ### What’s New - Partner Manager now supports JSON and XML formats as Receive from partners and Send to partners message types. - You can now receive inbound B2B transactions from partners via HTTP and HTTPS endpoints. - You can now use API Manager to secure and govern Receive from partners and Source at host HTTP and HTTPS receive endpoints. - You can now specify security level requirements for AS2 receive endpoints so that Partner Manager rejects incoming messages that are not signed or encrypted. - The Content-Type header is now passed on payloads sent to AS2, HTTP, and HTTPS endpoints. - Inbound and outbound AS2 Message Disposition Notifications (MDNs) are now visible on the Activity page. - You can now configure a secondary payload storage API URL that you can use to view the payload on the Activity page if the payload storage API is restricted to your internal network. - Partner Manager now supports using a group control number as a property placeholder for send endpoint file naming patterns. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-66)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 6.2.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.4.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.4 ### Fixed Issues
Issue ID

API key authentication was not enforced as configured in HTTP or HTTPS receive endpoints.

B2BSOLUT-5827

Configured AS2 outbound file name and subject headers were not sent to partner endpoints.

B2BSOLUT-5941

Runtime AS2 apps were not updated when new certificates were assigned in the partner profile.

B2BSOLUT-5989

The message flow runtime upgrade process was automatically triggered under some conditions.

B2BSOLUT-6013
## [](#2-8-6)2.8.6 **October 1, 2021** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-67)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues
Issue ID

Under certain conditions, Partner Manager left message flows in an inconsistent state.

B2BSOLUT-6023
## [](#2-8-5)2.8.5 **September 28, 2021** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-68)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues
Issue ID

The outbound AS2 service failed to parse the binary-encoded MDNs returned by partners.

B2BSOLUT-5983
## [](#2-8-4)2.8.4 **September 14, 2021** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-69)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues
Issue ID

Users could not upgrade earlier environments that contained references to inactive endpoints.

B2BSOLUT-5899
## [](#2-8-3)2.8.3 **September 9, 2021** ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-70)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues
Issue ID

Some inbound X12 transactions within batched interchanges were failing with a processing initialization failure.

B2BSOLUT-5886

Translated outbound EDI message payloads were not visible in the UI when unable to deliver data to partner AS2 endpoints.

B2BSOLUT-5876

CONTRL functional acknowledgments were not generated for some inbound EDIFACT messages.

B2BSOLUT-5923

997 functional acknowledgments were not generated for some inbound X12 messages.

SE-22607

The Transmission section was not shown in the Activity detail while retrying to deliver documents to SFTP, FTP, and HTTP target endpoints.

B2BSOLUT-5888
## [](#2-8-2)2.8.2 **August 18, 2021** This version does not require a runtime template update. ### Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-71)Dependent Components Used Partner Manager uses the following dependent components: - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 ### Fixed Issues
Issue ID

Users could not log into Partner Manager from new business groups.

B2BSOLUT-5899
### [](#limitations)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-8-1)2.8.1 **August 13, 2021** ### [](#compatibility-72)Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-72)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#fixed-issues-69)Fixed Issues - Some outbound X12 **Write** operations failed due to object store issues. ### [](#limitations-2)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-8-0)2.8.0 **August 12, 2021** ### [](#compatibility-73)Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-73)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.3 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.6.1 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#new-features)New Features - A new partner type, 3rd party connection, enables you to configure and manage identifiers and endpoints for connecting with data aggregators such as 3PLs and VANs. - Improved X12 and EDIFACT message validation error reporting. - Enhanced auto-generated endpoint names. - Improved accessibility standards in the Partner Manager interface, including: - Colors with better contrast for button hover states, links to rate and review assets, and search fields - Typehead styles - Focus states for certain menus and buttons - Dropdown menu styles - Page title field styles ### [](#fixed-issues-70)Fixed Issues - Status of some transmissions remained as `Processing`, even though the messages processed successfully (B2BSOLUT-5521). - Some transactions within an inbound interchange intermittently failed to process with the error `Message processing initialization failed when processing inbound messages` (B2BSOLUT-5728). - Some outbound messages failed in the X12 **Write** operation due to an object store error (B2BSOLUT-5748). - Retry configurations for AS2 send endpoints were not honored (B2BSOLUT-5559). - Translated outbound EDI message payloads were not visible in the UI when unable to deliver the data to partner SFTP, FTP and HTTP(s) endpoints (B2BSOLUT-5757). - Translated inbound application message payloads were not stored in the payload storage (B2BSOLUT-5743). - File name patterns for send endpoints were not validated against allowed mask placeholders (B2BSOLUT-5877). - Optimized the retry attempts and intervals for SFTP and FTP send endpoints to avoid repeated retries for prolonged duration (B2BSOLUT-5719). - Could not use the value `0` for retry attempts in AS2 send endpoint configurations (B2BSOLUT-5798). - Unable to save the character set encoding ‘PLATFORM’ in X12 receive settings (B2BSOLUT-5817). - Unable to create EDI identifiers with two-character values (B2BSOLUT-5818). - Unable to add new AS2 identifiers from the AS2 send endpoint creation dialog (B2BSOLUT-5846). ### [](#limitations-3)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-7-1)2.7.1 **July 6, 2021** ### [](#compatibility-74)Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-74)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#fixed-issues-71)Fixed Issues - Outbound message flows with custom EDI schemas did not apply custom EDIFACT schemas at runtime (B2BSOLUT-5689). - The host AS2 keystore was deleted when users deleted an AS2 endpoint (B2BSOLUT-5658). - Change log activity in the message flow details showed incorrect user names (B2BSOLUT-5298). - Transactions with non-fatal message validation errors showed as failed messages in activity reporting (B2BSOLUT-5596). - Caching issues occurred when receiving X12 and EDIFACT messages from the same partner concurrently (B2BSOLUT-5695). - Fixed issues with template runtime version upgrade behavior (B2BSOLUT-5699, B2BSOLUT-5740). - Partner Manager attempted to send functional acknowledgements (997) when processing inbound 997s if partner level acknowledgements were enabled in the X12 settings (B2BSOLUT-5520). - Inbound files with certain extension types did not process successfully in on-premises Mule runtime environments (B2BSOLUT-5423). - Minor UI fixes. ### [](#limitations-4)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-7-0)2.7.0 **June 15, 2021** ### [](#compatibility-75)Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-75)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for FTP Connector (FTP Connector) 1.5.3 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.4.0 - Anypoint Connector for X12 (X12 Connector) 2.5.8 - Anypoint Connector for EDIFACT (EDIFACT Connector) 2.3.0 ### [](#new-features-2)New Features - Support for exchanging B2B transactions with trading partners in the UN/EDIFACT message format. - Functional acknowledgment (CONTRL) generation and reconciliation for EDIFACT messages. - Support for exchanging B2B transactions with trading partners via the FTP transport protocol. - You can now give custom EDI schema definitions user-defined names for easier reference and reuse in message flows (B2BSOLUT-5420). ### [](#fixed-issues-72)Fixed Issues - Outbound message flows with custom EDI schemas did not apply custom X12 schemas in runtime (B2BSOLUT-5421). - More than one outbound message flow for the same partner could not have custom X12 message validation settings (B2BSOLUT-5380). - Internal worker URLs of AS2/HTTP received endpoints deployed to private ports in CloudHub VPC (B2BSOLUT-5650). ### [](#limitations-5)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premise Mule runtimes. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-6-2)2.6.2 **April 13, 2021** ### [](#compatibility-76)Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-76)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-3)New Features None. ### [](#fixed-issue)Fixed Issue In some environments with older message flows, new message flows did not load. (SE-19795) ### [](#known-issues-5)Known Issues None. ### [](#limitations-6)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions will fail if deployed to an on-premise Mule runtime engine. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-6-1)2.6.1 **March 31, 2021** ### [](#compatibility-77)Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-77)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-4)New Features None. ### [](#fixed-issues-73)Fixed Issues - Functional acknowledgements (997) are sent even when inbound transactions are rejected due to validation errors. (B2BSOLUT-5449) - Endpoints to send TA1 acknowledgements are deployed when inbound message flows are deployed. (B2BSOLUT-5414) - Message flow deployments no longer fail because of undeployed non-Partner Manager applications in the environment. (B2BSOLUT-5454) ### [](#known-issues-6)Known Issues None. ### [](#limitations-7)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions will fail if deployed to on-premise Mule runtime engine. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-6-0)2.6.0 **March 25, 2021** ### [](#compatibility-78)Compatibility
Application or Service Version

Mule

4.3 and later
### [](#dependent-components-used-78)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.2 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-5)New Features - New configuration to deploy AS2, HTTP, and HTTPS listener endpoints to a private port when deploying to CloudHub VPC. - Generic runtime applications for SFTP receive, SFTP send, HTTP send, and HTTPS send endpoints through dynamic configurations. - New filters for transactions in the **Activity** page: `Partner name`, `Partner message type`, `Host message type`, and `Message processing status`. - New file name pattern for SFTP receive endpoints. - Several minor bug fixes and improvements. ### [](#fixed-issues-74)Fixed Issues Users are no longer required to import the host organization’s AS2 certificate in each AS2 send endpoint configuration. You can now create an AS2 host keystore to save the host AS2 certificate and private key for reuse across different AS2 endpoints. ### [](#known-issues-7)Known Issues None. ### [](#limitations-8)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions will fail if deployed to on-premise Mule runtime engine. - Key-based authentication for SFTP transport is currently not supported. ## [](#2-5-3)2.5.3 **February 9, 2021** ### [](#compatibility-79)Compatibility
Application or Service Version

Mule

4.2.2 and later
### [](#dependent-components-used-79)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-6)New Features None. ### [](#fixed-issues-75)Fixed Issues Message flow deployments no longer fail when the Payload Storage API configuration is modified and redeployed. ### [](#known-issues-8)Known Issues None. ### [](#limitations-9)Limitations None. ## [](#2-5-2)2.5.2 **December, 11 2020** ### [](#compatibility-80)Compatibility
Application or Service Version

Mule

4.2.2 and later
### [](#dependent-components-used-80)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-7)New Features None. ### [](#fixed-issues-76)Fixed Issues Fixed the issue of XML/JSON schema-validation errors in standalone Mule runtime instances on Windows servers. ### [](#known-issues-9)Known Issues None. ### [](#limitations-10)Limitations None. ## [](#2-5-1)2.5.1 **November 25, 2020** ### [](#compatibility-81)Compatibility
Application or Service Version

Mule

4.2.2 and later
### [](#dependent-components-used-81)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-8)New Features None. ### [](#fixed-issues-77)Fixed Issues - When no outbound transaction matches the control numbers specified in the 997 functional acknowledgments received from trading partners, the transform process now ignores the EDI Acknowledgement. - If an outbound message flow for a specific partner and message type exists, you can now create a different outbound message flow for the same partner and message type using a different host-reference identifier. - When viewing identifiers in the **Message Flow** page, issues no longer occur. - When the payload storage API configuration is modified, the template upgrade deployment process now leverages an API replication service to push the selected configuration changes to the application runtime. - When connecting to your trading partner’s AS2 endpoint configurations to transmit AS2 messages, connection timeouts are now used in the runtime. ### [](#known-issue)Known Issue When connecting to your trading partner’s AS2 endpoints to transmit AS2 messages, the runtime limits connection retry attempts to 20 every two minutes. ### [](#limitations-11)Limitations None. ## [](#2-5-0)2.5.0 **November 13, 2020** ### [](#compatibility-82)Compatibility
Application or Service Version

Mule

4.2.2 and later
### [](#dependent-components-used-82)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.1 - Anypoint Connector for AS2 (AS2 Connector) 5.1.4 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.23 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.10 - Anypoint Connector for X12 Connector (X12 Connector) 2.5.2 ### [](#new-features-9)New Features - X12 outbound messaging You can now exchange B2B transactions bidirectionally with your trading partner ecosystem: - Receive inbound EDI transactions and integrate with your backend systems as JSON or XML application messages. - Receive JSON or XML application messages from your backend systems and send to your trading partners as EDI X12 transactions. - Acknowledgement reconciliation Partner Manager reconciles the inbound functional acknowledgements received from trading partners and updates the corresponding outbound transaction’s acknowledgment status. - Support for XML message format for backend integrations You can now use XML as the target message format in inbound flows and source message format in outbound flows for integration with your backend systems. - Deployment upgrades You can easily upgrade your deployed message flows to take advantage of new features in the latest Mule release. - X12 Conditional relationship validation You can configure the X12 message validation settings to enable and disable X12 conditional relationship validation on inbound and outbound transactions to improve X12 compliance in the EDI messages you are exchanging with your trading partners. - Improved transaction search with additional search filters for: - Direction type of the transmission - From Date timestamp - To Date timestamp - Acknowledgement status of the transmission - Improved X12 error reporting Reporting of validation errors is now at the segment and element levels. - Improved configuration management for endpoints and message types Message types configured in Partner Manager are categorized based on usage. They are available for reuse across message flows for all trading partners. You can assign ownership to endpoint configurations for controlled reuse. - Dynamic file name patterns for send endpoints You can configure the file name pattern on send endpoints based on the requirements of your backend systems or your trading partners. ### [](#fixed-issues-78)Fixed Issues None. ### [](#known-issue-2)Known Issue When connecting to your trading partner’s AS2 endpoints to transmit AS2 messages, the runtime limits you to three connection retry attempts every 10 seconds. Additionally, each connection retry attempt times out after 10 seconds. ### [](#limitations-12)Limitations - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing EDI data received from trading partners to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premises Mule instances. - Virtual Private Cloud and Dedicated Load Balancer are currently not supported for CloudHub deployments. ## [](#2-4-5)2.4.5 **August 28, 2020** ### [](#compatibility-83)Compatibility
Application or Service Version

Mule

4.2.2 and later

Google Chrome

77 and later

Firefox

69 and later
### [](#dependent-components-used-83)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-10)New Features None. ### [](#fixed-issue-2)Fixed Issue Fixed the issue that caused TA1 acknowledgment payloads to not be saved for message flows deployed in CloudHub. ### [](#known-issues-10)Known Issues None. ### [](#limitations-13)Limitations None. ## [](#2-4-4)2.4.4 **July 29, 2020** ### [](#compatibility-84)Compatibility
Application/Service Version

Mule

4.2.2 and later

Google Chrome

77 and later

Firefox

69 and later
### [](#dependent-components-used-84)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-11)New Features None. ### [](#fixed-issue-3)Fixed Issue Fixed the Anypoint MQ region mapping for the EU Frankfurt region. ### [](#known-issues-11)Known Issues None. ### [](#limitations-14)Limitations None. ## [](#2-4-3)2.4.3 **July 15, 2020** ### [](#compatibility-information)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-support-for-anypoint-partner-manager)Browser Support for Anypoint Partner Manager Use Anypoint Partner Manager with the latest version of any of the supported browsers: - Microsoft Edge with Chromium - Microsoft Edge without Chromium (supported through December 31, 2020) - Google Chrome - Mozilla Firefox - Safari Browser support for Anypoint Platform follows the Salesforce Lightning Experience Policy. ### [](#dependent-components-used-85)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-12)New Features None. ### [](#fixed-issues-79)Fixed Issues None. ### [](#known-issues-12)Known Issues None. ### [](#limitations-15)Limitations None. ## [](#2-4-2)2.4.2 **June 25, 2020** ### [](#compatibility-information-2)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-compatibility)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-86)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-13)New Features None. ### [](#fixed-issue-4)Fixed Issue Updated the NodeJS version with the latest security patches (B2BSOLUT-4213). ### [](#known-issues-13)Known Issues None. ### [](#limitations-16)Limitations None. ## [](#2-4-1)2.4.1 **June 8, 2020** ### [](#compatibility-information-3)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-compatibility-2)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-87)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-14)New Features None. ### [](#fixed-issue-5)Fixed Issue Fixed runtime engine issues in the Document Processing Service that caused unnecessary retries of send tracking messages. ### [](#known-issues-14)Known Issues None. ### [](#limitations-17)Limitations None. ## [](#2-4-0)2.4.0 **May 28, 2020** ### [](#compatibility-information-4)Compatibility Information Mule runtime engine 4.2.2 and later ### [](#browser-compatibility-3)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-88)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-15)New Features - Enhanced security with granular role-based access control with permissions - Ability to set the CloudHub deployment region for Partner Manager - Ability to select and view endpoint details from the endpoints list ### [](#fixed-issues-80)Fixed Issues - Functional acknowledgements are now generated when all the transaction sets in the Functional Group are rejected. - AK2 and AK5 segments are now included when returning a functional acknowledgment for an unsupported transaction set. ### [](#known-issues-15)Known Issues None. ### [](#limitations-18)Limitations - Sending outbound B2B messages to trading partners is not supported. - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used during routing to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to an on-premise instance of Mule. - Virtual Private Cloud and Dedicated Load Balancer are currently not supported for CloudHub deployments from Partner Manager. ## [](#2-3-0)2.3.0 **April 30, 2020** ### [](#compatibility-information-5)Compatibility Information Mule runtime engine 4.2.2 ### [](#browser-compatibility-4)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-89)Dependent Components Used - Anypoint Connector for MQ (MQ Connector) 3.1.0 - Anypoint Connector for AS2 (AS2 Connector) 5.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.17 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.7 - Anypoint Connector for X12 Connector (X12 Connector) 2.2.0 ### [](#new-features-16)New Features - Deployment to CloudHub You can now deploy your B2B message flows to the MuleSoft-hosted CloudHub platform. You can select the deployment target for your business group (CloudHub or your own hosted Mule runtime) by navigating to the Partner Manager settings page in Access Management. - Enhanced AS2 protocol support Added support for additional signing and encryption algorithms for secured B2B transmissions with your trading partners over the AS2 transport protocol. - Support for additional X12 versions Added support for X12 versions 006010, 006030, 006040, 006050, 007010, 007020, 007030, 007040, and 007050. ### [](#fixed-issues-81)Fixed Issues - If a user logs out of an Anypoint Platform session while a B2B message flow deployment is in progress, the deployment continues to completion. (B2BSOLUT-2682) - Special characters can now be used in the search bar. (B2BSOLUT-3118) ### [](#known-issues-16)Known Issues None. ### [](#limitations-19)Limitations - Sending Outbound B2B messages to trading partners is not supported. - DataWeave maps must be created in Anypoint Studio. - The X12 GS identifiers are currently not used while routing to message flows. X12 message routing is based on a unique combination of the X12 ISA and the message type, such as X12 850. - When the content storage API is unavailable or incorrectly configured, B2B transactions fail when deployed to on-premise Mule. - Virtual Private Cloud and Dedicated Load Balancer are currently not supported for CloudHub deployments from Partner Manager. ## [](#2-2-0)2.2.0 **January 11, 2020** ### [](#compatibility-information-6)Compatibility Information Mule runtime engine 4.2.2 ### [](#browser-compatibility-5)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-90)Dependent Components Used - Anypoint Connector for AS2 (AS2 Connector) 4.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.11 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.2 - Anypoint Connector for X12 Connector (X12 Connector) 2.1.1 ### [](#new-features-17)New Features - View and search for endpoints You can now view a list of endpoints from both the host and partner profile pages. The endpoints are searchable by: - The name of the endpoint - The transport protocol used, such as SFTP or AS2 - Details associated with the URL for the endpoint, such as the path - Delete endpoints You can now delete an endpoint that is not used in any message flow configuration. If an endpoint is used in a message flow, you must dissociate the endpoint, update the message flow, and then delete the endpoint. - Delete certificates You can now delete certificates from both the host and partner profile pages. - View and download maps You can now view maps that are part of message flow configurations. You can also download these maps and reuse them. - The B2B integration apps now leverage a circuit breaker pattern to detect failures and prevent failures from continually recurring. ### [](#fixed-issues-82)Fixed Issues - Replaced the third-party Jackson library that was used to serialize and deserialize Java objects to JSON, with the more secure GSON library (B2BSOLUT-2309) - Implemented stricter length and character validations for the message flow and the message type names (B2BSOLUT-2692) - Custom names provided via the UI are now recognized when creating a new HTTP or HTTPs endpoint. (B2BSOLUT-2940) - A timestamp is now added when the flow undeployment completes. (B2BSOLUT-2980) - The archival path is now an optional field when configuring an SFTP endpoint to receive an inbound file. (B2BSOLUT-2984) - After a message flow is deleted, its reference now appears without a hyperlink on the related transmission activities details page. (B2BSOLUT-2994) ### [](#known-issues-17)Known Issues - Using special characters while searching leads to an error. - If a user logs out of an Anypoint Platform session while a B2B message flow deployment is in progress, the deployment terminates. ### [](#limitations-20)Limitations - Outbound/Send flows are not supported. - DataWeave maps must be created in Anypoint Studio. - Routing of X12 files are based on a unique combination of the X12 ISA and the message type, such as X12 850. The X12 GS value is presently not used while routing to message flows. ## [](#2-1-3)2.1.3 **December 20, 2019** ### [](#new-features-18)New Features None. ### [](#fixed-issues-83)Fixed Issues - The latest deployment activity was overriding previous recent deployment activity from the deployment activity section in Message flow details. (B2BSOLUT-2970, B2BSOLUT-2982) - The undeployment action details were not showing up correctly in the message flows list. (B2BSOLUT-3011) ### [](#known-issues-18)Known Issues None. ### [](#limitations-21)Limitations None. ## [](#2-1-2)2.1.2 **December 17, 2019** ### [](#new-features-19)New Features None. ### [](#fixed-issue-6)Fixed Issue Deployed message flows were failing to deliver acknowledgments and marking the transmission as "failed" when using identical endpoint configurations of a previously deployed endpoint. \[B2BSOLUT-2979\] ### [](#known-issues-19)Known Issues None. ### [](#limitations-22)Limitations None. ## [](#2-1-1)2.1.1 **December 13, 2019** ### [](#new-features-20)New Features None. ### [](#fixed-issue-7)Fixed Issue Updating the authentication type and its details in your [payload storage API configuration](https://docs.mulesoft.com/jp/partner-manager/latest/setup-payload-storage-API) in Anypoint Partner Manager resulted in an error. \[B2BSOLUT-2996\] ### [](#known-issues-20)Known Issues None. ### [](#limitations-23)Limitations None. ## [](#2-1-0)2.1.0 **December 7, 2019** ### [](#compatibility-information-7)Compatibility Information Mule runtime engine 4.2.2 ### [](#browser-compatibility-6)Browser Compatibility - Google Chrome 77 and later - Firefox 69 and later ### [](#dependent-components-used-91)Dependent Components Used - Anypoint Connector for AS2 (AS2 Connector) 4.1.0 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.11 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.3 - Anypoint Connector for X12 Connector (X12 Connector) 2.1.1 ### [](#new-features-21)New Features - Undeploy Message Flows Users can now undeploy message flows to remove the associated message flow configuration and the B2B integration applications from Mule. Undeploying a flow stops further processing of any messages associated with that flow. - Delete Identifiers Users can now delete all X12 ISA identifiers, X12 GS identifiers, and DUNS identifiers. Every partner must have at least one identifier. - Delete Message Flows Users can now delete a message flow. A message flow must be undeployed before attempting to delete it. - Delete Trading Partners Users can now delete trading partners. Deleting a trading partner deletes the information associated with that partner, such as identifiers, certificates, endpoints, and message flows. Activities for the partner that occurred before the partner was deleted are not deleted, although the **Activities** page shows that the partner has since been deleted. ### [](#fixed-issues-84)Fixed Issues - On the **Activities** page, using certain special characters caused the backend API to respond with an HTTP 400 error. \[B2BSOLUT-2350\] - An uncaught error when creating a new message type is resolved. \[B2BSOLUT-2491\] - If the name of a message flow is changed, the details about routing after sending files show "missing message flow" on the **Activities** page. \[B2BSOLUT-2531\] - Upgraded `commons-codec` to v1.13 to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2539\] - Upgraded `react.dom` to v16.12.0 to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2548\] - Users were unable to reuse a path in several different endpoints. \[B2BSOLUT-2651\] - Resolved a fatal error when using a dash (-) when deploying an SFTP to an HTTPS message flow. \[B2BSOLUT-2673\] - The API now validates a valid email address when defining an AS2 endpoint. \[B2BSOLUT-2675\] - Links were previously shown with an invalid color in Firefox. \[B2BSOLUT-2676\] - Users were unable to create a new partner with an X12 ISA/SCAC qualifier when the identifier value used the maximum permissible length. \[B2BSOLUT-2684\] - Upgraded `netty-code-http` to v4.1.7 to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2708\] - Creating long names with AS2 identifiers raised errors. \[B2BSOLUT-2711\] - The transmission data patch was occasionally missed, leaving reported activities in an incomplete state. \[B2BSOLUT-2733\] - Sending the same type of EDI files simultaneously to multiple partners caused transactions for one of the partners to fail. \[B2BSOLUT-2746\] - Upgraded `jquery` to overcome a security vulnerability in earlier versions. \[B2BSOLUT-2791\] - Clicking the Partner Manager logo and name now reloads the page. \[B2BSOLUT-2849\] - After changing the name of a deployed message flow, the old name showed up in the activities title. \[B2BSOLUT-2850\] - Uploading a custom JSON schema failed. \[B2BSOLUT-2879\] - The View payload feature failed in the backend service. \[B2BSOLUT-2903\] ### [](#known-issues-21)Known Issues - Using special characters in the search bars leads to an error in subsequent search operations. - If a user logs out of an Anypoint Platform session while a B2B message flow deployment is in progress, the deployment terminates. - The number of message flows using an acknowledgment endpoint incorrectly appears as 0, even when the endpoint is in use. ### [](#limitations-24)Limitations - AS2 identifiers, certificates, and endpoints cannot be deleted. - Outbound - Send flows are not supported. - The ability to test endpoint configurations via the UI for AS2, SFTP, HTTP, and HTTPS before deploying them in Mule is not supported. - DataWeave maps must be created in Anypoint Studio prior to using Anypoint Partner Manager. - Routing of X12 files is based on a unique combination of the X12 ISA and the message type, such as X12 850. The X12 GS value is not leveraged while routing to message flows. ## [](#2-0-1)2.0.1 **November 9, 2019** ### [](#new-features-22)New Features None. ### [](#fixed-issue-8)Fixed Issue Transmission data attributes were not being shown for failed transmissions. These attributes include partners involved in the transmission, EDI format and metadata for the interchange. All new deployments use the latest version of the `DocumentProcessingService` application. If you have any message flows deployed with Partner Manager 2.0.0, use Anypoint Runtime Manager to remove the existing `DocumentProcessingService` application. To get latest version of `DocumentProcessingService`, use the Deploy button to redeploy any message flow from Anypoint Partner Manager. Removing the `DocumentProcessingService` application pauses transaction processing until you deploy these message flows again. For information about deleting applications, refer to [Managing Applications on Your Own Servers](https://docs.mulesoft.com/runtime-manager/managing-applications-on-your-own-servers#deleting-applications). ### [](#known-issues-22)Known Issues None. ### [](#limitations-25)Limitations None. ## [](#2-0-0)2.0.0 **October 19, 2019** This release marks the general availability of Anypoint Partner Manager 2.0 ### [](#whats-new-in-anypoint-partner-manager-2-0)What’s new in Anypoint Partner Manager 2.0 - Based on Mule runtime engine 4.x Anypoint Partner Manager 2.0 enables developers to accomplish B2B integration tasks with fewer steps. Anypoint Partner Manager 2.0 delivers templatized B2B integration flows that can be configured via the Partner Manager management console. The templatized flows leverage the power of the Mule runtime engine 4.x, Dataweave transformations, and connectors such as the X12, SFTP, AS2, and HTTP connector. - Simplified, wizard-driven configuration of B2B flows Anypoint Partner Manager 2.0 introduces a message flow wizard that enables users to easily set up B2B integration flow components such as endpoints, messages, maps, and acknowledgments. Furthermore, the solution enables the reuse of the building blocks of a B2B integration flow thereby speeding up trading partner technical onboarding. You can use Anypoint Partner Manager v2 to setup inbound - receive flows with your trading partners using protocols such as SFTP and AS2. - Support for hybrid deployments With this release of Anypoint Partner Manager 2.0, users are able to leverage the cloud-based Partner Manager management console to configure and manage their B2B flows, while the corresponding B2B integration flows based on the packaged templates provided by the Anypoint Partner Manager 2.0 solution, processes workloads on Mule runtime engine 4.x which can be hosted on-premise in your data centers or in public clouds of your preference. - Tracking of B2B transaction activity Anypoint Partner Manager 2.0 provides a detailed view into the B2B integration transactions processed on your Mule runtime engine. The solution allows you to monitor trading partner transmission activity via a set of end-to-end events related to transmission metadata, messages, and errors. The information includes: - The received EDI payload that can be viewed and downloaded - Acknowledgements (such as TA1 and/or 997/999) that are sent back to the partner - A view into the transformed payload - A detailed view of errors including error messages, error codes, and identification of segments that contain errors ### [](#components-released)Components Released - Partner Manager Console 2.0.0 - B2B Integration Templates 2.0.0 ### [](#compatibility-information-8)Compatibility Information Mule Runtime 4.2.1 ### [](#browser-compatibility-7)Browser Compatibility - Google Chrome version 77 and later - Firefox version 69 and later ### [](#dependent-components-used-92)Dependent Components Used - Anypoint Connector for AS2 (AS2 Connector) 4.0.7 - Anypoint Connector for HTTP Connector (HTTP Connector) 1.5.9 - Anypoint Connector for SFTP Connector (SFTP Connector) 1.3.2 - Anypoint Connector for X12 Connector (X12 Connector) 2.1.1 ### [](#known-issues-23)Known Issues - Using special characters in the search bars leads to an error in subsequent search operations. - Using special characters in the name of the organization leads to an error in the creation of the host partner. - If a user logs out of the Anypoint Platform session while a B2B message flow deployment is in progress, the deployment is terminated. ### [](#limitations-26)Limitations - Assets such as identifiers, certificates, endpoints, partners, and message flows cannot be deleted. - Outbound - Send flows are not supported. - The ability to test endpoint configurations via the UI for AS2, SFTP, HTTP and HTTPS before deploying them onto the Mule runtime, is not supported. - The DataWeave maps must be created in Anypoint Studio prior to using Anypoint Partner Manager. - Routing of X12 files is based on a unique combination of the X12 ISA and the message type, such as X12 850. The X12 GS value is not leveraged while routing to message flows. ## [](#see-also)See Also - [Partner Manager Documentation](https://docs.mulesoft.com/jp/partner-manager/latest/) - [Anypoint Partner Manager のトラブルシューティング](https://docs.mulesoft.com/jp/partner-manager/latest/troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform CLI Release Notes Anypoint Platform CLI is a scripting and command-line tool for Anypoint Platform and Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). The following release notes are provided for Anypoint Platform CLI: - [Anypoint Platform CLI 4.x](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Anypoint Platform CLI 3.x](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli) ## [](#see-also)See Also - [Anypoint CLI Documentation](https://docs.mulesoft.com/jp/anypoint-cli/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Command-Line Interface 4.x Release Notes ## [](#1-6-28)1.6.28 **October 13, 2026** ### What’s New - `api-mgr upstream list` now returns upstream objects in JSON format when using `--output json`. - Basic endpoint creation with `--type raml` now preserves the endpoint type as RAML. RAML is still mapped to `rest-api` when creating an API with `--withProxy`. ## [](#1-6-27)1.6.27 **August 24, 2026** ### Fixed Issues
Issue Resolution ID

The DX Mule plugin dependency is upgraded to address several reported security vulnerabilities in bundled Java JARs and npm dependencies.

W-23852828
## [](#1-6-26)1.6.26 **July 29, 2026** ### What’s New - The `dx:mule:describe-connector` command now supports describing private and custom connectors published to your organization’s Anypoint Exchange. Connected App credentials configured via `anypoint-cli-v4 conf` are automatically used to authenticate with Exchange when resolving the connector artifact. - You can now download a JDK using the new `dx:mule:jdk:download` command, which automatically detects your OS and architecture and downloads the latest version by default. ### Fixed Issues
Issue Resolution ID

The Governance plugin is upgraded to address a reported security vulnerability.

W-23086228

The minimatch dependency in the Design Center plugin is upgraded to address a reported security vulnerability.

W-21680716
## [](#1-6-25)1.6.25 **July 8, 2026** ### What’s New - New `governance:ruleset` commands are added to author governance rulesets locally, without a network connection or APB dependency. For more information, see the [API Governance Command Documentation](https://docs.mulesoft.com/jp/anypoint-cli/latest/api-governance). - The `amf` metadata domain is renamed to `api-spec` in the ruleset authoring commands. If you used `--domain amf` to filter classes, use `--domain api-spec` instead. - The `api-instance` metadata domain is removed from ruleset authoring. This domain and its related types are no longer targetable when authoring rulesets. ## [](#1-6-23)1.6.23 **June 24, 2026** ### What’s New - You can now create Mule projects from Anypoint Exchange templates or local template files using the new `dx:mule:project:create` command flags: - `--template-asset ` — Creates a project from an Anypoint Exchange template. - `--template-file ` — Creates a project from a local `.jar` or `.zip` template file. - `--asset-type template|example` — Specifies the Maven classifier when downloading from Exchange. - `--skip-environment` — Bypasses environment resolution for local template flows that don’t require an Anypoint API call. - Consumers of the `anypoint-cli-core-library` can now customize the `User-Agent` header value sent in HTTP requests. If no custom value is provided, the default `Anypoint-CLI/` is used to ensure backward compatibility. - The Anypoint CLI Exchange plugin npm package has been renamed to `mulesoft-anypoint-cli-exchange-plugin`. If you’re using the former package name (`anypoint-cli-exchange-plugin`), update your `package.json` to use the new package name. The old package name no longer receives updates. ### Fixed Issues
Issue Resolution ID

The 200 MB upload limit in anypoint-cli-core-library that caused ERR_FR_MAX_BODY_LENGTH_EXCEEDED errors when uploading assets larger than 200 MB is increased.

W-23086435
## [](#1-6-22)1.6.22 **June 4, 2026** ### Fixed Issues
Issue Resolution ID

The minimatch transitive dependency is upgraded to address reported security vulnerabilities.

W-22309904

The DX Mule plugin dependency is upgraded to address a reported security vulnerability.

W-22587408
## [](#1-6-21)1.6.21 **May 19, 2026** ### What’s New - The DX Mule plugin is added to manage Mule runtimes, scaffold Mule projects, and introspect connector metadata from the command line. For more information, see the [anypoint-cli::dx-mule.adoc](#anypoint-cli::dx-mule.adoc). ## [](#1-6-20)1.6.20 **May 13, 2026** ### Fixed Issues
Issue Resolution ID

CloudHub 2.0 application updates using runtime-mgr:application:modify no longer reset ingress settings when no HTTP flags are provided. The CLI now omits deploymentSettings.http unless at least one HTTP-related flag is explicitly passed.

W-20365627

Using runtime-mgr:application:modify with --publicEndpoints now correctly controls default public URL generation for CloudHub 2.0 applications by setting generateDefaultPublicUrl when appropriate.

W-20365627
## [](#1-6-19)1.6.19 **May 6, 2026** ### What’s New - The Anypoint CLI Governance plugin 1.0.19. npm package name is now `mulesoft-anypoint-cli-governance-plugin`. If you’re using the former package name (`anypoint-cli-governance-plugin`), update your `package.json` to use the new package name. The old package name no longer receives updates. See [Migrate to the New Governance Plugin Package Name](https://docs.mulesoft.com/jp/anypoint-cli/latest/install#migrate-governance-plugin). - Validation reports now include source information by default with accurate file, line, and column locations for each governance violation. ### Fixed Issues
Issue Resolution ID

The AJV dependency is upgraded to 6.14.0 to address reported security vulnerabilities.

W-19028240

Error messages now provide helpful information when validating rulesets with unsupported file extensions.

W-22139481

Exchange asset downloads via S3 signed URLs no longer fail with 403 Forbidden errors.

W-22139481
## [](#1-6-18)1.6.18 **April 15, 2026** ### Fixed Issues
Issue Resolution ID

The Design Center plugin now functions correctly after resolving an internal reference issue.

W-21665505
## [](#1-6-17)1.6.17 **April 6, 2025** ### Fixed Issues
Issue Resolution ID

Design Center projects that use connected apps with the client_credentials grant type can now be published to Exchange using Anypoint CLI.

W-21343761

Publishing Design Center projects with connected app authentication no longer returns a 404 error.

W-21720296

Design Center now correctly handles GitHub-synced projects when publishing through Anypoint CLI.

W-21621786
## [](#1-6-16)1.6.16 **February 2, 2026** ### What’s New - You can now use the new `api-mgr:client-provider:list-importable` command to list client applications that can be imported from client providers in API Manager. - You can now use the new `api-mgr:application:import` command to import client applications from client providers into API Manager. - You can now use the new `api-mgr:application:possible-owners-list` command to list possible owners for client applications. - You can now use the new `api-mgr:application:add-owner` command to add an owner to a client application. - The `anypoint-cli-v4` library is renamed to `anypoint-cli-v4-public`. Use `npm i anypoint-cli-v4-public` instead of `npm i anypoint-cli-v4`. ## [](#1-6-15)1.6.15 **January 16, 2026** ### What’s New - The Anypoint CLI Agent Fabric plugin npm package has been renamed to `mulesoft-anypoint-cli-agent-fabric-plugin`. If you previously installed the plugin using the former package name, installing the new package results in an `npm error EEXIST: file already exists` error because both packages share the same command alias. To resolve this issue, reinstall the plugin using the `--force` flag to overwrite the existing alias: `npm i mulesoft-anypoint-cli-agent-fabric-plugin --force` ## [](#1-6-14)1.6.14 **November 14, 2025** ### What’s New - The runtime manager plugin now includes support for Managed Omni Gateway operations. ## [](#1-6-13)1.6.13 **November 10, 2025** ### What’s New - You can now use the `api-mgr:api:manage` command to work with server endpoint types. - You can now use the `api-mgr:api:manage` command with the `--groupId` flag to create an API instance using a specification from a different business group. ## [](#1-6-12)1.6.12 **October 11, 2025** ### Fixed Issues
Issue Resolution ID

Concurrency race conditions that occurred when commands were run in parallel or in quick succession have been resolved.

W-19025514
## [](#1-6-11)1.6.11 **October 3, 2025** ### What’s New The Agent Fabric plugin is added to create, build, publish, and deploy agent networks. For more information, see the [Agent Fabric for CLI documentation](#anypoint-cli::agent-fabric.adoc). ## [](#1-6-10)1.6.10 **July 14, 2025** ### What’s New - You can now use the new `api-mgr:policy:order` command to retrieve or update the policy order for an API instance. - You can now use the new `api-mgr:upstream:bulk-edit` command to edit the TLS context for all upstreams of an API instance. ## [](#1-6-6)1.6.6 **June 5, 2025** ### Fixed Issues
Issue Resolution ID

You can now successfully authenticate using the proxy.

W-17710058
## [](#1-6-5)1.6.5 **May 15, 2025** ### What’s New - You can now use the `--config` flag on the `api-mgr:policy:apply` command to apply `jwtExpression` JWT policies. ## [](#1-6-4)1.6.4 **May 12, 2025** ### What’s New - You can now use the new `--version` and `--format` flags on the `designcenter:project:create` command. - You can now specify OAS format when using the `--type` flag on the `designcenter:project:create` command ## [](#1-6-3)1.6.3 **March 15, 2025** ### What’s New - You can now use the `api-mgr:api:deploy` command to deploy API instances to managed Flex Gateways. - You can now use the `--routing` flag on the `api-mgr:api:edit` command to configure upstreams to API instances. - You can now use the `--upstreamId` flag on the `api-mgr:policy:apply` command to configure outbound policies. ## [](#1-6-2)1.6.2 **November 7, 2024** ### Fixed Issues
Issue Resolution ID

You can now successfully authenticate using the proxy.

W-17029367

You can now successfully authenticate using MFA environments.

W-16953543

You can now successfully authenticate using the HTTP proxy.

W-16452550
## [](#1-6-1)1.6.1 **October 14, 2024** ### Fixed Issues
Issue Resolution ID

You can now use the exchange:asset:download command without getting an ERR_BAD_REQUEST error message.

W-16952385
## [](#1-6-0)1.6.0 **October 3, 2024** ### What’s New - You can now use the `--status` flag on the `designcenter:project:publish` command. - Certain dependencies are updated to improve security. ### Fixed Issues
Issue Resolution ID

The connected app token now works as expected.

W-16239175
## [](#1-5-8)1.5.8 **July 25, 2024** ### What’s New - Certain dependencies are updated to improve security. ### Fixed Issues
Issue Resolution ID

An endpoint defaultSslEndpoint is now automatically provided in CloudHub commands.

W-15453317

You can now use the governance:ruleset:clone command without cloning the rulesets from the original severity.

W-16225975
## [](#1-5-7)1.5.7 **June 27, 2024** ### What’s New - You can now use the `--output` flag on all API Manager commands. - The CloudHub plugin is updated to accept 8 and 16 vCores. - You can now use the `--configFile` flag on the `api-mgr:policy:edit` command. - You now get an error message specifying details if the `api-mgr:policy:apply` command fails. ## [](#1-5-6)1.5.6 **April 25, 2024** ### Fixed Issues
Issue Resolution ID

You can now publish Mule applications with the exchange:asset:upload command successfully.

W-15279240

You can now use the --releaseChannel, --publicEndpoints, and --javaVersion flags on CloudHub 2.0 commands.

W-15227119, W-15227226

You can now use the --pageSize flag on the designcenter:project:list command.

W-15303243
## [](#1-5-5)1.5.5 **March 15, 2024** ### Fixed Issues
Issue Resolution ID

You can now successfully use API Designer commands.

W-15263849
## [](#1-5-2)1.5.2 **February 29, 2024** ### What’s New - The runtime version is now upgraded to 4.6.0. - New deployments for CloudHub 2.0 and Anypoint Runtime Fabric are now supported. ## [](#1-5-1)1.5.1 **February 7, 2024** ### What’s New - New `--releaseChannel`, `--javaVersion` flags for Cloudhub commands are added. For more information, see [Cloudhub](https://docs.mulesoft.com/jp/anypoint-cli/latest/cloudhub-apps). ## [](#1-5-0)1.5.0 **February 6, 2024** ### What’s New - The new Secrets Manager plugin is added to manage secrets and secret groups. For more information see the [Secrets Manager documentation](#anypoint-cli::secrets-manager.adoc). - New `--releaseChannel`, `--javaVersion` flags for Cloudhub 2.0 commands are added. For more information, see [Cloudhub 2.0 Commands](https://docs.mulesoft.com/jp/anypoint-cli/latest/cloudhub2-apps). - Errors are now tracked for better support. ## [](#1-4-4)1.4.4 **January 18, 2024** ### Fixed Issues
Issue Resolution ID

You now see an authentication header when making a request.

W-14838539
## [](#1-4-3)1.4.3 **January 15, 2024** ### Fixed Issues
Issue Resolution ID

You now download the exchange_module folder when using the designcenter:project:download command

W-14581414

You no longer get a 429 error message when doing multiple requests.

W-14667994
## [](#1-4-2)1.4.2 **December 1, 2023** ### Fixed Issues
Issue Resolution ID

You can now use GraphQL commands without getting empty responses.

W-14588742
## [](#1-4-0)1.4.0 **October 25, 2023** ### Fixed Issues
Issue Resolution ID

You can now use certificates without getting an Unsafe Legacy Renegotiation error message.

W-14147387

You can now render reports for Governance projects.

W-14274588

You can now successfully use the --fragment-type flag with Design Center commands.

W-14153380
## [](#1-3-0)1.3.0 **September 27,2023** ### Fixed Issues
Issue Resolution ID

You can now use the designcenter:project:create command for RAML and RAML-fragment types projects without getting a status code 500 error.

W-13999860

You can now successfully use the designcenter:project:download command to download exchange dependencies.

W-14058134
## [](#1-2-9)1.2.9 **August 9, 2023** ### Fixed Issues
Issue Resolution ID

You can now use the --output option with the runtime-mgr:application:describe command to specify the json response format.

W-13813626
## [](#1-2-8)1.2.8 **July 26, 2023** ### Fixed Issues
Issue Resolution ID

You can now upload ruleset.yaml files when using the governance:api:validate command.

W-13701374
## [](#1-2-7)1.2.7 **June 14, 2023** ### What’s New - You can now use the new `--secureProperty` flag to set encrypted properties on `runtime-mgr application modify` and `runtime-mgr application deploy` commands. ## [](#1-2-6)1.2.6 **May 31, 2023** - Certain dependencies are updated to improve functionality.
Anypoint CLI versions 1.0.0 to 1.2.5 use old dependencies that do not work at the moment.
## [](#1-2-5)1.2.5 **May 17, 2023** ### What’s New - You can now use objectStoreV2 flags on Cloudhub commands. For more information, see [Cloudhub](https://docs.mulesoft.com/jp/anypoint-cli/latest/cloudhub-apps) and [Cloudhub 2.0 Commands](https://docs.mulesoft.com/jp/anypoint-cli/latest/cloudhub2-apps). ### Fixed Issues
Issue Resolution ID

You can now use true and false boolean flags.

W-13135940

You now see descriptions for ruleset error messages.

W-11124216
## [](#1-2-4)1.2.4 **May 3, 2023** ### Fixed Issues
Issue Resolution ID

You no longer get an error message when using the ANYPOINT_CERTIFICATE environment variable.

W-12976257
## [](#1-2-3)1.2.3 **April 14, 2023** ### Fixed Issues
Issue Resolution ID

Governance commands now work as expected.

W-13038510
## [](#1-2-2)1.2.2 **April 5, 2023** ### What’s New For the Anypoint API Manager CLI: - The `api-mgr:api:deploy` command can deploy Flex Gateway APIs and APIs created using the UI. - The `api-mgr:api:redeploy` command can redeploy Flex Gateway APIs. - The `api-mgr:api:describe` command includes the API type and deployment target ID in the description. - The `api-mgr:api:delete` command undeploys deployed APIs before deleting. - The `api-mgr:api:edit` command supports Flex Gateway APIs and redeploys the edited API if it was previously deployed. - The `api-mgr:api:manage` command supports Flex Gateway APIs. - You can add TLS configuration for Flex Gateway APIs using the `api-mgr:api:manage` and `api-mgr:api:edit` commands. For more information, see [API Manager Commands](https://docs.mulesoft.com/jp/anypoint-cli/latest/api-mgr). ### Fixed Issues
Issue Resolution ID

The api-mgr:api:download-proxy command now works as expected.

W-12221664

The governance:api:validate command now works as expected and no longer shows the incorrect error TypeError: global.AMFterminateValidator is not a function.

W-12266732

You can now use the governance:api:inspect command with Windows paths.

W-12120881

The governance:profile:create and governance:profile:update option to configure notifications now works as documented.

W-12651115
## [](#1-2-1)1.2.1 **March 8, 2023** ### What’s New - You can now install the ` autocomplete` plugin to generate autocomplete files. Use tab to use the autocomplete feature. - You can now authenticate with the new environment variable `ANYPOINT_CERTIFICATE`. This variable adds CAcert certificates to Anypoint CLI. ## [](#1-2-0)1.2.0 **February 22,2023** ### What’s New - You can now search by organization ID when using the `account:business-group:describe` command. - You can now use the `--output` flag when using the `runtime-mgr:application:list` command. - You can now write all commands separated by spaces instead of colons (for example: `runtime-mgr:application:list` can also be `runtime-mgr application list`). ## [](#1-1-1)1.1.1 **February 8, 2023** ### What’s New - You can now use the new optional `--timeout` flag when using the `runtime-mgr:cloudhub-application:deploy` command. - You can now use the `--fragmentType` flag of the `designcenter:project:create` command to select `oas-components` and `json-schema` fragment types. ### Fixed Issues
Issue Resolution ID

The certificateName flag is now optional on Cloudhub dedicated load balancer commands.

W-12289516

You can now use the --categories flag while using the exchange:asset:upload command.

W-12385831

Your password is now obfuscated when stored in your credentials file.

W-12397848

You can now use the artifactid and runtimeVersion flags when using the runetime-mgr:application:modify command.

W-12438267

The api-mgr:api:deploy command now works as expected.

W-12475213

You can now edit an API specification that is published using the designcenter:project:publish command in Exchange

W-12230497
## [](#1-1-0)1.1.0 **January 11, 2023** ### What’s New - The new API Governance plugin is added to apply governance rules to your APIs. For more information see the [API Governance Command Documentation](https://docs.mulesoft.com/jp/anypoint-cli/latest/api-governance). ### Fixed Issues
Issue Resolution ID

The api-mgr:api:manage command now works as expected.

W-12128681

The runtime-mgr:cloudhub-application:copy command now works as expected.

W-12165914

You can now use the runtime-mgr:cloudhub-application:copy command with targets with static IPs.

W-12167960

You can now use the api-mgr:api:describe command with deployment target IDs from Hybrid, Flex, and Runtime Fabric APIs.

W-12221558

You can now use the --categories flag while using the exchange:asset:upload and exchange:asset.mutableDataUpload commands.

W-12270382
## [](#1-0-3)1.0.3 **November 29, 2022** ### Fixed Issues
Issue Resolution ID

You can now use the cloudhub-application:copy command without deleting the application that you copy.

W-11584309

The exchange:asset:uploadv2 command now works as expected.

W-12113687

The MB value is now set to 1,048,576.

W-12065146
## [](#1-0-2)1.0.2 **November 14, 2022** ### What’s New - You can now use multi-factor authentication (MFA) by logging in through the browser. - New CloudHub 2.0 commands are added for managing applications. ## [](#1-0-0)1.0.0 **October 13, 2022** Mulesoft announces the release of Anypoint CLI 4.x. Anypoint Platform CLI is a scripting and command-line tool for Anypoint Platform and Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ### What’s New - New standardized CLI framework: OCLIF, aligned with all Salesforce products. - New support for API Catalog. - Individual plug-ins per each topic. This new architecture extends CLI functionality by delivering new plug-ins, and by fixing and updating each plug-in separately without updating the whole suite of CLI. - Node JS v16+ is required. To see how version 4.x differs from previous versions, see the [Anypoint CLI 4.x documentation](https://docs.mulesoft.com/jp/anypoint-cli/latest/diff-earlier-ver).
You can still download and use Anypoint CLI 3.x. The product will be available until it reaches its End Of Life, when extended support ends.
## [](#see-also)See Also - [anypoint-cli::troubleshooting.adoc](#anypoint-cli::troubleshooting.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Command-Line Interface Release Notes - [Anypoint Platform CLI 4.x](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Anypoint Platform CLI 3.x](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli) ## [](#see-also)See Also - [anypoint-cli::troubleshooting.adoc](#anypoint-cli::troubleshooting.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Command-Line Interface Release Notes ## [](#3-22-8)3.22.8 **June 29, 2026** ### What’s New - The Anypoint CLI v3 npm package has been renamed to `anypoint-cli-v3`. If you’re using the former package name (`anypoint-cli`), update your `package.json` to use the new package name. The old package name no longer receives updates. ### Fixed Issues

Issue Resolution

ID

Anypoint CLI v3 no longer returns a Bad Request error when used behind a corporate proxy. Previously, Axios independently attempted to route requests through the proxy while HttpsProxyAgent simultaneously opened a CONNECT tunnel, causing double-proxied requests that the proxy server rejected with HTTP 400.

W-23207614
## [](#3-22-7)3.22.7 **July 25, 2024** ### Fixed Issues

Issue Resolution

ID

An endpoint defaultSslEndpoint is now automatically provided in Cloudhub commands.

W-15453317
## [](#3-22-6)3.22.6 **June 27, 2024** ### What’s New - The Cloudhub plugin is updated to accept 8 and 16 vCores. ## [](#3-22-5)3.22.5 **March 15, 2024** ### Fixed Issues

Issue Resolution

ID

You can now successfully use API Designer commands.

W-15263849

You can now use the --pageSize flag on the designcenter:project:list command.

W-15303243
## [](#3-22-4)3.22.4 **February 29, 2024** ### Fixed Issues

Issue Resolution

ID

Deploying Mule runtime 4.5.3 to CloudHub 2.0 with CLI v3 no longer fails.

W-15044298

Anypoint CLI now passes the CPU limit and memory as expected for new deployments.

W-15058332
## [](#3-22-3)3.22.3 **February 7, 2024** ### What’s New - New `--reservedCPU`, `--vCPULimit` and `--memory` flags for Runtime Fabric commands are added. For more information, see [CLI for Managing Apps in Runtime Fabric](https://docs.mulesoft.com/jp/anypoint-cli/3.x/runtime-fabric-apps). ## [](#3-22-2)3.22.2 **February 7, 2024** ### What’s New - New `--releaseChannel`, `--javaVersion` flags for Cloudhub commands are added. For more information, see [Cloudhub](https://docs.mulesoft.com/jp/anypoint-cli/3.x/cloudhub-apps) ## [](#3-22-1)3.22.1 **February 6, 2024** ### What’s New - New `--releaseChannel`, `--javaVersion` flags for Cloudhub 2.0 commands are added. For more information, see [Cloudhub 2.0 Commands](https://docs.mulesoft.com/jp/anypoint-cli/3.x/cloudhub2-apps). ## [](#v3-22-0)3.22.0 **January 15, 2024** ### Fixed Issues

Issue Resolution

ID

You can now use the api-mgr:alert:add command to create a policy violation alert without getting an error message.

W-14067902

You now download the exchange_module folder when using the designcenter:project:download command

W-14581414
## [](#v3-21-9)3.21.9 **October 25, 2023** ### Fixed Issues

Issue Resolution

ID

You can now use certificates without getting an Unsafe Legacy Renegotiation error message.

W-14147387
## [](#v3-21-7)3.21.7 **September 27,2023** ### Fixed Issues

Issue Resolution

ID

You can now use the designcenter:project:create command for RAML and RAML-fragment types projects without getting a status code 500 error.

W-13999860

You can now successfully use the designcenter:project:download command to download exchange dependencies.

W-14058134
## [](#v3-21-6)3.21.6 **June 14, 2023** ### What’s New - You can now use the new `--secureProperty` flag to set encrypted properties on `runtime-mgr application modify` and `runtime-mgr application deploy` commands. ## [](#v3-21-5)3.21.5 **May 31, 2023** - Certain dependencies are updated to improve functionality.
Anypoint CLI versions 3.18.0 to 3.21.4 use old dependencies that do not work at the moment.
## [](#v3-21-4)3.21.4 **May 17, 2023** ### What’s New - You can now use objectStoreV2 flags on Cloudhub commands. For more information, see [Cloudhub](https://docs.mulesoft.com/jp/anypoint-cli/3.x/cloudhub-apps) and [Cloudhub 2.0 Commands](https://docs.mulesoft.com/jp/anypoint-cli/3.x/cloudhub2-apps). ## [](#v3-21-3)3.21.3 **March 8, 2023** ### What’s New - You can now authenticate with the new environment variable `ANYPOINT_CERTIFICATE`. This variable adds CAcert certificates to Anypoint CLI. ## [](#v3-21-2)3.21.2 **February 22, 2023** ### What’s New - You can now search by organization ID when using the `account:business-group:describe` command. ### Fixed Issues

Issue

ID

You can now use the exchange:asset:page:upload command without getting an error message.

W-12555915
## [](#v3-21-1)3.21.1 **February 8, 2023** ### What’s New - You can now use the new optional `--timeout` flag when using the `runtime-mgr cloudhub-application deploy` command. - You can now use the `--fragmentType` flag of the `designcenter:project:create` command to select `oas-components` and `json-schema` fragment types. ### Fixed Issues

Issue

ID

You can now use the --categories flag while using the exchange:asset:upload command.

W-12385831

The anypoint CLI proxy now works as expected.

W-12413855
## [](#v3-21-0)3.21.0 **January 10, 2023** ### Fixed Issues

Issue

ID

The cloudhub-application copy command now works as expected.

W-12150352

The anypoint-cli governance api validate command now works as expected

W-12266732
## [](#v3-20-0)3.20.0 **December 13, 2022** ### What’s New - The governance commands `governance profile create` and `governance profile update` have new options to configure notifications and to automatically use latest as the ruleset version. ### Fixed Issues

Issue Resolution

ID

You can now use the governance api inspect command with Windows paths.

W-12120881

The cloudhub-application copy command now works as expected.

W-12150352
## [](#v3-19-1)3.19.1 **November 29, 2022** ### Fixed Issues

Issue

ID

You can now use the cloudhub-application copy command without deleting the application that you copy.

W-11584309

The exchange asset uploadv2 command now works as expected.

W-12113687

The MB value is now set to 1,048,576.

W-12065146
## [](#v3-19-0)3.19.0 **November 15, 2022** ### What’s New - You can now use multi-factor authentication (MFA) by logging in through the browser. ## [](#v3-18-2)3.18.2 **November 1, 2022** ### What’s New - Internal libraries are updated. - Command tracking is improved. - The command `governance api inspect` now has OAS support. ### Fixed Issues

Issue

ID

The runtime-mgr standalone application deploy command now works as expected.

W-11696354

You can now use Anypoint CLI while connected trough a proxy.

W-11761129
## [](#v3-18-1)3.18.1 **October 11, 2022** ### What’s New - You can now use the `runtime-mgr standalone-application copy` command without having the Manage Servers permission. ## [](#v3-18-0)3.18.0 **September 27, 2022** ### What’s New - The command `governance ruleset validate` now works on Windows 10. - The command `governance api validate` now works with multiple rulesets. - You can now use anypoint CLI when connecting through a proxy. ## [](#v3-17-0)3.17.0 **September 13, 2022** ### What’s New Updates to the `governance` command group: - New command to enable you to evaluate the rulesets that might apply to your API: - `governance api evaluate` - New commands to enable you to scaffold rules from data schemas: - `governance api inspect` - `governance ruleset init` - New commands to enable you to customize individual rules by changing severity levels and enabling or disabling rules: - `governance ruleset info` - `governance ruleset clone` - Updates to `governance create profile` and `governance update profile` to add the following option: - `--criteria`, where you can specify filters for tags, categories, and scope, such as API types `async-api` and `rest-api` - Updates to `governance api validate` to add the following options: - `--remote`, to enable you to validate APIs published in Exchange - `--remote-rulesets`, to enable you to validate APIs against rulesets published in Exchange See [the governance command group](https://docs.mulesoft.com/jp/anypoint-cli/3.x/api-governance) in the Anypoint CLI 3.x documentation. ### Fixed Issues

Issue

ID

The designcenter project publish command does not allow the tags flags anymore.

W-11359020

The api-mgr api deploy and api-mgr api redeploy commands now work as expected.

W-11610551

The datagraph load-balancer-config add and datagraph load-balancer-config describe commands now work as expected.

W-11637288
## [](#v3-16-0)3.16.0 **August 23, 2022** ### What’s New - New CloudHub 2.0 commands are added for managing applications. - APB is upgraded to version 1.0.7. ## [](#v3-15-1)3.15.1 **August 9, 2022** ### What’s New - Certain deprecated dependencies are upgraded. ## [](#v3-15-0)3.15.0 **July 26, 2022** ### What’s New - Replaced non-compliant term in adherence to our Inclusive Product Language Program. ### Fixed Issues

Issue

ID

The designcenter project create command no longer displays an error message creating resource types and user-documentation RAML fragments.

W-11357917
## [](#v3-14-0)3.14.0 **July 11, 2022** ### What’s New - A message now displays to warn users regarding any occurrences of non-compliant terms in the Inclusive Product Language Program, alternately, suggesting the use of `allowlist` instead. - You can now select the project branch using the `--branch` option for the `designcenter project publish`, `designcenter project upload`, and `designcenter project download` commands. - The command `anypoint-cli governance api validate` now accepts an API project ZIP file or folder and downloads dependencies, including rulesets against which to validate. You can optionally use the `--rulesets` option to specify a comma-separated list of local rulesets. - The command `governance ruleset validate` now accepts the following as the ruleset definition parameter: - A ruleset definition YAML file - A ZIP file that contains an API project with an `exchange.json` file that specifies the ruleset as the main file - A folder that contains an API project with an `exchange.json` file that specifies the ruleset as the main file ## [](#v3-13-0)3.13.0 **June 14, 2022** ### What’s New This release includes the following changes: - Replaced non-compliant term with "allowlist" in compliance with our Inclusive Product Language Program. - Replaced clean ANSI characters in standard output with plain text. ### Fixed Issues

Issue

ID

The api-mgr contract list command now displays the correct error message when exceeding the 250 limit.

W-11216223
## [](#v3-12-0)3.12.0 **May 31, 2022** ### What’s New This release includes the following changes: - Added `datagraph` commands for working with source APIs. ## [](#v3-11-0)3.11.0 **May 17, 2022** ### What’s New This release includes the following changes: - Added more fields to the `exchange asset copy` command. ### Fixed Issues

Issue

ID

The designcenter project publish command no longer returns a 500 - undefined error.

W-11101077
## [](#v3-10-0)3.10.0 **April 28, 2022** ### What’s New This release includes the following changes: - Added `governance` command group. ## [](#v3-9-7)3.9.7 **April 5, 2022** ### What’s New This release includes the following changes: - Added an option to send a file as `--configFile` with the `api-mgr policy apply` command. ## [](#v3-9-6)3.9.6 **March 22, 2022** ### What’s New This release includes the following changes: - Added the `assetUpdateStatus` command to specify the `--status` property when creating an asset. ## [](#v3-9-4)3.9.4 **January 12, 2022** ### Fixed Issues

Issue

ID

Fixed an issue that broke up the JSON output when using commands with the -o formatting parameter.

SE-24109
## [](#v3-9-3)3.9.3 **January 11, 2022** ### Fixed Issues

Issue

ID

Source dependencies are now included when copying an asset.

SE-23974

Fixed an issue that broke up the standard output when using the colors library.

SE-24083
## [](#v3-9-2)3.9.2 **December 14, 2021** ### Fixed Issues

Issue

ID

The runtime-mgr standalone-application copy command now works as expected and provides an authentication method with client_id and client_secret.

SE-19129
## [](#v3-9-1)3.9.1 **November 2, 2021** ### Fixed Issues

Issue

ID

The designcenter project publish command no longer fails when the --apiVersion option is not specified.

DESIGNER-6949

Updated dependencies to avoid the error The unauthenticated git protocol on port 9418 is no longer supported. during install.

APC-226
## [](#v3-9-0)Version 3.9.0 - September 21, 2021 - Added the `mutableDataUpload` command to upload mutable data to an existing asset. - Added the `page update` command to update an Asset Portal page in Markdown format. ## [](#v3-8-2)Version 3.8.2 - September 7, 2021 - To improve the Anypoint CLI experience, we gather anonymized usage data. You can opt out by setting `collectMetrics` to false in the `credentials` file. - Fixed an issue related to basic type WSDL API instance creation. ## [](#v3-8-1)Version 3.8.1 - August 24, 2021 - Added the `--endpointUri` argument for the `api-mgr api manage` and `api-mgr api edit` commands. - Fixed issues with the `load-balancer mappings` commands. ## [](#v3-8-0)Version 3.8.0 - July 13, 2021 - Added exchange commands for managing asset resources. - Added arguments to `exchange asset uploadv2` command. - Added `organizationId` option to `exchange asset list` command. ## [](#v3-7-1)Version 3.7.1 - June 22, 2021 - The `runtime-mgr standalone-application deploy` command now works as expected in both interactive and non-interactive modes. (SE-19237, SE-20345, SE-21102) - Removed Beta from `exchange asset uploadv2` command. ## [](#v3-7-0)Version 3.7.0 - May 4, 2021 - Added support for Anypoint DataGraph configuration. For more information, see [the DataGraph commands](https://docs.mulesoft.com/jp/anypoint-cli/3.x/datagraph) in the Anypoint CLI 3.x documentation. ## [](#v3-6-1)Version 3.6.1 - March 22, 2021 - Fixed an issue with the `runtime mgr deploy` command where it failed to deploy multiple times standalone applications that had the same name but pointed to different targets. (SE-19237) - Fixed an issue with `exchange asset page list` and `exchange asset page download` commands to allow downloading pages from public assets. (EXC-5362) ## [](#version-3-6-0-march-4-2021)Version 3.6.0 - March 4, 2021 - Fixed an issue with the `api-mgr policy disable/enable` command and authentication-based policies that caused the `Missing parameter at password` error. (SE-18665) - Fixed an issue with the `exchange asset copy` command that prevented copying an exchange asset from one org to another. (SE-18990) - Fixed an issue with the `runtime-mgr cloudhub-application copy` command that occurred when copying an app with safely hidden application properties. Added the `--property` option to specify properties. For information, see the [runtime-mgr cloudhub-application copy](https://docs.mulesoft.com/jp/anypoint-cli/3.x/cloudhub-apps#runtime-mgr-cloudhub-application-copy) command in the Anypoint CLI 3.x documentation. ## [](#version-3-4-3-august-6-2020)Version 3.4.3 - August 6, 2020 - Fixed an issue that caused extra information being logged in non-interactive mode. ## [](#version-3-4-2-august-5-2020)Version 3.4.2 - August 5, 2020 - Fixed an issue that occurred with secure properties when deploying CloudHub applications. ## [](#version-3-4-1-august-5-2020)Version 3.4.1 - August 5, 2020 - Fixed an issue that occurred when uploading an asset with an `apiVersion` value that included trailing zeroes. ## [](#version-3-2-6-september-4-2019)Version 3.2.6 - September 4, 2019 - Fixed issue that caused the `exchange asset describe` command to threw a "Cannot read property 'versions'" error. ## [](#version-3-2-5-august-12-2019)Version 3.2.5 - August 12, 2019 - Fixed issue when runtime list did not show default mule version. ## [](#version-3-2-4-july-28-2019)Version 3.2.4 - July 28, 2019 - Fixed update `exchange.json` stage when publishing to exchange. ## [](#version-3-2-3-july-11-2019)Version 3.2.3 - July 11, 2019 - Fixed mapping of Asset Type on API Manager. ## [](#version-3-2-2-july-1-2019)Version 3.2.2 - July 1, 2019 - Fixed issue when publishing to exchange with different `groupId`. ## [](#version-3-2-1)Version 3.2.1 - - Fixed issue when uploading asset with file path starting with `~`. ## [](#version-3-2-0-april-26-2019)Version 3.2.0 - April 26, 2019 - Added a warning when an invalid `HTTPS_PROXY` or `HTTP_PROXY` environment value is found. ## [](#version-3-1-1-april-22-2019)Version 3.1.1 - April 22, 2019 - Fixed issue when using properties with colon or equal characters in the value field. ## [](#version-3-1-0-april-17-2019)Version 3.1.0 - April 17, 2019 This release of Anypoint Platform CLI adds the following Exchange feature: - Added the ability to publish RAML assets. Example: `exchange asset upload --classifier raml --apiVersion v1 --name HelloWorld --mainFile helloworld.raml helloword/1.0.0 /Users/nmouso/Downloads/helloworld.raml.zip` ## [](#version-3-0-5-january-25-2019)Version 3.0.5 - January 25, 2019 This release of Anypoint Platform CLI addresses the following issue: - Added support for pagination within Design Center. When running `designcenter project list`, you can now pass `--pageIndex` to set number of the page to retrieve from a paginated project, and `--pageSize` to set the number of results per page. ## [](#version-3-0-4-january-18-2019)Version 3.0.4 - January 18, 2019 This release of Anypoint Platform CLI adds the following Exchange feature: - Added `mainFile` option to determine a main file for OAS and WSDL API types when publishing an API specification to Exchange. ## [](#version-3-0-3-december-27-2018)Version 3.0.3 - December 27, 2018 This release of the Anypoint CLI fixes the following issue: - `api-mgr api manage` command when using `--referencesUserDomain true` on Hybrid does not checks the **Reference User Domain** checkmark when viewing the API in the API Manager UI. ## [](#version-3-0-2-december-12-2018)Version 3.0.2 - December 12, 2018 This release of Anypoint CLI focuses on bug fixes. ## [](#version-3-0-1-november-20-2018)Version 3.0.1 - November 20, 2018 This release of Anypoint CLI focuses on bug fixes. ## [](#version-3-0-0-october-5-2018)Version 3.0.0 - October 5, 2018 This release of the Anypoint CLI includes CLI commands for API Manager 2.x (crowd release) - Added support for API Manager v2. - Removed previous api-mgr commands (API Manage v1). - Renamed api-mgr applications \* → api-mgr contract \*. - Renamed api-mgr tiers \* → api-mgr tier \*. - Fixed an issue whereby if an API contained null values, it was trowing an error. - Added support for graphQL APIs. - Removed support for Node < 8.12.0. ## [](#see-also)See Also - [anypoint-cli::troubleshooting.adoc](#anypoint-cli::troubleshooting.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform EU Control Plane Release Notes: December 15, 2017 This document describes new features and enhancements, known limitations, issues, and fixes in EU control plane. ## [](#new-features-and-enhancements)New Features and Enhancements Beginning on December 15, 2017 the Anypoint Platform control plane is available in the European Union. This release includes the following new features and enhancements: - EU control plane deployed in EU - Runtime Manager supports deploying to applications to CloudHub hosted in the EU. - The `amc_setup` command supports `eu1` as value of the `region` option. This enables you to connect a customer-managed Mule runtime to the EU control plane. - Mule runtime includes changes to the `wrapper.conf` file and the command line that support connecting to the EU control plane. - Support for Object Store v2. ## [](#changes-in-this-release)Changes in This Release There are no changes in this release. ## [](#fixed-issues)Fixed Issues There are no fixed issues in this release. ## [](#known-limitations-and-workarounds)Known Limitations and Workarounds This section lists known limitations and workarounds for this release. - Public exchange is not fully supported in this release. Although certain public assets are available in the EU control plane, the full set of public assets are not available. To take advantage of assets available in the public Exchange of the US control plane, copy those assets to a private Exchange within the EU control plane. Private Exchange is fully supported in the EU control plane. - When deploying to CloudHub, you can only deploy applications and gateways to the Frankfurt region. Additionally, the number of supported Mule runtime versions is smaller. - Object Store v1 is not supported. - Anypoint Platform users must create a separate account to access the EU control plane. - You can only create dedicated load balancers and virtual private clouds (VPCs) in the Frankfurt region. The suffix for the external domain names of dedicated load balancers on the EU control plane is `lb-prod-eu-rt.anypointdns.net`. - Migration between regions is a manual process. You must manually copy each asset from the US control to the EU control plane. ## [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements in this release. ## [](#compatibility-notes)Compatibility Notes - CloudHub When deploying an application to CloudHub in the EU control plane, only the following versions of the Mule runtime are supported: - 3.8.5 or later - 3.9.0 or later - 4.0.0 or later - API Gateway 2.2.0 - Customer-managed Mule Runtimes (Hybrid) When deploying to a customer-managed runtime, Mule runtime version 3.x is supported as long as you are using Mule Runtime Manager Agent, version 1.9.2. This version is bundled with Mule runtime, version 3.8.x and later. To use earlier versions of Mule runtime, you must download version 3.8.x and install version 1.9.2 of the Runtime Manager Agent in your environment. - Anypoint Studio Anypoint Studio versions 6.4.2 and 7.0.1 support the Anypoint Platform EU control plane. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Private Cloud Edition 3.2.0 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition. ## [](#january-17-2023)January 17, 2023 ## What’s New This version of Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) contains security and vulnerability fixes, accessibility improvements, and the following features and enhancements: - API Platform - Support for OAS 3.0. - Access Management - Support for multiple external identity providers (IdPs). See [Features Shipped with Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/#features-shipped-with-anypoint-platform-pce-version-3-2) for details on component versions. ## Compatibility
Compatibility with Version

Mule runtime engine

3.9.x, 4.1.x, 4.2.x, 4.3.0, 4.4.0

Anypoint Runtime Manager Agent

1.7 through 1.9.x, 2.1.x and later

Anypoint Studio

7.15 and later

Infrastructure

* VMWare * Bare metal * Amazon Web Services
## Known Issues
Known Issue Workaround ID

When you add dependencies to a project in Studio, Studio does not display available modules from Exchange.

To see available modules, search directly from Exchange.

AOP-3771

Organization names cannot start with api.

This is a known issue that affects API Manager functionality. Do not start organization names with api.

N/A

Design Center DB Migrations attempts to connect to an external source on an isolated environment.

N/A

W-12506348

Stolon is not upgraded when you upgrade a cluster from version 3.0.x to version 3.1.x and then to 3.2.x.

Before upgrading to 3.2.0, remove the stolon-upgrade-pg11 secret and configmap files if they exist.

W-13578311
## Upgrade Upgrades are supported from PCE 3.1.x. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/3.2/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Private Cloud Edition 3.2.1 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition. ## [](#march-6-2023)March 6, 2023 ## What’s New See [Features Shipped with Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/#features-shipped-with-anypoint-platform-pce-version-3-2) for details on component versions. ## Compatibility
Compatibility with Version

Mule runtime engine

3.9.x, 4.1.x, 4.2.x, 4.3.0, 4.4.0

Anypoint Runtime Manager Agent

1.7 through 1.9.x, 2.1.x and later

Anypoint Studio

7.15 and later

Infrastructure

* VMWare * Bare metal * Amazon Web Services
## Fixed Issues
Issue ID

Design Center DB Migrations attempts to connect to an external source on an isolated environment.

W-12506348
## Known Issues
Known Issue Workaround ID

When you add dependencies to a project in Studio, Studio does not display available modules from Exchange.

To see available modules, search directly from Exchange.

AOP-3771

Organization names cannot start with api.

This is a known issue that affects API Manager functionality. Do not start organization names with api.

N/A

Stolon is not upgraded when you upgrade a cluster from version 3.0.x to version 3.1.x and then to 3.2.x.

Before upgrading to 3.2.1, remove the stolon-upgrade-pg11 secret and configmap files if they exist.

W-13578311
## Upgrade Upgrades are supported from PCE 3.1.x. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/3.2/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Private Cloud Edition 3.2.2 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition. ## [](#august-2-2023)August 2, 2023 ## What’s New - This version of Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) contains security and vulnerability fixes. - This release adds support for RHEL 8.7 and 8.8. - This release adds support to API Console Proxy and Trusted Domains. For guidance on how to add new trusted domains, see [Trusted Domains](https://docs.mulesoft.com/private-cloud/latest/config-add-proxy-allowlist#trusted-domains). - This release adds a 30-minute account locking after 100 failed local user login attempts. ## Compatibility
Compatibility with Version

Mule runtime engine

3.9.x, 4.1.x, 4.2.x, 4.3.0, 4.4.0

Anypoint Runtime Manager Agent

1.7 through 1.9.x, 2.1.x and later

Anypoint Studio

7.15 and later

Infrastructure

* VMWare

* Bare metal

* Amazon Web Services
## Fixed Issues
Issue ID

Stolon is now upgraded when you upgrade a cluster from version 3.0.x to version 3.1.x and then to 3.2.x.

W-13578311

All new environments now display correctly, and no team permission errors occur after a new install.

W-12063059
## Known Issues
Known Issue Workaround ID

When you add dependencies to a project in Studio, Studio does not display available modules from Exchange.

To see available modules, search directly from Exchange.

AOP-3771

Organization names cannot start with api.

This is a known issue that affects API Manager functionality. Do not start organization names with api.

N/A

False cluster alerts for Gravity 9.0.3 and 9.0.4: etcdInsufficientMembers appear when you run the gravity status command

This is a known issue and safe to ignore. It is fixed in PCE 3.2.3 with Gravity >=v9.0.5

W-14989671
## Upgrade Upgrades are supported from PCE 3.1.x. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/3.2/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Private Cloud Edition 3.2.3 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition. ## [](#march-1-2024)March 1, 2024 ## What’s New - This version of Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) contains security and vulnerability fixes. - This release adds support for RHEL 8.9, 8.10, 9.0, 9.2, and 9.3. ## Compatibility
Compatibility with Version

Mule runtime engine

* 3.9.x and 4.1.x with Java 8

* 4.2.x, 4.3.0, 4.4.0, and 4.5.0 with Java 8 and 11

* 4.6.0 with Java 8 and 11

Anypoint Runtime Manager Agent

1.7 through 1.9.x, 2.1.x and later

Anypoint Studio

7.15 and later

Infrastructure

* VMWare

* Bare metal

* Amazon Web Services
## Fixed Issues
Issue ID

Pithos CPU and memory resources limit is increased.

W-14331382

Cassandra is bumped to 4.0.11.

W-14497055

Periods in usernames for LDAP-sourced accounts are now allowed.

W-14288980

NPM start-up errors no longer occur in many services.

W-14601803

Didactic issues no longer occur in Access Management.

W-14628545

PCE 3.2.2 install and upgrade no longer fails.

W-15132469

Gravity no longer displays alerts if they are info level only.

W-14989671
## Known Issues
Known Issue Workaround ID

When you add dependencies to a project in Studio, Studio does not display available modules from Exchange.

To see available modules, search directly from Exchange.

AOP-3771

Organization names cannot start with api.

This is a known issue that affects API Manager functionality. Do not start organization names with api.

N/A

Upgrades from 3.2 versions with AMV Add-on get stuck waiting for dias-prov-k8s-am-influxdb-comp-data pods to come up

Rollback dias-prov-k8s-am-influxdb-comp-data helm release to unblock pods in Pending status.

W-15346023
## Upgrade Upgrades are supported from PCE 3.1.x. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/3.2/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Platform Private Cloud Edition 3.2.4 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition. ## [](#january-30-2025)January 30, 2025 ## What’s New - This version of Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) contains security and vulnerability fixes. - This release adds support for RHEL 9.2, 9.3, 9.4, and 9.5. ## Compatibility
Compatibility with Version

Mule runtime engine

* 3.9.x and 4.1.x with Java 8 * 4.2.x, 4.3.0, 4.4.0, and 4.5.0 with Java 8 and 11 * 4.6.0 with Java 8 and 11

Anypoint Runtime Manager Agent

1.7 through 1.9.x, 2.1.x and later

Anypoint Studio

7.15 and later

Infrastructure

* VMWare * Bare metal * Amazon Web Services
## Fixed Issues
Issue Resolution ID

Security vulnerabilities are fixed.

W-16837891, W-16838272, W-17250684

Updated PSP for services deployed for STIG requirements.

W-16556295

Updated PSP for services defined in the core-paas-namespaces service for STIG requirements.

W-16574008

Alerts are no longer missing for API manager.

W-16912884

OIDC redirect URL for Identity Client Registration is no longer incorrect in Anypoint Platform PCE.

W-16735355

Multiple external IDPs now work correctly in Anypoint Platform PCE.

W-16848460

The option to configure a SMTP server is no longer missing in Access Management.

W-17589581

Services now appear correctly in the Access Management UI.

W-17589622

The LDAP login no longer returns an invalid response type.

W-16784075

Anypoint Platform PCE cluster creation no longer fails if AMV is enabled.

W-17555281

The backup process now backs up more than 1000 files per bucket.

W-15461160

You can now disable DNS configuration updates in the Anypoint Platform PCE UI.

W-16656021

API manager proxy no longer fails with error code 503 for proxy application deployments.

W-16610874

The change_owner.js is no longer missing from the authentication-server image in Access Management.

W-17417832

You can now add properties correctly in apps deployed with a hybrid server.

W-16407330

You can now create identity providers correctly in the Access Management UI.

W-12169648, W-12074377

The error 500 no longer occurs while creating a project type in Design Center.

W-16952001

You can now access Runtime Manager correctly from Access Management.

W-17610679

The Create error no longer occurs for a 7-node cluster with the latest installer.

W-17600311, W-17606442

You can now import a dependency correctly from exchange.

W-11676181

You can now create asyncAPI correctly in Design Center.

W-12061692

A newly created user no longer experiences "Session has Expired" when accessing Design Center.

W-12065654

Environments now display correctly in Access Management following a new installation. Additionally, the creation of a new team also functions properly.

W-12063059

Design Center Import no longer returns 500 Internal Server error.

W-11890588

An unsupported field schema exception no longer occurs while adding a policy in the API Manager UI.

W-11741358

Deploying an application in Runtime Manager no longer returns a blank page with the message NotAuthrorizedException.

W-11983041

When deploying an application in Runtime Manager, the UI displays the correct Deploy button.

W-11603890

Policies are now applied correctly to an application.

W-17672003

Upgrade paths to Anypoint Platform 3.2.4 now works correctly.

W-17656610

There is no longer mismatch in replica counts for services for Anypoint Platform 3.2.4.

W-17591099

OPS center login now works correctly for 7-node cluster with AMV enabled.

W-17591099

OPS center access now works correctly.

W-12058486

Alert based emails are now triggered correctly.

W-16572559

You can now close correctly the actions window for a server group or cluster.

W-11613216
## Upgrade Upgrades are supported from PCE 3.1.x. ## [](#see-also)See Also - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/3.2/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 3.2.5 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#april-3-2025)April 3, 2025 ## What’s New - This version of Anypoint Platform PCE contains security and vulnerability fixes. - In Design Center, the **Merge** functionality to merge changes from a feature branch into the main branch is not available for Anypoint Platform PCE environments. - To see updated users permissions in Exchange, users must log out of Exchange and log in again. For details, refer to [Set User Access Permissions](https://docs.mulesoft.com/jp/exchange/to-set-permissions). - AsyncAPI is not supported in PCE 3.2.x. ## Compatibility
Compatibility with Version

Mule runtime engine

4.3.x, 4.4.x, 4.5.x, 4.6.x with Java 8 and 11

Anypoint Runtime Manager Agent

1.7 through 1.9.x, 2.1.x and later

Anypoint Studio

7.15 and later

Infrastructure

* VMWare * Bare metal * Amazon Web Services
## Fixed Issues
Issue Resolution ID

Security vulnerabilities are fixed.

W-17250565, W-17250569, W-17250573, W-17250575, W-17250576, W-17250579, W-17250582, W-17250583, W-17250584, W-17250586, W-17250589, W-17250590, W-17250591, W-17250593, W-17250595, W-17250612, W-17250616, W-17250617, W-17250623, W-17250625, W-17250669, W-17250692, W-17250695, W-17250698, W-17250706, W-17250710, W-17250713, W-17250714, W-17250721, W-17250730, W-17250733, W-17250743, W-17250746, W-17458367, W-17459472, W-17466920, W-17466922, W-17466925, W-17466926, W-17466929, W-17466931, W-17466935, W-17466938, W-17466946, W-17466947, W-17466948, W-17542778, W-17542830, W-17542883, W-17542930, W-17542956, W-17543001, W-17543091
## Upgrade Upgrades are supported from PCE 3.1.x. ## [](#see-also)See Also - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/3.2/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 4.0.0 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#october-31-2024)October 31, 2024 ### What’s New - This release supports running Anypoint Platform PCE in an enterprise-ready Kubernetes cluster. The following Kubernetes distributions have been tested: OpenShift, Amazon EKS Anywhere (EKS-A) and Rancher Kubernetes Engine (RKE2). For information, see [Upgrading Anypoint Platform PCE 3.2.3 to 4.0](https://docs.mulesoft.com/private-cloud/latest/upgrade). - This release supports Java 17. - This release is compatible with Mule runtime engine versions 4.3 - 4.6. Use version 4.6 LTS to get the best performance from all Anypoint Platform connectors. - The internal Identity Provider (IDP) does not support Multi-Factor Authentication (MFA). Use an external IDP. - Anypoint Monitoring Visualizer (AMV) is not supported in this release. - Anypoint Platform PCE isn’t compatible with CloudHub 2.0. In the Runtime Manager UI, under **Application Manager > Alerts**, the option to filter by CloudHub 2.0 doesn’t apply to Anypoint Platform PCE. ## Compatibility
Compatibility with Version

Mule runtime engine

4.3.x, 4.4.x, 4.6.x with Java 8 and 11
4.6.x with Java 17

Anypoint Runtime Manager Agent

2.6.7

Anypoint Studio

7.19 and later
## Upgrade Upgrades to Anypoint Platform PCE 4.0 are supported only from version 3.2.3. ## [](#see-also)See Also - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/4.0/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 4.1.0 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#july-17-2025)July 17, 2025 ### What’s New - Anypoint Platform PCE now supports installation on any Kubernetes cluster, regardless of the number of nodes, and can be co-located with other Mule applications on a shared Kubernetes cluster. - The Anypoint Platform PCE installation time is reduced by 60 percent. - You can install Anypoint Platform PCE on FIPS-enabled hosts and FIPS-enabled Kubernetes clusters. - Anypoint Platform PCE services now have Horizontal Pod Autoscaling (HPA) enabled, allowing for dynamic scaling to manage peak workloads. - Mitigation of CAT-I STIGS for services addressed and resolved critical CAT-I STIGS for Anypoint Platform PCE Mule applications. - Anypoint Platform PCE 4.1 installation is tested and validated on various Kubernetes distributions, including Rancher RKE2, OpenShift, and AWS-EKS. - You can [upload custom policies and publish assets to Exchange using the Maven client](https://docs.mulesoft.com/private-cloud/latest/custom-policies). ## Compatibility
Compatibility with Version

Mule runtime engine

4.6.x and 4.7.x with Java 8, 11, and 17

Anypoint Runtime Manager Agent

2.6.7

Anypoint Studio

7.19 and later

Kubernetes

1.32.x and 1.31.x
## Upgrade Upgrades to Anypoint Platform PCE 4.1 are supported only from version 3.2.3 or higher. ## [](#see-also)See Also - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/4.1/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 4.1.2 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#october-30-2025)October 30, 2025 ### What’s New - Anypoint Platform PCE 4.1.2 is now validated and supported on vSphere Kubernetes Service (VKS) platform with Kubernetes version 1.33. This new capability provides greater flexibility and control when managing and deploying your applications in a private cloud setting. - Anypoint Platform PCE 4.1.2 is incompatible with RedHat OpenShift environments that are FIPS-enabled. ## Compatibility
Compatibility with Version

Mule runtime engine

4.6 with Java 8 ,11 and 17, 4.9 with Java 17

Anypoint Runtime Manager Agent

2.6.7

Anypoint Studio

7.19 and later

Kubernetes

1.33, 1.32.x, 1.31.x
## Upgrade Upgrades to Anypoint Platform PCE 4.1 are supported only from version 3.2.3 or later. ## [](#see-also)See Also - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/4.1/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 4.1.3 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#november-24-2025)November 24, 2025 ### What’s New - You can now deploy Anypoint Platform PCE 4.1.3 on the Red Hat Openshift platform with FIPS enabled. - These Mule 4.9 connectors are also validated in the Anypoint Platform PCE 4.1.3 environment: - [A2A Connector](https://docs.mulesoft.com/a2a-connector/latest/) - [MCP Connector](https://docs.mulesoft.com/mcp-connector/latest/) - [MuleSoft AI Chain Connector](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/) - [MuleSoft Inference Connector](https://docs.mulesoft.com/mulesoft-inference-connector/latest/) ## Compatibility
Compatibility with Version

Mule runtime engine

4.6 with Java 8 ,11 and 17, 4.9 with Java 17

Anypoint Runtime Manager Agent

2.6.7

Anypoint Studio

7.19 and later

Kubernetes

1.33, 1.32.x, 1.31.x
## Fixed Issues
Issue Resolution ID

API Manager now connects successfully to Access Management in FIPS-enabled OpenShift environments.

W-20062877

Access Management now successfully issues authentication tokens in FIPS-enabled OpenShift environments.

W-19995052

The platform-message-service pods now start successfully in FIPS-enabled OpenShift and RKE2 environments.

W-19976892
## Upgrade Upgrades to Anypoint Platform PCE 4.1 are supported only from version 3.2.3 or later. ## [](#see-also)See Also - [NFS エラーのトラブルシューティング](https://docs.mulesoft.com/jp/private-cloud/4.1/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 4.2.0 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#april-30-2026)April 30, 2026 ### What’s New - Anypoint Platform PCE now supports Kubernetes version 1.34. - Updated guidelines on how to migrate Anypoint Platform PCE version 3.x to 4.x. For information, see [Upgrading Anypoint Platform PCE 3.x to 4.x](https://docs.mulesoft.com/private-cloud/latest/upgrade). - Anypoint Platform PCE now supports TLSv1.2+EMS and TLSv1.3 to ensure full compliance with FIPS-140-3 security standards. Connections from legacy clients will be rejected, including: - TLSv1.0 and TLSv1.1 protocols - TLSv1.2 clients without Extended Master Secret (EMS) support - OpenSSL versions older than 1.0.2 - Java versions older than 8u261 Most modern web browsers have natively supported TLSv1.2+EMS and TLSv1.3 since approximately 2015. All Mule versions listed in the official Anypoint PCE documentation remain compatible. However, to maintain TLSv1.3 and FIPS-140-3 compliance, use Anypoint Runtime Manager Agent version 2.7.12 or later. This version is already included in Mule versions 4.9.16+ and 4.11.3+. - CSI Driver Support - Anypoint Platform PCE 4.2.0 now mandates a pre-installed Kubernetes CSI driver for NFS mounting. - The previous method of mounting NFS using host binaries is no longer supported. - The `input.yaml` configuration now requires the `fileSystemCsiDriverName` parameter. - Users of the EFS CSI Driver must provide four specific filesystem volume handles in the configuration. For details, refer to [CSI Driver Requirement](https://docs.mulesoft.com/private-cloud/latest/verify-nfs#csi-driver-requirement). - Override Default NFS Mount Options - You can now override default NFS mount options (for example, to remove noresvport) in the input.yaml. - Use the optional override fields: - `fileSystemBareMountOptionsOverride` - `fileSystemWcMountOptionsOverride` - `fileSystem01MountOptionsOverride` For details, refer to [Override NFS Mount Options](https://docs.mulesoft.com/private-cloud/latest/verify-nfs#nfs-mount-options-override). ## Compatibility
Compatibility with Version

Mule runtime engine

4.6 with Java 8 ,11 and 17, 4.9 with Java 17, 4.11 with Java 17

Anypoint Runtime Manager Agent

2.7.2 and later

Anypoint Studio

7.19 and later

Kubernetes

1.34, 1.33, 1.32.x

FIPS

140-3
## Fixed Issues
Issue Resolution ID

Users with periods in their usernames can now successfully log in via LDAP for the first time without prior import.

W-14288980

A JSON validation error no longer occurs when attempting to add or delete scopes for existing "Client" type Connected Apps.

W-20017921
## Upgrade Upgrades to Anypoint Platform PCE 4.2 are supported only from version 3.2.3 or later. ## [](#see-also)See Also - [Troubleshooting NFS Errors](https://docs.mulesoft.com/private-cloud/latest/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 4.2.1 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#july-20-2026)July 20, 2026 ### What’s New - Anypoint Platform PCE now supports Mule Runtime 4.12 Edge, enabling you to deploy and manage applications on the latest Mule runtime version. - Anypoint PCE 4.2.1 introduces the ability to install the platform with non-admin privileges, providing greater flexibility and enhanced security alignment when deploying in shared environments. - Anypoint Platform PCE now supports Direct Telemetry Streaming, which enables telemetry data to stream directly from the Mule runtime engine to the Anypoint Monitoring stack without intermediate aggregation. - Anypoint Platform PCE now supports Dual Ingestion, enabling you to run both the legacy Anypoint Monitoring stack and the new OpenTelemetry Direct Telemetry Stream simultaneously during migration. - Anypoint Platform PCE now provides expanded OpenTelemetry support for Mule runtime monitoring metrics, including JVM statistics, flow execution metrics, and connector metrics. ## Compatibility
Compatibility with Version

Mule runtime engine

4.6 with Java 8 and 11, 4.9 with Java 17, 4.11 with Java 17, 4.12 Edge with Java 17

Anypoint Runtime Manager Agent

2.7.2 and later

Anypoint Studio

7.19 and later

Kubernetes

1.34, 1.33.x, 1.32.x
## Fixed Issues
Issue Resolution ID

Creating or publishing a new API asset no longer fails with a 400 Bad Request error caused by an invalid environment API ID format.

W-22731971

Unsupported components such as Anypoint Monitoring and Visualizer no longer appear as selectable options when configuring scopes for Connected Apps.

W-22607265

After upgrading from Anypoint PCE 3.2.5 to 4.2.x using the backup and restore process, the monitoring dashboard no longer fails to load with a 502 Bad Gateway error.

W-22210600, W-22253905

When performing a backup and restore on an Anypoint PCE 4.2 cluster, Anypoint Monitoring and Visualizer no longer fail to generate metrics with a 500 Internal Server Error.

W-22253939

Adding or modifying a login disclaimer in Access Management no longer fails with a 500 Internal Server Error.

W-23032790

Platform backup and restore on an Anypoint PCE 4.2.x cluster no longer fails with a Forbidden error.

W-23094469

The Trusted Domains page in Access Management no longer returns a 404 Not Found error.

W-23035185

When deploying an application to a hybrid server for the first time, custom properties no longer disappear during initial deployment.

W-22287104

When creating or publishing a new API asset in API Manager, the operation no longer fails with a 400 Bad Request error regarding the environmentApiId format.

W-23076590
## Upgrade In-place upgrades to Anypoint Platform PCE 4.2.1 are supported only from version 4.1.1 or later. ## [](#see-also)See Also - [Troubleshooting NFS Errors](https://docs.mulesoft.com/private-cloud/latest/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition 4.3.0 Release Notes These release notes describe updates to Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). ## [](#october-6-2026)October 6, 2026 ### What’s New - You can now use Anypoint Code Builder to design, implement, and deploy Mule apps on Anypoint Platform PCE. You can optionally use MuleSoft Vibes skills to complete these tasks with natural language. For more information, see: - [Deploying Mule Applications to Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/deploy-apps) - [Configuring Anypoint Code Builder for Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/config-code-builder) - [Deploying Mule Applications Using Anypoint Code Builder](https://docs.mulesoft.com/private-cloud/latest/deploy-apps-code-builder) - Anypoint Platform PCE now supports Kubernetes version 1.35. - You can now use Kubernetes StorageClass mode for the platform shared filesystem, in addition to NFS mode. Anypoint Platform PCE can dynamically provision ReadWriteMany (RWX) shared volumes from a `StorageClass` you provide, so you don’t have to operate an external NFS server. For details, see [StorageClass Mode](https://docs.mulesoft.com/private-cloud/latest/verify-nfs#storage-class-mode) and [Shared Filesystem Prerequisites](https://docs.mulesoft.com/private-cloud/latest/verify-nfs). - You can now deploy Anypoint Platform PCE services into customer-managed Kubernetes namespaces by using Bring Your Own Namespaces (BYONS). When you use BYONS, create the required namespaces with the MuleSoft labels and provide a ConfigMap that maps logical namespace names to the actual namespaces in your cluster. For more information, see [Installing Anypoint Platform PCE with Bring Your Own Namespaces](https://docs.mulesoft.com/private-cloud/latest/install-byons). - Anypoint Platform PCE 4.3.0 doesn’t include the bundled Prometheus and Grafana monitoring stack. The Configuring Grafana Dashboards topic doesn’t apply to this version. When you upgrade, you can keep an existing monitoring stack, connect your own Prometheus instance, or remove the monitoring namespace. Contact MuleSoft Professional Services for upgrade guidance. - Anypoint Platform PCE 4.3.0 introduces the ability to configure a custom sender email address for outbound SMTP alert notifications, instead of using the default system-generated address. This lets administrators send alert emails from a domain that matches their organization’s branding and email policies. Available in all Anypoint Platform PCE installation modes. For more information, see [Set a Custom Sender Address](https://docs.mulesoft.com/private-cloud/latest/access-management-SMTP#set-a-custom-sender-address). ## Compatibility
Compatibility with Version

Mule runtime engine

4.6 with Java 8 and 17, 4.9 with Java 17, 4.11 with Java 17, 4.12 with Java 17

Anypoint Runtime Manager Agent

2.7.2 and later

Anypoint Studio

7.19 and later

Kubernetes

1.35.x, 1.34.x, 1.33.x, 1.32.x

FIPS

140-3
## Upgrade Upgrades to Anypoint Platform PCE 4.3 are supported only from version 4.1.0 or later. For more information, see [Migrating Anypoint Platform PCE v3.X to v4.X](https://docs.mulesoft.com/private-cloud/latest/upgrade). ## [](#see-also)See Also - [Deploying Mule Applications to Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/deploy-apps) - [Configuring Anypoint Code Builder for Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/config-code-builder) - [Deploying Mule Applications Using Anypoint Code Builder](https://docs.mulesoft.com/private-cloud/latest/deploy-apps-code-builder) - [Shared Filesystem Prerequisites](https://docs.mulesoft.com/private-cloud/latest/verify-nfs) - [Installing Anypoint Platform PCE with Bring Your Own Namespaces](https://docs.mulesoft.com/private-cloud/latest/install-byons) - [Configuring SMTP in Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/access-management-SMTP) - [Troubleshooting NFS Errors](https://docs.mulesoft.com/private-cloud/latest/troubleshoot-nfs) - [Known Issues](https://help.salesforce.com/s/issues) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # Anypoint Platform Private Cloud Edition Release Notes - [Anypoint Platform Private Cloud Edition 4.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.3.0-release-notes) - [Anypoint Platform Private Cloud Edition 4.2.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.2.1-release-notes) - [Anypoint Platform Private Cloud Edition 4.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.2.0-release-notes) - [Anypoint Platform Private Cloud Edition 4.1.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.1.3-release-notes) - [Anypoint Platform Private Cloud Edition 4.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.1.2-release-notes) - [Anypoint Platform Private Cloud Edition 4.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.1.0-release-notes) - [Anypoint Platform Private Cloud Edition 4.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.0.0-release-notes) - [Anypoint Platform Private Cloud Edition 3.2.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-3.2.5-release-notes) - [Anypoint Platform Private Cloud Edition 3.2.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-3.2.4-release-notes) - [Anypoint Platform Private Cloud Edition 3.2.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-3.2.3-release-notes) - [Anypoint Platform Private Cloud Edition 3.2.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-3.2.2-release-notes) - [Anypoint Platform Private Cloud Edition 3.2.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-3.2.1-release-notes) - [Anypoint Platform Private Cloud Edition 3.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-3.2.0-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Fabric 1.x.x Release Notes The following are release notes for Runtime Fabric v1.x.x. The latest downloadable package versions are displayed in the **Runtime Fabric downloads** page, located in Anypoint Runtime Manager in the **Runtime Fabrics** tab. A link to each package’s release notes is provided. For additional information on cluster-level component (installer package) upgrades, refer to [Anypoint Runtime Fabric Installer Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-installer-release-notes). Make sure to perform a cluster-level component upgrade if a new version of the installer package is available. Refer to [Upgrade Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/upgrade-index) for more information. Complete Runtime Fabric documentation is available at [Anypoint Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/) documentation.

Starting September 2022, agent releases for Runtime Fabric appliance distributions will continue on the v1.x.x line. Runtime Fabric agent releases on the v2.0.0 line apply only to partner platforms (both Kubernetes and VMs/Bare Metal).
Runtime Fabric agent 1.13.112 and later should only be used with (rtf-installer) versions 2.0.1661808686-2ff0e92 or later.
## [](#1-13-133)1.13.133 **June 30, 2023** ### Fixed Issues
Issue Resolution ID

This release includes several security fixes.

W-12692341

The Applications dashboard now automatically picks up a series of values and updates the dashboard view correctly.

W-12975095
## [](#1-13-112)1.13.112 **January 23, 2023** ### What’s New - The use of custom Log4j appenders is now disabled by default in Runtime Fabric. See [Integrating with Your Logging System Using Log4j](https://docs.mulesoft.com/runtime-fabric/latest/use-log4j-appender) for more information on enabling and using Log4j appenders. - This release includes security fixes. - Updated dependencies for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:v1.13.112` - coreAction: `mulesoft/rtf-core-actions:v1.0.48` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:v1.3.62` - clusterOps: `mulesoft/rtf-cluster-ops:v1.2.5` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:v1.2.74` - appInit: `mulesoft/rtf-app-init:v1.0.76` - persistenceGateway: `mulesoft/rtf-object-store:v1.0.102` - nginx: `mulesoft/base-image-nginx-1.21.1:v1.2.15` - resourceFetcher: `mulesoft/rtf-resource-fetcher:v1.0.92` - rtfDaemon: `mulesoft/rtf-daemon:v1.0.76` ### Fixed Issues
Issue Resolution ID

This release contains security fixes.

W-12082836

Grafana dashboards no longer show inaccurate data for application graphs.

W-11431389

Agent disconnect issue no longer occurs after upgrading to the latest version.

W-12042544

Edge in Runtime Fabric gravity appliance now initializes in http-only mode.

W-12101525

The core pricing metrics error disabled due to missing asset_id configuration no longer occurs in Runtime Fabric.

W-13136267

Monitoring sidecar no longer produces error logs.

W-11559681
## [](#1-13-91)1.13.91 **November 17, 2022** ### What’s New - You can now use a Log4j appender to integrate your logging system with applications deployed to Runtime Fabric. - You can now dynamically apply log levels when deploying apps on Runtime Fabric. - This release upgrades Fluent Bit to version 1.2.83 for external log forwarding. - This release includes security fixes. - Updated dependencies for installing and managing Runtime Fabric with a local registry: - agent version: `mulesoft/rtf-agent:v1.13.91` - coreAction: `mulesoft/rtf-core-actions:v1.0.44` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:v1.3.40` - clusterOps: `mulesoft/rtf-cluster-ops:v1.2.2` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:v1.2.75` - appInit: `mulesoft/rtf-app-init:v1.0.73` - persistenceGateway: `mulesoft/rtf-object-store:v1.0.98` - nginx: `mulesoft/base-image-nginx-1.21.1:v1.2.9` - resourceFetcher: `mulesoft/rtf-resource-fetcher:v1.0.88` - rtfDaemon: `mulesoft/rtf-daemon:v1.0.70` ### Fixed Issues
Description Issue

This release contains a security fix.

W-12045345

The Runtime Fabric agent no longer reports an OOM Killer process.

W-11558741

Persistence gateway pod replicas are no longer incorrectly scheduled on the same node.

W-10867273
### Known Issues
Known Issue Workaround ID

This upgrade includes a runtime log format change which may impact Anypoint Monitoring log forwarding.

W-12082202
## [](#1-13-54)1.13.54 **August 3, 2022** ### What’s New - This release adds supports for Kubernetes version 1.23 on Microsoft Azure Kubernetes Service (AKS). - This release upgrades Fluent Bit to version 1.8.14 for external log forwarding. - Reported security vulnerabilities are now fixed. - Updated dependencies for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:v1.13.54` - coreAction: `mulesoft/rtf-core-actions:v1.0.30` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:v1.3.26` - clusterOps: `mulesoft/rtf-cluster-ops:v1.1.63` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:v1.2.61` - appInit: `mulesoft/rtf-app-init:v1.0.51` - persistenceGateway: `mulesoft/rtf-object-store:v1.0.74` - nginx: `mulesoft/base-image-nginx-1.21.1:v1.1.37` - resourceFetcher: `mulesoft/rtf-resource-fetcher:v1.0.71` - rtfDaemon: `mulesoft/rtf-daemon:v1.0.51` ### Fixed Issues
Description Issue

The Runtime Fabric agent no longer restarts after an upgrade because of a WebSocket connection failure.

W-11217136

Runtime Fabric services running in EKS clusters now refresh service tokens as expected.

W-11188620

This release contains security fixes for Runtime Fabric components.

W-11302288
### [](#kubernetes-support)Kubernetes Support This version of Runtime Fabric on Self-Managed Kubernetes supports the following Kubernetes versions: - 1.19.x - 1.20.10 or later patch versions on 1.20.x - 1.21.3 or later patch versions on 1.21.x - 1.22.x - 1.23.x (on AKS only) ## [](#1-13-6)1.13.6 **June 2, 2022** ### What’s New - Updated dependencies for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:v1.13.6` - appInit: `mulesoft/rtf-app-init:v1.0.51` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:v1.2.49` - resourceFetcher: `mulesoft/rtf-resource-fetcher:v1.0.59` - nginx: `mulesoft/base-image-nginx-1.21.1:v1.1.29` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:v1.3.20` - clusterOps: `mulesoft/rtf-cluster-ops:v1.1.48` - coreAction: `mulesoft/rtf-core-actions:v1.0.21` - persistenceGateway: `mulesoft/rtf-object-store:v1.0.61` - rtfDaemon: `mulesoft/rtf-daemon:v1.0.29` ### Fixed Issues
Description Issue

Nodes no longer show incorrect CPU values after an upgrade to 1.13.6 or later.

W-11227257
## [](#1-13-0)1.13.0 **May 24, 2022** ### What’s New - You can now use Helm to install and upgrade Runtime Fabric on Self-Managed Kubernetes. Refer to [Installing Runtime Fabric on Self-Managed Kubernetes Using Helm](https://docs.mulesoft.com/runtime-fabric/latest/install-helm) for instructions. Note that Helm upgrades are not available for existing installations that used the `rtfctl` command line tool. - This release adds support for Kubernetes version 1.22.x for Runtime Fabric on Self-Managed Kubernetes. This Kubernetes version [removes several deprecated APIs](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22). See [Kubernetes Support](#kubernetes-support) for a full list of supported Kubernetes versions. - Updated dependencies for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:v1.13.0` - appInit: `mulesoft/rtf-app-init:v1.0.51` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:v1.2.49` - resourceFetcher: `mulesoft/rtf-resource-fetcher:v1.0.59` - nginx: `mulesoft/base-image-nginx-1.21.1:v1.1.29` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:v1.3.20` - clusterOps: `mulesoft/rtf-cluster-ops:v1.1.48` - coreAction: `mulesoft/rtf-core-actions:v1.0.21` - persistenceGateway: `mulesoft/rtf-object-store:v1.0.61` - rtfDaemon: `mulesoft/rtf-daemon:v1.0.29` ### Fixed Issues
Description Issue

The rtfctl backup command for Runtime Fabric on VMs / Bare Metal, now correctly backs up ClusterRole and ClusterRoleBinding for the external log forwarder.

W-10760181

This release corrects an issue in which the control plane reported a mismatch in agent versions.

W-10985884

This release contains security fixes for all Runtime Fabric components.

N/A

This release adds TCP keep-alive processing to ingress inbound connections.

W-10818442

Anypoint Security Edge logs are now written to both file and stdout.

W-11037800

Anypoint Security Edge logs are now rotated.

W-11037810
### Known Issues
Known Issue Workaround ID

If you plan to rollback to a version earlier than 1.13.0, and you have Anypoint Monitoring log forwarder enabled, you must disable it before you trigger the rollback. You can re-enable it after the rollback completes.

N/A

N/A
### [](#kubernetes-support-2)Kubernetes Support This version of Runtime Fabric on Self-Managed Kubernetes supports the following Kubernetes versions: - 1.19.x - 1.20.10 or later patch versions on 1.20.x - 1.21.3 or later patch versions on 1.21.x - 1.22.x ## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Fabric 2.x.x Release Notes The following are release notes for Runtime Fabric v2.x.x. For the complete Runtime Fabric documentation, refer to [Anypoint Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/). To maintain compatibility and system integrity, customers using a private registry must synchronize the `rtf-mule-actions` image, refer to [Runtime Fabric Mule Action Image Synchronization](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-rtf-mule-action) for details.

Starting September 2022, Runtime Fabric agent releases on the v2.0.0 line apply only to partner platforms (both Kubernetes and VMs/Bare Metal). Agent releases for Runtime Fabric appliance distributions will continue on the v1.x.x line.
The following table shows Kubernetes supported versions:
K8s version Upstream K8s GA Runtime Fabric Support GA Runtime Fabric Support EOL

1.24

May 2022

January 2023

February 2024

1.25

August 2022

May 2023

June 2024

1.26

December 2022

June 2023

May 2024

1.27

April 2023

November 2023

January 2025

1.28

August 2023

March 2024

June 2025

1.29

December 2023

June 2024

October 2025

1.30

May 2024

October 2024

Runtime Fabric support of 1.34

1.31

August 2024

January 2025

Runtime Fabric support of 1.35

1.32

December 2024

June 2025

Runtime Fabric support of 1.36

1.33

April 2025

October 2025

Runtime Fabric support of 1.37
## [](#2-11-50)2.11.50 **October 3, 2025** ### What’s New - Runtime Fabric agent now supports Kubernetes version 1.33. - Runtime Fabric agent now supports Oracle Kubernetes Engine (OKE). - You can now use the MuleSoft diagnostics agent to troubleshoot Mule applications deployed to Runtime Fabric. This feature leverages Einstein generative AI to automate diagnostics collection and provide intelligent, actionable insights. For details, refer to [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/runtime-fabric/latest/view-app-diagnostics). - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.11.50` - coreAction: `mulesoft/rtf-core-actions:1.0.173` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.263` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.38` - appInit: `mulesoft/rtf-app-init:1.0.218` - persistenceGateway: `mulesoft/rtf-object-store:1.0.239` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.224` - rtfDaemon: `mulesoft/rtf-daemon:2.0.189` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.1.38` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.11.50` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.173` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.263` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.38` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.218` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.239` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.224` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.189` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.30` ### Fixed Issues
Issue Resolution ID

The resource cache no longer redownloads artifacts from AMC artifacts.

W-15901814

The client trust store now correctly trusts the DiGiCert Global Root G3 certificate.

W-19651269

This release includes security fixes.

W-19723504, W-19639371, W-19639220, W-19639164, W-18886584, W-19005736, W-19338580, W-19338562
### [](#supported-kubernetes-versions)Supported Kubernetes Versions Runtime Fabric version 2.11.50 supports these Kubernetes versions: - 1.33.x - 1.32.x - 1.31.x - 1.30.x ## [](#2-11-0)2.11.0 **July 31, 2025** ### What’s New - You can now [configure core software high availability parameters](https://docs.mulesoft.com/runtime-fabric/latest/install-helm#configure-core-software-high-availability-parameters) in your `values.yml` file when installing Runtime Fabric using Helm. - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.11.0` - coreAction: `mulesoft/rtf-core-actions:1.0.159` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.250` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.31` - appInit: `mulesoft/rtf-app-init:1.0.209` - persistenceGateway: `mulesoft/rtf-object-store:1.0.232` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.220` - rtfDaemon: `mulesoft/rtf-daemon:2.0.167` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.100` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.11.0` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.159` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.250` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.31` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.209` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.232` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.220` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.167` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29` ### Fixed Issues
Issue Resolution ID

Invalid memory address or nul pointer dereference no longer occur in Runtime Fabric cluster ops initialization.

W-19064118

This release includes security fixes.

W-19005719
### [](#supported-kubernetes-versions-2)Supported Kubernetes Versions Runtime Fabric version 2.11.0 supports these Kubernetes versions: - 1.32.x - 1.31.x - 1.30.x - 1.29.x ## [](#2-10-34)2.10.34 **June 30, 2025** ### What’s New - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.10.34` - coreAction: `mulesoft/rtf-core-actions:1.0.154` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.245` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.28` - appInit: `mulesoft/rtf-app-init:1.0.203` - persistenceGateway: `mulesoft/rtf-object-store:1.0.230` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.218` - rtfDaemon: `mulesoft/rtf-daemon:2.0.152` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.95` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.10.34` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.154` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.245` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.3.120` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.4.28` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.230` - Ubi resourceFetcher: ``mulesoft/rtf-resource-fetcher-ubi:`1.0.218`` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.152` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29` ### Fixed Issues
Issue Resolution ID

Runtime Fabric agent now correctly renders OpenShift ingress templates with TLS Edge termination configurations (tls: - {}).

W-18657349

Runtime Fabric agent now correctly manages and matches ingress templates using wildcards in tls.hosts section.

W-18472498

Runtime Fabric agent now correctly renders ingress templates with wildcard host and the actual Mule application host from the application deployment configuration, rather than the wildcard pattern.

W-18839829

Runtime Fabric now supports the deprecated Kubernetes kubernetes.io/ingress.class annotation that was removed in Runtime Fabric agent version 2.10.0. This ensures backward compatibility as you transition to the newer spec.ingressClassName field.

W-18299600

Fixed an issue where removed secure properties were not properly deleted from Kubernetes secrets, causing stale data accumulation.

W-18483799

Intermittent K8s permission errors that were observed in OpenShift or Runtime Fabric agents with version 2.7.0 and higher no longer occur.

W-17446390
### [](#supported-kubernetes-versions-3)Supported Kubernetes Versions Runtime Fabric version 2.10.34 supports these Kubernetes versions: - 1.32.x - 1.31.x - 1.30.x - 1.29.x ## [](#2-10-17)2.10.17 **April 29, 2025** - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.10.17` - coreAction: `mulesoft/rtf-core-actions:1.0.148` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.245` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.28` - appInit: `mulesoft/rtf-app-init:1.0.203` - persistenceGateway: `mulesoft/rtf-object-store:1.0.230` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.218` - rtfDaemon: `mulesoft/rtf-daemon:2.0.139` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.95` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.10.17` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.148` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.245` - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:1.3.120` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.28` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.203` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.220` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.218` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.139` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29` ### Fixed Issues
Issue Resolution ID

Now all matching placeholders in ingress templates are replaced.

W-17910019

This release includes security fixes.

W-18147430, W-18147417, W-17829739
### [](#supported-kubernetes-versions-4)Supported Kubernetes Versions Runtime Fabric version 2.10.17 supports these Kubernetes versions: - 1.31.x - 1.30.x - 1.29.x - 1.28.x ## [](#2-10-0)2.10.0 **March 25, 2025** ### What’s New - You can now [exclude nodes from Runtime Fabric cluster capacity](https://docs.mulesoft.com/jp/general/usage-metrics#exclude-node). - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.10.0` - coreAction: `mulesoft/rtf-core-actions:1.0.142` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.240` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.25` - appInit: `mulesoft/rtf-app-init:1.0.201` - persistenceGateway: `mulesoft/rtf-object-store:1.0.227` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.211` - rtfDaemon: `mulesoft/rtf-daemon:2.0.135` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.84` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.10.0` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.142` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.240` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.25` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.201` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.227` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.211` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.135` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.29` ### Fixed Issues
Issue Resolution ID

Runtime Fabric agent now correctly consumes the port number configured in the ingress template.

W-17624273

Mule apps created from an HTTP ingress template are no longer forced to use HTTPS due to the inclusion of an empty TLS block.

W-17647069

This release includes security fixes.

W-17829729, W-17744569, W-17952645, W-17794265, W-17952607

The NodeAffinity configurations defined in the Kubernetes template are now consumed by the Runtime Fabric agent without the Enforce deploying replicas across nodes flag for Mule app deployments.

W-17778302
### [](#supported-kubernetes-versions-5)Supported Kubernetes Versions Runtime Fabric version 2.10.0 supports these Kubernetes versions: - 1.31.x - 1.30.x - 1.29.x - 1.28.x ## [](#2-9-2)2.9.2 **January 14, 2025** ### What’s New - You can now [configure ingress with HTTP Route-Template Custom Resource](https://docs.mulesoft.com/runtime-fabric/latest/configure-ingress-http-resource) in Runtime Fabric.
If you upgrade to Runtime Fabric version 2.9.2 and use the ingress template with port number configuration other than 8081, then update the ingress template to either use port 8081 or use the recommended port name. For details on using port name, refer to Example Ingress Resource Templates
Currently, the `rtfctl backup` and `restore` commands aren’t supported for ingress with the HTTP Route-Template Custom Resource. After upgrading to Runtime Fabric agent 2.9.2, all new deployments and any redeployments will include the following changes: - The ingress naming convention is updated to `appName-uniqueIdentifier`. For example, for a test app, the resulting ingress name can be `test-dc844797c`. - The app ingress resource is now managed by Helm as part of the Mule application deployment. - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.9.2` - coreAction: `mulesoft/rtf-core-actions:1.0.136` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.229` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.23` - appInit: `mulesoft/rtf-app-init:1.0.199` - persistenceGateway: `mulesoft/rtf-object-store:1.0.222` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.201` - rtfDaemon: `mulesoft/rtf-daemon:2.0.129` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.72` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.9.2` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.136` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.229` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.23` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.199` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.222` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.201` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.129` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.28` ### Fixed Issues
Issue Resolution ID

Outbound network tests now point to the correct control plane.

W-17129454

OpenShift infra nodes are no longer taken into account when calculating Runtime Fabric cluster capacity.

W-17407017

The deployment manifest file no longer returns duplicate entries for the topologySpreadConstraints.

W-16985683
### [](#supported-kubernetes-versions-6)Supported Kubernetes Versions Runtime Fabric version 2.9.2 supports these Kubernetes versions: - 1.31.x - 1.30.x - 1.29.x - 1.28.x ## [](#2-8-2)2.8.2 **October 21, 2024** ### What’s New - Runtime Fabric now supports Kubernetes 1.30. - Runtime Fabric no longer runs any Kubernetes CronJob. Now, the rtf-daemon component handles the certificate renewal. - Helm-managed Runtime Fabric instances (rtf-daemon, agent, and resource-fetcher) are now FIPS 140-2 compliant. To enable FIPS, set `fipsEnabled` to `true` in the Helm `values.yml` file. For more details, see: - [Install Runtime Fabric with Helm: Optional Parameters](https://docs.mulesoft.com/runtime-fabric/latest/install-helm#optional-parameters) - [Runtime Fabric Security Architecture](https://docs.mulesoft.com/runtime-fabric/latest/security-architecture#security-diagram) - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.8.2` - coreAction: `mulesoft/rtf-core-actions:1.0.134` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.225` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.120` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.19` - appInit: `mulesoft/rtf-app-init:1.0.195` - persistenceGateway: `mulesoft/rtf-object-store:1.0.218` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.197` - rtfDaemon: `mulesoft/rtf-daemon:2.0.95` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.62` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.8.2` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.134` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.225` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.19` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.195` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.218` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.197` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.95` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.28` ### Fixed Issues
Issue Resolution ID

When retrieving object store keys, the returned keys are no longer URL-encoded.

W-16487863

Parsing ingress templates without an HTTP path defined no longer returns an error.

W-16650398

Runtime Fabric upgrades no longer fail due to flex CRD installation.

W-16563430
### [](#supported-kubernetes-versions-7)Supported Kubernetes Versions Runtime Fabric version 2.8.2 supports these Kubernetes versions: - 1.30.x - 1.29.x - 1.28.x - 1.27.x ## [](#2-7-0)2.7.0 **August 15, 2024** ### What’s New - For all OpenShift upgrades from versions 2.6.52 and earlier to versions 2.7.0 and later, manually increase the `rtfd` container resources to the desired values. See [Upgrade Pre-requisites](https://docs.mulesoft.com/runtime-fabric/latest/upgrade-pre-requisites). - Runtime Fabric OpenShift operator is available in the stable release channel. - More versions than just the last two OpenShift operator versions are now available to be installed. - CPU limit for Runtime Fabric daemon has increased from 50m to 200m. - The memory limit for Runtime Fabric daemon has increased from 250Mi to 300Mi. - In large clusters, Runtime Fabric agent and Runtime Fabric daemon have shown approximately a 25% reduction in CPU usage and a 40% reduction in overall memory consumption. Additionally, the Runtime Fabric agent’s start-up time has improved by 20%, and deployment latency has been cut by around 6%. See [Scalability Benchmarks](https://docs.mulesoft.com/runtime-fabric/latest/rtf-scale) for guidance on large clusters. - You can now use any Helm release name. However, `runtime-fabric` is still the default and recommended name. - You can now override the creation of a new `ServiceAccount` for every Mule application deployment, by setting the `DISABLE_PER_APP_SA` variable in the `env` section of the Kubernetes template. See [Disable Per Application Service Account](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd#disable-service-account). - The following dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.7.0` - coreAction: `mulesoft/rtf-core-actions:1.0.127` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.215` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.114` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.17` - appInit: `mulesoft/rtf-app-init:1.0.192` - persistenceGateway: `mulesoft/rtf-object-store:1.0.216` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.193` - rtfDaemon: `mulesoft/rtf-daemon:2.0.80` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:2.1.48` - The following dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.7.0` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.127` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.215` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.17` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.192` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.216` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.193` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.80` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.26` ### Fixed Issues
Issue Resolution ID

An invalid ephemeralStorageLimit defined in the KubernetesTemplate now results in a more readable error message.

W-16441132

Increased nginx proxy defaults for worker processes/connections to allow more concurrent connections to take place. This can potentially improve throughput when a lot of configuration resolver requests are received at once.

W-13304547

Added explicit rate limit configuration to nginx proxy to avoid Denial-of-Service attacks.

W-15781441
### [](#kubernetes-supported-versions)Kubernetes Supported Versions This version of Runtime Fabric supports the following Kubernetes versions: - 1.26.x - 1.27.x - 1.28.x - 1.29.x ## [](#2-6-52)2.6.52 **June 7, 2024** ### What’s New - Starting `rtfctl` version 1.0.70, if you use an rtf-agent version higher than 2.6.52, the `rtfctl` backup bundle doesn’t contain the Mule app deployments. The deployments are synced from the Runtime Manager UI at the time of restoration. Refer to [Backing up and restoring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-backup-restore). - By default, console logging is disabled if your Mule app logs to at least one external source (such as Anypoint Monitoring or Splunk via a third-party Log4j appender). Using Anypoint Monitoring (with console logging disabled) can improve your Mule app’s performance by up to 40%. If you must use console logging, you can enable it by setting the `ENABLE_CONSOLE_LOG` variable to `"true"` in the `env` section of the Kubernetes template. For more information, refer to [Enable Console Logging](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd#enable-console-logging). Unresolved include directive in modules/ROOT/pages/runtime-fabric/runtime-fabric-release-notes-2.x.x.adoc - include::runtime-fabric::partial$log-console-stdout.adoc\[\] - Review [Runtime Fabric Core Software Kubernetes Permissions](https://docs.mulesoft.com/runtime-fabric/latest/rtf-permissions) and [Mule App Deployments Kubernetes Permissions on Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/rtf-mule-app-permissions). - Starting Runtime Fabric agent version 2.6.52, monitoringSidecar (otel) version is bound to Mule runtime versions. Refer to [Mule Runtime Patch Update Release Notes for Mule Apps on Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes). - You can now deploy [`SNAPSHOT` version assets](https://docs.mulesoft.com/jp/exchange/to-publish-assets-maven#asset-lifecycle-state) to Runtime Fabric using the Mule Maven plugin without the need to increment your application’s version number manually. Refer to [Exchange Snapshot Assets](https://docs.mulesoft.com/runtime-fabric/latest/deploy-maven-4.x#exchange-snapshot-assets). Using Exchange snapshot assets in Anypoint Exchange during the development and testing phase, you can avoid incrementing your application’s version number for small changes. After your snapshot asset is overwritten in Anypoint Exchange, you can redeploy your `SNAPSHOT` version application to Runtime Fabric via the Mule Maven plugin to deploy the latest changes. - The following dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.6.52` - coreAction: `mulesoft/rtf-core-actions:1.0.118` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.208` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.114` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.15` - appInit: `mulesoft/rtf-app-init:1.0.179` - persistenceGateway: `mulesoft/rtf-object-store:1.0.205` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.183` - rtfDaemon: `mulesoft/rtf-daemon:2.0.48` - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:1.2.152` - The following dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.52` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.118` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.208` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.15` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.179` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.205` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.183` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.48` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.26` ### [](#kubernetes-supported-versions-2)Kubernetes Supported Versions This version of Runtime Fabric supports the following Kubernetes versions: - 1.26.x - 1.27.x - 1.28.x - 1.29.x ## [](#2-6-42)2.6.42 **May 13, 2024** ### What’s New - You can now [enable trace data](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#enable-trace-data) collection for Mule apps. You can use the [Telemetry Exporter](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter) in Anypoint Monitoring to export traces to third-party observability and analytics apps. - Refer to [Mule Runtime Patch Update Release Notes for Mule Apps on Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes) going forward to check the latest Otel sidecar version. ### Fixed Issues
Issue Resolution ID

You can now view logs forwarded from Mule apps that have not restarted after upgrading to version 2.6.23 on non-Openshift self-managed platforms.

W-15666862

Mule apps no longer start with a warning regarding an invalid group ID.

W-15362056
- The following dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.6.42` - coreAction: `mulesoft/rtf-core-actions:1.0.116` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.205` - monitoringSidecar (otel): `mulesoft/dias-anypoint-monitoring-sidecar:2.0.45` - monitoringSidecar (daemonset): `mulesoft/dias-anypoint-monitoring-sidecar:1.3.114` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.11` - appInit: `mulesoft/rtf-app-init:1.0.176` - persistenceGateway: `mulesoft/rtf-object-store:1.0.201` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.180` - rtfDaemon: `mulesoft/rtf-daemon:2.0.44` - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.148` - The following dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.42` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.116` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.205` - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:2.0.45` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.11` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.176` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.201` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.180` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.44` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.25` ### [](#kubernetes-supported-versions-3)Kubernetes Supported Versions This version of Runtime Fabric supports the following Kubernetes versions: - 1.25.x - 1.26.x - 1.27.x - 1.28.x ## [](#2-6-23)2.6.23 **April 17, 2024** ### What’s New - If you have a self-hosted container registry, you may encounter a no image found error during app restart or redeployment. Due to this, any redeployment or deployments using version 2.6.22 after May 15 will use the new 2.0.45 sidecar version. As a workaround, pull the image 2.0.45 to the local registry. Refer to [Synchronize Runtime Fabric Core Software Dependencies and Images to Your Local Registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry#synch-rtf). ### Fixed Issues
Issue Resolution ID

For Openshift clusters, upgrade to Runtime Fabric version 2.6.23 to avoid noisy warning log messages in Runtime Fabric agent.

W-15532104
Known Issue Workaround ID

Unable to view logs forwarded from Mule apps that have not restarted after upgrading to version 2.6.23 on non-Openshift self-managed platforms.

Do not upgrade to version 2.6.23 and wait for the next version release. If you already upgraded, refer to the Anypoint Monitoring Log Forwarder Pods (daemon set) stop sending logs after upgrade to RTF agent version 2.6.22 or 2.6.23 knowledge base article for potential workarounds.

W-15666862
- The following dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.6.23` - coreAction: `mulesoft/rtf-core-actions:1.0.113` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.181` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:2.0.45` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.11` - appInit: `mulesoft/rtf-app-init:1.0.170` - persistenceGateway: `mulesoft/rtf-object-store:1.0.197` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.174` - rtfDaemon: `mulesoft/rtf-daemon:2.0.34` - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.100` - The following dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.23` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.113` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.181` - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:2.0.45` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.11` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.170` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.197` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.174` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.34` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.20` ### [](#kubernetes-supported-versions-4)Kubernetes Supported Versions This version of Runtime Fabric supports the following Kubernetes versions: - 1.25.x - 1.26.x - 1.27.x - 1.28.x ## [](#2-6-22)2.6.22 **April 11, 2024** ### What’s New - Starting Runtime Fabric version 2.6.22, you must configure new [Anypoint Monitoring endpoints](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#enable-anypoint-monitoring) for Runtime Fabric instance setup. - Starting version 2.6.22 Anypoint Monitoring sidecar is only compatible with http-proxy instead of the monitoring SOCKS5 proxy. If you run Mule apps in a controlled environments, ensure you [configure an HTTP proxy for services in Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-proxy-self#configure-an-http-proxy-for-services-in-runtime-fabric). Note that if you have a self-hosted container registry, you may encounter no image found error during app restart or redeployment. Due to this, any redeployment or deployments using version 2.6.22 after May 15 will use the new 2.0.45 sidecar version. As a workaround pull the image 2.0.45 to the local registry. Refer to [Synchronize Runtime Fabric Core Software Dependencies and Images to Your Local Registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry#synch-rtf). - Runtime Fabric now supports Horizontal Pod Autoscaling (HPA), refer to [Configuring Horizontal Pod Autoscaling (HPA) for Runtime Fabric Deployments](https://docs.mulesoft.com/runtime-fabric/latest/configure-horizontal-autoscaling) To upgrade an already created Runtime Fabric in an old K8s cluster version, you must first upgrade the agent to the new version, and then upgrade the cluster to use K8s. ### Fixed Issues
Issue Resolution ID

The cluster health status box in the Runtime Manager user interface no longer displays more nodes than were actually live.

W-14374870

Persistence Gateway no more fails with the error `reached maximum value of sequence "items_id_seq".

W-14811114

Added timezone to the Mule-license expiry info which is displayed on the Runtime Fabric user interface.

W-15177341
Known Issue Workaround ID

Unable to view logs forwarded from Mule apps that have not restarted after upgrading to version 2.6.22 on non-Openshift self-managed platforms.

Do not upgrade to version 2.6.22 and wait for the next version release. If you already upgraded, refer to the Anypoint Monitoring Log Forwarder Pods (daemon set) stop sending logs after upgrade to RTF agent version 2.6.22 or 2.6.23 knowledge base article for potential workarounds.

W-15666862
- The following dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.6.22` - coreAction: `mulesoft/rtf-core-actions:1.0.113` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.181` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:2.0.34` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.11` - appInit: `mulesoft/rtf-app-init:1.0.170` - persistenceGateway: `mulesoft/rtf-object-store:1.0.197` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.174` - rtfDaemon: `mulesoft/rtf-daemon:2.0.34` - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.100` - The following dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.22` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.113` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.181` - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:2.0.34` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.11` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.170` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.197` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.174` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.34` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.20` ### [](#kubernetes-supported-versions-5)Kubernetes Supported Versions This version of Runtime Fabric supports the following Kubernetes versions: - 1.25.x - 1.26.x - 1.27.x - 1.28.x ## [](#2-6-2)2.6.2 **March 5, 2024** ### What’s New - Runtime Fabric now supports Kubernetes 1.28. To upgrade an already created Runtime Fabric in an old K8s cluster version, you must first upgrade the agent to the new version, and then upgrade the cluster to use K8s v1.28. - MuleSoft now consolidates telemetry transport through a single sidecar per application replica. Review the resource allocation changes of Anypoint Monitoring agent that enables you to [monitor Mule apps deployed on Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#resource-and-permission-requirements-for-anypoint-monitoring-agent). - Review how to [synchronize image dependencies to your local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry) using `helm` or `rtfctl`. - Mule app deployments via the API with AM log forwarding `enabled` must have the Mule app deployment request `disableAmLogForwarding` set to `false`. - Review [customize Mule app Kubernetes resources](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd) on how to customize `automountServiceAccountToken` using CRD. - Review [downgrading Runtime Fabric Versions](https://docs.mulesoft.com/runtime-fabric/latest/downgrade-runtime-fabric). - Starting with this version, there are changes to the registry endpoint validation. Previously, an empty authorization header was sent during the probe on the registry endpoint for network checking. Now, Runtime Fabric sends no authorization header at all. If you are using a private registry, you might find that your network checks fail on the registry endpoint. ### Fixed Issues
Issue Resolution ID

For OpenShift clusters, Mule app’s ingress now uses openshift-default as the ingressClassName when using rtf-openshift in the ingress template.

W-13840301

Runtime Fabric OpenShift route template now supports the default TLS-certificate.

W-14937104

Runtime Fabric BYOK ingress template with multi-hosts now propagates correctly the protocol to the Runtime Manager UI.

W-14687741

Runtime Fabric daemon no longer ignores Anypoint Monitoring proxy.

W-14785603

Runtime Fabric object store service now returns a structured response for errors.

W-14446241

This release includes security fixes.

W-14309677

Cluster IP service now works correctly with Runtime Fabrics installed in a custom namespace.

W-14828458
- The following dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:2.6.2` - coreAction: `mulesoft/rtf-core-actions:1.0.104` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.176` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:1.3.111` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.7` - appInit: `mulesoft/rtf-app-init:1.0.160` - persistenceGateway: `mulesoft/rtf-object-store:1.0.185` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.167` - rtfDaemon: `mulesoft/rtf-daemon:2.0.29` - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.100` - The following dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:2.6.2` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.104` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.176` - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:1.3.111` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.7` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.3.111` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.185` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.167` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.29` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.20` ### [](#kubernetes-supported-versions-6)Kubernetes Supported Versions This version of Runtime Fabric supports the following Kubernetes versions: - 1.25.x - 1.26.x - 1.27.x - 1.28.x ## [](#2-5-0)2.5.0 **November 15, 2023** ### What’s New - Runtime Fabric now supports Kubernetes 1.27. To upgrade an already created Runtime Fabric in an old K8s cluster version, you must first upgrade the agent to the new version, and then upgrade the cluster to use K8s v1.27. ### Fixed Issues
Issue Resolution ID

Runtime Fabric namespaced Kubernetes templates in authorized mode and handling of node affinity rules now work correctly.

W-14182584

The ingress template now uses OCP default certificate for TLS Runtime Manager details to show the URL as plain HTTP instead of HTTPS.

W-13750378

Runtime Fabric agent now recovers correctly after a network outage if proxy is enabled.

W-14308672

The ingress resource watcher no longer publishes the ingress template every hour resulting in the CPU spike at the ingress controller.

W-13588326
### Known Issues
Known Issue Workaround ID

For Runtime Fabric instances on OpenShift cluster, which are using authorized namespaces, additional ClusterRolebinding is required. If not provided InvalidSemverException occurs during the deployment of a Mule app.

Refer to 2.5.0 - Ingress creation failure (InvalidSemverException) for details.

W-14668801
- The following dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:v2.5.0` - coreAction: `mulesoft/rtf-core-actions:v1.0.88` - clusterOps: `mulesoft/rtf-cluster-ops:v2.0.141` - monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar:v1.3.90` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:v1.3.22` - appInit: `mulesoft/rtf-app-init:v1.0.141` - persistenceGateway: `mulesoft/rtf-object-store:v1.0.158` - resourceFetcher: `mulesoft/rtf-resource-fetcher:v1.0.151` - rtfDaemon: `mulesoft/rtf-daemon:v2.0.10` - Base Image Nginx: `mulesoft/base-image-nginx-1.21.6:v1.2.87` - The following dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) Operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:v2.5.0` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:v1.0.88` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:v2.0.141` - Ubi monitoringSidecar: `mulesoft/dias-anypoint-monitoring-sidecar-ubi:v1.3.90` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:v1.3.22` - Ubi appInit: `mulesoft/rtf-app-init-ubi:v1.0.141` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:v1.0.158` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.151` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:v2.0.10` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:v0.3.17` ### [](#kubernetes-supported-versions-7)Kubernetes Supported Versions This version of Runtime Fabric supports the following Kubernetes versions: - 1.24.x - 1.25.x - 1.26.x - 1.27.x ## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Fabric 3.x.x Release Notes These are the release notes for Runtime Fabric v3.x.x. For the complete Runtime Fabric documentation, refer to [Anypoint Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/). To maintain compatibility and system integrity, customers using a private registry must synchronize the `rtf-mule-actions` image, refer to [Runtime Fabric Mule Action Image Synchronization](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-rtf-mule-action) for details. This table shows Kubernetes supported versions:
K8s version Upstream K8s GA Runtime Fabric Support GA Runtime Fabric Support EOL

1.36

April 2026

October 2026

Runtime Fabric support of 1.40

1.35

December 2025

July 2026

Runtime Fabric support of 1.39

1.34

August 2025

March 2026

Runtime Fabric support of 1.38

1.33

April 2025

October 2025

Runtime Fabric support of 1.37

1.32

December 2024

June 2025

Runtime Fabric support of 1.36

1.31

August 2024

January 2025

Runtime Fabric support of 1.35

1.30

May 2024

October 2024

Runtime Fabric support of 1.34

1.29

December 2023

June 2024

October 2025

1.28

August 2023

March 2024

June 2025

1.27

April 2023

November 2023

January 2025

1.26

December 2022

June 2023

May 2024

1.25

August 2022

May 2023

June 2024

1.24

May 2022

January 2023

February 2024
## [](#3-0-35601)3.0.35601 **October 8, 2026** ### What’s New - Anypoint Runtime Fabric now supports Kubernetes 1.36. - Anypoint Controller now deletes Mule applications more reliably. Deletion finishes only after Anypoint Platform confirms the application is removed. Deleting an older application no longer affects a newer one with the same name, and applications that never reach the control plane no longer stay stuck. For more information, refer to [Deploying and Managing Mule Applications Using Anypoint Controller for Kubernetes](https://docs.mulesoft.com/runtime-fabric/latest/deploy-mule-app-anypoint-controller). - Third-party dependencies are upgraded to address reported security vulnerabilities. - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:3.0.35601` - coreAction: `mulesoft/rtf-core-actions:1.0.9000` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.16100` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.8500` - appInit: `mulesoft/rtf-app-init:1.0.10900` - persistenceGateway: `mulesoft/rtf-object-store:1.0.12500` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.16900` - rtfDaemon: `mulesoft/rtf-daemon:2.0.27100` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.2.400` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:3.0.35601` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.9000` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.16100` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.8500` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.10900` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.12500` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.16900` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.27100` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:1.0.4900` ### Fixed Issues
Issue Resolution ID

duplicate entries for key [name="rtf-pull-secret"] errors no longer occur when starting Managed Omni in Runtime Fabric.

W-24445888
### [](#supported-kubernetes-versions)Supported Kubernetes Versions Runtime Fabric version 3.0.35601 supports these Kubernetes versions: - 1.36.x - 1.35.x - 1.34.x - 1.33.x ## [](#3-0-34501)3.0.34501 **October 7, 2026** ### What’s New - Anypoint Runtime Fabric now supports Kubernetes 1.36. - Anypoint Controller now deletes Mule applications more reliably. Deletion finishes only after Anypoint Platform confirms the application is removed. Deleting an older application no longer affects a newer one with the same name, and applications that never reach the control plane no longer stay stuck. For more information, refer to [Deploying and Managing Mule Applications Using Anypoint Controller for Kubernetes](https://docs.mulesoft.com/runtime-fabric/latest/deploy-mule-app-anypoint-controller). - Third-party dependencies are upgraded to address reported security vulnerabilities. - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:3.0.34501` - coreAction: `mulesoft/rtf-core-actions:1.0.9000` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.16100` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.8500` - appInit: `mulesoft/rtf-app-init:1.0.10900` - persistenceGateway: `mulesoft/rtf-object-store:1.0.12500` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.16900` - rtfDaemon: `mulesoft/rtf-daemon:2.0.27100` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.2.400` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:3.0.34501` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.9000` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.16100` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.8500` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.10900` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.12500` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.16900` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.27100` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:1.0.4900` ### Fixed Issues
Issue Resolution ID

Upgrading the rtf-agent chart with --reuse-values from an older release no longer fails when optional values are missing.

W-23665449

Third-party dependencies are updated to address reported security vulnerabilities.

W-24103552
### [](#supported-kubernetes-versions-2)Supported Kubernetes Versions Runtime Fabric version 3.0.34501 supports these Kubernetes versions: - 1.36.x - 1.35.x - 1.34.x - 1.33.x ## [](#3-0-277)3.0.277 **July 30, 2026** ### What’s New - Anypoint Runtime Fabric now supports Kubernetes 1.35. - The new `rtfctl agent-truststore` command group lets you inspect, back up, merge, and update the certificate authority (CA) certificates that the Runtime Fabric agent uses for mutually authenticated TLS (mTLS) connections to the Anypoint Platform control plane. This simplifies CA rotation without requiring additional tooling. For more information, refer to [Managing the Agent Truststore with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/manage-agent-truststore-rtfctl) and [Runtime Fabric Command-Line Tool (rtfctl) Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes). - You can now deploy agent networks to Runtime Fabric. Your Runtime Fabric agent deployment must be on version 3.0.277 or later. - Starting date October 3, 2025 Runtime Fabric agent supports Oracle Kubernetes Engine (OKE). - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:3.0.277` - coreAction: `mulesoft/rtf-core-actions:1.0.219` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.384` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.92` - appInit: `mulesoft/rtf-app-init:1.0.274` - persistenceGateway: `mulesoft/rtf-object-store:1.0.312` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.333` - rtfDaemon: `mulesoft/rtf-daemon:2.0.400` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.2.7` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:3.0.274` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.219` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.384` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.92` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.274` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.312` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.333` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.400` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.57` ### Fixed Issues
Issue Resolution ID

Improved identity-bootstrap reliability: failed bootstrap Job pods are now retained for diagnosis, and the retry limit and deadline were increased.

W-22775237

FIPS-compliant deployments now apply the correct binary flags consistently.

W-22822294

Third-party dependencies are upgraded to address security vulnerabilities.

W-22781322, W-23027089

The Runtime Fabric agent now starts correctly on FIPS-enabled clusters.

W-22011308

Upgrades no longer fail when stale bring-your-own-CA (BYOCA) PEM certificates conflict with automatic certificate issuance. This condition is now logged as a warning instead.

W-22692378
### [](#supported-kubernetes-versions-3)Supported Kubernetes Versions Runtime Fabric version 3.x.x supports these Kubernetes versions: - 1.35.x - 1.34.x - 1.33.x - 1.32.x ## [](#3-0-102)3.0.102 **May 28, 2026** ### What’s New - The Anypoint Runtime Manager UI now supports handlebar-style placeholders (such as `{{ .ApplicationName }}`) when configuring public endpoints for HTTP route templates. Runtime Manager replaces placeholders that you enter in host or path fields with deployment-specific values at deployment time. The Runtime Manager UI now treats legacy ingress-style strings such as `app-name` as literal strings, not as placeholders, for HTTP route templates. For details, refer to [HTTP Route-Template Custom-Resource Placeholders](https://docs.mulesoft.com/runtime-fabric/latest/configure-ingress-http-resource#http-route-template-custom-resource-placeholders). - Supported keys for pod.env field in the Anypoint Controller When deploying Mule applications using the Anypoint Controller CR (MuleApplication), the pod.env field in the CR spec supports only these keys: - `ENABLE_CONSOLE_LOG`: Enables console logging for the application container. - `ENABLE_READINESS_PROBE_ON_HTTP_GET`: Enables the native Kubernetes HTTP GET readiness probe (requires Mule runtime patches from November 7, 2025 or later). - `DISABLE_PER_APP_SA`: Disables the per-application service account, causing the Mule application to use the default namespace service account. For further details, refer to [Kubernetes Customization](https://docs.mulesoft.com/runtime-fabric/latest/deploy-mule-app-anypoint-controller#kubernetes-customization). - Starting date June 30, 2026 [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/runtime-fabric/latest/view-app-diagnostics) is supported. - Starting date October 3, 2025 Runtime Fabric agent supports Oracle Kubernetes Engine (OKE). - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:3.0.102` - coreAction: `mulesoft/rtf-core-actions:1.0.200` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.299` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.52` - appInit: `mulesoft/rtf-app-init:1.0.245` - persistenceGateway: `mulesoft/rtf-object-store:1.0.264` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.259` - rtfDaemon: `mulesoft/rtf-daemon:2.0.284` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.1.44` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:3.0.102` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.200` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.299` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.52` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.245` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.264` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.259` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.284` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.48` ### Fixed Issues
Issue Resolution ID

Updated third-party dependencies to address security vulnerabilities. These changes include no API or behavioral modifications and are part of the standard security maintenance cadence included in every Runtime Fabric release.

W-22371736

Timing-related failures no longer prevent applications created by Anypoint Controller from being deleted.

W-22200626

FIPS-compliant deployments now apply the correct binary flags consistently.

W-22265793, W-22348521

rtfctl installations now create the am-monitoring-certificate secret automatically.

W-21562809
### [](#supported-kubernetes-versions-4)Supported Kubernetes Versions Runtime Fabric version 3.0.102 supports these Kubernetes versions: - 1.34.x - 1.33.x - 1.32.x - 1.31.x ## [](#3-0-43)3.0.43 **March 11, 2026** ### What’s New - Runtime Fabric agent version 3.0.43 now supports Kubernetes (K8s) 1.34. - Starting date June 30, 2026 [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/runtime-fabric/latest/view-app-diagnostics) is supported. - Starting date October 3, 2025 Runtime Fabric agent supports Oracle Kubernetes Engine (OKE). - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:3.0.43` - coreAction: `mulesoft/rtf-core-actions:1.0.178` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.273` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.41` - appInit: `mulesoft/rtf-app-init:1.0.225` - persistenceGateway: `mulesoft/rtf-object-store:1.0.246` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.233` - rtfDaemon: `mulesoft/rtf-daemon:2.0.246` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.1.42` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:3.0.43` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.178` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.273` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.41` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.225` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.246` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.233` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.246` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.30` ### Fixed Issues
Issue Resolution ID

This release includes security fixes.

W-20921271

Runtime Fabric application initialization pods no longer fail with Error: checksum validation failed following a Runtime Fabric upgrade. The application init container now correctly detects corrupt or outdated cache artifacts and requests a new version from the upstream.

New or updated deployments automatically receive this fix with the latest Runtime Fabric version. Redeploy existing applications to use the updated init container image and resolve any persistent checksum errors.

W-20383477
### [](#supported-kubernetes-versions-5)Supported Kubernetes Versions Runtime Fabric version 3.0.43 supports these Kubernetes versions: - 1.34.x - 1.33.x - 1.32.x - 1.31.x ## [](#3-0-1)3.0.1 **December 8, 2025** ### What’s New - Runtime Fabric agent version 3.0.1 now supports Anypoint Controller for Kubernetes. This operator enables you to deploy and manage Mule applications on Runtime Fabric using GitOps workflows and Custom Resources (CR). For details, refer to [Deploying and Managing Mule Applications Using Anypoint Controller for Kubernetes](https://docs.mulesoft.com/runtime-fabric/latest/deploy-mule-app-anypoint-controller). - Runtime Fabric agent version 3.0.1 now supports Mule app restart. You can restart applications to resolve runtime issues such as memory leaks or unresponsive services without redeploying. All restart activities are tracked in the Access Management audit log. For details, refer to [Restarting Mule Applications on Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/restart-applications). - Runtime Fabric agent version 3.0.1 removes support for the legacy DaemonSet-based log forwarding method. Application logs are now forwarded exclusively through sidecar containers deployed alongside each application replica, providing better isolation and improved resource management. For details, refer to [Log Forwarding in Runtime Fabric 3.0.1](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#log-forwarding-in-runtime-fabric-3-0-0). - When using Runtime Fabric 3.0.1 or later, the HTTP GET readiness probe configuration (which defaults to false) requires your applications to run on Mule runtime engine patches from [November 7, 2025](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#november-7-2025), or later. If this feature is enabled for applications on older patches, they may fail to become ready or restart correctly. If you can’t upgrade your runtimes immediately, make sure the feature remains disabled. For details, refer to [Readiness Probe](https://docs.mulesoft.com/runtime-fabric/latest/customize-kubernetes-crd#enable-readiness-probe). - Starting date June 30, 2026 [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/runtime-fabric/latest/view-app-diagnostics) is supported. - Starting date October 3, 2025 Runtime Fabric agent supports Oracle Kubernetes Engine (OKE). - These dependencies are updated for [installing and managing Runtime Fabric with a local registry](https://docs.mulesoft.com/runtime-fabric/latest/configure-local-registry): - agent version: `mulesoft/rtf-agent:3.0.1` - coreAction: `mulesoft/rtf-core-actions:1.0.177` - clusterOps: `mulesoft/rtf-cluster-ops:2.0.266` - muleClusterIpService: `mulesoft/rtf-mule-clusterip-service:1.4.39` - appInit: `mulesoft/rtf-app-init:1.0.222` - persistenceGateway: `mulesoft/rtf-object-store:1.0.242` - resourceFetcher: `mulesoft/rtf-resource-fetcher:1.0.228` - rtfDaemon: `mulesoft/rtf-daemon:2.0.218` - Base Image Nginx: `mulesoft/supply-chain-nginx-base-image:3.1.40` - These dependencies are updated for [installing Runtime Fabric as a Kubernetes (K8s) operator](https://docs.mulesoft.com/runtime-fabric/latest/install-openshift): - Ubi agent version: `mulesoft/rtf-agent-ubi:3.0.1` - Ubi coreAction: `mulesoft/rtf-core-actions-ubi:1.0.177` - Ubi clusterOps: `mulesoft/rtf-cluster-ops-ubi:2.0.266` - Ubi muleClusterIpService: `mulesoft/rtf-mule-clusterip-service-ubi:1.4.39` - Ubi appInit: `mulesoft/rtf-app-init-ubi:1.0.222` - Ubi persistenceGateway: `mulesoft/rtf-object-store-ubi:1.0.242` - Ubi resourceFetcher: `mulesoft/rtf-resource-fetcher-ubi:1.0.228` - Ubi rtfDaemon: `mulesoft/rtf-daemon-ubi:2.0.218` - Ubi Base Nginx: `mulesoft/rtf-ubi-base-nginx:0.3.30` ### Fixed Issues
Issue Resolution ID

This release includes security fixes.

W-20141521

Applying a trust anchor (certificate) for a local, self-signed registry now works correctly on Runtime Fabric, ensuring the Runtime Fabric agent can establish trust.

W-16483594

Deploying updated applications using the Mule Maven Plugin 4.6.0 with a -SNAPSHOT version to Runtime Fabric now correctly deploys the latest asset.

W-20077300

Excessive process accumulation in readiness probes no longer occurs, ensuring more stable application startup.

W-19853421
### [](#supported-kubernetes-versions-6)Supported Kubernetes Versions Runtime Fabric version 3.0.1 supports these Kubernetes versions: - 1.33.x - 1.32.x - 1.31.x - 1.30.x ## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Fabric Command-Line Tool (rtfctl) Appliance Release Notes The following release notes are for Runtime Fabric Command Line Tool (`rtfctl`) appliance version: The Runtime Fabric CLI is the installation and management utility tool for your Runtime Fabric running on Kubernetes. You must manually replace the existing rtfctl binary if the version is not an appliance version currently. ## [](#0-6-0-6-release-gravity)0.6.0-6.release-gravity **October 4, 2023** ### What’s New - The `rtfctl report` command now includes the Anypoint Monitoring data of Mule deployments with the option `--include-mule-monitoring-data`. ## [](#0-6-0-2-release-gravity)0.6.0-2.release-gravity **August 4, 2023** ### Fixed Issues
Issue Resolution ID

The rftctl report command now includes correctly all namespaces in the report.

W-13797014

The rftctl status command no longer fails.

W-13726105
## [](#0-5-2-4-release-gravity)0.5.2-4.release-gravity **July 17, 2023** ### Fixed Issues
Issue Resolution ID

The rftctl restore command now works correctly for clusters.

W-13180067

The rftctl status command now works correctly for clusters.

W-13184287
## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Fabric Command-Line Tool (rtfctl) BYOK Release Notes The following release notes are for Runtime Fabric Command Line Tool (`rtfctl`) BYOK (Bring your own Kubernetes) version: The Runtime Fabric CLI is the installation and management utility tool for your Runtime Fabric running on Kubernetes. To download and install `rtfctl`, refer to [Install the Runtime Fabric Command Line Tool](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl). ## [](#1-0-150)1.0.150 **July 30, 2026** ### What’s New - `rtfctl` 1.0.150 introduces a new `rtfctl agent-truststore` command group. Inspect, back up, merge, and update the certificate authority (CA) certificates that the Runtime Fabric agent uses for mutually authenticated TLS (mTLS) connections to the Anypoint Platform control plane. This simplifies CA rotation, such as during a CA compromise or planned infrastructure change, without requiring additional tooling. For more information, refer to [Managing the Agent Truststore with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/manage-agent-truststore-rtfctl) and [Agent Truststore Commands](https://docs.mulesoft.com/runtime-fabric/latest/manage-agent-truststore-rtfctl#commands). ## [](#1-0-118)1.0.118 **March 11, 2026** ### Fixed Issues
Issue Resolution ID

rtfctl apply and rtfctl delete commands failed to manage secure properties if the property names contained certain suffixes or were malformed (for example, names containing literal strings like --value). The rtfctl utility is now updated with improved command-line argument parsing to correctly identify and process properties regardless of their name structure, ensuring that updates and deletions execute successfully

W-20497173
## [](#1-0-113)1.0.113 **December 8, 2025** ### What’s New - Anypoint Runtime Fabric Command-Line Tool (rtfctl) now supports the backup and restore of the Mule Application Custom Resource Definition (CRD).

Mule Application Custom Resources (CRs) aren’t supported for backup and restore. You must plan your recovery strategy using your source control repository as the single source of truth for all application configurations. After a Runtime Fabric cluster restore, you must re-apply your Mule Application CRs from your repository.
## [](#1-0-107)1.0.107 **September 03, 2025** ### What’s New - The `--core-software-only` flag in the rtfctl `restore` command enables you to restore only the core Runtime Fabric software components without triggering Mule app synchronization from the control plane. For details, refer to the [restore](https://docs.mulesoft.com/runtime-fabric/latest/rtfctl-reference#restore) command. ### Fixed Issues
Issue Resolution ID

The --core-software-only flag is now available in the rtfctl restore command.

W-19087426
## [](#1-0-98)1.0.98 **July 31, 2025** ### Fixed Issues
Issue Resolution ID

The clarity of ctl messages for rtctl validate and restore commands is now enhanced.

W-18181576, W-18109029

The validation prompt before restore in the case namespace no longer matches the backup.

W-12227576

This release includes security fixes.

W-18493468
## [](#1-0-92)1.0.92 **March 25, 2025** ### Fixed Issues
Issue Resolution ID

rtfctl commands no longer fail by missing Custom Resource Definitions (CRDs).

W-18024871
## [](#1-0-89)1.0.89 **March 10, 2025** ### What’s New - Anypoint Runtime Fabric Command-Line Tool now supports backup and restore of HTTP Route-Template CRD and CR. ### Fixed Issues
Issue Resolution ID

The --cluster-ops image flag taken from the local registry that is used to install the Runtime Fabric agent is now correctly configured.

W-16224293

rtfctl backup for OpenShift fabrics now considers the secrets required for the ingress resources.

W-17283597

The value for crds.install during helm migration is no longer explicitly set to false .

W-16452863

Informational output from Anypoint CLI now goes through stdout as in older versions.

W-16701108

Validation of the Anypoint user and bearer tokens is now run before initiating the backup phase in the rtfctl migrate flow.

W-16596517
## [](#1-0-79)1.0.79 **August 15, 2024** ### Fixed Issues
Issue Resolution ID

The rtfctl validate command no longer fails with a container unready error message when running jobs.

W-15895512
## [](#1-0-70)1.0.70 **June 7, 2024** ### What’s New - Starting with `rtfctl` version 1.0.70, if you use an rtf-agent version higher and equal to 2.6.52, the `rtfctl` backup bundle doesn’t contain the Mule app deployments. The deployments are synched from the Runtime Manager UI at the time of restoration. Refer to [Backing up and restoring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-backup-restore). - The new `rtfctl renew-expired-client-cert` command renews an expired client certificate using a pre-downloaded package. Refer to [Commands for Configuring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl#configure-rtfctl). - The `rtfctl report` command has a new flag, `--release-name`, that specifies the name of the helm release to support installations using custom release names. Refer to [Report](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl#report) command documentation. ### Fixed Issues
Issue Resolution ID

The rtfctl report command now creates unique temporary directories for each process, eliminating conflicts from shared directory usage. Additionally, the command avoids overwriting existing reports unless you specify the --overwrite flag. For two concurrent reports to work, they need to have different report file names, for example:

./rtfctl report --debug --file report1.tgz --namespace rtf-test
./rtfctl report --file report2.tgz --namespace rtf-test

W-15618561
## [](#1-0-55)1.0.55 **May 13, 2024** ### What’s New - The `rtfctl report` command collects data on a best-effort basis. The command generates the report even if sub-tasks fails. ### Fixed Issues
Issue Resolution ID

The rtfctl report command collects data on a best-effort basis. The command generates the report even if sub-tasks fails.

W-15696698
## [](#1-0-47)1.0.47 **April 12, 2024** ### What’s New - The `rtfctl report` command is updated for OTel sidecar. ## [](#1-0-44)1.0.44 **March 7, 2024** ### What’s New - The `rtfctl report` command now outputs an additional JSON formatted file for resources in agent versions v2.6.0 and above. - The `rtfctl report`, `backup`, and `restore` commands now extends the support to `kubernetestemplate` resources used to customize your app deployments. ### Fixed Issues
Issue Resolution ID

The rtfctl test command now fails sooner when there are terminal errors and does not require you to wait until the operation times out.

W-14992372

For Helm based agent installations, rtfctl apply mule-license command now detects and provides a Helm command for you to execute.

W-14278334
## [](#1-0-29)1.0.29 **November 14, 2023** ### What’s New - Review new [RTFCTL Kubernetes permissions](https://docs.mulesoft.com/runtime-fabric/latest/rtfctl-permissions) documentation. - Review new [Auditing rtfctl Operations](https://docs.mulesoft.com/runtime-fabric/latest/install-rtfctl#auditing) documentation. ## [](#1-0-20)1.0.20 **September 25, 2023** ### What’s New - The `rtfctl report` command now includes the Anypoint monitoring data of Mule deployments with the option `--include-mule-monitoring-data`. - The `rtfctl validate` command now supports `--image-pull-registry` and `--image-pull-secret` flags for validating against a local registry. ### Fixed Issues
Issue Resolution ID

The apply proxy command no longer returns an invalid warning message.

W-13032322

The restore operation now restores custom resources correctly.

W-13974770
## [](#1-0-12)1.0.12 **August 4, 2023** ### What’s New - Runtime Fabric now supports `rtfctl backup` and `rtfctl restore` commands for OpenShift clusters, refer to [Backing up and Restoring Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-backup-restore) documentation. - You can now migrate to helm native Runtime Fabrics from `rtfctl`, refer to the [Migrating to Helm Managed Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/migrate-helm) documentation. ### Fixed Issues
Issue Resolution ID

The rftctl backup and rtfctl restore commands now work correctly with custom resources.

W-13285192

Applying an HTTP proxy setting configuration to the app namespace no longer applies the proxy setting in the Runtime Fabric namespace.

W-12981038
## [](#0-4-22)0.4.22 **May 9, 2023** ### What’s New - The `rtfctl report` command now generates a fast compression file archive by using the new flag `use-fast-compression`. - The `rtfctl report` command now executes tasks in parallel worker pools by using the new `workers` flag. - The `rtfctl report` command now lets you choose which application namespaces to report using `app-namespaces` flag. ### Fixed Issues
Issue Resolution ID

When running the rtfctl uninstall command, the system namespace now waits for deletion of all relevant namespaces.

W-13100550

Runtime Fabric now uses the correct reference to cluster-ops during installation.

W-13074624

Runtime Fabric now unblocks CPC deployments correctly.

W-13097851

Reported security vulnerabilities are fixed.

W-12692341

Runtime Fabric now exposes an endpoint that takes version as input and responds with a pre-signed URL to download the given version.

W-13075535
## [](#0-4-1)0.4.1 **April 11, 2023** ### What’s New - Runtime Fabric now supports multiple instances on a single cluster. Refer to the [Installing Multiple Instances of Runtime Fabric on a Single Cluster](https://docs.mulesoft.com/runtime-fabric/latest/install-multiple-instances) documentation. ### Fixed Issues
Issue Resolution ID

An issue with a transport layer check no longer occurs when an application firewall blocks AMQP traffic while allowing HTTP/Websockets. Now the test attempts to validate the accessibility of the transport layer endpoint by sending actual AMQP frames over Websockets.

W-11958442

The rtfctl test outbound-network now works correctly for appliance-based clusters.

W-12499930

Backups of multiple instances created with rtfctl backup command can now be restored.

W-12742772
## [](#0-3-198)0.3.198 **January 23, 2023** ### Fixed Issues
Issue Resolution ID

The backup and restore commands now work correctly with persistence gateway resources.

W-11987155

The report command no longer reports non-RTF related namespaces.

W-12197726

The package command no longer fails when used with the -heap-dump flag.

W-11235954
### Known Issues
Known Issue Workaround ID

rtfctl restore command fails with segmentation fault.

Upgrade to the latest rtfctl version.

W-11987155
## [](#0-3-191)0.3.191 **December 15, 2022** ### Fixed Issues
Issue Resolution ID

Fixed security vulnerabilities.

W-12049033
## [](#0-3-179)0.3.179 **November 17, 2022** ### Fixed Issues
Issue Resolution ID

This release improves help messages on the command line.

W-11955726
## [](#0-3-175)0.3.175 **November 8, 2022** ### Fixed Issues
Issue Resolution ID

This release improves message formatting.

W-11174874, W-11942966

The rtfctl backup command now supports concurrent user execution and deletes the tmp/backup directory when the backup completes.

W-11063729

Clusters in the EU control plane are properly connected to the Anypoint Platform control plane after upgrading.

W-11227117
## [](#0-3-168)0.3.168 **May 24, 2022** ### What’s New - This release improves the example of how to use the `renew-expired-client-cert` command. - The `package` command now requires a mandatory argument for the path to the directory where the file will be created. ### Fixed Issues
Description Issue

The apply system-configuration command no longer fails because of a permission issue.

W-10993223

The package command no longer fails with an incorrect directory path error on Windows.

W-10810849
## [](#0-3-160)0.3.160 **April 5, 2022** ### Fixed Issues
Description Issue

This release includes improvements to support multiple authentication providers.

SE-24124

rtfctl now allows a custom pull-secret-name for local registries.

N/A

This release improves rtfctl documentation examples.

W-10647420
## [](#0-3-157)0.3.157 **February 22, 2022** ### What’s New - To support local registries in Runtime Fabric on Self-Managed Kubernetes version 1.12.0 and later, the `rtfctl` utility now includes the `get registry-credentials` command. Additionally, the `rtfctl install` command now includes the following flags: - `--image-pull-registry` - `--image-pull-secret` ## [](#0-3-145)0.3.145 **November 1, 2021** ### What’s New - You can now run the `rtfctl test outbound-network` command on all nodes or on a specific node. ### Fixed Issues
Description Issue

The rtfctl test outbound-network command allows network checks on all nodes or on specific nodes per the node selector.

SE-22084
## [](#0-3-139)0.3.139 **October 12, 2021** ### What’s New - The `rtfctl report` command now captures any previous container logs in a separate file. - The `rtfctl backup` and `rtfctl restore` commands are now compatible with Kubernetes 1.20. ### Fixed Issues
Description Issue

The rtfctl utility now reads both NO_PROXY and no_proxy settings from the environment.

SE-22108

The rtfctl proxy command throws an error if the RTF namespace is not present when the command applies proxy settings.

RTF-2933
## [](#0-3-135)0.3.135 **August 12, 2021** ### What’s New - The `rtfctl apply ingress-configmap` command is deprecated. If you attempt to apply an ingress ConfigMap with `rtfctl` against Runtime Fabric 1.10 or later, Runtime Fabric rejects the request. - The latest version of `rtfctl` includes backup and restore support for ingress resource templates. Use `rtfctl report` to see details about the ingress resource templates you applied. ### Fixed Issues
Issue Number

The rtfctl apply secure-property command now allows = for single-line values.

SE-22118

The rtfctl report no longer fails due to old pull secret references on old Runtime Fabric clusters.

SE-21254
## [](#jun-24-2021-0-3-128)Jun 24, 2021 (0.3.128) This release includes the following enhancements and bug fixes: - Added: The `rtfctl apply secure-property` command now handles special characters in a value. - Fixed: The `rtfctl get secure-properties` command no longer fails when retrieving values that have a '\\n' character. - Fixed: The `rtfctl report` command now captures all container logs. ## [](#apr-22-2021-0-3-122)Apr 22, 2021 (0.3.122) This release includes the following enhancements and bug-fixes: - Added: Improvement to the `rtfctl report` command to include information about persistent gateway deployment. - Added: Enhancement to the `rtfctl backup` and `rtfctl restore` commands to handle persistent gateway configuration and deployment. - Fixed: Issue where `rtfctl uninstall` may fail on gravity clusters. - Fixed: Issue where the state file for binary upgrade check was not created in the user’s home directory. ## [](#mar-18-2021-0-3-103)Mar 18, 2021 (0.3.103) This release includes the following major enhancement(s): - Added: The `rtfctl report` command includes runtime fabric helm history information. - Added: Enhancements to the `rtfctl status` command to fetch information from inside the runtime fabric cluster (Self-Managed Kubernetes only). - Added: Outbound Network tests now include both legacy and new Anypoint Monitoring endpoint(s). ## [](#feb-10-2021-0-3-102)Feb 10, 2021 (0.3.102) This release includes the following major enhancement(s): - Added: Improvements to capture logs from previous container restarts in the debug report. - Added: Enhancement to backup and restore any gravity custom resources created for smtp and log-forwarder. - Fixed: Issue where `rtfctl restore` command would throw an error while restoring on the same Self-Managed Kubernetes cluster where the backup was taken. ## [](#dec-16-2020-0-3-94)Dec 16, 2020 (0.3.94) This release includes the following major enhancement(s): - Added: `rtfctl status dns-check` command to test DNS health (Self-Managed Kubernetes only). - Added: `rtfctl delete secure-properties` command to remove secure properties. - Fixed: `rtfctl validate` command shows overall validation status message (Self-Managed Kubernetes only). - Fixed: `rtfctl` commands `help` and `version` now works without having Kubernetes context. ## [](#nov-23-2020-0-3-87)Nov 23, 2020 (0.3.87) This release includes the following major enhancement(s): - Added: `rtfctl validate` command to validate the Kubernetes environment prior to installing Runtime Fabric (Self-Managed Kubernetes only). - Added: `rtfctl apply ingress-configmap` command to apply ingress configuration on Runtime Fabric (Self-Managed Kubernetes only). - Added: `rtfctl uninstall` command to uninstall Runtime Fabric. - Fixed: bug fixes and improvements. ## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Fabric Install Scripts Release Notes These are the release notes for the Runtime Fabric install scripts (`rtf-install-scripts`). You use the install scripts to provision a new Runtime Fabric on VMs/Bare Metal. ## [](#20230621-7ebe87c)20230621-7ebe87c **July 17, 2023** ### What’s New - The Runtime Fabric install script is updated to use the new `rtfctl` appliance binary. ### What’s New
Issue Resolution Issue

Subnets creation no longer fail if VPC CIDR (Virtual Private Clouds Classless Inter-Domain Routing) block has a prefix higher than 16.

W-10631575
## [](#20220811-0e8a332)20220811-0e8a332 **August 29, 2022** ### What’s New - This release adds the `ClusterName` tag to identify a cluster by its name. ### What’s New
Description Issue

The install scripts now automatically installs the net-tools package if it’s absent when installing on machines running Ubuntu 20.04.

W-11588493
## [](#20220310-0094759)20220310-0094759 **March 31, 2022** ### What’s New - During installation, you can now set an optional variable, `RTF_PRIVATE_INTERFACE`, to allow private IP addresses to be discovered from the network interface. ## [](#20220112-f8b0e44)20220112-f8b0e44 **January 19, 2022** ### What’s New - Added support for RHEL/CentOS 8.4 using installer version 1.1.1636064094-8b70d2d or later. ### Fixed Issues
Description Issue

The install script now supports spaces in tags.

SE-22511

The install script no longer attempts to add nodes if the cluster is not in an "active" state.

SE-22610

The install script no longer runs lvextend on non-logical volumes.

SE-22553
### Known Issues
Known Issue Workaround ID

For RHEL/CentOS 8.4, the install scripts disable the Network Mangager Cloud Setup (nm-cloud-setup) service.

If you’re upgrading your node operating systems from RHEL/CentOS 8.3 to 8.4, you must disable the nm-cloud-setup service before upgrading or installing Runtime Fabric with the latest install scripts. To disable nm-cloud-setup, run the following on each node:

cat > disable_nm_cloud.sh << 'EOF'
#!/bin/bash

function perform_os_specific_operations() {
    set +e
    if [[ "$ID_LIKE" == *"fedora"* ]] && [[ $VERSION_ID == 8.4 ]]; then
        echo "Disabling nm-cloud-setup service on RHEL 8.4"
        systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
        systemctl stop nm-cloud-setup.service nm-cloud-setup.timer
        echo "Removing ip rule prio 30400 on RHEL 8.4"
        ip rule del prio 30400
        if [[ -d "/etc/systemd/system/nm-cloud-setup.service.d" ]]; then
            rm -rf /etc/systemd/system/nm-cloud-setup.service.d
        fi
        echo "Restarting NetworkManager.service on RHEL 8.4"
        systemctl restart NetworkManager.service
    fi
    set -e
}
source /etc/os-release
perform_os_specific_operations
EOF

sudo chmod +x ./disable_nm_cloud.sh
sudo ./disable_nm_cloud.sh

N/A
## [](#20210826-d2dad4d)20210826-d2dad4d **August 27, 2021** ### Fixed Issues
Description Issue

Appliance upgrades now install iptables on all nodes if that functionality is not already installed.

SE-21995

Appliance upgrades disable firewalld and add the corresponding iptables rules across all nodes.

SE-22018
## [](#20210709-b48dec6)20210709-b48dec6 **July 14, 2021** ### What’s New - Added support for Ubuntu 18.04 using installer version 1.1.1625094374-7058b20 or later. - Removed support for firewalld and added support for iptables on RHEL/Centos 8.x . - Removed the Terraform variable `internal_interface` from the AWS install scripts. This release includes the following fixed issues:
Issue Description

SE-21706

Install scripts for Azure no longer fail with an "`opt` does not exist" error on RHEL and CentOS 8.x versions.
## [](#20210430-318d1a9)20210430-318d1a9 **April 30, 2021** ### What’s New - Added the Terraform variable `block-aws-metadata-svc`, which allows or blocks access to the AWS Instance Metadata Service (IMDS). - The Terraform variable `disable_selinux` now has a default value of `true`. ## [](#20210129-4a7f3c6)20210129-4a7f3c6 **February 1, 2021** ### What’s New - Added the Terraform variable `disable_selinux`, which disables SELinux on the host operating system during installation. ## [](#20200720-3c88ca5)20200720-3c88ca5 **July 22, 2020** ### What’s New - Runtime Fabric now supports RHEL only with Logical Volume Manager (LVM) on Azure Bare Metal. Non-LVM instances of RHEL on Azure Bare Metal are not supported. ## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Fabric Installer Release Notes These are the release notes for the installer package bundle for Runtime Fabric on VMs / Bare Metal. In addition to these release notes, see the [Anypoint Runtime Fabric release notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes) and the complete [Anypoint Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/) documentation. ## [](#2-0-1683838781-797f198)2.0.1683838781-797f198 **May 12, 2023** ### What’s New - The container logging format changed from JSON (docker-specific) to CRI (cri-o, containerd, etc.). ### Fixed Issues
Issue Resolution ID

The new Runtime Fabric Installer version 2.0.1683838781-797f198 enables you to log in correctly into Ops center.

W-13191265
## [](#2-0-1682628878-0253858)2.0.1682628878-0253858 **May 5, 2023** ### What’s New - This release contains bug fixes only. ### Fixed Issues
Issue Resolution ID

Latest installer is based on gravity 5.5.77, which switches from Docker to containerd as the container manager.

W-12353489

Ops center now displays medium or long term data for memory related metrics.

W-12549948

Performance issues no longer occur when operating appliance clusters with high utilization or many apps after they are upgraded.

W-11781677, W-12353489
### Known Issues
Known Issue Workaround ID

When you log into the Ops Center using the https://<OpsCenter-URL-here>:32009/web/login URL, the landing page shows an Invalid Version: 2.0.1682628878-0253858 internal error.

To access Ops Center, use the https://<OpsCenter-URL-here>:32009/web/site/<cluster-name>/monitor URL.

W-13191265

Log format changed starting with Runtime Fabric installer version 2.0.1682628878-0253858. The log output scrambles information and affects multiline logging.

  1. Edit the DaemonSet by running the command kubectl edit ds -n rtf external-log-forwarder.

  2. In the DaemonSet configuration window, locate the section under spec > template > spec > containers that corresponds to the external-log-forwarder container.

  3. Find the line that contains the Image field.

  4. Modify the value of the Image field to use the desired version rtf-pkg-fluentbit v1.2.113 that contains the fix for the multiline logging issue, for example, rtf-runtime-registry.kprod.msap.io/mulesoft/rtf-pkg-fluentbit:v1.2.113.

  5. Save the changes.

  6. Close the text editor.

W-13504485
## [](#2-0-1668062290-074bc49)2.0.1668062290-074bc49 **December 14, 2022** ### What’s New - This release contains bug fixes only. ### Fixed Issues
Issue Resolution ID

Runtime Fabric appliance upgrades no longer fail due to a long running etcd backup command.

W-11585892

This release upgrades Helm3 to v3.10.0.

W-11820302

The Telegraf monitoring app no longer issues false alerts for node uptime.

W-11740287
### Known Issues
Known Issue Workaround ID

Starting with release 2.0.1661808686-2ff0e92, you might experience performance issues operating appliance clusters with high utilization or many apps, after they are upgraded. Usually during node maintenance. After the nodes are brought back into operation, they might show signs of increased CPU usage and fail to start deployed applications.

W-11781677
## [](#2-0-1661808686-2ff0e92)2.0.1661808686-2ff0e92 **August 29, 2022** ### What’s New - This release includes fixes for security vulnerabilities. ### Fixed Issues
Issue Resolution ID

This release includes fixes for security vulnerabilities.

W-11585892
### Known Issues
Known Issue Workaround ID

Starting with release 2.0.1661808686-2ff0e92, you might experience performance issues operating appliance clusters with high utilization or many apps, after they are upgraded. Usually during node maintenance. After the nodes are brought back into operation, they might show signs of increased CPU usage and fail to start deployed applications.

W-11781677
## [](#1-1-1660253001-ab8f5e5)1.1.1660253001-ab8f5e5 **August 12, 2022** ### What’s New - This release adds support for Ubuntu 20.04 and RHEL 8.6 ### Fixed Issues
Description Issue

When starting an upgrade, the installer now performs an InfluxDB size check.

W-10606099

The etcd.tick Kapacitor alert no longer re-appears if you delete it.

W-10760515

The systemd Kapacitor task is now works as expected.

W-10833331

The sudo gravity leave command now removes a node as documented.

W-10946440

The Ops Center Individual Node Memory Usage graph now shows the correct legend.

W-10961514

The RTF readiness probe no longer fails with a cgroup.procs: invalid argument error.

W-10647444
### Known Issues
Description Issue

Runtime Fabric might issue false alerts about uptime.

W-10819071
## [](#1-1-1636064094-8b70d2d)1.1.1636064094-8b70d2d **January 19, 2022** ### What’s New - Added support for RHEL/CentOS 8.4 using install scripts version 20220112-f8b0e44 or later. ### Known Issues
Known Issue Workaround ID

For RHEL/CentOS 8.4, the install scripts disable the Network Mangager Cloud Setup (nm-cloud-setup) service.

If you’re upgrading your node operating systems from RHEL/CentOS 8.3 to 8.4, you must disable the nm-cloud-setup service before upgrading or installing Runtime Fabric with the latest install scripts. To disable nm-cloud-setup, run the following on each node:

cat > disable_nm_cloud.sh << 'EOF'
#!/bin/bash

function perform_os_specific_operations() {
    set +e
    if [[ "$ID_LIKE" == *"fedora"* ]] && [[ $VERSION_ID == 8.4 ]]; then
        echo "Disabling nm-cloud-setup service on RHEL 8.4"
        systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
        systemctl stop nm-cloud-setup.service nm-cloud-setup.timer
        echo "Removing ip rule prio 30400 on RHEL 8.4"
        ip rule del prio 30400
        if [[ -d "/etc/systemd/system/nm-cloud-setup.service.d" ]]; then
            rm -rf /etc/systemd/system/nm-cloud-setup.service.d
        fi
        echo "Restarting NetworkManager.service on RHEL 8.4"
        systemctl restart NetworkManager.service
    fi
    set -e
}
source /etc/os-release
perform_os_specific_operations
EOF

sudo chmod +x ./disable_nm_cloud.sh
sudo ./disable_nm_cloud.sh

N/A
## [](#1-1-1625094374-7058b20)1.1.1625094374-7058b20 **July 15, 2021** ### [](#whats-new-7)What’s New - Ubuntu 18.04 support using the install scripts version 20210709-b48dec6 or later. - The InfluxDB pod no longer crashes due to `localhost` resolving to an invalid IP address. ## [](#1-1-1619717580-73a133d)1.1.1619717580-73a133d **May 3, 2021** This release includes the following fix and enhancement: - Added: Support for RHEL/CentOS 8.3 - Fixed: Issue that caused the Ops Center UI metrics retention page to sometimes fail to load after reboot. ## [](#1-1-1613157109-f27c821)1.1.1613157109-f27c821 **Mar 4, 2021** This release includes the following fix and enhancement: - Added: Improvement to inject Google’s metadata server’s host record in the Planet container when using Google Cloud Platform. - Fixed: Issue with stale alerts being shown in the output of the `gravity status` utility. ## [](#1-1-1606942735-3f99c37-dec-15-2020)1.1.1606942735-3f99c37 - Dec 15, 2020 This release includes the following fixes and enhancements: - Added: RHEL/CentOS 7.9 support. - Added: Improvements to the resiliency of the dns-app component during upgrades. - Fixed: Custom taints were not tolerated by logging and monitoring services. - Fixed: Upgrades with etcd may break watches in internal services. ## [](#1-1-1603929599-47b2888-nov-10-2020)1.1.160392​9599-47b2888 - Nov 10, 2020 This release includes the following fixes and enhancements: - Added: RHEL/CentOS 8.1 and 8.2 support. - Added: Improvements in reducing etcd load when querying system services during heavy usage. - Added: Improvements in debug reporting to include cluster configuration information. - Added: Checks to prevent cluster from entering an inconsistent state when executing a rollback. - Fixed: Issue with cluster status reporting healthy when few nodes are reported offline. - Updated: TLS config to use secure ciphers and TLSv1.2 for Kubernetes internal components. ## [](#1-1-1599670979-d08f56e-sep-18-2020)1.1.1599670979-d08f56e - Sep 18, 2020 This release includes the following fixes and enhancements: - Added: Validation for proxy settings configured in the appliance. - Added: Pre-upgrade validation to mitigate overlay network failures. - Added: Improvements in appliance status to display detailed alerts and warnings. - Added: Improvements that increase the resiliency with the appliance upgrade process. - Fixed: Upgrades with etcd were not applied on worker nodes in some cases. - Fixed: Issue with cluster network which could in some cases cause node-to-node communication to hang indefinitely. - Fixed: Issue with log forwarding causing increased CPU utilization. ## [](#1-1-1597283557-2e1fc6a-aug-19-2020)1.1.1597283557-2e1fc6a - Aug 19, 2020 This release includes the following fixes and enhancements: - Added: Patch for CVE-2020-8558. - Added: Automated pre-upgrade checks for validating cluster state before applying the upgrade. - Added: Ability to update auth servers in teleport node config. - Added: Resiliency improvements to the upgrade agent. - Added: RHEL/CentOS 8.0 support. - Added: Logging improvements and an additional command line option for following the plan progress during upgrade. - Fixed: InfluxDB continuous queries resulting in max series limit exhaustion. - Fixed: Cleaning up residual kube-dns resources when upgrading from older versions. - Fixed: Issue with etcd shutdown phase during upgrade. ## [](#1-1-1593137954-fe02b2c-july-9-2020)1.1.1593137954-fe02b2c - July 9, 2020 This release includes the following fixes and enhancements: - Added: Patch for CVE-2020-13379. - Added: Pre-upgrade checks to ensure that the previous upgrade operation was not in progress. - Fixed: Kubernetes API server entering failed state during failover. - Fixed: Ops Center Monitoring tab displaying `Dashboard not found` error. - Fixed: Disk space check executing for volumes that don’t have disk requirements specified. - Fixed: Upgrade failure when manually resumed on a node with an incomplete state. ## [](#1-1-1591285019-e135da0-june-4-2020)1.1.1591285019-e135da0 - June 4, 2020 This release includes the following fixes and enhancements: - Added: CentOS 7.8 support. - Added: Stability and performance improvements. - Fixed: Issue with restarting etcd due to large request size during an upgrade. - Fixed: Issue with RPC agent credentials not being rotated during an upgrade. - Fixed: Issue with pulling images on slow network environments. - Fixed: Security issues. ## [](#1-1-1588363273-4110aff-may-4-2020)1.1.1588363273-4110aff - May 4, 2020 This release includes the following fixes and enhancements: - Added: RHEL 7.8 support. - Fixed: Issue with Influxdb consuming high CPU and Memory in some cases over time. - Fixed: Issue with Teleport nodes failing to join after expand operation. - Fixed: Issue with missed etcd events caused by a forced reboot. - Updated: kube-apiserver and kubelet to use Mozilla modern compatibility ciphers. ## [](#1-1-1586472858-1609d2f-april-15-2020)1.1.1586472858-1609d2f - April 15, 2020 This release includes the following fixes and enhancements: - Added: Cleanup mechanism within the appliance to prevent leaking cgroups. - Added: Detection for issues with the overlay network. - Added: Improvements with appliance upgrades and detection to prevent unsupported upgrade paths. - Fixed: Support for copying lengthy commands from the web terminal in the Ops Center. ## [](#1-1-1583954392-3121bcd-march-12-2020)1.1.1583954392-3121bcd - March 12, 2020 This release includes the following fixes and enhancements: - Fixed: Mitigated issues with Buster-based Docker containers in some environments by rolling back to stretch. - Fixed: Fixed issue with Teleport nodes failing to upload recorded sessions after upgrading from older clusters. ## [](#1-1-1581474166-1f657f1-february-14-2020)1.1.1581474166-1f657f1 - February 14, 2020 This release includes the following fixes and enhancements: - Fixed: Spurious error message from telegraf-node pod. - Fixed: Connectivity between nodes degraded after being restarted. - Fixed: A 500 internal error when accessing monitoring and authentication settings using Ops Center. - Added: Ability to configure a non-authenticating SMTP server to be used for sending alerts. ## [](#1-1-1572976203-3ad8a93-november-5-2019)1.1.1572976203-3ad8a93 - November 5, 2019 This release includes the following fixes and enhancements: - Fixed: In some cases, HTTP and Anypoint Monitoring proxy configuration was removed and had to be re-applied. - Fixed: Unused `docker0` interface, which had the potential to cause conflicts with existing services in the `172.17.0.0` range, was removed. ## [](#1-1-1571866618-0015ffd-october-28-2019)1.1.1571866618-0015ffd - October 28, 2019 This release includes the following fixes and enhancements: - Fixed: Upgrade fails when a directory which does not exist is listed in `/etc/mtab` - Added: Patch for CVE-2019-11253. - Updated: Kubernetes upgraded to `v1.13.12`. ### [](#known-issues-6)Known Issues - Applying this upgrade will cause the Ops Center to stop reporting heap memory usage for applications. Redeploying your applications will resolve this issue. ## [](#1-1-1568899906-253f482-september-19-2019)1.1.1568899906-253f482 - September 19, 2019 This release includes the following fixes and enhancements: - Fixed: Connectivity between nodes was degraded in some cases after upgrading etcd. - Added: Patch for CVE-2019-11251. - Updated: Kubernetes upgraded to `v1.13.11`. ## [](#1-1-1568409420-d6dff88-september-13-2019)1.1.1568409420-d6dff88 - September 13, 2019 This release includes the following fixes and enhancements: - Added: Support for more than 3 controller nodes. ## [](#1-1-1567702318-6a0bb3f-september-5-2019)1.1.1567702318-6a0bb3f - September 5, 2019 This release includes the following fixes and enhancements: - Added: Patch for CVE-2019-9512, CVE-2019-9514, CVE-2019-9512, CVE-2019-9514. - Added: Support for RHEL/CentOS 7.7 - Updated: Kubernetes upgraded to `v1.13.10`. ## [](#1-1-1565299957-f751c25-august-16-2019)1.1.1565299957-f751c25 - August 16, 2019 This release includes the following fixes and enhancements: - Added: Patch for CVE-2019-11247 and CVE-2019-11249. - Updated: Kubernetes upgraded to `v1.13.9`. - Fixed: Permission error when managing monitoring resources via `gravity resource` command. ## [](#1-1-1561762676-fed2e0b-july-1-2019)1.1.1561762676-fed2e0b - July 1, 2019 This release includes the following fixes and enhancements: - Added: Support for running backup and restore jobs through OpsCenter. - Added: Patches to address security vulnerabilities. - Updated: Kubernetes upgraded to `v1.14.2`. - Updated: `kubedns` replaced with `coredns` to align with upstream Kubernetes defaults. - Updated: The _patch_ component versioning scheme is now based on the build time. (Correction: Kubernetes was upgraded to `v1.13.6`) ## [](#1-0-7-may-28-2019)1.0.7 - May 28, 2019 This release includes the following fixes and enhancements: - Fixed: Docker proxy to support authorization credentials with special characters. ## [](#1-0-6-april-10-2019)1.0.6 - April 10, 2019 This release includes the following fixes and enhancements: - Added: Patch for CVE-2019-1002100 and CVE-2019-1002101. ## [](#1-0-5-february-22-2019)1.0.5 - February 22, 2019 This release includes the following fixes and enhancements: - Added: Script to allow updating HTTP proxy configuration. (See `scripts/` directory) ## [](#1-0-4-february-13-2019)1.0.4 - February 13, 2019 This release includes the following fixes and enhancements: - Added: Security patch to address CVE-2019-5736 ## [](#1-0-3-february-6-2019)1.0.3 - February 6, 2019 This release includes the following fixes and enhancements: - Added: Support for RHEL/CentOS 7.6 ## [](#1-0-2-january-17-2019)1.0.2 - January 17, 2019 This release includes the following fixes and enhancements: - Added: Patch for internal component used by Ops Center ## [](#1-0-1-december-13-2018)1.0.1 - December 13, 2018 This release includes the following fixes and enhancements: - Added: Security patch to address CVE-2018-1002105 - Added: Support for RedHatEnterpriseServer - Fixed: Mule 4 license handling ## [](#1-0-0-august-13-2018)1.0.0 - August 13, 2018 Initial release ## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Manager Private Cloud Edition September 2015 The Anypoint Runtime Manager Private Cloud Edition September 2015 release enables users to enhance their unified monitoring experience by easily integrating their on-premises Mule servers and API Gateways with third parties’ monitoring tools, such as Splunk & ELK, for monitoring, analytics and governance. ## [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ## [](#compatibility)Compatibility Agent plugins integrations is compatible with the following runtime versions: \* Runtime Manager Agent 1.2.0 and above \* Mule 3.6.x and above \* API GW 2.1.x for API Analytics ## [](#features-and-functionality)Features and Functionality ### [](#agent-plugins-integration-splunk-log)Agent Plugins Integration (Splunk & Log) Users will now have the ability to monitor their applications with an out-of-the box integration experience for monitoring tools such as Splunk & ELK. This enables the user to have a unified view of all applications, servers, etc. ### [](#api-gateway-integration-splunk-log)API Gateway Integration (Splunk & Log) Users now have the ability to integrate their API Gateway with Agent/ARM and pass API Metrics for analytics and governance. ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ### [](#resolved-issues)Resolved Issues - Bug fixes for error while deleting servers - Reconnection strategy for Agent - Usability improvements while creating server groups ## [](#known-issues)Known Issues No way to change buffering configuration for Splunk from the UI. ## [](#support)Support No change. # Anypoint Runtime Manager Release Notes This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager. ## [](#august-2021)August 2021 ### Fixed Issues

Issue

ID

Fixed a UI issue that caused the Use persistent object store checkbox to be deselected when applying changes.

SE-21862

Fixed a UI issue in which the Edit Application page for Anypoint Runtime Fabric applications was not loading properly on slow networks, causing fields to return to default values.

SE-21967
## [](#june-2021)June 2021 ### [](#whats-new)What’s New - When deploying new apps or redeploying existing apps to Anypoint Runtime Fabric, Runtime Manager now selects the latest date patch of the Mule runtime version, if applicable, by default. During the grace period, you can select earlier date patches until they are no longer available. If you select an earlier date patch, and make any subsequent changes to that application, you might be required to update it to a later date patch. For more information, see [Mule Runtime Patch Updates for Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/runtime-patch-updates). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Manager Release Notes (Archived)
The releases listed in this page refer to changes made to Runtime Manager in hybrid deployment scenarios, which enables you to deploy Mule applications on user-hosted servers, but continue to manage and monitor them through MuleSoft’s cloud based platform.
## [](#august-2021)August 2021 See [Runtime Manager August 2021 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-monthly-release-notes#august-2021). ## [](#june-2021)June 2021 See [Runtime Manager June 2021 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-monthly-release-notes#june-2021). ## [](#version-2-13-0-dec-9-2019)Version 2.13.0 - Dec 9, 2019 See [Runtime Manager v2.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.13.x-release-notes#2-13-0) ## [](#version-2-12-4-nov-9-2019)Version 2.12.4 - Nov 9, 2019 Internal release only. No customer-facing changes. ## [](#version-2-12-3-oct-5-2019)Version 2.12.3 - Oct 5, 2019 Internal release only. No customer-facing changes. ## [](#version-2-12-2-sep-21-2019)Version 2.12.2 - Sep 21, 2019 Internal release only. No customer-facing changes. ## [](#version-2-12-1-sep-7-2019)Version 2.12.1 - Sep 7, 2019 Internal release only. No customer-facing changes. ## [](#version-2-12-0-aug-24-2019)Version 2.12.0 - Aug 24, 2019 See [Runtime Manager v2.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.12.x-release-notes#2-12-0) ## [](#version-2-11-4-jun-27-2019)Version 2.11.4 - Jun 27, 2019 See [Runtime Manager v2.11.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.11.x-release-notes#2-11-4) ## [](#version-2-11-3-jun-15-2019)Version 2.11.3 - Jun 15, 2019 See [Runtime Manager v2.11.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.11.x-release-notes#2-11-3) ## [](#version-2-11-2-may-18-2019)Version 2.11.2 - May 18, 2019 See [Runtime Manager v2.11.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.11.x-release-notes#2-11-2) ## [](#version-2-11-1-may-18-2019)Version 2.11.1 - May 18, 2019 See [Runtime Manager v2.11.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.11.x-release-notes#2-11-1) ## [](#version-2-11-0-mar-23-2019)Version 2.11.0 - Mar 23, 2019 See [Runtime Manager v2.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.11.x-release-notes#2-11-0) ## [](#version-2-10-1-feb-16-2019)Version 2.10.1 - Feb 16, 2019 See [Runtime Manager v2.10.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.10.x-release-notes#2-10-1) ## [](#version-2-10-0-jan-26-2019)Version 2.10.0 - Jan 26, 2019 See [Runtime Manager v2.10.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.10.x-release-notes#2-10-0) ## [](#version-2-9-2-jan-12-2019)Version 2.9.2 - Jan 12, 2019 See [Runtime Manager v2.9.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.9.x-release-notes#2-9-2) ## [](#version-2-9-1-dec-15-2018)Version 2.9.1 - Dec 15, 2018 Internal release only. No customer-facing changes. ## [](#version-2-9-0-dec-8-2018)Version 2.9.0 - Dec 8, 2018 See [Runtime Manager v2.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.9.x-release-notes#2-9-0) ## [](#version-2-8-4-may-19-2018)Version 2.8.4 - May 19, 2018 See [Runtime Manager v2.8.r Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.8.x-release-notes#2-8-4) ## [](#version-2-8-3)Version 2.8.3 Internal release only. No customer-facing changes. ## [](#version-2-8-2-march-24-2018)Version 2.8.2 - March 24, 2018 See [Runtime Manager 2.8.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.8.x-release-notes#2-8-2) ## [](#version-2-8-1-february-22-2018)Version 2.8.1 - February 22, 2018 See [Runtime Manager v2.8.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.8.x-release-notes#2-8-1) ## [](#version-2-8-0-january-25-2018)Version 2.8.0 - January 25, 2018 See [Runtime Manager v2.8.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.8.x-release-notes#2-8-0) ## [](#version-2-7-0-january-13-2018)Version 2.7.0 - January 13, 2018 See [Runtime Manager v2.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.7.x-release-notes#2-7-0) ## [](#version-2-6-1-november-19-2017)Version 2.6.1 - November 19, 2017 See [Runtime Manager v2.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.6.x-release-notes#2-6-1) ## [](#version-2-6-0-october-20-2017)Version 2.6.0 - October 20, 2017 See [Runtime Manager 2.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.6.x-release-notes#2-6-0). ## [](#version-2-5-0-september-9-2017)Version 2.5.0 - September 9, 2017 See [Runtime Manager 2.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.5.x-release-notes#2-5-0). ## [](#version-2-4-3-august-26-2017)Version 2.4.3 - August 26, 2017 See [Runtime Manager 2.4.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.4.x-release-notes#2-4-3). ## [](#version-2-4-0-june-24-2017)Version 2.4.0 - June 24, 2017 - Enables Runtime Manager to display additional information about remote server. See [Runtime Manager 2.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.4.x-release-notes#2-4-0). ## [](#version-2-3-1-june-3-2017)Version 2.3.1 - June 3, 2017 - Enables restart and shutdown of servers in hybrid deployment scenarios. See [Runtime Manager 2.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.3.x-release-notes#2-3-1). ## [](#version-2-3-0-may-20-2017)Version 2.3.0 - May 20, 2017 This release introduces the following features: - Enhancements to features supported in hybrid installations. See [Runtime Manager 2.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.3.x-release-notes#2-3-0). ## [](#version-2-2-0-april-8-2017)Version 2.2.0 - April 8, 2017 This release introduces the following feature: - Flow Monitoring: Users now have the ability to monitor key metrics in each Mule flow over time. This will help to visualize the evolution of the application and compare their flows. See [Runtime Manager 2.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.2.x-release-notes#2-2-0). ## [](#version-2-1-0-march-11-2017)Version 2.1.0 - March 11, 2017 This release introduces the following capabilities: - Improved support for promotion of hybrid applications between environment from the UI - Capability to enable and disable insights at deployment time for hybrid applications - Capability to configure the log levels at deployment time for hybrid applications This release also includes significant backend improvements to boost performance and reduce response times. See the full [Runtime Manager 2.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.1.x-release-notes#2-1-0). ## [](#version-2-0-november-19-2016)Version 2.0 - November 19, 2016 This release contains the following new features: - [Insight](https://docs.mulesoft.com/jp/runtime-manager/insight) for Hybrid Users. - Flow Management - Monitoring V2.0 See the full [Runtime Manager 2.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-2.0.x-release-notes#2-0-0). ## [](#version-1-5-1-august-27-2016)Version 1.5.1 - August 27, 2016 This release includes a few minor enhancements. See the full [Runtime Manager 1.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-1.5.x-release-notes#1-5-1). ## [](#version-1-5-july-21-2016)Version 1.5 - July 21, 2016 This release includes the following new features: - [Dashboards](https://docs.mulesoft.com/jp/runtime-manager/monitoring-dashboards) for applications and servers on-premises, and new [alerts](https://docs.mulesoft.com/jp/runtime-manager/alerts-on-runtime-manager) linked to the metrics these display - [Insights](https://docs.mulesoft.com/jp/runtime-manager/insight) for applications deployed on-premises - Migration tool to automatically migrate deployments on – soon to be deprecated – Mule Management Console (MMC) to Runtime Manager See the full [Runtime Manager 1.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-1.5.x-release-notes#1-5-0). ## [](#version-1-4-1-may-6-2016)Version 1.4.1 - May 6, 2016 This release includes the following new features: - [Alerts](https://docs.mulesoft.com/jp/runtime-manager/alerts-on-runtime-manager) for applications and servers on-premises - Support for [static IP addresses](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-allowlists#static-ip-addresses) See the full [Runtime Manager 1.4.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-1.4.x-release-notes#1-4-1). ## [](#version-1-4-0-april-23-2016)Version 1.4.0 - April 23, 2016 This release includes the following new features: - [Audit Logging](https://docs.mulesoft.com/jp/access-management/audit-logging) for Runtime Manager Events - Name change on homepage, the console formerly known as CloudHub is now known as Runtime Manager.
The name CloudHub is from now on only used to reference the features of the Runtime Manager that involve deploying applications to cloud workers, VPC, and load balancing.
See the full [Runtime Manager 1.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-1.4.x-release-notes#1-4-0). ## [](#version-1-3-1)Version 1.3.1 This release includes the following new features: - Enhancements to the handler for [sending data to Splunk](https://docs.mulesoft.com/jp/runtime-manager/sending-data-from-arm-to-external-analytics-software) - JMX handler enhancements See the full [Runtime Manager 1.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/anypoint-runtime-manager-1.3.x-release-notes#1-3-1). ## [](#version-1-3-0)Version 1.3.0 This release includes the following new features: - Usability Enhancements for [Clustering](https://docs.mulesoft.com/jp/runtime-manager/managing-servers#create-a-cluster) - RDBMS support (Beta) See the full [Runtime Manager 1.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/anypoint-runtime-manager-1.3.x-release-notes#1-3-0). ## [](#version-1-2-0)Version 1.2.0 This release includes the following new features: - [Agent Plugins Integration](https://docs.mulesoft.com/jp/runtime-manager/sending-data-from-arm-to-external-analytics-software) for Splunk and generic Logs - API Gateway runtime Integration See the full [Runtime Manager 1.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-1.2.x-release-notes#1-2-0). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Runtime Manager Version 2.13.x Release Notes ## [](#2-13-0)2.13.0 December 9, 2019 This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.13.0. ### [](#new-features-and-enhancements)New Features and Enhancements There are no new features or enhancements in this release. ### [](#changes-in-this-release)Changes in This Release The flow metrics feature is deprecated and is no longer collecting data. ### [](#fixed-issues)Fixed Issues None ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes There are no compatibility notes in this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Security Release Notes Anypoint Security provides a layered approach to secure your application network. These layers work together to protect both the application network and its individual nodes by controlling access to APIs, enforcing policies, and proxying all inbound or outbound traffic to mitigate external threats. These capabilities are optimized for security, providing you with a dedicated endpoint to detect attacks and validate traffic without taxing your implementations. - [Secrets Manager](https://docs.mulesoft.com/jp/release-notes/anypoint-security/secrets-manager-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Security Release Notes Anypoint Security provides a layered approach to secure your application network. These layers work together to protect both the application network and its individual nodes by controlling access to APIs, enforcing policies, and proxying all inbound or outbound traffic to mitigate external threats. These capabilities are optimized for security, providing you with a dedicated endpoint to detect attacks and validate traffic without taxing your implementations. These release notes apply to Anypoint Security: - [Secrets Manager Release Notes](https://docs.mulesoft.com/jp/release-notes/anypoint-security/secrets-manager-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Studio 7.20.1 Release Notes Anypoint Studio is an Eclipse-based integration development environment for designing and testing Mule applications. ## [](#april-13-2024)April 13, 2024 ### [](#components-bundled-with-this-release)Components Bundled with This Release
Product Version

Mule runtime engine

4.8.12

DataWeave

2.8.0

MUnit

3.7.0

MUnit Studio Plugin

2.7.19

Mule Maven Plugin

4.8.0

Eclipse

4.31

Maven

3.9.6

Adoptium Eclipse Temurin OpenJDK

JDK 8 (8u432-b06)

JDK 17 (17.0.13+11)
- This version of Studio requires Java 17. - JDK 17 starts and runs Studio. - JDK 17 is the default JRE for running Mule projects and the Mule runtime instance used for tooling.
Studio 7.16 and later bundle a newer version of Apache Maven and Mule Maven Plugin. These versions aren’t backward compatible with Apache Maven 3.8 or earlier, or Mule Maven Plugin 3.8.7 or earlier. Use your own Maven if you need an earlier version.
## Fixed Issues
Issue Resolution ID

Anypoint Studio 7.20.1 now works as expected with Java 21 compatible connectors.

W-20003662
## Compatibility ### [](#mule-runtime-engine-compatibility)Mule Runtime Engine Compatibility Applications developed in Studio 7.20.1 are compatible with these Mule runtime engine versions:
Mule Runtime Engine Version Compatible

Mule runtime engine 4.8.x

Yes***

Mule runtime engine 4.7.x

Yes

Mule runtime engine 4.6.x

Yes

Mule runtime engine 4.5.x

Yes*

Mule runtime engine 4.4.x

Yes

Mule runtime engine 4.3.x

Yes**

Mule runtime engine 4.2.x

Yes*

Mule runtime engine 4.1.x

Yes*

Mule runtime engine 3.9.x

No**

Mule runtime engine 3.8.x

No*
\* This Mule runtime version reached [End of Life](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf). \*\* This Mule runtime version has entered [Extended Support](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf). \*\*\* Studio bundles this version of Mule runtime engine. ### [](#ui-compatibility-with-application-deployment-targets)UI Compatibility with Application Deployment Targets Studio 7.20.1 offers a graphical interface to deploy Mule 4.x applications to these application deployment targets:
Application Deployment Target Compatible

CloudHub

Yes

On-premises Mule runtime engine instances

Yes

Runtime Fabric

No

You can deploy to Runtime Fabric by exporting your application in Studio and deploying it separately.
### [](#compatibility-with-anypoint-platform-installation-options)Compatibility with Anypoint Platform Installation Options Studio 7.20.1 integrates with components of these platforms:
Anypoint Platform Installation Compatible

US Cloud

Yes

EU Cloud

Yes

See Configure Anypoint Studio to Use a Specific Control Plane Region.

MuleSoft Government Cloud

Yes

See Access MuleSoft Government Cloud from Anypoint Studio.

Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

Yes

Studio 7.20.1 can connect to Anypoint Platform PCE 3.1.x, 3.2.x, and 4.0.0.

See Configure Private Cloud Edition in Anypoint Studio.

Canada Cloud

Yes

See Configure Anypoint Studio to Use a Specific Control Plane Region.

Japan Cloud

Yes

See Configure Anypoint Studio to Use a Specific Control Plane Region.
### [](#hardware-requirements)Hardware Requirements - 8GB of memory Studio needs a minimum of 4GB of free RAM on a developer workstation. As applications become more complex, consider adding more RAM. - 2GHz CPU - 10GB free hard drive space ### [](#software-requirements)Software Requirements Studio is compatible with these operating systems and their standard configuration. Using Studio on configurations other than the supported operating systems can result in unexpected behaviors. - Operating Systems - macOS 12 through 14 - Windows 10, Windows 11 (64-bit)\* - RHEL 9\* - Ubuntu 18.04 or later LTS \*Windows 11 and RHEL support is based on the Eclipse support matrix. For more information, see [Eclipse target environments](https://eclipse.dev/eclipse/development/plans/eclipse_project_plan_4_28.xml).

Running real-time antivirus protection software on your operating system might have a negative impact on Anypoint Studio performance. Although this issue is prominent on Windows, it also occurs on Linux and macOS.

The steps to solve these performance issues vary depending on your antivirus software. A typical solution is to either allow or exclude the Anypoint Studio and Java executables, the Studio install and workspace filesystem locations, or some combination of both. See examples of solutions for Trellix Endpoint Security Threat Prevention, Windows Security, and Broadcom Endpoint Protection.
## [](#workspace-upgrade-requirements)Workspace Upgrade Requirements You can create and organize projects in workspaces with Studio. When you first open Studio, it automatically generates a default workspace to store your projects. Your Mule application projects aren’t fully compatible with workspaces in a different version of Studio. Projects created with Studio 6.x aren’t compatible with Studio 7.x because they’re Mule 3.x projects. See [Update Workspaces in Anypoint Studio](https://docs.mulesoft.com/studio/update-workspace) for more information. ## [](#see-also)See Also - [Anypoint Studio](https://docs.mulesoft.com/studio/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Anypoint Studio Troubleshooting](https://docs.mulesoft.com/studio/troubleshooting-studio) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Studio 7.29.0 Release Notes Anypoint Studio is an Eclipse-based integration development environment for designing and testing Mule applications. ## [](#october-20-2026)October 20, 2026 ## What’s New - Studio now supports Mule runtime engine 4.13.0, which includes new features and enhancements. For more information, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). ### [](#components-bundled-with-this-release)Components Bundled with This Release
Product Version

Mule runtime engine

4.13.0

DataWeave

2.13.0

MUnit

3.7.5

MUnit Studio Plugin

2.8.0

Mule Maven Plugin

4.10.3

Eclipse

4.40

Maven

3.9.15

Adoptium Eclipse Temurin OpenJDK

JDK 17 (17.0.13+11)
- This version of Studio requires Java 17. - JDK 25 starts and runs Studio. - JDK 17 is the default JRE for running Mule projects and the Mule runtime instance used for tooling.
Studio 7.16 and later bundle a newer version of Apache Maven and Mule Maven Plugin. It’s not backward compatible with Apache Maven 3.8 or earlier, or Mule Maven Plugin 3.8.7 or earlier. Use your own Maven if you need an earlier version.
A MuleSoft Government Cloud version of Anypoint Studio 7.29.0 is available from MuleSoft Downloads in the Salesforce Help Center. This version includes all the features and capabilities of Anypoint Studio 7.29.0, bundled with the Anypoint Runtime LTS version 4.9.0.
To access the Help Center, log in with your MuleSoft credentials. For more information, see [How to access MuleSoft Downloads](https://help.salesforce.com/s/articleView?id=005167229&type=1). ## Fixed Issues
Issue Resolution ID

Components that are commented out or disabled in Anypoint Code Builder now display correctly in the Studio canvas.

W-22708679

Connectors that use the interpreted-connectivity loader ID now load as expected without validation errors.

W-23971851

On macOS, you can now highlight and select multiple lines in XML and YAML files as expected.

W-20173653

Studio now automatically resolves inconsistencies between the minMuleVersion and javaSpecificationVersions values in a project’s mule-artifact.json file.

W-24192843
## Compatibility ### [](#mule-runtime-engine-compatibility)Mule Runtime Engine Compatibility Applications developed in Studio 7.29.0 are compatible with these Mule runtime engine versions:
Mule Runtime Engine Version Compatible

Mule runtime engine 4.13.x

Yes*

Mule runtime engine 4.12.x

Yes*

Mule runtime engine 4.11.x

Yes

Mule runtime engine 4.10.x

Yes

Mule runtime engine 4.9.x (LTS)

Yes

Mule runtime engine 4.6.x (LTS)

Yes
\* Studio bundles this version of Mule runtime engine. ### [](#ui-compatibility-with-application-deployment-targets)UI Compatibility with Application Deployment Targets Studio 7.29.0 offers a graphical interface to deploy Mule 4.x applications to these application deployment targets:
Application Deployment Target Compatible

CloudHub

Yes

On-premises Mule runtime engine instances

Yes

Runtime Fabric

No

You can deploy to Runtime Fabric by exporting your application in Studio and deploying it separately.
### [](#compatibility-with-anypoint-platform-installation-options)Compatibility with Anypoint Platform Installation Options Studio 7.29.0 integrates with components of these platforms:
Anypoint Platform Installation Compatible

US Cloud

Yes

EU Cloud

Yes

See Configure Anypoint Studio to Use a Specific Control Plane Region.

MuleSoft Government Cloud

Yes

See Access MuleSoft Government Cloud from Anypoint Studio.

Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

Yes

Studio 7.29.0 can connect to Anypoint Platform PCE 3.1.x, 3.2.x, and 4.1.0.

See Configure Private Cloud Edition in Anypoint Studio.

Canada Cloud

Yes

See Configure Anypoint Studio to Use a Specific Control Plane Region.

Japan Cloud

Yes

See Configure Anypoint Studio to Use a Specific Control Plane Region.

India Cloud

Yes

See Configure Anypoint Studio to Use a Specific Control Plane Region.
### [](#hardware-requirements)Hardware Requirements - 8GB of memory Studio needs a minimum of 4GB of free RAM on a developer workstation. As applications become more complex, consider adding more RAM. - 2GHz CPU - 10GB free hard drive space ### [](#software-requirements)Software Requirements Studio is compatible with these operating systems and their standard configuration. Using Studio on configurations other than the supported operating systems can result in unexpected behaviors. - Operating Systems - macOS 12 through 26 - Windows 10, Windows 11 (64-bit)\* - RHEL 9\* - Ubuntu 18.04 or later LTS \*Windows 11 and RHEL support is based on the Eclipse support matrix. For more information, see [Eclipse target environments](https://eclipse.dev/eclipse/development/plans/eclipse_project_plan_4_28.xml).

Running real-time antivirus protection software on your operating system might have a negative impact on Anypoint Studio performance. Although this issue is prominent on Windows, it also occurs on Linux and macOS.

The steps to solve these performance issues vary depending on your antivirus software. A typical solution is to either allow or exclude the Anypoint Studio and Java executables, the Studio install and workspace filesystem locations, or some combination of both. See examples of solutions for Trellix Endpoint Security Threat Prevention, Windows Security, and Broadcom Endpoint Protection.
## [](#workspace-upgrade-requirements)Workspace Upgrade Requirements You can create and organize projects in workspaces with Studio. When you first open Studio, it automatically generates a default workspace to store your projects. Your Mule application projects aren’t fully compatible with workspaces in a different version of Studio. For more information, see [Update Workspaces in Anypoint Studio](https://docs.mulesoft.com/studio/update-workspace). ## [](#see-also)See Also - [Anypoint Studio](https://docs.mulesoft.com/studio/) - [Salesforce Help](https://help.salesforce.com/s/) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Studio Release Notes These release notes are available for Studio: - [Anypoint Studio 7.29.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/studio/anypoint-studio-7.29.0-release-notes) - [Anypoint Studio 7.20.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/studio/anypoint-studio-7.20.1-with-4.8-runtime-release-notes) For previous versions of Studio 7.x and 6.x that reached [end of life](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf), see the [Anypoint Studio Release Notes Archive](https://archive.docs.mulesoft.com/release-notes/studio/studio-archive). ## [](#see-also)See Also - [Anypoint Studio Troubleshooting](https://docs.mulesoft.com/studio/troubleshooting-studio) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Visualizer Release Notes Anypoint Visualizer provides an interactive, graphical representation of your application network. The following pages contain new features and enhancements, known limitations, issues, and fixes for Anypoint Visualizer. - [Anypoint Visualizer Release Notes - 2022 and Later](https://docs.mulesoft.com/jp/release-notes/visualizer/anypoint-visualizer-release-notes-2022) - [Anypoint Visualizer Release Notes - 2020](https://docs.mulesoft.com/jp/release-notes/visualizer/anypoint-visualizer-release-notes-2020) - [Anypoint Visualizer Release Notes - 2019](https://docs.mulesoft.com/jp/release-notes/visualizer/anypoint-visualizer-release-notes-2019) - [Anypoint Visualizer Release Notes - 2018](https://docs.mulesoft.com/jp/release-notes/visualizer/anypoint-visualizer-release-notes-2018) See [Anypoint Visualizer](https://docs.mulesoft.com/visualizer/) documentation for more information. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Visualizer Release Notes - 2018 ## [](#december-15-2018)December 15, 2018 Version 2.0.0 ### [](#new-features-and-enhancements)New Features and Enhancements - Added support for applications running in standalone Mule runtime engines.
This capability is being released incrementally.
- Added the ability to select multiple nodes on the Visualizer canvas so you can apply layers and tags to all selected nodes at once. ### [](#known-issues)Known Issues - Standalone Mule runtime engines do not support HTTP calls using IP addresses instead of DNS names. - When an application deployed to a standalone Mule runtime engine calls a CloudHub application, an extra edge is displayed. This issue is fixed in the `-AM` runtime only. ## [](#november-27-2018)November 27, 2018 Version: 1.7.0 ### [](#new-features-and-enhancements-2)New Features and Enhancements - Side Panel - Added the ability to add tags to services using the UI or properties - Moved layer assignment from the **Details** panel to the **Customization** panel - Added filtering by tags - Added **Include related services** button to the **Services** filter ## [](#november-13-2018)November 13, 2018 Version: 1.6.0 ### [](#new-features-and-enhancements-3)New Features and Enhancements - Side Panel - Added filtering by environments and services (nodes) ### [](#fixed-issues)Fixed Issues - Dashboard button in side panel links to appropriate monitoring dashboard ## [](#november-1-2018)November 1, 2018 Version: 1.5.0 ### [](#new-features-and-enhancements-4)New Features and Enhancements - View - Added new text field to allow searching for nodes (services). - Added dimming functionality for when service is selected. Clicked node and its dependencies will show and other services will be grayed out. ## [](#october-3-2018)October 3, 2018 Version: 1.3.1 ### [](#new-features-and-enhancements-5)New Features and Enhancements - Side Panel - Added links to Anypoint Monitoring dashboard and logs page (for premium users only) for selected nodes. - Added a warning message to nodes that cannot be customized by user because of lack of permissions. ## [](#september-28-2018)September 28, 2018 Version: 1.3.0 ### [](#new-features-and-enhancements-6)New Features and Enhancements - Side Panel - Added API/Application monitoring metrics for selected node. - Added embedded chart from Anypoint Monitoring for selected node. - View - In-line metrics displayed for the selected node. - Drop-down to choose metric and time frame. - Improved color themes. - Permissions - Removed the **Visualizer** viewer permission. Starting this release, Anypoint Visualizer uses the **CloudHub Application Read** permission to display which applications should be shown. ### [](#fixed-issues-2)Fixed Issues - Environments with legacy Id value are shown in the environment selector ## [](#september-5-2018)September 5, 2018 Version: 1.2.0 ### [](#new-features-and-enhancements-7)New Features and Enhancements - Side Panel - Removed "Highlight most depended-on nodes" checkbox. - View - Updated "Inbound connections" legend appearance. - Updated color themes. ## [](#august-21-2018)August 21, 2018 Version: 1.1.0 ### [](#new-features-and-enhancements-8)New Features and Enhancements - Improved node layout to minimize crossing arrows. - Environment selector aligned to platform-level business group user experience. ### [](#fixed-issues-3)Fixed Issues - Allow special characters as node names - Incorrect Node positioning in special circumstances ## [](#july-27-2018)July 27, 2018 Version: 1.0.2 ### [](#new-features-and-enhancements-9)New Features and Enhancements - Changes to how permissions are managed - Users can only see the environments in which they have Runtime Manager Read applications permission, or the administrator role. - Users can only see the business groups that they have access to, and at least have one environment where they have view permissions. - Layers - Collapsed layers maintain the width of the canvas view ### [](#fixed-issues-4)Fixed Issues - Invalid dependency detected when using mule gateways - When using a Mule 4 application the flow validation component was shown as a dependency. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ## [](#june-30-2018)June 30, 2018 Version: 1.0.0 ### [](#new-features-and-enhancements-10)New Features and Enhancements This is the initial release of Anypoint Visualizer. Anypoint Visualizer provides a graphical representation of the APIs, and Mule applications, and third-party systems within your application network. See [Anypoint Visualizer](https://docs.mulesoft.com/visualizer/) for more information. ### [](#changes-in-this-release)Changes in This Release This release contains no feature changes. ### [](#fixed-issues-5)Fixed Issues There are no fixed issues in this release. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements To use Anypoint Visualizer, you must deploy you application to a supported version of Mule Runtime on CloudHub. ### [](#compatibility-notes)Compatibility Notes Anypoint Visualizer supports the following Mule runtimes running on CloudHub: - Mule Runtime, version 3.9.x - Mule Runtime, version 4.1.2
Applications using supported runtimes before June 30th, will have to update the runtime, which can be done with 0-downtime for CloudHub applications, APIs and proxies.
## [](#see-also)See Also - [Troubleshooting App Visualization](https://docs.mulesoft.com/visualizer/troubleshooting-visualization) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Visualizer Release Notes - 2019 ## [](#december-18-2019)December 18, 2019 ### [](#new-features-and-enhancements)New Features and Enhancements When you select an edge in the canvas, you can view a metric chart for the given metric. ### [](#known-limitations)Known Limitations - Edge metrics charts cannot be shown on connections from your Mule apps to external Mule apps, such as Mule apps that are in external business groups. - Anypoint Visualizer does not currently support dedicated load balancers for CloudHub apps using Mule 4. - Inbound metrics are not supported on the connection level when the source node is a Mule 4 app. For complete information about which connections support metrics, see [Supported Connection-Level Metrics](https://docs.mulesoft.com/visualizer/connection-metrics-compatibility). ## [](#december-12-2019)December 12, 2019 If you are using a Mule runtime engine version that was released after December 12, 2019, Anypoint Visualizer now supports all unicode characters with UTF-8 encoding, including international characters. You are no longer limited to using alphanumeric characters when adding layer names, tag names, and display names. ## [](#december-3-2019)December 3, 2019 ### [](#new-features-and-enhancements-2)New Features and Enhancements Anypoint Visualizer now includes a new metric called _failure rate_, which appears instead of failures. For your selected time range, failure rate is defined as the total number of failures divided by the total number of requests. This metric is available for applicable nodes and connections. ### [](#known-limitations-2)Known Limitations Inbound metrics are not supported on the connection level when the source node is a Mule 4 app. For complete information on which connections support metrics, see [Supported Connection-Level Metrics](https://docs.mulesoft.com/visualizer/connection-metrics-compatibility). ## [](#november-7-2019)November 7, 2019 ### [](#new-features-and-enhancements-3)New Features and Enhancements Anypoint Visualizer now shows the average response time and average throughput metrics on the connection level as well as the application level.
This feature is being rolled out in phases.
### [](#known-limitations-3)Known Limitations - Inbound metrics are not supported on the connection level when the source node is a Mule 4 app. For complete information on which connections support metrics, see [Supported Connection-Level Metrics](https://docs.mulesoft.com/visualizer/connection-metrics-compatibility). - Visualizer does not currently support dedicated load balancers for CloudHub apps using Mule 4. ## [](#october-29-2019)October 29, 2019 ### [](#new-features-and-enhancements-4)New Features and Enhancements Similar to Anypoint Monitoring, Visualizer now shows inbound and outbound metric values for average response time, average throughput, and failures. The value shown on the node is the weighted average of the values for the selected metric for either all inbound or all outbound connections, depending on user selection. ### [](#known-limitations-4)Known Limitations Visualizer does not currently support dedicated load balancers for CloudHub apps using Mule 4. ## [](#september-24-2019)September 24, 2019 ### [](#new-features-and-enhancements-5)New Features and Enhancements - Metrics will now load progressively in batches to increase overall topology loading time. ### [](#known-limitations-5)Known Limitations - Visualizer does not currently support dedicated load balancers for CloudHub apps using Mule version 4. ## [](#september-10-2019)September 10, 2019 ### [](#new-features-and-enhancements-6)New Features and Enhancements - You can now hide nodes through what you select in the canvas. When you select one or more nodes, you have the option to hide the services that you selected. Alternatively, you can also hide the services other than the ones that you currently have selected. To simplify the process, there is a new button that automatically selects all services in a dependency stack. - The Display Name can now be set using the Mule Runtime property `anypoint.platform.visualizer.displayName=`. - Visualizer supports Mule version 3.8.7 running on CloudHub. ### [](#fixed-issues)Fixed Issues - If there has been traffic in the past 7 days from a client app that has since been deleted, the client app is still registered and is included in the count on the group node. It will appear as “1 Deleted App” in the list of client apps in the details pane. - You now have the ability to select/unselect and customize external Mule applications (Mule apps that are not in your root organization that are being called by Mule apps that you have permission to view). These customizations persist only for your root organization. ### [](#known-limitations-6)Known Limitations - Visualizer does not currently support dedicated load balancers for CloudHub apps using Mule version 4. ## [](#august-29-2019)August 29, 2019 ### [](#new-features-and-enhancements-7)New Features and Enhancements Client ID nodes that used to appear in the canvas with a client ID as the label now appear with the respective client app name instead. To organize the canvas, all client apps that call the same Mule app are grouped into a single client app group node. The number of client apps in the group will be specified in the name. By selecting the group node in the canvas, you can see more details in the card on the left and access the full list of client apps. ### [](#known-limitation)Known limitation If there has been traffic in the past 7 days from a client app that has since been deleted, the client app is still registered and is included in the count on the group node. However, the client app’s name will not be listed with the client app names that appear in the detail pane. ## [](#july-24-2019)July 24, 2019 ### [](#new-features-and-enhancements-8)New Features and Enhancements Visualizer now has two collapsible cards: - The **Metric** card contains metric and the time range selection. - The **View** card is where you can choose which services you want to display on the canvas. It contains the menu options for defining views and filtering options by environment, tags, and services. You can also access **Save** and more menu options on this card. When you select a node in the canvas, a card appears, displaying two tabs: - The **Details** tab contains service details and configuration options. - The **Monitoring** tab contains connection information. When you toggle **Show Dependencies**, the dependents now appear in a list under the toggle. The zoom to fit functions are enhanced. To export the canvas as a PNG file, you can select **Export as Image**, located next to the zoom to fit. ## [](#june-7-2019)June 7, 2019 ### [](#new-features-and-enhancements-9)New Features and Enhancements Visualizer now detects running Mule applications that don’t appear on the canvas and: - Lists the missing applications in each environment - Outlines the reasons why Visualizer cannot support them in their current states - Directs you to where you can update the applications to make them appear in the Visualizer canvas If any apps are missing from a given environment, an icon and the number of excluded apps appear by the environment name in the side panel. Click the icon for more details. ## [](#april-30-2019)April 30, 2019 Visualizer now supports applications deployed to Runtime Fabric. See [Set up Anypoint Visualizer](https://docs.mulesoft.com/visualizer/setup) for more information. Visualizer relies on a header injection to display connections between services correctly. The header injection is disabled by default for Mule 4. The correct connections will not be displayed for your Mule 4 Runtime Fabric applications unless you enable the header injection. See [Set up Anypoint Visualizer](https://docs.mulesoft.com/visualizer/setup) for more information. This release has the following known limitations: - If a Mule 3 CloudHub app with the old Visualizer agent (version earlier than April 5, 2019) calls a Runtime Fabric ingress endpoint, there will be an extra edge from the CloudHub app to a node with the IP address for the controller. Please upgrade to the latest release of the Mule runtime engine. - If a Mule 4 CloudHub app calls a Runtime Fabric ingress endpoint, there will be and extra edge from the CloudHub app to a node with the IP address for the controller. You can use your filters within Visualizer to hide this node. - If a Runtime Fabric Mule app calls a Mule 3 CloudHub Mule app with the old Visualizer agent (version earlier than April 5, 2019) using its DNS, the correct connection is drawn, but there will be an additional edge from the **External Traffic** node to the CloudHub app. - If a Runtime Fabric Mule app calls a Mule 4 CloudHub Mule app using its DNS, the correct connection is drawn, but there will be an additional edge from the **External Traffic** node to the CloudHub app. - If you have an app in two different clusters with the same name, these applications are drawn as one node on the canvas. You should rename one app. ## [](#april-25-2019)April 25, 2019 - Visualizer editors can define views so that everyone in the organization has a dynamic and consistent view of the architecture for each project. - All Visualizer users have a private view, which provides a complete picture of all the apps they have access to. See [Visualizer Views](https://docs.mulesoft.com/visualizer/view) for more information. ## [](#april-5-2019)April 5, 2019 - Anypoint Monitoring Agent Moving to Mule Version 3.9 Runtimes - The latest patch release for Mule runtime engine version 3.9.x (04-05-2019 or later) includes an agent that unifies the Anypoint Monitoring and Anypoint Visualizer agents. Having this single agent means that applications using this Mule version display metrics in Visualizer and the -AM runtime version is no longer required. - Upgrade to 4.1.x 03-22-2019 or later, or 3.9.x 04-05-2019 or later 1. If you upgrade Mule 4 to the newest patch (03-22-2019 or later) or the Mule 3.9.x newest patch (04-05-2019 or later), you’ll notice that you can’t see your apps in Visualizer or Anypoint Monitoring. Don’t worry, they are still running. 2. You must [enable the Anypoint Monitoring agent](https://docs.mulesoft.com/visualizer/setup) to see your applications appear in Visualizer after the upgrade.
Please take careful note of which Mule versions that Visualizer now supports and the necessary tasks to perform (depending on the version) to ensure that your applications appear in Visualizer and have metrics enabled.
- Visualizer supports dedicated load balancers for apps using Mule version 3.9.x.
While Visualizer doesn’t yet support dedicated load balancers for apps using Mule version 4.1.x, MuleSoft anticipates that support for Mule version 4.2. This anticipation is not a guarantee. Visualizer documentation and release notes will be updated when support is available.
## [](#march-25-2019)March 25, 2019 - Standalone Mule Only Due to a potential performance impact for Mule 4.1.x, header injection in the Anypoint Monitoring agent is now disabled by default for standalone Mule. Visualizer does not work properly without this header, so to see your applications correctly, you must enable the property at the server level after you install the Anypoint Monitoring Agent. For instructions, see [Set up Anypoint Visualizer](https://docs.mulesoft.com/visualizer/setup#_set_up_for_standalone_mule). ## [](#march-23-2019)March 23, 2019 Version 2.1.0 ### [](#new-features-and-enhancements-10)New Features and Enhancements - Side Panel - Replaced Rename Node feature with the ability to modify the Display Name of a service from the Customization section of the details. - View - Layers set via application properties can no longer be overridden in the Customization section within the Visualizer UI. - Layers can no longer be deleted or renamed. Instead, reassign a service to a new layer to accomplish the same outcome. - All default layers (System, Process, Experience) will be offered by default and cannot be deleted. - Anypoint Monitoring Agent Moving to Non-AM Runtimes - The latest patch release for Mule runtime engine version 4.1.x (03-23-2019 or later) includes an agent that unifies the Anypoint Monitoring and Anypoint Visualizer agents. Having this single agent means that applications using this Mule version display metrics in Visualizer and the -AM runtime version is no longer required. - Upgrade to 4.1.x 03-23-2019 1. If you upgrade Mule 4 to the newest patch (03-23-2019 or later), you’ll notice that you can’t see your apps in Visualizer or Anypoint Monitoring. Don’t worry, they are still running. 2. You must [enable the Anypoint Monitoring agent](https://docs.mulesoft.com/visualizer/setup) to see your applications appear in Visualizer after the upgrade.
Please take careful note of which Mule versions that Visualizer now supports and the necessary tasks to perform (depending on the version) to ensure that your applications appear in Visualizer and have metrics enabled.
### [](#changes-to-layers)Changes to Layers - Layer labels and names may change. The first letter of every layer will be capitalized. All default layers will be restored. ## [](#february-11-2019)February 11, 2019 Version 2.0.3 ### [](#new-features-and-enhancements-11)New Features and Enhancements - Side Panel - Added **Export as PNG** button that allows users to export their network topology as it is currently displayed on the canvas. ## [](#january-23-2019)January 23, 2019 Version 2.0.2 ### [](#new-features-and-enhancements-12)New Features and Enhancements - View - Edges shown between services are now active. This means that they appear only if there has been traffic in the past seven days. Non-active edges do not appear on the canvas. - When a service connects to a service in an organization in which a user does not have the **CloudHub Viewer** permission, the service the user does not have access to is displayed as an HTTP node. ## [](#january-8-2019)January 8, 2019 Version 2.0.1 ### [](#new-features-and-enhancements-13)New Features and Enhancements - Side Panel - Changed **Include related services** box to a toggle named **Show dependents and dependencies**, which allows you to view dependencies of the nodes and services with the selected tags. - Updated the placement of the **Select all/Select none** button for filtering. - View - Updated icon on node to indicate if application is deployed in CloudHub or on-premises. ### [](#fixed-issues-2)Fixed Issues - Hostname is no longer truncated in the details panel. - Fixed **Select all/select none** button functionality to work as expected with search bar within environments and services filtering. ## [](#see-also)See Also - [Troubleshooting App Visualization](https://docs.mulesoft.com/visualizer/troubleshooting-visualization) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint Visualizer Release Notes - 2020 ## [](#may-20-2020)May 20, 2020 ### [](#new-feature)New Feature You can now access the Troubleshooting visualization for an app in the **Application Network** section of the **Built-In Dashboards** page in Anypoint Monitoring. The **Application Network** section enables you to view direct callers and callees for a single app for the most recent seven days. ## [](#april-20-2020)April 20, 2020
IE 11 is not supported in Anypoint Visualizer.
### [](#enhancements)Enhancements If you are using Mule version 4.x released on April 7, 2020 or later, header injection is now enabled by default. For more information on how this change affects connection-level metrics compatibility, see [Supported Connection-Level Metrics](https://docs.mulesoft.com/visualizer/connection-metrics-compatibility). ## [](#january-28-2020)January 28, 2020 ### [](#new-features-and-enhancements)New Features and Enhancements - Anypoint Visualizer is redesigned to host three use case-specific visualizations (Architecture, Troubleshooting, and Policy). You can open your defined views in each of these contexts to see different metadata for each of your services. - Anypoint Visualizer now provides the Policy visualization. This visualization shows the relationships between your Mule app deployments and the APIs they are implementing. It has an overview mode that shows all of the policies applied to your APIs, and a compliance mode in which you can select individual policies from a list and see which APIs are compliant or noncompliant through visual indicators in the canvas. ### [](#known-limitations)Known Limitations If you are using Runtime Fabric, the Policy visualization is not yet supported. ## [](#see-also)See Also - [Troubleshooting App Visualization](https://docs.mulesoft.com/visualizer/troubleshooting-visualization) - [Known Issues](https://help.salesforce.com/s/issues) # Anypoint VPN Updates Release Notes After the October 2022 quarterly maintenance window, Anypoint VPN will no longer support quarterly customer self-upgrades. From this point forward, updates made to Anypoint VPN will adhere to AWS’s standard continuous upgrade process. Upgrades will be applied on-demand, with no published maintenance window schedule, and no customer opt-in self-upgrade capabilities. In addition to these release notes, see [Anypoint VPN Maintenance](https://docs.mulesoft.com/cloudhub/vpn-maintenance) to avoid any impact on VPN availability. Anypoint VPN-related new feature releases will be updated in [CloudHub Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes). ## [](#see-also)See Also - [Troubleshoot Anypoint VPN](https://docs.mulesoft.com/cloudhub/vpn-troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Apache Kafka Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Apache Kafka (Kafka Connector) enables you to connect to the Apache Kafka messaging system, enabling seamless integration between your applications and an Apache Kafka cluster. Guide: [Apache Kafka Connector](https://docs.mulesoft.com/kafka-connector/latest/) Reference: [Apache Kafka Connector Reference](https://docs.mulesoft.com/kafka-connector/latest/kafka-connector-reference) ## [](#4-15-4)4.15.4 **October 23, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.4 to address reported security vulnerabilities.

W-24605939
## [](#4-15-3)4.15.3 **October 8, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.xerial.snappy:snappy-java library is upgraded to version 1.1.10.11 to address reported security vulnerabilities.

W-24409903
## [](#4-15-2)4.15.2 **September 29, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Consumed Avro messages that include decimal logical types now render numeric values correctly. To enable this functionality, use the mule.kafka.muleKafkaAvroDeserializer.useLogicalTypeAwareRenderer system property. For more information, see Configure the Confluent Schema Registry in the Kafka Connector Connection.

W-23832785

The io.confluent:kafka-avro-serializer library is upgraded to 7.9.9.

W-23832785

The at.yawk.lz4:lz4-java library is upgraded to 1.11.3.

W-23832785

The com.github.luben:zstd-jni library is upgraded to 1.5.7-18 to address reported security vulnerabilities.

W-24165087

The com.fasterxml.jackson.core:jackson-databind library is upgraded to 2.22.3 to address reported security vulnerabilities.

W-24311523, W-24311522, W-24311518, W-24311520
## [](#4-15-1)4.15.1 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Publish operation no longer deadlocks when the connector retries a failed connection.

W-17754401

The connector no longer leaves unused consumer client IDs that continuously attempt to reconnect after the consumer pool unexpectedly closes.

W-22537872
## [](#4-15-0)4.15.0 **August 20, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - Kafka Connector now supports AWS Identity and Access Management (IAM) authentication for secure connections to Amazon MSK clusters. For more information, see [Consumer SASL/AWS IAM Connection](https://docs.mulesoft.com/kafka-connector/latest/kafka-connector-reference#consumer-sasl-aws-iam) and [Producer SASL/AWS IAM Connection](https://docs.mulesoft.com/kafka-connector/latest/kafka-connector-reference#producer-sasl-aws-iam). For examples, see [Configure AWS IAM Authentication](https://docs.mulesoft.com/kafka-connector/latest/kafka-connector-configure-aws-iam-example). ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Batch Message Listener source no longer throws a MULE:EXPRESSION error when using the default redelivery policy.

W-18772894

The at.yawk.lz4:lz4-java library is upgraded to version 1.11.2 to address reported security vulnerabilities.

W-23796448
## [](#4-14-0)4.14.0 **June 12, 2026** ### What’s New - Kafka Connector now supports DataWeave expressions in connection parameters. Expression support applies to the username, password, token ID, token HMAC, client ID, client secret, consumer group ID, and bootstrap servers parameters. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core:jackson-databind component is upgraded to 2.22.0.

W-3300013

The at.yawk.lz4:lz4-java component is upgraded to 1.11.0.

W-3300013

The commons-io:commons-io component is upgraded to 2.22.0.

W-3300013
## [](#4-13-1)4.13.1 **April 25, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated Apache Kafka client to version 3.9.2 for enhanced security and stability.

W-22161314
## [](#4-13-0)4.13.0 **March 21, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-20953782
## [](#4-12-2)4.12.2 **January 23, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now includes the secure LZ4 compression library (at.yawk.lz4:lz4-java:1.10.1) as an explicit dependency, ensuring full support for LZ4 compression (compression.type=lz4). This update addresses a security vulnerability (CVE-2025-66566) in the previous LZ4 implementation while maintaining complete functionality for LZ4 compression.

W-20880709
## [](#4-12-1-deprecated)4.12.1 (Deprecated) This version is deprecated. The fixed issues for this version are in version [4.12.2](#4-12-2). **December 21, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now properly skips certificate validation when the TLS context is configured with insecure=true. Previously, the connector failed with certificate validation errors even when certificate validation was explicitly disabled. The fix implements a custom SSL engine factory that correctly handles the insecure TLS context setting.

W-18214347
## [](#4-12-0)4.12.0 **November 5, 2025** ### What’s New - Kafka Connector now supports deserializing records serialized with Avro schemas. This new functionality enables you to easily integrate your Mule applications with Avro Schema Deserializer. For details, refer to [Configure the Confluent Schema Registry](https://docs.mulesoft.com/kafka-connector/latest/kafka-connector-configure-confluent-example#configure-the-confluent-schema-registry). ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer throws a ClassCastException at runtime when attempting to use a custom deserializer, such as KafkaAvroDeserializer, that returns Java objects instead of the required InputStream. To enable Avro deserialization, configure the connector to use the new internal deserializer: MuleKafkaAvroDeserializer.

W-19153642
## [](#4-11-1)4.11.1 **September 24, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Upgraded jackson-databind library version from 2.18.3 to 2.20.0.
Upgraded snappy-java library version from 1.1.10.7 to 1.1.10.8.
Upgraded commons-io library version from 2.18.0 to 2.20.0.

W-19688916
## [](#4-11-0)4.11.0 **August 28, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0, 3.9.1

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

All operations now throw the new KAFKA:SECURITY error.

W-19132680
## [](#4-10-2)4.10.2 **July 23, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Kafka client dependency is upgraded to version 3.9.1 to fix the CVE-2025-27817 vulnerability.

W-19063366
## [](#4-10-1)4.10.1 **April 17, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, 3.7.0, 3.8.0, 3.9.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer overrides serializers configuration when it is configured in the Additional Properties field for both the Publish and Bulk publish operations.

W-17105037
## [](#4-10-0)4.10.0 **December 19, 2024** ### What’s New - The **Partitioner** field for all connection types in the producer configuration now includes a `NONE` option, which enables the Kafka client to manage the partition strategy. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, and 3.7.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer overrides the transaction ID if it is configured in the Additional Properties field in the producer configuration.

W-17105037

The connector now handles Kafka headers with null values properly by converting them to empty byte arrays instead of throwing a NullPointerException error.

W-16167262
## [](#4-9-0)4.9.0 **August 23, 2024** ### What’s New - The **Bulk publish** operation is added to publish multiple messages at the same time. - The custom `MuleKafkaAvroSerializer` property is added to publish messages in Avro format. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, and 3.7.0

OpenJDK

8, 11, and 17
## [](#4-8-0)4.8.0 **June 18, 2024** ### What’s New - Apache Kafka Connector now supports OAuth2 Client Credentials grant type authentication to integrate seamlessly with OAuth2-compliant authorization servers. Use the **Consumer SASL/OAUTHBEARER - Client Credentials Connection** or **Producer SASL/OAUTHBEARER - Client Credentials Connection** options in the connector configuration. - The consumer and producer connection configurations have a new **Additional properties** field to customize the Kafka connection as you desire. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, 3.6.1, and 3.7.0

OpenJDK

8, 11, and 17
## [](#4-7-6)4.7.6 **May 31, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, and 3.6.1

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector performance is now improved when redeploying.

W-15637208
## [](#4-7-5)4.7.5 **February 2, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, 3.5.1, and 3.6.1

OpenJDK

8, 11, and 17
## [](#4-7-4)4.7.4 **January 9, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, 3.4.0, and 3.6.1

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Mule application deployment no longer fails when the connector connection test fails.

W-13197433

The Kafka clients library is upgraded to version 3.6.1 to address reported security vulnerabilities.

W-14486778
## [](#4-7-3)4.7.3 **November 29, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, and 3.4.0

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded snappy-java library version from 1.1.8.1 to 1.1.10.4.

W-14486778
## [](#4-7-2)4.7.2 **May 4, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0, 3.3.2, and 3.4.0

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Kafka Clients library from org.apache.kafka:kafka-clients:3.3.2 to org.apache.kafka:kafka-clients:3.4.0.

W-12665458
## [](#4-7-1)4.7.1 **March 17, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0 and 3.3.2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Updated the Maximum polling interval field description both in the Studio UI and the Apache Kafka Connector Reference.

W-12660459

Updated internal dependencies.

W-12710406
## [](#4-7-0)4.7.0 **February 13, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.1, 3.2.0 and 3.3.2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Kafka Connector now uses kafka-clients 3.3.2.

W-11554436

The Publish operation now handles AUTHENTICATION_ERROR.

W-12042969

Kafka connector now supports the boolean system property -Dmule.kafka.publish.useNull to be set as true or false, if not set, the default value is false. This allows the Publish operation to send null messages.

W-12150770
## [](#4-6-8)4.6.8 **November 25, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Kafka record is no longer empty when using the Consume operation more than once without using the Commit operation.

W-11768903

Kafka Connector now throws the expected error when the message body exceeds the maximum topic size.

W-12042969
## [](#4-6-7)4.6.7 **May 30, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The connector now displays the correct field names for Default operation poll timeout and Default operation poll timeout time unit.

W-11137428
## [](#4-6-6)4.6.6 **May 5, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Kafka message key is no longer empty when reprocessing messages when the topic contains more than one partition.

W-11048498

The connector no longer throws null pointer exceptions when the message key is null.

W-11090869
## [](#4-6-5)4.6.5 **April 7, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Kafka message key is no longer empty when reprocessing messages.

W-10795597, W-10889605
## [](#4-6-4)4.6.4 **February 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Reconnection issues caused the Kafka Message Listener to stop consuming messages.

SE-22821, SE-24437
## [](#4-6-3)4.6.3 **February 2, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The IsolationLevel parameter was declared but not implemented in the code.

CONN-9887
## [](#4-6-2)4.6.2 **January 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Kafka Message Listener did not process tombstone messages correctly.

SE-23630

Kafka Message Listener stopped when attempting to consume messages in corner cases.

SE-22821
## [](#4-6-1)4.6.1 **October 27, 2021** ### What’s New - Upgraded the Kafka client library to version 2.8.1. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, 2.7.0, and 2.8.1

OpenJDK

8 and 11
## [](#4-6-0)4.6.0 **October 19, 2021** ### What’s New - Added the **Consumer SASL/TOKEN Connection** and **Producer SASL/TOKEN Connection** authentication types, which use token delegation to connect to the Kafka cluster. ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
## [](#4-5-7)4.5.7 **September 28, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Kafka Connector reconnection did not work when there was an ACL access issue.

SE-22595

Kafka Message Listener did not handle duplicate headers.

SE-22520
## [](#4-5-6)4.5.6 **September 15, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The reconnection strategy did not work.

SE-22340
## [](#4-5-5)4.5.5 **July 12, 2021** ### [](#compatibility-37)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### [](#fixed-issues-32)Fixed Issues - Kafka **Consumer** and **Message Listener** failed after picking one message. (SE-21705) ## [](#4-5-4)4.5.4 **June 11, 2021** ### [](#compatibility-38)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### [](#fixed-issues-33)Fixed Issues - Kafka **Message Listener** failed to process messages while using IMMEDIATE ACK. (SE-21070) ## [](#4-5-3)4.5.3 **June 8, 2021** ### [](#compatibility-39)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### [](#fixed-issues-34)Fixed Issues - Kafka Connector was continuously rebalancing the loop when using multiple consumers per partition. (SE-20824) ## [](#4-5-2)4.5.2 **April 8, 2021** ### [](#compatibility-40)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### [](#fixed-issues-35)Fixed Issues - Payload was null in the Batch component when using the Batch message listener source. (SE-20119) ## [](#4-5-1)4.5.1 **March 19, 2021** ### [](#compatibility-41)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### [](#fixed-issues-36)Fixed Issues - Performance degraded when using the Publish operation. (SE-20124) - Kafka connector created a new connection every time a producer published a new message. (SE-20003) ## [](#4-5-0)4.5.0 **February 25, 2021** ### [](#compatibility-42)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, 2.6.0, and 2.7.0

OpenJDK

8 and 11
### [](#features)Features Added a new configuration property to Producer connections to enable the selection of a message partition strategy from those provided by the `kafka-clients` library. The message partition strategy is used for routing messages to partitions when a key or a partition is not provided. ### [](#fixed-issues-37)Fixed Issues Fixed the performance degradation issue that occurred when an incorrect key was used to remove closed sessions. (SE-19638) ## [](#4-4-3)4.4.3 **January 29, 2021** ### [](#compatibility-43)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, and 2.7.0

OpenJDK

8 and 11
### [](#fixed-issues-38)Fixed Issues Fixed the Anypoint Studio test connection functionality for producer and consumer connections. ## [](#4-4-2)4.4.2 **January 15, 2021** ### [](#compatibility-44)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0, and 2.7.0

OpenJDK

8 and 11
### [](#features-2)Features Upgraded the Kafka client library to version 2.7.0. ## [](#4-4-1)4.4.1 **January 12, 2021** ### [](#compatibility-45)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0

OpenJDK

8 and 11
### [](#fixed-issues-39)Fixed Issues On Windows, using backslashes as path separators when providing a full path for a keytab file did not work. (SE-15416) ## [](#4-4-0)4.4.0 **November 26, 2020** ### [](#compatibility-46)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0

OpenJDK

8 and 11
### [](#new-features)New Features Added the ability to leverage the manual offset commit option for the **Consume** operation. ### [](#fixed-issues-40)Fixed Issues The manual connector commit inside Mule error handling had no effect. (SE-18605) ## [](#4-3-5)4.3.5 **November 2, 2020** ### [](#compatibility-47)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0

OpenJDK

8 and 11
### [](#fixed-issues-41)Fixed Issues Apache Kafka Connector ignored the values of the **Heartbeat interval** and **Session timeout** fields in the consumer configuration. (SE-18343) ## [](#4-3-4)4.3.4 **October 15, 2020** ### [](#compatibility-48)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0

OpenJDK

8 and 11
### [](#fixed-issues-42)Fixed Issues The issue that caused the Kafka Connector source to fail to reconnect after multiple queue stop events is fixed. (SE-17727) ## [](#4-3-3)4.3.3 **September 18, 2020** ### [](#compatibility-49)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0

OpenJDK

8 and 11
### [](#fixed-issues-43)Fixed Issues The issue that caused Kafka Connector to throw a `KAFKA:COMMIT_FAILED` error when messages took a longer time to process than what was specified in the **Maximum poll interval** parameter is fixed. (SE-17447) ## [](#4-3-2)4.3.2 **July 30, 2020** ### [](#compatibility-50)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0
### [](#fixed-issues-44)Fixed Issues The issue that caused Kafka Connector to throw a `No ConnectionProvider defined` error when the connection expires while the client consumer is polling is fixed. (SE-16727) ## [](#4-3-1)4.3.1 **July 14, 2020** ### [](#compatibility-51)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0
### [](#fixed-issues-45)Fixed Issues Fixed an issue where the value for the password key of the JAAS configuration was not set. (SE-16670) ## [](#4-3-0)4.3.0 **June 30, 2020** ### [](#compatibility-52)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0
### [](#new-features-2)New Features Added support for a SASL/PLAIN connection. ## [](#4-2-0)4.2.0 **June 19, 2020** ### [](#compatibility-53)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0, 2.5.0
### [](#new-features-3)New Features Added support for a Kerberos connection. ### [](#fixed-issues-46)Fixed Issues - Kafka Connector 4.1.0 did not allow you to pass `ssl.endpoint.identification.algorithm` with a blank value. (SE-16215) - Kafka Connector 4.0.0 had missing connection options. (SE-15175) ## [](#4-1-0)4.1.0 **May 28, 2020** ### [](#compatibility-54)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0
### [](#new-features-4)New Features - Added the SASL SCRAM connection type for connecting to a Kafka broker. This connection type works with the SCRAM-SHA-256 and SCARM-SHA-512 authentication mechanisms. - Added the Endpoint Identification Algorithm field to all connection types. Clients use this field to validate the server hostname. ### [](#fixed-issues-47)Fixed Issues - Inability to set additional properties in Kafka Connector 4.0.0 (SE-15197) ## [](#4-0-0)4.0.0 **February 25, 2020** ### [](#compatibility-55)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0
### [](#new-features-5)New Features Kafka Connector 4.0.0 contains a lot of changes to improve efficiency, including new operations to enable you to better understand how to use the connector. All of the changes included in this version break backward compatibility. See [Kafka Connector Upgrade](https://docs.mulesoft.com/kafka-connector/latest/kafka-connector-upgrade-migrate) for detailed information about all of the changes in this release. The new features and changes in this release include: - Four new operations, including: - Commit - Consume - Publish - Seek - A new Batch Message Listener source - The addition of different acknowledgment modes in the Consumer configuration, including: - AUTO - MANUAL - DUPS\_OK - IMMEDIATE - One plaintext connection type that supports transactions ## [](#3-0-12)3.0.12 **September 9, 2020** ### [](#compatibility-56)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.4.0
### [](#fixed-issues-48)Fixed Issues - Fixed a vulnerability related to the Guava library. - Kafka Connector versions 3.0.8 through 3.0.11 do not work with Mule 4.1.x, as previously stated by the documentation. (SE-17493) ## [](#3-0-11-deprecated)3.0.11 (Deprecated) **June 12, 2020** ### [](#compatibility-57)Compatibility
Software Version

Mule

4.2.1 and later

Apache Kafka

2.4.0
### [](#fixed-issues-49)Fixed Issues Changed the Scheduler type from cpuLight to IO. (SE-16328) ## [](#3-0-10-deprecated)3.0.10 (Deprecated) **December 17, 2019** ### [](#compatibility-58)Compatibility
Software Version

Mule

4.2.1 and later

Apache Kafka

2.4.0
### [](#fixed-issues-50)Fixed Issues - Updated Kafka Client version to the latest to prevent internal exceptions. (SE-14104) - Fixed Kafka consumer disconnection that occurred after a period of inactivity. (SE-14221) ## [](#3-0-9-deprecated)3.0.9 (Deprecated) **December 16, 2019** ### [](#compatibility-59)Compatibility
Software Version

Mule

4.2.1 and later

Apache Kafka

2.3.0
### [](#fixed-issues-51)Fixed Issues Fixed relative path issue for Kafka connector settings with Windows. (SE-14140) ## [](#3-0-8-deprecated)3.0.8 (Deprecated) **November 25, 2019** ### [](#compatibility-60)Compatibility
Software Version

Mule

4.2.1 and later

Apache Kafka

2.3.0
### [](#fixed-issues-52)Fixed Issues When `KafkaConsumer` was stopped by the Mule runtime engine, Kafka threw a concurrency error. (SE-13970) ## [](#3-0-7)3.0.7 **August 21, 2019** ### [](#compatibility-61)Compatibility
Software Version

Mule

4.1.1 and later

Apache Kafka

2.3.0
### [](#features-3)Features - Upgraded the Kafka Clients library to version 2.3.0. (CONN-2857) - Implemented validation method for producer and consumer connection. (CONN-2698) - Added Scheduler Service for spawning new threads for consumers. (CONN-2849) ### [](#fixed-issues-53)Fixed Issues - Refactoring to improve compliance with the Mule development best practices. (CONN-2699, CONN-2700, CONN-2701, CONN-2702, CONN-2848, CONN-2703, CONN-2847, CONN-2747, CONN-2696, CONN-2697) - Deprecated the UNKNOWN error type that will be removed in the next major upcoming release. (CONN-2703) - In Kafka versions 3.0.2 to 3.0.6, in the **Publish Message** operation, the **Key** field appeared in Anypoint Studio as required. In version 3.0.7, the **Key** field was no longer required. - In Kafka versions 3.0.2 to 3.0.6, in the **Message Consumer** source operation, the **Partition Offsets** field was described as "a list of offsets representing the partitions offsets configuration. For each element in the list you have to specify partition index and offset". In version 3.0.7, the **Partition Offsets** field is now described as "a list of objects that contain the index of the partition and the offset". - In Kafka versions 3.0.2 to 3.0.6, in the **Message Consumer** source operation, the **Partition Offsets** field is typed as an array of offsets. In 3.0.2 to 3.0.6 in the Offset array, the **Partition Number** and **Partition Offset** fields did not require values. In 3.0.7, the **Partition Number** and **Partition Offset** fields now require values. - In Kafka versions 3.0.2 to 3.0.6, in the **Repeatable File Store Stream** object, the **Max in Memory Size** field name was changed to be **In Memory Size** in 3.0.7. ## [](#3-0-6)3.0.6 **July 2, 2019** ### [](#compatibility-62)Compatibility
Software Version

Mule

4.0.0 and later

Apache Kafka

2.2.0
### [](#fixed-issues-54)Fixed Issues Kafka connector overrode the user-defined `security.protocol=SASL_SSL` to use the `security.protocol=SSL` value. (SE-11947) ## [](#3-0-5)3.0.5 **June 19, 2019** ### [](#compatibility-63)Compatibility
Software Version

Mule

4.0.0 and later

Apache Kafka

2.2.0
### [](#fixed-issues-55)Fixed Issues - Updated the Kafka Clients library to version 2.2.0. - Updated code to use the `poll(java.time.Duration)` method provided in the new library that replaces the deprecated `poll(long)` method. The deprecated method did not block beyond the timeout for waiting on a partition assignment. (KIP-266) ## [](#3-0-4)3.0.4 **May 16, 2019** ### [](#compatibility-64)Compatibility
Software Version

Mule

4.0.0 and later

Apache Kafka

0.10.2.0
### [](#fixed-issues-56)Fixed Issues Fixed a performance connection validation issue relating to the same issue as in v3.0.3. (SE-11817) ## [](#3-0-3)3.0.3 **May 16, 2019** ### [](#compatibility-65)Compatibility
Software Version

Mule

4.0.0 and later

Apache Kafka

0.10.2.0
### [](#fixed-issues-57)Fixed Issues - The **Test Connection** button in Anypoint Studio for the Kafka connector did not work in Mule 4. (SE-11817) - Fixed a performance connection validation issue relating to the same issue as in v3.0.3. (SE-11817) ## [](#3-0-2)3.0.2 **April 30, 2019** ### [](#compatibility-66)Compatibility
Software Version

Mule

4.0.0 and later

Apache Kafka

0.10.2.0
### [](#fixed-issues-58)Fixed Issues - Can’t stop Kafka consumer flow. See [How To Stop Or Start Flows In Mule 4.x Programmatically](https://help.salesforce.com/s/articleView?id=001114843&type=1). (SE-11337) - The **Test Connection** button in Anypoint Studio for the Kafka connector did not work in Mule 4. (SE-11817) ## [](#3-0-1)3.0.1 **June 26, 2018** ### [](#compatibility-67)Compatibility
Software Version

Mule

4.0.0 and later

Apache Kafka

0.10.2.0
### [](#features-4)Features None ### [](#fixed-issues-59)Fixed Issues Kafka connector was not serializing and deserializing properly the messages that were not plain text. Now the content of the messages can be sent as any type (plain, XML, JSON) as the value is serialized and deserialized properly. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # API Catalog CLI Release Notes MuleSoft announces the release of Anypoint API Catalog CLI. API Catalog CLI enables you to discover and catalog your API definitions, documentation files, and associated metadata by running commands at a command prompt or as part of your automation tools, such as a CI/CD pipeline or custom scripts. ## [](#1-1-2)1.1.2 **March 06, 2024** ### Fixed Issues
Issue Resolution ID

API Catalog now shows a detailed error message when the publication of an asset fails.

W-15084821
## [](#1-1-1)1.1.1 **October 31, 2023** ### What’s New - Certain dependencies are updated. ## [](#1-1-0)1.1.0 **April 1, 2023** ### What’s New - You can now use API Catalog CLI with a Network Proxy. For more information, see [Using API Catalog CLI with a Network Proxy.](https://docs.mulesoft.com/jp/exchange/apicat-use-proxy) - You can now authenticate to API Catalog with the new environment variable `ANYPOINT_CERTIFICATE`. This variable adds CAcert certificates to API Catalog CLI. ### Fixed Issues
Issue Resolution ID

API Catalog now successfully publishes ASSETs when running behind a proxy.

W-12353992
## [](#1-0-2)1.0.2 **July 23, 2022** ### Fixed Issues
Issue ID

API Catalog now successfully creates the documentation page when defining references between markdown files.

W-11133763
## [](#1-0-1)1.0.1 May 17, 2022 ### What’s New This release includes the following changes: - Improvements to the documentation in the `api-catalog-tool` Github repository and the `api-catalog-cli` npm page ## [](#1-0-0)1.0.0 May 16, 2022 ### What’s New You can autocatalog your APIs using the API Catalog CLI commands as follows: - Run the API Catalog `create-descriptor` command to identify and create descriptor information for all API assets in your API project directory structure. - Run the API Catalog `update-descriptor` command to identify new and changed APIs and update the descriptor information. - Reference the descriptor file in the API Catalog `publish-asset` command to publish the API assets to Exchange either at a command prompt or as part of your CI/CD pipelines or custom scripts. You can control the API information to publish using the descriptor file as follows: - Add descriptor information that cannot be automatically generated, such as version strategies and tags. - Add descriptor conditions and pass parameters to the publish command to determine whether all or some of the APIs are published. - Add descriptor conditions and pass parameters to the publish command to control the version strategy of the APIs that are published. ### [](#commands)Commands
Command Description

api-catalog autocomplete

Configures autocompletion for API Catalog commands

api-catalog conf

Creates or deletes a credentials configuration file

api-catalog create-descriptor

Creates a descriptor file

api-catalog update-descriptor

Updates a descriptor file

api-catalog publish-asset

Publishes assets to Exchange
### [](#documentation)Documentation For details, see the [API Catalog CLI documentation](https://docs.mulesoft.com/jp/exchange/apicat-about-api-catalog-cli). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # API Community Manager Release Notes Use Anypoint API Community Manager to build and operate communities around your APIs for developers and partners, both inside and outside of your organization, who write applications that use your APIs. The following release notes are provided for API Community Manager: - [Anypoint API Community Manager Release Notes](https://docs.mulesoft.com/jp/release-notes/api-community-manager/api-community-manager-release-notes) ## [](#see-also)See Also - [API コミュニティマネージャー](https://docs.mulesoft.com/jp/api-community-manager/) - [Known Issues](https://help.salesforce.com/s/issues) # API Console Release Notes API Console automatically generates documentation for an API project. An interactive component, API Console shows information about your REST APIs and their methods, and enables you to test the methods by sending requests. API Console is embedded in multiple MuleSoft platform products including API Designer, Exchange, and Studio. ## [](#6-6-40)6.6.40 February 9, 2024 ### Fixed Issues
Issue Resolution ID

Imported schemas and XML examples now display in the Documentation panel.

W-14846319

In Design Center and Exchange, Swaqgger JSON now displays valid examples in the response.

W-14874965
## [](#6-6-39)6.6.39 January 15, 2024 ### Fixed Issues
Issue Resolution ID

Design Center now generates JSON with nested objects for OAS 3.0.

W-14278539

AsyncAPI examples now appear in the API Console.

W-14588829

XML examples now show in REST APIs for OAS.

W-14651311
## [](#6-6-38)6.6.38 November 11, 2023 ### Fixed Issues
Issue Resolution ID

Header names are no longer showing in code examples.

W-14454298

When editing an example, the mocking service URL no longer changes and causes the request to fail.

W-14071465

The example names are no longer missing when defining the XML schema definition.

W-12646073
## [](#6-6-37)6.6.37 October 23, 2023 ### Fixed Issues
Issue Resolution ID

The example for an API is no longer missing.

W-14102462

An unexpected Content type header is no longer added to a GET request when a POST request was sent previously during the same browser session.

W-13959789
## [](#6-6-36)6.6.36 September 25, 2023 ### Fixed Issues
Issue Resolution ID

The cookie authentication value is now sent in the Cookies header.

W-13832170

The Authorization scopes in the Security section now updates between endpoints.

W-14015302
## [](#6-6-35)6.6.35 August 28, 2023 ### Fixed Issues
Issue Resolution ID

The child property no longer displays mandatory fields.

W-13772034

The query parameters are now rendering properly and the parameter value box is no longer hidden.

W-13813608

A new error message now displays for error code 0.

W-13957966
## [](#6-6-34)6.6.34 July 31, 2023 ### Fixed Issues
Issue Resolution ID

A field error no longer overlaps with other inputs.

W-13463891

Query parameters now list all options.

W-13599882
## [](#6-6-33)6.6.33 July 3, 2023 ### Fixed Issues
Issue Resolution ID

The oauth-popup.html no longer causes an access vulnerability.

W-1358830

The anyOf details now display in the OAS specification.

W-13547158

All fields no longer display as required.

W-13536254

Fields are now rending in the request panel.

W-13524893

The content for schema types now displays in the API specification.

W-13207777

An error no longer displays when the oneOf keyword is used in the JSON schema.

W-13079436
## [](#6-6-32)6.6.32 June 5, 2023 ### Fixed Issues
Issue Resolution ID

The URL protocol is no longer missing when making a request.

W-112688568
## [](#6-6-31)6.6.31 May 12, 2023 ### Fixed Issues
Issue Resolution ID

When an OAS API specification scheme is not defined, HTTPS is now the default for the URL protocol.

W-12598786

For AsyncAPIs, the Kafka key element and its datatype now display in the documentation panel.

W-12528949
## [](#6-6-30)6.6.30 April 24, 2023 ### Fixed Issues
Issue Resolution ID

For AsyncAPIs, the Kafka key element and its datatype now display in the documentation panel.

W-12528949
## [](#6-6-29)6.6.29 March 27, 2023 ### Fixed Issues
Issue Resolution ID

OAuth 2.0 token generation now populates after the request.

W-12119152

DIN fonts are now deprecated.

W-12726752
## [](#6-6-28)6.6.28 February 17 ### Fixed Issues
Issue Resolution ID

Data type values now display correctly in the documentation panel.

W-12137562

The request access token is now working as expected with the OAuth 2.0 implicit flow.

W-12227877

Types now render as expected in the documentation panel when called from other libraries.

W-12276910

Properties are no longer missing in generated examples when merging anyOf and properties in OAS 2.0.

W-1248170

The value for anyOf now displays when clicking Show in the documentation panel.

W-12428173
## [](#6-6-27)6.6.27 February 1, 2023 ### Fixed Issues
Issue Resolution ID

Boundary is no longer missing in multipart content-type headers.

W-12465439
## [](#6-6-26)6.6.26 January 6, 2023 ### Fixed Issues
Issue Resolution ID

Information is no longer missing when merging allOf and properties in OAS 2.0.

W-12142859

The mocking service now receives the correct Content-type.

W-12146715

The information for the allOf type now displays in the documentation.

W-12183115
## [](#6-6-25)6.6.25 December 19, 2022 ### Fixed Issues
Issue Resolution ID

The documentation for type is no longer missing when properties are defined as allOf.

W-12065773
## [](#6-6-24)6.6.24 November 17, 2022 ### Fixed Issues

Issue Resolution

ID

The custom query parameters are no longer reset when the server value is set in the Request panel.

W-12030452
## [](#6-6-23)6.6.23 October 28. 2022 ### Fixed Issues

Issue Resolution

ID

The request URL now populates correctly.

W-11386481

The example for string arrays now generate correctly.

W-11798608

The example for enum types in parameters section are no longer missing.

W-11836777

The correct value now displays for the header when making requests.

W-11843862

The miniItems and maxItems values are no longer missing in the data type documentation.

W-11858334

You now can allow the OAuth2 Token requests to be prevented.

W-11921592

The names for security fields now display correctly.

W-11939928
## [](#6-6-22)6.6.22 October 11, 2022 ### Fixed Issues

Issue Resolution

ID

Parameters are now sent on request.

W-11517665
## [](#6-6-21)6.6.21 September 16, 2022 ### What’s New - For an AsyncAPI with multiple messages for an operation, you can now choose a message from the drop-down menu. ## [](#6-6-20)6.6.20 August 26, 2022 ### Fixed Issues

Issue

ID

Optional headers are now shown in the Documentation panel.

W-11429833

The input fields in the Try it panel now display properly.

W-11486959

The input fields in the Try it panel no longer display as missing information once rendered.

W-11486967

The labels of multiple API keys now render correctly in the Documentation panel and in the Request panel.

W-11541233
## [](#6-6-19)6.6.19 August 5, 2022 ### Fixed Issues

Issue

ID

In OpenAPI, deprecated endpoints are now displaying in the documentation panel.

W-11383870

Examples in OAS 3.0.0 for content-type application/xml are now displaying tags with a prefix.

W-11423667
## [](#6-6-18)6.6.18 July 15, 2022 ### Fixed Issues

Issue

ID

An array now displays an element in the API documentation preview.

W-11117349

The miniItems and maxItems information is now displaying in the data type documentation.

W-11209734
## [](#6-6-17)6.6.17 June 24, 2022 ### Fixed Issues

Issue

ID

All messages render correctly when there are multiple AsyncAPI messages.

W-11105366

XML responses render correctly in the response viewer.

W-11196904

Operation headers for AsyncAPIs render correctly.

W-11308473
## [](#6-6-16)6.6.16 May 27, 2022 ### Fixed Issues

Issue

ID

Namespace is no longer missing from the body example.

W-11084386
## [](#6-6-15)6.6.15 May 19, 2022 ### Fixed Issues

Issue

ID

Request responses for images, SVG, and XML no longer cause an XSS vulnerability.

W-11031948
## [](#6-6-14)6.6.14 May 6, 2022 ### Fixed Issues

Issue

ID

When navigating to the method documentation, the console browser no longer displays an error.

W-10914362

To increase accessibility, this release adds alt text for icons in the request panel.

W-11083487
## [](#6-6-13)6.6.13 April 18, 2022 ### Fixed Issues

Issue

ID

The API server description no longer causes an XSS vulnerability.

W-10881270
## [](#6-6-12)6.6.12 April 7, 2022 ### Fixed Issues

Issue

ID

This release removes non-inclusive language.

W-10921614

XML name can now override type name.

W-10743611

OAuth 2.0 token request events now dispatch properly.

W-10749540

The properties of the data type datetime-only now display properly in the API specification documentation.

W-10928298

When the queryParameter value is 0, the parameter in the URL is no longer empty.

W-10839261
## [](#6-6-11)6.6.11 March 3, 2022 ### Fixed Issues The Code icon is no longer missing in the response example. ## [](#6-6-10)6.6.10 February 25, 2022 ### Fixed Issues - A long XML schema example is not duplicated. - Saving response does not generate an empty .HAR file. - Headers are reset when navigating to another operation without headers. - Adding a new custom header changes focus to the newly added field properly. \* Icon for saving .HAR response is no longer missing. - An array response collapse button displays properly. ## [](#6-6-9)6.6.9 January 28, 2022 ### What’s New - Added request body description to documentation. - Added test for overwriting `Content-Type` header with `multipart` body. - Added functional tests for flattened model. - Added test for sending request with a file attachment as body. ## [](#6-6-8)6.6.8 January 10, 2022 ### What’s New - Added documentation support for allOf types in OAS 3.0 APIs. - Added functional tests for responses. - Added functional tests for AsyncAPIs. - Added functional tests for OAS 3.0 APIs. - Set up visual tests to run as part of GitHub actions. ### Fixed Issues - The request panel renders correctly. - Multipart body has the correct type stored internally when initializing. - OAuth scopes renders correctly. ## [](#6-6-7)6.6.7 December 20, 2021 ### Fixed Issues - Populating credentials after removing a header does not throw an error. - Modifying a header does not clear the previous changes after populating credentials. ## [](#6-6-6)6.6.6 November 30, 2021 ### [](#new-features)New Features - Added documentation panel tests for security and types. - Added documentation panel tests for endpoints and methods. - Added request panel tests for query parameters. - Added basic visual tests. ### [](#fixed-issues-33)Fixed Issues - The anypoint-web-components that use an API are available in FF. - Request panel fields are updated after credentials population event. - Annotations display correctly in partial models. - Empty headers are not removed from request editor if body was present in request. - Headers are updated in the model when input is changed.\* Request with a file attachment in the body is sent. ## [](#6-6-5)6.6.5 October 19, 2021 ### [](#new-features-2)New Features - Increase timeout for request test (921794bf) - Authorization in request panel (ce15b4eb) - Request panel tests (07f9a5f3) - Increase timeout (d988c6f3) - Increase timeout (10e49c5b) - Basic documentation panel tests (76200b0e) ### [](#fixed-issues-34)Fixed Issues Use timeout to avoid using many nextframes. ## [](#6-6-4)6.6.4 September 24, 2021 ### [](#new-features-3)New Features - Added support for populating parameters with custom domain properties in the request editor through the `populate_annotated_fields` event. - Added multiple component tests to request panel (Headers & Body, Authorization) and documentation. ## [](#6-6-3)6.6.3 ### [](#new-features-4)New Features - Added `--api-responses-method-padding-left` and `--api-responses-method-padding-right` CSS variables. - Added listener for `securitysettingsinfochanged` to populate security settings fields in request panel. ### [](#fixed-issues-35)Fixed Issues - Fixed visual bug in code selector divider in responses documentation. - Fixed bug where summary would not clear when changing AMF model to a library. - Removed `force-resolutions` package to avoid sub-dependency clashes. ## [](#6-6-2)6.6.2 August 27, 2021 ### [](#new-features-5)New Features - Multiple new `data-` attributes across components enable testing. ### [](#fixed-issues-36)Fixed Issues - Request URLs include optional query parameters. - XML examples correctly render `application/xml` bodies. - Header autocomplete opens on focus. - Selecting the previously selected item closes the drop-down menu. - The newly added `force-resolutions` dependency resolves specific component versions in sub-dependencies. ## [](#6-6-1)6.6.1 August 11, 2021 ### [](#fixed-issues-37)Fixed Issues - `arc-response` renders responses correctly. ## [](#6-6-0)6.6.0 August 6, 2021 ### [](#new-features-6)New Features - The `persistCache` property prevents cache clearing in the request panel after an AMF property change. - API Console renders the description for named examples. ### [](#fixed-issues-38)Fixed Issues - API Console correctly generates and shows nullable properties examples. - XML generated examples consider a defined XML name. - The response time has the correct number of digits after the decimal place. - Scalar types show generated examples without duplication. ## [](#6-5-2)6.5.2 July 26, 2021 ### [](#new-features-7)New Features - Added `oneOf` types to the available types displayed in type documentation. - Added the option to disable required parameters in the request panel. ### [](#fixed-issues-39)Fixed Issues - Media type names in the selector display correctly. - The `Content-Type` header is sent in the request correctly. - Application authorization flow is processed correctly. ## [](#6-5-1)6.5.1 July 12, 2021 ### [](#fixed-issues-40)Fixed Issues - Fixed bug where request panel was allowing user to encode payload multiple times, creating a breaking payload in most cases - Fixed bug with rendering examples when wrapped property was set - Fixed bug where tabs in Code Examples would flicker endlessly - Fixed bug where decimal numbers would always show as invalid in input ## [](#6-5-0)6.5.0 June 25, 2021 ### [](#new-features-8)New Features - Added support for OAS 3 `deprecated` property - Added support for flattened AMF model - Added `renderFullPaths` property to render endpoints as their full paths, without indentation - `rearrangeEndpoints` now sorts endpoints alphabetically by path ### [](#fixed-issues-41)Fixed Issues - Fixed OAuth grant type issue for OAS 2 APIs - Fixed bug where navigating between some endpoints caused incorrect URI parameters to appear - Fixed bug in enum array properties where the enums where not being rendered - Fixed missing application/xml media types in body - Fixed API-asset showing incomplete description of JSON-schema ## [](#6-4-12)6.4.12 June 11, 2021 ### [](#fixed-issues-42)Fixed Issues - Add Optional Content Type for File upload Multipart - When "Query Parameters" or "Query Strings" is added, it is not displayed in "Try it" panel - Missing server description in summary - Change toggle button to checkbox for "enable/disable header" option and other minor correction ## [](#6-4-11)6.4.11 May 26, 2021 ### [](#fixed-issues-43)Fixed Issues - Arrows in responses tabs were not rendering correctly - Toggling optional parameters was changing the values of the parameters ## [](#6-4-10)6.4.10 May 14, 2021 ### [](#new-features-9)New Features - Convert multiline headers to single line when parsing ### [](#fixed-issues-44)Fixed Issues - It is not possible to add a new Field in the multipart-payload-editor, it gets removed after adding it - Missing "anyOf" details for types - Union type examples of arrays not displaying as arrays - The title of a property, defined as a union of arrays, appears as "undefined" - Array type title appears as "undefined" - Wrong title for a property defined as an array of numbers - Code example curl shows undefined - Use description from Parameter over schema if available - Query parameter input value can hardly be seen - Example section showing extra spaces - Tabs flicker in Code Examples ## [](#6-4-9)6.4.9 April 23, 2021 ### [](#new-features-10)New Features - Added multiple new CSS variables for further fine tuning of styling ### [](#fixed-issues-45)Fixed Issues - "Show optional parameters" has been re-added - When adding multiple headers with the same name, the first instance would not reflect the correct value of the header - Example names are now ignored if they match the media type + a numerical iteration (e.g. `application/json2`) - Hide type name for inline types (if the type name is `default`) - Mintor styling fixes ## [](#6-4-8)6.4.8 March 29, 2021 ### [](#fixed-issues-46)Fixed Issues - Fix `content-type` header not being sent in requests - Add warning messages to body form items in request - Fix styling for request panel subheaders - Fix warning messages spacing in query parameters ## [](#6-4-7)6.4.7 March 25, 2021 ### [](#fixed-issues-47)Fixed Issues - Missing examples for parameters, types and headers - When a query parameter is defined as optional, the checkbox "Show optional parameters" is not displayed - Content type not being set on requests - Font labels for URI parameters and Query parameter sections are large and labels are indented ## [](#6-4-6)6.4.6 March 25, 2021 ### [](#fixed-issues-48)Fixed Issues - Content type being sent when sending requests - Warning messages overlapping with multiple required headers - Header schemas are now copied from original AMF model ones when switching between source and form editors - Fixed version URI parameter being replaced with API version - Fixed example generation with tracked elements for partial models - Fixed autocomplete not closing when clicking outside of overlay - Fixed headers being added/removed incorrectly - Disable copy button when there are no headers ## [](#6-4-5)6.4.5 March 9, 2021 ### [](#new-features-11)New Features - For required fields that have no other restrictions, do not show as invalid. Instead, show an info message under the field - Added `noOverview` property to remove `Overview` items from navigation. If enabled, clicking on the endpoint name will select it, and the arrow will toggle the collapsible element - Added `operationsOpened` property to toggle all operations opened/closed - Added `credentialsSource` to optionally populate credentials in the request editor ### [](#fixed-issues-49)Fixed Issues - Server selection for slotted servers was not changing the request URL - Copy button in Headers is now disabled if there are no headers - Response headers are hidden until deliberately shown - Response body was not being formatted - Response body was not being rendered with error responses - Re-add CSS variable to style form titles in request panel, and fix indenting in the titles ## [](#6-3-7)6.3.7 February 22, 2021 ### [](#fixed-issues-50)Fixed Issues - Show message object schema in documentation view for `subscribe` operations ## [](#6-4-4)6.4.4 February 17, 2021 ### [](#fixed-issues-51)Fixed Issues - Message schema was not being shown in api-method-documentation view ## [](#6-4-3)6.4.3 February 5, 2021 ### [](#fixed-issues-52)Fixed Issues - Boundary missing when content-type is multipart ## [](#6-3-6)6.3.6 January 7, 2021 ### [](#new-features-12)New Features - Add PKCE OAuth flow in advanced settings in request panel. Enabled by default if declared in specificartion, can be enabled/disabled manually ### [](#fixed-issues-53)Fixed Issues - Fixed bug where the `Content-Type` header inferred from the payload was not being added in the Request Panel - Fixed bug where client\_secret was not being sent alongside thee rest of the information for the OAuth2 Password Grant - Fixed visual bug where channel and url were too compressed if channel was too long - `anyOf` in body payload now appears correctly - Changed an instance of "endpoints" to "channels" for AsyncAPIs - Do not prefix AsyncAPI url with `http` in summary view - Fixed operation label styling in summary and endpoint documentation views - Add styling to Publish and Subscribe operations in endpoint documentation ## [](#6-3-5)6.3.5 December 9, 2020 ### [](#fixed-issues-54)Fixed Issues - Fixed bug where changing the server would not immediately update the URL in the method documentation and endpoint documentation - Fixed bug where selecting Custom URI would make selector disappear if only one other server option was present ## [](#6-3-4)6.3.4 December 4, 2020 ### [](#fixed-issues-55)Fixed Issues - Bug UI bug where Summary and Endpoint views showed a small gray box where method would be - Fixed example generation bug for compact model where the value for a number would sometimes generate empty string instead of `0` ## [](#6-3-3)6.3.3 December 3, 2020 ### [](#fixed-issues-56)Fixed Issues - Fixed bug where endpoints with closely related named may cause one of them to appear blank in navigation - Fixed bug where multiple, fully expressed endpoints which could be nested, would appear blank - Fixed bug in URL handling where, if the url did not have examples for a query param, an error would be thrown and nothing would render ## [](#6-3-2)6.3.2 December 2, 2020 ### [](#new-features-13)New Features - `api-request-panel` does not return empty content if model does not belong to a WebAPI. This behavior is expected of whoever renders it - `api-console` and `api-console-app` check if AMF belongs to a non WebAPI, and hide the request panel & propagate the `noTryIt` accordingly ### [](#fixed-issues-57)Fixed Issues - Fixed bug where `baseUri` on `api-method-documentation` was not propagating the change to `api-url` ## [](#6-3-1)6.3.1 December 1, 2020 ### [](#fixed-issues-58)Fixed Issues - Fixed regression in `api-navigation` that caused an error to happen when the first endpoint in a specification had a URI parameter in it ## [](#6-3-0)6.3.0 November 30, 2020 ### [](#new-features-14)New Features - Annotation name is now rendered with the annotation - AsyncAPI 2.0 - Support for non HTTP protocols in documentation - `api-request-panel` is hidden when present model is from an AsyncAPI - `Endpoints` renamed to `Channels` - Operation URL is displayed differently for non-HTTP protocols - Example and snippets are hidden for non-HTTP protocols ### [](#fixed-issues-59)Fixed Issues - Required query parameters are now added to code snippets - Fixed bug with URL persisting after being removed from the spec - Fixed password grant type in Authorization where client secret was not being passed into the grant - Fixed bug where unordered endpoints would cause a endpoint path name to be shortened when it shouldn’t be - WCAG - Navigation collapse/expand was not being properly read by screen reader - Query parameters input box was not associated with any form label - Code Examples and Body collapse/expand were not being properly read by screen reader - Server selector dropdown was not properly associated with form label ## [](#6-2-6)6.2.6 September 28, 2020 ### [](#fixed-issues-60)Fixed Issues - Fixed bug example generation for partial models where some properties would not appear in rendered example if their values were empty strings, false boolean values or 0 integer values - Fixed bug in type documentation where enum array properties weren’t being rendered correctly - Fixed bug where the queryString node was defined on an operation, but the query parameters didn’t render in the try it panel - Fixed bug where XML example structures did not match the definition in the RAML type - Fixed bug where JSON schemas in RAML did not render completely ## [](#6-2-5)6.2.5 August 31, 2020 ### [](#new-features-15)New Features - New css variable for text wrapping for navigation items ### [](#fixed-issues-61)Fixed Issues - Changing RAML baseUri made query parameters section disappear - Duplicated examples in type documentation - Query string documentation was missing - Media types selector was missing when multiple media types defined in spec - Increase space between input and selectors and their labels - Table view was not displaying string examples - When setting no-auto-encoding annotation to URL elements, components were still being encoded ## [](#6-0-4)6.0.4 July 23, 2020 ### [](#fixed-issues-62)Fixed Issues - Client secret missing on request when authorizing for client\_credentials authorizationGrants ## [](#6-2-4)6.2.4 July 21, 2020 ### [](#new-features-16)New Features - Add rearrangeEndpoints property to api-documentation component, so it will be passed down to the api-summary if present - Pass down rearrangeEndpoints value to api-documentation as well ### [](#fixed-issues-63)Fixed Issues - Add scrolling to response codes in documentation to be able to see all possible response code options - Example generation for partial models now accounts for arrays with only 1 item appearing as a single object in partial model - Fix issue where documentation pages were listed in navigation with its description content rather than its title ## [](#6-2-3)6.2.3 July 7, 2020 ### [](#new-features-17)New Features - Implement oneOf, anyOf from OAS3 ### [](#fixed-issues-64)Fixed Issues - When a library is applied, documentation is blank for types - Server menu list width should fit dropdown width - URI in api-documentation and api-request-panel component does not update when servers in model change - Duplicate headers and headers from other methods shown in request panel - API Console do not understand readOnly fields when generating examples for OAS3 APIs - A property of type Object is rendered as a String - Library type documentation is blank - Missing response examples ## [](#6-0-3)6.0.3 June 25, 2020 ### [](#fixed-issues-65)Fixed Issues - Client Id and Client secret fields missing for client\_credentials authorizationGrants ## [](#6-2-2)6.2.2 June 12, 2020 ### [](#fixed-issues-66)Fixed Issues - XML example with missing "e" at the end - Response body type not rendering ## [](#6-2-1)6.2.1 May 27, 2020 ### [](#fixed-issues-67)Fixed Issues - Examples generation after AMF model changes - Auto selection of a custom server when no servers are defined in an API - Support for the partial AMF model when querying for servers - api-request event listener is now registered on the request panel instead of the eventsTarget - Duplicated content-type header on the request editor - XSS via authorization URI - Authorization method styling issue - Restored support for partial model when getting servers - Additional model support when computing servers - Operation and endpoint servers override base servers when switching to Try It panel - Fix display of enum values for array type document - Added OAS' external documentation support in the navigation ## [](#6-2-0)6.2.0 April 27, 2020 ### [](#new-features-18)New Features - OAS 3 support - Support for multi-server definitions - Custom servers - OAS multi-authorization - OAS links and callbacks - Support for `no-auto-encoding` annotation ## [](#6-1-1)6.1.1 March 31, 2020 ### [](#new-features-19)New Features - fixed issues with multiple security scheme names in the navigation by adding name of the scheme to the type - upgrading AMF processor helper to better support OAS 3 features and build background for OAS 3 full support - upgraded `lit-html` and `lit-element` libraries to the latest version - upgraded dev dependencies ## [](#6-0-1)6.0.1 February 6, 2020 ### [](#new-features-20)New Features - cleared dependencies - updated api-summary component with sanitization enabled for license URLs ## [](#6-0-0)6.0.0 January 16, 2020 ### [](#new-features-21)New Features - Upgrade to final web components specification: replacing HTML imports with JavaScript modules - Replacing Polymer with super lightweight, almost native, `LitElement`. This triggers a series of changes: - All dash-case attributes are now "no-dash", lowercase, web style attributes. For example old `redirect-uri` is now `redirecturi`. This is true for all properties used as HTML attribute. Properties names are the same. - New templating engine. API Console now uses `lit-html` which is performant HTML templating system. - Build process is completely different. See documentation at [https://docs.api-console.io](https://docs.api-console.io). - Redesigned base input controls. API console now uses own, material design based, basic UI input controls. It comes with 3 predefined styles: - Default - Material design filled style - Outlined - Material design outlined state controlled by `outlined` attribute - Anypoint - Compatibility layer with the Anypoint platform. Controlled by `compatibility` attribute - The request panel (aka try it) now only renders editors that corresponds to the API data model. This means that, for example, if headers are not defined for given operation then headers panel is not rendered. - Dropped support for tabs view for the editors in the request panel and they are stacked now. - Code mirror dependency requires some additional libraries that won’t work inside JavaScript module. This means that those libraries have to be included into the web application before initializing the element. See the documentation or readme file for details. - API Console is now WCAG compliant. All components used to build the console passed axe-core tests and therefore are fully accessible. - The application and the component are now split into separate components. Use `api-console` custom element for embedding the console inside existing web application and `api-console-app` to create stand alone application. - New demo pages. Preview the console with `npm start` command (run inside cloned repository) to see API console with various scenarios and configuration options. - Removed any reference to CSS mixins (the `@apply` function). All styling options are now defined via CSS variables. Any styles defined for previous version of API console won’t work. - Minimised use of icons in favour of regular buttons with labels. - This release contains tones of bug fixes and improvements reported by the community and our customers ❤ - The Chrome proxy extension banner is not rendered by default. Set `allowExtensionBanner` property to initialize the console with the extension support. - Added configuration option to set a static OAuth 2 client ID and secret for the application. This way it is easier to demo an API by providing demo client id. - Added markdown sanitization - Now XML schemas and examples are propertly rendered. - Huge XML schemas are now not syntax highlighted (above 10K characters) as it causes the browser to hang. - XML examples are now properly formatted and RAML type name is properly resolved (instead of `` element) ## [](#3-0-34)3.0.34 August 30, 2019 ### [](#new-features-22)New Features - New headers for mocking service requests ## [](#3-0-33)3.0.33 June 26, 2019 ### [](#fixed-issues-68)Fixed Issues - Various fixed issues. ## [](#5-0-2)5.0.2 May 29, 2019 ### [](#new-features-23)New Features - Updated AMF parser version and support for new model structure - Fixed examples rendering in the type documentation - Now type documentation renders generated JSON/XML schema when RAML’s `mediaTypes` / OAS' `produces` property is set - Examples now have default values for boolean, number, and null values when default value and example is missing ## [](#3-0-32)3.0.32 May 6, 2019 ### [](#new-features-24)New Features - Bump parser to version v1.1.50 ## [](#5-0-1)5.0.1 March 13, 2019 ### [](#fixed-issues-69)Fixed Issues - Fixed vulnerability issues. ## [](#6-0-0-preview-1)6.0.0-preview.1 March 1, 2019 ### [](#new-features-25)New Features - Preview of ES6 modules version of API Console. This is an early preview, not targeted for production. Try it and give us your feedback. ## [](#5-0-0)5.0.0 January 15, 2019 ### [](#new-features-26)New Features - Support for AMF data model instead of RAML parser allows to render a documentation for RAML and OAS specification and enables the console to read even more API types - Users can now define new properties (headers, query parameters) in the request editor that are not defined in the API spec. - API console now works with web components specification version 1. This allows to target all browsers with native support for web components spec and those with polyfill support. - Build process to create separate bundles for ES5 and ES6 enabled browsers so modern browsers can run the console with minimal required setup - Redesigned styling API to enable consumers to apply corporate theme using CSS variables - Build tools for the console now are based on AMF library to generate new data model - Redesign of the documentation part to deliver best in class documentation tool for APIs - Redesign of navigation for faster recognition of the API structure and to search for an endpoint - Added documentation for security schemes - Added code examples in the method documentation - Updated how union types are rendered - now it renders type name in the type selector instead of “Variant” ### [](#fixed-issues-70)Fixed Issues - Feedback from our customers and the open source community was applied to this version resolving tens of issues regarding performance, stability and design ## [](#5-0-0-rc-2)5.0.0-rc.2 January 12, 2019 ### [](#fixed-issues-71)Fixed Issues - Fixing CORS extension banner behavior. ## [](#5-0-0-rc-1)5.0.0-rc.1 January 11, 2019 ### [](#new-features-27)New Features - Support for AMF data model instead of RAML parser allows to render a documentation for RAML and OAS specification and enables the console to read even more API types - Users can now define new properties (headers, query parameters) in the request editor that are not defined in the API spec. - API console now works with web components specification version 1. This allows to target all browsers with native support for web components spec and those with polyfill support. - Build process to create separate bundles for ES5 and ES6 enabled browsers so modern browsers can run the console with minimal required setup - Redesigned styling API to enable consumers to apply corporate theme using CSS variables - Build tools for the console now are based on AMF library to generate new data model - Redesign of the documentation part to deliver best in class documentation tool for APIs - Redesign of navigation for faster recognition of the API structure and to search for an endpoint - Added documentation for security schemes - Added code examples in the method documentation - Updated how union types are rendered - now it renders type name in the type selector instead of “Variant” ### [](#fixed-issues-72)Fixed Issues - Feedback from our customers and the open source community was applied to this version resolving tens of issues regarding performance, stability and design ## [](#5-0-0-preview-3)5.0.0-preview.3 January 2, 2019 ### [](#new-features-28)New Features - Updated styles to enable theming - Added demo page with dark theme ## [](#5-0-0-preview-1)5.0.0-preview-1 October 31, 2018 ### [](#new-features-29)New Features - It is fully functional - Has working demo pages - Documentation for the HTML component - Documentation for building application - Build tools (which is the reason of creating the release) - Build documentation - Styling documentation ## [](#3-0-31)3.0.31 September 26, 2018 ### [](#new-features-30)New Features - Bump parser to version v1.1.48 ### [](#fixed-issues-73)Fixed Issues - Bug fixing ## [](#4-2-3)4.2.3 September 21, 2018 ### [](#fixed-issues-74)Fixed Issues - Forcing "marked" library update due to security vulnerability ## [](#4-2-2)4.2.2 September 20, 2018 ### [](#new-features-31)New Features - Updating dev dependencies - Bumping version - Removing silent bower installation - Updating tests configuration ### [](#fixed-issues-75)Fixed Issues - Fixing bower configuration ## [](#3-0-30)3.0.30 July 20, 2018 ### [](#new-features-32)New Features - Bump parser to version v1.1.45 ## [](#5-0-0-preview-0)5.0.0-preview-0 July 1, 2018 ### [](#new-features-33)New Features - It is fully functional - Has working demo pages - Build tools (which is the reason of creating the release) - Build documentation ## [](#3-0-29)3.0.29 June 7, 2018 ### [](#new-features-34)New Features - Bump parser to version v1.1.43 ## [](#3-0-28)3.0.28 May 10, 2018 ### [](#new-features-35)New Features - Bump parser to version v1.1.42 ## [](#3-0-27)3.0.27 April 21, 2018 This release includes the following enhancement and resolves a number of issues: ### [](#enhancements)Enhancements - Bumped RAML Parser to version to [1.1.41](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.41). ### [](#fixed-issues-76)Fixed Issues - Properties defined in the **items** facet were not displayed. - Values in optional headers were required to be specified. - Properties defined in response bodies for custom data types were not displayed in the console. - The error message “Cannot read property 'type' of undefined” appeared when a type was defined as an array and the array did not contain any elements. ## [](#3-0-26)3.0.26 February 24, 2018 This release includes the following enhancements and resolves a number of issues: ### [](#enhancements-2)Enhancements - Bumped RAML Parser to version to [1.1.40](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.40). - Because API Manager 1.x does not support digest authentication, the error message has been changed for Digest Authentication as follows: _Digest Authentication is not supported in Try it._ ### [](#fixed-issues-77)Fixed Issues - When including a data type, the invalid error in IE _Object doesn’t support property or method \`include\`_ appeared. - When selecting the Try It option, if the Request section is expanded and has the details, the Response section remained collapsed. - The problem declaring Arrays using defining items. - Partially blocked visibility of the tooltip for traits help. - A problem with the example defined for the query parameter. ## [](#3-0-25)3.0.25 January 13, 2018 This release resolves a number of issues. ### [](#resolved-issues)Resolved Issues - Fixed an issue that caused a missing description and examples when using a security scheme. - Body extending from a type defined at a library is now displayed correctly. - Fixed the issue that required you to scroll to the right to see an example having many attibutes. - Fixed the issue causing API Console to throw "Custom Security Schemes are not supported in Try It”. - Fixed an issue related to using inline !include in query param rendering. ## [](#3-0-21)3.0.21 November 4, 2017 This release introduces improvements and bug fixes. ### [](#improvements)Improvements Bump JS RAML Parser to [v1.1.31](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.31) ### [](#resolved-issues-2)Resolved Issues Display descriptions in sub-level resources. ## [](#3-0-20)3.0.20 August 26, 2017 This release focuses on a few RAML 1.0-related improvements and bug fixes. ### [](#resolved-issues-3)Resolved Issues - The description of types was not being displayed when defined using libraries. - Types were not displayed correctly at Types section. - Description of inner resources (those defined at sublevels) were not displayed. - API Console would not parse Raml files when using IE 11. - API Console was not rendered in IE. ### [](#improvements-2)Improvements Bumped RAML Parser to version to [1.1.29](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.29) ## [](#3-0-19)3.0.19 July 15, 2017 This release focuses on a few RAML 1.0-related improvements and bug fixes. ### [](#resolved-issues-4)Resolved Issues - Fixed an issue causing types defined in libraries to display incorrect information. - Fixed an issue preventing libraries from expanding and causing a display problem with the console library preview. ### [](#improvements-3)Improvements - Bumped RAML Parser to version [1.1.24](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.24). - Added support for the file type to the Try It view. ## [](#3-0-18)3.0.18 June 17, 2017 This release focuses on a few RAML 1.0 related improvements and bug fixes. ### [](#resolved-issues-5)Resolved Issues - Fixed an issue preventing the console from showing schemas that contain patterns that used `|`. - Fixed an issue preventing body parameters of type 'application/x-www-form-urlencoded' from being rendered in the Try It view. ### [](#improvements-4)Improvements - Bumped the RAML Parser to version [1.1.24](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.24) - Added showing the request URL in the Try It view even before you send out the request. ## [](#3-0-17)3.0.17 June 3, 2017 This release focuses on a few RAML 1.0 related improvements and bug fixes. ### [](#resolved-issues-6)Resolved Issues - API Console was not accurately displaying enum values defined in a library. - Arrays defined using type expression shortcut were not displayed correctly. - The order of query parameters and types properties were not preserved when navigating to a resource. - API Console was not showing DataTypes examples when using inheritance. - API Console returned an Invalid Type error inside the TryIt panel when using RAML 1.0 array types. - API Console renders example information twice. - Parameter examples were not shown when defined in a response. - The description and examples of Pass Through security scheme were missing from API console. - Validation of uriParameters failed when using a custom type. - API Console did not entirely show examples when provided in type definitions (either for the entire type or single properties). - Rendering issues occurred when a type extends from another type declaration. - A validation issue occurred when the type is a number and has a related enum. ### [](#improvements-5)Improvements - Bumped RAML Parser to version [1.1.20](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.20) - Enhanced performance when rendering large projects. ## [](#3-0-16)3.0.16 April 8, 2017 This release focuses on minor bug fixes. ### [](#resolved-issues-7)Resolved Issues - Fixed an issue preventing API documentation from being displayed at the Portal due to incorrect url resolution after library expansion. - Fixed an issue preventing error feedback from being displayed (white page or greyed page was displayed instead, depending on implementation). - Fixed an issue that prevented response type and examples from being refreshed accurately when changing methods. - Fixed an issue causing multiple inheritance types to be incompletely rendered in the method response. ### [](#improvements-6)Improvements - Bumped RAML Parser to version to [1.1.19](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.19) - Added an improvement for rendering the root description of an API on the top of the page. ## [](#3-0-14)3.0.14 March 11, 2017 This release includes a JS parser update. ### [](#improvements-7)Improvements Bumped JS parser version to [1.1.14](https://github.com/raml-org/raml-js-parser-2/releases/tag/1.1.14). ## [](#3-0-13)3.0.13 February 3, 2017 This release includes a JS parser update. ### [](#improvements-8)Improvements Bumped JS parser version to 1.1.13. ## [](#3-0-12)3.0.12 January 14, 2017 This release includes a JS parser update. ### [](#improvements-9)Improvements Bumped JS parser version to 1.1.12. ## [](#3-0-11)3.0.11 December 3, 2016 This release includes several fixes for rendering information as well as fixes for issues around RAML 1.0. ### [](#resolved-issues-8)Resolved Issues - Add support for Pass Through to reflect the complete set of security schemes defined in RAML 1.0. - In the previous version, the error output was not correctly handled and had to be updated. - Several other smaller bug fixes. ### [](#improvements-10)Improvements - Bumped JS parser version to 1.1.8. - Several other smaller improvements. ## [](#3-0-9)3.0.9 November 19, 2016 ### [](#improvements-11)Improvements Bumped JS parser version to 1.1.6. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # API Designer (Crowd) Release Notes These release notes cover the following versions of API Designer (Crowd): ## [](#2-83-200)2.83.200 **August 21, 2026** ### What’s New ### [](#user-interface-improvements)User Interface Improvements - The Documentation pane in API Designer now correctly displays operation labels for AsyncAPI specifications. - The API Documentation pane now correctly displays all properties from schemas that use `allOf` composition, including properties from deeply nested schema extensions. - Navigating directly to an API Designer project URL without an active session no longer redirects you to the Design Center home page. API Designer now opens the requested project after a successful sign-in. ### Fixed Issues
Issue Resolution ID

Design Center no longer displays an Authentication Required error when GitHub integration returns a 403 error due to an expired or revoked token.

W-23448410

When a branch merge fails, API Designer now displays an error instead of a false success message.

W-21683785

The project lock is now correctly released when a user exits API Designer through the Anypoint Platform navbar, closes the browser tab, reloads the page, or navigates away using the address bar.

W-21980033
## [](#2-79-0)2.79.0 **April 4, 2026** ### What’s New - You can now use **Go to Definition** and **Rename Symbol** actions reliably in API Designer. These actions no longer fail when working with OAS specifications. - You can now see a clearer error message when publishing to Exchange fails due to a mismatch between the `exchange.json` configuration and the authenticated user. The message now indicates that the `groupId` must match your organization UUID. - You can now see correct rendering of `nullable: true` fields in OAS 3.0 specifications in the API Documentation pane. These fields are now displayed as **Array or null**, and the original description is preserved. ### [](#improved-specification-validation-in-the-text-editor)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.10.0-0. ### Fixed Issues
Issue Resolution ID

Switching GitHub branches in Design Center no longer overwrites the local working copy when the authenticated user lacks the required repository permissions.

W-20037105

API Governance no longer sends error notifications when the API specification does not contain errors in API Designer.

W-19675036

The Governance validation progress bar in Design Center no longer remains stuck in the Validation in progress state after a validation failure.

W-20031294

Union types in RAML 1.0 DataType definitions that include arrays (for example, type: lib.user | nil) are now correctly rendered in the API Console documentation pane as Array or null instead of a generic union or single object.

W-19861175
## [](#2-76-0)2.76.0 **November 20, 2025** ### What’s New - API Designer now limits projects to a maximum of 100 dependencies. - API Designer now redirects users to the Design Center home page after deleting the current project. ### [](#improved-specification-validation-in-the-text-editor-2)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.9.1-3. ### Fixed Issues
Issue Resolution ID

OAS specifications are now rendered correctly in Design Center and Exchange.

W-17403032

RAML annotationType definitions are now rendered correctly at the method level.

W-16582426

Design Center now displays an error message when a branch merge fails.

W-17324282

The Examples Required ruleset no longer shows errors for URI parameters that already include examples.

W-15844364, W-16070725

API Console documentation pages are now displayed correctly when libraries with empty examples are referenced within a RAML project.

W-17902371

OAS component fragments can now be published to Exchange without triggering an invalid root file error.

W-18987255

The Design Center project filter now works correctly when project names contain spaces.

W-19304737

Validation errors in OAS specifications are now displayed at the correct line number.

W-17026937

The Download / Mule 4 Connector feature in Exchange now works correctly for multi-fragment OAS assets published from API Designer.

W-17421488

Validation no longer fails with a “RangeError: Maximum call stack size exceeded” message for specific RAML specifications.

W-16879247

Validation now correctly raises an error when a path parameter is referenced in an endpoint URI but not defined in the parameters section.

W-18252679, W-17776609

Nested references in external OAS fragments are now resolved correctly.

W-18018893, W-18034660

Documentation overview in API Console no longer disappears when using oneOf and defaultContentType in an AsyncAPI specification.

W-18010141

OAuth 2.0 security definitions now include the required flow field when converting a RAML API to OAS.

W-17981210, W-17495471

Missing items fields in array types are now correctly generated when converting RAML specifications to OAS 2.0.

W-18062983

The Parameters referenced in the path string must be defined error no longer appears when using the Anypoint Best Practices ruleset (v1.6.4).

W-17756973

The OperationRef object now supports escaped characters in JSON Pointer syntax when referencing paths in OAS specifications.

W-18556488

Design Center now displays a preview for RAML project files when opening the “View code” option from Exchange while not logged in.

W-19897297, W-20002392, W-20189489, W-20198464, W-20174392, W-20220656

RAML examples defined with YAML notation are now displayed without unwanted escape characters in the UI.

W-17290968, W-18189939

The Syntax error in the following text validation message no longer appears for valid OAS components.

W-17106459
## [](#2-75-2)2.75.2 **March 25, 2025** ### What’s New - API Designer and Design Center now enforce file type validation when importing files, allowing only supported formats. ## [](#2-75-1)2.75.1 **November 19, 2024** ### [](#improved-specification-validation-in-the-text-editor-3)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.6.3-0. ### Fixed Issues
Issue Resolution ID

OAS 3 Component fragment references are now resolved correctly.

W-16971126
## [](#2-75-0)2.75.0 **November 9, 2024** ### [](#autocompletion-improvements)Autocompletion Improvements - You now see `$ref` suggestions under user schemas on AsyncAPI 2.6 API Specifications. ### [](#improved-specification-validation-in-the-text-editor-4)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.6.3. - You can now use a Solace server without triggering warnings in the AsyncAPI Best Practices ruleset. ### Fixed Issues
Issue Resolution ID

You can now use required properties inside conditional fields on JSON Schemas correctly.

W-16798864

You now see the Validate for Governance button once the API model has finished loading.

W-15674453

You now see the displayName of a property shown corretly in the API Console

W-16683090
## [](#2-74-0)2.74.0 **October 12, 2024** ### What’s New - You can now search only valid characters when filtering API Projects. ### [](#new-features)New Features - This product has a refreshed UI. This new UI brings the product visually closer to the [new visual style of Salesforce](https://www.salesforce.com/blog/salesforce-cosmos-slds-2/) and enhances consistency, accessibility, and the user experience. Changes include a refreshed navigation, icons, and colors. Note: Some new features may not be available immediately as they are being activated progressively for clients. ### [](#improved-specification-validation-in-the-text-editor-5)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.6.2. ### [](#autocompletion-improvements-2)Autocompletion Improvements - You now see the `defaultContentType` field on the auto-complete suggestions on an AsyncAPI 2.6. ### Fixed Issues
Issue Resolution ID

API specifications published on Exchange through Studio now automatically get a git tag.

W-16808944
## [](#2-73-0)2.73.0 **September 28, 2024** ### What’s New - You can now see the dependencies and rulesets options button without having to expand the Dependencies panel. ## [](#2-72-1)2.72.1 **August 27, 2024** ### Fixed Issues
Issue Resolution ID

You can now share projects with a team without getting an Unable to update project permissions error.

W-16570967
## [](#2-72-0)2.72.0 **August 17, 2024** ### What’s New - Certain dependencies are updated to improve security when authorizing the GitHub Application. ### [](#improved-specification-validation-in-the-text-editor-6)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.5.4. ### Fixed Issues
Issue Resolution ID

You now see payload properties in the documentation pane in AsyncAPI JSON Specifications.

W-16254309

You now see the examples in the documentation pane when including RAML library data types in API Specifications.

W-14798477
## [](#2-71-0)2.71.0 **July 20, 2024** ### What’s New - You now see a 500 status code error when the dependency resolver fails. - You no longer see an error when selecting a Github project if you’re not synced to GitHub. You can open the project in read-only mode instead. ### [](#improved-specification-validation-in-the-text-editor-7)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.5.3. ### Fixed Issues
Issue Resolution ID

You no longer get a validation exception can’t resolve reference error message when validating a JSON schema fragment.

W-14796249
## [](#2-70-0)2.70.0 **June 24, 2024** ### What’s New - You now receive a notification if the project size is likely to affect performance. - You now see a login message when your session expires. Note: Some new features may not be available immediately as they are being activated progressively for clients. ### [](#new-features-2)New Features - API Designer now supports AsyncAPI 2.6. To learn about the AsyncAPI journey, see [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). ### [](#improved-specification-validation-in-the-text-editor-8)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.5.2. ## [](#2-69-0)2.69.0 **May 25, 2024** ### What’s New - You can now successfully see the Design Center project list after navigating through settings. ### [](#improved-specification-validation-in-the-text-editor-9)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.5.1. ### Fixed Issues
Issue Resolution ID

Exchange dependencies are now updated when you use / in a branch name.

W-15780320
## [](#2-68-1)2.68.1 **April 30, 2024** ### [](#improved-specification-validation-in-the-text-editor-10)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.5.0-0. ### Fixed Issues
Issue Resolution ID

You can now successfully publish API RAML fragments with multiple dependencies to Exchange.

W-14931067
## [](#2-68-0)2.68.0 **April 27, 2024** ### What’s New - You can now see text with links highlighted in the **Publish to Exchange** modal. - You can now click the version link on the **Publish to Exchange** modal to be successfully redirected to your asset. ### [](#improved-specification-validation-in-the-text-editor-11)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.5.0. ## [](#2-67-0)2.67.0 **April 6, 2024** ### What’s New ### [](#new-feature)New Feature - You can now select the project’s branch before opening your projects in Design Center. ### [](#improved-specification-validation-in-the-text-editor-12)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.4.9. ### Fixed Issues
Issue Resolution ID

You can now put spaces in the search bar of the Share project modal and get the correct results.

W-15191959

You now see the correct error message when referencing a non-existent response object in an API fragment.

W-15570769
## [](#2-66-0)2.66.0 **March 2, 2024** ### What’s New - Media types now show in alphabetical order in API Designer Visual mode. - The horizontal scroll bar is now hidden when there are no errors to show on the **Project Errors** panel. - You now need to enter a valid asset ID to publish an API specification to Exchange. ### [](#new-features-3)New Features - Validation of Governance rulesets is improved. If you enable manual validation mode, you now see a `No conformance issues to show after validation` message on the **Project Errors** panel after successful validation.+ If the validation fails, you can copy the details of the error to your clipboard to see the non-validating ruleset. ### Fixed Issues
Issue Resolution ID

You can now see examples in the API Console when defining nullable properties as true.

W-14855586

Now only the exchange_module folder and the exchange.json file re-fetch when importing a .zip file with dependencies to improve performance.

W-14616485 / W-14234271

Now only the exchange_module folder and the exchange.json file now re-fetch when adding, deleting, or changing a version with dependencies to improve performance.

W-14616485 / W-14234271

Files are now re-fetched after publishing specifications to Exchange to improve performance.

W-14616485 / W-14234271
## [](#2-65-0)2.65.0 **February 3, 2024** ### What’s New - You can now see the correct language badge tag on the `Rulesets` and `Import from Exchange` modals. - You can now use paste options on API Designer. - You can now scroll to see all your files on the `Replace file` modal. - The Filter by project name field now resets when switching organizations. ### Fixed Issues
Issue Resolution ID

You can now see examples in the API Console when defining nullable properties as true.

W-14249741

You can now see examples in the API Console when providing them under properties with XML attributes.

W-14615657

You can now see examples in the API console when defining payload properties on AsyncAPI specifications.

W-14572757

You now see an authentication required message when you don’t have permission to access a project or your session has expired.

W-14674994

Performance is improved on API specifications.

W-14557131 / W-14236380
## [](#2-64-0)2.64.0 **January 6, 2024** ### What’s New - Now, when switching between the **API Projects** and the **Shared with me** tabs on the Design Center home page, the project name input field resets. ## [](#2-63-0)2.63.0 **December 9, 2023** ### What’s New - You can now filter files by `.` or `+` characters. ### [](#new-features-4)New Features - Project owners and organization administrators can now transfer their ownership to a different organization member. For more information, see [Design Center Permissions.](https://docs.mulesoft.com/design-center/design-assigning-permissions) ### [](#improved-specification-validation-in-the-text-editor-13)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.4.5. - You can now narrow `int64` base types to `int62` base types without getting an `invalid type inheritance base type` error message. ### Fixed Issues
Issue Resolution ID

Your API now shows the correct header name when defining header parameters.

W-14438988

You can now see examples in the correct format when defining XSD schema examples.

W-12623953

You can now convert your API from OAS YAML to JSON without having some query parameters under the x-amf-queryParameters tag instead of under the parameters tag.

W-13976753

You can now see validation issues in the Publishing to Exchange modal when trying to publish an API.

W-14399162

You can now reference existing components in API Fragments without getting a cannot find parameter or payload reference error message.

W-14380118

You can now reference response types in Open API specifications without getting a cannot find response reference error message.

W-13759080

You can successfully access synced with Github projects with more than 30 branches.

W-14408711

You can successfully open RAML specifications without getting error messages.

W-14445080
## [](#2-62-0)2.62.0 **November 11, 2023** ### What’s New - You can now change the version of your dependencies without removing them from your project. - You can now delete one version of your dependency to remove all versions from your project. - The `project limit reached` dialog is improved to facilitate the use of assistant technologies such as screen readers. - You can now delete a project directly from the Design Center home page. ### [](#new-features-5)New Features - You can now disable auto-validation of Governance rulesets to run a single validation for each ruleset rather than triggering multiple automatic validations that can exhaust your resources. For more information, see [Improving Ruleset Validation](https://docs.mulesoft.com/design-center/design-add-api-dependency#fix-gov-issues). ### [](#autocompletion-improvements-3)Autocompletion Improvements - You now get suggestions for `!include` tags in RAML specifications and `$ref` properties in Async APIs. ### [](#improved-specification-validation-in-the-text-editor-14)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.4.4. - You now get a message specifying we don’t support XML 1.1 when referencing a XML 1.1 file. ### Fixed Issues
Issue Resolution ID

You can now publish complex API specifications without getting an error message.

W-14251387 / W-14216791

You can now successfully see the conformance issues of your projects.

W-14210545

You can now include XSD files as data-type for a request in an API specification without getting a schema document xsd cannot include itself error message.

W-14202641

You can now successfully publish to Exchange without delays.

W-14094069
## [](#2-61-0)2.61.0 **October 13, 2023** ### [](#improved-specification-validation-in-the-text-editor-15)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.4.3-0. ### Fixed Issues
Issue Resolution ID

The Security section of the API Console is not updated between endpoints.

W-14008660
## [](#2-60-0)2.60.0 **September 30, 2023** ### What’s New - API project `exchange.json` files are now displayed in pretty print format when you create new projects. ### [](#improved-specification-validation-in-the-text-editor-16)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.4.2-4. - You can now parse a union of three or more members that are not nested under a different union. ### Fixed Issues
Issue Resolution ID

You can now define child properties without having them display the mandatory fields of the parent property in the API Console.

W-13770031

You can now define reference a RAML library without getting a Resolution error: incompatible types [shape,shape] error message.

W-14109695

You can now publish RAML libraries without getting a should be integer should match some schema in anyOf error message.

W-14074325

You can now publish a RAML specification without getting a cyclic inheritance: id? → id? error message

W-14105863

You now see a Resolution error: invalid scalar inheritance base type error message when having an invalid RAML specification.

W-13217899
## [](#2-59-3)2.59.3 **September 1, 2023** ### Fixed Issues
Issue Resolution ID

You can now create connectors to use with Flow Designer and Anypoint Studio, and publish those to exchange, without getting an email with the Invalid scalar inheritance base type any cant override error message.

W-13794149

You can now define examples with union type properties without getting a Should NOT have additional properties…​ error message.

W-13820034
### [](#improved-specification-validation-in-the-text-editor-17)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.4.1-4. ## [](#2-59-0)2.59.0 **August 19, 2023** ### Fixed Issues
Issue Resolution ID

You can now use multiple Oauth 2.0 properties when parsing OAS 3.0 APIs without getting a scope not found error message.

W-13723448

You can now see the examples in the API console when defining multiple response examples.

W-13609146

You can now see query parameters defined as a union correctly listed in the API console.

W-13580768

You can now properly see error messages in the API console.

W-13260699
## [](#2-58-0)2.58.0 **July 22, 2023** ### Fixed Issues
Issue Resolution ID

You can now see XSD schema content types in the API Console.

W-13195361

You can now use oneOf properties without getting a specify the data model error message.

W-13062033

Performance improvements are implemented when validating large APIs before publishing to Exchange.

W-13280705
## [](#2-57-0)2.57.0 **June 24, 2023** ### Fixed Issues
Issue Resolution ID

You can now see a list of errors as soon as you add a new ruleset, or open a project with existent rulesets.

W-12707967
## [](#2-56-0)2.56.0 **May 29, 2023** ### What’s New - API Designer now supports new audit logs. For more information, see [Audit Logging](https://docs.mulesoft.com/jp/access-management/audit-logging). ### [](#improved-specification-validation-in-the-text-editor-18)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.3.0. - You now see the correct error message when using different formats for two examples of the same type. ### Fixed Issues
Issue Resolution ID

When the OAS API spec schema is not defined, it now defaults to HTTPS.

W-12592278

You now see the information typed in kafka bindings displayed on the API Console for AsyncAPI specifications.

W-12528269
## [](#2-55-0)2.55.0 **April 29, 2023** ### [](#improved-specification-validation-in-the-text-editor-19)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.2.6. - You now see an error message when using a JSON schema with `type inheritance` properties. ### Fixed Issues
Issue Resolution ID

You can now successfully generate an access token from the API Console.

W-12065711
## [](#2-54-0)2.54.0 **April 1, 2023** ### What’s New - You can now select API fragments with the same name when selecting API fragments in the Dependencies modal. - You are now redirected to the documentation page when clicking **Help with Sharing API projects** on the share dialog. ### [](#new-feature-2)New Feature - You can now disable the API Designer GitHub Integration. For more information, see [Disabling the GitHub Integration](https://docs.mulesoft.com/design-center/design-ghs-install-authorize#disabling-the-github-integration). ### [](#improved-specification-validation-in-the-text-editor-20)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.2.5. - You now see an error message when a RAML type is invalid. (For example, in `properties: products []` you now see `[] is not a valid type`) - Design Center now validates that the property type and the `discriminatorValue` field are the same. ### Fixed Issues
Issue resolution ID

You can now see exactly where the error is when validating union types with an empty array in a RAML 1.0 specification.

W-12513290

You can now see an error message in the API Console when building a request with a question mark as a header.

W-12371572

You can now properly publish a new version of an existing asset to exchange.

W-12359794
## [](#2-53-2)2.53.2 **March 20, 2023** ### What’s New - API Designer and Design Center fonts are updated to improve legibility, localization, and site performance. ## [](#2-53-0)2.53.0 **March 4, 2023** ### What’s New - You now get a confirmation message when removing a fragment from the Exchange Dependencies panel. - When you open an API specification created in Visual mode through the Exchange portal, it opens in the Visual editor as Read only mode. ### [](#improved-specification-validation-in-the-text-editor-21)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.2.4. ### Fixed Issues
Issue resolution ID

You no longer get an incorrect error when defining examples in parameters and headers. Note that the Required Examples version must be updated to 1.0.3.

W-12205009

You can now see where exactly the error is when defining examples in parameters and headers.

W-12059358

You can now see the correct information in the API Console when defining AnyOf properties.

W-12163469

You can now see all properties in the console when defining AllOf properties.

W-12138301

You can now see the correct information in the API Console when defining OneOf properties.

W-12080342

The API console now shows the endpoint details when opening an API fragment project.

W-12266057
## [](#2-52-0)2.52.0 **February 4, 2023** ### What’s New - You can now set the API version directly from the code when publishing API specifications in OAS 2 or OAS 3. - You can now edit the example area in Visual API Designer mode without losing your place on the page. - You can now use the **Chance access** button with the keyboard. ### [](#autocompletion-improvements-4)Autocompletion Improvements - When defining an `ExternalFragments` property in a OAS specification, it now links to the referenced node properly. ### [](#new-features-6)New Features - You can now create API Fragments in RAML, OAS 3.0, and JSON Schema format. For more information, see [Create and Publish an API Fragment in the Text Editor in API Designer](https://docs.mulesoft.com/design-center/design-create-publish-api-fragment)
Studio does not support OAS 3.0 fragments.
### [](#improved-specification-validation-in-the-text-editor-22)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.2.3. ### Fixed Issues
Issue resolution ID

You no longer get incorrect API conformance errors when defining the 204 status code in the response. Note that the Anypoint Best Practices version must be updated to 1.5.1

W-12447219
## [](#2-51-0)2.51.0 **January 21, 2023** ### What’s New ### [](#user-interface-improvements-2)User Interface Improvements - API Designer displays an error message when you publish an asset with invalid values in the `Business Group ID`, `Asset ID`, or `Asset name` fields in the Publishing to Exchange dialog. - You can now see the correct information when clicking the **Exchange** tab on the sidebar in the read-only asset page. - You can now use `control + F` to search for strings in a project with errors without crashing the browser. - The exchange tab is no longer visible when viewing code from Exchange. - The Design Center User Interface is updated for better accessibility. ### [](#new-features-7)New Features - New Design Center Business Group and Project Level permissions are added for more granularity when sharing projects. For more information see [Design Center Permissions.](https://docs.mulesoft.com/design-center/design-assigning-permissions) ### [](#improved-specification-validation-in-the-text-editor-23)Improved Specification Validation in the Text Editor - API Designer now supports the AML Modeling Framework (AMF) 5.2.2. ### Fixed Issues
Issue resolution ID

The example data field is now null in the API Designer documentation when a string property is defined with the nullable field set to true for an OAS 3.0 specification.

W-11323805

You can now use the < and > characters when defining an enum property without them being validated as XML characters for a RAML 1.0 specification.

W-12019663

The API console now shows the correct data when using the discriminator field in the definition of a JSON schema.

W-12039245

You can now convert a RAML 1.0 API specification to OAS 3.0 when defining a union type with null values.

W-12099989
## [](#2-50-1)2.50.1 **December 15, 2022** ### Fixed Issues
Fixed resolution ID

You can now open a published project from the Exchange portal with API Designer without getting an error message.

W-12040250, W-12218977, W-12284772
## [](#2-50-0)2.50.0 **December 10, 2022** ### What’s New ### [](#user-interface-improvements-3)User Interface Improvements - The user interface navigation is updated for better accessibility - You now get an error message when publishing an invalid asset in exchange. - You can now see a visual indicator of the keyboard focus when navigating through the visual editor mode. ### [](#improved-specification-validation-in-the-text-editor-24)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 5.2.1. ### Fixed Issues
Fixed resolution ID

You can now define a scope callback URL and have its value displayed in the Security tab of the Summary.

W-12003404
## [](#2-49-0)2.49.0 **November 12, 2022** ### What’s New ### [](#user-interface-improvements-4)User Interface Improvements - When creating an API Spec in the **Visual editor mode**, you can now successfully delete and add new content in the **Example** area of a data type. - You can now navigate through the **Filter** menu of a project with your keyboard. - You can now properly see the values defined for `enum` types in the **Query parameters** section in the summary page of the API documentation. - You can now successfully generate a request URL with a defined path parameter. ### [](#autocompletion-improvements-5)Autocompletion Improvements - When defining `AnnotationType` and `properties` in RAML, you no longer get incorrect suggestions. - When suggesting boolean fields in OAS2, you no longer get incorrect suggestions that add double quotes. ### [](#improved-specification-validation-in-the-text-editor-25)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 5.2.0. - You no longer get validation errors when defining additional properties. ### Fixed Issues
Fixed resolution ID

You can now succesfully preview DataType documentation when using minItems and maxItems properties in the Summary page of the API documentation.

W-11848788

You can now use a root $id on JSON schema documents without getting an error message.

W-11689045

Now, in the summary page of the API documentation, you see the object name as label instead of the properties value added in the request panel.

W-11866516
## [](#2-48-5)2.48.5 **October 29, 2022** ### [](#new-features-8)New Features - Added a security layer to the API console, so that only registered domains are reachable. For more information, see the [Allowlisting Trusted Domains documentation.](https://docs.mulesoft.com/jp/access-management/allowlisting-trusted-domains) - You now get an email notification when your API fails conformance to rulesets your organizations validates. For more information, see the [Adding Dependencies to an API-Specification Project documentation.](https://docs.mulesoft.com/design-center/design-add-api-dependency) ### Fixed Issues
Issue ID

When publishing an API specification from API Designer to Exchange, the version field is now pre-populated according to what you define in the API spec. For more information, see the Publishing API Specifications documentation.

W-11705888
## [](#2-48-0)2.48.0 **October 15, 2022** ### What’s New ### [](#user-interface-improvements-5)User Interface Improvements - You can now edit the **API Version** field when publishing a project to exchange. - The Publish button is updated for better accessibility, and a new **Exchange** tab is added to the sidebar. - You can now use special characters when renaming branches on projects synced to GitHub. - You can now have multiple response status codes on API Visual Designer. ### [](#improved-specification-validation-in-the-text-editor-26)Improved Specification Validation in the Text Editor - API Designer now supports AML Modeling Framework (AMF) version 5.1.0. ### Fixed Issues
Issue ID

You can now successfully preview documentation for DataType fragment files.

W-11649355

You no longer get incorrect API Governance conformance errors when adding an API fragment as a dependency.

W-11587420

You can now successfully refer to API fragments without getting conformance errors.

W-11460246

You can now properly use the oneOf property to define two different messages for AsyncAPIs documentation.

W-11091661
## [](#2-47-0)2.47.0 **September 13, 2022** ### What’s New ### [](#user-interface-improvements-6)User Interface Improvements - When defining multiple keys in an OAS 3 spec, they now show the correct documentation and labels associated with those fields. - When entering the Try It panel, the Client ID field no longer shows an error message, and the warning messages are fully and correctly displayed - You can now click on **Clone**, **Edit**, and **Delete** using assistant technologies. - You can now see a visual indicator of the keyboard focus when navigating through API Specification fragments. - You can now enter values for query parameters without losing focus. - You can now extract the body of your project to a new data type without getting an error message. - You can now navigate through UI elements with the keyboard. ### [](#autocompletion-improvements-6)Autocompletion Improvements - When using the `securedBy` and `SecuredByCompletionPlugin` fields with RAML files, you no longer get incorrect suggestions. - When using API annotations that generate a YAML Map, you will now be suggested to include a break line at the end instead of an empty space. ### Fixed Issues
Issue ID

The customer header is now displayed correctly when enabled.

W-11407528

You now get an error message when creating invalid RAML (union types with enums) definitions.

W-11381880

When designing an API specification using OAS 3.0, you no longer get a duplicated resource path error message.

W-11295643
## [](#2-46-0)2.46.0 **August 20, 2022** ### What’s New ### [](#user-interface-improvements-7)User Interface Improvements - You can now navigate through the Exchange Dependencies panel using assistant technologies such as screen readers. - When clicking **View Code** on a published exchange asset related to a no longer existing branch, you no longer receive an error message. - When clicking **View Code** on a published exchange asset, you no longer receive an error message. - When renaming your branches with a `$` character, you no longer receive an error message. - When renaming or cloning a project, you now need to enter a name before confirming. - Design Center now includes links to our Github Synchronization documentation page. - You now have more granularity in API Designer permissions. ### [](#new-features-9)New Features - All user interface components have been updated to APID Components v3. ### Fixed Issues
Issue ID

You can now click Authorize to successfully connect your Github account with Design Center.

W-11585264

You can now use API Governance rules without getting an error message.

W-11225118

Namespaces and tags are now successfully displayed when added on examples for content-type application/XML schema.

W-11077505

The Datagraph Admin permission can’t be used to download Design Center projects anymore.

W-11253041
## [](#2-45-0)2.45.0 **July 23, 2022** ### What’s New ### [](#user-interface-improvements-8)User Interface Improvements - The user interface navigation is updated for better accessibility. ### [](#autocompletion-improvements-7)Autocompletion Improvements - You can now see suggestions under the `uses` property in a library fragment when defining data type properties in RAML Data Type fragments files. ### [](#improved-specification-validation-in-the-text-editor-27)Improved Specification Validation in the Text Editor - API Designer now supports AML Modeling Framework (AMF) version 5.0.10. - When you use `$ref` in OAS Parameter Specifications, you no longer receive an error message. ### Fixed Issues
Issue ID

You can now edit a branch from exchange without having its content overwritten with other branches.

W-11378789

You can now successfully filter by Project Type.

W-11429747

You can now define the root file for Async projects imported from Github.

W-11279542

API designer now successfully deletes a branch after a merge.

W-11253255

API designer now creates the correct documentation for an AsyncAPI when using multiple messages.

W-11091661

Governance conformance issues are no longer shown in the Functional tab.

W-11316515

When you view code from Exchange in the text editor, you no longer receive a 'No zip file for gav' error.

W-11316441
## [](#2-44-0)2.44.0 **June 25, 2022** ### What’s New ### [](#user-interface-improvements-9)User Interface Improvements - When using the expander toggle (`>`) on the Errors panel, you now expand the item you selected instead of multiple items. - When you click **Cancel** on a create dialog, you no longer receive an error message. - You can now navigate through create menus without losing focus. ### [](#new-features-10)New Features - GitHub Synchronization is a version control tool that maintains API specifications existing in several locations. Use GitHub Synchronization to enable two-way synchronization between API Designer and your GitHub repository. For more information, see the [Github Synchronization documentation](https://docs.mulesoft.com/design-center/design-ghs-about-github-sync). - You can now re-name the main branch in adherence to our Inclusive Product Language Program. ### [](#autocompletion-improvements-8)Autocompletion Improvements - You can now see suggestions when defining data type properties in RAML Data Type fragments files. ### [](#improved-specification-validation-in-the-text-editor-28)Improved Specification Validation in the Text Editor - API Designer now supports AML Modeling Framework (AMF) version 5.0.9. - All AML Dialect JSON Schema `integer` types are now converted into `long` types to support larger numbers. ### Fixed Issues
Issue ID

You can now add a new response on a resource instead of replacing the existing one while using the visual editor.

W-11262351
## [](#2-43-0)2.43.0 **May 28, 2022** ### What’s New ### [](#user-interface-improvements-10)User Interface Improvements - User interface terminology and navigation have been updated for better accessibility. - The text editor sidebar and editor shelf expander toggles (`>` and `<`) are no longer overlapped with other elements. - When you view code from Exchange in the text editor, you no longer receive a 'No zip file for gav' error. - The visual editor UI now validates the resource name field and disallows entry of invalid characters such as double quotes ("), carat (^), and percent (%). - You can now successfully import an example from the visual editor. ### [](#improved-specification-validation-in-the-text-editor-29)Improved Specification Validation in the Text Editor - API Designer now supports AML Modeling Framework (AMF) version 5.0.8. - In OAS3 APIs with references to endpoints that have references to schemas, second-level references with valid paths are resolved properly. - When you convert a RAML API to OAS 2.0 and `mediaType` is defined for an endpoint, the text editor uses the endpoint’s `mediaType` rather than the default. ### Fixed Issues
Issue ID

API Designer now properly renders markdown files in the documentation view.

W-10647692

The mocking service now properly renders examples and schemas in OAS 3.0 APIs when you use allOf or oneOf properties.

W-10888940

The error that the schema must not import, include, or redefine itself no longer occurs when you import RAML API specifications.

W-10685149
## [](#2-42-0)2.42.0 **April 30, 2022** ### What’s New ### [](#api-governance-support)API Governance Support - A new ruleset dependency type is introduced in this release to enable you to validate your API specifications against rulesets cataloged in Exchange. For more information, see the [API Governance documentation](https://docs.mulesoft.com/api-governance/). ### [](#user-interface-improvements-11)User Interface Improvements - The visual editor UI refresh rate has been improved. ### [](#improved-specification-validation-in-the-text-editor-30)Improved Specification Validation in the Text Editor - API Designer now supports AML Modeling Framework (AMF) version 5.0.6. - When you declare a security scheme in a RAML library, use it in an API specification, and then convert the RAML specification to OAS, the OAS specification is now generated with valid security scheme information. - When you define both date and pattern formats for OAS types, API Designer shows a warning that the pattern property might be ignored if the date format already defines a standard pattern. ### Fixed Issues
Issue ID

The property of data type datetime-only now shows properly as DateTime in the API specification documentation in API Designer and in Exchange.

W-10899011
### [](#known-limitations-and-workarounds)Known Limitations and Workarounds Due to an enhancement in the way absolute paths are parsed, if you apply a governance ruleset dependency to a project in API Designer, absolute file paths are no longer allowed in fragment dependencies for that project. If this enhancement impacts your project, you can either update and republish the fragments or switch back to the prior behavior and opt not to apply rulesets to that project. ## [](#2-41-0)2.41.0 **April 2, 2022** ### What’s New ### [](#improved-specification-validation-in-the-text-editor-31)Improved Specification Validation in the Text Editor - Boolean schemas are now parsed for JSON schema draft-06. - Security scheme fragments with media type defined at the global level are now validated properly. ### [](#autocompletion-improvements-9)Autocompletion Improvements - Code suggestions are now properly shown for OAS 3.0 specifications that use `externalDocs` regardless of the position of the cursor. - The hover text is now properly shown for OAS 3.0 specifications that use `externalDocs`. ### Fixed Issues
Issue ID

The file import now properly validates file names regardless of how the files are imported.

SE-24042
## [](#2-40-0)2.40.0 **March 5, 2022** ### What’s New You can now select lifecycle states when publishing API specifications to Exchange. For more information, see [Publish an API Specification](https://docs.mulesoft.com/design-center/design-publish). ### [](#improved-specification-validation-in-the-text-editor-32)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 5.0.4. - AMF parser validations no longer show duplicate examples for error codes. ## [](#2-39-0)2.39.0 **February 5, 2022** ### Fixed Issues
Issue ID

Tests of OAS v3 endpoints can now be executed.

SE-23274

When errors are found in included files, the editor now indicates errors in the root file as well as in the included files.

DESIGNER-7123
## [](#2-38-0)2.38.0 **January 8, 2022** ### [](#improved-specification-validation-in-the-text-editor-33)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 5.0.2. - OAS 3.0 specification properties with nullable fields set to `true` are now correctly validated when sent in payloads. ### Fixed Issues
Issue ID

The exclusiveMinimum and exclusiveMaximum properties are now numeric values in JSON schema versions draft-06 and draft-07.

SE-23167

In the visual editor, selecting an Array data type now shows two separate sections: Array Fields and Items.

The Items section displays fields corresponding to the selected Items type, for example: Object, Boolean, or DataType.

DESIGNER-2821

In the visual editor, a union data type is now correctly rendered after saving changes and then reloading a project.

DESIGNER-4705
### [](#autocompletion-improvements-10)Autocompletion Improvements - In OAS 3.0 specifications, 'responses' node autocomplete suggestions no longer include the `New Response` option. - In RAML 1.0 specifications, autocomplete suggestions now correctly show for objects inside `array` types. - In RAML 1.0 specifications, autocomplete now correctly shows prefix suggestions. - In RAML 1.0 specifications, autocomplete no longer suggests duplicates for `resourceTypes` and `traits`. ## [](#2-37-0)2.37.0 **December 11, 2021** ### [](#improved-specification-validation-in-the-text-editor-34)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 5.0.1. - AMF parser validations no longer incorrectly highlight the origin of the document. Validations now highlight the correct line of the validated shape or fragment. ### Fixed Issues
Issue ID

External schemas referenced in an API specification no longer introduce unexpected <schema> tags in generated XML.

SE-22292

Selected resources and methods now correctly show in the Description field in the visual editor.

SE-22991

URI parameter data types imported from libraries no longer return validation errors.

SE-23076

When using Mozilla Firefox, the client_id and client_secret headers now correctly display in API Console.

SE-23195
## [](#2-36-0)2.36.0 **November 13, 2021** ### [](#user-interface-improvements-12)User Interface Improvements - When you initiate the import of a ZIP file but do not choose a file, the **Import** button is no longer enabled. - The tooltip for a deprecated dependency is now displayed correctly. ### [](#improved-specification-validation-in-the-text-editor-35)Improved Specification Validation in the Text Editor API Designer now provides support for AML Modeling Framework (AMF) 5.0.0. ### Fixed Issues
Issue ID

When a branch is changed externally and you click Discard and Use New Changes, the window no longer remains open with the Updating message.

DESIGNER-6835

API Designer now supports relative references from one XSD schema to another. If you create an API specification that contains an XSD schema that references another XSD schema, the import no longer fails with the warning Could not validate XSD schema: Resource /{anotherSchema}.xsd not found.

For example, you can now include an import line such as <xs:import namespace="http://www.wincor-nixdorf.com" schemaLocation="WNExtensions.xsd"/> in another XSD schema, such as POSLog.xsd.

SE-22684
## [](#2-35-0)2.35.0 **October 16, 2021** ### [](#new-feature-3)New Feature - You can now create, import, and edit AsyncAPI specifications in API Designer. See [Event-Driven API (AsyncAPI) Support Release Notes](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api). ### [](#improved-specification-validation-in-the-text-editor-36)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.8. - Inheriting from array types no longer results in an `Incompatible types [array, array]` validation error. - Including a disjoint `UnionShape` within the `examples` node of a schema no longer results in an `expected type: X, found: Y` error. ### Fixed Issues
Issue ID

The Publish to Exchange dialog now prevents publishing a project with an invalid root file name.

DESIGNER-6885

API Designer now enforces a 50MB limit when performing an Import from File.

DESIGNER-6900

AMF now correctly validates arrays of types in JSON schemas.

SE-22204
## [](#2-34-2)2.34.2 **September 30, 2021** ### Fixed Issues
Issue ID

Publishing to Exchange while the root file resides in a folder no longer results in the following error:

Cannot publish with invalid root file name

SE-22876
## [](#2-34-1)2.34.1 **September 27, 2021** ### Fixed Issues
Issue ID

API Designer no longer repeatedly displays the following when creating or switching branches:

This branch has changed externally

SE-22744
## [](#2-34-0)2.34.0 **September 18, 2021** ### [](#improved-specification-validation-in-the-text-editor-37)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.7. - The `union` and `nil` types are now parsed with equivalence. - Validation no longer fails for required facets in properties containing the `nillable` shorthand type. For example, the following code no longer results in `Error: Property 'required' not supported in a RAML 1.0 string node`: #%RAML 1.0 title: APIMF-2975 types: Test: properties: name: required: false type: string? - AMF now saves properties declared in `required` but not present in `properties`. For example, the following code no longer results in an ignored `address` property: { "$schema": "http://json-schema.org/draft-04/schema#", "type" : "object", "properties": { "name": {"type": "string"}, "age": {"type": "integer"} }, "additionalProperties": false, "required": \[ "address" \] } ### [](#autocompletion-improvements-11)Autocompletion Improvements - Inner document path suggestions no longer contain a trailing slash. ### Fixed Issues
Issue ID

API Designer no longer incorrectly validates empty oneOf schemas that contain the required keyword.

SE-21827, SE-21981, SE-22242

Content is no longer deleted after changing a file extension (via the Rename option) within the text editor.

DESIGNER-6664

Importing files with names containing invalid characters (such as ,) is now correctly allowed.

DESIGNER-6667
## [](#2-33-0)2.33.0 **August 21, 2021** ### [](#improved-specification-validation-in-the-text-editor-38)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.6. - RAML 1.0 definitions containing duplicate property names were incorrectly validated. For example, the following definition did not result in an error: #%RAML 1.0 title: test-example version: v1 types: failing: type: object properties: duplicate: string duplicate?: string example: duplicate: "hello error" An error is now displayed: ```none Error: Duplicated property names: duplicate ``` ### [](#autocompletion-improvements-12)Autocompletion Improvements - Autocompletion in OAS specifications containing `parameters` tags now suggests "info" (instead of "in") for root nodes. - Autocompletion in OAS specifications is now correct for `version` tags when subsequent text exists. ### [](#fixed-issues-49)Fixed Issues - The time to open the **Publish to Exchange** dialog is improved for projects containing several files and dependencies. - The XML 'name' property was ignored in the example XML payload generated via API Console. - Opening a project occasionally resulted in a non-completing `Loading…​` message. The browser console displayed the following error: ```none Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope' ``` - When publishing assets to Exchange takes more than 1 minute, the following message is now displayed: ```none Error publishing to Exchange: Request timed out due to project size. Asset may have been successfully published. Please verify in Exchange. ``` Previously, `unknown error` was returned. - Options were not rendered in API Console for schema properties containing the `oneOf` keyword. - RAML 1.0 inline unions in extensions now parse correctly. For example, given the following specification and extension: #%RAML 1.0 title: example API to be extended types: TestObject: type: object /test: get: responses: 200: body: application/json: type: TestObject #%RAML 1.0 Extension extends: /api.raml types: TestObject: properties: unionDate: datetime-only|nil example: unionDate: null /test: get: responses: 200: body: application/json: type: TestObject The `unionDate` property parsed as the first declared type (in this case a `datetime-only`). However, given the inverse union, only nil values were validated. This resulted in an error: ```none Error: 'unionDate' should be string 'unionDate' should match some schema in anyOf ``` - Adding an enum property to an extension resulted in duplicate values in API Console. - When trying to use the same library defined in an API specification more than once, the following error was returned: ```none Error: Libraries must be applied by using 'uses' ``` ## [](#2-32-0)2.32.0 **July 24, 2021** ### [](#improved-specification-validation-in-the-text-editor-39)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.5. - OAS 2.0 security scheme definitions that do not contain `name` and `in` required fields now result in warnings: ```none Warning: Property 'in' is required in a OAS 2.0 apiKey node Warning: Property 'name' is required in a OAS 2.0 apiKey node ``` ### [](#autocompletion-improvements-13)Autocompletion Improvements - Autocompletion now displays correct options for `example` nodes that include example fragment files. - Autocompletion now displays correct RAML method names for endpoint name nodes. ### [](#fixed-issues-50)Fixed Issues - Enum values declared in an array type were not displayed in the **Documentation** panel. - When publishing to Exchange, API projects with a large number of files intermittently resulted in the following HTTP 502 timeout error response: ```none Error publishing to Exchange: Unknown error ``` - In API Console, selecting a body content type of `application/xml` created an invalid payload. The following error was displayed: ```none 400 Bad Request ``` - It was not possible to scroll through large amounts of Exchange dependencies. - API Console displayed a validation error when entering fractional numbers as query parameters. ## [](#2-31-0)2.31.0 **June 26, 2021** ### [](#improved-specification-validation-in-the-text-editor-40)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.4. - The RAML datetime-only validator now returns an error for years with over four digits. For example, previously `"effectiveDate": "22021-06-05T00:00:00"` would not return an error. It now returns a `400 Bad Request` error. ### [](#autocompletion-improvements-14)Autocompletion Improvements Autocompletion now: - Does not suggest incorrect options within a type definition when defining facets. - Does not suggest in-use options. - Suggests only `description` for the description field of a parameter. - Provides suggestions if a colon is after your cursor. ### [](#fixed-issues-51)Fixed Issues - API Language Server (ALS) would not return an error payload for a Serialization request while a workspace was still initializing. ALS now returns an error payload if the Serialization request can’t be validated. - API server descriptions are now present in the **Documentation** pane with their servers. ## [](#2-30-0)2.30.0 **June 8, 2021** ### [](#improved-specification-validation-in-the-text-editor-41)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.3-1. - Invalid discriminator mapping values now result in a warning. For example, the `invalid` value in the last line of the following snippet results in `Warning: Unresolved reference 'null'`. openapi: "3.0.0" info: version: 1.0.0 title: 1-api paths: {} components: schemas: Dog: type: string Cat: type: string Animal: oneOf: - $ref: '#/components/schemas/Dog' - $ref: '#/components/schemas/Cat' discriminator: propertyName: petType mapping: invalid: 'null' - In RAML 0.8, specifying a relative reference (for example, `!include common/400.example`) instead of the intended absolute reference (for example, `!include /common/400.example`) results in an error: ```none Error: Resource common/400.example not found ``` - The parser now resolves spaces in values with `!include` tags, such as the following: title: !include /title file.yaml ### [](#fixed-issues-52)Fixed Issues - Schemas with `schemaLocation` values containing `.xsd` files resulted in the following incorrect warnings: ```none Unreferenced file: This file is not referenced by the root file ``` - Incorrect strings replaced the response section title in the **Responses** section. The title text is now displayed as **Example** in all cases. - OAS specification 'description' and 'example' values did not display in the **Documentation** section. - Mocking service requests did not successfully complete due to certain missing JSON headers. - API Console did not display the correct property type for arrays declared with the `[]` qualifier (for example, `string[]`). - API Console did not display the correct information for schema definitions containing the `anyOf` keyword, such as in the following snippet: "companyType": { "anyOf": \[ { "type": "string", "maxLength": 10, "description": "The legal name of the given company.", "enum": \[ "EU" \] }, { "type": "string", "description": "Any future added type", "maxLength": 10 } \] } }, The **Documentation** section incorrectly displayed the following: ```none item.companyType Any ``` ## [](#2-29-0)2.29.0 **May 1, 2021** ### [](#improved-specification-validation-in-the-text-editor-42)Improved Specification Validation in the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.2. - RAML nillable shorthand `string?` types were not recognized in `uriParameters`, `queryParameters`, or `headers` maps. The following error was displayed: ```none Cannot declare unresolved parameter ``` ### [](#fixed-issues-53)Fixed Issues - Previously published Exchange dependencies failed to load in API Designer when importing an API specification or fragment and creating branches containing `/` (for example, `features/mybranch`). - For some projects in the project list, the `Created By` field displayed UUIDs instead of names. - The mocking service returned an `Invalid Schema` error after correcting `ref` paths in an `.xsd` schema file. ## [](#2-28-0)2.28.0 **April 3, 2021** ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor)Improvements in the Validation of Specifications by the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) 4.7.1., which improves validation of object payloads inside enums. For example, the following RAML defines two types (`AnimalWithPaws` and `AnimalWithHoofs`), and a union of these two types called `Animal`: #%RAML 1.0 title: Some API types: AnimalWithPaws: properties: name: string pawsCount: number AnimalWithHoofs: properties: name: string hoofsCount: number Animal: type: AnimalWithPaws | AnimalWithHoofs enum: - name: Cat pawsCount: 4 - name: Horse hoofsCount: 4 The type `Animal` is now considered valid. ### [](#fixed-issues-54)Fixed Issues - By design, the visual editor will not add the URI parameter (for example, `bookId`) to the resource name (for example, `/book`). The following message now displays, advising you to add the parameter: Please add it to the resource name input as needed, e.g /book{bookId} - From the visual editor, the following error was returned after selecting the **Access token (browser flow)** grant type and attempting to authorize an OAuth access token: Cannot GET /node\_modules/@advanced-rest-client/oauth-authorization/oauth-popup.html - In the text editor, renaming an array type with the **Rename Symbol** action resulted in a non-array type name. For example, renaming `person[]` to `user` in the following RAML resulted in a new symbol named `user` instead of `user[]`. #%RAML 1.0 title: My API with Types "person" types: person: description: this is person's description properties: firstname: string manager: type: string Alertable: manager | person /person: get: responses: 200: body: application/json: type: person\[\] example: | \[{ "firstname": "person" }\] /person/{manager}: post: body: application/json: - In the text editor, autocomplete incorrectly suggested the `responses` tag after entering "r". The error occurred when typing under the `queryParameters:` node. ## [](#2-27-0)2.27.0 **March 6, 2021** ### [](#new-features-11)New Features - The API Designer text editor now supports the following actions: - Find locations where a definition is referenced. - Select code ranges. - Navigate to a symbol. - Extract an element to a declaration. For more information, see [Helpful Features in the Text Editor](https://docs.mulesoft.com/design-center/design-helpful-features-text-editor). - The AML Modeling Framework (AMF) parser is now version 4.7.0. ### [](#fixed-issues-55)Fixed Issues - OAS 3.0 code generated when switching from the visual editor to the text editor was invalid and could not be published to Exchange. For example, under **API Summary** in the visual editor, specifying `application/json` and switching to the text editor resulted in the following invalid code: "produces": \[ "application/json" \], The following error was reported: Error: Property 'produces' not supported in a OAS 3.0 webApi node - Publishing an asset to Exchange and then deleting the project resulted in the option to edit the specification from Exchange. Selecting **Edit spec** resulted in the following error: Project not found The **Edit spec** option no longer displays in **READ ONLY VIEW** if the project was previously deleted in Design Center. - Previously you could create a file with the reserved name, `exchange.json`. - Importing a ZIP file with a file named `exchange.json` located in a folder other than the reserved `exchange_modules` folder resulted in two added files named `exchange.json`. Now, the duplicate file is ignored and not imported. ### [](#known-issues)Known Issues - The **Documentation** panel displays an incorrect `type: number` value if the value is 16 digits or larger. For example, the following snippet contains a `type: number` value that is 16 digits: 16digits: type: number maximum: 9999999999999999 Design Center incorrectly displays `Max value: 10000000000000000`. The current type system does not support the required precision. ## [](#2-26-0)2.26.0 **February 6, 2021** ### [](#fixed-issues-56)Fixed Issues - OAS 3.0 specifications with `nullable` fields generated unexpected `anyOf` keys when converted to RAML 1.0 specifications. - When using the **Import from File** option, importing a Mac-compressed ZIP file incorrectly added a reserved folder `__MACOSX` to the project. - When using the **Import from File** option with a ZIP file containing a single folder at root level (with the API specification content inside), the root level folder was not removed and was incorrectly imported into the created project. Now the root level folder is removed and its content is imported into the root folder of the new project. - When sorting projects by **Name**, **Project Type** or **Last Update**, the projects disappeared from the view. - After publishing a project via **Publish to Exchange**, the code suggestions were not displayed in the text editor. ## [](#2-25-0)2.25.0 **January 7, 2021** ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-2)Improvements in the Validation of Specifications by the Text Editor - API Designer now provides support for AML Modeling Framework (AMF) version 4.5.1. Version 4.5.1 enables JSON parsing recovery, which better validates JSON files with syntax errors. These errors are now more isolated, and more JSON content is now validated. For example, the following demonstrates JSON with syntax errors: { "name": "john", "surname": "doe "age": "33" } Prior to AMF version 4.5.1, the following was displayed: Error: Syntax error : Expecting ',' but 'age'" found Error: Syntax error : Expecting '"' but 'age'" found In AMF version 4.5.1, additional information is now displayed: Error: Syntax error : Expecting ',' but ' ' found Error: Syntax error in the following text: 'doe' Error: Syntax error : Unexpected '"' but ' ' found Error: Syntax error : Missing ',' ### [](#fixed-issues-57)Fixed Issues - Errors were not being reported when publishing malformed OAS assets to Anypoint Exchange. - Moving files into renamed directories caused the following error: is not a valid directory - The **Documentation** panel’s **Operation ID** URL did not match the selected server after loading an OAS 3.0 specification. - Specifications that did not define `baseUri` resulted in no endpoint URL documentation. ## [](#2-24-0)2.24.0 **December 12, 2020** ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-3)Improvements in the Validation of Specifications by the Text Editor - Support for boolean facet properties using JSON Specification Draft 4 or later. This release of API Designer provides support for AML Modeling Framework (AMF) version 4.5.0. In this version of AMF the severity of validation for required boolean facet properties was downgraded from violation to warning. Although it throws a warning, in any JSON Schema specification draft this field is still parsed and set correctly in the model. The following example shows an incorrect usage: { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "property1": { "type": "string", "required": true } } } This example returns the error: `Required property boolean value is only supported in JSON Schema draft-3.` MuleSoft recommends not using this approach. ### [](#fixed-issues-58)Fixed Issues - Fixed an issue where nested resources where incorrectly displayed under the parent resource. - Fixed an issue with periods in the name of a forked branch. - Added warning message when loading a RAML specification containing OAS security schema types. - Fixed an issue where clicking the **Edit spec** button in Exchange caused an error. - Fixed a minor display issue. ### [](#known-issues-2)Known Issues - When selecting a server to use for the mocking service, the URL displayed does not match the selection. - In some cases the endpoint URL may not display in the API specification’s documentation panel. ## [](#2-23-0)2.23.0 **November 14, 2020** ### [](#new-features-12)New Features - Added new dialogs for creating an API specifications and fragments. You can more easily create new API specifications and fragments from an existing file or project. Supported file types are JSON, RAML and YAML. You can also use an existing project saved as a ZIP file. This feature also enables you to create a new Mule application from a JAR file. - For assets published to Anypoint Exchange, you can view the source code directly from Exchange by selecting **View code in API Designer**. By default the project opens in API Designer in read-only mode. If you have edit permissions and the project exists in Exchange, API Designer give you the option to edit the project. - Added hover tooltips that provides additional information about the nodes in an API specification or fragment. ### [](#fixed-issues-59)Fixed Issues - Fixed an issue where data fragment was not shown in API Designer when imported into a library fragment. - Fixed an error in the AMF parser where maximum call stack was exceeded. - Fixed an issue where 404 errors were returns if a branch name contained a slash. - Fixed a YAML error when using the @type in a JSON example. - Fixed an issue where duplicating fragments resulted in a 400 error. - Fixed an issue where API Designer did not complete loading when opening a branch with no files in its root. - Fixed an issue where the branches dialog was not visible when no preview existed for the current selected file. - Fixed an issue where changing the extension of a file required a user interface refresh. - Fixed an issue in the visual editor where values in query parameters could not be set. - In the visual editor, fixed an issue with query parameters after creating an enum type. ## [](#2-22-0)2.22.0 **October 29, 2020** ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-4)Improvements in the Validation of Specifications by the Text Editor - RAML Unions Fixed issue where incorrect validations were occuring under specific conditions using unions. For example, the following API is now valid: #%RAML 1.0 title: Secrets Provider version: v1 baseUri: https://test.com/provider/ types: EncryptedResponse: type: object properties: encryptedKey: type: string sharedSecretUsernamePassword: type: object properties: username: type: string sharedSecretSymmetricKey: type: object properties: key: type: string SharedSecret: sharedSecretUsernamePassword | sharedSecretSymmetricKey /path: get: responses: 200: body: application/json: type: SharedSecret | EncryptedResponse examples: encrypted: | { "encryptedKey": "encryptedKey", "cipherText": "cipherText" } - RAML Version Base URI Parameter Added validation for missing version definitions for the baseUri. For example, the following API is now valid: #%RAML 1.0 title: Brown Google Admin Directory API baseUri: https://localhost/services/cis/brown-google-admin-directory-api/v{version} ### [](#fixed-issues-60)Fixed Issues - Fixed an issue where JSON schemas in RAML specifications were not displayed properly in the Design Center API Console. - Arrays defined in a RAML specification in Design Center were being treated as objects within Studio. - Importing resources failed if they contained invalid file names. API Designer now checks the validity of resources in a ZIP file and alters the filenames if necessary. - Fixed a bug where a file inside a folder did not suggest the correct module when using an !include tag. ## [](#2-21-0)2.21.0 **September 19, 2020** ### [](#new-features-13)New Features - You can have multiple files open simultaneously in API Designer’s text editor. Each file can be open in its own tab. For details, see [Edit in Multiple Tabs in the Text Editor](https://docs.mulesoft.com/design-center/design-edit-multiple-tabs). - Using only one action, you can rename declarable objects everywhere they are used in a project that is open in the text editor. For details, see [Helpful Features in the Text Editor](https://docs.mulesoft.com/design-center/design-helpful-features-text-editor). ### [](#fixed-issues-61)Fixed Issues - When multiple media types were declared in a response body, the documentation pane sometimes did not list them all. - When multiple responses were declared for an API specification written in OAS 2.0, the documentation pane sometimes did not display all of the example responses. - The properties `accessTokenUri` and `authorizationTokenUri` in `settings` nodes were not validated in OAuth 2.0 security schemes. - The properties `requestTokenUri`, `authorizationTokenUri`, and `tokenCredentialsUri` in `settings` nodes were not validated in OAuth 1.0 security schemes. - Examples defined for `queryString` nodes were not appearing in the documentation pane. - The text editor incorrectly allowed the YAML multi-document tag `---`. Now, the editor flags this tag as a syntax error. Here is an example of this tag used in an API specification, and that the text editor flags as a syntax error: #%RAML 1.0 title: api --- /test: - The text editor did not correctly validate the use of security schemes that were defined in RAML SecurityScheme fragments. For example, in this API specification, the scope used is `USER`: #%RAML 1.0 title: API securitySchemes: oauth\_2\_0: !include securitySchemes/oauth\_2\_0.raml /users: get: securedBy: \[ oauth\_2\_0: { scopes: \[ USER \] } \] However, in this SecurityScheme fragment, the scheme is defined with the scope `ADMIN`: #%RAML 1.0 SecurityScheme description: | This API supports OAuth 2.0 for authenticating all API requests. type: OAuth 2.0 settings: accessTokenUri: https:/host/path/oauth2/access\_token authorizationGrants: \[ client\_credentials \] scopes: \[ ADMIN \] In previous releases, the text editor would have allowed the use of the `USER` scope in the API specification. ## [](#2-20-1)2.20.1 **September 1, 2020** This release fixes this issue: The text editor prevented users from typing in invalid characters when naming a new branch. However, in previous releases it was possible for users to paste names that contained invalid characters into the **Create branch** field and create branches with those names. Now, the text editor automatically removes invalid characters that are pasted into the **Create branch** field. ## [](#2-20-0)2.20.0 **August 22, 2020** This release includes a new feature and an enhancement. It also fixes one issue and includes improvements to how API specifications are validated by the text editor. ### [](#new-feature-4)New Feature - You can highlight the names of declarable objects where they are used in a file. To see all of the locations in a file where an object is used, click the cursor in the name of the object where that object is declared. For example, the type `person` is declared on line 5 at the first callout in the following example API specification. That type is subsequently used on line 16 at the second callout. If you click `person` on line 5, the text editor highlights `person` on line 16. #%RAML 1.0 title: Test Highlighting types: person: **(1)** type: object properties: name: string /test: get: responses: 200: body: application/json: type: person **(2)** This highlighting works for all declarable objects, such as types, security schemes, resource types, and traits. Highlighting appears only where the object is used, not every location where its name appears. For example, in the following example API specification, `person` is declared as a type on line 5 at callout 1, mentioned on line 14 at callout 2, and used on line 17 at callout 3. When you click in `person` at callout 1, `person` is highlighted only at callout 3. #%RAML 1.0 title: Test Highlighting types: person: **(1)** type: object properties: name: string /test: get: responses: 200: description: person **(2)** body: application/json: type: person **(3)** ### [](#enhancement)Enhancement The button highlighted by default in the **Replace File?** dialog is now **Keep Both** rather than **Replace**. ### [](#fixed-issue)Fixed Issue When validation of any XML instance against any type declaration cannot be performed, the following warning message is now displayed: Warning: Could not validate XML. ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-5)Improvements in the Validation of Specifications by the Text Editor Two improvements were made in the validation of API specifications written in OAS. One improvement was made in the validation of API specifications written in RAML 1.0. #### [](#oas)OAS - Cyclic references between files are now supported for API specifications that are written in OAS. For example, the following API specification is now considered valid: swagger: '2.0' info: title: pet api version: 1.0 definitions: pet: type: object properties: animalRef: $ref: 'ref.yaml#/definitions/animal' paths: {} definitions: animal: type: object properties: petRef: $ref: 'api.yaml#/definitions/pet' - Unresolved Reference error messages no longer appear for valid specifications. For example, in releases prior to version 2.20.0, the text editor returned the error message ``Unresolved reference `TestSchema`` for an API specification like the following: swagger: "2.0" info: title: 'test' version: "1.2" paths: /pets: get: produces: - application/json responses: '403': $ref: 'ref.yaml#/responses/response1' definitions: TestSchema: type: string responses: response1: description: 'test' schema: $ref: '#/definitions/TestSchema' #### [](#raml-1-0)RAML 1.0 Error messages no longer appear for valid examples inside of overlays. For example, the following API specification is now considered valid: #%RAML 1.0 title: Test types: TestEntity: type: object properties: id: string #%RAML 1.0 Overlay title: Overlay extends: ./api.raml types: TestEntity: example: | { "id": "t123" } ## [](#2-19-0)2.19.0 **July 25, 2020** ### [](#new-feature-5)New Feature You can duplicate projects in API Designer. You might want to duplicate a project if you need to make extensive changes to the project without losing the original on which the duplicate project is based. For more information, see [Duplicate a Project](https://docs.mulesoft.com/design-center/design-duplicate-project). ### [](#enhancements)Enhancements - When you move a file into a folder that already contains a file that has the same name and extension, a new confirmation dialog asks whether you would like to cancel the move, keep both files, or replace the file that is already in the folder. - The text editor no longer validates projects that are in read-only mode. In previous releases, the text editor reported dependencies as missing when projects entered read-only mode. ### [](#fixed-issues-62)Fixed Issues - In the text editor, the order of the data types presented in the documentation pane could differ from their order in a currently open API specification written in RAML. - In some cases, a header could be duplicated on the **Try It** page and, when an API specification was published to Anypoint Exchange, endpoints might display headers that were not defined for those endpoints. - A recursive shape was created from the merge of an endpoint and a resource type when both referenced the same type but in different ways: one referencing it from a library, the other referencing it through a type declaration. - The text editor reported an error if, in the `settings` attribute used by OAuth2, the `scopes` property was not set. - The text editor could fail to make suggestions if the root file of a project was being edited. - If the root file was selected in the text editor, it was possible for the documentation for referenced types not to appear in the documentation pane, although the type definitions in the referenced files did contain documentation. - If any parameter was defined as an enum and the default value was not the first value in the array, the mocking service replaced the first value with the default value. - In the text editor, the Import feature accepted files for which the names included back slashes. Such files were imported, but they could not be accessed in the text editor. ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-6)Improvements in the Validation of Specifications by the Text Editor #### [](#oas-3-0)OAS 3.0 Invalid recursive references are not detected. For example, the following OAS 3.0 API specification is now invalid: { "openapi": "3.0.0", "info": { "version": "0.0.1", "title": "test" }, "paths": { "/path": { "post": { "responses": { "400": { "description": "desc", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/mytype" } } } } } } } }, "components": { "schemas": { "mytype": { "$ref": "#/components/schemas/mytype" } } } } #### [](#raml-1-0-2)RAML 1.0 If you do not define scopes in an OAuth 2.0 security schema, you can use any scope in the implementation of your API. For example, the following specification is now valid: #%RAML 1.0 title: GitHub API securitySchemes: oauth\_2\_0: description: This API supports OAuth 2.0 for authenticating all API requests. type: OAuth 2.0 settings: accessTokenUri: https://someurl/oauth2/access\_token authorizationGrants: \[ client\_credentials \] /users: get: securedBy: \[ oauth\_2\_0: { scopes: \[ USER \] } \] ## [](#2-18-0)2.18.0 **June 27, 2020** This release includes new features and fixes issues. ### [](#new-features-14)New Features - Limited support for OAS 3.0 For details, see [OpenAPI Specification 3.0 Support](https://docs.mulesoft.com/jp/release-notes/platform/oas3). - Changes to the documentation panel in API Designer: The right panel in the text editor of API Designer, which displays the documentation that is written into API specifications and enables you to make requests to the mocking service, includes these changes: - Support for features that are specific to OAS 3.0 For details, see [Differences for OAS 3.0 in Rendered Documentation](https://docs.mulesoft.com/design-center/design-documentation). - Support for OAS flows for OAuth 2.0 For information about OAS flows, see the page "OAuth 2.0" on swagger.io at [https://swagger.io/docs/specification/v3\_0/authentication/oauth2/](https://swagger.io/docs/specification/v3_0/authentication/oauth2/). - Support for applying multiple security definitions simultaneously in requests made to the mocking service - Support for disabling automatic encoding of URI parameters in requests to the mocking service Use the new `no-auto-encoding` annotation, as in this example: paramName: (no-auto-encoding): type: string - New "go to" actions in the text editor In RAML API specifications, you can: - Right-click the name of a type and select **Go to Definition** in the pop-up menu to navigate to the declaration of the type. - Right-click the name of a resource type or trait and then select one of these options in the pop-up menu: - Select **Go to Definition** to navigate to the declaration for the resource type or trait. - Select **Go to Type Definition** to navigate to the definition of the resource type or trait. - Right-click a `resourceTypes` or `traits` node and select **Go to Implementations** to see where the resource types or traits that are defined in the node are implemented. - Right-click the declaration of a Type and Annotation Type that uses a library, and then select one of these options from the pop-up menu: - Select **Go to Definition** to navigate to the corresponding definition. - Select **Go to Type Definition** to navigate to the corresponding type definition. In OAS API specifications, you can: - Right-click an example of a reference object and select **Go to Definition** in the pop-up menu to navigate to the definition of that object. - Right-click a reference to a schema file (for example, `schema.yaml` in `$ref:"schema.yaml"`) and select **Go to Definition** to navigate to the file. - Right-click the name of an embedded schema in a reference to a schema file (for example, `Contact` in `$ref:"schema.yaml#/definitions/Contact"`) and select **Go to Definition** to navigate to that portion of the schema. ### [](#fixed-issues-63)Fixed Issues - The text editor could not open an API specification that was written in RAML. The error message was `Missing header x-user-id`. - Enum values in a RAML API specification that was published to Anypoint Exchange from the text editor did not appear in the documentation of the specification in Anypoint Exchange. - The text editor did not detect duplicate keys if one of the two keys was surrounded by quotation marks. - In the documentation pane of the text editor, the table view of the Response body did not correctly translate the source view. - The text editor displayed the error message `Internal error during validation` for an API specification that was written in RAML. - In the text editor, when objects that contain arrays or collections were shown in XML in the documentation pane, the names of child elements were generated incorrectly. - For API specifications written in OAS 2.0, the **Response** section in the documentation pane showed the same response example for all response codes. - Examples defined at the property level of types were not included in examples at the resource level in the documentation pane of the text editor if a RAML API specification defined more than one endpoint. - The warning message `Unable to load schema from 'http://schema.hropenstandards.org/4_0/common/json/meta/hros.json'. No schema request service available.` appeared erroneously in the text editor for a particular JSON schema. ### [](#improvement-in-the-validation-of-api-specifications)Improvement in the Validation of API Specifications - Fixed the "Unresolved reference" error for references to `.yaml` files in OAS API specifications. For example, the following API is now valid: swagger: '2.0' info: title: Sample API version: '' paths: /resource: get: responses: '200': description: '' schema: $ref: 'f/complexType.yaml' /resource2: get: responses: '200': description: '' schema: $ref: 'f/baseType.yaml' type: object properties: ref: $ref: baseType.yaml type: object properties: name: type: string ## [](#2-17-2)2.17.2 **June 2, 2020** This release fixes these issues: - Suggestions and errors were not displayed for an API specification written in RAML 1.0 and that should have generated the error message "Error recursive shape". - The text editor allowed an API specification written in RAML 1.0 to be published to Anypoint Exchange, even though the specification contained an error. - The search field in the text editor lost focus whenever a character was typed in it. - At times, the **Documentation** panel did not display any content. - At times, clicking a link to an unreferenced file from within the **Project Errors** view caused the browser window to become blank. ## [](#2-17-0)2.17.0 **May 30, 2020** This release includes new features and fixes several issues. ### [](#new-feature-6)New Feature - The text editor now displays error messages and warnings in a new view that you can open by clicking a tab in the editor’s bottom-right corner. You can view the errors and warnings for all files in a project, or the errors and warnings for the file that is currently displayed in the editor. This new view also lists all unreferenced files in the current project. When you first open the text editor in this release, a dialog appears that describes the features of the new view and displays screenshots. - The new status bar at the bottom of the text editor shows the name of the currently open file, the position of the cursor in the file, whether the file is the root file of the project, the language (RAML or OAS) that the current file is written in, and the type of project that you are working in. ### [](#fixed-issues-64)Fixed Issues - API Designer did not publish a project to Exchange if the project contained a filename that included a space. - Attempting to update an Exchange dependency sometimes resulted in the error message `502 Bad Gateway`. - Neither the **Documentation** pane nor the **Try It** panel were generating the correct XML example for element names that contained periods, such as `[abc.xyz]`. - For API specifications written in OAS 2.0, the **Documentation** panel could display **API Key** twice in the **Authorization method** field if two security definitions were both defined as the `apiKey` type. - When the client ID or secret for a RAML API specification that included `authorizationGrants: [client_credentials]` was not visible in the **Documentation** pane, the **Client ID** or **Secret** field was also not visible. - The text editor sometimes failed to render methods and endpoints in imported OAS 2.0 API specifications. ### [](#improvement-in-the-validation-of-api-specifications-2)Improvement in the Validation of API Specifications The text editor now validates recursive shapes correctly. For example, the following OAS 2.0 API specification is considered valid: { "swagger": "2.0", "info": { "title": "test", "version": "1.1" }, "definitions": { "Causes": { "$ref": "#/definitions/Test" }, "Test": { "properties": { "subsenses": { "items": { "$ref": "#/definitions/Test" }, "minItems": 1, "type": "array" } }, "type": "object" } }, "paths": {} } However, the following RAML 1.0 API specification is considered invalid: #%RAML 1.0 title: Recursive types: Recursive: type: object properties: myP: type: Recursive /recursiveType: post: responses: 201: body: application/json: type: Recursive ### [](#known-issue)Known Issue The URL for the mocking service might remain visible even after the mocking service is switched off. To hide the URL, switch to another page in the **Documentation** pane. ## [](#2-16-0)2.16.0 **May 2, 2020** This release includes three enhancements and four fixes. It also includes an improvement in how the text editor validates API specifications that are written in OAS 2.0. ### [](#enhancements-2)Enhancements - Beginning with Anypoint Studio 7.5.0, users can edit API-Designer projects directly in Studio. If you are working in a project in the text editor in API Designer at the same time that someone using Anypoint Studio 7.5.0 or later is working in the same project, there could be save conflicts. As you work in the text editor in API Designer, the editor saves your project frequently if you have made changes since the last automatic save. However, if a user in Studio is working in the same project and saves changes before the next automatic save in the text editor in API Designer, the editor displays this message: This branch has changed externally A new commit has been made to this branch since your last save. We will use the changes from your repository and discard your latest updates. The message shows a **Discard and Use New Changes** button. You must click the button to accept the changes. Because the text editor automatically saves often, you will usually lose only a few changes. - The **Exchange Dependencies** pane lists RAML API fragments that have been added as dependencies in a project directly from Anypoint Exchange. Now, when a new version of a fragment listed in the **Exchange Dependencies** pane is published on Exchange, an icon appears next to the name of the dependency to notify you that the version you are using is deprecated. As in previous releases, follow these steps to use the new version in your project: 1. Click the name of the dependency. 2. Select **Change version**. 3. Select the current version in the **Change version** dialog. - If an error occurs when you publish a project to Anypoint Exchange, the error message now appears in the publish dialog. - In the `exchange_modules` folder in projects in the text editor, there are two changes: - An icon of a lock now appears next to the `exchange.json` file to indicate that this file is read-only. - The names of all of the files in this folder are now in gray to indicate that they should not be edited. ### [](#fixed-issues-65)Fixed Issues - In some cases, the text editor reported that RAML trait fragments in an API-specification project included unresolved file references, even when the file references were correct. - The text editor displayed the error message "Error recursive shape" when a RAML API specification referenced an Exchange Library type. - The use of `$ref` caused the text editor to display error messages about unresolved file references when referenced files were in project subfolders and when they were in the top level folder. - In the visual editor, if a search in the filter field found results in the **DATATYPES** section, the **RESOURCE** section, or both, those sections were not automatically expanded if they were closed. ### [](#improvement-in-the-validation-of-specifications-by-the-text-editor)Improvement in the Validation of Specifications by the Text Editor In API specifications written in OAS 2.0, references to YAML files are now supported. For example, the following API specification is now considered valid: `root.yaml` swagger: "2.0" info: version: 1.0.0 title: Swagger Petstore paths: /pets: get: responses: "200": description: unexpected error schema: $ref: 'ref.yaml' `ref.yaml` type: object required: - code - message properties: code: type: integer format: int32 message: type: string ## [](#2-15-0)2.15.0 **April 4, 2020** This release includes several new features, two enhancements, several fixes, and several improvements to how the text editor validates specifications. ### [](#new-features-15)New Features - The new **Filter** field in the **Files** pane of the text editor can help you locate files in your project faster. The equivalent field on the left side of the visual editor can help you locate security schemes, resources, and data types faster. - You can now import API specifications from Anypoint Exchange into the visual editor. An imported specification completely replaces the specification that is currently open in the visual editor. You can import a specification only if it does not contain any fragments. - In the visual editor, you can proxy a request to a REST service by deselecting the shield in the top-right corner: - If the shield is selected, the request won’t be proxied. For example, request URLs that the mocking service provides look like this: `https://anypoint.mulesoft.com/mocking/api/v1/links//` ![Selected](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-firewall-checkbox-visual-editor.png) Figure 1. The shield is selected. - If the shield is not selected, the request will be proxied. For example, request URLs that the mocking service provides look like this: `https://anypoint.mulesoft.com/apiconsoleproxy/api/v1/proxy/https:///mocking/api/v1/links//` ![Not selected](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-firewall-checkbox-visual-editor-off.png) Figure 2. The shield is not selected. ### [](#enhancements-3)Enhancements - When you are working in the text editor on files written in RAML, you can now hold the command key and click on the file name in an `!include` tag to open that file. - When a line of text in a file in the text editor is underlined red, indicating that there are one or more errors in the line you can click in the line to see the error message or messages. ### [](#fixed-issues-66)Fixed Issues - In the visual editor, changing a data type’s minimum and maximum lengths could result in these lengths being changed for other data types, too. - If you view the asset page for an API specification in Anypoint Exchange, you can click **View Code** to open the specification in read-only mode in the text editor of API Designer. The issue was that, if you tried to view different files in an API specification after entering read-only mode this way, the text editor displayed the error message "The requested resource could not be found." - API Designer did not flag as invalid cases in which a property was defined as a numeric or object type, but then overridden with type "any", which is less restrictive. - The text editor displayed the error message `Should NOT be longer than _n_ characters at …​` because it incorrectly invalidated inheritance in examples. - Some properties defined in API specifications written in RAML appeared in the **Types** section in the left pane of the asset page in Anypoint Exchange. - Endpoints were sometimes not grouped and listed correctly in the **Documentation** pane. - Microsoft Internet Explorer 11 closed unexpectedly when opening API Designer projects. ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-7)Improvements in the Validation of Specifications by the Text Editor One improvement was made for the validation of specifications written in RAML. Three were made for the validation of specifications written in OAS 2.0. #### [](#raml)RAML Declarations of status codes as optional are now flagged as invalid. For example, the definition of the response `201` in the following specification causes the text editor to display the error message `Status code for a response must be a value between 100 and 599 at (x, y)`: #%RAML 1.0 title: test types: x-ratelimit-limit: type: number description: The rate limit ceiling for this endpoint. traits: rateLimited: responses: 201?: headers: x-ratelimit-limit: x-ratelimit-limit /test: get: is: \[rateLimited\] responses: 200: #### [](#oas-2-0)OAS 2.0 - Duplicate `body` parameters are now parsed as invalid. For example, the following specification causes the text editor to display the error message `Cannot declare more than one 'body' parameter for a request or a resource at (x, y)`. { "swagger": "2.0", "info": { "title": "Test", "version": "1.0.0" }, "paths": { "/": { "parameters": \[ { "name": "body parameter 1", "in": "body", "schema": {} }, { "name": "body parameter 2", "in": "body", "schema": {} } \], "get": { "responses": { "200": { "description": "ok" } } } } } } - The value of a security requirement object now must be an array. For example, the text editor flags this specification as invalid because the value of `Bearer` is set to a string: { "swagger" : "2.0", "info" : { "title" : "Registry", "version" : "1" }, "paths" : { }, "security" : \[ { "Bearer" : "" } \], "securityDefinitions" : { "Bearer" : { "in" : "header", "name" : "Authorization", "type" : "apiKey" } } } To correct the problem, set the value to an array: { "swagger" : "2.0", "info" : { "title" : "Registry", "version" : "2" }, "paths" : { }, "security" : \[ { "Bearer" : \[\] } \], "securityDefinitions" : { "Bearer" : { "in" : "header", "name" : "Authorization", "type" : "apiKey" } } } - The `name` facet is now required. For example, the following specification causes the text editor to display the message `Name is mandatory in License object at (x, y)`: { "swagger": "2.0", "info": { "title": "Testing API", "version": "1.0.0", "license": {} }, "paths": {} } ## [](#2-14-2)2.14.2 **March 11, 2020** This release includes the following two fixes: \* The visual editor displayed the **Publish with unreferenced files?** confirmation dialog during the publish process. This dialog is relevant only for projects created in the text editor. \* The text editor displayed the error message `Not found` when a file for which the name contained invalid characters was selected. ## [](#2-14-1)2.14.1 **March 7, 2020** This release includes one enhancement, seven fixes, and four improvements to how API specifications are validated. ### [](#enhancement-2)Enhancement - By default, files in a project that are not directly or indirectly referenced by the project’s root file are not published to Anypoint Exchange along with the rest of the project. However, you can select an option to override this default and to include unreferenced files in a published project. ![The dialog with the option](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-unreferenced-files.png) Figure 3. This is the dialog that provides the option to override the default or to cancel publication so that you can remove unreferenced files. ### [](#fixed-issues-67)Fixed Issues - The text editor no longer suggests the `usage` facet for any types of RAML fragment other than ResourceType, Trait, Library, Overlay, and Extension. - In the text editor, files were allowed to be renamed to include characters that broke the process for publishing to Anypoint Exchange. - In the text editor, API specifications written in OAS 2.0 generated errors if their first line was composed of three dashes or if a line of three dashes followed directives. Example of the first case \--- swagger: "2.0" info: description: This API is written in OAS 2.0. version: "1.0" title: api-in-oas Example of the second case %YAML 2.0 %TAG !/directive/ --- swagger: "2.0" info: description: This API is written in OAS 2.0. version: "1.0" title: configuration-exp-api-consul - In certain cases, starting a project from an existing example generated an error. - It was possible to create an OAS 2.0 (JSON) project named "exchange", which led to a malformed initial file because of the conflict with the metadata file "exchange.json". Now, if you try to name such a project "exchange", the name given to the project is "1-exchange". - In the **Asset name** field of the dialog for publishing projects to Anypoint Exchange, spaces were replaced by dashes. - The navigation icon in the **Documentation** pane appeared for all types of RAML fragment, rather than only for Library, Overlay, and Extension fragments. The firewall icon also appeared for all types of RAML fragment, rather than only for Overlay and Extension fragments. ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-8)Improvements in the Validation of Specifications by the Text Editor ### [](#improved-validation-of-the-required-field-in-json-schemas)Improved Validation of the required Field in JSON Schemas If you are using JSON Schema 4 or later (the text editor uses version 4 if you do not specify a version), the `required` field takes an array as its value. In previous versions of JSON Schema, this facet took a boolean value. In previous releases of API Designer, the text editor did not display an error message if you were using JSON Schema 4 or later and you used a boolean value for the `required` field. Now, the text editor displays this error message: `'required' field has to be an array at (,)` For example, the text editor no longer considers valid the use of the `required` field in this specification: #%RAML 0.8 title: amf-validations /jobs: displayName: Jobs post: description: Create a Job body: application/json: schema: | { "$schema": "http://json-schema.org/draft-04/schema", "properties": { "input": { "type": "string" } }, "required": "true", "type": "object" } ### [](#validation-of-the-type-field-in-parameters-in-oas-2-0-api-specifications)Validation of the type Field in Parameters in OAS 2.0 API Specifications In previous releases, the text editor did not display an error message when the list of parameters for an endpoint in an OAS 2.0 API specification lacked a `type` field. Now, the text editor displays this message: `Cannot find valid schema for parameter at (,)` For example, the text editor no longer considers valid the lack of the `type` field in this specification: { "swagger": "2.0", "info": { "title": "amf-validations", "version": "v1" }, "host": "api.github.com", "schemes": \[ "https" \], "paths": { "/users": { "get": { "description": "Get a list of users", "parameters": \[ { "name": "page", "description": "Specify the page that you want to retrieve", "required": true, "in": "query" } \] } } } } ### [](#validation-of-the-definitions-of-properties-in-json-schemas)Validation of the Definitions of Properties in JSON Schemas In previous releases, the definitions of properties in JSON schemas were not validated. For example, the text editor no longer considers valid the definition of the property in this specification, which contains an array instead of an object: #%RAML 0.8 title: amf-validations /media: displayName: Most Popular Media get: description: Get a list of what media is most popular at the moment. responses: 200: body: application/json: schema: | { "$schema": "http://json-schema.org/draft-03/schema", "type": "object", "properties": \[ { "date": "date" }, { "amount": "integer" } \] } ### [](#validation-of-json-schemas-that-do-not-define-types)Validation of JSON Schemas That Do Not Define Types In previous releases, if an example of a property for which no type was defined used any type other than `object`, the text editor incorrectly displayed this error message: should be object at (,) For example, the text editor would display the error message for this specification because the definition of the property `from` does not include a definition of the property’s type. The example, however, shows that the type is `string`: #%RAML 1.0 title: amf-validations types: Client: type: | { "$schema": "http://json-schema.org/draft-03/schema", "type": "object", "properties": { "from": { "required": true } } } example: { "from": "test" } ## [](#2-13-3)2.13.3 **February 13, 2020** This release fixes two issues. - Clicking the **Upgrade** button in the notice about upgrading the mocking service resulted in the error message `Connection lost`. - The browser window in which the text editor in API Designer was being used would sometimes go blank. ## [](#2-13-0)2.13.0 **February 6, 2020** ### [](#new-features-16)New Features - A new filter dialog enables you to filter the list of projects in Design Center, in addition to filtering the list of projects in the existing search box at the top of the list. ![The filter dialog](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-dc-filter.png) Figure 4. You can filter on project type and range of time during which projects were last updated. You can also view only those projects that you created.
1The button for opening the filter dialog.
2The filter for specifying or selecting the type of project to list.
3The filter for selecting the range of time during which projects that you want to list were last updated.
4The checkbox for selecting only the projects that you created.
- You can now sort the list of projects in Design Center by clicking the column headings. - Options for importing files into a project and downloading a project are now in a new menu that you open by clicking an button on which a gear appears. Two new project-level options also appear on that menu: **Rename** and **Delete**. ![The new project menu](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-project-menu.png) Figure 5. The button for opening this menu is in the top-right corner of API Designer, next to the **Publish** button.
1The menu includes two sections. This section includes the options for importing files and downloading the project.
2This section includes the options for renaming the project and deleting it.
3This is the button that you click to open the menu.
- Import files from your computer or from Exchange into folders that are listed in the **Files** pane of the text editor. Click the three dots to the right of the name of a folder and select either **Import** or **Import from Exchange**. ### [](#enhancements-4)Enhancements - The dialog for publishing API specifications has been simplified. ![A comparison of the previous publish dialog with the new one.](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-publish-dialogs.png) Figure 6. The new dialog for publishing API specifications is more simple and more helpful.
1 The name of the API specification appears as the title of the dialog.
2 There are now only two fields that require values.
3 An option to add the API specification to API Manager is included in the More options section.
4 Help for deciding on an asset version number appears within the dialog.
5 Links to additional help are provided.

To learn more about publishing an API specification, see Publish an API Specification.
- The dialog for publishing API fragments has also been simplified. ![A comparison of the previous publish dialog with the new one.](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-publish-dialogs-api-fragments.png) Figure 7. The new dialog for publishing API fragments is also more simple and more helpful.
1 The name of the API specification appears as the title of the dialog.
2 There is now only one field that requires a value.
3 Help for deciding on an asset version number appears within the dialog.
4 A link to additional help is provided.

To learn more about publishing an API specification, see Create and Publish an API Fragment.
- Within the text editor, you can now set the root file for an API-specification project and for an API-fragment project. In the previous release, you set the root file in the **Main file** field of the publishing dialog. ![The controls related to root files](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-set-root-file.png) Figure 8. The controls that are related to root files are in the **Files** pane. This image shows the controls in an API-specification project.
1The menu opened by clicking the three dots to the right of a specification includes the option Set as root file.
2An indicator shows which specification is currently set as the root file.
3Click the question mark in the menu to learn more about root files. The question mark opens this topic in the online documentation: Root Files in Projects in the Text Editor in API Designer.
### [](#fixed-issues-68)Fixed Issues - The **Import from Exchange** dialog is not opened when the option **Import from Exchange** is selected in an empty API-fragment project. - Fixed a problem that caused the parser to return `Unresolved reference` error messages in a particular situation. - When a user accessed an API specification that had dependencies that were published in a business group other than the one that the user belonged to, those dependencies were deleted from the specification. Now, when the user opens a project, if the specification any has dependencies that were removed from Exchange or if the project was published in a different business group, API Designer takes the following actions: - Displays a message in the Dependencies pane to warn of the missing dependencies. - Disables the options "Show in files," "Change version," and "Open in Exchange" for each missing dependency. - Disallows publishing the API specification to Anypoint Exchange. - The code examples generated for RAML API specifications in the **Documentation** pane in the text editor contained errors. - Custom annotations were ignored both in the **Documentation** pane in the text editor and in Anypoint Exchange. - The **Documentation** pane in the text editor was showing under the 200 status code the responses for the other status codes for an HTTP method. ### [](#improvement-in-the-validation-of-specifications-by-the-text-editor-2)Improvement in the Validation of Specifications by the Text Editor In previous releases, the text editor displayed an error message similar to this one when a specification included a `repeat` facet in an API specification written in RAML 0.8: `Property 'repeat' not supported in a RAML 1.0 string node at (13, 13)`. The parser incorrectly validated the facet against the RAML 1.0 specification, which does not define this facet. Now, the parser correctly validates RAML 0.8 API specifications that use the `repeat` facet, such as this specification, and does not display an error message: ```none #%RAML 0.8 title: Test API securitySchemes: - oauth_2_0: description: | Supports OAuth 2.0 for authenticating all API requests. type: OAuth 2.0 describedBy: headers: Authorization: type: string repeat: true /users: get: securedBy: [ oauth_2_0 ] ``` ## [](#2-12-0)2.12.0 **January 11, 2020** This release includes seven enhancements, twenty fixes, and three improvements to how API specifications are validated. ### [](#enhancements-5)Enhancements - The **Documentation** pane now renders RAML fragments of the types DataTypes, DocumentationItem, and SecurityScheme; complies with Web Content Accessibility Guidelines (WCAG) 2.1; includes new console elements for rendering XML schemas and examples; includes a simpler request panel; renders complex API specifications faster; and includes fixes for several issues reported by customers. - The **Filter** field in the visual editor did not accept input. - If you are using the text editor to write an API specification in RAML, and you try to edit a file that is a dependency, the message "This file is read-only." appears at the top of the editor. For information about dependencies, see [Add a RAML API Fragment to an API-Specification Project as a Dependency](https://docs.mulesoft.com/design-center/design-add-api-dependency). - A number of fixes and styling changes were made to the **Documentation** pane, which displays the documentation for API specifications and supported RAML fragments, and to the **Try It** feature, which lets you use the mocking service to simulate calls to resource methods in your specifications. - In the visual editor, errors are now easier to find due to red indicators placed in various locations. For example, an error in a response body for a resource method is indicated in red in four locations: ![apid vapid resource error 1](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-vapid-resource-error-1.png) Figure 9. Annotations 1 through 4 show four locations of red indicators that signal the presence of one or more errors. Annotation 5 shows that you can expand the resource body to see the error. Annotation 1 points to the first red indicator: the name of the type of resource method. Annotation 2 points to the second red indicator: the name of the resource method. Annotation 3 points to the third red indicator: the response code. Annotation 4 points to the fourth red indicator: the border of the **Bodies (1)** section. Annotation 5 points to the arrow you can click to expand the **Bodies (1)** section to see the error. When you click it, the border expands (as shown by Annotation 1 in the next image) and red borders appear on the left and right of the field where the error is located. ![apid vapid resource error 2](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-vapid-resource-error-2.png) Figure 10. Annotation 1 shows the red border of the section that the error appears in. Annotation 2 points to the field where the error is located. Hover over the field for a message that explains the error. The same types of indicator appear for errors in other parts of a specification. In this next example, the error is in the definition of the definition of a property of a data type. The name of the data type appears in red, the left border of the **Property Name** section is red, and you can click the arrow icon to expand this section and see the error. ![apid datatype error 1](/mulesoft/current/ja-jp/release-notes/_images/design-center/apid-datatype-error-1.png) - When you import a specification in a `.zip` file or import an asset from Exchange into an existing project, the **Replace** dialog appears when files with the same filename appear in both the `.zip` file or asset and the project. In this dialog, you can select the files that you want to replace in the project. With the 2.10.0 release, this dialog includes the new option **Select all**, which lets you select all of the listed files. - The **Import** dialog now displays a spinner to indicate that the import action is taking place. - It is now easier to include files in a specification. Open the action menu on any file that you want to include and select either the **Copy Name** or **Copy Path** options. You can then paste the name or the path into your `include` statement. - You can clone any file in a project in the text editor. In the **Files** pane, open a file’s action menu by clicking the three dots to the right of its name. Then, select **Clone File**. A copy of the file appears in the file list for the project. By default, each copy is named `n-name.extension`, where `n` is the next available number, starting from 1. To rename a clone, click the action menu and select **Rename**. ### [](#fixed-issues-69)Fixed Issues - Users without the Design Center Developer permission could open projects. Now, if a user does not have this permission, the user cannot view the list of projects in Design Center or open a project by visiting the URL. - The Experience API responded with a 403 in a particular case, but a project was still created. - The visual editor displayed an error when a data type was defined as nil and the example used a null value. Several fixes were made to the Undo/Redo feature in the visual editor. - Using the `$schema` keyword with a custom URI caused the following error: `Warning: Unable to load schema from . No schema request service available.` - The `schemaLocation` attribute now loads the location of a referenced XML schema. - The locations of XML schemas to import were not being resolved. - For the fragment types Data Type, Documentation, Extension, Library, Overlay, and Security Scheme, the message `Base URI not defined in the API file` no longer appears in API Console. - Code samples generated in API Console for resource methods sometimes included errors. - Boolean properties were rendered by API Console as strings in payloads before being passed to the mocking service in method bodies. - Spaces in URI parameters were encoded by API Console as `+` rather than as `%20` in URIs generated by the mocking service. - Large API specifications would not appear in API Console in some cases. - XML-wrapped examples in specifications written in RAML were not parsed correctly in API Console. - A specification written in OAS caused the mocking service to fail with the error \`org.json.JSONException: Duplicate key "” at…​'. - The content of the `summary` field in specifications written in OAS did not appear in API Console. - API Console was rendering integers as strings. - When a specification written in OAS had internal references to schema definitions, this message appeared in API Console in the body of the responses for a method: `The API file specifies body for this request but it does not specify the data model.` - When the mocking service was used for a GET request for which the authorization method was x-clientIDSecret, the message `Fill in required parameters` appeared even when the **Client-id** and **Client-Secret** fields in API Console were filled in. - API Console added tags to XML examples that contained arrays. ### [](#improvements-in-the-validation-of-specifications-by-the-text-editor-9)Improvements in the Validation of Specifications by the Text Editor - The text editor now accepts as valid non-Boolean values for the `additionalItems` keyword, which is part of JSON Schema.

According to JSON Schema (https://json-schema.org/understanding-json-schema/reference/array), the additionalItems keyword "controls whether it’s valid to have additional items in the array beyond what is defined in items."
For example, the text editor no longer displays an error message that says the use non-Boolean values for the instance of `additionalItems` in this schema is invalid: #%RAML 1.0 title: AMF-VALIDATIONS types: contact: | { "$schema": "http://json-schema.org/draft-04/schema#", "type": "object", "description": "Allows the insertion of a Contact Us request into Unilever backend systems", "properties": { "consumer": { "type": "array", "items": \[ { "type": "number" }, { "type": "string" }, { "type": "string", "enum": \["Street", "Avenue", "Boulevard"\] }, { "type": "string", "enum": \["NW", "NE", "SW", "SE"\] } \], "additionalItems": {"type": "integer"} } } } /contact: post: body: application/json: type: contact example: | { "consumer": \[1600, "Pennsylvania", "Avenue", "NW", 2050\] } - Fields used in shape merging are now being validated. For example, the following lines will be no longer valid in a RAML specification: #%RAML 1.0 title: test API resourceTypes: rt: post: body: application/json: type: object properties: a1: number /endpoint: type: rt post: body: application/json: type: string In this example, an attempt is being made to merge an object, defined as `rt` under `resourceTypes` and that has a `number` property, into a scalar. The definition of the endpoint defines its payload type as an `rt` object. However, the definition of the endpoint then tries to set the type of the payload to `string`, which is incompatible with the definition of the `rt` object as being of type `number`. - Incorrect values specified for enums are now flagged as invalid. For example, the value for this enum would be flagged as invalid because it is a map with a key and a value, rather than just a value: ```none { "swagger": "2.0", "info": { "title": "My API with Types", "version": "1.0" }, "paths": { "/orgs": { "get": { "responses": { "200": { "description": "", "schema": { "type": "string", "enum": [{ "key": "value" }] } } }, "security": [] } } } } ``` The correct declaration would be this: ```none { "swagger": "2.0", "info": { "title": "My API with Types", "version": "1.0" }, "paths": { "/orgs": { "get": { "responses": { "200": { "description": "", "schema": { "type": "string", "enum": [ "value", "value1" ] } } }, "security": [] } } } } ``` - The validation of `!include` tags is improved. For example, the following example is now parsed as valid because it is considered to be a string payload: ```none #%RAML 1.0 title: test API /resource: get: responses: 200: body: application/json: example: !includedexample ``` ## [](#2-9-0)2.9.0 **October 4, 2019** This release includes two new features, an enhancement, and several fixes. Also, four more types of errors are flagged as invalid by the parser that was released on January 10 of this year. The parser that API Designer used before that date did not flag these errors as invalid. ### [](#new-features-17)New Features - You can now add custom headers when using the mocking service to test endpoints in API specifications that you are developing in the visual editor. ### [](#enhancement-3)Enhancement - You might experience a delay of a few seconds When you switch between branches of a project in the text editor. Now, a message appears that shows the progress in switching to the selected branch. ### [](#fixed-issues-70)Fixed Issues - In Google Chrome, the text editor displayed no error messages for a project. However, the text editor displayed many error messages for the same project in Mozilla Firefox. - A test request for a file made to the mocking service from a browser correctly resulted in the downloading of the file. However, test requests for the same file made to the mocking service from within API Designer and Exchange did not result in the downloading of the file, even though a status code of 200 was returned. - The error message `Error publishing to Exchange: Nout found` appeared in the following scenario: 1. Create an API-specification project in the text editor. 2. Go to the Dependencies panel and consume one or more Exchange assets. 3. Close the project. 4. Go to Exchange and delete one of the two consumed assets. 5. Return to API Designer and reopen the project. 6. Try to publish the API specification to Exchange. ### [](#errors-now-flagged-as-invalid)Errors Now Flagged As Invalid - Types defined as `nil` in payloads are no longer valid. **Example 1** In this example, the value of `type` must be `string`, not `nil`: ```none #%RAML 1.0 title: test types: MyType: type: nil example: “test” ``` **Example 2** In this example, the JSON schema must define `MyType` as a `string` type. However, the schema is empty. ```none #%RAML 1.0 title: test types: MyType: type: !include schema.json # schema.json is an empty file example: “test” ``` The error message in cases like this is `should be null at …​`. - A subtype defining a weaker constraint than one defined by its parent is no longer valid. In this example, the subtype MyType2 has the optional property `name`, defined as a string, even though the parent type MyType1 already defines its `name` property as required. ```none #%RAML 1.0 title: test types: MyType1: properties: name: string MyType2: type: MyType1 properties: name?: string #invalid ``` The error message in cases like this is `Resolution error: sub type has a weaker constraint for minItems than base type for minItems.` - A URI parameter that contains a forward slash (/) is no longer valid. In this example, the `example` for the URI parameter `transaction-Date` would cause the parser to display an error message. ```none #%RAML 1.0 title: test /endpoint: uriParameters: transaction-Date: example: 01/02/2018 ``` The error message in cases like this is `Value '01/02/2018' of uri parameter must not contain '/' character.` - Formats for `datetime` types that do not use "rfc3339" or "rfc2616" are now invalid. The following example would cause the parser to display an error message. ```none #%RAML 1.0 title: test types: MyType: type: datetime format: "rfc3338" ``` The error message in cases like this is `Invalid format value for datetime, must be ‘rfc3339’ or ‘rfc2616’.` ## [](#2-8-3)2.8.3 **September 19, 2019** This release fixes the following issue: In the 2.8.0 release, an `Unresolved reference` error was reported for a resource type that was in fact free of errors. ## [](#2-8-0)2.8.0 **September 7, 2019** ### [](#announcement)Announcement Version 2 of the mocking service is replacing Version 1. You must migrate any API-specification project that meets _both_ of these conditions: - The mocking service was switched on for the project before January 10, 2019. - The mocking service has been running continuously since it was switched on. #### [](#dates-for-the-deprecation-and-end-of-life-of-version-1)Dates for the Deprecation and End of Life of Version 1 - **On November 29, 2019**, Version 1 of the mocking service will be deprecated. Starting on that date, third-party tools must include this header in requests that they send to the mocking service to test endpoints in API specifications being developed in API Designer: `x-deprecation-acknowledgement` The header must have this value: `I understand that version 1 of the mocking service is deprecated and that I need to upgrade before February 1, 2020.` - **Starting February 1, 2020**, Version 1 of the mocking service will no longer send responses to requests. If you have not migrated your projects to use Version 2 of the mocking service by this date, the mocking service will return the HTTP status code 301 and provide a link to this document. ### [](#new-feature-7)New Feature The new behavioral header `MS2-Status-Code-Selection` gives you two options for controlling how the mocking service selects a status code for responses to requests. See [Add Behavioral Headers to Simulated API Calls](https://docs.mulesoft.com/design-center/apid-behavioral-headers) for details. ### [](#enhancements-6)Enhancements - The button **Publish to Exchange** is now **Publish**. It opens a small message that contains the button **Publish to Exchange**. The message explains why you might want to publish a specification or fragment to Exchange. If a spec or fragment has already been published, the message contains a link to it on Exchange. - In the visual editor, the top of the **Documentation** pane now shows the path of the selected resource. - In the **Publish to Exchange** dialog in previous releases, the version number in the **Version** field was generated automatically if a specification lacked a `version` node. Now, if a specification lacks this node, the field remains blank and you must specify a value. ### [](#fixed-issues-71)Fixed Issues - Uploading a library into an API-specification project when using Google Chrome caused Chrome to crash. - The text editor did not recognize the date form "yyy-mm-dd" in JSON example schemas. - Importing a particular API specification into the text editor caused Design Center to become unresponsive in Google Chrome. - The text editor was reporting an internal error during validation, but the reference in the error message was unrelated to the line at which the message stated that the error occurred. - The text editor was incorrectly reporting an unresolved reference for a library type in a resource type. - Very long project names could not be read in various locations. - The text editor displayed random warnings that XSD schemas were invalid in an API specification that had numerous, complex schemas. ## [](#2-7-0)2.7.0 **August 10, 2019** This release introduces two new features and fixes several issues. ### [](#new-features-18)New Features - You can now see a list of API-specification projects and API-fragment projects that you recently opened or created. In the top-left corner of your browser window, click the three lines to the left of the Design Center logo. - **For projects created before January 10, 2019:** If no errors appear in your project when the switch that is labeled **Show Strict Errors** is toggled off, and if errors do appear in your project when that switch is toggled on, a countdown timer appears to the left of the **Publish** button to remind you of how many days you have left to resolve the errors. If the timer for such a project expires before you have resolved the errors, you will not be able to publish the specification to Exchange until you have done so. ### [](#fixed-issues-72)Fixed Issues - Published copies of complex API specifications in RAML on Exchange were truncated by 20 characters. - API specifications in RAML that included Arabic characters could not be published to Exchange. - JSON examples that included umlauts could not be uploaded to API Designer by means of the Save API. - In some cases, publishing an API specification in RAML to Exchange resulted in the last few characters of the specification not appearing in Exchange. - Importing an asset from Exchange that included dependencies could result in an error message similar to this one: `Unexpected token o in JSON at position 1`. - An `!include` in a `type` definition was incorrectly causing the error message `Error while parsing file. at (1,0)` to appear. - The API Designer xAPI was truncating the last line from specifications that were uploaded to projects by means of Anypoint CLI. - During attempts to publish an API specification in RAML, the **Main file** field in the **Publish API Specification** dialog was blank and the specification could not be published. However, if the specification was imported into a new project, then publishing it to Exchange was possible. - The validation process was erroneously generating the message `Recursive type at (0,1)` for a particular API specification in RAML. - The fractional-seconds (`ff`) part of the date-time format `yyyy-mm-ddThh:mm:ss[.ff…​]` was not supported by the mocking service, which expected the format `yyyy-MM-dd’T’HH:mm:ss`. - The validation process would erroneously display an `Unresolved reference` error message for JSON schemas that referenced other JSON schemas by using relative paths. ## [](#2-6-0)2.6.0 **July 13, 2019** This release introduces two enhancements and fixes several issues. ### [](#enhancements-7)Enhancements - When you republish a project to Exchange, you now can edit the name only in Exchange. This enhancement prevents naming conflicts. Due to this change, three fields are disabled in the **Publish to Exchange** dialog when you republish a project: **Name**, **Group ID**, and **Asset ID**. - The **Publish to Exchange** button is now disabled if your user ID does not have the role either of Exchange Contributor or Exchange Administrator. Disabling the button prevents you from filling in the **Publish to Exchange** dialog only to receive an error message if your user ID does not have a required role. ### [](#fixed-issues-73)Fixed Issues - Design Center presented a false positive Warning message of different values for the `discriminator` value. - AMF showed a Warning message of an unused parameter when using the declared `uriParameter` in a resource type. - In an AMF implementation, using `NamedExample` inside a NamedExample did not work with Exchange and API Designer. - Design Center allowed the first line in a RAML API definition document to be blank. - The \[object Object\] error shows up when typing a path to a filename and referencing a directory. ## [](#2-5-0)2.5.0 **June 15, 2019** This release introduces several new features in the visual editor. ### [](#new-features-in-the-text-editor)New Features in the Text Editor - You can now import binary files, such as PDF and PNG files, into your projects. Such files are not parsed and no preview for them is available. - Use behavioral headers with the mocking service to modify in various ways how the mocking service behaves. See [Add Behavioral Headers to Simulated API Calls](https://docs.mulesoft.com/design-center/apid-behavioral-headers). ### [](#new-features-in-the-visual-editor)New Features in the Visual Editor - Create security schemes for your API specifications. The different supported types are OAuth 1.0, OAuth 2.0, Basic Authentication, Digest Authentication, and Pass Through. - Define union types for elements. In previous releases, you could select only one data type at a time for properties, bodies, payloads, headers, and any other kind of element. Now, you can choose multiple data types to create _union_ data types for any of those elements. When creating a union type, you won’t be able to edit any custom properties of the union type itself. An instance of the data type should meet all restrictions of at least one of the super types. - Define enums for strings and numbers. - Specify display names for methods. - Add groups to help you organize assets in the left pane. ### [](#enhancements-8)Enhancements - When you are using Microsoft Internet Explorer or Microsoft Edge as your browser and you click **Design Center** or the hamburger menu in the top-left corner as you are using the text editor, there is no longer a browser pop-up asking whether you want to leave the page. - It is now possible to view inline documentation for errors if you are using Microsoft Internet Explorer, Microsoft Edge, or Mozilla Firefox as your browser. Click the information icon that appears next to error messages. ### [](#fixed-issues-74)Fixed Issues - Changes made in the text editor might take up to six minutes to be parsed. - In the text editor, creating a fragment in an API-specification project, leaving the fragment without content, and then adding a reference to it from the main file before adding content to the fragment, caused the reference to be parsed as an error. - Underscores, spaces, and hyphen were not parsed as separator characters in variables in resourceTypes. - It was possible to create API specifications without the appropriate entitlement. - Very long names of API-specification projects are now better supported. If the name of a branch does not appear because the name of a project is too long, you can move your mouse over the path of the branch to see the full path. If the name of a project is too long to be seen all at once in the **Publish API Specification to Exchange** dialog, you can scroll though the field in which the name appears. - When an API specification included the definition of a type with an `!include` tag and the example of the type was also included with an `!include` tag, then the following message appeared: `should have required property '' at .raml` Here are examples of an API specification, a data type, and an example that would produce this error: API specification #%RAML 1.0 title: ac-dgt-xcpr types: DigitalProfileCreateRequest: type: !include dataType.raml examples: DigitalProfileCreateRequest\_Example: !include example.raml /profiles: post: body: application/json: DigitalProfileCreateRequest Data type #%RAML 1.0 DataType type: object properties: customerProfile: type: object properties: password: type: string Example #%RAML 1.0 NamedExample "customerProfile": { "password": "abc123" } - For certain API specifications, the API console was not appearing. - Not all types were being displayed in the list of types in the API console. - When a specification defines a boolean value but does not provide a default value, the API console now provides a default value. Doing so prevents problems from arising with the mocking service. - In some cases, an API-specification project might never finish loading when an attempt was made to open it. - API specifications that included binary files were not displayed properly in Exchange after being published. To ensure that binary files appear properly for API specifications that were created in previous releases of API Designer, follow these steps: 1. Delete the binary file from your API-specification project. 2. Import the binary file again into your project. 3. Publish the specification to Exchange again, making sure to increment the version number. - In some cases, references could not be resolved when examples were included. The error message was confusing and gave little information about the cause. ## [](#2-4-8)2.4.8 **May 18, 2019** This release introduces three new features and an enhancement, and it fixes several issues. There is also one known issue. ### [](#new-features-19)New Features - The visual API editor now supports union datatypes and enums. - An information icon now appears after error messages that are related to problems with named examples. Click the icon for a description of such errors and of ways to resolve them. - There is a new dialog that asks you to confirm whether you want to delete a branch. ### [](#enhancement-4)Enhancement The dialog for creating projects in API Designer has been redesigned for a simpler experience. ### [](#fixed-issues-75)Fixed Issues - When a datatype was declared as the union of an object type with an array type, the API editor returned an incorrect parsing error. - When a datatype was declared as a union in the last `type` entry of a `types` declaration, the API console did not display the datatype. For example, the datatype `unionType` that is declared in the specification `Test types` below would not appear in the API console because it is the last `type` declared in the list of `types`. #%RAML 1.0 DataType # This file is located at DataTypeA.raml type: object additionalProperties: false properties: a: type: string #%RAML 1.0 DataType # This file is located at DataTypeB.raml type: object properties: a: type: number b: type: string #%RAML 1.0 title: Test types types: A: type: !include DataTypeA.raml B: type: !include DataTypeB.raml unionType: type: A | B /events: /device: get: body: application/json: type: unionType However, if you moved the declaration of `unionType` (as in the example below), then `unionType` would appear in the API console. #%RAML 1.0 title: Test types types: A: type: !include DataTypeA.raml unionType: type: A | B B: type: !include DataTypeB.raml /events: /device: get: body: application/json: type: unionType - The `title` facet was allowed in RAML Library fragments, even though this facet is invalid in fragments of that type. - The Javascript exception `Maximum call stack size exceeded` was thrown when an API specification contained a recursive datatype reference. - The error message `Syntax error, generating empty array at…​` appeared when an array type was included in the declaration of a union type by means of a type expression, as in this example: #%RAML 1.0 title: Example types: a1: type: string\[\] /samples: post: responses: 200: body: application/json: type: string | a1 - Importing an API specification from Exchange would overwrite newer versions of existing assets in a project. These steps reproduced the problem: 1. Create a RAML fragment and publish it as version 1.0.0 to Exchange. 2. Create a RAML API specification, import the fragment, and publish the API specification to Exchange. 3. Open the RAML fragment created in step 1, edit it, and publish it as version 1.0.1. 4. Create a new project and RAML API specification, import version 1.0.1 of the fragment. 5. In the project, import from Exchange the RAML API specification created in step 2. The version of the RAML fragment that is being used in the project is now 1.0.0, rather than 1.0.1. - In the visual API editor, it was not possible to drag resources and data types into groups in the left pane of the editor if you were using Microsoft Internet Explorer. ### [](#known-issue-2)Known Issue If you are not using Google Chrome or Mozilla Firefox as your web browser when using the API editor, clicking an information icon that appears next to an error message does not open a window to display information about the error. ## [](#2-4-6)2.4.6 **April 20, 2019** This release includes two new features and several fixes. There is also one known issue. ### [](#new-features-20)New Features - You can now import projects directly from Exchange. You no longer have to download a project from Exchange to your computer or other location, and then import it into a new project in API Designer. See [Import Files into an API Project](https://docs.mulesoft.com/design-center/design-import-files) for the steps. - If you define a global media type in a specification in the visual API editor, you no longer are required to select a media type when you define the body of a response for a method. Instead, you can now leave the option `default` specified. This option is available only if a global media type is defined. ### [](#fixed-issues-76)Fixed Issues - Specifications that were several MB in size could not be published to Exchange. Now, for both the importing of projects from Exchange and the publishing projects to Exchange, the .zip files are reduced in size, preventing such errors. - Resource types and traits in API specifications that were written in RAML 1.0 were not being validated. - A project might never finish loading if you created the project in the visual API editor, created a data type in that project, closed the project, and then attempted to reopen the project. - The API editor returned the error message `Recursive type at (_x_, _y_)` for recursive DataType definitions. - The mocking service would fail if an API specification used the `example` facet, rather than the `examples` facet, to include a NamedExample fragment. - The API console might display all examples for all methods that were in a specification, not just the examples for the selected method. ### [](#known-issue-3)Known Issue Because of a bug in a third-party library that is used for the validation of XML against an XSD schema, the API editor can be inconsistent in displaying the error message `Could not validate XSD schema`. For example, you might or might not see the error message whenever you open a particular file that contains XML. ## [](#2-4-5)2.4.5 **April 6, 2019** This release includes a new feature, two enhancements, and two fixes. ### [](#new-feature-8)New Feature The editor now caches validations that are made by the AMF parser. (This parser was released on January 10 this year in the 2.4.0 release. See the release notes for 2.4.0 for more details about it.) Every time a file was opened in previous releases, the AMF parser would validate the file; during the validation, the API console would not appear in the right-hand pane of the editor. Now, opening a file does not cause the AMF parser to validate it. Therefore, the API console appears immediately whenever you switch to another file in a project. Any change to a project — typing, importing a file, or other actions — clears the project’s cache and triggers the AMF parser to validate the project again. ### [](#enhancements-9)Enhancements - The usability of the feature for forking projects is improved. - The navigation bar at the top of API Designer is now consistent with the navigation bars in other tools within Design Center. ### [](#fixed-issues-77)Fixed Issues - The option **API is behind a firewall**, which you can toggle on and off by clicking the shield that is on the left side of the toggle for the mocking service, was not functional. - The validation of headers was not occurring when the headers were defined in RAML files that were included as dependencies from Anypoint Exchange. - API Designer did not release a user’s lock on a project branch if the user left the project in the API editor by clicking the hamburger icon (the stack of three horizontal bars) in the top-left corner of the screen. Subsequently, no other user could edit the project branch until the previous user opened the project, opened the branch, and then left the project by clicking **Design Center** to the right of the hamburger icon. ## [](#2-4-4)2.4.4 **March 23, 2019** This release fixes six issues. ### [](#fixed-issues-78)Fixed Issues - When you are working on an API fragment, the editor now no longer displays the switch to turn on the mocking service. - When the documentation displayed in the **Documentation** pane contains more lines than the pane can accommodate, the pane does not display a scrollbar. Therefore, it is not possible to see all of the documentation. - Properties that are defined as numbers in the body of an API appear as strings in the API console. - The mocking service might return a response in JSON, even though the specification defined responses to be in XML. - The mocking service responded with a `400 Bad Request` error if a RAML API specification defined a JSON type for an HTTP header. - The editor did not display an error message when a NamedExample fragment contained properties that the RAML specification does not allow. ## [](#2-4-3)2.4.3 **February 23, 2019** This release fixes two issues. ### [](#fixed-issues-79)Fixed Issues - The behavior of the **Import API Example** dialog was faulty, making a selection difficult. You can open this dialog when you first create an API-specification project by clicking the word "example" in the sentence "Start project from an existing example," which appears in the left pane of the editor - The mocking service created invalid OAuth redirect URLs. ## [](#2-4-2)2.4.2 **February 9, 2019** This release fixes a number of issues. ### [](#fixed-issues-80)Fixed Issues - When the Mocking Service was on, the right pane of the editor was not displaying examples of JSON types for request bodies. - The editor did not show errors when the facet `properties` was declared twice for a type. - The editor displayed the error message `Expecting !!str and !!int provided` when numbers were used as keys in type definitions and in named examples. - For type declarations such as the one in this example, the editor displayed an error message that said the example value should be a multiple of the value of the `multipleOf` key: #%RAML 1.0 DataType displayName: exampleType type: number multipleOf: 0.01 example: 19.99 - The editor displayed the following error message after parsing a RAML project that included an XSD schema: `The schema document '.xsd' cannot include itself` - MIME types are now validated as strings, not as regular expressions. - Auto-completion after elements such as `uses` and `!include` was not working, and suggestions for content to place after such elements were not being offered. ## [](#2-4-1)2.4.1 **January 25, 2019** This release includes enhancements and fixes a number of issues. ### [](#enhancements-10)Enhancements - **For projects created before January 10, 2019:** You can turn on or off the stricter validation that began with the 2.4.0 release on January 10, 2019. You might want to do so to work with in an API-specification project that was created before this date, but don’t yet have plans for resolving the messages that this validation displays. To turn this validation off, toggle the switch that is labeled **Show Strict Errors** in the top-right corner of the editor. The default is On. + Even if you toggle this validation off, the grace period in which you must resolve the messages is still in effect. The grace period lasts at least until January 10, 2020. - The documentation describes additional RAML problems that generate violation and warning messages since the 2.4.0 release. ### [](#fixed-issues-81)Fixed Issues - When a RAML specification uses an `example` facet was being used, rather than an `examples` facet, the API editor displays a message. In the previous release, the message was not clear. - Design Center was not using the latest version of the API Console. Therefore, the JSON type for request bodies was not appearing in the right-hand pane of the API editor. - In Firefox, the body of POST and PUT requests was not appearing when the mocking service was being used, preventing requests from being sent correctly. ## [](#2-4-0)2.4.0 **January 10, 2019** This release includes several enhancements and fixes a number of issues. ### [](#enhancement-5)Enhancement - The API editor (one of the two editors in Design Center’s API Designer) is now using the AMF parser. This parser checks for full conformance with the RAML specification (either 0.8 or 1.0) that is being used for an API specification. If you reopen in the API editor any RAML API specifications that have already been published, you might find that there are instances of stricter validation. The AMF parser is at version 2.0.0. - The Design Center now provides native support for OAS 2.0. To learn more, [see the documentation](https://docs.mulesoft.com/design-center/design-create-publish-api-specs). - The names of projects for API specifications and API fragments can now be as long as 64 characters. - The option to download a project in YAML is now replaced with the following options, which you can access by clicking the three dots next to the name of a specification in the left pane: - **Download as**: Downloads a RAML specification as an OAS specification, or an OAS specification as a RAML specification.

The downloaded file is not guaranteed to be a correct specification.
- **Convert**: Converts a RAML specification to an OAS specification, or an OAS specification to a RAML specification.

The converted file is not guaranteed to be a correct specification.
### [](#fixed-issues-82)Fixed Issues - A problem occurred in which an API specification could not be tested with the mocking service when OAuth 2.0 was used for security. Clicking **Authorize and Send** after filling in all of the required authentication information merely resulted in the message "Fill in the authorization form first". - The API editor did not detect that an incorrect JSON schema was being referenced. - The API console pane of the API editor was sometimes not being refreshed as different types were being selected. The same problem could occur as different responses were selected. - There were a few formatting problems in the information displayed in the API console pane. - Swedish characters were not supported in the Crowd release (November 2017). - If a RAML API specification contained a DataType that extended another DataType, the information shown in the API console pane about the extending DataType could sometimes be incorrect. - The API editor could take too long to resolve one or more DataType resources. During that time, the API console pane was blank. - When a RAML extension extended a file that used a library that was itself defined in a fragment, and the library included a trait with the `!include` tag, the API editor was unable to locate the trait. - If a RAML API fragment defined multiple properties as `: string | nil`, the API console pane did not display any information, or did so only after a long delay, after the API specification that referenced the fragment was opened. - If a project included a JSON schema, and that file itself included another JSON schema, Design Center failed to load the second schema. - The API editor was requiring the media type to be declared for message bodies, even though the RAML specifications state that `mediaType` is optional for `body` nodes. - If you tried to import a Swagger 2.0 JSON file that contained an array of objects, Design Center threw a parsing error. - The mocking service was not presenting a choice of authentication methods when a basic `securityScheme` was being referenced from a library RAML fragment. - It was possible for projects imported into Anypoint Studio from the API editor in Design Studio to contain RAML errors that were not pointed out by the API editor. - RAML errors not reported by the API editor could cause problems in the API console pane, such as failures to display various pieces of information. - If a `uses` node specified an invalid path to a library, the API editor displayed this unhelpful message: Cannot read property 'ast' of null at (1, 0) The message has been improved. - The API editor was allowing a blank line as the first line in RAML files. - For very large API specifications, validation and the appearance of the API Console in the API editor could require much more time than usual. - If an endpoint were simply `/`, the API editor would throw a parsing error. - In the API console of the API editor, query parameters did not appear after you clicked the **Try It** button. - In the API editor, changing the version number of an API specification that you were publishing to Exchange would change the value of all instances of the "version" keyword in the specification. Only the value for the root instance should have been changed. - When a custom datatype was declared as Int64, the range declared for the datatype was not validated. For example, the mistake in this definition — declaring a maximum value that is too high for Int64 values — was not caught: my\_int64: type: integer format: int64 minimum: 1000000000000000000 maximum: 9999999999999999999 - Using double angle brackets (double chevrons) enclose a parameter name in resource type and trait definitions was not supported in the API editor. - Some valid regular expressions in the RAML "pattern" element were unsupported in the API editor. - In some cases, publishing an API specification to Exchange from the API editor would result in the content of the API specification being reordered incorrectly in the editor. ## [](#2-2-9)2.2.9 **August 9, 2018** This release contains an enhancement. ### [](#enhancement-6)Enhancement If your organization contains more than one group ID, you can now select the group ID to associate an API specification with when you publish that specification to Anypoint Exchange. ## [](#2-2-8)2.2.8 **July 26, 2018** This release introduces a change and fixes for several issues. ### [](#enhancement-7)Enhancement The text editor now supports the following structure for the declaration of a `baseUri` in specifications that are written in RAML 1.0: ```raml baseUri: value: http://www.example.com/api ``` ### [](#fixed-issues-83)Fixed Issues - OAS files with identical names were allowed to be imported. There was no check to find out whether existing OAS 2.0 files in a project already had the same name as an OAS 2.0 file being imported. - The `protocols` node was not being validated either in the text editor or in the visual editor. - Error messages were not appearing for invalid `examples` nodes. Here is an example of an invalid `examples` node: ```raml title: New API types: ids: type: object properties: identification: type: string examples: - MuleSoft - Salesforce ``` The correct way to define this `examples` node would be as follows: ```raml title: New API types: ids: type: object properties: identification: type: string examples: id1: MuleSoft id2: Salesforce ``` The symbol `-`, which is used incorrectly in the invalid `examples` node is used for defining elements in arrays, as in this example: ```raml title: New API types: ids: type: object properties: identification: type: array examples: id1: - MuleSoft - Salesforce id2: - Mule - CRM ``` - Uploading an API-specification project by using `anypoint-cli` resulted in the following message if the project contained a large number of files: `Error: Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: Could not open connection` - Importing an OAS 2.0 file that used parentheses in its name resulted in an error, but the error message did not explain the problem well. - The conversion of an OAS 2.0 file to RAML, which takes place when an OAS file is imported, resulted in the `required` field in the properties of response objects being set to `false` even when the value in the OAS file was `true`. - Attempts to import either RAML files or OAS 2.0 files via URL failed. If you tried to import a RAML file via URL, the file appeared empty in the text editor. If you tried to import an OAS 2.0 file via URL, the **Import** dialog would display the error message `Invalid OAS document`. - When switched on, the mocking service could incorrectly insert the URI to the mocking server. - It was possible to import an example into an API-specification project that was in read-only mode. - If in the text editor you clicked the plus sign in the left sidebar, selected **Other** in the **Add New File** dialog, and then clicked **Create** without specifying a name for the file, a new file with the name `*/` appeared in the file list. It was not possible to delete that file. ## [](#2-2-7)2.2.7 **May 16, 2018** This release fixes these issues: - Supplying a base URI parameter in the visual editor, using the parameter in a base URI, closing the visual editor, and then reopening the project resulted in an error message and a blank middle panel. - Selecting the type Number for a new Data Type in the visual editor, specifying a format, and changing the type to Integer resulted in the RAML viewer still including the specified number format. - In the visual editor, changing the type for a base URI parameter caused the RAML viewer to show the new type, but the **Type** field continued to show the previously selected type. ## [](#2-2-6)2.2.6 **April 20, 2018** This release fixes these issues: - Attempts to import OAS JSON files would result in this error message being displayed: `Cannot read property 'hasOwnProperty' of null` Such files could also fail to be converted by the JSON-to-RAML online conversion tool. - Some warning and error messages were not being displayed. ## [](#2-2-5)2.2.5 **April 6, 2018** This release includes two enhancements and fixes an issue. ### [](#enhancements-11)Enhancements - The left sidebar of the editor now lists groups, their resources, and their datatypes. - An example API to use in the visual editor is now available from a link in the left sidebar. ### [](#fixed-issue-2)Fixed Issue The word "type" could not be used as the name of a property in a RAML API specification. ## [](#see-also)See Also - [Troubleshooting](https://docs.mulesoft.com/design-center/design-troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # API Experience Hub Release Notes API Experience Hub is an API management platform and digital experience that enables organizations to create vibrant API ecosystems within and outside the enterprise. API providers can share, promote, and engage with their developer community. Developers and partners can find, explore, and consume APIs designed anywhere from a single place. The following release notes are provided for API Experience Hub: - [Anypoint API Experience Hub Release Notes](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes) ## [](#see-also)See Also - [API Experience Hub の概要](https://docs.mulesoft.com/jp/api-experience-hub/) - [Known Issues](https://help.salesforce.com/s/issues) # API Functional Monitoring (AFM) Release Notes These release notes cover the following versions of this product: ## [](#2-10)2.10 **October 8, 2026** ### What’s New - BAT CLI installation on Linux and macOS now uses a ZIP-based method instead of a remote install script. You download the BAT CLI ZIP file and run a local shell command to extract and install it under `$HOME/.bat`. For more information, see [BAT のインストール](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-install-task). ## [](#2-9)2.9 **August 3, 2026** ### What’s New - API Functional Monitoring now supports Mule Runtime 4.9 LTS (Java 17) for private locations. This update ensures continued security and compatibility as Mule Runtime 4.4 LTS reaches End of Life. - The BAT CLI now requires Java 17 on Linux, MacOS, and Windows WSL environments. ### Compatibility
Software Version

Mule Runtime

  • 4.9 LTS (Java 17): Supported. No action required.

  • 4.6 LTS: Supported. Plan upgrade before end of support.

  • 4.4 LTS: End of Life. No longer supported. Immediate upgrade required.

Java

Java 17 (Linux, MacOS, Windows WSL)
Running private location monitors on an End-of-Life runtime poses security risks and is not supported. If your private locations use Mule Runtime 4.4, upgrade to Mule Runtime 4.6 or 4.9 immediately.
## [](#2-8)2.8 **March 20, 2024** ### What’s New - You can now choose Cloudhub 2.0 servers as a deployment target. + For more information, refer to [Create a Private Location](https://docs.mulesoft.com/jp/api-functional-monitoring/afm-monitoring-private-apis). ## [](#2-7)2.7 **July 11, 2023** ### What’s New The BAT playground is now integrated into the API Functional Monitoring UI. You can select from a menu of example tests in the Functional Monitoring editor when creating a monitor. See [テストの記述の開始](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-write-tests-task). ## [](#2-6)2.6 **February 1, 2023** ### What’s New The UI component contrast is now increased for better visibility and accessibility. ## [](#2-5)2.5 **December 15, 2022** ### What’s New - The **Validate SSL Certificate** option for safe self-signed certifications is now toggled on by default for each of a monitor’s endpoints. The option is now set for each endpoint rather than for the entire monitor. To allow unsafe self-signed certifications for an endpoint, you must toggle **Validate SSL Certificate** off for that endpoint. - You can now log in to Anypoint Platform through a connected app using the BAT CLI login command. This provides an alternative way to log in using MFA (multi-factor authentication), so that a second factor is not required. MFA is now required for non-SSO accounts unless they are on your organization’s exemption list. ## [](#2-4)2.4 **November 15, 2022** ### What’s New - API Functional Monitoring is now integrated with the New Relic Metric API instead of the New Relic plugin for reporting test suite metrics. For more information, see [Configure and View Reports](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-reporting-task). ## [](#2-3)2.3 **October 27, 2022** ### What’s New - For improved security, to access the BAT playground you are now prompted to log in to your own secure Anypoint Platform account. ## [](#2-2)2.2 **August 2, 2022** ### What’s New - You can now log in through a proxy through the CLI using the `bat` command’s new `--useProxy` option. ### Fixed Issues
Issue Resolution ID

Inside a business group, you can now successfully create a private location if you have the proper permissions at this level.

W-11330456
## [](#2-1)2.1 **April 11, 2022** ### Fixed Issues
Issue Resolution ID

Switching between editors no longer infers assertion types incorrectly. A new drop-down was added in the assertions when creating a monitor. You can choose from String, Number, Boolean or Expression types. The drop-down eliminates adding quotes for string values in the form since quotes are now added in the code editor automatically. This enhancement does not impact existing monitors.

W-10647932
## [](#2-0)2.0 **August 6, 2021** MuleSoft announces the release of API Functional Monitoring 2.0. ### [](#new-features-and-enhancements)New Features and Enhancements The following new features and enhancements are introduced in API Functional Monitoring 2.0. You can now: - Create and edit BAT source via the new inline code editor. - Copy tests. - Run tests against endpoints prior to creating a monitor. Additionally, the **Monitor Detail** view has been redesigned, consolidating the following information: - Test duration - Daily average response times - A list of recent test executions - The test’s next run - Buttons for executing a test run, viewing monitor history, editing a monitor, downloading a monitor, and deleting a monitor ## [](#1-21)1.21 **May 30, 2020** This release includes these enhancements: ### [](#enhancements-to-the-slack-reporter)Enhancements to the Slack reporter - The look and feel of notifications are improved. - Each notification now includes the name of the configuration used for the test execution. - The three following options are added to the Slack reporter: SEND\_NOTIFICATION\_IF\_PASSED Setting this option to `true` causes a notification to be sent if a test passes. AT\_HERE\_ENABLED Setting this option to `true` adds `@here` to a notification if a test fails. DISABLED\_FOR\_CONFIGS Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension. ### [](#enhancements-to-the-email-reporter)Enhancements to the Email reporter The two following options are added to the Email reporter: SEND\_NOTIFICATION\_IF\_PASSED Setting this option to `true` causes the email to be sent if the tests pass DISABLED\_FOR\_CONFIGS Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension. ### [](#enhancement-to-the-new-relic-reporter)Enhancement to the New Relic reporter The following option are added to the New Relic reporter: DISABLED\_FOR\_CONFIGS Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension. ### [](#enhancement-to-the-sumo-logic-reporter)Enhancement to the Sumo Logic reporter The following option are added to the Sumo Logic reporter: DISABLED\_FOR\_CONFIGS Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension. ### [](#enhancement-to-the-pagerduty-reporter)Enhancement to the PagerDuty reporter The following option are added to the PagerDuty reporter: DISABLED\_FOR\_CONFIGS Disables the reporter for one or more configurations. The value is the name of one configuration or multiple names that are separated by commas. Names do not include the .dwl file extension. ### [](#enhancements-to-private-locations)Enhancements to private locations - Updated to use Mule Runtime 4.3.0. - Updated Mule app dependencies. - Fixed an issue that generated infinite `bat` test executables in Mule-app filesystems. - Added log appenders to enable troubleshooting in CloudHub. ## [](#1-20)1.20 **February 8, 2020** This release introduces one enhancement: If you run a monitor online in Anypoint Platform (instead of through the BAT CLI), and you specify an email address for an email reporter to notify you of failed tests, each emailed report contains a link. The link opens the result of the failed test in the **Functional Monitoring** section of Anypoint Monitoring. ## [](#1-19)1.19 **December 7, 2019** This release introduces the following two new features: - Integration with Anypoint Secrets Manager When you write tests manually and run them with the BAT CLI, you can access shared secrets in Anypoint Secrets Manager within those tests, which enables you to securely store sensitive information, such as a password, authentication token, endpoint URL, or webhook URL. You must run the tests from a private location when you use shared secrets. For more information, see [BDD Test-Writing Syntax Reference](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-bdd-reference) and [Configure Reports of Test Failures](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-reporting-task). - Support for creating monitors for endpoints that use self-signed certificates When you create a monitor in the Anypoint Functional Monitoring section of Anypoint Monitoring, you can toggle the **SSL Certificate Validation** switch to off if the endpoints that your monitor will test use self-signed certificates. If they do use self-signed certificates and you do not toggle this switch off, tests against those endpoints fail. - If the toggle is on, all endpoints that use SSL certificates must have certificates that are signed by a trusted authority. - If the toggle is off, all endpoints that use SSL certificates must be self-signed. To test a combination of endpoints that use trusted SSL certificates and endpoints that use self-signed certificates, create two separate monitors: one for testing the first group of endpoints, the other for testing the second group of endpoints. ## [](#1-17)1.17 **October 5, 2019** This release introduces _private locations_, which enable you to monitor private (system and process) APIs without allowing IP addresses. Private locations are namespaces in an instance of Anypoint Virtual Private Cloud (VPC) that is configured to allow workers to access your private network. AFM can create workers within that namespace that can run tests against APIs that are accessible only within the network that VPC is configured for. You can create multiple private locations in a single VPC. For more information, see [Monitoring the Endpoints of Private APIs](https://docs.mulesoft.com/jp/api-functional-monitoring/afm-monitoring-private-apis). ## [](#1-16)1.16 **July 27, 2019** This release introduces one new feature in the interface for Anypoint Monitoring: you can now create new tests that are based on existing tests for monitors in Anypoint Monitoring. For details, see [Create a New Test from an Existing One](https://docs.mulesoft.com/jp/api-functional-monitoring/afm-in-anypoint-platform). ## [](#1-15)1.15 **June 15, 2019** This release introduces one new feature: you can now get notifications of failed tests through email. Select **Email** as the reporter in API Functional Monitoring in Anypoint Monitoring, or set up email as a reporter in the BAT CLI. See [Create a Monitor](https://docs.mulesoft.com/jp/api-functional-monitoring/afm-create-monitor) for instructions about using API Functional Monitoring in Anypoint Monitoring, and see [To Configure and View Test Reports](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-reporting-task) for details about creating reporters in the BAT CLI. ## [](#1-1)1.1 **July 12, 2018** This release introduces an enhancement and a new feature. ### [](#enhancement)Enhancement When you create a monitor in the **Functional Monitoring** section of Anypoint Monitoring, you can now specify more than one endpoint to test and more than one assertion per endpoint. ### [](#new-feature)New Feature You can write and run BAT tests in IntelliJ IDEA with the support of the DataWeave 2.0 IntelliJ plugin. For details, see [Write and Run BAT Tests in IntelliJ IDEA](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-intellij-idea). ## [](#1-0)1.0 This release introduces a new user interface that is incorporated into Anypoint Monitoring. To access this user interface, select **Functional Monitoring** after opening Anypoint Monitoring. For documentation about this new user interface, see [API Functional Monitoring in Anypoint Monitoring](https://docs.mulesoft.com/jp/api-functional-monitoring/afm-in-anypoint-platform). You can still create tests and schedule them using the BDD Test-Writing Language and the Blackbox Automated Testing (BAT) CLI. The documentation for doing that is located at [API Functional Monitoring with the Blackbox Automated Testing (BAT) CLI](https://docs.mulesoft.com/jp/api-functional-monitoring/bat-top). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # API Functional Monitoring Release Notes Use API Functional Monitoring to perform consistent testing of the functional behavior and performance of APIs throughout the API lifecycle, in testing and production environments. The following release notes are provided for API Functional Monitoring: - [API Functional Monitoring (AFM) Release Notes](https://docs.mulesoft.com/jp/release-notes/api-functional-monitoring/api-functional-monitoring-release-notes) ## [](#see-also)See Also - [API 機能監視の概要](https://docs.mulesoft.com/jp/api-functional-monitoring/) - [Known Issues](https://help.salesforce.com/s/issues) # API Gateway Extensions Release Notes Release notes for API Gateway Extensions include information about changes, improvements, and resolved issues in each extension version. ## [](#release-notes-for-mule-4-extensions)Release Notes for Mule 4 Extensions - [OAuth2 Client Store](https://docs.mulesoft.com/jp/release-notes/api-gateway-extensions/api-gateway-oauth-client-store) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # API Gateway OAuth2 Client Store ## [](#2-1-0)2.1.0 **Apr 25, 2024** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.2.0** ### What’s New - Client Store is now compatible with Java 17. ## [](#2-0-0)2.0.0 **Jun 30, 2023** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.2.0** ### [](#fixed-issues)Fixed Issues - Changed the client retrieval endpoint from contract services. For this change to take effect it must be used in conjunction with runtimes 4.3.0-20230417, 4.4.0-20230417 and Mule OAuth Provider 1.0.11 or newer versions. ## [](#1-0-2)1.0.2 **May 19, 2022** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.2.0** ### [](#fixed-issues-2)Fixed Issues - Updated Mule OAuth Provider module version from 1.0.3 to 1.0.8. ## [](#1-0-1)1.0.1 **August 04, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.2.0** ### [](#fixed-issues-3)Fixed Issues - Fixed Anypoint Studio integration. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # API Manager 2.x Release Notes API Manager release notes include information about changes, new features, improvements, and resolved issues in releases of API Manager. ## [](#2-5-32)2.5.32 **October 21, 2026** ### What’s New - API Manager now supports creating API instances from OAS 3.1 API specifications for Mule Gateway and applying policies to them. For more information, see [OpenAPI Specification Support Release Notes](https://docs.mulesoft.com/jp/release-notes/platform/oas3). **October 19, 2026** ### What’s New - API Manager now supports enabling different versions of the same policy on a single API instance. - Sensitive fields are now redacted from audit log entries for policy operations (enable, disable, edit, and create). - Managed Gateways now support configuring OpenTelemetry log output and selecting a custom tracing provider. - The key metrics panel in API Manager now links to the Anypoint Monitoring page in the enhanced experience. ### Fixed Issues
Issue Resolution ID

Contract creation no longer fails when an API has more than 100 tiers.

W-19808895

Public API instances are now displayed correctly in the public portal.

W-21151907

Users with API Manager permissions (API Creator, View APIs Configuration, Edit APIs Configuration, or Manage Policies) can now create and manage LLM proxies without requiring the Organization Administrator role. Model names now display correctly in Model Wallets and Model Proxies for these users.

W-24194029
## [](#2-5-31)2.5.31 **August 13, 2026** ### What’s New - The model proxy now uses the embedding provider from the selected Semantic Service configuration when creating prompt topics. ### Fixed Issues
Issue Resolution ID

Mule proxies deployed to CloudHub 2.0 private spaces now preserve the customer-defined ingress configuration.

W-21464257
## [](#2-5-30)2.5.30 **May 14, 2026** ### What’s New - API Manager now includes a DataWeave expression validator in policy configurations, helping you identify and avoid common errors when writing expressions. - The model proxy now supports advanced semantic routing using vector database providers, enabling intent-based routing of LLM requests to the appropriate model. - The model proxy now supports the Nvidia Nemotron model. - OAuth configuration in the model proxy now supports DataWeave expressions for dynamically retrieving client LLM provider keys. - The model proxy monitoring dashboard now shows token usage broken down per LLM provider. - The MCP Bridge now supports updating existing MCP Bridge servers. ## [](#2-5-29)2.5.29 **April 20, 2026** ### What’s New - API Manager now supports agent verification using GoDaddy Agent Name Service (ANS), enabling you to validate domain ownership and establish a trusted identity for your agents. To learn more, see [api-manager::godaddy-ans-registration.adoc](#api-manager::godaddy-ans-registration.adoc). ## [](#2-5-28)2.5.28 **March 30, 2026** ### What’s New - API Manager now supports model proxies, allowing you to manage and govern interactions with multiple large language models (LLMs) providers through API Manager. To learn more, see [general::model-proxy.adoc](#general::model-proxy.adoc). ## [](#2-5-27)2.5.27 **March 16, 2026** ### What’s New - API Manager now supports managing gRPC APIs as API instances when the API is published as a gRPC asset in Anypoint Exchange and deployed using Omni Gateway. ## [](#2-5-26)2.5.26 **March 6, 2026** - API Manager now supports creating an MCP Bridge to expose API instances as an MCP server. See [api-manager::create-instance-task-mcp-bridge.adoc](#api-manager::create-instance-task-mcp-bridge.adoc). ## [](#2-5-25)2.5.25 **February 13, 2026** ### Fixed Issues
Issue Resolution ID

Mule proxies deployed to CloudHub 2.0 private spaces from API Manager no longer have the public endpoint disabled by default.

W-17293229
## [](#2-5-24)2.5.24 **January 23, 2026** ### What’s New - You can now create and manage instances for publicly available MCP servers in API Manager. These assets are published to Exchange under Provided by MuleSoft and are maintained by their original providers, not by MuleSoft. When you create an instance from a publicly available asset, the instance is created within your private organization and managed like any other instance in API Manager. For more information, see [Adding an MCP Server Instance from Public Exchange](#api-manager::create-instance-public-exchange.adoc). ## [](#2-5-23)2.5.23 **December 17, 2025** ### What’s New - You can now import client applications from Okta client providers into API Manager and use them to request access to API instances. For details, see [Import Client Applications from Client Providers](#api-manager::import-client-applications.adoc). ## [](#2-5-22)2.5.22 **December 11, 2025** ### What’s New - You can now configure the same API-level or automated policy more than once on a single API instance. For details, see [Apply Duplicate Policies](https://docs.mulesoft.com/gateway/latest/policies-reorder#apply-duplicate-policies). - Policy templates now support an optional `assetTypes` field in their capabilities (`http`, `rest`, `wsdl`, `a2a`, `mcp`, `llm`, `grpc`). When this field is defined, the policy can only be applied to assets whose endpoint type matches one of the specified values. - Automated policies now support an optional `endpointTypes` field in their application rule. If the associated policy template defines `assetTypes`, the `endpointTypes` value must be a subset of those asset types. Automated policies apply only to assets whose endpoint type is included. ## [](#2-5-21)2.5.21 **November 10, 2025** ### What’s New - API Manager now prevents applying deprecated policy template versions from Exchange and clearly flags existing policies that use deprecated versions. ## [](#2-5-20)2.5.20 **October 3, 2025** ### What’s New - API Manager now supports managing brokers, MCP servers, LLMs, and agents. - TLS 1.0 and 1.1 support is removed for enhanced security compliance. ## [](#2-5-19)2.5.19 **October 1, 2025** ### What’s New - You can now filter the API list by endpoint type. - You can now select API assets from other business groups you have access to when creating new instances. ## [](#2-5-18)2.5.18 **September 22, 2025** ### What’s New - API Manager now includes comprehensive entity limits documentation, providing clear information about API policies, groups, SLA tiers, and automated policy configurations. See [API Manager Entity Limits](https://docs.mulesoft.com/jp/api-manager/latest/limits#api-manager-entity-limits). ## [](#2-5-17)2.5.17 **September 4, 2025** ### What’s New - API Manager now includes a link to test DataWeave expressions in the Anypoint DataWeave Playground when configuring policies. - This release contains accessibility improvements in the UI. ## [](#2-5-16)2.5.16 **July 25, 2025** ### What’s New - API Manager now allows requiring manual approval when adding an API instance. - Resource Level Policies for Omni Gateway now support case-insensitive URI patterns using the `(?i)` flag, allowing regex-based policies to match URIs regardless of letter casing. ## [](#2-5-15)2.5.15 **June 27, 2025** ### What’s New - API Manager now supports publishing an Omni Gateway SOAP API instance by uploading a WSDL file for your SOAP API. See [Flex Gateway API インスタンスの追加](https://docs.mulesoft.com/jp/api-manager/latest/create-instance-task-flex). ## [](#2-5-14)2.5.14 **June 3, 2025** ### What’s New - Mule API Analytics is now replaced by [Anypoint Monitoring](https://docs.mulesoft.com/jp/monitoring/). Use Anypoint Monitoring to monitor APIs effectively. Contact your MuleSoft representative for more information. ## [](#2-5-13)2.5.13 **May 28, 2025** MuleSoft announces API Manager support for Model Context Protocol (MCP) and Agent2Agent (A2A) Protocol through Omni Gateway. ### What’s New - API Manager now supports publishing Omni Gateway MCP and A2A server instances, enabling you to secure, manage, and govern agent interactions. To learn more, see: - [Omni Gateway Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes) - [Securing Agent Interactions with Omni Gateway](https://docs.mulesoft.com/gateway/latest/agent-secure) - [api-manager::create-instance-task-agent-tool.adoc](#api-manager::create-instance-task-agent-tool.adoc) ## [](#2-5-12)2.5.12 **May 15, 2025** ### What’s New - Automated policies can now be reordered from the Automated Policies configuration page. - The Upstream Service limits per API is now increased to 100 for Omni Gateway. ## [](#2-5-11)2.5.11 **April 30, 2025** ### Fixed Issues
Issue Resolution ID

Deployments to Flex Gateway no longer fail if users trigger them without secret access permissions.

W-17566778

Contract status no longer changes when a team owns the application.

W-18034262

You can now access the correct documentation pages from links in the UI.

W-17865398
## [](#2-5-10)2.5.10 **February 18, 2025** ### What’s New - Patch operations to existing API portals are no longer supported. For more information, see se [API Experience Hub](https://docs.mulesoft.com/jp/api-experience-hub/). - Application responses no longer contain unsolicited owner information. - Flex Gateways now report their status as `Running` or `Not Running` instead of `Connected` or `Disconnected`. - The user owner search UI now includes a username field. - You can now change policy versions when editing Automated Policies. ## [](#2-5-9)2.5.9 **November 12, 2024** ### What’s New - Now, when the first request from a Mule API Gateway to API Manager is performed for a particular API, API Manager makes an initial setup with the provided information. NOTE: If additional requests are received for the same API during this setup, the Gateway will receive a 429 error status. - The Service Mesh End Of Life creation blocker is now active. - Customers without a CloudHub entitlement cannot deploy proxy applications through API Manager. ## [](#2-5-8)2.5.8 **November 1, 2024** ### What’s New - Teams can now be client application owners. ## [](#2-5-7)2.5.7 **October 31, 2024** ### What’s New - Service Mesh is scheduled for End of Life on May 21, 2025. To integrate your micro services with Anypoint Platform, use [Flex Gateway](https://docs.mulesoft.com/gateway/latest/) instead. ## [](#2-5-6)2.5.6 **October 30, 2024** ### What’s New - The automated policy list is now shown in order of application. ### Fixed Issues
Issue Resolution ID

The API list now shows the correct states for Flex Gateway APIs.

W-17015895
## [](#2-5-5)2.5.5 **October 16, 2024** ### What’s New - You can now view more owners by default on the Client Applications page. - You can now apply policies to APIs deployed to Flex Gateway, even if the Gateway version is unknown (because no replicas are connected). - You can now see APIs with multiple upstreams in the Project View. - You can now create self-managed server APIs using the API wizard. - You now see a notification for API Manager 1.x end of life on organizations that have unclassified APIs. - You can now use both internal and external client providers within the same environment at the same time. For more information, see [クライアント管理用の複数のクライアントプロバイダーの設定](https://docs.mulesoft.com/jp/api-manager/latest/configure-multiple-credential-providers). ## [](#2-5-4)2.5.4 **October 7, 2024** ### What’s New - Now, when deploying an API with policies to Flex Gateway for the first time, policy implementations are pinned. - Now, if a user attempts to change the Flex Gateway version where an API is deployed, and one of the applied policies is not compatible with the new target, the operation is rejected. - Now, When changing the Flex Gateway version, if an Automated Policy currently covering the API is lost, the user is now warned and can choose to either proceed or cancel the operation. ## [](#2-5-3)2.5.3 **October 1, 2024** ### What’s New - You can now see HTTP API instances in Governance reports, as well as AsyncAPI and REST API instances. - API Manager now includes a header `x-request-d` to include the internal trace ID. - Email URL functionality for contracts generated in API instances within sub-organizations is now operational. - You can now apply different versions of the same policy to various resources within the same API instance. - API instance SLA Tier limits are now validated to ensure that `maximumRequests` and `timePeriodInMilliseconds` are integers. - You can now see the SLA Tier in the client application page for APIs from environments. - Now, only users with environment or organization credentials are able to export API instances policies with sensitive fields. ### Fixed Issues
Issue Resolution ID

You can now see new implementations when using the Check for implementation updates button for automated policies.

W-16619577
## [](#2-5-2)2.5.2 **August 27, 2024** ### What’s New - The API Key Metrics experience receives frequent updates. To ensure uninterrupted access, verify that [Anypoint Monitoring](https://docs.mulesoft.com/jp/monitoring/) is enabled: - CloudHub 2.0 and Runtime Fabric applications: Anypoint Monitoring is enabled by default. - CloudHub applications: Configure Anypoint Monitoring. See [CloudHub デプロイメントの監視のセットアップ](https://docs.mulesoft.com/jp/monitoring/configure-monitoring-cloudhub). - Hybrid Runtime applications: Install the Anypoint Monitoring Agent. See: [ハイブリッドデプロイメントの Monitoring のセットアップ](https://docs.mulesoft.com/jp/monitoring/am-installing). ## [](#2-5-1)2.5.1 **August 23, 2024** ### What’s New - Mule API Analytics will soon be replaced by [Anypoint Monitoring](https://docs.mulesoft.com/jp/monitoring/). Start transitioning to Anypoint Monitoring to monitor APIs effectively. Contact your MuleSoft representative for more information. - Audit logs now include a trace id. ### Fixed Issues
Issue Resolution ID

Modifying an API label for a hybrid proxy application now correctly updates the existing proxy application.

W-15838700

Users without FlexGateway entitlement are now able to publish split model custom policies.

W-16496236
## [](#2-5-0)2.5.0 **July 11, 2024** ### What’s New The following endpoint responses now include fewer fields, and the responses include no sensitive information: - [GET API Instance Contract by ID](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/api-manager-api/minor/1.0/console/method/%231674/) - [GET API Group Instance Contract by ID](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/api-manager-api/minor/1.0/console/method/%232394/) For information about which fields are now included in the responses for these endpoints, see the [API Manager API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/) documentation. ## [](#2-4-30)2.4.30 **June 11, 2024** ### What’s New - API Manager now limits the number of API Groups, API Group Versions, and API Group Instances per business group. Each business group can have a maximum of: - 1200 API Groups - 1200 API Group Versions - 2000 API Group Instances - This release contains accessibility improvements. ### Fixed Issues
Issue Resolution ID

Deploying an API proxy for the first time with an old policy implementation version now succeeds (and no longer returns HTTP status code 500).

W-15945517
## [](#2-4-29)2.4.29 **May 22, 2024** ### What’s New - When multiple Mule gateways are connected to the same API instance, API Manager now saves the highest gateway version. - This release contains accessibility improvements, including additional focus indicators and fixes for some contrast color issues. ### Fixed Issues
Issue Resolution ID

Policy incompatibilities are now calculated each time rather than only when the runtime or java version changes.

W-15467066

The correct Java version is now shown when creating Mule APIs.

W-15578441
## [](#2-4-28)2.4.28 **April 12, 2024** ### What’s New The following API Manager permissions are now available in Access Management: - **Manage Client Applications**: Enables users to create and manage client applications in the root organization. Users with this permission can view and modify application credentials and can add and remove client owners. - **View Client Applications**: Enables users to view client applications in the root organization. Users with this credential cannot view an application’s secrets and cannot modify applications. ## [](#2-4-27)2.4.27 **February 29, 2024** ### Fixed Issues
Issue Resolution ID

When editing APIs, Save & Apply is now disabled for users that don’t have the edit API permissions.

W-15040213

When configuring a new hybrid API instance in an environment where only Mule 3 targets are present, you can now select a Mule 3 target.

W-15102034
## [](#2-4-26)2.4.26 **February 15, 2024** ### Fixed Issues
Issue Resolution ID

When you promote a Hybrid API instance to a new environment, the API Summary now renders correctly.

W-15030396
## [](#2-4-25)2.4.25 **February 7, 2024** ### What’s New - You can now upgrade your policies and API proxies to Java 17. See [Upgrading Policies](https://docs.mulesoft.com/jp/general/java-support#policies) and [Upgrading API Proxies](https://docs.mulesoft.com/jp/general/java-support#api-proxies). ### Fixed Issues
Issue Resolution ID

When applying a resource-level policy to specific methods of the API instance, the URI template regex field no longer shrinks when you select multiple Method values.

W-14802785

When you promote a Hybrid API instance to a new environment, the API instance classification remains Hybrid and is no longer reclassified to Standalone.

W-14829827
## [](#2-4-24)2.4.24 **January 24, 2024** ### Fixed Issues
Issue Resolution ID

When applying an automated policy, the Rule of application selection now renders correctly.

W-14853129
## [](#2-4-23)2.4.23 **December 6, 2023** ### What’s New - Resource-level configuration options are no longer shown when applying a policy that does not support resource-level configurations. - The UI is now improved for accessibility by including the addition of alternative text for images, and alternative visual and non-visual indicators. - A warning is now displayed when policies are incompatible with the API runtime version. ### Fixed Issues
Issue Resolution ID

API Manager now properly redirects pre-crowd customers.

W-13783748
## [](#2-4-22)2.4.22 **October 27, 2023** ### What’s New API Manager now supports space selection for Mule API Proxies deployed to CloudHub 2.0. ## [](#2-4-21)2.4.21 **October 17, 2023** ### What’s New API Manager now supports Anypoint API Governance conformance reports for governed API instances. \+ To learn more about governing API instances, see: \+ **[Anypoint API Governance Release Notes](https://docs.mulesoft.com/jp/release-notes/api-governance/api-governance-release-notes)** [API インスタンスの管理](https://docs.mulesoft.com/jp/api-manager/latest/govern-api-instances) ## [](#2-4-20)2.4.20 **October 10, 2023** ### What’s New - Mule 4.4.x is now the default version for API proxies deployed to CloudHub, CloudHub 2.0, and Runtime Fabric. - For API instances deployed to CloudHub 2.0, the space name is now visible in the API Settings. - You can now dismiss Mule 3 end of life notifications for 14 days. - For API instances deployed to Flex Gateways version 1.5.0 or later, API Manager automatically sets the upstream’s **Weight** to 100% and disables the field when only one upstream service exists for that route. Adding an additional upstream to the route enables you to configure the upstream **Weight**. - This release contains accessibility improvements in the UI, including the addition of alternative text for images and alternative visual and non-visual indicators. ### Fixed Issues
Issue Resolution ID

For Flex Gateway HTTPs API instances sharing the same port, if one of the instances has an inbound TLS context applied, leaving the inbound TLS context blank for additional instances applied to the same port does not result in an error.

W-14162848
## [](#2-4-19)2.4.19 **August 23, 2023** ### What’s New - For requests made from Connected Apps, API Manager Audit logs now include the Connected App’s name and ID. - The **Mule API Analytics** tab is now visible to users with `View APIs Configuration` permission. - Some error messages are now improved for clarity. ## [](#2-4-18)2.4.18 **August 7, 2023** ### What’s New - External **Bad Request** (`400`) errors do not convert to **Bad Gateway** (`502`) errors. - This release contains accessibility improvements in the UI, including the addition of alternative text for images and alternative visual and non-visual indicators. ### Fixed Issues
Issue Resolution ID

You can now apply Mule 4 custom policies uploaded to Exchange via Maven as automated policies in an environment without APIs.

W-12369588
## [](#2-4-17)2.4.17 **July 20, 2023** ### What’s New - API Manager now supports API instances with multiple upstream services for Flex Gateway running in Connected Mode. For more information, see [Multiple Upstream Services for Flex Gateway Running in Connected Mode](https://docs.mulesoft.com/jp/api-manager/latest/create-instance-task-flex#traffic-management). - Deployments to deprecated Flex Gateway versions are now blocked. For information about Flex Gateway version support, see [Product Versioning and Back Support Policy](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) - This release contains accessibility improvements in the UI, including the addition of alternative text for images and alternative visual and non-visual indicators. ### Fixed Issues
Issue Resolution ID

Autocomplete for the Upstream URL field now works correctly. API Manager now only autocompletes the field when the page is first loaded and only if the information is available.

W-13735853

The Client provider field now shows the correct provider when editing an API instance.

W-13768260
## [](#2-4-16)2.4.16 **July 3, 2023** ### What’s New - When adding a new API instance, there are now separate pages for the upstream and downstream configuration settings. - When editing an API instance from the settings page, there are now separate sections for the upstream and downstream configuration settings. ## [](#2-4-15)2.4.15 **June 6, 2023** ### What’s New - Selecting an API instance from **API Administration** now navigates you to the new **API Summary** page instead of the API **Settings** page. The API **Key Metrics** and the API instance information such as the type, API version, and API instance ID now appear on the **API Summary** page. Only the runtime and endpoint configuration still appear on the **Settings** page. - In **API Administration**, the **Analytics** tab is now **Mule API Analytics**. ## [](#2-4-14)2.4.14 **May 23, 2023** ### Fixed Issues
Issue Resolution ID

The API Instance field now appears correctly when filtering client applications with Datagraph contracts.

W-12964876
## [](#2-4-13)2.4.13 **May 10, 2023** ### Fixed Issues
Issue Resolution ID

API Manager now correctly shows disabled policies.

W-13030137
## [](#2-4-12)2.4.12 **April 14, 2023** ### What’s New - Connected Apps can create and manage client applications. For more information, see [接続アプリケーションを使用したクライアントアプリケーションの作成](https://docs.mulesoft.com/jp/api-manager/latest/manage-client-apps-connected-apps-concept). - API status is now shown as active only when deployment is successful. - API Manager uses a standalone replica list to report configuration status based on the version of each connected replica. ### Fixed Issues
Issue Resolution ID

When a deployed API instance with policies applied is deleted, the policies are also deleted.

W-12779232
## [](#2-4-11)2.4.11 **March 28, 2023** ### What’s New You can deploy Mule Gateway proxy applications directly to CloudHub 2.0. ### Fixed Issues When applying policies to non-REST APIs, policies only applicable to REST APIs are not visible. ## [](#2-4-10)2.4.10 **February 22, 2023** ### What’s New For Flex Gateway running in Connected Mode, API Manager now supports: - Policy execution order For more information, see [Reordering Policies](https://docs.mulesoft.com/gateway/latest/policies-reorder). - TLS and mTLS context configuration For more information, see [Configuring TLS Context for Flex Gateway in Connected Mode](https://docs.mulesoft.com/gateway/latest/conn-tls-config). ## [](#2-4-9)2.4.9 **January 18, 2023** ### What’s New For API Instances, the **Implementation URI** and **Consumer endpoint** fields now: - Validate if the specified URL is a valid URL. - Support parameterization using `{}`, `<>`, or `<<>>`. ## [](#2-4-8)2.4.8 **November 8, 2022** ### What’s New Added TLS inbound and outbound support for RTF targets. ## [](#2-4-7)2.4.7 **November 2, 2022** ### What’s New The API Header on the settings page is improved for a better experience: - The API actions are now inside the **Actions** button in the page header title. - The API header is now only informative. The content in the API header is not editable, and the edit buttons were removed. The API instance label and API consumer endpoint fields editable in the API header are now only editable in the Endpoint configuration section following the API header. - For Mule 4 APIs, since the auto-discovery ID is the same as the API instance ID, the auto-discovery ID was removed for clarity. The API Manager docs are updated to highlight this change and instruct users where to find the API instance ID. - The API notification messages are now displayed at the beginning of the API header. ## [](#2-4-6)2.4.6 **October 17, 2022** ### What’s New Mule 3.8 and 3.9 EOL messages are shown in API Manager for: - APIs running on Mule 3.8, which has already reached end of life and whose extended support ended on **November 16, 2021**. - APIs running on Mule 3.9, whose standard support ended on **March 20, 2021**. Improved user experience over Flex 1.2.0 new features: - Adding port sharing validation. ## [](#2-4-5)2.4.5 **September 28, 2022** ### What’s New Flex Gateway information shown in API Manager has been enhanced as follows: - Flex Gateway data representation on API Manager charts is improved. - Message logs can now be viewed and downloaded in order from latest to oldest. - The message log streaming information now specifies log level, such as **Info**, **Warn**, and **Error**. ## [](#2-4-4)2.4.4 **August 25, 2022** ### What’s New The SLA Tiers, Contracts, and Client applications sections are improved for a better experience: - For SLA Tiers, the delete and deprecate actions are now found in the context menu at the end of each tier. - For Contracts: - The Pending tier change status is now named Approved (pending tier change). The current tier and requested tier can now be edited using the pencil icon without opening the application detail information. - The text in the column now changes from N/A to - when there is no current tier or requested tier. - The Refresh functionality is now added. - For Client applications: - The Pending contract column now shows the amount of pending contracts for each application. - Owners are now shown by email and not by name. - The Pending tag is now added to the drop-down options for APIs, API versions, API instances, group, group versions, and group instances to search for pending contracts easily. ### Fixed Issues - For Contracts: - The Status filter now considers all contracts for the api and not just the contracts shown in the current view. - The Requested SLA tier can now be changed when a contract is in the Approve (pending tier change) status. ## [](#2-4-3)2.4.3 **July 29, 2022** ### What’s New - API Manager now notifies you when policy implementations are incompatible with your current Flex Gateway version. - Applying a Message Logging policy to your API instance in API Manager allows you to view basic message logs for APIs managed by Flex Gateway within API Manager. ## [](#2-4-2)2.4.2 **July 28, 2022** ### What’s New - You can now sort by the **Error Rate** and **Total Requests** columns in the API Manager **API Administration** page. ## [](#2-4-1)2.4.1 **June 22, 2022** ### [](#new-features)New Features The alerts section has been improved for a better experience: - Clicking an alert will now show its details. To edit an alert, you can use the context menu icon. - Added an icon in the **State** column explaining each state in detail when you hover on it. ## [](#2-4-0)2.4.0 **May 2, 2022** MuleSoft announces the release of API Manager 2.4.0. ### [](#new-features-and-enhancements)New Features and Enhancements The following new features and enhancements are introduced in API Manager 2.4.0: - You can now manage Flex Gateway APIs. - The new API Wizard introduces a streamlined way to create APIs. - Policy and automated policy management have been improved. - The release introduces a new way to create custom policies for Mule 4 and Flex Gateway. - The behavior of some policies has changed. For example, The IP Allowlist and IP Blocklist policies no longer accept a comma-separated list. The policies now accept data formatted as an array. For details, see [Anypoint API Manager](https://docs.mulesoft.com/jp/api-manager/latest/latest-overview-concept). ## [](#2-3-0)2.3.0 **August 12, 2021** MuleSoft announces the release of API Manager 2.3.0. ### [](#new-features-and-enhancements-2)New Features and Enhancements The following new features and enhancements are introduced in API Manager 2.3.0: - The API list view has been redesigned to enable quick glances at important information, without having to click into specific API instances. - In the redesigned API list, you can now view total requests and error rates for an API (for the previous 24 hours). For details, see [What Anypoint API Manager Is](https://docs.mulesoft.com/jp/api-manager/latest/latest-overview-concept). ## [](#2-2-16)2.2.16 **June 4, 2021** This release introduces the following enhancement: - Enhanced the UI to have the Mule 4 version selected by default for APIs. - Fixed bugs and implemented security improvements. ## [](#2-2-15)2.2.15 **October 20, 2020** ### [](#fixed-issues-23)Fixed Issues API proxies were responding with an unexpected HTTP status code when an API policy rejected an incoming HTTP Request. ### [](#known-issues)Known Issues None. ## [](#2-2-14)2.2.14 **May 30, 2020** This release introduces platform-wide support for API Groups across API Manager, Exchange, and API Community Manager, enabling you to package multiple API instances into a single cohesive unit for your API consumers. API consumers can access the published API Groups from Anypoint Exchange and API Community Manager. For more information about this feature, see [API Groups](https://docs.mulesoft.com/jp/api-manager/latest/api-groups-landing-page). ### [](#fixed-issues-24)Fixed Issues None. ### [](#known-issues-2)Known Issues None. ## [](#2-2-13)2.2.13 **April 02, 2020** This release introduces support for multiple identity providers for client management. You can now assign different client identity providers to business groups, environments, and APIs. Configuring multiple client providers enables you to enforce security and regulations in your business organization. For more information about this feature, see [Configuring Multiple Client Providers](https://docs.mulesoft.com/jp/api-manager/latest/configure-multiple-credential-providers). ## [](#2-2-12)2.2.12 **October 5, 2019** This release provides this new feature: - Support for WSDL and RAML payload validations for Mule 3 and Mule 4 proxy applications. See [API Proxy Validations](https://docs.mulesoft.com/jp/api-manager/latest/api-proxy-landing-page) for more information. ## [](#2-2-11)2.2.11 **May 4, 2019** This release provides this new feature: - Improved UI modal for changing Mule 3 custom policy version. ## [](#2-2-10)2.2.10 **April 6, 2019** This release provides this new feature: - Support for Mule 4 API proxy versions in API configuration ### [](#fixed-in-this-release)Fixed in This Release - Incorrect user information received in request api access email - Federated users unable to create APIs ## [](#2-2-9)2.2.9 **Jan 26, 2019** This release provides this new feature: - Automated policy for Mule 4 APIs - Adding RAML support for "Create new API" - While creating an API instance, API version and asset version are prepopulated - When deploying Mule 4 to CloudHub it is possible to choose specific runtime version - Notification for a managed API if API spec changes or newer version available in Exchange ## [](#2-2-8)2.2.8 **December 21, 2018** This release provides this new feature: - JWT policy for Mule 4 APIs ## [](#2-2-7)2.2.7 **November 17, 2018** This release provides this new feature: - Domain support for Mule 4 ### [](#fixed-in-this-release-2)Fixed in This Release - Bug when users download a HTTPS proxy without TLS context. - Changed policy display order, sorting version in descending order. ## [](#2-2-6)2.2.6 **November 3, 2018** This release provides this new feature: - API Manager 2.x users will get access to Secrets Manager. - Configure, secure & deploy HTTPs proxies using certificates (keystore/truststore) stored in Secrets Manager. This feature will be available for Mule 4 APIs deployed to CloudHub & Hybrid deployment targets. ## [](#2-2-5)2.2.5 **August 30, 2018** This release provides this new feature: - User-defined ports for CloudHub deployments - Added "Manage Runtime Fabric" proxy link - Auto populate implementation URI from Exchange - Support for Analytics chart to every granular permission ### [](#fixed-in-this-release-3)Fixed in This Release - Bug when users couldn’t add tags - Bug when users with custom roles weren’t receiving email notifications for API access ## [](#2-2-4)2.2.4 **June 30, 2018** This release provides this new feature: - Caching Policy for Mule 4 APIs ## [](#2-2-3)2.2.3 **June 2, 2018** This release provides this new feature: - Changes in platform APIs for unclassified environments to facilitate CI/CD pipelines. ### [](#fixed-in-this-release-4)Fixed in This Release - Bug when cannot save a change in API configuration. (AP-4030) - Bug when Mule 4 Runtime in a business group is unable to retrieve contracts. (AP-4081) ## [](#2-2-2)2.2.2 **May 17, 2018** This release provides these features: - Fine-grained access control for the November release of API Manager 2.0. - Logging and Header injection and removal policy for 3.8.5+ runtimes. - On the API Settings page "Client Applications" has been renamed to "Contracts". - Bug fixes. ### [](#fixed-in-this-release-5)Fixed in This Release - Bug when displaying client ID enforcement details. (AP-3976) - Exporting a Mule 4 API containing a policy resulted in a "TypeError: Cannot read property" message. (AP-3941) - If a valid URL with OAuth was copied from API Manager, and the user then logged out, subsequent attempts to access the URL failed with an NPE. (AP-3907) - Redeploy button incorrectly disabled after a deploy. (AP-3955) - When a user only has Asset Admin permission in Anypoint Exchange, the action of making the API Instance public or private fails. (AP-3860) - Allow updating these fields, which were set to read-only after the November upgrade: api.name, api.groupId (also updates the apiversion.groupId), api.assetId (also updates the apiversion.assetId), and apiversion.name. (AP-4020) ## [](#2-2-1)2.2.1 **April 23,2018** This release includes these improvements and bug fixes. - Support for 3.9 proxies. - Fixes an issue when approval email was not sent after requesting access for published APIs with manual approval. - Fixes an issue with autocomplete on import from Exchange. - Improved error message when deleting Client Applications with OKTA as the IM provider. - When autodiscovery looks for API ID that does not exist, Platform returns 403 instead of 404. ## [](#2-2-0)2.2.0 **January 27, 2018** This release supports deployment for Mule 4.1.0 proxies on the November release. ## [](#2-0-0)2.0.0 **November 18, 2017** This release of API Manager includes new and enhanced features for accounts that have upgraded to the November release. If your account hasn’t been upgraded yet, please contact your Customer Success representative. ### [](#key-changes-and-enhancements)Key Changes and Enhancements - A tight integration of Anypoint Platform components extends the [use of environments](https://docs.mulesoft.com/jp/api-manager/latest/environments-concept) to API management. - API permissions are now environment-based. - You can now [create multiple instances](https://docs.mulesoft.com/jp/api-manager/latest/api-instance-landing-page) of an API. - APIs in Exchange can be [managed from API Manager](#api-manager::manage-exchange-api-task.adoc). - There are two new APIs for managing APIs: - API Manager API v1.0 to manage API. - API Manager proxy API v1.0 to manage deployment of API proxies through API Manager. - Support for Mule 4 Early Access. Mule 4-related changes to API Manager are: - Classloader isolation exists between the application, the runtime and the connectors, and policies. - This release of Mule 4 [changes the packaging, size, and scope](https://docs.mulesoft.com/jp/api-manager/latest/policy-scope-size-concept) of a policy. - All policies are non-blocking. - All policies except CORS, which is executed first, can be ordered. - [Custom policy development](https://docs.mulesoft.com/jp/mule-gateway/policies-custom-getting-started) has changed. - Header propagation no longer occurs by default and needs to be configured. - Resource level policy support, which was restricted to RAML-based APIs, is extended to any HTTP API. ### [](#changes-related-to-using-mule-4-early-access)Changes Related to Using Mule 4 Early Access - API Manager [does not support auto-generation and deployment of proxies](https://docs.mulesoft.com/jp/api-manager/latest/latest-overview-concept). - The Throttling policy is not supported in this Mule release. - Mule 4 replaces the security manager policies with two HTTP Basic Authentication policies: - A combination of HTTP Basic Authentication and Simple Security Manager - A combination of HTTP Basic Authentication and LDAP Security Manager The policy protects an API by expecting and validating a user name and password. - You can configure the Rate Limiting policy if the quota is shared among the cluster nodes or not. By default, the quota is shared among the cluster nodes. ## [](#see-also)See Also - [トラブルシューティング](https://docs.mulesoft.com/jp/api-manager/latest/troubleshooting-landing-page) - [Known Issues](https://help.salesforce.com/s/issues) # API Manager Policies Release Notes Release notes for API Manager Policies include information about changes, improvements, and resolved issues in each released policy version.

The following release notes provide information about the policy’s definition. To find information about the policy’s implementation, see the implementation release notes in API Manager.

To learn more about managing policy implementation versions, see Update Policy Implementations.
## [](#release-notes-for-mule-4-policies)Release Notes for Mule 4 Policies - [API Security-Identification Header](https://docs.mulesoft.com/jp/release-notes/policies/api-security-identification-header-policy-release-notes) - [Basic Authentication - LDAP](https://docs.mulesoft.com/jp/release-notes/policies/ldap-policy-release-notes) - [Basic Authentication - Simple](https://docs.mulesoft.com/jp/release-notes/policies/http-basic-auth-release-notes) - [Client ID Enforcement](https://docs.mulesoft.com/jp/release-notes/policies/client-id-enforcement-release-notes) - [Cross-Origin Resource Sharing](https://docs.mulesoft.com/jp/release-notes/policies/cors-policy-release-notes) - [Detokenization](https://docs.mulesoft.com/jp/release-notes/policies/detokenization-release-notes) - [Header Injection](https://docs.mulesoft.com/jp/release-notes/policies/header-injection-release-notes) - [Header Removal](https://docs.mulesoft.com/jp/release-notes/policies/header-removal-release-notes) - [HTTP Caching](https://docs.mulesoft.com/jp/release-notes/policies/http-caching-release-notes) - [IP Allowlist](https://docs.mulesoft.com/jp/release-notes/policies/ip-allowlist-policy-release-notes) - [IP Blocklist](https://docs.mulesoft.com/jp/release-notes/policies/ip-blocklist-policy-release-notes) - [Legacy IP Allowlist](https://docs.mulesoft.com/jp/release-notes/policies/ip-whitelist-policy-release-notes) - [Legacy IP Blocklist](https://docs.mulesoft.com/jp/release-notes/policies/legacy-ip-blocklist-policy-release-notes) - [JSON Threat Protection](https://docs.mulesoft.com/jp/release-notes/policies/json-threat-protection-release-notes) - [JWT Validation](https://docs.mulesoft.com/jp/release-notes/policies/jwt-validation-release-notes) - [Message Logging](https://docs.mulesoft.com/jp/release-notes/policies/message-logging-release-notes) - [OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider](https://docs.mulesoft.com/jp/release-notes/policies/mule-oauth-token-enforcement-policy-release-notes) - [OpenAM Access Token Enforcement](https://docs.mulesoft.com/jp/release-notes/policies/openam-oauth-token-enforcement-policy-release-notes) - [OpenID Connect Access Token Enforcement](https://docs.mulesoft.com/jp/release-notes/policies/openid-connect-oauth-token-enforcement-policy-release-notes) - [PingFederate Access Token Enforcement](https://docs.mulesoft.com/jp/release-notes/policies/pingfederate-oauth-token-enforcement-policy-release-notes) - [Rate Limiting](https://docs.mulesoft.com/jp/release-notes/policies/rate-limit-policy-release-notes) - [Rate Limiting - SLA-based](https://docs.mulesoft.com/jp/release-notes/policies/rate-limit-sla-release-notes) - [Spike Control](https://docs.mulesoft.com/jp/release-notes/policies/spike-control-release-notes) - [Tokenization](https://docs.mulesoft.com/jp/release-notes/policies/tokenization-release-notes) - [XML Threat Protection](https://docs.mulesoft.com/jp/release-notes/policies/xml-threat-protection-release-notes) ## [](#see-also)See Also - [Policies in Mule 4](https://docs.mulesoft.com/jp/mule-gateway/policies-included-overview) - [Known Issues](https://help.salesforce.com/s/issues) # API Manager Proxy Release Notes Release notes for API Manager Proxies include information about changes, improvements, and resolved issues in each proxy version. ## [](#release-notes-for-mule-4-proxies)Release Notes for Mule 4 Proxies - [HTTP and HTTPs Proxies](https://docs.mulesoft.com/jp/release-notes/proxies/https-proxies-release-notes) - [REST Proxies](https://docs.mulesoft.com/jp/release-notes/proxies/rest-proxies-release-notes) - [WSDL Proxies](https://docs.mulesoft.com/jp/release-notes/proxies/wsdl-proxies-release-notes) ## [](#see-also)See Also - [API Proxy](https://docs.mulesoft.com/jp/api-manager/latest/api-proxy-landing-page) - [Known Issues](https://help.salesforce.com/s/issues) # API Manager Release Notes API Manager automatically updates to the latest version available; you don’t need to perform any tasks to move to the new version. The following release notes are provided for API Manager: - [API Manager 2.x Release Notes](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes) - [API Manager Policies Release Notes](https://docs.mulesoft.com/jp/release-notes/policies/policies-release-notes) - [API Manager Proxy Release Notes](https://docs.mulesoft.com/jp/release-notes/proxies/proxies-release-notes) - [API Gateway Extensions Release Notes](https://docs.mulesoft.com/jp/release-notes/api-gateway-extensions/api-gateway-extensions-release-notes) To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of your runtime. The following release notes are provided for your runtime: - [Omni Gateway Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-rn-landing-page) - [Mule Runtime Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # API Mocking Service Release Notes ## [](#2-71-0)2.71.0 **September 28, 2024** ### Fixed Issues
Issue Resolution ID

You now get the correct response when simulating a request on an endpoint.

W-15150842
## [](#2-67-0)2.67.0 **June 24, 2024** ### Fixed Issues
Issue Resolution ID

You can now use PKCE to test API specifications without defining the client_secret field.

W-15759980
## [](#2-65-0)2.65.0 **April 27, 2024** ### Fixed Issues
Issue Resolution ID

You can now change the mime-type without getting an incorrect status code response.

W-14845230
## [](#2-62-0)2.62.0 **February 3, 2024** ### What’s New - You can now change the server URL without the make public toggle automatically unchecking. - The `/link` endpoint was replaced by the new `/links` endpoint. For more information, refer to [Mocking Service 2 API Endpoints](https://anypoint.mulesoft.com/exchange/org.mule.examples/mocking-service-2-api/minor/1.3/?status=published). ## [](#2-60-0)2.60.0 **December 9, 2023** ### What’s New - The mocking service is now permanently enabled and you no longer need to define a mocking service URI in your specifications. - You can now open your projects without getting a warning to update to remove the mocking service URI. ## [](#2-59-0)2.59.0 **November 11, 2023** ### What’s New - You can now successfully test dependencies using the Mocking Service. ### Fixed Issues
Issue Resolution ID

You can now use application/json query parameter when defining a content-type scheme for a multipart/data attribute without getting an error message.

W-13896554
## [](#2-58-0)2.58.0 **October 13, 2023** ### Fixed Issues
Issue Resolution ID

You can now see the name of the field that contains multipart data in the error message.

W-13802993

You now see the correct status codes when using the API Console.

W-13590915

You can now use the cookie query parameter when defining an apiKey security scheme without getting an error message.

W-13602285
## [](#2-56-0)2.56.0 **August 19, 2023** ### What’s New - You can now use the `cookie` query parameter when defining an `apiKey` security scheme. ### Fixed Issues
Issue Resolution ID

Now, when defining a URL, the mocking service URL is successfully removed.

W-13498665
## [](#2-54-0)2.54.0 **June 24, 2023** ### Fixed Issues
Issue Resolution ID

You can now successfully use URLs as selected servers without getting an error message.

W-12613109
## [](#2-53-0)2.53.0 **May 29, 2023** ### Fixed Issues
Issue Resolution ID

The mocking service now displays a 400 bad request error message when you don’t include an authorization header when using the OAuth 2.0 security scheme type.

W-12740857
## [](#2-52-0)2.52.0 **April 29, 2023** ### Fixed Issues
Issue Resolution ID

Your session no longer expires with an error when you switch to branches with / in their name.

W-12708537 / W-12613956 / W-12986979
## [](#2-50-0)2.50.0 **March 4, 2023** ### Fixed Issues
Fixed resolution ID

You can now use the Request access token button when requesting a token using OAuth 2.0 flow.

W-12219253
## [](#2-47-0)2.47.0 **December 10, 2022** ### Fixed Issues
Fixed resolution ID

You can now use the allOf property on OAS 3.0 APIs without getting an incomplete response.

W-11491070
## [](#2-46-0)2.46.0 **November 12, 2022** ### What’s New - You now see the correct header values when sending a request. ### Fixed Issues
Fixed resolution ID

You can now successfully send a request with an array with a single string (for example: A12) without getting an error message.

W-11790087

You now get a response when defining nullable properties in return types.

W-11789702

Mocking service now automatically generates examples when given a type that only contains optional fields and the MS2-Randomize behavior header is set as true.

W-11569372

You can now successfully send HTTP headers.

W-11491118
## [](#2-45-4)2.45.4 **October 29, 2022** ### [](#new-features)New Features - Added a security layer to the API console, so that only registered domains are reachable. For more information, see the [Allowlisting Trusted Domains documentation.](https://docs.mulesoft.com/jp/access-management/allowlisting-trusted-domains) ## [](#2-44-0)2.44.0 **September 13, 2022** ### Fixed Issues
Issue ID

You can now use allOf in OAS 3.0 without getting an empty response.

W-11491130
## [](#2-43-0)2.43.0 **August 20, 2022** ### Fixed Issues
Issue ID

When simulating a Spec API using the Mocking service, you can now add XML tags in JSON string values without them being removed in the response body.

W-11394026

When clicking Request access token, you can now use the API is behind a firewall toggle to set the proxy.

W-11329433
## [](#2-42-0)2.42.0 **July 23, 2022** ### Fixed Issues
Issue ID

When the API is behind a firewall option is enabled, the Mocking Service requests no longer route through the proxy.

W-11240933
## [](#2-41-0)2.41.0 **June 25, 2022** ### Fixed Issues
Issue ID

When using the application/json+enhanced+v.10 media type, the mocking service now returns a valid response.

W-11141216

Trying to retrieve a PDF file no longer returns the encoded content of the file.

W-10747573
## [](#2-40-0)2.40.0 **May 28, 2022** ### Fixed Issues
Issue ID

When you test an API that has main and nested fragments that are Exchange dependencies, the mocking service now returns valid responses for PUT and PATCH methods.

W-10673086

When you use allOf in the definition to define type inheritance in OAS 3.0 APIs, the mocking service now returns a valid response.

W-10803321
## [](#2-39-0)2.39.0 **April 30, 2022** ### Fixed Issues
Issue ID

The mocking service now properly handles a zero value in queryParameter.

W-10764024
## [](#2-38-0)2.38.0 **April 2, 2022** ### Fixed Issues
Issue ID

The mocking service now properly renders examples in OAS 3.0 that use the AllOf property.

W-10647695

The web UI no longer collapses when the mocking service expiration date is deleted.

W-10819894
## [](#2-37-0)2.37.0 **March 5, 2022** ### Fixed Issues
Issue ID

Endpoints are now properly parsed for RAML specifications that were created from OAS specifications that have path parameters.

W-10647958

RAML maximum value validation for type: integer in application/xml no longer fails with REQUEST_VALIDATION_ERROR.

W-10647957
## [](#2-36-0)2.36.0 **February 5, 2022** ### Fixed Issues
Issue ID

If a resource name contains an unsupported character such as $, an accurate error message is shown.

SE-23187

When an OAS API specification is tested, the mocking service now handles the header correctly by accepting the value of the header name rather than the header name itself.

SE-23664
## [](#2-35-0)2.35.0 **January 8, 2022** ### Fixed Issues
Issue ID

Defining identical paths for the endpoint and baseUri parameters no longer results in 400 Bad Request - INVALID_PARAMETER - Could not apply any validation.

SE-23447

The Update Specification dialog now correctly shows when opening OAS 3.0 specifications that contain a v1 server URL. Afterward, clicking the Update now option deletes the server URL from the specification.

MSERV-1172
## [](#2-32-0)2.32.0 **October 16, 2021** ### Fixed Issues
Issue ID

Headers defined as required are now correctly validated in API Console.

SE-22132
## [](#2-31-0)2.31.0 **September 18, 2021** ### Fixed Issues
Issue ID

Publishing a RAML asset to Exchange and calling the asset’s endpoint via the mocking service no longer results in a RESOURCE_NOT_FOUND error.

SE-21215

RAML 0.8 API specifications containing URI parameters no longer result in the following parsing error:

{"code":"COULD_NOT_PARSE_PARAMETERS","message":"The resource was found but an error happened when parsing the parameters sent."}

MSERV-1271
## [](#2-30-0)2.30.0 **August 21, 2021** ### Fixed Issues
Issue ID

The mocking service now correctly renders examples when the OAS 3 nullable attribute is set to true.

SE-21983

In API Console, a toggle now enables you to select between query parameters that use the OR operation.

SE-21709

The mocking service no longer incorrectly returns 400 - Bad Request when content-type is omitted.

SE-20620
## [](#2-29-0)2.29.0 **July 24, 2021** ### [](#fixed-issues-26)Fixed Issues - Request URLs that included RAML `baseUriParameters` with a value of `/v1` resulted in the following error: Status Code: 404 Not Found ## [](#2-28-0)2.28.0 **June 26, 2021** ### [](#fixed-issues-27)Fixed Issues - When using the mocking function for an OAS 3 API array object, the response contained extra brackets in the array object. The response now returns array objects with the correct number of brackets. - The mocking service responded with an empty payload when a union type was defined as the response in an endpoint condition. The response now contains the correct payload. For example, the following RAML snippet would return an empty payload: responses: 200: body: application/json: type: test1Response | test2Response Now, the payload is not empty and contains the union of the two responses. ## [](#2-26-0)2.26.0 **May 1, 2021** ### [](#new-feature)New Feature - The mocking service now supports template URIs. A _template URI_ is a URI parameter enclosed in curly brackets inside a relative URI of a resource. The following RAML snippet demonstrates using a reserved expansion template URI (callout 1). The addition operator (`+`) allows for expanded values that include reserved URI characters. #%RAML 1.0 title: reserved expansion mediaType: application/json /reserved/{+hello}: **(1)** get: responses: 200: body: application/json: type: object properties: type: string example: type: hello Similarly, the following RAML snippet demonstrates using a fragment expansion template URI (callout 2). The crosshatch (`#`) operator allows for expanded values that include fragment identifiers. #%RAML 1.0 title: fragment expansion mediaType: application/json /fragment/{#hello}: **(2)** get: responses: 200: body: application/json: type: object properties: type: string example: type: hello For additional information on using reserved expansion and fragment expansion to resolve URI templates, refer to RFC 6570. ### [](#fixed-issues-28)Fixed Issues - The mocking service returned `HTTP 400 - INVALID_PARAMETER` in scenarios such as the following. An `example_code` parameter was defined with the `^\d{2}$` pattern: uriParameters: example\_code: type: string pattern: ^\\d{2}$ Specifying `12` as the value of `example_code` and sending a request to the mocking service resulted in: { "code": "INVALID\_PARAMETER", "message": "Could not apply any validation" } The mocking service now returns the correct `200 OK` status code. ## [](#2-25-0)2.25.0 **April 3, 2021** ### [](#fixed-issues-29)Fixed Issues - Sending payloads with characters after the end tag of a JSON array resulted in no parsing errors. The mocking service now returns: HTTP 400 - Bad Request - The mocking service returned an empty response if the response content type was `application/vnd.api+json`. The response now includes the body payload as defined in the example node. - Requests with a required string type parameter could include a zero-length string for the parameter. These requests resulted in errors. The mocking service now displays the following warning when sending requests with empty strings: Value is required but currently empty Instead of sending an empty string, you can disable a parameter, which causes the mocking service to return an expected `400 - Bad Request` response. To enable or disable a parameter, toggle the button next to the parameter’s text field. - The mocking service detected incorrect endpoints when the endpoints were defined with a trailing `/`, as demonstrated in the following example: /messaging/v1/email/definitions/ /messaging/v1/email/definitions/{definitionKey}/ ## [](#2-24-0)2.24.0 **March 6, 2021** ### [](#fixed-issues-30)Fixed Issues - Calling the mocking service with a value whose size was greater than 16 (the maximum) incorrectly resulted in a status code of `200 OK`. The following is now returned: {"code": "REQUEST\_VALIDATION\_ERROR","message": "Invalid schema for content type application/json. Errors: /16digits 10000000000000000 is not less or equal to 1.0E16. "} ## [](#2-23-0)2.23.0 **February 6, 2021** ### [](#fixed-issues-31)Fixed Issues - Accessing endpoints with numerous nested resources resulted in the following `400 Bad Request` error: { "code": "INVALID\_PARAMETER", "message": "Could not apply any validation" } - Under **Mocking Service Configuration**, toggling the **Make Public** button (creating or deleting a Public Mocking Service Link) was not output to the audit logs. - Enabling the **Set expiration date for public link** checkbox option (under **Mocking Service Configuration**) caused the following error: Status Code: 404 Not Found - An API that redirected could have forwarded the request (including the authentication header) to a malicious server. To prevent attacks, the mocking service no longer redirects to the URL indicated in the `Location` header. The following `302 Found` message is now displayed: Details are not exposed due to browser security policies. ## [](#2-20-0)2.20.0 **November 14, 2020** ### [](#new-feature-2)New Feature - The mocking service now runs automatically and no longer needs to be enabled. When you open an existing API specification or fragment, API Designer safely removes the baseURI property from your specification since this property is no longer needed. API Designer now allows you to create a public link that you can share with users outside of Anypoint Platform. ## [](#2-19-0)2.19.0 **October 29, 2020** - Added support for the MS2-Example behavioral headers. MS2-Example allows you to choose a specific response example if your endpoint defines more than one example for the same status code. - Fixed an issue in the mocking service where URI parameters were not working correctly in RAML. ## [](#2-18-0)2.18.0 **September 19, 2020** This release includes one fix: the mocking service could parse query strings incorrectly. ## [](#2-17-0)2.17.0 **August 22, 2020** This release includes this fix: the mocking service could, in some cases, treat optional headers as required parameters. ## [](#2-16-0)2.16.0 **July 25, 2020** - If an API specification written in OAS 3.0 uses an OAuth 2.0 security scheme, the mocking service requires an authorization header in each request. If a request does not include an authorization header, the mocking service returns this error message: "code": "REQUEST\_VALIDATION\_ERROR", "message": "Error validating Oauth 2.0 Flows. Required header Authorization is missing." - The MS2-Delay behavioral header now takes a maximum value of 10000 milliseconds (ms), and now follows this behavior: - If the value is set to fewer than 10000 ms, the mocking service adds a delay of ~5000 ms. - If the value is set to more than 10000 ms, the mocking service adds a delay of ~10000 ms. Examples: - If the value is set to a range of 5000 - 9000 ms, the mocking service adds a delay of ~5000 - ~9000 ms. - If the value is set to a range of 9000 - 20000 ms, the mocking service adds a delay of ~9000 - ~10000 ms. - If the value is set to a range of 20000 - 30000 ms, the mocking service returns this error message: { "code": "INVALID\_HEADER\_VALUE", "message": "Invalid value for header MS2-Delay. Requested range is higher than the max value allowed: 10000 ms" } ## [](#2-15-0)2.15.0 **June 27, 2020** This release includes minor bug fixes. ## [](#2-14-0)2.14.0 **May 30, 2020** This release includes minor bug fixes. ## [](#2-13-0)2.13.0 **May 2, 2020** - The mocking service returned an `Invalid schema for content type application/xml` error message for POST methods when these two conditions were met: - The value for a string in the request matched a regex pattern. - The media type for the specification was `application/xml`. For example, mocking a POST request for the following specification would cause the error: + #%RAML 1.0 title: Regex-Test mediaType: application/xml types: xml: properties: zip: type: string pattern: (\\d{5}) /test: post: body: application/xml: type: xml responses: 200: - The mocking service would fail to start if a project contained any files with filenames that contained characters not allowed in URLs. - The mocking service was not validating file types when files in mock POST requests were uploaded. - The mocking service returned an `Invalid schema for content type application/xml` message when an enum was used in POST requests for which the response body was declared as `application/xml`. - The mocking service returned an `Invalid schema for content type text/xml` message when the content type for an XSD file in the body of a POST request was declared as `text/xml`. ## [](#2-12-0)2.12.0 **April 4, 2020** - The mocking service returned the wrong example in cases such as the following: in an API specification written in RAML, a type is defined with an example, but a response that uses the type overrides the example with an `!include` directive. Rather than use the included example in the response, the mocking service used the example from the type definition. For example, the following simple specification defines the type `ExampleRoot`. The definition includes the example `Internal Example`. For the endpoint `/tmp`, the specification defines a response that uses `ExampleRoot`, but provides a different example, which is referred to with an `!include` directive. #%RAML 1.0 title: Example API with types and resources to showcase how examples look. mediaType: - application/json types: ExampleRoot: properties: string: type: string example: Internal Example /foo/example: get: responses: 200: body: type: ExampleRoot /tmp: get: responses: 200: body: type: ExampleRoot examples: !include external-example.raml If a request was made on `/tmp` before the fix, the response that the mocking service sent incorrectly contained `Internal Example` as the example for `ExampleRoot`. - The mocking service was not validating an example-array header that was of `type: string` and not an array. Now, you can use valid strings in these headers. ## [](#2-11-0)2.11.0 - March 7, 2020\* This release of the mocking service fixes the following issues: - The mocking service was not validating DataType fragments that were referenced by a Library fragment that was in trun referenced by the root file in an API-specification project. - The mocking service did not return an error message if a required query parameter was missing or the value was empty. - In a particular case, the mocking service was not returning an example in responses, even though the example was defined. - It was not possible to import an XSD schema into API Designer in Anypoint Design Center through the mocking service. The mocking service failed with the message `Invalid schema for content type application/xml. Errors: key not found: [http://www.w3.org/2001/xml.xsd](http://www.w3.org/2001/xml.xsd).` ## [](#2-9-0)2.9.0 **January 11, 2020** This release of the mocking service fixes the following issues. - If you set the authentication type to "Client Credentials" and then set a scope, the scope was not saved. - The mocking service returned empty responses instead of expected JSON responses in some cases, both in API Designer and in Exchange. - When the mocking service validated XML against an XSD schema that imported a namespace, it returned the following error message: `Invalid schema for content type application/xml. Errors: URI has an authority component.`. - XML payloads in requests were not considered valid when a Union data type was used for XML schemas. - When the behavioral header MS2-Status-Code was used and set to `400`, the mocking service returned the example that was defined for status code 200. - In API Console, the names of query parameters were being populated from parameter identifiers in parameter definitions, not from the parameter names. This problem occurred for API specifications written in OAS 2.0. ### [](#deprecation-of-version-1-of-the-mocking-service)Deprecation of Version 1 of the Mocking Service As of December 1, 2019, Version 1 of the mocking service is deprecated. MuleSoft recommends that you upgrade your API-specification projects in API Designer to use Version 2 of the mocking service. You can continue to use Version 1 until February 1, 2020. By default, however, Version 1 now returns the following response to every request: Status Code: 410 Gone Response headers: deprecation: date="Fri, 29 Nov 2019 23:59:59 GMT" link: https://docs.mulesoft.com/design-center/design-migrating-ms For Version 1 to respond with a status code that is defined in an API specification, you must add the following header to requests: name: x-deprecation-acknowledgement value: I understand that version 1 of the mocking service is deprecated and that I need to upgrade before February 1, 2020. Here is an example of this header used in a specification that is written in RAML: #%RAML 1.0 baseUri: https://mocksvc.devx.anypoint.mulesoft.com/mocks/d25ddb9c-ad20-4e80-af96-60217cc9f0b6/ version: v1 title: MS-TEST /test: get: headers: x-deprecation-acknowledgement: type: string required: false example: I understand that version 1 of the mocking service is deprecated and that I need to upgrade before February 1, 2020. Cache-Control: type: string required: true example: no-cache responses: 200: body: application/json: example: "OK" ## [](#2-6-0)2.6.0 **October 5, 2019** DateTime elements appeared with null values in responses from the mocking service, even when API specifications provided example responses that contained values for these elements. ## [](#2-5-0)2.5.0 **September 7, 2019** ### [](#announcement)Announcement Version 2 of the mocking service is replacing Version 1. You must migrate any API-specification project that meets _both_ of these conditions: - The mocking service was switched on for the project before January 10, 2019. - The mocking service has been running continuously since it was switched on. #### [](#dates-for-the-deprecation-and-end-of-life-of-version-1)Dates for the Deprecation and End of Life of Version 1 - **On November 29, 2019**, Version 1 of the mocking service will be deprecated. Starting on that date, third-party tools must include this header in requests that they send to the mocking service to test endpoints in API specifications being developed in API Designer: `x-deprecation-acknowledgement` The header must have this value: `I understand that version 1 of the mocking service is deprecated and that I need to upgrade before February 1, 2020.` - **Starting February 1, 2020**, Version 1 of the mocking service will no longer send responses to requests. If you have not migrated your projects to use Version 2 of the mocking service by this date, the mocking service will return the HTTP status code 301 and provide a link to this document. ### [](#new-feature-3)New Feature The new behavioral header `MS2-Status-Code-Selection` gives you two options for controlling how the mocking service selects a status code for responses to requests. See [Add Behavioral Headers to Simulated API Calls](https://docs.mulesoft.com/design-center/apid-behavioral-headers) for details. ## [](#2-4-0)2.4.0 **August 10, 2019** This release includes minor bug fixes. ## [](#2-3-0)2.3.0 **July 13, 2019** ### [](#fixed-issues-32)Fixed Issues - Executing the Get command in RAML produces an empty response in the example data. - Request and response are not showing up in the mocking service. ## [](#2-2-0)2.2.0 **June 15, 2019** This release contains one new feature and two fixes. ### [](#new-feature-4)New Feature - Use behavioral headers with the mocking service to modify in various ways how the mocking service behaves. See [Add Behavioral Headers to Simulated API Calls](https://docs.mulesoft.com/design-center/apid-behavioral-headers). - Now, the mocking service supports XML serialization facets, such as `wrapped`, `attribute`, and `name`, when generating an XML response that is based on a RAML example. ### [](#fixed-issues-33)Fixed Issues - The mocking service included invalid tags in returned XML when the data type contained an array. - The mocking service converted null values to string "null" values. ## [](#2-1-8)2.1.8 **May 18, 2019** - The API Console and the mocking service were adding invalid tags to XML examples. - Though multiple examples were defined for an endpoint, the mocking service always used the same example, rather than randomly selecting one to use. - When an OAS API specification did not define any consuming media type for a specific endpoint, the mocking service failed. ## [](#2-1-0)2.1.0 **February 23, 2019** The following issues were resolved in this release: \* For an API specification written in RAML, the mocking service returned content that was in YAML, although the returned content should have been in XML. \* The mocking service returned a misleading error message when `baseURI` was invalid. ## [](#2-1-0-2)2.1.0 **January 10, 2019** The following issues were resolved in this release: - \[SE-8276\] - Issues with Design Center - \[SE-8614\] - Request header 'Accept' failing when application/xml is present before application/json - \[SE-8666\] - Mocking service for OAuth 2.0 requires users to provide both authorization header and access token - \[SE-8745\] - Mocking service required parameters are allowed to be left out - \[SE-8790\] - Mocking Server Validation on Message Body - \[SE-8999\] - RAML in Design Center: Unexpected token A in JSON at position 1 - \[SE-9588\] - Mock Service returns 404 for paths with hyphens in 3rd level resource name - \[SE-9830\] - Mock service api always return 400 - \[SE-9990\] - JSON Schema defined inline in Design Center RAML gives error, OK on Studio - \[SE-10045\] - Incorrect Datetime-only format error when trying on mocking service from design center - \[SE-10194\] - RAML issue with optional enum type headers - \[SE-10222\] - additionalProperties=false in RAML are ignored by Design Center and exchange Mocking services. ## [](#1-1-11)1.1.11 **August 21, 2018** This release fixes the following issue: - The mocking service did not return messages for the 400 response in the correct styling. ## [](#1-1-10)1.1.10 **June 30, 2018** This release fixes the following issue: - TLS 1.0 and 1.1 were still supported. Now, only 1.2 is supported. ## [](#1-1-9)1.1.9 **May 19, 2018** The parser is now at version 1.1.42. ## [](#1-1-8)1.1.8 **April 21, 2018** - Invoking a resource that required the `uriParameter` (e.g., “/main/{attname}”) returned the example response for root instead of the defined example. - Invoking a resource that required a `uriParameter` and then using the example parameter in a GET or PUT method resulted in a response containing the complete API specification. ## [](#1-1-7)1.1.7 **March 24, 2018** This release bumps the parser and includes bug fixes. ### [](#improvements)Improvements Bumped parser to 1.1.41. ### [](#fixed-issues-34)Fixed Issues - Parsing no longer returns an Error for XML and Schema valid. - Fixed an issue with getting validation errors while building RAML for XML with Attributes and Inner text. - Fixed an issue that prevented some methods that return an Array from correctly showing the response example. ## [](#1-1-6)1.1.6 **February 24, 2018** This release fixes several bugs. ### [](#fixed-issues-35)Fixed Issues - A problem that prevented validation datetime query parameters with format RFC3339. - The issue causing RAML with a null response to return "message": in the HTTP response with 0 length. - The `multipleOf` facet validation issue. ## [](#1-1-5)1.1.5 **January 13, 2018** This release resolves a few issues: ### [](#resolved-issues)Resolved Issues - Fixed a problem related to a URI parameter name containing a hyphen (-) character. - Fixed an issue with making a request that has a empty body of type application/json. - Fixed a bug that returned a 400 "body: unknown type any" when using a body with an example that has no type definition. ## [](#1-1-4)1.1.4 **December 16, 2017** This release introduces the following improvements and resolved issues: ### [](#improvements-2)Improvements - Using the mocking service from a proxy application overrides the mocking service of the API itself. - The Authorization header check for path simulation has been removed. - When you don’t specify the main example for a DataType, the mocking service provides the examples defined for each property. ### [](#resolved-issues-2)Resolved Issues - Using a proxy application, the mocking service now validates the Body of the method when you try to POST it. - Using a base URI ending with / no longer causes a 404 error. - The mocking service now recognizes object type as an enum in a URI parameter. - Enforcement of a required data type has been fixed. An absent data type or one that does not include all required fields is rejected. - The problem related to using the RAML anonymous security scheme has been fixed. ## [](#1-1-3)1.1.3 **October 21, 2017** This release focuses on bug fixes. ### [](#improvements-3)Improvements - Enhanced the Mocking Server to respond with random examples if more than one is available. - A successful mock creation POST request now returns a 201 response status code instead of 200. ### [](#resolved-issues-3)Resolved Issues Fixed to work properly when the RAML has URI parameters. ## [](#1-1-2)1.1.2 **August 26, 2017** This release focuses on bug fixes. ### [](#resolved-issues-4)Resolved Issues - Examples defined in datatypes were not displayed properly. - Mocking server was returning 404 for calls with query parameters. ## [](#1-1-1)1.1.1 **July 15, 2017** This release focuses on bug fixes and closing gaps for RAML 1.0 support. ### [](#resolved-issues-5)Resolved Issues Fixed an issue preventing API Notebook text from expanding properly. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # API Security-Identification Header The API Security-Identification Header policy injects organization and API instance identifiers as response headers to enable integration with external security platforms such as Akamai. For configuration details, see [API Security-Identification Header Policy](https://docs.mulesoft.com/gateway/latest/policies-included-api-security-identification-header). ## [](#october-1-2026)October 1, 2026 ### What’s New - API Security-Identification Header policy definition version 1.0.1 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#august-6-2026)August 6, 2026 ### What’s New - API Security-Identification Header policy implementation version 1.0.0 is now supported by Omni Gateway. - API Security-Identification Header policy definition version 1.0.0 is now supported by Omni Gateway. # API Security-Identification Header ## [](#1-0-1)1.0.1 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-0-0)1.0.0 **August 6, 2026** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.12.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Introduced the API Security-Identification Header policy that injects organization and API instance identifiers as response headers to enable integration with external security platforms such as Akamai. # API Visualizer Release Notes - 2022 and Later ## [](#june-15-2026)June 15, 2026 ### What’s New - API Visualizer (formerly Anypoint Visualizer) is now available in India Cloud. For more information, see [API Visualizer Features by Control Plane](https://docs.mulesoft.com/visualizer/#visualizer-control-plane) and [Salesforce Hyperforce Overview](https://docs.mulesoft.com/hyperforce/). ## [](#december-9-2024)December 9, 2024 ### What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) For more information, see [API Visualizer Features by Control Plane](https://docs.mulesoft.com/visualizer/#visualizer-control-plane) and [Salesforce Hyperforce Overview](https://docs.mulesoft.com/hyperforce/). ## [](#april-5-2022)April 5, 2022 ### What’s New - API Visualizer is now available in Mulesoft Government Cloud. ## [](#march-17-2022)March 17, 2022 ### What’s New - When viewing your application network, the list of tags is now filtered to include only tags that exist in the selected environments. ## [](#see-also)See Also - [Troubleshooting App Visualization](https://docs.mulesoft.com/visualizer/troubleshooting-visualization) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit 1.3.0 for Mule 4 Release Notes **November 28, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed an issue that is was not validating a RAML specified date time format - Now a summary is displayed when opening console - Updated APIKit Console to latest version - Fixed an issue that does not allow type names that contain dots - Fixed an issue of the API console that doesn’t work if RAML doesn’t have BaseUri parameter ## [](#improvements)Improvements - The Scaffolding result is now enriched with errors during the processs. - AMF console updated to lastest version - Java 11 support on APIKit - now when Scaffolding empty API Specs (no resources). APIKit generates mule configs with the main flow but no resource flows. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit 4.0.0 Release Notes **November 19, 2017** These release notes briefly describe changes, known issues, and limitations in APIkit 4.0.0. ## [](#whats-new)What’s New - Performance improvements have been achieved through the support of a non-blocking strategy for APIKit operations. - API Console no longer appears in Studio. The URL for launching the Console appears in the logs in Studio when you create an APIkit API. To launch the Console, enter the URL in a browser. - You can now configure APIkit Router properties to [enable or disable the validations](https://docs.mulesoft.com/jp/apikit/latest/validate-4-task) of query parameters and headers. - APIkit now processes the operations declared after the APIkit router component. - Only one of two 3.x-supported methods of configuring the Console is supported in this release. - You can configure the Console only from within the apikit:config element. - Retrieving the RAML is supported from the Console, but not from the API. - Generated XML code differs from that generated by APIkit 3.x. The XML code complies with new Mule 4.0 components as shown in the following snippets: **3.x** **Mule 4.0** ## [](#compatibility)Compatibility - Mule Runtime 4.0.0 - Anypoint Studio 7.0.0 - Java Parser RAML 1.0 v1.0.16 - Java Parser RAML 0.8 v0.8.20 - API Console 4.2.0 ## [](#now-available-in-this-release)Now available in this release - Non-blocking requests - DataSense metadata - The Community edition ## [](#limitations)Limitations This release does not support the following: - Inbound endpoints - APIkit for SOAP - OData Post requests using form parameters are supported, but not validated. ## [](#features-and-functionality)Features and Functionality Enhancement requests fulfilled are: - Check that custom headers are not duplicated. \[APIKIT-868\] - Strict validation of query parameters and headers. \[APIKIT-869\] ### [](#fixed-in-this-release)Fixed in this release - PUT and POST requires a request body. \[APIKIT-793\] - Form Parameter type is not being validated. \[APIKIT-839\] - Fixing Exception caused by trying to load a JSON Schema from a path with spaces. \[APIKIT-850\] - APIkit scaffolder is generating mule-deploy.properties file. \[APIKIT-873\] - Critical vulnerability in Jackson prior to 2.8.9. \[APIKIT-876\] - Expose Console Resources to the RAML GW Proxy. \[APIKIT-889\] - Resource found in RAML but not in config, throws 500 server error. \[APIKIT-901\] - Console source location should be saved to a file. \[APIKIT-902\] - Error 500 when sending a request to a resource without schema defined. \[APIKIT-925\] - Scaffolder: Build fails when mule version is not sent (default CE version). \[APIKIT-931\] - Metadata is not reported for APIKit routes. \[APIKIT-940\] - Use single quote on set-variable tag. \[APIKIT-942\] - Porting to 4.0: Only one HTTP Response code evaluated for return from APIKit Rest Requests. \[APIKIT-949\] - Ensure multiple success status defined in RAML are considered for the REST response in APIKIT 4. \[APIKIT-951\] - ApikitErrorTypes is using a not exported mule-core class. \[APIKIT-956\] - Use Optional instead of null in FlowMetadata. \[APIKIT-963\] - Multipart: Bad request when expecting default value in the response. \[APIKIT-973\] - APIKit console does not start. Error : "No listener for endpoint: /console/". \[APIKIT-994\] - Mule4 :APIKit fails on XML starting with BOM and containing tab character. \[APIKIT-957\] **[Github RAML Java Parser](https://github.com/raml-org/raml-java-parser/releases) Issues Fixed** - #428 Fixing float value in 'multipleOf' causes a 'Cannot divide by zero' exception - #429 JSON Schema validation fails when relative '$ref' is used - #434 Apply traits when having unimplemented optional methods with resourcePathName in type - #437 Upgrade jackson to version 2.9.2 - #413 Upgrade json-schema-validator to version 2.2.8 - #400 Upgrade commons-beanutils to 1.9.3 - #377 displayName is not valid for methods with RAML 0.8 ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit 4.0.1 Release Notes **March 20, 2018** This release fixes an important issue related to the handling of Mule runtime exceptions by the APIkit router. The following behavior was fixed: the execution of the flow in the router might result in a MuleException, a MuleRuntimeException, or an Exception. APIkit was only handling the first one by rethrowing it. The others were wrapped in a DefaultMuleException, which is mapped to an UNKNOWN error. ## [](#compatibility)Compatibility - Mule Runtime 4.0.0+ - Anypoint Studio 7.0.2 ## [](#fixed-in-this-release)Fixed in this Release - APIkit Router incorrectly wraps MuleRuntimeException. (APIKIT-1129) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit 4.1.15 Release Notes **May 23, 2019** There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.2 and later
## [](#fixed-in-this-release)Fixed in this release - Fixed issue where APIKit returns 404 for url with ":". - Fixed issue where APIKit won’t send error response when request leads to an exception. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for AsyncAPI 1.0.0 Release Notes ## [](#june-24-2024)June 24, 2024 ## What’s New - [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi) supports scaffolding Mule apps with the AsyncAPI 2.6 spec in Anypoint Code Builder and Anypoint Studio. With this support, you can use asynchronous messaging protocols and design event-driven APIs. - For information about dependencies, configurations, and supported message brokers, see [APIkit for AsyncAPI モジュールリファレンス](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-module-reference). - To learn about predefined error types and descriptions, and enhance your ability to manage and troubleshoot errors in event-driven API implementations, see [APIkit for AsyncAPI エラー処理リファレンス](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-error-handling-reference). ## Compatibility
Product Version

Anypoint Code Builder

June 4, 2024 and later

Anypoint Studio

7.18.0 and later

Mule runtime

4.5.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi) - [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api) # APIkit for AsyncAPI 1.1.0 Release Notes APIkit for AsyncAPI supports scaffolding Mule apps with the AsyncAPI 2.6 spec in Anypoint Code Builder and Anypoint Studio. With this support, you can use asynchronous messaging protocols and design event-driven APIs. ## [](#october-8-2024)October 8, 2024 ## What’s New - APIkit for AsyncAPI now supports Avro schemas Improve data serialization for your API interactions. See [APIkit for AsyncAPI モジュールでの Avro スキーマの実装と検証](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-avro-support) - APIkit for AsyncAPI now supports Solace PubSub+ Connector and Anypoint Connector for Salesforce Pub/Sub (Salesforce Pub/Sub Connector). Expand your integration capabilities and streamline event-driven architectures. See [Supported Message Brokers](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-module-reference#supported-message-brokers) - Validation features are improved to create more robust and reliable API implementation. See [Validation of Messages](https://docs.mulesoft.com/jp/apikit/latest/apikit-asyncapi-module-reference#validation-of-messages). - Multiple message handling in an operation is now improved. Enhance the flexibility and scalability of your API operations ## Compatibility
Product Version

Anypoint Code Builder

October 8, 2024 and later

Anypoint Studio

7.19.0 and later

Mule runtime

4.6.0 and later

OpenJDK

8, 11, and 17
## Known Issues

Known Issue

ID

If you enable the validation and the mediaType of the message doesn’t match the mediaType specified in the API spec, the message isn’t flagged as invalid.

W-16663560

AsyncAPI Message Listener doesn’t preserve the mediaType property and transforms it as the defaultContentType present in the Async API spec unless AsyncAPI Message Listener supports the inbound message type.

W-16663585

In Salesforce Pub/Sub Connector, the source validation doesn’t work if contentType is application/XML.

W-16756836

When implementing AsyncAPI APIs in Windows, an empty extra Mule-config file is created.

W-15757808

APIkit for AsyncAPI connector fails while parsing Async APIs that reference Avro schema files.

W-16896197
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi) - [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api) # APIkit for AsyncAPI 1.1.1 Release Notes APIkit for AsyncAPI supports scaffolding Mule apps with the AsyncAPI 2.6 spec in Anypoint Code Builder and Anypoint Studio. With this support, you can use asynchronous messaging protocols and design event-driven APIs. ## [](#january-31-2025)January 31, 2025 ## Compatibility
Product Version

Anypoint Code Builder

February 4, 2025 and later

Anypoint Studio

7.20.0 and later

Mule runtime

4.6.0 and later

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

APIkit for AsyncAPI now adds the brokerHost broker for Solace to the dev-properties.properties as a property.

W-17245272

DataSense no longer encounters a NullPointerException when the contentType field is missing in the AsyncAPI spec in Studio.

W-16979930

APIkit for AsyncAPI no longer fails on parsing Async APIs that refer to external message schema files.

W-16896197
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi) - [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api) # APIkit for AsyncAPI 1.1.2 Release Notes APIkit for AsyncAPI supports scaffolding Mule apps with the AsyncAPI 2.6 spec in Anypoint Code Builder and Anypoint Studio. With this support, you can use asynchronous messaging protocols and design event-driven APIs. ## [](#june-13-2025)June 13, 2025 ## Compatibility
Product Version

Anypoint Code Builder

February 4, 2025 and later

Anypoint Studio

7.20.0 and later

Mule runtime

4.6.0 and later

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

APIkit for AsyncAPI no longer fails in some cases when deploying to CloudHub and CloudHub 2.0 environments.

W-18234733

The AnypointMQ Publish operation now passes the media type information along with the payload as expected.

W-15816422
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi) - [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api) # APIkit for AsyncAPI 1.2.0 Release Notes APIkit for AsyncAPI supports scaffolding Mule apps with the AsyncAPI 2.6 spec in Anypoint Code Builder and Anypoint Studio. With this support, you can use asynchronous messaging protocols and design event-driven APIs. ## [](#may-29-2026)May 29, 2026 ## What’s New - APIkit for AsyncAPI now provides enhanced observability by including dynamic span naming and route metadata in OpenTelemetry traces, so you can identify specific API operations and matched resource templates. For more information, see the [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi). ## Compatibility
Product Version

Anypoint Code Builder

February 4, 2025 and later

Anypoint Studio

7.20.0 and later

Mule runtime

4.6.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [APIkit for AsyncAPI](https://docs.mulesoft.com/jp/apikit/latest/apikit-for-asyncapi) - [AsyncAPI Support to Implement Event-Driven Architecture](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for GraphQL 1.0.0 for Mule 4 Release Notes The APIkit for GraphQL module works with Anypoint Code Builder, which enables you to develop Mule applications. This module supports implementing GraphQL services, which map GraphQL APIs to the existing backends where source data is stored. ## [](#july-26-2023)July 26, 2023 ## What’s New - The APIkit for GraphQL module is released. ## Compatibility
Product Version

Mule runtime engine

4.3.0 and later
## [](#see-also)See Also - [APIkit for GraphQL](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-graphql) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for GraphQL 1.0.1 for Mule 4 Release Notes The APIkit for GraphQL module works with Anypoint Code Builder, which enables you to develop Mule applications. This module supports implementing GraphQL services, which map GraphQL APIs to the existing backends where source data is stored. ## [](#february-27-2024)February 27, 2024 ## What’s New - APIkit for GraphQL 1.0.1 is now FIPS 140-2 compliant. ## Compatibility
Product Version

Mule runtime engine

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

GraphQL configuration no longer breaks with Mule runtime 4.5 and later.

W-14980208
## [](#see-also)See Also - [APIkit for GraphQL](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-graphql) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for GraphQL 1.1.0 for Mule 4 Release Notes ## [](#may-9-2024)May 9, 2024 ## What’s New - APIkit for GraphQL is now compatible with Java 17. ## Compatibility
Product Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [APIkit for GraphQL](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-graphql) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for GraphQL 1.1.1 for Mule 4 Release Notes ## [](#october-17-2025)October 17, 2025 ## What’s New - This release upgrades the **graphql-java** and **gson** dependencies to address reported security vulnerabilities. ## Compatibility
Product Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The graphql-java and gson dependencies are upgraded to address reported security vulnerabilities.

W-19855996
## [](#see-also)See Also - [APIkit for GraphQL](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-graphql) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for GraphQL 1.2.0 for Mule 4 Release Notes ## [](#april-24-2026)April 24, 2026 ## What’s New - Identify API Operations More Easily with Dynamic Telemetry Traces APIkit for GraphQL 1.2.0 introduces dynamic telemetry traces for easier API operation identification. This enhancement improves visibility into API behavior and performance, streamlining troubleshooting and optimization ## Compatibility
Product Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [APIkit for GraphQL](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-graphql) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for gRPC 1.0.0 Release Notes APIkit for gRPC supports scaffolding Mule projects with the gRPC spec in Anypoint Code Builder. With this support, you can use gRPC protocols and design gRPC-based APIs. ## [](#march-16-2026)March 16, 2026 ## What’s New - APIkit for gRPC now supports the gRPC protocol. Design and implement gRPC APIs in Anypoint Code Builder with the first release of APIkit for gRPC. This initial version provides a contract-first development experience for Protobuf 3, including API scaffolding to automatically generate routing logic and implementation flows for all four gRPC communication patterns. See [apikit::apikit-for-grpc.adoc](#apikit::apikit-for-grpc.adoc). ## Compatibility
Product Version

Anypoint Code Builder

March 16, 2026 and later

Mule runtime

4.11.0 and later

OpenJDK

17
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [apikit::apikit-for-grpc.adoc](#apikit::apikit-for-grpc.adoc) # APIkit for Mule 4 1.10.0 Release Notes ## [](#january-4-2024)January 4, 2024 ## What’s New - APIkit now supports Java 17. - This update fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.48

AMF

5.4.5
### Fixed Issues
Issue Resolution ID

APIkit no longer throws a MalformedStreamException exception when validating the length of a multipart body.

W-13792058
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.10.1 Release Notes ## [](#february-2-2024)February 2, 2024 ## What’s New - This update fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.4.7
### Fixed Issues
Issue Resolution ID

APIkit no longer throws an unhandled exception when the header is malformed.

W-13792058
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.10.2 Release Notes ## [](#february-6-2024)February 6, 2024 ## What’s New - This release updates dependencies. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.4.7
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.10.3 Release Notes ## [](#february-13-2024)February 13, 2024 ## What’s New - This release updates dependencies. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.4.7
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.10.4 Release Notes ## [](#march-6-2024)March 6, 2024 ## What’s New - APIkit for Mule 4 1.10.4 is now FIPS 140-2 compliant. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.4.9
### Fixed Issues
Issue Resolution ID

APIkit no longer accepts null values as valid strings for parameters.

W-15008392

APIkit no longer disregards the Accept header when specified.

W-15162242
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.0 Release Notes ## [](#august-12-2024)August 12, 2024 ## What’s New - APIkit for REST now allows headers of type `array` to be accessed using small-case text style for header names to match the behavior of other header types. - Request URI for REST now requires non-empty path parameters to ensure the necessary data is included in the API call. - The APIkit router can now process payloads that have accented characters. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.4.9
### Fixed Issues
Issue Resolution ID

APIkit for REST improves its handling of empty path variables to correctly distinguish request URIs with a trailing slash.

W-14747249

The APIkit router no longer freezes if processing an API specification that has regex patterns and payloads with accented characters.

W-16189110

APIkit for REST omits patterns in a RAML specification with no corresponding action when matching request URIs.

W-16306395

Http request headers of the type array now correctly follow the lower-case naming convention.

W-16328046

APIkit for REST now correctly accepts requests with any mediaType if the RAML spec of the request defines a wildcard mediaType.

W-16366365
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.1 Release Notes ## [](#september-20-2024)September 20, 2024 ## What’s New - This release upgrades some dependencies to address reported security vulnerabilities.
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.4.9
### Fixed Issues
Issue Resolution ID

Accessing request headers post request routing is now case-insensitive.

W-16518905

APIkit for REST no longer throws the ConcurrentModificationException exception if high concurrency occurs.

W-16629616

apikit-rest-parser-wrapper upgrades dependencies to address reported security vulnerabilities.

W-16594370
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.10 Release Notes ## [](#october-31-2025)October 31, 2025 ## What’s New - APIkit for Mule 4 1.11.10 upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
### Fixed Issues
Issue Resolution ID

APIkit for Mule 4 1.11.10 upgrades the raml-parser library to version 0.9.16 and raml-parser-2 to version 1.1.7 to address reported security vulnerabilities.

W-19898739
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.11 Release Notes ## [](#january-14-2026)January 14, 2026 ## What’s New - APIkit for Mule 4 1.11.11 upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
### Fixed Issues
Issue Resolution ID

APIkit for Mule 4 1.11.11 upgrades the commons-io dependency to a safer version to address a reported security vulnerability.

W-20593156
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.12 Release Notes ## [](#february-5-2026)February 5, 2026 ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
### Fixed Issues
Issue Resolution ID

APIkit for Mule 4 1.11.12 no longer incorrectly recognizes string values as objects in error messages.

W-20335356
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.13 Release Notes ## [](#february-20-2026)February 20, 2026 ## What’s New - APIkit for Mule 4 1.11.13 upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
### Fixed Issues
Issue Resolution ID

APIkit for Mule 4 1.11.13 upgrades the DOMPurify dependency to a safer version to address a reported security vulnerability.

W-20628445

APIkit for Mule 4 1.11.13 upgrades the org.apache.logging.log4j dependency to a safer version to address a reported security vulnerability.

W-21247179
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.14 Release Notes ## [](#march-6-2026)March 6, 2026 ## What’s New - This release upgrades the **org.mozilla:rhino**, **org.apache.avro:avro**, and **com.google.code.gson:gson** dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AMF

5.10.0
### Fixed Issues
Issue Resolution ID

The transitive dependency org.mozilla:rhino is updated to version 1.17.15.1 to address security vulnerabilities.

W-20622115

The transitive dependency org.apache.avro:avro is updated to version 1.11.5 to address security vulnerabilities.

W-21322583

The direct dependency com.google.code.gson:gson is updated to version 2.12.0 to address security vulnerabilities.

W-21343955
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.15 Release Notes ## [](#march-25-2026)March 25, 2026 ## What’s New - APIkit for Mule 4 now provides enhanced observability by including dynamic span naming and route metadata in OpenTelemetry traces, so you can identify specific API operations and matched resource templates. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AMF

5.10.0
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.16 Release Notes ## [](#april-16-2026)April 16, 2026 ## What’s New - This release upgrades the **jackson-core** dependency to address reported security vulnerabilities. ## Fixed Issues
Issue Resolution ID

The transitive dependency jackson-core is updated to version 2.18.6 to address security vulnerabilities.

W-20622115
## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.17 Release Notes ## [](#april-30-2026)April 30, 2026 ## What’s New - This release upgrades the **Log4j** library to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

The Log4j library is updated to version 2.25.4. to address security vulnerabilities.

W-21246829
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.18 Release Notes ## [](#june-26-2026)June 26, 2026 ## What’s New - This release upgrades API Console to version 6.6.91 to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

TAPI Console is updated to version 6.6.91 to address security vulnerabilities.

W-22392963 / W-22392962
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.2 Release Notes ## [](#october-24-2024)October 24, 2024 ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.4.9
## Fixed Issues
Issue Resolution ID

APIkit for REST 1.11.0 and later no longer fails with the validation timeout error in some deployments to CloubHub.

W-16728899
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.3 Release Notes ## [](#january-15-2025)January 15, 2025 ## What’s New - This release upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.61

AMF

5.6.4
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.4 Release Notes ## [](#february-7-2025)February 7, 2025 ## What’s New - This release upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.5 Release Notes ## [](#march-5-2025)March 5, 2025 ## What’s New - APIkit upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
## Fixed Issues
Issue Resolution ID

APIkit for REST 1.11.5 no longer fails if the header ends with a semicolon.

W-17760012
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.6 Release Notes ## [](#june-10-2025)June 10, 2025 ## What’s New - APIkit upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.7 Release Notes ## [](#august-6-2025)August 6, 2025 ## What’s New - Dependencies are upgraded to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
## Fixed Issues
Issue Resolution ID

Dependencies are upgraded to address reported security vulnerabilities.

W-18939539
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.8 Release Notes ## [](#october-17-2025)October 17, 2025 ## What’s New - APIkit for Mule 4 1.11.8 and later now includes a commercial license file to support automated legal and compliance scanning. - APIkit for Mule 4 1.11.8 and later automatically validates the number of elements in an array using the `minItems` and `maxItems` properties from your API spec. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
### Fixed Issues
Issue Resolution ID

APIkit for Mule 4 now correctly returns a 400 BAD REQUEST message for malformed JSON files that have extra braces in the request body.

W-19561124

APIkit for Mule 4 now deploys OAS fragments as expected, even if referenced in multiple locations within the API spec.

W-19405030
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.11.9 Release Notes ## [](#october-28-2025)October 28, 2025 ## What’s New - APIkit for Mule 4 1.11.9 upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.73

AMF

5.6.4
### Fixed Issues
Issue Resolution ID

APIkit for Mule 4 upgrades the org.apache.commons:commons-lang3 library to version 3.18.0, and the parser-service library to version 2.7.14 to address reported security vulnerabilities.

W-19174569
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.0 Release Notes ## [](#june-29-2026)June 29, 2026 ## What’s New - This release upgrades the **jackson-databind** library to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

The jackson-databind library is updated to version 2.18.7 to address security vulnerabilities.

W-23082462
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.1 Release Notes ## [](#june-30-2026)June 30, 2026 ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit now correctly parses comma-separated query parameter values as arrays when explode: false is specified, resolving APIKIT:BAD_REQUEST errors.

W-21884373
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.10 Release Notes ## [](#october-9-2026)October 9, 2026 ## What’s New - This release upgrades some dependencies to address a reported security vulnerability. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit upgrades the jackson dependency to version 2.22.3 and the xmlschema-core dependency to 2.3.3 to address a reported security vulnerability.

W-24369260 / W-24344802
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.2 Release Notes ## [](#july-8-2026)July 8, 2026 ## What’s New - This release upgrades the **jackson-databind** library to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit upgrades the jackson-databind library to version 2.21.4 to address reported security vulnerabilities.

W-23346701
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.3 Release Notes ## [](#august-3-2026)August 3, 2026 ## What’s New - This release upgrades the **log4j** dependency to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit updates the log4j dependency to 2.25.5 to address reported security vulnerabilities.

W-23569287
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.4 Release Notes ## [](#august-6-2026)August 6, 2026 ## What’s New - This release upgrades some dependencies to address a reported security vulnerability. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.85

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit updates the RAML Parser 2 dependency to 1.2.1 and the Eclipse Parsson dependency to 1.1.9 to address reported security vulnerabilities.

W-23424710

APIkit updates the jackson-databind library to 2.21.5 to address reported security vulnerabilities.

W-23623900
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.5 Release Notes ## [](#august-14-2026)August 14, 2026 ## What’s New - This release upgrades some dependencies to address a reported security vulnerability. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit upgrades the dompurify dependency to address a reported security vulnerability.

W-23387112
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.6 Release Notes ## [](#august-31-2026)August 31, 2026 ## What’s New - This release upgrades some dependencies to address a reported security vulnerability. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit upgrades the transitive Jackson Databind dependency to 2.22.2 to address a reported security vulnerability.

W-23387112
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.7 Release Notes ## [](#september-24-2026)September 24, 2026 ## What’s New - This release upgrades the **reactor** dependency to address a reported security vulnerability. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit upgrades the reactor dependency to 3.8.7 to address a reported security vulnerability.

W-24208239
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.8 Release Notes ## [](#october-1-2026)October 1, 2026 ## What’s New - This release includes only non-user-impacting changes. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.12.9 Release Notes ## [](#october-1-2026)October 1, 2026 ## What’s New - OpenTelemetry traces for APIkit for REST now show the specific API operation that matched the request, instead of a wildcard route. For more information, see [OpenTelemetry Route on the HTTP Span](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-xml-reference#opentelemetry-route-on-the-http-span). ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.13.0 Release Notes ## [](#october-9-2026)October 9, 2026 ## What’s New - This release provides general improvements and internal issue fixes. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.13.1 Release Notes ## [](#october-14-2026)October 14, 2026 ## What’s New - This release upgrades some dependencies to address a reported security vulnerability. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.10.0
## Fixed Issues
Issue Resolution ID

APIkit upgrades the jackson dependency to version 2.22.3 and the xmlschema-core dependency to 2.3.3 to address a reported security vulnerability.

W-24469711
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.13.2 Release Notes ## [](#october-15-2026)October 15, 2026 ## What’s New - APIkit for Mule 4 1.13.0 now supports OAS 3.1. For more information, see [APIkit の互換性](https://docs.mulesoft.com/jp/apikit/latest/apikit-compatibility). ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.15.0
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.13.3 Release Notes ## [](#october-23-2026)October 23, 2026 ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later

OpenJDK

8, 11, and 17
### [](#dependencies)Dependencies
Application/Service Version

Anypoint API Console

6.6.500

AML Modeling Framework (AMF)

5.15.0
## Fixed Issues
Issue Resolution ID

Dependency scanners no longer quarantine APIkit for Mule 4 because the module declares the CPAL 1.0 license as expected.

W-24371611
## [](#see-also)See Also - [APIkit for REST](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-rest) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.10 Release Notes ## [](#february-21-2022)February 21, 2022 ## What’s New - This release fixes bugs. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.22

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Fixed an issue with API Sync resource loader

APIKIT-3151 W-10564216

Fixed an issue with nullable properties for OAS 3

SE-23357 W-10717203
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.11 Release Notes ## [](#march-25-2022)March 25, 2022 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.22

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Unions in query strings are now properly validated.

SE-24430 W-10647630

Improved the description of the error message in a multipart form parameter validation.

SE-22685 W-10647637
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.12 Release Notes ## [](#april-12-2022)April 12, 2022 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.22

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Fix duplicated-key issue

W-10745349
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.5 Release Notes ## [](#september-2-2021)September 2, 2021 ## What’s New - This release fixes bugs. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Fixed API Console issue rendering large APIs.

SE-20459

Fixed API Console issue handling fractional numbers.

SE-21538

Query strings validation is now consistent with query parameters validation.

SE-22454
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.6 Release Notes ## [](#october-22-2021)October 22, 2021 ## What’s New - This release fixes bugs. ## [](#dependencies)Dependencies - Anypoint API Console 6.6.2 ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Fixed query string issue with default values.

APIKIT-3020

Fixed error message when validating YAML file.

APIKIT-2816
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.7 Release Notes ## [](#december-2-2021)December 2, 2021 ## What’s New - This release fixes bugs. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.2

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Fixed an issue validating multipart/related payload

SE-23514

Fixed issues rendering API Console

SE-22779, SE-23269, SE-23296, APIKIT-3067, APIKIT-3100
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.8 Release Notes ## [](#december-23-2021)December 23, 2021 ## What’s New - This release fixes bugs. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.2

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Fixed an issue validating json payload

SE-22687
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.5.9 Release Notes ## [](#february-3-2022)February 3, 2022 ## What’s New - This release fixes bugs. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.22

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Fixed an issue when rendering a number in API Console

SE-22349
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.6.0 Release Notes ## [](#may-16-2022)May 16, 2022 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.27

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

APIkit no longer triggers an error when there is a leading asterisk (*) in a union field of queryString.

W-10976666
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.6.1 Release Notes ## [](#june-30-2022)June 30, 2022 ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.30

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

APIkit now estimates the API specification type and version in a more accurate way.

W-11255939
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.7.0 Release Notes ## [](#september-26-2022)September 26, 2022 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.30

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

The APIkit Router no longer requires to quote query parameters if the type is defined as a union of repeatable strings and the value has only digits.

W-11210718

Multipart form validation now throws an exception if a required parameter is not sent.

W-11234660

The connector no longer throws an OutOfMemory error when validating a part of a multipart request defined as an array of file types.

W-11669811

The result of RequestValidator now returns the correct content length when the incoming request is multipart.

W-11666958

Multipart form-data requests are no longer rejected for content length validation unless the max and min properties are specified in the spec or the default limit size for multipart content is exceeded (256MiB). The limit of this value varies by specifying the apikit.multipart.size.limit system property (expressed in bytes).

W-11667374

Parsing API synced from Exchange now works correctly if there are filenames with spaces in them.

W-11687519
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.7.1 Release Notes ## [](#october-27-2022)October 27, 2022 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.30

Anypoint Studio

7.2 and later
## Fixed Issues
Issue ID

Parsing an API synced from Exchange no longer fails if there are filenames containing spaces.

W-11687519
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.7.2 Release Notes ## [](#october-31-2022)October 31, 2022 ## What’s New - This release updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.30

Anypoint Studio

7.2 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.7.3 Release Notes ## [](#november-10-2022)November 10, 2022 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
Table 1. Dependency
Application/Service Version

Anypoint API Console

6.6.30

Anypoint Studio

7.2 and later
## Fixed Issues
Issue resolution ID

Now union of enums from RAML API specifications are validated correctly.

W-12010817
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.8.0 Release Notes ## [](#december-16-2022)December 16, 2022 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.30

AMF

5.2.2
## Fixed Issues
Issue Resolution ID

An out of memory issue no longer occurs when redeploying a customer application several times.

W-11356027
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.8.1 Release Notes ## [](#january-9-2023)January 9, 2023 ## What’s New - This release updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.30

AMF

5.2.2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.8.2 Release Notes ## [](#february-8-2023)February 8, 2023 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.39

AMF

5.2.3
## Fixed Issues
Issue Resolution ID

Default values for array query parameters are now correctly interpreted.

W-11956701

APIkit now returns all validation errors instead of just the first one.

W-12113783

APIkit now parses correctly repeated array headers with quotes.

W-11365512
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.8.3 Release Notes ## [](#march-17-2023)March 17, 2023 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.39

AMF

5.2.3
## Fixed Issues
Issue Resolution ID

Memory usage is improved.

W-12687160
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.8.4 Release Notes ## [](#april-17-2023)April 17, 2023 ## What’s New - This release updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.42

AMF

5.2.3
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.9.0 Release Notes ## [](#may-15-2023)May 15, 2023 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.42

AMF

5.3.0
### Fixed Issues
Issue Resolution ID

APIkit now supports case-insensitive matching for the Content-Disposition header in a multipart/form-data request.

W-12964758

APIkit now provides better support for flexible matching of boundary parameters in multipart/form-data payloads.

W-12980886

APIkit no longer fails to validate multipart form array parameters.

W-13081661

APIkit improves its validation capabilities to correctly detect illegal leap year dates.

W-13153056
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.9.1 Release Notes ## [](#jun-12-2023)Jun 12, 2023 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.48

AMF

5.3.0
### Fixed Issues
Issue Resolution ID

APIkit no longer fails to load XSD schemas when validating an XML against such XSD schema.

W-13273173
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for Mule 4 1.9.2 Release Notes ## [](#october-27-2023)October 27, 2023 ## What’s New - This release fixes bugs and updates dependencies. ## Compatibility
Application/Service Version

Mule runtime

4.1.5 and later

Anypoint Studio

7.2 and later
## [](#dependency)Dependency
Application/Service Version

Anypoint API Console

6.6.48

AMF

5.4.4
### Fixed Issues
Issue Resolution ID

APIkit now handles query strings with mutually exclusive properties without validation failures.

W-14088058

APIkit no longer throws method-not-allowed exceptions for RAML resources defined at the same level.

W-13223477

APIkit no longer fails to validate object arrays in multipart requests.

W-13749792
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData 1.0.6 Release Notes December 26, 2017 For Studio, this version is distributed as APIkit for OData Feature 1.0.2. ## [](#compatibility)Compatibility - Mule 3.8.1+ - APIkit 3.8.2+ - Anypoint Studio 6.2.3+ ## [](#fixed-in-this-release)Fixed in this Release - ODATA-7 Using maven, it’s necessary to double-click "Mule > Generate OData" to generate the OData configuration. - ODATA-8 OData fails when getting a key value in Int64 format. - ODATA-9 Performance issue: OData is parsing the RAML definition on every request. ## [](#links-to-legacy-odata-documentation)Links to Legacy OData Documentation - [OData Extension Studio Plugin 1.0.1 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-release-notes-101) - [OData Extension Studio Plugin 1.0.0 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-studio-plugin-release-notes) # APIkit for OData 1.0.7 Release Notes August 14, 2018 For Studio, this version is distributed as APIkit for OData Feature 1.0.3. ## [](#compatibility)Compatibility - Mule 3.8.1+ - APIkit 3.8.2+ - Anypoint Studio 6.2.3+ ## [](#fixed-in-this-release)Fixed in this Release - ODATA-44 OData APIKit deployment to CloudHub naming restrictions. - ODATA-43 Improve error message when _odata.raml_ file contains errors. ## [](#links-to-legacy-odata-documentation)Links to Legacy OData Documentation - [OData Extension Studio Plugin 1.0.1 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-release-notes-101) - [OData Extension Studio Plugin 1.0.0 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-studio-plugin-release-notes) # APIkit for OData 1.0.9 Release Notes **December 23, 2018** This release includes bug fixes. ## [](#compatibility)Compatibility - Mule 3.8.1+ - APIkit 3.8.2+ - Anypoint Studio 6.2.3+ ## [](#fixed-in-this-release)Fixed in this Release - Fixed issue where Odata query options `inlinecount`, `top`, and `filter` were not supported. ## [](#links-to-legacy-odata-documentation)Links to Legacy OData Documentation - [OData Extension Studio Plugin 1.0.1 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-release-notes-101) - [OData Extension Studio Plugin 1.0.0 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-studio-plugin-release-notes) # APIkit for OData 2.0.1 Release Notes January 22, 2019 ## [](#compatibility)Compatibility - Mule 4.1.x+ - APIkit M4-1.2.x+ - Anypoint Studio 7.3.x+ ## [](#fixed-in-this-release)Fixed in this Release - APIkit for OData now accepts a number as Edm.String - Upgrade Odata core version. ## [](#links-to-legacy-odata-documentation)Links to Legacy OData Documentation - [OData Extension Studio Plugin 1.0.1 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-release-notes-101) - [OData Extension Studio Plugin 1.0.0 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-studio-plugin-release-notes) # APIkit for OData 2.0.3 Release Notes June 5, 2019 ## [](#compatibility)Compatibility - Mule 4.1.x+ - APIkit M4-1.2.x+ - Anypoint Studio 7.3.x+ ## [](#fixed-in-this-release)Fixed in this Release - Fix error when the path to the RAML contains blank spaces. - Fix error when the entity key contains special characters. ## [](#links-to-legacy-odata-documentation)Links to Legacy OData Documentation - [OData Extension Studio Plugin 1.0.1 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-release-notes-101) - [OData Extension Studio Plugin 1.0.0 Release Notes](https://archive.docs.mulesoft.com/release-notes/studio/odata-extension-studio-plugin-release-notes) # APIkit for OData 2.0.4 for Mule 4 Release Notes **November 1, 2019** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue where APIkit was unable to modify xml:base URL for OData service # APIkit for OData 2.0.5 for Mule 4 Release Notes **August 6, 2020** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue where APIkit `xml:base` was malformed # APIkit for OData 2.0.6 for Mule 4 Release Notes **August 28, 2020** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue wrong base URI returned in APIKit for OData response # APIkit for OData 2.0.7 for Mule 4 Release Notes **February 2, 2021** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fix an issue where OData extension uses wrong EDM type - Fix an issue where OData extension fails to create flows when workspace contains spaces # APIkit for OData 2.0.8 for Mule 4 Release Notes **February 24, 2021** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fix stack overflow issue for very long $select query params # APIkit for OData 2.0.9 for Mule 4 Release Notes **March 3, 2021** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fix issue where request headers were not passed to the subflow # APIkit for OData 2.1.0 for Mule 4 Release Notes **March 16, 2021** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - APIKit 1.5.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue with odata multiple redeploys # APIkit for OData 2.1.1 for Mule 4 Release Notes **May 31, 2021** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - APIKit 1.5.0 and later ## [](#bug-fixes)Bug Fixes - Fixed bug when receiving '&' char in odata $filter system query option # APIkit for OData 2.1.2 for Mule 4 Release Notes ## [](#september-21-2021)September 21, 2021 ## What’s New This release adds the `apikit.odata.skipFilterValidation` system property to avoid filter validation when needed. ## Compatibility
Application/Service Version

Mule runtime engine

4.1.2 and later

Anypoint Studio

7.2.0 and later

APIkit

1.5.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 2.1.3 for Mule 4 Release Notes ## [](#december-2-2021)December 2, 2021 ## What’s New This release focuses on bug fixes. ## Compatibility
Application/Service Version

Mule runtime engine

4.1.2 and later

Anypoint Studio

7.2.0 and later

APIkit

1.5.0 and later
## Fixed Issues
Issue ID

Fixed an issue encoding HTTP attributes.

SE-22594
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 2.1.4 for Mule 4 Release Notes ## [](#may-20-2022)May 20, 2022 ## Compatibility
Application/Service Version

Mule runtime engine

4.1.2 and later

Anypoint Studio

7.2.0 and later

APIkit

1.5.0 and later
## Fixed Issues
Issue ID

OData extension now honors base path in listener configuration.

W-11024817
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 2.1.5 for Mule 4 Release Notes ## [](#february-15-2023)February 15, 2023 ## What’s New - This release fixes bugs. ## Compatibility
Application/Service Version

Mule runtime engine

4.1.2 and later

Anypoint Studio

7.2.0 and later

APIkit

1.5.0 and later
## Fixed Issues
Issue Resolution ID

OData extension no longer loses precision when serializing an Edm.Decimal value.

W-12481800
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 2.2.0 for Mule 4 Release Notes ## [](#april-4-2023)April 4, 2023 ## What’s New - This release fixes bugs and updates dependencies. - This release updates the AMF version used for scaffolding to AMF 5. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

APIkit

1.5.0 and later
## Fixed Issues
Issue Resolution ID

OData extension no longer blocks threads if waiting for flow completion.

W-12697977
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 4 1.0.0 for Mule 4 Release Notes **July 07, 2021** ## [](#compatibility)Compatibility - Mule Runtime 4.3.0 and later - Anypoint Studio 7.9.0 and later # APIkit for OData 4 for Mule 4 1.0.1 Release Notes ## [](#1-0-1)1.0.1 **October 28, 2021** ### What’s New - This release fixes bugs. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
### Fixed Issues
Issue ID

Fixed incorrect composite key from context URL in navigation from entity.

APIKIT-3063

Fixed serialization error when context URL contained special characters.

APIKIT-3064
\* \* # APIkit for OData 4 for Mule 4 1.0.2 Release Notes ## [](#1-0-2)1.0.2 **December 29, 2021** ### What’s New - This release fixes bugs. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
### Fixed Issues
Issue ID

Fixed issue with quotes in query parameters

APIKIT-3110

Fixed metadata for entity collection serializer

APIKIT-3111

Fixed Transform to SQL Select to honor grouping by parentheses in $filter

SE-23726
\* \* # APIkit for OData 4 for Mule 4 1.1.0 Release Notes ## [](#1-1-0)1.1.0 **March 08, 2022** ### What’s New - This release enables you to return response metadata properties from your Mule flows. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 4 for Mule 4 1.2.0 Release Notes ## [](#1-2-0)1.2.0 **May 9, 2022** ### What’s New - This release enables you to use fetch instead of limit, and configure identifiers delimiter in SQL transformation. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
### Fixed Issues
Issue ID

APIkit for OData 4 now displays the appropriate symbol for less than or equal to.

W-10927663
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 4 for Mule 4 1.3.0 Release Notes ## [](#1-3-0)1.3.0 **October 26, 2022** ### What’s New - You can now configure a generic `$expand` implementation by selecting the navigation properties that you want APIKit to expand for each entity. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 4 for Mule 4 1.3.1 Release Notes ## [](#1-3-1)1.3.1 **November 9, 2022** ### What’s New - You can now configure the **databaseSchema** name in the **transform-to-sql-select** operation. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 4 for Mule 4 1.3.2 Release Notes ## [](#1-3-2)1.3.2 **November 23, 2022** ### What’s New - The **generic expand** feature now automatically limits its depth to 2. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData 4 for Mule 4 1.3.3 Release Notes ## [](#1-3-3)1.3.3 **March 16, 2023** ### What’s New - The `$filter` now is propagated with the `generic expand` feature. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
### Fixed Issues
Issue Resolution ID

Null values in foreign keys are removed in the generic expand feature when requesting child entities.

W-12228478
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v2 2.2.1 for Mule 4 Release Notes ## [](#november-21-2023)November 21, 2023 ## What’s New - APIkit for OData v2 2.2.1 is now FIPS 140-2 compliant. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

APIkit

1.8.3 and later

OpenJDK

8 and 11
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v2 2.3.0 for Mule 4 Release Notes ## [](#may-9-2024)May 9, 2024 ## What’s New - APIkit for OData v2 is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v2 2.3.1 for Mule 4 Release Notes ## [](#july-22-2025)July 22, 2025 ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

APIkit for OData v2 now populates variables as expected if using Mule runtime 4.9.x.

W-18022038
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v2 2.3.2 for Mule 4 Release Notes ## [](#august-26-2025)August 26, 2025 ## What’s New - This release upgrades some dependencies to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The cxf-rt-frontend-jaxrs dependency is upgraded to address reported security vulnerabilities.

W-19182588
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v2 2.3.3 for Mule 4 Release Notes ## [](#october-17-2025)October 17, 2025 ## What’s New - This release upgrades the **commons-lang** dependency to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-lang dependency is upgraded to version 20030203.000129 to address reported security vulnerabilities.

W-19857808
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v2 2.3.4 for Mule 4 Release Notes ## [](#november-7-2025)November 7, 2025 ## What’s New - This release upgrades the `commons-lang` and `commons-collections` dependencies to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-lang dependency is upgraded to version 3.19.0 and the commons-collections dependency is upgraded to version 4.3 to address reported security vulnerabilities.

W-20106645
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v2 2.3.5 for Mule 4 Release Notes ## [](#january-23-2026)January 23, 2026 ## What’s New - APIkit for OData introduces new RAML annotations `odata.entitySet` and `odata.entitySetEnabled` to enhance control over the pluralization of entity set names in OData services. For more information, see [APIkit for OData v2 Module リファレンス](https://docs.mulesoft.com/jp/apikit/latest/apikit-odatav2-extension-reference). ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

APIkit for OData no longer pluralizes EntityType names by automatically appending an "s" to create EntitySet names.

W-20133725
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v2 2.4.0 for Mule 4 Release Notes ## [](#april-30-2026)April 30, 2026 ## What’s New - Identify API operations more easily with dynamic telemetry traces Get better visibility into your API behavior with dynamic span naming and new route attributes for OpenTelemetry traces. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [APIkit for OData v2](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav2) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v4 1.6.0 Release Notes ## [](#april-14-2026)April 14, 2026 ## What’s New - Identify API Operations More Easily with Dynamic Telemetry Traces APIkit for OData v4 1.6.0 introduces dynamic telemetry traces that allow you to identify API operations more easily. This enhancement provides better visibility into the performance and behavior of your APIs, making it easier to troubleshoot issues and optimize performance. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

Studio

7.9.0 or later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

APIkit for OData 4 connector no longer results in error if enabling the $expand feature when the parent dataset is empty.

W-21578232
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v4 1.6.1 Release Notes ## [](#july-31-2026)July 31, 2026 ## What’s New - This release upgrades the **jackson-databind** dependency to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

Studio

7.9.0 or later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-databind dependency is upgraded to 2.18.9 to address reported security vulnerabilities.

W-23569199
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v4 1.6.2 Release Notes ## [](#september-22-2026)September 22, 2026 ## What’s New - This release upgrades some dependency to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

Studio

7.9.0 or later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-databind and jackson-core dependencies are upgraded to 2.21.6, and jackson-annotations dependency is upgraded to version 2.21 to address reported security vulnerabilities.

W-23994473
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for OData v4 for Mule 4 1.3.4 Release Notes ## [](#may-4-2023)May 4, 2023 ## What’s New - APIkit for OData v4 1.3.4 is now FIPS 140-2 compliant. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The query parameters generated by the Transform to SQL Select operation now handle the correct boolean values.

W-13067134
## [](#see-also)See Also - [APIkit for OData v4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v4 for Mule 4 1.4.0 Release Notes ## [](#may-9-2024)May 9, 2024 ## What’s New - APIkit for OData v4 is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [APIkit for OData v4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v4 for Mule 4 1.4.1 Release Notes ## [](#june-10-2024)June 10, 2024 ## What’s New - APIkit for OData v4 1.4.1 introduces the [`Date Transform Type` parameter](https://docs.mulesoft.com/jp/apikit/latest/apikit-odatav4-transform-to-sql-operation) in the `transform to sql select` operation, enabling the seamless transformation of `Date/DateTime` OData parameters to either `strings` or `java.time` objects enhancing data consistency and reducing manual coding effort. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The query parameters that the Transform to SQL Select operation generates now handle the correct date/datetime values.

W-15954804
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v4 for Mule 4 1.4.2 Release Notes ## [](#july-9-2024)July 9, 2024 ## What’s New - APIkit for OData v4 1.4.2 adds the `java.time - LocalDate and LocalDateTime` and `java.time - LocalDate and OffsetDateTime` options to the [`Date Transform Type` parameter](https://docs.mulesoft.com/jp/apikit/latest/apikit-odatav4-transform-to-sql-operation#implement-the-transform-to-sql-select-operation-by-using-apikit-for-odata-v4) to enhance precision and flexibility in handling dates and times. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The request parameters are now correctly recognized if they contain special characters such as +.

W-15807826

Incoming queries now effectively resolve the issue of malformed SQL queries in the absence of an orderBy parameter if the FETCH_NEXT_ROWS_ONLY option is selected for the SQL Limit Rows parameter in the transform to sql select operation.

W-16165146

APIkit for Odata now correctly resolves unexpected class loading logs and call-site initialization exceptions for Mule runtime 4.3 and 4.4.

W-16189071
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v4 for Mule 4 1.4.3 Release Notes ## [](#july-23-2024)July 23, 2024 ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The error type from the subflow is now saved and correctly sent to the main flow.

W-15938107
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v4 for Mule 4 1.5.0 Release Notes ## [](#july-25-2024)July 25, 2024 ## What’s New - You can now have a consistent [`route correlation id`](https://docs.mulesoft.com/jp/apikit/latest/apikit-odatav4-extension-reference) parameter in the `route` operation across subsequent flows to enhance traceability and simplify the debugging process of systems using APIkit for OData. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

APIkit for OData v4 now sets the same correlation id parameter in subsequent flows.

W-16094462
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v4 for Mule 4 1.5.1 Release Notes ## [](#august-12-2024)August 12, 2024 ## What’s New - You can now use the new [`searchFieldsAsType` search transformation option](https://docs.mulesoft.com/jp/apikit/latest/apikit-odatav4-extension-reference) to typecast columns to `TEXT` in the `WHERE` clauses to improve the `$search` operation with PostgreSQL databases. ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

APikit for OData v4 no longer makes PostgreSQL DB throw an error for non-text-based columns during comparison if using the $search operation.

W-14645981
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for OData v4 for Mule 4 1.5.2 Release Notes ## [](#september-20-2024)September 20, 2024 ### Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.9.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now use the $top, $skip, and $search query parameters at the nested levels of the $expand parameter as expected.

W-16408499

The`NavigationProperty` for OData entities can now have multiple referential constraints to enable expansion with two matching criteria.

W-16408486
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.0.1 Release Notes **March 21, 2017** This version of APIKit for SOAP includes a fix in the runtime. This solves a problem when using a SOAP Envelope element with an xmlns:xsi namespace definition. ## [](#compatibility)Compatibility - Mule Runtime 3.7.3 and 3.8.x - Anypoint Studio 6.2.3 ## [](#fixed-in-this-release)Fixed in This Release APIKITSOAP-58 APIKit SOAP + DataWeave = Undeclared namespace prefix "xsi" # APIkit for SOAP 1.0.2 Release Notes **September 8, 2017** This version of APIkit for SOAP includes a fix to the runtime. In Studio, if a SOAP action is not defined, an attempt to generate flows based on a WSDL (scaffold a WSDL) now throws an error message: `SOAP action is required`. The scaffolding process is aborted. No flows are generated. For Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.3. ## [](#compatibility)Compatibility - Mule Runtime 3.7.3 and 3.8.x - Anypoint Studio 6.2.3 and later ## [](#fixed-in-this-release)Fixed in This Release APIKITSOAP-62 The SOAP router should log error message when the SOAP action is undefined. # APIkit for SOAP 1.0.3 Release Notes **December 1, 2017** This version of APIkit for SOAP includes a fix to the runtime. In this version and later, you do not need to specify the SOAP action to route messages to the correct flow. In earlier versions of APIkit for SOAP, the SOAP action was mandatory and the scaffolding process was aborted if the WSDL did not include it. Additionally, two minor fixes were included in this release. For Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.4. ## [](#compatibility)Compatibility - Mule Runtime 3.7.3, 3.8.x, and 3.9.x - Anypoint Studio 6.2.3+ ## [](#fixed-in-this-release)Fixed in This Release - APIKITSOAP-93 SOAP action should not be mandatory - APIKITSOAP-108 Route messages correctly when SOAP action is not specified - APIKITSOAP-83 SOAP Router not generated when scaffolding an existing project with no SOAP router defined - APIKITSOAP-81 Scaffolder now validates that the operations in WSDL have a valid input/output (SE-6113) # APIkit for SOAP 1.0.4 Release Notes **April 23, 2018** This version of APIkit for SOAP includes only one fix to the runtime. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.4. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

3.7.3, 3.8.x, and 3.9.x

Anypoint Studio

6.2.3 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - When accessing a SOAPkit Service endpoint, SOAPkit throws a NPE. (APIKITSOAP-186) ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.0.5 Release Notes **July 4, 2018** This version of APIkit for SOAP includes two fixes to the runtime. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.5. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

3.7.3, 3.8.x, and 3.9.x

Anypoint Studio

6.2.3 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - SOAP Fault namespaces fixed according to SOAP Version (APIKITSOAP-201) - Routing to the correct flow when no soapAction is defined (APIKITSOAP-208) ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.0.7 Release Notes **May 29, 2019** This version of APIkit for SOAP includes fixes to the runtime. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

3.7.3, 3.8.x, and 3.9.x

Anypoint Studio

6.3.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - Fixed issue when schema validation ()```inboundValidationMessage="true"``) returned the tag names enclosed by `<``>``` in a `SOAP:fault`. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.0.7 Release Notes **October 22, 2019** This version of APIkit for SOAP includes fixes to the runtime. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

3.7.3, 3.8.x, and 3.9.x

Anypoint Studio

6.3.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - Fixed issue where a `SAXParseException` was thrown when running a project that has been scaffolded after creating a new project. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.0 Release Notes **April 3, 2018** This new version of APIkit for SOAP is intended to run with Mule Runtime 4. It has the same functionality than previous versions. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.0. ## [](#compatibility)Compatibility - Mule Runtime 4.1.0+ - Anypoint Studio 7.1.0+ - SOAP 1.1 and 1.2 # APIkit for SOAP 1.1.1 Release Notes **February 7, 2018** This version of APIkit for SOAP includes a fix to the runtime. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.1. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - RuntimeException error creating a Config from scratch. (APIKITSOAP-163) ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.10 Release Notes **November 6, 2018** This version of APIkit for SOAP includes bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#issues-fixed-in-this-release)Issues Fixed in this Release - Fixed performance issue where SOAP APIkit Router executed a blocking operation when executing `cpuLight` and `cpuIntensive` types of threads. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.11 Release Notes **February 6, 2019** This version of APIkit for SOAP includes bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#issues-fixed-in-this-release)Issues Fixed in this Release - Fixed issue that prevented metadata from working when importing a project created in Windows. - Fixed issue that caused SOAP APIkit to return a `200 Status Code` for `Schema Validation Fault`. - Fixed issue that caused an error in SOAP operation to return `SOAP fault` but to not trigger a `` and ``, and to return a `HTTP Status 200` response. - Fixed issue causing a `Unbound namespace prefix` error for working Mule applications. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.12 Release Notes **April 5, 2019** This version of APIkit for SOAP includes bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#issues-fixed-in-this-release)Issues Fixed in this Release - `HTTP status` is now a protocol header to maintain backwards compatibility. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.2 Release Notes **April 3, 2018** This version of APIkit for SOAP includes a fix to the runtime. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.2. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - RuntimeException error creating a Config from scratch. (APIKITSOAP-168) - WSDL from URL not working. (APIKITSOAP-169) - Sometimes scaffolding of flows in Windows does not work. (APIKITSOAP-170) - Metadata Keys in Windows do not work, the Service and Port combo boxes are never populated with values. (APIKITSOAP-171) - Fixed Fault Metadata behavior. (APIKITSOAP-176) ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.3 Release Notes **July 24, 2018** This version of APIkit for SOAP includes bug fixes. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.1.3. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - Use currentThread().classloader to load WSDL. - WSDL and xsd resources are now included in mule-artifact.json. - Backport: APIKIT For SOAP is not routing to the correct flow when no soapAction defined. - Scaffolder does not load the full WSDL definition with references. - Upgrade WSDLParser version in SOAPKIT for M4. - Failed to deploy artifact `[soap-exp-api]` when creating a Mule application based on WSDL. - Referenced WSDL and XSD are not copied to `/api` during scaffolding. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.4 Release Notes **August 31, 2018** This version of APIkit for SOAP includes bug fixes. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.2.2. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - Error message improved when selecting an invalid WSDL file. - XSD and WSDL files are not being imported when creating a Mule project using WSDL. - Blank spaces in XSD folder names are created with %20 instead of blank spaces. - SoapKit Tooling fail in Studio 7.2.0. - Avoid Connection Server Error when SOAP Version is wrong. - SOAPKit tooling error in Studio Console when scaffolding a WSDL file. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.5 Release Notes **October 5, 2018** This version of APIkit for SOAP includes bug fixes. For Anypoint Studio, this version is distributed as Anypoint APIkit SOAP Extension 1.2.3. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - APIKit for Soap Router doesn’t route correctly when multiple port types are present in a WSDL. - Sometimes XSD and WSLD files are not being imported when creating a Mule project using WSDL. - Deduce automatically SOAP Version from WSDL. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.6 Release Notes **October 29, 2018** This version of APIkit for SOAP includes bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - `publishedEndpointUrl` can not be configured when using Apikit:soap router. ## [](#tasks-completed-in-this-release)Tasks Completed in This Release - Remediate vulnerabilities detected by NexusIQ. - Release APIKit for SOAP M4-1.1.6. - Release Tooling for APIKit for SOAP M4-1.1.6. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.7 Release Notes **November 12, 2018** This version of APIkit for SOAP includes bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#fixed-in-this-release)Fixed in This Release - SOAP API Kit is discarding the attributes and variables. - APIKit for SOAP does not preserves CDATA tags on SOAP. - APIKit for SOAP is failing validation when attribute is present. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.8 Release Notes **November 23, 2018** This version of APIkit for SOAP includes bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#tasks-completed-in-this-release)Tasks Completed in This Release - Release APIKit for SOAP M4-1.1.8. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.1.9 Release Notes **January 28, 2019** This version of APIkit for SOAP includes bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#issues-fixed-in-this-release)Issues Fixed in this Release - Fixed issue where APIKit was not propagating the variables and attributes set in the flow preventing to set a dynamic HTTP status code. The status code is now reachable using the variable `protocolHeader`. - Fixed issue where the SOAP Router was not validating headers. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIKit for SOAP 1.2.0 Release Notes **May 28, 2019** This version of APIkit for SOAP includes the capability to set custom prefixes for the namespaces of the XML responses and bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#enhancements)Enhancements - Added the capability to change namespaces prefixes on APIKit for SOAP responses ## [](#issues-fixed-in-this-release)Issues Fixed in this Release - Fixed issue when payload set in an `on error propagate` for a SOAP Fault wasn’t returned to the caller. - Fixed issue when `SOAPRouter` was not trowing any error and did not go in to the error handling block. - Fixed issue when APIKit soap did not support simple type message parts on operations. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIKit for SOAP 1.2.1 Release Notes **July 10, 2019** This version of APIkit for SOAP is focused on performance and bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#issues-fixed-in-this-release)Issues Fixed in this Release - Fixed error when SOAP Router was impacting significantly on the response time of the application. - Fixed error when the stream is closed when working with a big payload. - Fixed error when `errorDescription` was unable to propagate from subflow using APIKit for SOAP. ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.2.10 Release Notes **March 16, 2021** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 ## [](#bug-fixes)Bug Fixes - Fixed an issue when soap body contains multiple parts # APIkit for SOAP 1.2.11 Release Notes **Jun 1, 2021** ## [](#whats-new)What’s New This release focuses on dependencies updates. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 # APIkit for SOAP 1.2.12 Release Notes **Jun 23, 2022** ## [](#whats-new)What’s New This release updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 # APIKit for SOAP 1.2.2 Release Notes **July 12, 2019** This release fixes a vulnerability that was present on CXF Woodstox version 2.7.18. APIKit for SOAP now uses `cxf-core` (3.2.5) + `woodstox` (5.0.3). ## [](#compatibility)Compatibility
Software Version

Mule Runtime

4.1.0 and later

Anypoint Studio

7.1.0 and later

SOAP

1.1 and 1.2
## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.2.3 Release Notes **September 13, 2019** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 ## [](#bug-fixes)Bug Fixes - Fixed issue where variables created in the operational flow were not available once the flow execution completed and invocation returned back to the main flow. - Fixed issue where SOAPKit router failed after a WSDL file had been retrieved. - Fixed issue where a WSDL retrieved from SOAPkit via HTTPS had HTTP `soap:address` on CloudHub. # APIkit for SOAP 1.2.4 Release Notes **January 8, 2020** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 ## [](#bug-fixes)Bug Fixes - Fixed issue regarding repeatable streaming on SOAP response # APIkit for SOAP 1.2.5 Release Notes **March 12, 2020** ## [](#whats-new)What’s New This release focuses on dependencies update. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 # APIkit for SOAP 1.2.6 Release Notes **March 13, 2020** ## [](#whats-new)What’s New This release focuses on dependencies update. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 # APIkit for SOAP 1.2.7 Release Notes **June 29, 2020** ## [](#whats-new)What’s New Added extension icon ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 # APIkit for SOAP 1.2.8 Release Notes **October 27, 2020** ## [](#whats-new)What’s New This release fixes bugs and updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 ## [](#bug-fixes)Bug Fixes - Fixed issues in namespaces with `xsi`. # APIkit for SOAP 1.2.9 Release Notes **January 28, 2021** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 ## [](#bug-fixes)Bug Fixes - Fixed a performance issue under high load that occurred when running a blocking operation that introduces a delay. # APIkit for SOAP 1.3.0 Release Notes **Nov 17, 2022** ## [](#whats-new)What’s New This release updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - SOAP 1.1 and 1.2 # APIkit for SOAP 1.3.1 Release Notes ## [](#1-3-1)1.3.1 **January 12, 2023** ### What’s New - This release fixes bugs and removes unused dependencies. ### Compatibility
Application/Service Version

Mule Runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2
### Fixed Issues
Issue Resolution ID

Charset propagation now works as expected when router executes flows.

W-12221453

Variables are handled correctly when routed flows result in a fault message.

W-12011863
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.3.2 Release Notes ## [](#1-3-2)1.3.2 **March 01, 2023** ### What’s New - This release updates dependencies. ### Compatibility
Application/Service Version

Mule Runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.3.3 Release Notes ## [](#1-3-3)1.3.3 **March 21, 2023** ### What’s New - This release updates dependencies. ### Compatibility
Application/Service Version

Mule Runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.3.4 Release Notes ## [](#1-3-4)1.3.4 **April 24, 2023** ### What’s New - This release updates dependencies. ### Compatibility
Application/Service Version

Mule Runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.4.0 Release Notes ## [](#1-4-0)1.4.0 **Jul 18, 2023** ### What’s New - The APIkit for SOAP configuration now has the new `inboundValidationMessageLevel` property that enables you to throw an error if the payload validation fails. ### Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.4.1 Release Notes ## [](#november-30-2023)November 30, 2023 ### What’s New - APIkit for SOAP 1.4.1 is now FIPS 140-2 compliant. ### Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

APIkit for SOAP now does not parse the WSDL file more than once.

W-14372798
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.5.0 Release Notes ## [](#may-31-2024)May 31, 2024 ### What’s New - APIkit for SOAP is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.5.1 Release Notes ## [](#july-24-2024)July 24, 2024 ### Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

APIkit for SOAP now successfully deploys to CloudHub with JDK 17 when built using Maven.

W-16270022
### Known Issues

Known Issue

Workaround

ID

APIkit for SOAP loses payload and variables with some flow errors.

Rebuild the fault payload within the main error handler.

W-10647938
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) # APIkit for SOAP 1.5.2 Release Notes ## [](#february-7-2025)February 7, 2025 ## What’s New - The **org.apache.cxf:cxf-core** module of the Apache CXF library is updated to 3.5.9. - APIkit for SOAP can now handle C0 control characters. To enable this feature, set the system property `mule.soapkit.allowControlCharacters` to `true`. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP can now handle C0 control characters.

W-16270022
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.0 Release Notes ## [](#january-31-2025)January 31, 2025 ## What’s New - In alignment with the release of Mule runtime engine 4.9, APIkit for SOAP 1.6.0 and later drops support for the `SoapSdk` and `SoapService` components. APIkit for SOAP 1.6.0 and later uses the `SoapClient` component instead of using the `SoapSdk` and `SoapService` components so you don’t use components that have known vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP now handles C0 control characters, which are supported in XML 1.1.

W-17241557

The SOAP router no longer omits the prolog tag from the XML SOAP response during transformation.

W-17084554
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.1 Release Notes ## [](#march-5-2025)March 5, 2025 ## What’s New - APIkit upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP removes several indirect dependencies so that the file size is no longer increased when upgrading the module.

W-17849012
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.10 Release Notes ## [](#february-6-2026)February 6, 2026 This version is deprecated. All the features and fixed issues for this version are available in APIkit for SOAP 2.0.0 and later. ## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.2 Release Notes ## [](#june-3-2025)June 3, 2025 ## What’s New - APIkit upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.3 Release Notes ## [](#july-31-2025)July 31, 2025 ## What’s New - APIkit upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

The runtime classpath issue in SOAPkit 1.6.2 is now resolved and no longer causes a NoClassDefFoundError during API calls in Mule apps that are compiled with JDK 8 and running on Mule 4.9.x with JDK 17.

W-18961619

Upgraded the cxf-core dependency to address reported security vulnerabilities.

W-18979187
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.4 Release Notes ## [](#august-26-2025)August 26, 2025 ## What’s New - APIkit upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

The org.apache.cxf dependency is upgraded to address reported security vulnerabilities.

W-19175579
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.5 Release Notes ## [](#october-17-2025)October 17, 2025 This version is deprecated. All the features and fixed issues for this version are available in APIkit for SOAP 2.0.0 and later. ## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.6 Release Notes ## [](#october-28-2025)October 28, 2025 This version is deprecated. All the features and fixed issues for this version are available in APIkit for SOAP 2.0.0 and later. ## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.7 Release Notes ## [](#january-9-2026)January 9, 2026 This version is deprecated. All the features and fixed issues for this version are available in APIkit for SOAP 2.0.0 and later. ## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.8 Release Notes This version is deprecated. All the features and fixed issues for this version are available in APIkit for SOAP 2.0.0 and later. ## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.6.9 Release Notes ## [](#january-30-2026)January 30, 2026 This version is deprecated. All the features and fixed issues for this version are available in APIkit for SOAP 2.0.0 and later. ## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.7.0 Release Notes ## [](#april-6-2026)April 6, 2026 ## What’s New - This release upgrades internal dependencies to address security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

The Apache Commons Lang (commons-lang3) library is upgraded to version 3.18.0 to address security vulnerabilities.

W-19174629

The Gson (com.google.code.gson:gson) library is upgraded to version 2.12.0 to address security vulnerabilities.

W-21508262

The Log4j Core (org.apache.logging.log4j:log4j-core) library is upgraded to version 2.25.3 to address security vulnerabilities.

W-21508262
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.7.1 Release Notes ## [](#june-23-2026)June 23, 2026 ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP now correctly routes RPC-style SOAP operations when the WSDL specifies empty soapAction attributes and the incoming request omits the SOAPAction HTTP header.

W-19810193
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 1.7.2 Release Notes ## [](#july-31-2026)July 31, 2026 ## What’s New - This release upgrades the **log4j** dependency to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.1.2 and later

Anypoint Studio

7.2.0 and later

SOAP

1.1 and 1.2

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP updates the log4j dependency to 2.25.5 to address reported security vulnerabilities.

W-23572962
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.0.0 Release Notes ## [](#april-6-2026)April 6, 2026 ## What’s New - Develop SOAP-based APIs with support for Java 17 and Mule runtime 4.9.11 and later. This version includes the latest security fixes, resolves compatibility issues found in previous patches, and serves as the foundation for future updates in this major version line. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP now properly terminates DelayedCachedOutputStreamCleaner threads after use, preventing thread accumulation over time.

W-1979374133
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.0 Release Notes ## [](#april-30-2026)April 30, 2026 ## What’s New - Identify API operations more easily with dynamic telemetry traces Get better visibility into your API behavior with dynamic span naming and new route attributes for OpenTelemetry traces. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.1 Release Notes ## [](#june-23-2026)June 23, 2026 ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP now correctly routes RPC-style operations if WSDL files define empty soapAction attributes and requests omit the SOAPAction HTTP header.

W-19810193
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.2 Release Notes ## [](#july-31-2026)July 31, 2026 ## What’s New - This release upgrades the **log4j** dependency to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP updates the log4j dependency to 2.25.5 to address reported security vulnerabilities.

W-23572962
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.3 Release Notes ## [](#august-7-2026)August 7, 2026 ## What’s New - This release upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP upgrades its Apache CXF dependency to 4.1.7, along with the related jakarta.annotation-api and jakarta.xml.ws-api dependencies, to address reported security vulnerabilities.

W-23600823
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.4 Release Notes ## [](#august-27-2026)August 27, 2026 ## What’s New - This release upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP upgrades its Apache CXF dependency to 4.1.8 to address reported security vulnerabilities.

W-23664309
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.5 Release Notes ## [](#september-21-2026)September 21, 2026 ## What’s New - This release upgrades some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP upgrades its Jetty dependency to 12.0.38 to address reported security vulnerabilities.

W-24116112
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.6 Release Notes ## [](#october-1-2026)October 1, 2026 ## What’s New - This release includes only non-user-impacting changes. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit for SOAP 2.1.7 Release Notes ## [](#october-22-2026)October 22, 2026 ## What’s New - This release upgrades the Spring library to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Mule runtime

4.9.11 and later

Anypoint Studio

7.21.0 and later

SOAP

1.1 and 1.2

OpenJDK

17
## Fixed Issues
Issue Resolution ID

APIkit for SOAP upgrades its Spring library to address reported security vulnerabilities.

W-24468359
## [](#see-also)See Also - [APIkit for SOAP](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-soap) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.1.16 for Mule 4 Release Notes **August 21, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue where API console was not fully limiting the resources in its base path. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.2.5 for Mule 4 Release Notes **August 21, 2019** ## [](#whats-new)What’s New This release focuses on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue where a non closed `FileInputStream` threw an error when trying to delete a project with an API dependency. - Fixed issue where flow names were being generated with extra content causing invalid name errors. - Fixed `Invalid form parameter` exception caused when sending a Multipart request with Form-Data in RAML using APIKit. - Fixed issue where the RAML Parser v2 implementation did not parse API that included the `exchange_module` folder. - Fixed APIKit validation error after version 1.1.9. - Fixed issue where APIKit returned 404 for URLs with `:`. - Fixed issue where API console was not fully limiting the resources in its base path. ## [](#improvements)Improvements - Updated APIKit Console ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.1 for Mule 4 Release Notes **May 24, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue causing `Invalid URI` message when using absolute `includes` from files in subfolders. - Fixed issue when flow names were generated with charset content. - Fixed issue when schemas (JSON or XML) referenced from other schemas in a RAML file were not being considered. - Fixed `apikit.exception.NotAcceptableException` when using charset in OAS response types. - Fixed issue when APIKit returned 404 for URL with colons (`:`). - Fixed issue where APIKit did not send an error response when a request leads to an exception. ## [](#improvements)Improvements - Support JSON and XML files as form parameters ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.10 for Mule 4 Release Notes **March 13, 2020** ## [](#whats-new)What’s New - Anypoint API console v6.0.49 - This release is focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.3 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed issues - Special characters in request query parameters causing validation errors - Fix error message behavior changed - Query params get lost after APIKit Router - Unexpected Shape class amf.client.model.domain.FileShape when posting multipart/form file - Invalid APIKit WARN messages when two APIKit routers included in project ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.11 for Mule 4 Release Notes **April 17, 2020** ## [](#whats-new)What’s New This release is focused on performance improvements and enhancements to APIkit usability, including: - Improved performance of the execution of API implementations - Fixing headers validation message - Better distinguishing of parsing errors from parsing warnings in the API scaffolding process ## [](#compatibility)Compatibility - Mule Runtime 4.1.3 and later - Anypoint Studio 7.2.0 and later - Bundled with Anypoint Studio 7.5.0 and Mule runtime 4.3.0 for optimal usability. ## [](#bug-fixes-in-detail)Bug Fixes in detail - Fixed TPS degradation issue. - Fixed issue where AMF validation reports contained warnings, APIKit report contained errors instead of warnings. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.12 for Mule 4 Release Notes **May 8, 2020** ## [](#whats-new)What’s New This release is focused on memory and thread management improvements, including: - Anypoint API console v6.0.52 ## [](#compatibility)Compatibility - Mule Runtime 4.1.3 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes-in-detail)Bug Fixes in detail - Fixed invalid error for length validation of number over 16 digits - Application with APIKit throws OutOfMemory Metaspace error with consecutive re-deploys ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.13 for Mule 4 Release Notes **July 2, 2020** ## [](#whats-new)What’s New - APIKit can now resolve parameter validation with leading zeros. - Introduced clearer error messages for parsing OAS 3.0 specifications. - Anypoint API console v6.0.61. ## [](#compatibility)Compatibility - Mule Runtime 4.1.3 and later. - Anypoint Studio 7.2.0 and later. ## [](#fixed-issues)Fixed issues - Fixed issue in which a long URI parameter with leading zeros was not being validated by APIKit. - APIKit with AMF parser no longer returns a wrong position and column number when a payload doesn’t match the RAML pattern. - Remove local packages that are exported by the runtime. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.14 for Mule 4 Release Notes **August 11, 2020** ## [](#whats-new)What’s New This release is focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed issues - Fixed an issue in which the APIKit router failed when both the space(`%20`) and colon(`:`) characters value existed in the URI parameter. - Fixed an issue in which an APIkit project built from a RAML specification gets a `500 Server Error` reponse from a POST method instead of the expected `405 method not allowed` response. - Fixed issue in which APIkit returned `No enum constant org.mule.apikit.model.ActionType.LINK` instead of `Method not allowed`. - Fixed issue in which Mule 4 API Console still pointed to `localhost`. - Fixed `AMF-SCHEDULER` issue during CloudHub deployments. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.15 for Mule 4 Release Notes **September 2, 2020** ## [](#whats-new)What’s New This release is focused on dependencies updates and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.3 ## [](#fixed-issues)Fixed issues - Fixed an issue where 500 error code was being returned instead of 415 for unsupported media type. - Fixed an issue validating payloads with special characters. - Fixed an issue where apps packaged with old http requester versions fails. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.16 for Mule 4 Release Notes **September 15, 2020** ## [](#whats-new)What’s New This release is focused on dependencies updates and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fixed an issue where MUnit failed when APIKit was upgraded from 1.3.4 to 1.3.12 ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.17 for Mule 4 Release Notes **October 20, 2020** ## [](#whats-new)What’s New This release fixes bugs and updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fixed an issue that caused an application running on Mule runtime engine 4.2.0 on CloudHub was unable to send an error response back to the client when Auto Discovery was enabled ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.18 for Mule 4 Release Notes **November 03, 2020** ## [](#whats-new)What’s New This release fixes bugs and updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fixed an issue where APIKit router failed when both space (`%20`) and colon (`:`) values existed in a URI param. - Fixed an issue where APIKit was not accepting colons (`:`) in URL paths declared in the API. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.19 for Mule 4 Release Notes **January 28, 2021** ## [](#whats-new)What’s New This release fixes bugs. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fixed an issue where APIKit not validating 'Accept' header correctly and returning an appropriate http code. - Fixed an issue where APIKit returns 405 Method Not Allowed instead of 404. - Fixed an issue where APIKit not able to parse base URI when HTTP Listener path contains a URI Params. - Fixed an issue where APIKit no longer accepts query parameters of type "any". - Fixed APIKit heap memory leak in cache. - Fixed ConcurrentModificationException thrown by APIKIT validating query parameters. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.2 for Mule 4 Release Notes **May 29, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue regarding a size limit for multipart form-data requests. - Upgraded several libraries versions that were causing security violations. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.3 for Mule 4 Release Notes **June 21, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. Updated API Console to the latest version. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed issues - Off-by-slash Path Travel when performing request - Uri params attributes should be added when validation is disabled - APIKit console should allow custom headers - Console resources should be relative to path ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.4 for Mule 4 Release Notes **July 8, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed issues - APIKit console can’t scroll `Response`. - Parallel deployment fails with `ConcurrentModificationException`. - Encoded URI parameter gives `APIKIT:NOT_FOUND`. - HTTP request hang without response when API auto-discovery is enabled. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.5 for Mule 4 Release Notes **August 21, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#bug-fixes)Bug Fixes - Fixed issue where the encoded URI parameter returned `APIKIT:NOT_FOUND`. - Fixed issue causing an `Illegal characater <:>` error in Windows. - Fixed issue where handling form-data dropped everything after the first space in a filename. - Fixed issue where, while validating a multipart payload, APIkit changed the boundary in the validated payload, even when no modification to any part was being done. - Fixed issue where API console was not fully limiting the resources in its base path. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.6 for Mule 4 Release Notes **September 2, 2019** ## [](#whats-new)What’s New You can now fully disable the APIKit console by setting `apikit.console.disabled` system property to `true`. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed Issues - Fixed issue where the `MessageProcessor` subflow exceptions are not correctly propagated to the APIkit main flow. - Fixed issue where APIkit AMF validation is only reporting the first error. - Fixed issue with RAML 0.8 in Windows machines. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.7 for Mule 4 Release Notes **November 7, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed issues - Fixed issue that prevented to propagate events when a subflow failed. - Fixed issue getting includes from API using API Sync. - Fixed issue where query params starting with asterisk were not supported. - Fixed issue importing public API from Exchange. - Fixed issue where an API with spaces in its name caused errors initializating API Sync. - Fixed issue where API Console did not scroll in the side bar. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.8 for Mule 4 Release Notes **October 15, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed issues - Fixed issue where APIKIT did not handle exceptions properly on query parameter validations. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.3.9 for Mule 4 Release Notes **January 10, 2020** ## [](#whats-new)What’s New - Anypoint API console v6 - This release is focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.3 and later - Anypoint Studio 7.2.0 and later ## [](#fixed-issues)Fixed issues - Fixed issue that prevented APIKit console to be displayed on "Firefox" or "Microsoft Edge" if the API includes content-type multipart - Fixed issue that prevented API Console to scroll in the body in side bar - Fixed issue where APIKit was consuming http body with content-type multipart - Fixed issue where adding query parameter not defined in RAML returned NullPointerException ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.4.0 for Mule 4 Release Notes **December 01, 2020** ## [](#whats-new)What’s New OAS 3 support. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - APIkit now allows sending type array headers as multiple values in one entry. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.4.1 for Mule 4 Release Notes **December 22, 2020** ## [](#whats-new)What’s New This release fixes bugs and updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fixed an issue that prevented APIkit from correctly validating the `Accept` header and returning an appropriate HTTP code. - Fixed an issue that caused APIkit to return a 405 "Method Not Allowed" status code instead of a 404 status code. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.4.2 for Mule 4 Release Notes **February 1, 2021** ## [](#whats-new)What’s New This release fixes bugs and updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fixed an issue where APIKit was not able to parse base URI when the HTTP Listener path contained URI Params. - Fixed APIKit heap memory leak in cache. - Fixed `ConcurrentModificationException` thrown by APIKIT when validating query parameters. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.5.0 for Mule 4 Release Notes **March 16, 2021** ## [](#whats-new)What’s New This release fixes bugs. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fixed an issue where apikit not able to parse AMF Model - Fixed an issue where RecursiveShape cannot be cast to AnyShape - Fixed an issue where apikit console does not show the right body ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.5.1 for Mule 4 Release Notes **March 29, 2021** ## [](#whats-new)What’s New This release fixes bugs and updates dependencies. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.3.8 ## [](#fixed-issues)Fixed issues - Fixed an issue while validating xml payload ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.5.2 for Mule 4 Release Notes **June 2, 2021** ## [](#whats-new)What’s New This release fixes bugs. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.2.6 ## [](#fixed-issues)Fixed issues - Fix issue where AMF provides wrong path to the resource loader. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.5.3 for Mule 4 Release Notes **July 6, 2021** ## [](#whats-new)What’s New This release fixes bugs. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.4.22 ## [](#fixed-issues)Fixed issues - Fix issue validating dates where year has 5 digits. - Fix issue where the console added an extra comma to the arrays. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Module 1.5.4 for Mule 4 Release Notes **August 10, 2021** ## [](#whats-new)What’s New This release fixes bugs. ## [](#compatibility)Compatibility - Mule Runtime 4.1.5 and later - Anypoint Studio 7.2.0 and later ## [](#dependencies)Dependencies - Anypoint API Console 6.4.22 ## [](#fixed-issues)Fixed issues - Fix issue validating OAS specifications parameters - Fix issue validating bodies defined without media type at OAS 2.0 specifications - Fix issue validating large multipart requests without defaults - Fix issue validating query strings when there is a leading asterisk (\*) in a string field ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.0 Release Notes **January 19, 2018** ## [](#whats-new)What’s New APIkit for SOAP ## [](#compatibility)Compatibility - Mule Runtime 4.1.0 - Anypoint Studio 7.1.0 - Java Parser RAML 1.0 v1.0.17 - Java Parser RAML 0.8 v0.8.21 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - APIkit config does not resolve RAMLs defined as a URL. (APIKIT-1091) - Field localAddress added to APIkit metadata. (APIKIT-1107) - Resolve {version} at resource level. (APIKIT-754) - Implement a custom ResourceLoader to manage Exchange Modules. (APIKIT-1099) - If query param starts with asterisk, surround it with quotes when validating. (APIKIT-1013) - API Console does not work with XML schema. (APIKIT-1131) - Performance overhead using APIkit router. (APIKIT-1146) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.1 Release Notes **March 12, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.1 and later - Anypoint Studio 7.1.1 and later - Java Parser RAML 1.0 v1.0.19 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - BaseUri was incorrectly rewritten on CloudHub (APIKIT-1208) - Upgraded Jackson library to 2.9.4. GitHub RAML Java Parser issues fixed in this release: - RAML parser validates additional properties before explicit ones. #468 - StackOverflowError parsing RAML with recursion. #460 - Global context is not taken into account when parsing libraries. RP-273 and #457 - NPE when parsing RAML files containing included fragments that reference types defined in the root RAML. RP-253 and #453 - Invalid reference when using a resourceType fragment that implements a trait which uses a type defined in the root RAML. #454 - Disabling Default Typing in ObjectMappers. #473 ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.10 Release Notes **October 16, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - Apikit archetype must generate heavyweight apps. - APIkit is discarding the variables set in the error handler. ## [](#enhancements-in-this-release)Enhancements in this release - Add Scaffolder Report to APISync Scaffolder ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.11 Release Notes **November 6, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - When scaffolding more than 1 API with same root name, it only scaffolds one. - When updating an API and scaffolding it, it duplicates the whole application. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.12 Release Notes **December 18, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - RAML validation Error when using a negative decimal. - Generate Flows from REST API is failing. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.13 Release Notes **January 29, 2019** ## [](#whats-new)What’s New There are no new features in this version. There are bug fixes and enhancements. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - Fixed internal tests that were not running on M4-1.1.x. - Fixed error that prevented validation for "Method not allowed" when using the api in 1.1.x. - Fixed issue where APIKIT was not resolving `%20` parameters in URI params. ## [](#enhancements)Enhancements - Exported `disableValidations` to the apikit 1.1.x API for Mule 4 ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.14 Release Notes **February 4, 2019** ## [](#whats-new)What’s New There are no new features in this version. There are bug fixes and enhancements. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - Fixed issue for RAML validator failing with `NullPointerException`. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.2 Release Notes **May 2, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.1.2 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - URI params should be exposed as variables. (APIKIT-1242) - APIKit unable to parse and validate JSON against schema referenced using $ref at design time. (APIKIT-1225) - When validating JSON against RAML, there is no obvious way to identify the failing element. (APIKIT-1222) GitHub RAML Java parser issues fixed in this release: - Datetime with RFC3339 validates invalid examples. #470 - Get more verbose output when validation fails due to maxLength. #476 - Improve error feedback when a type is invalid. #482 - Incorrect merging of properties when extending from a type. #488 - JSON schema validation error is not precise when using a not normalized URI in a $ref. #474 - Upgrade Jackson to 2.9.5 in v2. #484 - validate() in TypeDeclaration doesn’t work as expected when validating a blank space. #485 ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.3 Release Notes **July 4, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.1.2 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - Metadata shows all object properties as optionals even though they are required. - When Repetable Streams are disabled, MultiPart consumes the payload. - RAML example snippet is converted to invalid flow. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.4 Release Notes **July 30, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.1.2 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - APIKit scaffolder is unable to generate the flows for some APIs. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.5 Release Notes **July 24, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - APIKit scaffolder is not compatible with a reduced mule-artifact.json descriptor. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.6 Release Notes **July 27, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - This version of APIKit is compatible with the Mule Maven Plugin version 3.1.6 ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.7 Release Notes **August 29, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - APIKit validations don’t display the field. - APIkit not using example from raml. - SE-8909: Content type not allowed in flow mapping for APIKit. - SE-8900: skipNullOn="everywhere" causing issues java.nio.charset.IllegalCharsetNameException on Windows - 'content-type' is not accepted as valid flow-mapping attribute. - Metadata for Attributes communicates everything as nullable. - NPE in APIKit Metadata when no RAML is specified. ## [](#enhancements-in-this-release)Enhancements in this release - Scaffolder duplicates flows if there are in a different xml where the api router lives ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.8 Release Notes **October 3, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - APIKit is not auto-generating Transforms filled with example values when importing into Studio. - `mule-apikit-module` 1.1.10 is not in the maven repository. ## [](#enhancements-in-this-release)Enhancements in this release - Use Mule Runtime resource loader to load API Specs. - Upgrade API Console Version to 4.2.1. - Use Mule Runtime resource loader to load API Specs from API Console. - Update apikit-metadata to new semantics for referencing resources. - Update Resource format for APISync resources. - Add tests to Metadata for APISync. - Define new scaffolder interface for API Sync. - Implement Scaffolder API Sync Interface. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.1.9 Release Notes **October 11, 2018** ## [](#whats-new)What’s New There are no new features in this version. There are just a few enhancements and bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.20 - Java Parser RAML 0.8 v0.8.22 - API Console 4.2.0 ## [](#fixed-in-the-release)Fixed in the Release - APIkit negatively impacting performance. - Scaffolder generates files as resource::G:A:V:file.xml and should be file.xml - Issue when scaffolding two apis in one mule app. - `mule-apikit-module` 1.1.10 is not in the maven repository. ## [](#enhancements-in-this-release)Enhancements in this release - Update scaffolder to support new semantics for referencing resources. - Remediate vulnerabilities detected by NexusIQ. - Release APIKit with APISync as Beta. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.2.0 Release Notes **January 7, 2019** This release notes briefly describe the new features released in APIkit 1.2.0. ## [](#whats-new)What’s New - APIkit is now using AMF as the default framework to parse APIs and to validate all incoming requests. AMF provides a way to achieve a unified behavior both at design time (Designer Center) and during runtime as well as OAS support. If needed, there is a way to use the previous RAML parser by specifying it in the apikit `config` tag. - API Console was upgraded to version 5, which also uses AMF to read the API. This console is displayed when AMF is used. When specifying RAML parser in the config, the old console is displayed. - Query String validation support. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.29 - Java Parser RAML 0.8 v0.8.29 - API Console 4.2.1 - API Console 5 ## [](#limitations)Limitations - When using RAML parser to parse APIs and validate requests against them, the API Console used is the 4.2.1 version. - Validations on query string over either scalar or arrays types are not performed. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Mule4-1.2.4 Release Notes **March 14, 2019** ## [](#whats-new)What’s New This release focused on bug fixes. ## [](#compatibility)Compatibility - Mule Runtime 4.1.2 and later - Anypoint Studio 7.2.0 and later - Java Parser RAML 1.0 v1.0.29 - Java Parser RAML 0.8 v0.8.29 - API Console 4.2.1 - API Console 5 ## [](#bug-fixes)Bug Fixes - Fixed issue for RAML Parser implementations returning invalid references when building an API from URI. - Fixed failing scaffolding process for APIs downloaded from Exchange when that API contained a folder, and inside such folder, any of the files contained an include referencing an exchange module without a `/` at the start. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # APIkit Release Notes These release notes are provided for APIkit: - [APIkit for AsyncAPI 1.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-asyncapi-1.2.0) - [APIkit for AsyncAPI 1.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-asyncapi-1.1.2) - [APIkit for AsyncAPI 1.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-asyncapi-1.1.1.rn) - [APIkit for AsyncAPI 1.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-asyncapi-1.1.0.rn) - [APIkit for AsyncAPI 1.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-asyncapi-1.0.0.rn) - [APIkit for GraphQL 1.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-graphql-1.2.0) - [APIkit for GraphQL 1.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-graphql-1.1.1) - [APIkit for GraphQL 1.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-graphql-1.1.0) - [APIkit for GraphQL 1.0.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-graphql-1.0.1) - [APIkit for GraphQL 1.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-graphql-1.0.0) - [APIkit for gRPC 1.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-grpc-1.0.0) - [APIkit for OData 4 1.6.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.6.2) - [APIkit for OData 4 1.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.6.1) - [APIkit for OData 4 1.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.6.0) - [APIkit for OData 4 1.5.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.5) - [APIkit for OData 4 1.5.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.4) - [APIkit for OData 4 1.5.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.3) - [APIkit for OData 4 1.5.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.2) - [APIkit for OData 4 1.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.1) - [APIkit for OData 4 1.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.0) - [APIkit for OData 4 1.4.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.4.3) - [APIkit for OData 4 1.4.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.4.2) - [APIkit for OData 4 1.4.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.4.1) - [APIkit for OData 4 1.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.4.0) - [APIkit for OData 4 1.3.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.3.4) - [APIkit for OData 4 1.3.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.3.3) - [APIkit for OData 4 1.3.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.3.2) - [APIkit for OData 4 1.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.3.1) - [APIkit for OData 4 1.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.3.0) - [APIkit for OData 4 1.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.2.0) - [APIkit for OData 4 1.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.1.0) - [APIkit for OData 4 1.0.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.0.2) - [APIkit for OData 4 1.0.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.0.1) - [APIkit for OData 4 1.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.0.0) - [APIkit for OData 2.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.4.0) - [APIkit for OData 2.3.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.5) - [APIkit for OData 2.3.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.4) - [APIkit for OData 2.3.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.3) - [APIkit for OData 2.3.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.2) - [APIkit for OData 2.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.1) - [APIkit for OData 2.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.0) - [APIkit for OData 2.2.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.2.1) - [APIkit for OData 2.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.2.0) - [APIkit for OData 2.1.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.1.5) - [APIkit for OData 2.1.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.1.4) - [APIkit for OData 2.1.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.1.3) - [APIkit for OData 2.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.1.2) - [APIkit for OData 2.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.1.1) - [APIkit for OData 2.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.1.0) - [APIkit for OData 2.0.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.9) - [APIkit for OData 2.0.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.8) - [APIkit for OData 2.0.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.7) - [APIkit for OData 2.0.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.6) - [APIkit for OData 2.0.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.5) - [APIkit for OData 2.0.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.4) - [APIkit for OData 2.0.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.3) - [APIkit for OData 2.0.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.2) - [APIkit for OData 2.0.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.0.1) - [APIkit for OData 1.0.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-1.0.9) - [APIkit for OData 1.0.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-1.0.7) - [APIkit for OData 1.0.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-1.0.6) - [APIkit for SOAP 2.1.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.7) - [APIkit for SOAP 2.1.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.6) - [APIkit for SOAP 2.1.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.5) - [APIkit for SOAP 2.1.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.4) - [APIkit for SOAP 2.1.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.3) - [APIkit for SOAP 2.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.2) - [APIkit for SOAP 2.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.1) - [APIkit for SOAP 2.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.0) - [APIkit for SOAP 2.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.0.0) - [APIkit for SOAP 1.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.7.2) - [APIkit for SOAP 1.7.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.7.1) - [APIkit for SOAP 1.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.7.0) - [APIkit for SOAP 1.6.10 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.10) - [APIkit for SOAP 1.6.9 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.9) - [APIkit for SOAP 1.6.8 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.8) - [APIkit for SOAP 1.6.7 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.7) - [APIkit for SOAP 1.6.6 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.6) - [APIkit for SOAP 1.6.5 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.5) - [APIkit for SOAP 1.6.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.4) - [APIkit for SOAP 1.6.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.3) - [APIkit for SOAP 1.6.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.2) - [APIkit for SOAP 1.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.1) - [APIkit for SOAP 1.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.0) - [APIkit for SOAP 1.5.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.5.2) - [APIkit for SOAP 1.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.5.1) - [APIkit for SOAP 1.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.5.0) - [APIkit for SOAP 1.4.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.4.1) - [APIkit for SOAP 1.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.4.0) - [APIkit for SOAP 1.3.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.3.4) - [APIkit for SOAP 1.3.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.3.3) - [APIkit for SOAP 1.3.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.3.2) - [APIkit for SOAP 1.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.3.1) - [APIkit for SOAP 1.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.3.0) - [APIkit for SOAP 1.2.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.12) - [APIkit for SOAP 1.2.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.11) - [APIkit for SOAP 1.2.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.10) - [APIkit for SOAP 1.2.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.9) - [APIkit for SOAP 1.2.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.8) - [APIkit for SOAP 1.2.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.7) - [APIkit for SOAP 1.2.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.6) - [APIkit for SOAP 1.2.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.5) - [APIkit for SOAP 1.2.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.4) - [APIkit for SOAP 1.2.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.3) - [APIkit for SOAP 1.2.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.2) - [APIkit for SOAP 1.2.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.1) - [APIkit for SOAP 1.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.2.0) - [APIkit for SOAP 1.1.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.12) - [APIkit for SOAP 1.1.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.11) - [APIkit for SOAP 1.1.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.10) - [APIkit for SOAP 1.1.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.9) - [APIkit for SOAP 1.1.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.8) - [APIkit for SOAP 1.1.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.7) - [APIkit for SOAP 1.1.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.6) - [APIkit for SOAP 1.1.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.5) - [APIkit for SOAP 1.1.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.4) - [APIkit for SOAP 1.1.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.3) - [APIkit for SOAP 1.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.2) - [APIkit for SOAP 1.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.1) - [APIkit for SOAP 1.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.1.0) - [APIkit for SOAP 1.0.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.0.8) - [APIkit for SOAP 1.0.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.0.7) - [APIkit for SOAP 1.0.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.0.5) - [APIkit for SOAP 1.0.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.0.4) - [APIkit for SOAP 1.0.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.0.3) - [APIkit for SOAP 1.0.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.0.2) - [APIkit for SOAP 1.0.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.0.1) - [APIkit Mule 4 1.13.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.13.3-release-notes) - [APIkit Mule 4 1.13.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.13.2-release-notes) - [APIkit Mule 4 1.13.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.13.1-release-notes) - [APIkit Mule 4 1.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.13.0-release-notes) - [APIkit Mule 4 1.12.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.10-release-notes) - [APIkit Mule 4 1.12.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.9-release-notes) - [APIkit Mule 4 1.12.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.8-release-notes) - [APIkit Mule 4 1.12.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.7-release-notes) - [APIkit Mule 4 1.12.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.6-release-notes) - [APIkit Mule 4 1.12.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.5-release-notes) - [APIkit Mule 4 1.12.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.4-release-notes) - [APIkit Mule 4 1.12.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.3-release-notes) - [APIkit Mule 4 1.12.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.2-release-notes) - [APIkit Mule 4 1.12.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.1-release-notes) - [APIkit Mule 4 1.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.0-release-notes) - [APIkit Mule 4 1.11.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.18-release-notes) - [APIkit Mule 4 1.11.17 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.17-release-notes) - [APIkit Mule 4 1.11.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.16-release-notes) - [APIkit Mule 4 1.11.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.15-release-notes) - [APIkit Mule 4 1.11.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.14-release-notes) - [APIkit Mule 4 1.11.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.13-release-notes) - [APIkit Mule 4 1.11.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.12-release-notes) - [APIkit Mule 4 1.11.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.11-release-notes) - [APIkit Mule 4 1.11.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.10-release-notes) - [APIkit Mule 4 1.11.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.9-release-notes) - [APIkit Mule 4 1.11.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.8-release-notes) - [APIkit Mule 4 1.11.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.7-release-notes) - [APIkit Mule 4 1.11.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.6-release-notes) - [APIkit Mule 4 1.11.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.5-release-notes) - [APIkit Mule 4 1.11.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.4-release-notes) - [APIkit Mule 4 1.11.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.3-release-notes) - [APIkit Mule 4 1.11.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.2-release-notes) - [APIkit Mule 4 1.11.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.1-release-notes) - [APIkit Mule 4 1.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.0-release-notes) - [APIkit Mule 4 1.10.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.10.4-release-notes) - [APIkit Mule 4 1.10.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.10.3-release-notes) - [APIkit Mule 4 1.10.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.10.2-release-notes) - [APIkit Mule 4 1.10.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.10.1-release-notes) - [APIkit Mule 4 1.10.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.10.0-release-notes) - [APIkit Mule 4 1.9.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.9.2-release-notes) - [APIkit Mule 4 1.9.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.9.1-release-notes) - [APIkit Mule 4 1.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.9.0-release-notes) - [APIkit Mule 4 1.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.8.4-release-notes) - [APIkit Mule 4 1.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.8.3-release-notes) - [APIkit Mule 4 1.8.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.8.2-release-notes) - [APIkit Mule 4 1.8.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.8.1-release-notes) - [APIkit Mule 4 1.8.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.8.0-release-notes) - [APIkit Mule 4 1.7.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.7.3-release-notes) - [APIkit Mule 4 1.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.7.2-release-notes) - [APIkit Mule 4 1.7.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.7.1-release-notes) - [APIkit Mule 4 1.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.7.0-release-notes) - [APIkit Mule 4 1.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.6.1-release-notes) - [APIkit Mule 4 1.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.6.0-release-notes) - [APIkit Mule 4 1.5.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.12-release-notes) - [APIkit Mule 4 1.5.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.11-release-notes) - [APIkit Mule 4 1.5.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.10-release-notes) - [APIkit Mule 4 1.5.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.9-release-notes) - [APIkit Mule 4 1.5.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.8-release-notes) - [APIkit Mule 4 1.5.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.7-release-notes) - [APIkit Mule 4 1.5.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.6-release-notes) - [APIkit Mule 4 1.5.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.5-release-notes) - [APIkit Mule 4 1.5.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.4-release-notes) - [APIkit Mule 4 1.5.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.3-release-notes) - [APIkit Mule 4 1.5.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.2-release-notes) - [APIkit Mule 4 1.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.1-release-notes) - [APIkit Mule 4 1.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5.0-release-notes) - [APIkit Mule 4 1.4.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.4.2-release-notes) - [APIkit Mule 4 1.4.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.4.1-release-notes) - [APIkit Mule 4 1.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.4.0-release-notes) - [APIkit Mule 4 1.3.19 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.19-release-notes) - [APIkit Mule 4 1.3.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.18-release-notes) - [APIkit Mule 4 1.3.17 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.17-release-notes) - [APIkit Mule 4 1.3.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.16-release-notes) - [APIkit Mule 4 1.3.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.15-release-notes) - [APIkit Mule 4 1.3.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.14-release-notes) - [APIkit Mule 4 1.3.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.13-release-notes) - [APIkit Mule 4 1.3.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.12-release-notes) - [APIkit Mule 4 1.3.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.11-release-notes) - [APIkit Mule 4 1.3.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.10-release-notes) - [APIkit Mule 4 1.3.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.9-release-notes) - [APIkit Mule 4 1.3.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.8-release-notes) - [APIkit Mule 4 1.3.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.7-release-notes) - [APIkit Mule 4 1.3.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.6-release-notes) - [APIkit Mule 4 1.3.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.5-release-notes) - [APIkit Mule 4 1.3.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.4-release-notes) - [APIkit Mule 4 1.3.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.3-release-notes) - [APIkit Mule 4 1.3.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.2-release-notes) - [APIkit Mule 4 1.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.1-release-notes) - [APIkit Mule 4 1.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3.0-release-notes) - [APIkit Mule 4 1.2.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.2.5-release-notes) - [APIkit Mule 4 1.2.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.2.4-release-notes) - [APIkit Mule 4 1.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.20-release-notes) - [APIkit Mule 4 1.1.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.16-release-notes) - [APIkit Mule 4 1.1.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.15-release-notes) - [APIkit Mule 4 1.1.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.14-release-notes) - [APIkit Mule 4 1.1.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.13-release-notes) - [APIkit Mule 4 1.1.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12-release-notes) - [APIkit Mule 4 1.1.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11-release-notes) - [APIkit Mule 4 1.1.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.10-release-notes) - [APIkit Mule 4 1.1.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.9-release-notes) - [APIkit Mule 4 1.1.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.8-release-notes) - [APIkit Mule 4 1.1.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.7-release-notes) - [APIkit Mule 4 1.1.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.6-release-notes) - [APIkit Mule 4 1.1.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.5-release-notes) - [APIkit Mule 4 1.1.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.4-release-notes) - [APIkit Mule 4 1.1.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.3-release-notes) - [APIkit Mule 4 1.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.2-release-notes) - [APIkit Mule 4 1.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.1-release-notes) - [APIkit Mule 4 1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1-release-notes) - [APIkit 4.0.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.0.1-release-notes) - [APIkit 4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.0-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # AS2 Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the internet. Security is achieved by using digital certificates and encryption. Mule runtime engine (Mule) supports the AS2 protocol through the Anypoint Connector for AS2 (AS2 Connector). AS2 Connector enables trading partners to transmit and receive AS2 messages with EDI-X12, EDIFACT, XML, or binary payloads. Guide: [AS2 Connector User Guide](https://docs.mulesoft.com/as2-connector/latest/) ## [](#7-0-0)7.0.0 **March 4, 2026** ### What’s New - AS2 Connector now supports multiple security modes via a new global connector configuration. This configuration also supports selecting the appropriate external library based on your security mode. For more information about the supported security modes, see [Upgrading and Migrating AS2 Connector to Version 7.x](https://docs.mulesoft.com/as2-connector/latest/as2-connector-upgrade-migrate). These external libraries are supported for each security mode:
Security Mode Global Configuration Default Name Required Library Maven Coordinates

non-FIPS

AS2 Connector External Libs - Non FIPS

AS2_Connector_External_Libs___Non_FIPS

com.mulesoft.connectors:as2-bc-non-fips-impl:3.0.0, org.bouncycastle:bcpkix-jdk18on:1.82, org.bouncycastle:bcprov-jdk18on:1.82

FIPS 140-2

AS2 Connector External Libs - FIPS 140-2

AS2_Connector_External_Libs___FIPS_140_2

com.mulesoft.connectors:as2-bc1-fips-impl:3.0.0

FIPS 140-3

AS2 Connector External Libs - FIPS 140-3

AS2_Connector_External_Libs___FIPS_140_3

com.mulesoft.connectors:as2-bc2-fips-impl:3.0.0
Standard BouncyCastle (BC) security provider support continues for non-FIPS security modes.
- AS2 Connector is now FIPS 140-3 compliant, which includes: - Automatic FIPS mode detection via the `mule.security.model` system property - BouncyCastle FIPS (BCFIPS) security provider registration with safety controls - Prevention of unauthorized JVM security configuration modifications in FIPS mode - Restricted use of encryption and signature algorithms based on compliance needs
AS2 Connector still supports FIPS 140-2 compliance.
- AS2 Connector now provides enhanced security with modern TLS 1.3 protocol support. For AS2 Connector configuration instructions, see [Using Anypoint Studio to Configure AS2 Connector 7.0](https://docs.mulesoft.com/as2-connector/latest/as2-connector-studio). To upgrade from version 6.x to 7.x, see [Upgrading and Migrating AS2 Connector to Version 7.x](https://docs.mulesoft.com/as2-connector/latest/as2-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
## [](#6-9-3)6.9.3 **June 3, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector can now parse MDN signatures that include binary content, even if the MIME header for encoding is missing.

W-18573937
## [](#6-9-2)6.9.2 **May 14, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector can now parse MDN signatures with binary content.

W-18140838
## [](#6-9-1)6.9.1 **March 20, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

An IllegalAccessexception error no longer occurs when using Java 17.

W-17844886

Exceptions are no longer thrown when reading content with PKCS7 signatures in Binary format.

W-17282909
## [](#6-9-0)6.9.0 **November 17, 2024** ### What’s New - The connector now supports MDNs with signatures encoded in Base64, even when a line exceeds 76 characters. Per RFC 2045, use 76 characters or fewer per line when formatting Base64-encoded output streams. For more information, see [Upgrading and Migrating AS2 Connector to Version 6.x](https://docs.mulesoft.com/as2-connector/latest/as2-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#6-8-1)6.8.1 **November 15, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

MDNs received without CRLF characters at the end of the MIME part are now supported. Per RFC 4130, CRLF characters must be present.

W-16679147

MDNs with line endings that consist of only LF or CR characters are now supported. Per RFC 4130, both CR and LF characters must be present.

W-17102178
## [](#6-8-0)6.8.0 **October 21, 2024** ### What’s New - The connector now has more validations on the keystore and algorithm usage to address reported security vulnerabilities. For more information, see [AS2 Connector Reference](https://docs.mulesoft.com/as2-connector/latest/as2-connector-reference). ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#6-7-1)6.7.1 **March 26, 2024** ### What’s New The following libraries are upgraded to address reported security vulnerabilities: - The bcprov-jdk18on library is upgraded to version 1.77. - The bcpkix-jdk18on library is upgraded to version 1.77. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now returns the correct MDN error when the payload is encoded using Base64, as defined in RFC 4648.

W-15099775
## [](#6-7-0)6.7.0 **February 5, 2024** ### What’s New - This connector is now compatible with Java 17. - You can now configure the **AS2 Listener** to use a different keystore entry for the MDN signature than the one used for decryption. To use this feature, select **Use different Alias for MDN Signature** and complete the **Alias For MDN Signature** and **Private Key Password** fields. For more information, see the [Listener Config section](https://docs.mulesoft.com/as2-connector/latest/as2-connector-reference#ListenerConfig) in the AS2 Connector Reference. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11 and 17
### Fixed Issues
Issue Resolution ID

The cryptographic operations now comply with the FIPS 140-2 requirements.

W-14243186

Adjusted the logs to remove sensitive date.

W-14931729
## [](#6-6-0)6.6.0 **June 22, 2023** ### What’s New - You can now configure the **Send with Sync Mdn** operation to use a different certificate for MDN signature validation than the one used for encryption. To use this feature, select **Use different Alias for MDN Signature Validation** and complete the **x509 Alias For MDN Signature** field. For more information, see the [Send Config section](https://docs.mulesoft.com/as2-connector/latest/as2-connector-reference#send-config) in the AS2 Connector Reference. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### Fixed Issues
Issue Resolution ID

The AS2 Listener source now supports AS2-to and AS2-from header values that have double quotes, in accordance with RFC-4130.

W-12975888

The algorithm value used on headers now complies with RFC-8551.

W-13055720

The Send With Asnc Mdn and Send With Sync Mdn operations no longer generate message IDs with colons or extra double quotes, in accordance with RFC-2822.

W-13079117
## [](#6-5-0)6.5.0 **March 14, 2023** ### What’s New - You can now configure the **As2 listener** source so that it rejects new, incoming messages that have the same sender, receiver, and message ID as messages that have been processed already. To use this feature, select the **Check for duplicate messages** field and reference a global object store in the **Object Store** field. For more information, see the [AS2 Connector Reference](https://docs.mulesoft.com/as2-connector/latest/as2-connector-reference). ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
## [](#6-4-1)6.4.1 **December 7, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### Fixed Issues
Issue Resolution ID

The send operations no longer generate a thread leak in the Threshold or Identity transfer modes when the connector is configured with static expression values.

W-11723371

The send operations no longer generate a thread leak in dynamic configuration situations.

W-11796931

Payloads can now be encrypted with the AES256_WRAP algorithm, regardless of their length.

W-11888057
## [](#6-4-0)6.4.0 **November 14, 2022** ### What’s New - You can now configure the **As 2 listener** source to send the MDN at the end of the flow by using the **Mdn mode** option `AUTO`. - You can now configure retries to ensure the delivery of the MDN by using the **Retry interval** and **Retry count** fields in the **Async MDN Connection Provider** global configuration. - A new field named **Validate certificate expiration date** enables you to enable or disable the certificate expiration date validation. - The console logs a warning message when a certificate approaches its expiration date or if it already expired. You can configure when to get the warning by using the new **Warning before (days)** in the **KeyStore Config** field. For more information, see the [AS2 Connector Reference](https://docs.mulesoft.com/as2-connector/latest/as2-connector-reference). ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### Fixed Issues
Issue Resolution ID

The As 2 listener now sends back the MDN if there are errors.

W-11303187

The As 2 mdn listener won’t throw an exception when receiving an MDN without the Received-Content-Mic field.

W-11633079

When an error occurs in the As 2 listener, the execution of the flow now stops.

W-11633272

If an error occurs when setting the Request a Receipt field to SIGNED_REQUIRED from the Send configuration, the received MDN is now handled correctly.

W-11633356

The connector now cleans the temporal files created when the resource threshold is reached.

W-11715911

The As 2 listener now sends back the HTTP response when an async and unsigned MDN is requested.

W-11837866
## [](#6-3-2)6.3.2 **August 17, 2022** ### What’s New The following libraries are upgraded to address reported security vulnerabilities: - The bcprov-jdk15on is upgraded to version 1.69. - The bcpkix-jdk15on library is upgraded to version 1.69. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8

AS2

1.0, 1.1, and 1.2
### Fixed Issues
Issue ID

The shared listener mode option now supports using expressions to configure partners.

W-11507857
## [](#6-3-1)6.3.1 **June 27, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8

AS2

1.0, 1.1, and 1.2
### Fixed Issues
Issue ID

The As 2 listener and As 2 mdn listener sources now process signed and encrypted content correctly when the MIME header boundary entry contains colon characters.

W-11277855

An error is now thrown by the connector when the hostname resolution fails.

W-11278644
## [](#6-3-0)6.3.0 **June 06, 2022** ### What’s New - You can now configure a single AS2 listener endpoint to receive messages from multiple partners by using the **Shared listener mode** option. - You can now pass custom headers on outbound AS2 messages when using the **Send with Sync MDN** and **Send with Async MDN** operations. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### Fixed Issues
Issue ID

Log entry levels no longer print informational log messages.

W-11099643

The performance of the MDN listener under a high load is now improved.

W-11142320

AS2 Send operations now correctly handle an unknown-trading-partner error in the message disposition notification (MDN) returned from the receiver.

W-10580735
### Known Issues
Known Issue Workaround ID

Using expressions to configure partners when using Shared listener mode does not currently work.
## [](#6-2-4)6.2.4 **January 24, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8

AS2

1.0, 1.1, and 1.2
### Fixed Issues
Issue ID

Added and improved log messages.

CONN-9128

A NullPointerException error no longer occurs when a server sends a Message Disposition Notification (MDN) that uses lower-case text.

SE-23926
## [](#6-2-3)6.2.3 **November 17, 2021** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### Fixed Issues
Issue ID

Outbound encrypted messages contained extra name and smime-type parameters in the Content-Type header. Because extra parameters are no longer supported by the current AS2 RFC, some servers did not process the messages.

CONN-9285

The connector did not accept the smime-type and disposition-notification-options parameters in the Content-Type header with quotes. You can now specify these values with or without quotes.

SE-23387
## [](#6-2-2)6.2.2 **November 1, 2021** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### Fixed Issues
Issue ID

The Received-Content-MIC header was not parsed when the space character after a comma was suppressed.

SE-23058

The None option was removed from the General - Transfer Mode Configuration field because it behaved like the default option (Chunked transfer mode).

CONN-9143
## [](#6-2-1)6.2.1 **October 22, 2021** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities.

CONN-9115
## [](#6-2-0)6.2.0 **September 24, 2021** ### What’s New - The new **Custom Message ID** property enables you to specify a custom message ID for AS2 send operations. - The new **Propagate Content Transfer Encoding** property indicates whether to propagate the content transfer encoding on the AS2 message sent to the partner. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
## [](#6-1-4)6.1.4 **August 11, 2021** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### [](#fixed-issue)Fixed Issue AS2 send attributes with auto-generated message IDs are now available after running the **Send with Async MDN** operation. (CONN-8603) ## [](#6-1-3)6.1.3 **August 10, 2021** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### [](#fixed-issue-2)Fixed Issue The **Send** operation failed with a digest calculation error when using a signed and encrypted message. (SE-21764) ## [](#6-1-2)6.1.2 **March 30, 2021** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### [](#fixed-issue-3)Fixed Issue Changed the parser to fix the issue with splitting boundary headers. (SE-20159) ## [](#6-1-1)6.1.1 **November 12, 2020** ### [](#compatibility-25)Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### [](#fixed-issue-4)Fixed Issue Added `ReportingUA` (disposition notification content) to fix the issue with Synchronous MDN not working. (SE-18454) ## [](#6-1-0)6.1.0 **October 30, 2020** ### [](#compatibility-26)Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### [](#new-features)New Features - Added a new configuration to optionally enable or disable chunked data transfer in the **Send** operation. - Changed the `reporting-UA` parameter to an optional parameter in the MDN listener. ## [](#6-0-2)6.0.2 **October 15, 2020** ### [](#compatibility-27)Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8
### [](#fixed-issues-17)Fixed Issues - AS2 Listener did not clear incoming payloads, which caused the `/tmp` directory to become full and a 'java.io.IOException: No space left on device' error. (SE-17914) - The issue that caused a memory leak with Bouncy Castle `javax.crypto.JceSecurity` in applications with an AS2 Receiver is fixed. (SE-17950) ## [](#6-0-1)6.0.1 July 30, 2020 ### [](#compatibility-28)Compatibility
Software Version

Mule

4.3.0 and later

Java

8
### [](#fixed-issue-5)Fixed Issue - The `Subject` parameter was not being applied to outgoing AS2 messages. ## [](#6-0-0)6.0.0 July 16, 2020 ### [](#compatibility-29)Compatibility
Software Version

Mule

4.3.0 and later

Java

8
### [](#new-features-2)New Features - Non-repudiation of a signed message is now implemented for all operations and sources in AS2 Connector. - AS2 Send with Sync MDN operation now outputs the MDN payload to the user flow instead of the original payload. - AS2 Send with Async MDN operation now outputs nothing (void) to the user flow instead of the original payload. - AS2 Connector IO performance is improved on CloudHub, as the Send operations no longer retain the original payload. - Mule 4.3.0 enables a more efficient way of dispatching reusable streams to the Mule flow by using `ImmutableRepeatableFileInputStream`. - Added support for dynamically passing a Partner URL in AS2 Send operations. - The `securityLevel` configuration parameter sets the Security level requirement on the AS2 Listener to accept only signed, encrypted, or signed-and-encrypted based on your organization’s security guidelines. ### [](#fixed-issue-6)Fixed Issue The deprecated BasicAuthentication field has been removed from the `BaseConnection` class. ## [](#5-1-4)5.1.4 **November 2, 2020** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.2.2 and later

OpenJDK

8
### [](#fixed-issues-18)Fixed Issues - The issue that caused a memory leak with Bouncy Castle `javax.crypto.JceSecurity` in applications with an AS2 Receiver is fixed. (CONN-7171) ## [](#5-1-3)5.1.3 July 30, 2020 ### [](#compatibility-31)Compatibility
Software Version

Mule

4.2.2 and later

Java

8
### [](#fixed-issue-7)Fixed Issue The `Subject` parameter was not being applied to outgoing AS2 messages. ### [](#known-issues-2)Known Issues Signed copies of the document for non-repudiation are not saved. ## [](#5-1-2)5.1.2 July 14, 2020 ### [](#compatibility-32)Compatibility
Software Version

Mule

4.2.2 and later

Java

8
### [](#fixed-issue-8)Fixed Issue - Fixed security vulnerability issues (CONN-6397). ### [](#known-issues-3)Known Issues - Signed copies of the document for non-repudiation are not saved. ## [](#5-1-1)5.1.1 April 20, 2020 ### [](#compatibility-33)Compatibility
Software Version

Mule

4.2.2 and later

Java

8
### [](#fixed-issue-9)Fixed Issue - Validation of the as2-to and as2-from headers did not produce the expected error response (CONN-5653). ### [](#known-issues-4)Known Issues - Signed copies of the document for non-repudiation are not saved. ## [](#5-1-0)5.1.0 March 10, 2020 ### [](#compatibility-34)Compatibility
Software Version

Mule

4.2.2 and later

Java

8
### [](#new-features-3)New Features - Basic Authentication is now available for both send operations and on a receiving source. ### [](#fixed-issue-10)Fixed Issue - Support using the MIME type set on the input message for AS2 send data (CONN-4668)(SE-13003). ### [](#known-issues-5)Known Issues - Signed copies of the document for non-repudiation are not saved. ## [](#5-0-1)5.0.1 February 7, 2020 ### [](#compatibility-35)Compatibility
Software Version

Mule

4.2.2 and later

Java

8
### [](#fixed-issue-11)Fixed Issue - Fixed the issue where an MDN was not requested or sent, which resulted in an NPE with the payload not being passed to the Mule flow. (SE-14740) ### [](#known-issues-6)Known Issues - Signed copies of the document for non-repudiation are not saved. - Authentication over HTTP is currently not supported. ## [](#5-0-0)5.0.0 December 2019 ### [](#compatibility-36)Compatibility
Software Version

Mule

4.2.2 and later

Java

8
### [](#new-features-4)New Features - All operations support message payloads as a stream. - Experience using Anypoint Studio to configure Mule 4 application flows using HTTP endpoint configuration is improved, and new error types that improve error handling are available. - An explicit asynchronous MDN source enables you to process asynchronous MDN in the application. - CloudHub configuration is improved. - Information from the AS2 Send and Listener operation output attributes is more detailed. - Additional encryption/signing algorithms are now supported. ### [](#known-issues-7)Known Issues - Signed copies of the document for non-repudiation are not saved. - Authentication over HTTP is currently not supported. ## [](#4-1-6)4.1.6 August 26, 2020 ### [](#compatibility-37)Compatibility
Software Version

Mule

4.2.2 and later

Java

8
### [](#fixed-issue-12)Fixed Issue Fixed the issue that caused the Content Transfer Encoding `quoted-printable` error. (CONN-5908) ## [](#4-1-5)4.1.5 April 20, 2020 ### [](#compatibility-38)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#libraries-version-update)Libraries version update
Library Previous Version Current Version

bcprov-jdk15on

1.59

1.62

bcpkix-jdk15on

1.59

1.62

bcmail-jdk15on

1.59

1.62

dom4j

2.0.0

2.1.1

h2

1.4.197

1.4.199
## [](#4-1-4)4.1.4 March 10, 2020 ### [](#compatibility-39)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issue-13)Fixed Issue Added message IDs to the names of other files used for temporary storage, to avoid file name conflicts between messages. This is an addition to the changes made in 4.1.3. (SE-15153) ## [](#4-1-3)4.1.3 March 4, 2020 ### [](#compatibility-40)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issue-14)Fixed Issue Added message IDs to the names of files used for storing messages so multiple messages do not use the same name. (SE-15153). ## [](#4-1-2)4.1.2 January 6, 2020 ### [](#compatibility-41)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issue-15)Fixed Issue - Fixed startup error due to a slash (/) in the windows path. (SE-14173) ## [](#4-1-1)4.1.1 December 3, 2019 ### [](#compatibility-42)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-19)Fixed Issues - The `java.nio.file.Files.copy()` file is now used instead of the Apache Commons IO library for a file copy, fixing the "Error storing transaction" error caused by "java.io.IOException: Failed to copy full contents". (SE-14144) ## [](#4-1-0)4.1.0 October 17, 2019 ### [](#compatibility-43)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-20)Fixed Issues - The mime type is now a configurable value in the partnership configuration for outgoing messages. This enables users to set the content type of the sending document. (SE-13317) ## [](#4-0-8)4.0.8 October 15, 2019 ### [](#compatibility-44)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-21)Fixed Issues - Resolved a directory polling issue if the config folder is missing during runtime(SE-11935). ## [](#4-0-7)4.0.7 **July 17, 2019** ### [](#compatibility-45)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-22)Fixed Issues - Corrected NullPointerException thrown during HTTP response generation for error conditions (SE-11935). ## [](#4-0-6)4.0.6 **June 11, 2019** ### [](#compatibility-46)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-23)Fixed Issues - The AS2 Connector did not refer an SSL certificate from the keyStorePath specified in the Secure Receiver Module ports. ## [](#4-0-5)4.0.5 **May 29, 2019** ### [](#compatibility-47)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-24)Fixed Issues - Certain receive requests failed because the App was trying to process deleted files. ## [](#4-0-4)4.0.4 **May 16, 2019** ### [](#compatibility-48)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-25)Fixed Issues - Some send and receive requests failed because the app was starting to process files before they were completely transferred. - Releasing threads and file operations from the Send process increased the size of the thread pool and caused many operations to fail. - The send and receive operations were not supported together in the same instance. ## [](#4-0-3)4.0.3 **April 26, 2019** ### [](#compatibility-49)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-26)Fixed Issues - The connector always sent the content signed with SHA256. ## [](#4-0-2)4.0.2 **March 28, 2019** ### [](#compatibility-50)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#fixed-issues-27)Fixed Issues - The connector did not accept JKS and JCEKS keystores. - The encryption and signing algorithm lists in the configuration are now tho separate ones. Previously, you were able to select a signing algorithm for encrypting and vice-versa, which would not work. - The connector is now able to receive both signed and unsigned MDNs. ## [](#4-0-1)4.0.1 **February 20, 2019** ### [](#compatibility-51)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#features)Features - Added Receiver Host configuration, which must be set to "0.0.0.0" for operating on CloudHub. ### [](#fixed-issues-28)Fixed Issues - The connector would not accept incoming messages when run on CloudHub. - Using signing throws ClassCastException. ## [](#4-0-0)4.0.0 **November 12, 2018** ### [](#compatibility-52)Compatibility
Software Version

Mule

4.1.0 and later

Java

8
### [](#features-2)Features - Send - Allows you to send AS2 messages via HTTP or HTTPS. - Receive - Enables a Mule application to receive messages following the AS2 protocol. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Asana Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Asana gives you access to the Asana platform. This connector exposes operations provided by the Asana API. See the [https://developers.asana.com/reference/getattachment](https://developers.asana.com/reference/getattachment) to learn more. Guide: [Asana Connector User Guide](https://docs.mulesoft.com/jp/asana-connector/latest/) ## [](#1-0-10)1.0.10 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-9)1.0.9 **August 20, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Jackson library is upgraded to version 2.22.2.

  • The commons-io library is upgraded to version 2.22.0.

W-23441651
## [](#1-0-8)1.0.8 **May 9, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-7)1.0.7 **October 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853415
## [](#1-0-6)1.0.6 **April 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920491
## [](#1-0-5)1.0.5 **January 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9839
## [](#1-0-4)1.0.4 **December 22, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9681
## [](#1-0-3)1.0.3 **December 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CSCA-1200

Upgraded library dependencies.

CONN-9557
## [](#1-0-2)1.0.2 **June 16, 2021** ### [](#compatibility-9)Compatibility Asana Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-7)Fixed Issues Optimized the connector to improve its overall stability and performance. ## [](#1-0-1)1.0.1 **June 2, 2021** ### [](#compatibility-10)Compatibility Asana Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-8)Fixed Issues Optimized the connector to improve its overall stability and performance. ## [](#1-0-0)1.0.0 **March 4, 2021** New connector ### [](#compatibility-11)Compatibility Asana Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features For a list of supported configurations and operations, see the Asana Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # AsyncAPI Support to Implement Event-Driven Architecture Implement event-driven architecture (EDA) as part of your API-led strategy using the AsyncAPI support in Anypoint Platform. AsyncAPI is an open-source, industry-standard language that describes messaging interfaces. Anypoint Platform supports AsyncAPI in these products:
API-Led Journey Stage Product Versions Supported Learn More

Design Specs

Anypoint Design Center

2.0, 2.6

Design your AsyncAPI specs in API Designer or import them from Exchange.

Anypoint Code Builder

2.6

Design your AsyncAPI specs in Anypoint Code Builder or import them from Design Center.

Govern Specs

Anypoint API Governance

2.0, 2.6

Validate your AsyncAPI specs against governance rulesets during the design phase to ensure your APIs conform to your organization’s standards. After you publish the specs to Exchange, centrally govern them using API Governance.

Anypoint Code Builder

2.6

Validate your AsyncAPI specs against governance rulesets in Anypoint Code Builder. Doing so during the design phase ensures your APIs conform to your organization’s standards.

Publish Specs

Anypoint Exchange

2.0, 2.6

Publish your AsyncAPI specs to Exchange to share and promote collaboration within your organization of developers. You can publish specs from API Designer or publish them directly to Exchange.

Configure Non-managed Instances

Anypoint Exchange

2.0, 2.6

Although you can’t yet manage your AsyncAPI instances in Anypoint Platform, you can configure non-managed instances for your AsyncAPI asset in Exchange.

View Specs

Anypoint API Community Manager

2.0, 2.6

Discover and view AsyncAPI specs that are in your API Community Manager site.

Anypoint API Experience Hub

2.0, 2.6

Discover and view AsyncAPI specs that are in your API Experience Hub API portal.

Implement APIs

Anypoint Code Builder

2.0, 2.6

Scaffold and implement AsyncAPI specs in a Mule project using Anypoint Code Builder. Message brokers currently supported for implementations are Anypoint MQ, Kafka, Salesforce platform events, and Solace PubSub+. The minimum Mule runtime engine requirement for this feature is Mule 4.6.

Anypoint Studio

2.6

Scaffold and implement AsyncAPI specs in a Mule project using Anypoint Studio. Message brokers currently supported for implementations are Anypoint MQ, Kafka, Salesforce platform events, and Solace PubSub+. The minimum Mule runtime engine requirement for this feature is Mule 4.6.
## [](#october-8-2024)October 8, 2024 - Anypoint Platform supports AsyncAPI 2.6 in the following products: - Anypoint Code Builder for designing API specs and Avro schemas - Anypoint Code Builder for implementing APIs - Anypoint Studio for implementing APIs - Design Center for designing API specs - API Community Manager for viewing API specs with Avro schemas - API Governance for governing API specs - Exchange for publishing API specs with Avro schemas ## [](#july-24-2024)July 24, 2024 - API Experience Hub supports AsyncAPI 2.6. ## [](#june-24-2024)June 24, 2024 - Anypoint Platform supports AsyncAPI 2.6 in the following products: - Anypoint Code Builder (open beta support) for implementing APIs - Anypoint Studio (open beta support) for implementing APIs - Design Center for designing API specs - API Community Manager for viewing specs - API Governance for governing API specs - Exchange for publishing API specs and adding non-managed API instances ## [](#june-13-2023)June 13, 2023 - API Experience Hub supports AsyncAPI 2.0. ## [](#july-9-2022)July 9, 2022 - Anypoint API Governance supports AsyncAPI 2.0. ## [](#october-14-2021)October 14, 2021 - Anypoint Platform supports AsyncAPI 2.0 in the following products: - Design Center for designing API specs - Exchange for publishing and adding non-managed instances - API Community Manager for viewing specs ## [](#see-also)See Also - [AsyncAPI doc on www.asyncapi.com](https://www.asyncapi.com/docs/tutorials/getting-started) - [Anypoint Code Builder Release Notes](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes) - [Anypoint Studio Release Notes](https://docs.mulesoft.com/jp/release-notes/studio/anypoint-studio) - [API Designer (Crowd) Release Notes](https://docs.mulesoft.com/jp/release-notes/design-center/design-center-release-notes-api_specs) - [Anypoint Exchange Release Notes](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes) - [Anypoint API Community Manager Release Notes](https://docs.mulesoft.com/jp/release-notes/api-community-manager/api-community-manager-release-notes) - [Anypoint API Experience Hub Release Notes](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes) - [Known Issues](https://help.salesforce.com/s/issues) # AWS Lambda The AWS Lambda policy triggers an AWS Lambda function from a standard HTTP request. For configuration details, see [AWS Lambda Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-aws-lambda). ## [](#february-24-2025)February 24, 2025 ### What’s New - AWS Lambda policy implementation version 1.0.0 is now supported by Omni Gateway. - AWS Lambda policy definition version 1.0.0 is now supported by Omni Gateway. # AWS Request Signature The AWS Request Signature policy signs outgoing requests with AWS Signature Version 4 (SigV4) or Signature Version 4A (SigV4A). For configuration details, see [AWS Request Signature Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-aws-signature). ## [](#may-19-2025)May 19, 2025 ### What’s New - AWS Request Signature policy implementation version 1.0.0 is now supported by Omni Gateway. - AWS Request Signature policy definition version 1.0.0 is now supported by Omni Gateway. # Azure Content Safety Policy The Azure Content Safety Policy policy evaluates LLM prompts and responses against Azure AI Content Safety for harmful content, jailbreak attempts, hallucinations, and copyrighted material. For configuration details, see [Azure Content Safety Policy](https://docs.mulesoft.com/gateway/latest/policies-included-azure-content-safety). ## [](#may-15-2026)May 15, 2026 ### What’s New - Azure Content Safety Policy policy implementation version 1.0.0 is now supported by Omni Gateway. - Azure Content Safety Policy policy definition version 1.0.0 is now supported by Omni Gateway. # Azure Cosmos DB Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Azure Cosmos DB (Azure Cosmos DB Connector) enables you to use basic Azure Cosmos DB operations to create and access objects in the Azure Cosmos DB system. Guide: [Azure Cosmos DB Connector User Guide](https://docs.mulesoft.com/azure-cosmos-db-connector/latest/) ## [](#1-1-1)1.1.1 **October 1, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The msal4j library is upgraded to version 1.26.0 to address reported security vulnerabilities.

W-3300013
## [](#1-1-0)1.1.0 **August 31, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - Azure Cosmos DB Connector now supports [Service Principal authentication](https://docs.mulesoft.com/azure-cosmos-db-connector/latest/azure-cosmos-db-connector-reference#ServicePrincipalConfig) using a Microsoft Entra ID service principal. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The log4j library is upgraded to version 2.26.1.

  • The commons-io library is upgraded to version 2.22.0.

  • The msal4j library is added at version 1.25.1.

W-23858189
## [](#1-0-6)1.0.6 **April 19, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
Issue Resolution ID

The Query Documents operation now works correctly when running on Mule runtime 4.11.0 and no longer throws the 400 Bad Request error.

W-21933035
## [](#1-0-5)1.0.5 **April 3, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
Issue Resolution ID

The log4j-core and the log4j-slf4j-impl libraries are upgraded to 2.24.3.

W-18172123
## [](#1-0-4)1.0.4 **July 4, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-3)1.0.3 **June 30, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Pagination issues no longer occur across multiple partitions for collections.

W-11335940
## [](#1-0-2)1.0.2 **May 10, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The Key Token Auth Connection Provider now contains a Test Connection button.

W-11108523
## [](#1-0-1)1.0.1 **January 17, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9984
## [](#1-0-0)1.0.0 **December 13, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Azure Cosmos DB Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Azure Data Lake Storage Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Azure Data Lake Storage Gen 2 (Azure Data Lake Storage Connector) provides access to standard Azure Data Lake Storage Gen 2 operations using Anypoint Platform. Guide: [Azure Data Lake Storage Connector User Guide](https://docs.mulesoft.com/jp/azure-data-lake-storage-connector/latest/) ## [](#1-0-11)1.0.11 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-10)1.0.10 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The azure-storage-common library is upgraded to version 12.34.0.

  • The jackson-bom library is upgraded to version 2.22.1.

W-23441613
## [](#1-0-9)1.0.9 **June 17, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The azure-storage-common library is upgraded to version 12.33.0.

  • The jackson-bom library is upgraded to version 2.22.0.

W-22940826
## [](#1-0-8)1.0.8 **December 21, 2025** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address the CVE-2025-48924 security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The azure-storage-common library is upgraded to version 12.31.0.

W-20620713
## [](#1-0-7)1.0.7 **June 12, 2025** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Position field in the Update Path operation is now optional and has a default value of 0.

W-18704735
## [](#1-0-6)1.0.6 **March 31, 2025** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-18060809
## [](#1-0-5)1.0.5 **June 25, 2024** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

In the Update Path operation, the data types of the Position and Content Length fields are updated from Integer to Long.

W-15989274
## [](#1-0-4)1.0.4 **January 11, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-3)1.0.3 **October 6, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

The jackson-databind transitive dependency is excluded to address reported security vulnerabilities.

W-11853399
## [](#1-0-2)1.0.2 **April 20, 2021** ### [](#compatibility-10)Compatibility
Application/Service Version

Mule

4.2.1 and later
- Fixed reported security issues. ## [](#1-0-1)1.0.1 **January 8, 2021** ### [](#compatibility-11)Compatibility
Application/Service Version

Mule

4.2.1 and later
- Fixed security issues. ## [](#1-0-0)1.0.0 **October 29, 2020** New release ### [](#compatibility-12)Compatibility
Application/Service Version

Mule

4.2.1 and later
For a list of supported configurations and operations, see the Azure Data Lake Storage Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Azure Event Hubs Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Azure Event Hubs (Azure Event Hubs Connector) enables support for event producing and consuming. Guide: [Azure Event Hubs Connector User Guide](https://docs.mulesoft.com/jp/azure-event-hubs-connector/latest/) ## [](#1-2-6)1.2.6 **October 13, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.18.4

Azure Checkpoint Store Blob

1.16.6
### Fixed Issues
Issue Resolution ID

The connector now uses the Azure Core HTTP OkHttp client version 1.12.3, instead of the Netty HTTP client. This change removes the Netty and Reactor Netty libraries.

W-24262985

These libraries are upgraded to address reported security vulnerabilities:

  • The com.fasterxml.jackson.core:jackson-core and com.fasterxml.jackson.core:jackson-databind libraries are upgraded to version 2.22.3.

  • The com.google.guava:guava library is upgraded to version 33.7.2-jre.

W-24457648, W-24113383, W-24406484
## [](#1-2-5)1.2.5 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.18.4

Azure Checkpoint Store Blob

1.16.6
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The io.netty:netty-bom library is upgraded to version 4.1.138.Final.

  • The io.projectreactor.netty:reactor-netty library is upgraded to version 1.2.18.

  • The com.google.guava:guava library is upgraded to version 33.6.0-jre.

  • The jackson-modules library is upgraded to version 2.21.6.

  • The jackson library is upgraded to version 2.21.6.

  • The proton-j library is upgraded to version 0.35.0.

W-3300013
## [](#1-2-4)1.2.4 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.18.4

Azure Checkpoint Store Blob

1.16.6
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.google.guava:guava library is upgraded to version 33.6.0-jre.

  • The io.netty:netty-bom library is upgraded to version 4.1.136.Final.

W-23441705
## [](#1-2-3)1.2.3 **July 14, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.18.4

Azure Checkpoint Store Blob

1.16.6
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The azure-identity library is upgraded to version 1.18.4.

  • The azure-core-http-netty library is upgraded to version 1.16.5.

W-23155728
## [](#1-2-2)1.2.2 **June 5, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.18.1

Azure Checkpoint Store Blob

1.16.6
### Fixed Issues
Issue Resolution ID

The netty-codec-http, netty-codec, netty-codec-dns, netty-handler, and netty-resolver-dns libraries are upgraded to version 4.1.133.Final to address reported security vulnerabilities.

W-22490229
## [](#1-2-1)1.2.1 **December 5, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.18.1

Azure Checkpoint Store Blob

1.16.6
### Fixed Issues
Issue Resolution ID

The azure-identity library is upgraded to version 1.18.1 to address reported security vulnerabilities.

W-19647162
## [](#1-2-0)1.2.0 **March 4, 2025** ### What’s New - The **Eventhub Listener** source now includes the new **Event Position Type** field. For more information, refer to [Eventhub Listener](https://docs.mulesoft.com/jp/azure-event-hubs-connector/latest/azure-event-hubs-connector-reference#EventhubListener). ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.8.3

Azure Checkpoint Store Blob

1.16.6
## [](#1-1-0)1.1.0 **June 27, 2024** ### What’s New - Use the new **Azure endpoint** field to construct the complete URL that the connector uses to establish a connection. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2

Azure Identity

1.8.3

Azure Checkpoint Store Blob

1.16.6
## [](#1-0-2)1.0.2 **May 6, 2024** ### Fixed Issues
Issue Resolution ID

The checkpointing functionality now works correctly.

W-15040647
### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2
## [](#1-0-1)1.0.1 **April 30, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Azure Event Hubs SDK

5.15.2
## [](#1-0-0)1.0.0 **October 17, 2023** ### What’s New This is a new connector. For a list of supported configurations, refer to the Azure Event Hubs Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Azure Event Hubs SDK

5.15.2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Azure Key Vault Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Azure Key Vault (Azure Key Vault Connector) enables you to retrieve secrets, keys, or certificates, and encrypt or decrypt content. Guide: [Azure Key Vault Connector User Guide](https://docs.mulesoft.com/jp/azure-key-vault-connector/latest/) ## [](#1-2-7)1.2.7 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.2.

  • The netty-bom library is upgraded to version 4.2.18.Final.

  • The reactor-core library is upgraded to version 3.8.7.

  • The reactor-netty library is upgraded to version 1.3.7.

W-24113559
## [](#1-2-6)1.2.6 **August 17, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The io.netty:netty-bom library is upgraded to version 4.2.17.Final to address reported security vulnerabilities.

W-23441736
## [](#1-2-5)1.2.5 **July 8, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The io.netty:netty-handler library is upgraded to version 4.2.15.Final to address CVE-2026-33870.

  • The io.netty:netty-common library is upgraded to version 4.2.15.Final to address CVE-2026-33871.

  • The io.netty:netty-codec-http2 library is upgraded to version 4.2.15.Final to address CVE-2025-55163.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.0.

  • The com.azure:azure-security-keyvault-keys library is upgraded to version 4.11.1 to address CVE-2026-33117.

  • The com.azure:azure-security-keyvault-secrets library is upgraded to version 4.11.1.

  • The com.azure:azure-security-keyvault-certificates library is upgraded to version 4.9.0.

W-23192317
## [](#1-2-4)1.2.4 **April 19, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The io.netty:netty-codec-http library is upgraded to version 4.1.132.

  • The io.netty:netty-codec-http2 library is upgraded to version 4.1.132.

  • The io.netty:netty-handler library is upgraded to version 4.1.132.

  • The commons-io:commons-io library is upgraded to version 2.18.0.

W-21568266
## [](#1-2-3)1.2.3 **March 29, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.fasterxml.jackson.core:jackson-core library is upgraded to version 2.21.1.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.21.1.

  • The io.netty:netty-codec-http library is upgraded to version 4.1.131.

  • The io.netty:netty-codec-http2 library is upgraded to version 4.1.131.

  • The io.netty:netty-handler library is upgraded to version 4.1.131.

W-21568266
## [](#1-2-2)1.2.2 **January 22, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The io.netty:netty-handler library is upgraded to version 4.1.130 to address CVE-2025-67735.

W-20636701
## [](#1-2-1)1.2.1 **October 30, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.azure:azure-sdk-bom library is upgraded to version 1.2.35.

  • The com.fasterxml.jackson.core:jackson-core library is upgraded to version 2.17.2 to address CVE-2022-42003.

  • The io.netty:netty-handler library is upgraded to version 4.1.128 to address CVE-2023-34462.

  • The io.projectreactor.netty:reactor-netty-http library is upgraded to version 1.0.48 to address CVE-2022-31690.

  • The net.minidev:json-smart library is upgraded to version 2.5.2 to address CVE-2023-1370.

  • The com.nimbusds:nimbus-jose-jwt library is upgraded to version 10.5 to address CVE-2023-52428.

W-19772828
## [](#1-2-0)1.2.0 **February 21, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17315506
## [](#1-1-4)1.1.4 **August 16, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The following libraries are upgraded to address reported security vulnerabilities:

  • The com.azure:azure-sdk-bom library is upgraded to version 1.2.26.

  • The com.azure:azure-core-http-netty library is upgraded to version 1.15.3.

  • The com.fasterxml.jackson.core:jackson-core library is upgraded to version 2.17.2.

W-16284031
## [](#1-1-3)1.1.3 **June 13, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The azure-security-keyvault-secrets library is upgraded to version 4.8.3 to address reported security vulnerabilities.

W-15791750
## [](#1-1-2)1.1.2 **May 2, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-1)1.1.1 **January 9, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The azure-core-http-netty library is upgraded to version 1.13.11 to address reported security vulnerabilities.

W-14642864
## [](#1-1-0)1.1.0 **September 26, 2023** ### What’s New - The new **URI Override** field enables you to specify the URI for a key vault located outside Azure Commercial Cloud. - The new **Use Azure Default Credential** field enables you to use the authentication parameters taken from environment variables. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#1-0-1)1.0.1 **January 10, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

Updated internal dependencies.

W-12272032
## [](#1-0-0)1.0.0 **October 19, 2022** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Azure Key Vault Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Azure Key Vault Properties Provider Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Azure Key Vault Properties Provider is a configuration that enables you to retrieve your secrets from a secure Azure cloud service before your Mule app runs. Guide: [Azure Key Vault Properties Provider User Guide](https://docs.mulesoft.com/azure-key-vault-properties-provider-connector/latest/) ## [](#2-2-3)2.2.3 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core library is upgraded to version 2.22.2.

  • The jackson-databind library is upgraded to version 2.22.2.

  • The jackson-dataformat-xml library is upgraded to version 2.22.2.

  • The jackson-datatype-jsr310 library is upgraded to version 2.22.2.

W-24113935
## [](#2-2-2)2.2.2 **August 31, 2026** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Secret lookups now fail immediately when Azure Key Vault is unreachable, instead of waiting for a connection timeout on each secret.

W-23275136

The azure-core-http-netty and netty-codec-http 4.1.135.Final libraries are removed to address reported security vulnerabilities.

W-23953257
## [](#2-2-1)2.2.1 **August 19, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.azure:azure-sdk-bom library is upgraded to version 1.3.8.

  • The com.azure:azure-core-http-okhttp library is upgraded to version 1.13.5.

  • The io.netty:netty-bom library is upgraded to version 4.2.17.Final.

W-23441692
## [](#2-2-0)2.2.0 **July 27, 2026** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Mule applications no longer shut down silently on startup when using multiple Azure Key Vault Properties Provider configurations. You can now route secrets to the correct vault by specifying the configuration name using the ${azure-key-vault-properties-provider::configName::secret::key} format, while single-vault configurations continue to support the legacy ${azure-key-vault-properties-provider::secret::key} format.

For more information, see Upgrade the Azure Key Vault Properties Provider.

W-19368044
## [](#2-1-6)2.1.6 **June 12, 2026** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release fixes a transitive dependency issue to ensure the security patch for CVE-2026-33117 correctly propagates to Mule applications.

W-22960586
## [](#2-1-5)2.1.5 **June 4, 2026** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-22684713
## [](#2-1-4)2.1.4 **April 29, 2026** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The netty.bom library is upgraded to version 4.1.132.final.

  • The jackson.core library is upgraded to version 2.21.2.

W-22134399, W-19324168
## [](#2-1-3)2.1.3 **December 17, 2025** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now successfully imports into Anypoint Studio from Exchange for versions 2.1.2 and earlier.

W-18382058

The mule-azure-key-vault-client library is upgraded to version 1.2.3 to address reported security vulnerabilities.

W-20469267

The mule-secure-configuration-property-module library is upgraded to version 1.3.0.

W-20531122
## [](#2-1-2)2.1.2 **February 27, 2025** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The io.netty:netty-handler library is upgraded to version 4.1.118.Final.

  • The net.minidev:json-smart library is upgraded to version 2.5.2.

W-17818337
## [](#2-1-1)2.1.1 **August 19, 2024** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The following libraries are upgraded to address reported security vulnerabilities:

  • The com.azure:azure-sdk-bom library is upgraded to version 1.2.26.

  • The com.fasterxml.jackson.core:jackson-core library is upgraded to version 2.17.2.

W-16474205
## [](#2-1-0)2.1.0 **May 31, 2024** ### What’s New - The **Key Vault Name** attribute now uses the system property `MULE_AZURE_KEY_VAULT_NAME`, if you do not set any value for the attribute. - The `tenantId`, `clientId`, and `clientSecret` attributes are now optional. If you specify these attributes, they must be set together; otherwise, the connector uses the values from the environment variables. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Added the system property MULE_AZURE_KEY_VAULT_NAME to parameterize the key vault name.

W-15734326
## [](#2-0-1)2.0.1 **March 19, 2024** ### What’s New - This property provider is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17
## [](#2-0-0)2.0.0 **September 26, 2023** ### What’s New - The new **URI Override** field enables you to specify the URI for a key vault located outside Azure Commercial Cloud. - Azure Key Vault Properties Provider now supports Azure Default Credential. You can specify your authentication credentials via environment variables. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Deployments no longer fail for Mule apps with the Mule Secure Configuration Properties Extension module and Azure Key Vault Properties Provider.

W-12219112
## [](#1-0-1)1.0.1 **January 10, 2023** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Updated internal dependencies.

W-12272032
### Known Issues
Known Issue Workaround ID

The Mule Secure Configuration Properties Extension module and Azure Key Vault Properties Provider share the same project structure, so they both export the com.mulesoft.modules.configuration.properties.api package. In Mule apps, this causes deployment failures which results in the DuplicateExportedPackageException: There are multiple artifacts exporting the same package error, because the Mule runtime classloader doesn’t allow two different extensions to export the same package.

This issue is fixed in Azure Key Vault Properties Provider 2.0.0 and later. To ensure successful deployment of your Mule apps, upgrade Azure Key Vault Properties Provider to version 2.0.0 or later.

W-12219112
## [](#1-0-0)1.0.0 **October 19, 2022** ### What’s New This is a new properties provider. For a list of supported configurations, refer to the Azure Key Vault Properties Provider Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8 and 11
### Known Issues
Known Issue Workaround ID

The Mule Secure Configuration Properties Extension module and Azure Key Vault Properties Provider share the same project structure, so they both export the com.mulesoft.modules.configuration.properties.api package. In Mule apps, this causes deployment failures which results in the DuplicateExportedPackageException: There are multiple artifacts exporting the same package error, because the Mule runtime classloader doesn’t allow two different extensions to export the same package.

This issue is fixed in Azure Key Vault Properties Provider 2.0.0 and later. To ensure successful deployment of your Mule apps, upgrade Azure Key Vault Properties Provider to version 2.0.0 or later.

W-12219112
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Azure Service Bus Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Azure Service Bus (Azure Service Bus Connector) makes it easy to build integrations that send messages to and receive messages from Azure Service Bus, which is an asynchronous messaging cloud platform. This connector supports communication with queues and topics and can perform actions such as: - Send to queue - Send to topic - Receive from queue - Receive from subscription Guide: [Azure Service Bus Connector User Guide](https://docs.mulesoft.com/microsoft-azure-sb-connector/latest/) ## [](#3-8-1)3.8.1 **October 7, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

7.17.20

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Send and Send batch of messages operations now throw AZURE-SERVICE-BUS-MESSAGING:PAYLOAD_SIZE_EXCEEDED when a message exceeds the destination maximum size. Previously, some oversized messages were dropped and the flow completed as if the send succeeded.

W-23859601

The Message Listener source now recovers after Azure force-detaches an idle AMQP receive link. Previously, the listener stopped consuming after about 10 minutes with no messages until the application was restarted.

W-24207700

The Message Listener source now stops when the subscribed queue or subscription is ReceiveDisabled, instead of reconnecting in a tight loop against a healthy namespace. Re-enable Receive and restart the flow to resume consumption.

W-24070614

These libraries are upgraded to address reported security vulnerabilities:

  • The azure-messaging-servicebus library is upgraded to version 7.17.20.

  • The azure-identity library is upgraded to version 1.18.6.

  • The jackson-databind and jackson-core libraries are upgraded to version 2.22.3.

  • The reactor-core library is upgraded to version 3.8.7.

  • The proton-j library is upgraded to version 0.35.0.

  • The azure-core-http-netty library is replaced with azure-core-http-okhttp version 1.13.6.

W-24262985, W-23441771, W-24137088, W-3300013
## [](#3-8-0)3.8.0 **August 19, 2026** ### What’s New - The **Message Listener** source now supports the new **Enable Dynamic Sessions** field. Enable this field to process session-enabled entities whose session IDs are generated dynamically and not known in advance. Instead of locking a fixed **Message Session Id**, each consumer continuously accepts the next available Service Bus session, drains it, and rolls to the next one. The **Number Of Consumers** field controls how many sessions are processed concurrently. This field can’t be combined with a fixed **Message Session Id** or with **Consume From Dead Letter Queue**. For more information, refer to [Message Listener](https://docs.mulesoft.com/microsoft-azure-sb-connector/latest/azure-service-bus-connector-reference#message-listener) and see the [Receive Messages from Dynamically Generated Sessions](https://docs.mulesoft.com/microsoft-azure-sb-connector/latest/azure-service-bus-connector-examples#dynamic-sessions) example. - The **Message Listener** source now supports the new **Session Idle Timeout** field, which applies only when **Enable Dynamic Sessions** is enabled. Use this field to specify the maximum time a consumer waits for the next message within the currently locked session before treating the session as idle, releasing it, and rolling to the next available session. Configure this duration using an ISO-8601 string. The default value (`PT30S`) preserves existing behavior. For more information, refer to [Message Listener](https://docs.mulesoft.com/microsoft-azure-sb-connector/latest/azure-service-bus-connector-reference#message-listener). ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

7.17.16

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
## [](#3-7-0)3.7.0 **July 8, 2026** ### What’s New - The **Message Listener** source now includes the new **Max Auto Lock Renew Duration** field to specify how long the SDK automatically renews message locks during processing. You can configure this duration using an ISO-8601 string, replacing the previous fixed 5-minute limit. The default value (`PT5M`) preserves existing behavior. Additionally, the connector logs a structured warning if a message lock expires before settlement and warns at startup if the configured duration is shorter than the broker entity’s broker-side lock duration. - The **Message Listener** source now supports the new **Consume From Dead Letter Queue** field. Enable this field to consume messages directly from a queue’s or subscription’s native dead-letter sub-queue (`$deadletterqueue`), without manually constructing the sub-queue path. - The connector now includes a new **Dead Letter** operation. Use this operation to send a locked message to its entity’s native dead-letter sub-queue, with an optional reason, description, and custom properties. - The output attributes for received messages now include the new **Dead Letter Reason** and **Dead Letter Error Description** fields, which are populated when consuming messages from a dead-letter sub-queue. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

7.17.16

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
## [](#3-6-1)3.6.1 **March 18, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

7.17.16

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly honors the configured connection retry strategy for the Message Listener source. Previously, certain connection failures caused the receiver to stop without attempting to re-establish a connection.

W-21289737

The connector with the Azure Active Directory connection type now correctly validates connections for service principals that have only Send or Listen permissions and don’t have management-plane access. Previously, connection validation failed with the MULE:CONNECTIVITY error even though the credentials were valid and the principal could successfully send and receive messages.

W-21379356
## [](#3-6-0)3.6.0 **January 9, 2026** ### What’s New - The connector now uses the `azure-identity` library for authentication, replacing manual token handling. This provides built-in token caching and automatic refresh. - The **Message Listener** source now supports the new **Enable Auto Lock Renewal** field. Use this field to specify whether the source should automatically renew message locks, preventing lock expiration during long-running message processing. - The connector now uses the built-in Azure Service Bus exponential backoff mode for its retry behavior. This replaces custom retry logic with a standardized approach that automatically increases wait times between attempts, providing better connection stability during service interruptions or high-load periods. - The **Minimum Retry Backoff** field for the **Shared Access Signature** and **Azure Active Directory** connection types is now set to a default of 1 second. This must be a positive integer and setting it to zero results in ineffective retry behavior. - The **Increased Wait On Server Busy** and **Increased Wait On Server Busy Time Unit** fields are deprecated and no longer supported for **Shared Access Signature** and **Azure Active Directory** connection types. These behaviors are now fully managed by the Azure Service Bus Java SDK. - The new Azure Service Bus Java SDK v7.17.16 produces more detailed background logs. To keep your application logs clean, add `` to your `log4j2.xml` configuration to suppress excessive AMQP debug information. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

7.17.16

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
## [](#3-5-2)3.5.2 **November 21, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

3.6.7

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The io.netty:netty-codec, io.netty:netty-codec-http, com.fasterxml.jackson.core:jackson-core, com.squareup.okio:okio, com.squareup.okio:okio-jvm, and com.google.guava:guava libraries are updated explicitly to address the outdated version in the app pom.xml file.

W-20146653
## [](#3-5-1)3.5.1 **September 24, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

3.6.7

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.squareup.okhttp3 and net.minidev:json-smart libraries are added explicitly to address the outdated version in the app pom.xml file.

W-19602619

The org.apache.commons library is upgraded to version 3.18.0 to address reported security vulnerabilities.

W-19602619
## [](#3-5-0)3.5.0 **September 7, 2025** ### What’s New - Azure Service Bus Connector now supports session-aware queues. This feature adds the **Message Session Id** field to the **Message Listener** source, and renames the **Session Id** field to **Message Session Id** in the **Send** operation. For an example about how to use this feature, see [Send and Receive Messages Using Session IDs for Session-Aware Queues Example](https://docs.mulesoft.com/microsoft-azure-sb-connector/latest/azure-service-bus-connector-examples#send-receive-session-ids). ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

3.6.7

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
## [](#3-4-3)3.4.3 **June 26, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

3.6.7

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.squareup.okhttp3:okhttp library is upgraded to version 4.11.0.

  • The com.squareup.okio:okio library is upgraded to version 3.4.0.

  • The net.minidev:json-smart library is upgraded to version 2.5.2.

  • The com.google.guava:guava library is upgraded to version 32.1.3-jre.

W-18647584
## [](#3-4-2)3.4.2 **May 17, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Azure Service Bus Java SDK

3.6.7

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The outdated dependency versions are upgraded to address reported security vulnerabilities.

W-18291109
## [](#3-4-1)3.4.1 **August 12, 2024** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.7

Microsoft Authentication Library for Java

1.16.2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Receive Batch operation no longer prefetches messages to prevent retrieving messages that might never be read.

W-16325071

The AZURE-SERVICE-BUS-MESSAGING:ANY error is now thrown instead of the MULE:ANY error.

W-14052254

The following libraries are upgraded to address reported security vulnerabilities:

  • The io.netty:netty-codec, io.netty:netty-codec-http, io.netty:netty-common, io.netty:netty-codec-socks, io.netty:netty-handler-proxy, and io.netty:netty-handler libraries are upgraded to version 4.1.112.Final.

  • The com.microsoft.azure:azure-servicebus library is upgraded to version 3.6.7.

  • The com.microsoft.azure:msal4j library is upgraded to version 1.16.2.

  • The commons-io:commons-io library is upgraded to version 2.16.1.

  • The commons-codec:commons-codec library is upgraded to version 1.17.1.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.17.2.

W-14462875
## [](#3-4-0)3.4.0 **June 25, 2024** ### What’s New - Use the new **Azure endpoint** field to construct the complete URL that the connector uses to establish a connection. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The following libraries are upgraded:

  • com.google.guava:guava from 32.0.1-jre to 32.1.3-jre.

  • com.microsoft.azure:msal4j from 1.11.0 to 1.15.1.

W-15747087
## [](#3-3-0)3.3.0 **May 31, 2024** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The debug logging is now improved.

W-15613142

The connector now sends the correct ANY error type propagation for the Send operation.

W-15829526

The connector now allows disabling the producers (senders) cache.

W-15861141

The connector now allows to set additional backoff time whenever there is a ServerBusyException.

W-15846020
## [](#3-2-8)3.2.8 **February 6, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8, 11, and 17
## [](#3-2-7)3.2.7 **September 19, 2023** ### What’s New - The okio version 3.4.0 dependency was added. The following dependencies are upgraded: - json-smart 2.4.7 to 2.4.9 - netty-handler 4.1.48.Final to 4.1.94.Final - okhttp3 4.9.2 to 4.11.0 ### Fixed Issues
Issue Resolution ID

The following dependencies are upgraded:

  • json-smart 2.4.7 to 2.4.9

  • netty-handler 4.1.48.Final to 4.1.94.Final

  • okhttp3 4.9.2 to 4.11.0

W-14067647

The okio version 3.4.0 dependency was added.

W-14067647
### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
## [](#3-2-6)3.2.6 **July 19, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The correlation ID of the received message now matches the correlation ID of the flow.

W-13569728
## [](#3-2-5)3.2.5 **June 8, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Netty Codec library from io.netty:netty-codec:4.1.68.Final to io.netty:netty-codec:4.1.92.Final.

W-12665448
## [](#3-2-4)3.2.4 **April 28, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.13.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665862
## [](#3-2-3)3.2.3 **October 25, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The TimeoutException message now contains more information about the related error.

W-11785747
## [](#3-2-2)3.2.2 **October 6, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The jackson-databind library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853417
## [](#3-2-1)3.2.1 **May 19, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading io.netty:netty-common from 4.1.68.Final to 4.1.77.Final.

W-11124604
## [](#3-2-0)3.2.0 **February 1, 2022** ### What’s New - Added the Azure Active Directory connection provider, which enables authentication via client credentials. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

Microsoft Authentication Library for Java

1.11.0

OpenJDK

8 and 11
## [](#3-1-3)3.1.3 **December 7, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.6.5

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed security vulnerabilities.

CONN-9253
## [](#3-1-2)3.1.2 **April 14, 2021** ### [](#compatibility-24)Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.4.0

OpenJDK

8 and 11
### [](#fixed-issues-18)Fixed Issues - The Message Listener will now try to reconnect if you disable and then re-enable a queue from the Azure Portal. (SE-20365) ## [](#3-1-1)3.1.1 **November 25, 2020** ### [](#compatibility-25)Compatibility
Application/Service Version

Mule

4.2.1 and later

Azure Service Bus Java SDK

3.4.0

OpenJDK

8 and 11
### [](#fixed-issues-19)Fixed Issues - Fixed the missing dependency error that occured when the connector was added to Studio 7. (SE-18475) ## [](#3-1-0)3.1.0 **October 7, 2020** ### [](#compatibility-26)Compatibility
Application/Service Version

Mule

4.1.1 and later

Azure Service Bus Java SDK

3.4.0

OpenJDK

8 and 11
### [](#fixed-issues-20)Fixed Issues - Fixed the `nimbus-jose-jwt` and `lang-tag` dependency versions to avoid the `Missing Jar` errors. (SE-17751) - Fixed the `Delivery not found on the receive link` error in the Abandon operation when using the manual ACK type. (SE-17703) - Added a parameter to configure `Buffered` or `Serial mode` in the Message Listener operation. (SE-17364) ## [](#3-0-2)3.0.2 **September 8, 2020** ### [](#compatibility-27)Compatibility
Application/Service Version

Mule

4.1.6 and later

Azure Service Bus Java SDK

3.4.0
### [](#fixed-issues-21)Fixed Issues Fixed security vulnerabilities. (CONN-6884) ## [](#3-0-1)3.0.1 **September 3, 2020** ### [](#compatibility-28)Compatibility
Application/Service Version

Mule

4.1.6 and later

Azure Service Bus Java SDK

3.4.0
### [](#fixed-issues-22)Fixed Issues Fixed the `Delivery not found on the receive link` error in the Complete operation when using ACK manual type. (SE-17352) ## [](#3-0-0)3.0.0 **July 31, 2020** New release ### [](#compatibility-29)Compatibility
Application/Service Version

Mule

4.1.6 and later

Azure Service Bus Java SDK

3.4.0
### [](#features)Features Azure Service Bus Connector offers the following features: - Send and Fetch Multiple Messages Use the connector to send messages and fetch messages in batches. - Perform ACK’s and NACK’s Leverage the connector’s capabilities to acknowledge a message or to abandon a message. For a list of supported configurations and operations, see the Azure Service Bus Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Azure Service Bus Management Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Azure Service Bus Management (Azure Service Bus Management Connector) enables management integration with Azure Service Bus on the cloud. This connector connects to the Azure REST API and supports management operations for queues, topics, and subscriptions. You can use the built-in management API to discover Azure Service Bus objects automatically and provision them. Guide: [Azure Service Bus Management Connector User Guide](https://docs.mulesoft.com/jp/azure-service-bus-management-connector/latest/) ## [](#1-0-5)1.0.5 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule Runtime

4.2.0 and later

OpenJDK

8, 11, and 17

Service Bus

Microsoft Azure Service Bus (Cloud)
## [](#1-0-4)1.0.4 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule Runtime

4.2.0 and later

OpenJDK

8, 11, and 17

Service Bus

Microsoft Azure Service Bus (Cloud)
## [](#1-0-3)1.0.3 **March 25, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule Runtime

4.2.0 and later

OpenJDK

8, 11, and 17

Service Bus

Microsoft Azure Service Bus (Cloud)
## [](#1-0-2)1.0.2 **January 4, 2024** ### Compatibility
Software Version

Mule

4.2.0 and later

Service Bus

Microsoft Azure Service Bus (Cloud)
### Fixed Issues
Issue Resolution ID

The component org.json:json library is upgraded to version 20231013 to address reported security vulnerabilities.

W-13844861
## [](#1-0-1)1.0.1 **December 1, 2022** ### Compatibility
Software Version

Mule

4.1.6 and later

Service Bus

Microsoft Azure Service Bus (Cloud)
### Fixed Issues
Issue Resolution ID

Azure Service Bus Management Connector no longer fails to deploy in Windows due to an encoding error.

W-12143761
## [](#1-0-0)1.0.0 **July 31, 2020** New release ### [](#compatibility-6)Compatibility
Application/Service Version

Mule

4.1.6 and later

Service Bus

Microsoft Azure Service Bus (Cloud)
For a list of supported configurations and operations, see the Azure Service Management Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Basic Authentication - LDAP ## [](#1-4-2)1.4.2 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-4-0)1.4.0 **July 29, 2022** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-3-1)1.3.1 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. ### [](#fixed-issues)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-3-0)1.3.0 **Jul 26, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Several performance improvements are introduced in this release. - Improved error handling for LDAP server validation errors and user authentication errors with appropriate error messages. The application generated a 401 error for both LDAP server authentication problems and incorrect user credentials provided by the user. The application now generates error 500 for LDAP server authentication errors. When incorrect user credentials are provided, error 401 is generated. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Introduced support to encrypt sensitive information related to the policy. The Runtime version must be properly configured and must support encryption. Encryption is supported starting with Mule Runtime v4.2.0. - Several performance improvements are introduced. - Reduced policy weight. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ### [](#fixed-issues-2)Fixed Issues When a WSDL proxy received an empty payload, or an invalid XML, an ExpressionRuntimeException error was generated. This issue is now resolved. ## [](#1-1-1)1.1.1 **Jun 25, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements Added `violationCategory` in the YAML configuration for Feedback Loop. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Added subtree search scope. - Reduced error-handling verbosity in templates. ### [](#fixed-issues-3)Fixed Issues - Improved error message verbiage for the invalid server scheme error. - When an Authorization header is malformed, a 500 status code was returned instead of 401. This issue is now resolved. ## [](#1-0-0)1.0.0 **Nov 17, 2017** ### [](#minimum-mule-version-6)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [LDAP Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-basic-auth-ldap) - [Known Issues](https://help.salesforce.com/s/issues) # Basic Authentication - Simple ## [](#1-3-3)1.3.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-3-1)1.3.1 **May 26, 2022** ### [](#fixed-issues)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-3-0)1.3.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-2-2)1.2.2 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are made to the header manipulation engine. ### [](#fixed-issues-2)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-2-1)1.2.1 **Jul 22, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Several performance improvements are introduced in this release. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Introduced support to encrypt sensitive information related to the policy. The runtime version must support encryption and must be properly configured. Encryption is supported since Mule Runtime v4.2.0. - Several performance improvements are introduced. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-1)1.1.1 **Jun 29, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements Added `violationCategory` in the YAML configuration for Feedback Loop. ## [](#1-1-0)1.1.0 **Jan 26, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements Reduced error-handling verbosity in templates. ### [](#fixed-issues-3)Fixed Issues - When a WSDL proxy receives an empty payload, or an invalid XML, an `ExpressionRuntimeException` error is generated. - When Mule is redeployed, the basic auth policies do not work. - GroupId missing for proxy samples dependency. - When an Authorization header is malformed, a 500 status code is returned instead of 401. ## [](#1-0-0)1.0.0 **Nov 17, 2017** ### [](#minimum-mule-version-6)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [HTTP Basic Authentication Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-basic-auth-simple) - [Known Issues](https://help.salesforce.com/s/issues) # Basic Authentication: LDAP The Basic Authentication: LDAP policy allows access based on the basic authorization mechanism, with user-password defined on LDAP. For configuration details, see [Basic Authentication: LDAP Policy](https://docs.mulesoft.com/gateway/latest/policies-included-basic-auth-ldap). ## [](#october-1-2026)October 1, 2026 ### What’s New - Basic Authentication: LDAP policy definition version 1.4.2 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#september-04-2025)September 04, 2025 ### What’s New - Basic Authentication: LDAP policy implementation version 1.4.0 is now supported by Omni Gateway. - Basic Authentication: LDAP policy definition version 1.5.0 is now supported by Omni Gateway. # Basic Authentication: Simple The Basic Authentication: Simple policy allows access based on the basic authorization mechanism, with a single user-password. For configuration details, see [Basic Authentication: Simple Policy](https://docs.mulesoft.com/gateway/latest/policies-included-basic-auth-simple). ## [](#october-1-2026)October 1, 2026 ### What’s New - Basic Authentication: Simple policy definition version 1.3.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - Basic Authentication: Simple policy implementation version 1.2.2 is now supported by Omni Gateway. - Basic Authentication: Simple policy definition version 1.3.1 is now supported by Omni Gateway. # Bird Connector Release Notes Anypoint Connector for Bird (Bird Connector) enables Mule applications to access the Bird API. Guide: [Bird Connector User Guide](https://docs.mulesoft.com/bird-connector/latest/) ## [](#1-1-0)1.1.0 **September 1, 2026** ### What’s New This is a new connector. For more information, see the [Bird Connector User Guide](https://docs.mulesoft.com/bird-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [Bird Connector User Guide](https://docs.mulesoft.com/bird-connector/latest/) - [Bird Connector Reference](https://docs.mulesoft.com/bird-connector/latest/bird-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Blackboard Connector Release Notes Anypoint Connector for Blackboard (Blackboard Connector) enables Mule applications to access the Blackboard API. Guide: [Blackboard Connector User Guide](https://docs.mulesoft.com/blackboard-connector/latest/) ## [](#0-2-0)0.2.0 **September 2, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **April 14, 2026** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/blackboard-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [Blackboard Connector User Guide](https://docs.mulesoft.com/blackboard-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [Blackboard Connector User Guide](https://docs.mulesoft.com/blackboard-connector/latest/) - [Blackboard Connector Reference](https://docs.mulesoft.com/blackboard-connector/latest/blackboard-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Box Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Box (Box Connector) provides a bidirectional gateway between Box, a secure content management and collaboration platform, and Mule. Box Connector supports a subset of Box API v2.0 operations. Refer to the Box Connector reference documentation for a complete list of supported Box Connector operations. Guide: [Box Connector User Guide](https://docs.mulesoft.com/jp/box-connector/latest/) ## [](#5-3-4)5.3.4 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
## [](#5-3-3)5.3.3 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.2.

  • The gson library is upgraded to version 2.14.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

W-23441653
## [](#5-3-2)5.3.2 **July 21, 2026** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.1.

  • The jackson-databind library is upgraded to version 2.22.1.

  • The log4j library is upgraded to version 2.26.1.

W-23136414
## [](#5-3-1)5.3.1 **May 26, 2026** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
### Fixed Issues
Issue Resolution ID

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21762136

The log4j library is upgraded to version 2.25.4 to address reported security vulnerabilities.

W-21762136
## [](#5-3-0)5.3.0 **October 16, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. - The **Keystore Type** field in the JWT connection type now supports three predefined values and any custom types. ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
## [](#5-2-6)5.2.6 **June 20, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
### Fixed Issues
Issue Resolution ID

You can now install Box Connector in Anypoint Studio as intended.

W-16052117
## [](#5-2-5)5.2.5 **April 26, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
### Fixed Issues
Issue Resolution ID

You can now install Box Connector in Anypoint Studio as intended.

W-15593434
## [](#5-2-4)5.2.4 **April 18, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Box API

2.0
## [](#5-2-3)5.2.3 **January 12, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue Resolution ID

Query parameters of the List type are now concatenated into a single parameter with comma-separated values instead of multiple query parameters that each contain a single value and have the same name.

W-14556157
## [](#5-2-2)5.2.2 **August 11, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue Resolution ID

The List folder collaborations operation no longer uses pagination since Box changed its underlying API endpoint, so the offset and limit fields are now ignored but are present only for backward compatibility.

W-13687119
## [](#5-2-1)5.2.1 **June 8, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue Resolution ID

Package conflicts no longer occur when using this connector with other specific connectors in a project.

W-13311688
## [](#5-2-0)5.2.0 **May 29, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue Resolution ID

The Download zip archive operation now contains the new Zip download URL generated by 'Create zip download' operation field, which is the temporary URL to download the zip archive. The Zip download id field is now deprecated.

W-13058446

The com.fasterxml.jackson.core library is upgraded to version 2.15.0 to address reported security vulnerabilities.

W-12360274

The jose.4.j library is upgraded to version 0.9.3 to address reported security vulnerabilities.

W-12360274

The org.json library is upgraded to version 20230227 to address reported security vulnerabilities.

W-12360274
## [](#5-1-12)5.1.12 **October 19, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Library dependencies are upgraded to address reported security vulnerabilities.

W-11845805
## [](#5-1-11)5.1.11 **September 5, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11640492
## [](#5-1-10)5.1.10 **July 15, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

The Search for content operation no longer fails with a 400 error when retrieving items using the offset value increased by the value of limit.

W-11336383
## [](#5-1-9)5.1.9 **June 30, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Upgraded library dependencies.

W-11336767
## [](#5-1-8)5.1.8 **June 8, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Upgraded library dependencies.

W-11136076
## [](#5-1-7)5.1.7 **April 20, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Upgraded library dependencies.

W-11023862
## [](#5-1-6)5.1.6 **April 7, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920462
## [](#5-1-5)5.1.5 **January 10, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9845
## [](#5-1-4)5.1.4 **December 21, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9631
## [](#5-1-3)5.1.3 **December 14, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9555
## [](#5-1-2)5.1.2 **November 19, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

OpenJDK

8 and 11

Box API

2.0
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9252

Fixed an expression error with the Content-Type metadata when creating a multipart payload.

SE-23358
## [](#5-1-1)5.1.1 **July 15, 2021** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11

Box API

2.0
### [](#fixed-issues-21)Fixed Issues - Updated the connector’s UI to prevent the incorrect use of pagination. (SE-21739) ## [](#5-1-0)5.1.0 **July 12, 2021** ### [](#compatibility-25)Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11

Box API

2.0
### [](#new-features)New Features - Added the **On Download File**, **On New File In Folder**, **On New Folder**, and **On New Task Created** sources. ## [](#5-0-0)5.0.0 **March 18, 2021** ### [](#compatibility-26)Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11

Box API

2.0
### [](#features)Features This Box Connector release includes new operations. See the Box Connector Upgrade Guide for a list of the new operations. ## [](#4-0-5)4.0.5 **December 7, 2020** ### [](#compatibility-27)Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11

Box API

2.0
### [](#features-2)Features Upgraded the Apache Commons IO library to the latest version, 2.8.0. ## [](#4-0-4)4.0.4 **August 5, 2020** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8 and 11

Box API

2.0
### [](#fixed-issues-22)Fixed Issues OAuth properties that were missing in the configuration for the 4.0.2 and 4.0.3 versions of the connector are added back. (SE-16868) ## [](#4-0-3-deprecated)4.0.3 (Deprecated) **July 13, 2020** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.0 and later

Java

1.8 and later

Box API

2.0
### [](#features-3)Features The `commmons-codec` library is updated to version 1.14. ## [](#4-0-2-deprecated)4.0.2 (Deprecated) **May 20, 2020** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.1.0 and later

Java

1.8 and later

Box API

2.0
Box Connector supports a subset of operations from Box API v2.0. Refer to the Box Connector Module Documentation Reference for a complete list of Box Connector Operations. ### [](#features-4)Features - Updated multiple libraries to the latest versions. ## [](#4-0-1)4.0.1 **August 6, 2019** ### [](#compatibility-31)Compatibility
Software Version

Mule

4.1 and later

Java

1.8 and later

Box API

2.0
The Box connector supports a subset of operations from Box API v2.0. Refer to the Box Connector Module Documentation Reference for a complete list of Box Connector Operations. ### [](#fixed-issues-23)Fixed Issues - The `Get File Content` operation was not returning the payload \[SE-12060\] \[SE-12114\] ## [](#4-0-0)4.0.0 **February 27, 2018** ### [](#compatibility-32)Compatibility
Software Version

Mule

4.1 and later

Java

1.8 and later

Box API

2.0
Box Connector only supports a subset of operations from Box API v2.0. See the Connector Reference for the list of Box Connector Operations. ### [](#features-5)Features - Box Connector is an auto-generated connector built using the REST Connect which takes RAML 1.0 API specification files that are prepared for the Box 2.0 API as an input. - This connector has been migrated to support Mule 4.1 and later. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Canvas Connector Release Notes Anypoint Connector for Canvas (Canvas Connector) enables Mule applications to access the Canvas API. Guide: [Canvas Connector User Guide](https://docs.mulesoft.com/canvas-connector/latest/) ## [](#1-1-0)1.1.0 **September 2, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-0-0)1.0.0 **April 14, 2026** ### What’s New This is a new connector. For more information, see the [Canvas Connector User Guide](https://docs.mulesoft.com/canvas-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [Canvas Connector User Guide](https://docs.mulesoft.com/canvas-connector/latest/) - [Canvas Connector Reference](https://docs.mulesoft.com/canvas-connector/latest/canvas-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # CAQH Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for CAQH lets you connect to the CAQH - ProView and DirectAssure Rosters using CAQH Data API. The connector exposes convenient methods to retrieve information about providers in real-time for credentialing and other purposes for Participating Organizations. MuleSoft recommends that you install the latest version of Studio. Guide: [CAQH Connector User Guide](https://docs.mulesoft.com/jp/caqh-connector/latest/) ## [](#1-0-1)1.0.1 **May 21, 2019** ### [](#compatibility)Compatibility
Application/Service Version

Mule

Mule Enterprise Edition 4.0.0 and later

Java

8

CAQH - ProView

v2

CAQH - DirectAssure

v2
### [](#fixed-issues)Fixed Issues - Test connection bug is fixed for use in Design Center. - The Get Provider Credentials operation’s media type is changed to `application/xml`. - Updated icon to CAQH. ## [](#1-0-0)1.0.0 **May 3, 2019** ### [](#compatibility-2)Compatibility
Application/Service Version

Mule

Mule Enterprise Edition 4.0.0 and later

Java

8

CAQH - ProView

v2

CAQH - DirectAssure

v2
### [](#features)Features - ProView Roster API Service: Add, update, or delete roster request for CAQH ProView. - Proview Roster Status Check: Check status of providers in CAQH ProView. - DirectAssure Roster API Service: Add, update, or delete roster Request for CAQH DirectAssure. - DirectAssure Roster Status Check: Check status of providers in CAQH DirectAssure. ### [](#fixed-issues-2)Fixed Issues First version. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Cassandra Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Cassandra provides the capability to connect a Mule app to a Cassandra database or cluster. Guide: [Cassandra Connector User Guide](https://docs.mulesoft.com/cassandra-connector/latest/) ## [](#5-0-0)5.0.0 **September 21, 2026** ### What’s New - This connector now supports Apache Cassandra 5.x. The connector now uses DataStax Java Driver 4.17.0. - The **Cassandra Cluster Name** field is removed from Studio. It no longer appears on the **General** or **Advanced Settings** tab. Applications that still set `clusterName` on `cassandra-db:connection` fail to deploy. Delete the attribute. Contact points and [**Cassandra Cluster Nodes**](https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-reference#config_connection) still select the cluster. - The new [**Local Datacenter**](https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-reference#config_connection) field is on the **Advanced Settings** tab. It sets the local datacenter for the driver’s load-balancing policy. Set this field when contact points don’t share one datacenter, such as in a multi-DC cluster. You can omit it for single-DC clusters. - The new [**Request Timeout (ms)**](https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-reference#config_connection) field is on the **Advanced Settings** tab. It sets the per-request timeout for CQL operations. The default is `12000` milliseconds, which preserves the 12-second deadline from version 4.1. - TLS configuration now applies to the driver. The default [**Endpoint identification algorithm**](https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-reference#config_connection) is `DISABLED`. If your XML still sets `HTTPS` or `LDAPS`, version 5.0 validates the server certificate against the host. - Don’t select native protocol `V1` or `V2`. Those values fail at application initialization. Leave [**Protocol Version**](https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-reference#config_connection) unset to let the driver negotiate, including native protocol V5 on Apache Cassandra 5.x. - On Apache Cassandra 5.x, the [**Change Column Type**](https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-reference#changeColumnType) operation fails because Cassandra no longer supports altering column types. Add a new column, backfill the data, then drop the old column. For more information about how to upgrade, see [Upgrading and Migrating Cassandra Connector to 5.x](https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.6.0 and later

Cassandra database or cluster

5.x

CQL spec

3.x

OpenJDK

8, 11, and 17

DataStax Java Driver for Apache Cassandra

4.17.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.2.

  • The netty-codec library is upgraded to version 4.2.0.Final.

  • The netty-handler library is upgraded to version 4.1.137.Final.

  • The guava library is upgraded to version 32.1.3-jre.

  • The jnr-posix library is upgraded to version 3.2.2.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-collections4 library is upgraded to version 4.6.0.

W-24070820, W-24113938, W-23790517
## [](#4-1-4)4.1.4 **February 18, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8, 11, and 17

DataStax Java Driver for Apache Cassandra

3.11.3
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address the CVE-2025-24970 security vulnerability:

  • The netty-codec library is upgraded to version 4.1.125.Final.

  • The netty-handler library is upgraded to version 4.1.125.Final.

W-21239177

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The commons-collections library is migrated to commons-collections4 version 4.4.0.

W-21286162
## [](#4-1-3)4.1.3 **September 27, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8, 11, and 17

DataStax Java Driver for Apache Cassandra

3.11.3
## [](#4-1-2)4.1.2 **October 6, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.11.3
### Fixed Issues
Issue Resolution ID

The com.google.guava library is upgraded to version 32.0.1-jre to address reported security vulnerabilities.

W-13844875

The netty-handler library is upgraded to version 4.1.94.Final to address reported security vulnerabilities.

W-13844862
## [](#4-1-1)4.1.1 **May 2, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.11.3
### Fixed Issues
Issue Resolution ID

Cassandra driver is upgraded to version 3.11.3.

W-12665856

Jackson-core and jackson-databind libraries are upgraded to version 2.15.0.

W-12665443

Netty-codec library is upgraded to version 4.1.92-Final.

W-12665865
## [](#4-1-0)4.1.0 **Mar 27, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### Fixed Issues
Issue Resolution ID

Cassandra Connector now has a new Prepared Statements Cache Size parameter that enables you to set a cache in memory for prepared statements to avoid performance issues.

W-12630494
## [](#4-0-8)4.0.8 **May 20, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Netty Codec library from io.netty:netty-codec:4.1.68.Final to io.netty:netty-codec:4.1.77.Final.

W-11124605
## [](#4-0-7)4.0.7 **April 13, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.11.3 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920459

Fixed reported security vulnerabilities by upgrading the Netty Handler library from io.netty:netty-handler:4.1.59.Final to io.netty:netty-handler:4.1.76.Final.

W-10920459
## [](#4-0-6)4.0.6 **March 28, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### Fixed Issues
Issue ID

Cassandra Connector can now parse dates with the yyyy-mm-dd’T’HH:mm:ssZ format when performing an Insert operation.

W-10853991
## [](#4-0-5)4.0.5 **September 24, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### Fixed Issues
Issue ID

Fixed a CassandraDB vulnerability.

CONN-8854
## [](#4-0-4)4.0.4 **August 11, 2021** ### [](#compatibility-11)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### [](#fixed-issues-10)Fixed Issues - CloudHub schedules were not created when Cassandra Connector 4.x was configured within an application. (SE-22151) ## [](#4-0-3)4.0.3 **July 23, 2021** ### [](#compatibility-12)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### [](#fixed-issues-11)Fixed Issues - Fixed all reported vulnerabilities. ## [](#4-0-2)4.0.2 **March 12, 2021** ### [](#compatibility-13)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### [](#fixed-issues-12)Fixed Issues - The DATE type sent to Cassandra was not parsed correctly. (SE-19919) ### [](#limitation)Limitation Cassandra operations do not support frozen column types or other custom column types. When using these column types, use the **Execute CQL Query** operation with a raw CQL query. ## [](#4-0-1)4.0.1 **February 22, 2021** ### [](#compatibility-14)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### [](#fixed-issues-13)Fixed Issues - Fixed all reported security vulnerabilities. ### [](#limitation-2)Limitation Cassandra operations do not support frozen column types or other custom column types. When using these column types, use the **Execute CQL Query** operation with a raw CQL query. ## [](#4-0-0)4.0.0 **November 5, 2020** ### [](#compatibility-15)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11

DataStax Java Driver for Apache Cassandra

3.10.1
### [](#features)Features - Implemented Mutual TlS authentication. - Removed the **SSL** field from the configuration and replaced it with **TLS**. - Refactored error handling and error types. ### [](#fixed-issues-14)Fixed Issues - The package name was changed from `org/mule/modules/cassandradb` to `com/mulesoft/connector/cassandradb`. ### [](#limitation-3)Limitation Cassandra operations do not support frozen column types or other custom column types. When using these column types, use the **Execute CQL Query** operation with a raw CQL query. ## [](#3-1-4)3.1.4 **May 19, 2020** ### [](#compatibility-16)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x

OpenJDK

8 and 11
### [](#features-2)Features - None ### [](#fixed-issues-15)Fixed Issues - Fixed a man-in-the-middle vulnerability caused by the Netty handler is used by the Cassandra driver. ## [](#3-1-3)3.1.3 **May 6, 2020** ### [](#compatibility-17)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x
### [](#features-3)Features - None ### [](#fixed-issues-16)Fixed Issues - Fixed all reported vulnerabilities. ## [](#3-1-2)3.1.2 **January 17, 2020** ### [](#compatibility-18)Compatibility
Application/Service Version

Mule

4.1.1 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x
### [](#fixed-issues-17)Fixed Issues Fixed vulnerabilities ### [](#improvements-and-changes)Improvements and Changes - Added DEBUG logging level to help with troubleshooting - Added a Summary annotation - Javadoc improvements - Pluralized list names and changed variable’s names that refer to lists that use plural names - Parent upgrade - Removed Atlantic library ## [](#3-1-1)3.1.1 **April 26, 2019** ### [](#compatibility-19)Compatibility
Application/Service Version

Mule

4.0 and later

Cassandra database or cluster

1.2 and later

CQL spec

3.x
### [](#fixed-issues-18)Fixed Issues - Fixed an issue where the timestamp field was presenting the following error: com.datastax.driver.core.exceptions.CodecNotFoundException: Codec not found for requested operation: \[timestamp <→ java.lang.String\](https://docs.mulesoft.com/jp/release-notes/connector/SE-10920) The string date is now converted into a date accepted by the Cassandra driver. (SE-11613) ## [](#3-1-0)3.1.0 **July 31, 2018** Cassandra connector is available on Mule 4.0. ### [](#compatibility-20)Compatibility
Application/Service Version

Cassandra database or cluster

1.2 and later

CQL spec

3.x

Mule

4.0 and later
### [](#features-4)Features - This version supports Cassandra cluster configuration. Users can provide comma-separated Cassandra nodes, for example `127.0.0.1:9160, 127.0.0.2:9160`. ## [](#3-0-0)3.0.0 **January 12, 2018** Cassandra connector is available in Mule 4.0. ### [](#compatibility-21)Compatibility
Application/Service Version

Cassandra database or cluster

1.2 and later

CQL spec

3.x

Mule

4.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Circuit Breaker The Circuit Breaker policy prevents an upstream from receiving too many requests or connections. For configuration details, see [Circuit Breaker Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-circuit-breaker). ## [](#february-24-2025)February 24, 2025 ### What’s New - Circuit Breaker policy implementation version 1.0.0 is now supported by Omni Gateway. - Circuit Breaker policy definition version 1.0.0 is now supported by Omni Gateway. # Client ID Enforcement The Client ID Enforcement policy allows access only to authorized client applications. For configuration details, see [Client ID Enforcement Policy](https://docs.mulesoft.com/gateway/latest/policies-included-client-id-enforcement). ## [](#october-1-2026)October 1, 2026 ### What’s New - Client ID Enforcement policy definition version 1.3.4 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - Client ID Enforcement policy implementation version 1.3.1 is now supported by Omni Gateway. - Client ID Enforcement policy definition version 1.3.2 is now supported by Omni Gateway. # Client ID Enforcement ## [](#1-3-4)1.3.4 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-3-2)1.3.2 **May 26, 2022** ### [](#fixed-issues)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-3-1)1.3.1 **May 17, 2022** ### [](#fixed-issues-2)Fixed issues - When using HTTP Basic Authentication Header, policy was expecting a specific value for Client ID Expression. ## [](#1-3-0)1.3.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-2-4)1.2.4 **August 26, 2021** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-3)Fixed issues - An error occurred when generating the response of a multipart SOAP request with invalid credentials. ## [](#1-2-3)1.2.3 **January 06, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Added OAS 3.0 code snippet in the policy YAML file. ## [](#1-2-2)1.2.2 **Apr 30, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are made to the header manipulation engine. - Several performance improvements made in error handling. ### [](#fixed-issues-4)Fixed issues - After the policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). - An error occurred when handling invalid header values of the Basic Authentication policy. - When requests are made to the protected API endpoint with the Client ID Enforcement policy that does not include the client ID and/or secret, a log entry is now created with the details. However, this logging occurs only when you have specified the Debug level in the log4j settings. ## [](#1-2-1)1.2.1 **Jul 12, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Several performance improvements were introduced in this release. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Introduced support for encrypting sensitive information related to the policy. The runtime version must be correctly configured to support encryption. Encryption support was introduced in Mule Runtime v4.2.0. - Several performance improvements were introduced in this release. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-3)1.1.3 **Jan 10, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Improved RAML and OAS Snippets. ## [](#1-1-2)1.1.2 **Jun 27, 2018** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Added violationCategory in the YAML configuration file for Feedback Loop. ## [](#1-1-1)1.1.1 **May 11, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-5)Fixed Issues - An error occurred when attempting to set Authentication in an existing authentication object. This error is now resolved. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-8)New Features and Enhancements - Reduced error-handling verbosity in templates. ### [](#fixed-issues-6)Fixed Issues - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-10)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [Client ID Enforcement Policy](https://docs.mulesoft.com/gateway/latest/policies-included-client-id-enforcement) - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub 2.0 Release Notes ## [](#july-27-2026)July 27, 2026 ### What’s New - Horizontal Pod Autoscaling (HPA) is available to organizations with an Enterprise License Agreement (ELA). If the HPA option is not visible in the Runtime Manager UI, contact your account team to confirm the SKU is enabled. For more information, see [Configuring Horizontal Autoscaling (HPA) for CloudHub 2.0 Deployments](https://docs.mulesoft.com/cloudhub-2/ch2-configure-horizontal-autoscaling). ## [](#january-28-2026)January 28, 2026 ### What’s New - You can now establish secure and private outbound connections to various services hosted on AWS using CloudHub 2.0 private space and Outbound Private Link. For more information about configuring Outbound Private Link connections, see [Setting Up an Outbound Private Link Connection](https://docs.mulesoft.com/cloudhub-2/ps-outbound-private-link). ## [](#january-15-2026)January 15, 2026 ### What’s New - CloudHub 2.0 private spaces now include an updated ingress architecture that improves traffic reliability through enhanced connection pooling. This update applies to private spaces in the EU (eu-west-1) region only. ## [](#october-27-2025)October 27, 2025 ### What’s New - You can now use the MuleSoft diagnostics agent to collect diagnostics data from your applications and analyze them with Einstein. See [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/cloudhub-2/ch2-view-diag). ## [](#september-15-2025)September 15, 2025 ### What’s New - You can now use the in-product app migration tool in Runtime Manager to migrate your CloudHub applications to CloudHub 2.0. For more information, see [CloudHub to CloudHub 2.0 Application Migration](https://docs.mulesoft.com/cloudhub/app-migration). - You can now configure path rewriting per endpoint in your application’s **Ingress** configuration. When used in conjunction with the app migration tool, you can carry over differing mapping rules for different endpoints within the application. - You can now configure custom domains for internal endpoints that are only accessible from within your private network. Use the new **Access** field to specify internal or external access for your custom endpoints. ## [](#august-5-2025)August 5, 2025 ### What’s New - You can now set a TCP keepalive within the private space to prevent outgoing Mule application requests from timing out. To enable it at the socket level, set the `keepAlive` flag in your HTTP connector’s TCP client properties. For more information, see [TCP Client Socket Properties](https://docs.mulesoft.com/http-connector/latest/http-documentation#TcpClientSocketProperties). ## [](#july-1-2025)July 1, 2025 ### Fixed Issues
Issue Resolution ID

The system now mitigates the delay in applying app-level egress rules to applications.

W-18711089
## [](#june-13-2025)June 13, 2025 ### Fixed Issues
Issue Resolution ID

SFTP connectors no longer display as manageable schedulers in Runtime Manager.

W-14782361
## [](#april-25-2025)April 25, 2025 ### Fixed Issues
Issue Resolution ID

You can now revert applications from Mule runtime 4.9 to 4.4. For more information, see Known Issues.

W-17934919
## [](#april-23-2025)April 23, 2025 ### What’s New - The VPCs that were previously ineligible for upgrade to CloudHub 2.0 Private Space due to deprecated AZs are now eligible. ## [](#march-7-2025)March 7, 2025 ### Fixed Issues
Issue Resolution ID

When the client sends the Expect:100-Continue header, HTTP/1.1 Continue is now returned, followed by the response payload.

W-16954712

The precedence of validations in CloudHub 2.0 and Runtime Fabric deployments is now enforced.

W-16971170
## [](#february-4-2025)February 4, 2025 ### What’s New - You can now use the in-product VPC upgrade tool in Runtime Manager to migrate your CloudHub dedicated Virtual Private Clouds (VPCs) to CloudHub 2.0 private spaces. For more information, see [CloudHub VPC to CloudHub 2.0 Private Space Upgrade](https://docs.mulesoft.com/cloudhub/vpc-upgrade). ## [](#october-15-2024)October 15, 2024 ### Fixed Issues
Issue Resolution ID

Schedulers configured with variable properties now work as expected after editing any of their settings.

W-13974038
## [](#october-7-2024)October 7, 2024 ### What’s New - The maximum number of inbound firewall rules for CloudHub 2.0 is now 300. ## [](#september-13-2024)September 13, 2024 ### Fixed Issues
Issue Resolution ID

CloudHub 2.0 scheduler settings are now retained when redeploying an app using the Mule Maven plugin.

W-14325188
## [](#august-23-2024)August 23, 2024 ### What’s New - The maximum number of replicas per application deployed to CloudHub 2.0 is now 16 for organizations having the Anypoint Integration Advanced package or a Platinum or Titanium subscription to Anypoint Platform. ## [](#june-13-2024)June 13, 2024 ### What’s New - You can now deploy [`SNAPSHOT` version assets](https://docs.mulesoft.com/jp/exchange/to-publish-assets-maven#asset-lifecycle-state) to CloudHub 2.0 via the Mule Maven plugin. Using Exchange snapshot assets in Anypoint Exchange during the development and testing phase, you can avoid incrementing your application’s version number for small changes. After your snapshot asset is overwritten in Anypoint Exchange, you can redeploy your `SNAPSHOT` version application to CloudHub 2.0 via the Mule Maven plugin to deploy the latest changes. ## [](#june-5-2024)June 5, 2024 ### Fixed Issues
Issue Resolution ID

Access to internal endpoints from external internet is now disallowed.

W-15031444

X-Forwarded-Host headers received from the client are no longer overwritten or replaced.

W-15748883
## [](#may-16-2024)May 16, 2024 ### What’s New - You can no longer send `deploy` or `modify` deployment requests via [Application Manager API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/amc-application-manager) that have values other than `null` in the HTTP inbound configuration for the fields `pathRewrite` and `forwardSslSession` when the target is a CloudHub 2.0 Shared Space. The detailed paths to the affected fields are `target.deploymentSettings.http.inbound.pathRewrite` and `target.deploymentSettings.http.inbound.forwardSslSession`. ## [](#april-25-2024)April 25, 2024 ### What’s New - You can now schedule private space infrastructure upgrades earlier than the scheduled patching process. ## [](#march-25-2024)March 25, 2024 ### What’s New - When you create a private space, you can now specify reserved CIDR blocks to connect your cloud or on-premises corporate network without a risk of IP address overlap. ## [](#march-7-2024)March 7, 2024 ### What’s New - Customers using the new pricing and packaging model can now leverage CPU-based horizontal autoscaling on CloudHub 2.0. For more information, see [Configuring Horizontal Autoscaling (HPA) for CloudHub 2.0 Deployments](https://docs.mulesoft.com/cloudhub-2/ch2-configure-horizontal-autoscaling). ## [](#march-6-2024)March 6, 2024 ### What’s New - You can now enable trace data collection for applications using Mule Runtime 4.6 deployed to either shared or private spaces to leverage trace data export through Anypoint Monitoring [Telemetry Exporter](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter). ## [](#november-29-2023)November 29, 2023 ### What’s New - You can now opt into private-space infrastructure upgrade earlier than the scheduled patching process. - You can now configure application-level egress control rules. ## [](#september-25-2023)September 25, 2023 ### What’s New - For the 0.1 vCore offering in CloudHub 2.0, heap memory is now 480 MB. ## [](#august-25-2023)August 25, 2023 ### What’s New - When you attempt to delete a private space that has apps deployed, a warning appears, confirming you want to delete the private space and the apps that are deployed to it. If you continue to deletion, the private space and all its deployed apps are deleted. ## [](#august-18-2023)August 18, 2023 ### Fixed Issues
Issue Resolution ID

You can now use protected properties to configure a custom log appender. It requires update to the latest runtime 4.4 or 4.3 patch.

W-12756066
## [](#july-25-2023)July 25, 2023 ### What’s New - You can now configure private space inbound firewall rules to manage TCP-based traffic. You can then use the Application Manager API to [deploy apps using TCP ports](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-api). ## [](#july-7-2023)July 7, 2023 ### Fixed Issues

Issue Resolution

ID

Security fixes and infrastructure updates were added. You might experience app restarts due to infrastructure patching outside the CloudHub 2.0 monthly patching window. For more details, see CloudHub 2.0 Infrastructure Updates.

W-13643956

Long-lived connections to edge now remain up.

W-13236396
## [](#may-8-2023)May 8, 2023 ### Fixed Issues

Issue Resolution

ID

The Download Logs feature no longer truncates the downloaded file when many entries are present.

W-12756506
## [](#april-24-2023)April 24, 2023 ### What’s New - For sizing replicas, the 0.1 vCore memory offering has been increased from 1 GB to 1.2 GB. - The application size limit for uploading and deploying CloudHub 2.0 apps through the Runtime Manager UI has increased from 200 MB to 350 MB. - The number of application properties you can configure has increased from 100 to 300. You can view these properties in the **Settings** section of your application. ### Fixed Issues

Issue Resolution

ID

When you had multiple log level options selected and then unchecked a selection in the Log Levels menu, all log entries disappeared even if there were results that matched the selected filter.

W-12499456
## [](#april-20-2023)April 20, 2023 ### Fixed Issues

Issue Resolution

ID

TGW route 0.0.0.0/0 no longer shows up as "inactive" when added in a space with network isolation enabled.

W-12982406
## [](#march-28-2023)March 28, 2023 ### What’s New - CloudHub 2.0 now supports the deployment of API Gateways. ### Fixed Issues

Issue Resolution

ID

CloudHub 2.0 now supports the protection of API Gateway client ID and secret.

W-12047768
## [](#march-27-2023)March 27, 2023 ### What’s New - The limit for inbound and outbound firewall rules in a private space has increased from 40 to 180. - The limit for HTTP header length (`maxHeaderLength`) has increased from 16K to 32K. ### Fixed Issues

Issue Resolution

ID

Traffic within a VPC now allows networking components to function in all private spaces.

W-12471336

When you add or update inbound or outbound firewall rules, you can now specify local-private-network as the CIDR block in an API. You are no longer forced to add the individual CIDRs that are required to enable traffic within a private network.

W-12060691
## [](#march-23-2023)March 23, 2023 ### Fixed Issues

Issue Resolution

ID

Application logs are now visible in Anypoint Monitoring when third-party appenders are enabled in the application Log4j2 configuration.

W-12716627
## [](#march-8-2023)March 8, 2023 ### What’s New - You can now enable VPN logs to be directly accessible by MuleSoft support engineers. This shortens the process for obtaining the logs from AWS. For more information, see [Enable VPN Logs](https://docs.mulesoft.com/cloudhub-2/ps-manage#enable-vpn-logs). - When you configure a new private space, you can now remove the default route from the routing table. ### Fixed Issues

Issue Resolution

ID

Creating a redundant VPN now works correctly.

W-12555193
## [](#march-6-2023)March 6, 2023 ### What’s New - Limits for vCores, VPCs, and networking connections across CloudHub and CloudHub 2.0 are now enforced at the organization level. Running applications are not impacted, but you must keep your applications in compliance to ensure all operations run smoothly. For more information, see [Organization Entitlements](https://docs.mulesoft.com/cloudhub-2/ps-gather-setup-info#organization-limits). ## [](#february-2-2023)February 2, 2023 ### What’s New - You can now use queries to search application logs in Runtime Manager. ## [](#january-31-2023)January 31, 2023 ### Fixed Issues

Issue Resolution

ID

The validation when creating multiple VPN connections in a private space now prevents you from specifying different local ASNs, which could result in creating new VPN gateways and VPN connections.

W-12362854
## [](#january-17-2023)January 17, 2023 ### What’s New - The **Create VPN Connection** > **Advanced Options** UI has changed. When you select custom tunnel configuration, you must provide values for all four fields: - **Inside IP CIDRs** - **Tunnel 1** - **Tunnel 2** - **Pre-Shared Keys** - **Tunnel 1** - **Tunnel 2** Previously, these settings were optional. ### Fixed Issues
Issue Resolution ID

Selecting a custom CIDR for a firewall rule now works correctly.

W-12165021

The VPN configuration UI now validates tunnel settings.

W-12077102

You can now delete internal DNS servers from Private Spaces > Private network.

W-12076991
## [](#january-12-2023)January 12, 2023 ### Fixed Issues
Issue Resolution ID

Detaching a transit gateway previously attached to multiple private spaces now works correctly.

If you are unable to detach an existing transit gateway, remove it from your Anypoint Platform organization, and then recreate and attach it to a private space. For information about removing the transit gateway from Anypoint Platform, see the CloudHub 2.0 API on Exchange. For information about recreating the transit gateway attachment, see Creating Transit Gateway Attachments.

W-12212180
## [](#october-31-2022)October 31, 2022 ### What’s New - The Log Points and Reports features in Anypoint Monitoring are now supported for CloudHub 2.0. ### Fixed Issues

Issue Resolution

ID

Fixed an issue that prevented you from searching logs using event IDs.

W-11644799

Fixed an issue related to cron-based schedulers. You can now set the timezone in the user interface.

W-11389859
## [](#october-12-2022)October 12, 2022 ### Fixed Issues

Issue Resolution

ID

Fixed an issue that raised an AlreadyExists error when you tried to assign the same VPN to more than one private space.

W-11846052
## [](#october-6-2022)October 6, 2022 ### What’s New - Application endpoints now support path rewrite. The Path Rewrite feature is available only for apps deployed in private spaces. ## [](#august-16-2022)August 16, 2022 MuleSoft announces the release of CloudHub 2.0. CloudHub 2.0 is a fully managed, containerized integration platform as a service (iPaaS) where you can deploy APIs and integrations as lightweight containers in the cloud. Using CloudHub 2.0, you can: - Get started fast Set up an environment quickly with simplified configuration for private spaces and network connectivity. - Streamline your operations Reduce management overhead with new auto-provisioning and auto-scaling ingress and load balancer in private spaces. - Take advantage of lightweight isolation Improve performance and scale quickly with lightweight container-based application isolation. - Implement tighter security controls Simplify static IP management and customize outbound firewall rules at the private space level. - Meet present and future needs, faster Take advantage of new products and features faster to accelerate growth and innovation. To learn more about CloudHub 2.0, see the [CloudHub 2.0 overview](https://docs.mulesoft.com/cloudhub-2/). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub 2.0 Release Notes - [CloudHub 2.0 Feature Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes) - [CloudHub 2.0 Runtime Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes) - [Anypoint VPN Updates Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/anypoint-vpn-release-notes) ## [](#see-also)See Also - [CloudHub 2.0 Documentation](https://docs.mulesoft.com/cloudhub-2/) - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub 2.0 Runtime and Infrastructure Patch Update Release Notes These release notes describe monthly date-patch updates to Mule runtime engine and security updates to the underlying operating system for CloudHub 2.0. During upgrades, a Mule application might be restarted onto a new secure host. If the Mule worker is not running with multiple replicas or is using the Recreate deployment model, it experiences slight downtime. For more information, see the [Infrastructure Updates](https://docs.mulesoft.com/cloudhub-2/ch2-patch-updates#cloudhub-2-0-infrastructure-updates) documentation. In addition to these release notes, see: - [CloudHub 2.0 Product Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes) - [CloudHub 2.0 Documentation](https://docs.mulesoft.com/cloudhub-2/) - [CloudHub 2.0 Operating System Patch Updates](https://docs.mulesoft.com/cloudhub-2/ch2-patch-updates)
The monthly patching updates for CloudHub 2.0 started in January, 2023.
CloudHub 2.0 receives monthly OS security and Mule runtime patch updates. MuleSoft Composer (Composer) and MuleSoft Robotic Process Automation (RPA) run on CloudHub 2.0 infrastructure and receive the same monthly OS security and runtime patches. Patching for these spaces occur during the sandbox patching weekday window specified for the monthly maintenance. During this period, flows are rescheduled onto the updated infrastructure. ## [](#mulesoft-commercial-cloud-schedule)MuleSoft Commercial Cloud Schedule This table shows the current schedule for monthly updates. These dates are subject to change.
Month Release Available Sandbox Environment Auto-Update Production Environment Auto-Update

December

December 1

December 15-19

December 20-21

November

November 3

Self-upgrade only***

Self-upgrade only***

October

October 6**

October 19-23

October 24-25

September

September 4*

September 21-25

September 26-27
The release notes for an update are published in the same week in which the runtime patch is released for all Mule versions on CloudHub 2.0.
** The October 2026 infrastructure monthly patch release was rescheduled from October 6 to October 9. All subsequent update windows remain unchanged.
*** During the November 2026 cycle, CloudHub 2.0 offers only self-upgrades. Automated sandbox and production patching activities are paused. To receive the latest patches, manually upgrade your applications.
* The September 2026 monthly patch release is rescheduled from September 8 to September 4. All subsequent update windows remain unchanged.
Using a runtime version that is more than three months old can introduce security vulnerabilities. If your application doesn’t update automatically within two monthly patching cycles, CloudHub stops the application and force-updates the application to the latest patch version. If an application doesn’t automatically start after the forced patch update, make sure the patch is applied and start the application. For more information, see Failed Automated Updates.
CloudHub doesn’t auto-upgrade apps when the target Mule runtime version introduces incompatibilities with the application configuration, such as TLS or Java version changes. For example, apps that use TLS 1.1 in Mule 4.9 aren’t auto-upgraded to Mule 4.10 because Mule 4.10 doesn’t support TLS 1.1. Similarly, apps aren’t auto-upgraded across incompatible Java versions.
## [](#cloudhub-2-0-release-monthly-cadence)CloudHub 2.0 Release Monthly Cadence This table shows the current schedule for monthly updates. Updates are packaged as `--`
Monthly updates 4.13 Edge Patch 4.12 Edge Patch 4.11 Edge Patch 4.9 LTS Patch 4.9 Edge Patch (EOL) 4.6 LTS Patch 4.6 Edge Patch (EOL) 4.4 Patch (EOL) 4.3 Patch (EOL)

October 2026

-

-

-

-

-

September 2026

-

4.12.3:4e

-

4.9.21:4

-

4.6.34:6

-

-

-

August 2026

-

4.12.2:8e

4.11.6:7e

4.9.20:9

-

4.6.33:9

-

-

-

July 2026

-

4.12.1:4e

4.11.6:4e

-

-

-

-

June 2026

-

4.12.0:10e

4.11.5:4e

4.9.18:3

-

4.6.30:5

-

-

-

May 2026

-

-

4.11.4:4e

-

-

-

-

April 2026

-

-

4.11.3:4e

4.9.16:4

-

4.6.29:6

-

-

-

March 2026

-

-

4.11.2:3e

4.9.15:3

-

4.6.28:3

-

-

-

February 2026

-

-

-

-

-

January 2026

-

-

-

4.9.12:5

4.9.12:5e

4.6.25:5

-

-

-

December 2025

-

-

-

-

-

-

-

-

-

November 2025

-

-

-

-

-

October 2025

-

-

-

4.9.10:4

4.9.10:4e

4.6.23:4

-

4.4.0:20250919-3

-

September 2025

-

-

-

4.9.9:5

4.9.9:5e

4.6-22:4

-

4.4.0:20250829-1

-
- EOSS (End of Standard Support) - EOES (End of Extended Support) - EOL (End of Life) ## [](#october-15-2026)October 15, 2026 ### What’s New **4.13.1, 4.12.5, 4.9.23, and 4.6.36 Runtime Updates** This update addresses regressions introduced in the October release. **Runtime Manager agent versions included in Runtime 4.13.1, 4.12.5, 4.9.23, and 4.6.36** This release of 4.13.1, 4.12.5, and 4.9.23 includes Runtime Manager agent 2.8.5, and 4.6.36 includes Runtime Manager agent 2.7.20. For information, see [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) and [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20). ### Fixed Issues **4.13.1 Runtime Updates** For Mule runtime 4.13.1, the image name that corresponds with this update is 4.13.1:2e.
Issue Resolution ID

Mule

Applications no longer fail to deploy when the type of an on-error-propagate or on-error-continue is a property placeholder and the flow contains a component that supports streaming and requires a connection, such as an HTTP Request or Kafka operation.

W-24456406

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

Polling sources that use a CloudHub Object Store v2 for watermarks now track processed items in the object store’s configured partition instead of the default partition.

W-24459240

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
**4.12.5 Runtime Updates** For Mule runtime 4.12.5, the image name that corresponds with this update is 4.12.5:2e.
Issue Resolution ID

Mule

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
**4.9.23 Runtime Updates** For Mule runtime 4.9.23, the image name that corresponds with this update is 4.9.23:4.
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
**4.6.36 Runtime Updates** For Mule runtime 4.6.36, the image names that corresponds with this update is 4.6.36:2.
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
## [](#october-6-2026)October 6, 2026 ### What’s New - Mule runtime engine 4.13.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **4.13.0, 4.12.4, 4.9.22, and 4.6.35 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.13.0, 4.12.4, 4.9.22, and 4.6.35** This release of 4.13.0, 4.12.4, and 4.9.22 includes Runtime Manager agent 2.8.5, and 4.6.35 includes Runtime Manager agent 2.7.20. For information, see [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) and [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20). **Composer, RPA, and MDS Spaces** Composer, RPA, and MDS spaces are patched during the sandbox patching weekday window specified for the monthly maintenance. ### Fixed Issues **4.13.0 Runtime Updates** For Mule runtime 4.13.0 Edge, the image name that corresponds with this update is 4.13.0:16e.
Issue Resolution ID

Mule

The jsoup library is upgraded to 1.23.2.

W-23987955

The Jackson library is upgraded to 2.22.3.

W-24335732

The Reactor Core library is upgraded to 3.8.7.

W-23987958

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

The raml-parser-2 library is upgraded to 1.2.1.

W-23570110

Error-mapping preservation during error propagation is now enabled by default. An error whose type was already resolved inside a scope, including any remapping by an error mapping, now keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type. You can disable this behavior by setting the mule.honourErrorMappingsOnErrorPropagation system property to false.

W-23955755

OpenTelemetry metric exporters now support per-exporter view enrichment and resource attribute overrides.

W-23367495

JSON schema validation is migrated from the everit library to networknt, with everit retained as a fallback.

W-16530105

HTTP header values containing CR/LF characters are now sanitized instead of causing the request to be rejected.

W-22252135

minMuleVersion values are now normalized when loaded, preventing the patch or revision portion from being truncated.

W-24231362

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

Logging export reconfiguration is fixed for single application mode.

W-20908857

The ObjectStore API is extended with an upsert operation and an isThreadSafe indicator.

W-23090592

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809

A java.lang.UnsupportedClassVersionError thrown when a connector’s compiled target doesn’t match the running JVM is now handled gracefully.

W-24193358

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

A source policy that uses Async, Parallel For Each, or Scatter-Gather no longer builds its response from the failure response parameters instead of the success response parameters, and no longer silently drops the forked route’s response processing.

W-23938349

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

The commons-beanutils library and its transitive commons-collections 3.2.2 dependency are removed from Mule Runtime modules.

W-16918287

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

An unresolved placeholder in the meter-exporter configuration now degrades to its default value at tracer startup instead of causing a failure.

W-23650358

Dynamic reload of the metrics exporter configuration is now supported.

W-21921629

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

OutputHandler is deprecated and its support is removed.

W-23660888

A SerializationException now raises a MULE:SERIALIZATION error, instead of MULE:UNKNOWN.

W-21381359

The exporter-health backpressure-alert cadence for OpenTelemetry tracing, metrics, and logging is now configured through a single system property, mule.openTelemetry.meter.exporter.healthMetrics.alertingFrequency, instead of the separate per-signal metricsLogFrequency properties, which are deprecated and no longer consumed.

W-22193713

MULE:INVALID_INPUT_PARAM is now preserved as a suppressed error when a MULE:SOURCE_RESPONSE_GENERATE error occurs.

W-22293407

SDK parameter validation errors are now mapped to the MULE:INVALID_INPUT_PARAM error type.

W-2227652

Mule-generated tracing spans no longer truncate attribute values at OpenTelemetry’s default 128-character limit. Attribute values are now preserved up to 4096 characters before truncation.

W-20091299

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

SQSQueueManagementService is added to the serialization allowlist.

W-24197744

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401

DataWeave

Memory usage for text/plain output is reduced.

W-20063270

Eagerly materialize executable Weave reader results.

W-23837275

Thread safety is improved when processing Java map values.

W-23661641

DataWeave tooling now reports design-time warnings when Java classes referenced in application/java schemas can’t be found or are inaccessible through JPMS.

W-22797049

DataWeave now filters Java classes in JPMS-unexported packages during Java module resolution, preventing runtime IllegalAccessException failures. This behavior is enabled by default on JDK 17 and later with DataWeave language version 2.13 and later. To keep the previous behavior, set mule.dw.filter_jpms_inaccessible_modules=false.

W-22779527

Cryptographic security warnings and errors now include call stacks.

W-22144340
**4.12.4 Runtime Updates** For Mule runtime 4.12.4 Edge, the image name that corresponds with this update is 4.12.4:9e.
Issue Resolution ID

Mule

The Log4j library is upgraded to 2.26.1.

W-24061648

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

Network information listening ports are now scoped to the Mule process.

W-24043880

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

On CloudHub 2.0 and Runtime Fabric deployments, container logs exported through OpenTelemetry now correctly use the deployed application’s configured service name, instead of the generic mule-container name.

W-23734353

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809
**4.9.22 Runtime Updates** For Mule runtime 4.9.22 LTS, the image name that corresponds with this update is 4.9.22:8.
Issue Resolution ID

Mule

The Reactor Core library is upgraded to 3.8.7.

W-23953702

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
**4.6.35 Runtime Updates** For Mule runtime 4.6.35 LTS, the image name that corresponds with this update is 4.6.35:4.
Issue Resolution ID

Mule

The Reactor Core library is upgraded to 3.8.7.

W-3300013

The Jackson library is upgraded to 2.22.2.

W-23947149

The jsoup library is upgraded to 1.23.2.

W-23987949

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

An SDK API for queues (VM usage) and core adapters is added.

W-19439432

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. To change the behavior, configure the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
## [](#september-4-2026)September 4, 2026 ### What’s New **4.12.3, 4.9.21, and 4.6.34 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.12.3, 4.9.21, and 4.6.34** This release of 4.12.3 and 4.9.21 includes Runtime Manager agent 2.8.4, and 4.6.34 includes Runtime Manager agent 2.7.16. For information, see [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4) and [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). **Composer, RPA, and MDS Spaces** Composer, RPA, and MDS spaces are patched during the sandbox patching weekday window specified for the monthly maintenance. ### Fixed Issues **4.12.3 Runtime Updates** For Mule runtime 4.12.3 Edge, the image name that corresponds with this update is 4.12.3:4e.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23671475

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

DataWeave

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
**4.9.21 Runtime Updates** For Mule runtime 4.9.21 LTS, the image name that corresponds with this update is 4.9.21:4.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

The HTTP client configurer now includes a method to control whether sensitive headers are filtered when a request is redirected to a different domain.

W-21045658

A forward-proxy client no longer sends a malformed, path-only request line.

W-23384645

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540341

The RAML Parser library is upgraded to 2-1.2.1.

W-23328348

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

DataWeave

Vulnerable dependencies are upgraded to address reported security vulnerabilities.

W-23924223

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
**4.6.34 Runtime Updates** For Mule runtime 4.6.34 LTS, the image name that corresponds with this update is 4.6.34:6.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Apache Commons Compress library is upgraded to 1.26.0.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540335

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

DataWeave

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
## [](#august-12-2026)August 12, 2026 ### What’s New **4.12.2, 4.11.6, 4.9.20, and 4.6.33 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.12.2, 4.11.6, 4.9.20, and 4.6.33** This release of 4.12.2, 4.11.6, and 4.9.20 includes Runtime Manager agent 2.8.3, and 4.6.33 includes Runtime Manager agent 2.7.18. For information, see [Runtime Manager Agent 2.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-3) and [Runtime Manager Agent 2.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-18). **Composer, RPA, and MDS Spaces** Composer, RPA, and MDS spaces are patched during the sandbox patching weekday window specified for the monthly maintenance. ### Fixed Issues **4.12.2 Runtime Updates** For Mule runtime 4.12.2 Edge, the image name that corresponds with these fixes is 4.12.2:8e.
Issue Resolution ID

Mule

Lazy initialization no longer fails with a NullPointerException when an application using the VM connector’s publish operation also configures a global error handler.

W-23156632

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

An HTTP request client connecting through a proxy no longer hangs when the proxy responds with a 407 (Proxy Authentication Required) response during the CONNECT tunnel handshake.

W-23384719

The HTTP request client now sends a correctly formed request line when connecting through a forward proxy.

W-23384645

A NullPointerException no longer occurs when the HTTP request client reuses a pooled connection to a forward proxy.

W-23384744

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Batch module now provides a public API to configure a custom queue manager and queue timeout.

W-23371797

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Sec-WebSocket-Protocol header is now forwarded on outbound WebSocket connections, so subprotocol negotiation with the server succeeds.

W-23071781

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API Gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23165634

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

Type metadata processing now correctly handles sibling references that target the same type, preventing duplicate annotations.

W-23424037

DataWeave now handles Java Platform Module System (JPMS) access restrictions more gracefully when running on Java 17 and later in Mule runtime 4.6.0 and later.

W-23354139

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
**4.11.6 Runtime Updates** For Mule runtime 4.11.6 Edge, the image name that corresponds with these fixes is 4.11.6:7e. - Updated to the latest operating system security patches. **4.9.20 Runtime Updates** For Mule runtime 4.9.20 LTS, the image name that corresponds with these fixes is 4.9.20:9.
Issue Resolution ID

Mule

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23131090

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
**4.6.33 Runtime Updates** For Mule runtime 4.6.33 LTS, the image name that corresponds with these fixes is 4.6.33:9.
Issue Resolution ID

Mule

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23121654

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592
## [](#july-14-2026)July 14, 2026 The July 14 patch update 4.9.19:9 and 4.6.32:5 addresses an issue in the previous July 7 patch update and includes the fixes in those patches. ### Fixed Issues **4.9.19 Runtime Updates** For Mule runtime 4.9.19 LTS, the image name that corresponds with these fixes is 4.9.19:9.
Issue Resolution ID

The runtime no longer logs this warning:

Cannot start plugin 'rtf-cluster-server-plugin'. Plugin will be unregistered
java.lang.reflect.UndeclaredThrowableException

W-23373633
**4.6.32 Runtime Updates** For Mule runtime 4.6.32 LTS, the image name that corresponds with these fixes is 4.6.32:5.
Issue Resolution ID

The runtime no longer logs this warning:

Cannot start plugin 'rtf-cluster-server-plugin'. Plugin will be unregistered
java.lang.reflect.UndeclaredThrowableException

W-23373633
## [](#july-7-2026)July 7, 2026 ### What’s New **4.12.1, 4.11.6, 4.9.19, and 4.6.32 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.12.1, 4.11.6, 4.9.19, and 4.6.32** This release of 4.12.1, 4.11.6, 4.9.19, and 4.6.32 includes Runtime Manager Agent 2.7.16. For information, see [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). **Composer, RPA, and MDS Spaces** Composer, RPA, and MDS spaces are patched during the sandbox patching weekday window specified for the monthly maintenance. ### Fixed Issues **4.12.1 Runtime Updates** For Mule runtime 4.12.1 Edge, the image name that corresponds with these fixes is 4.12.1:4e.
Issue Resolution ID

Mule

Clustered applications deployed with two or more replicas no longer fail to start with a NullPointerException error during cluster node discovery.

W-22843942

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Object Store retrieved from the registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

The error type in the EE cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Test Connection for the HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the host field.

W-21921687

HTTP Server now supports upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

In-memory Object Store partitions are now created correctly when an application is deployed to a cluster with the Object Store plugin enabled.

W-17714668

Deserialization errors no longer occur in the Object Store during a runtime patch upgrade.

W-20880559

Applications deployed with a serialized AST now include all Mule error types in the error type repository.

W-22399271

Applications that use HTTP request attributes no longer fail annotation processing due to default constructor validation.

W-22385620

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

OpenTelemetry flow statistics now report metrics correctly for applications with more than one flow.

W-23051614

The artifact type (domain, policy, or application) is now included as an OpenTelemetry resource attribute.

W-21768636

OpenTelemetry metric attribute names now use a consistent notation.

W-21921584

The mule.openTelemetry.logging.exporter.resource.container.service.name system property is now available to set the service name that the Mule container reports for OpenTelemetry telemetry.

W-22861497

Event dumps now include a state for events that are waiting on a non-blocking operation.

W-22142952

The Netty library is upgraded to 4.2.15.Final.

W-22831076

The c3p0 library is upgraded to 0.14.1.

W-22990155

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The Reactor Netty library is upgraded to 1.3.6.

W-3300013

The Jackson Core library is upgraded to 2.21.1.

W-22839747

The Apache Neethi library is upgraded to 3.2.1.

W-22839752

The OpenTelemetry API library is upgraded to 1.62.0.

W-22849469

The Spring Framework is upgraded to 6.2.19.

W-22939417

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344
**4.11.6 Runtime Updates** For Mule runtime 4.11.6 Edge, the image name that corresponds with these fixes is 4.11.6:4e.
Issue Resolution ID

Mule

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The c3p0 library is upgraded to 0.14.1.

W-22990152

The Spring Framework is upgraded to 6.2.19.

W-3300013

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806044

The Netty library is upgraded to 4.2.15.Final.

W-22888966

The Reactor Netty library is upgraded to 1.3.6.

W-22939412

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
**4.9.19 Runtime Updates** For Mule runtime 4.9.19 LTS, the image name that corresponds with these fixes is 4.9.19:8.
Issue Resolution ID

Mule

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

The Content-Length header is now removed based on the actual entity byte length.

W-22570070

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

The Jackson Databind library is upgraded to 2.21.4.

W-3300013

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806027

The c3p0 library is upgraded to 0.14.1.

W-23012713

The Apache Neethi library is upgraded to 3.2.1.

W-22939389

The Apache CXF library is upgraded to 3.6.11.

W-23037617

The Rhino library is upgraded to 1.8.1.

W-22939391

The Log4j library is upgraded to 2.25.4.

W-22939403

The Reactor Netty library is upgraded to 1.2.18.

W-22939384

The Spring Framework is upgraded to 6.2.19.

W-22956997

The Netty library is upgraded to 4.2.15.Final.

W-22956998

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
**4.6.32 Runtime Updates** For Mule runtime 4.6.32 LTS, the image name that corresponds with these fixes is 4.6.32:4.
Issue Resolution ID

Mule

A NullPointerException error no longer occurs in event context handling when a flow times out while a non-blocking operation is still in flight.

W-22902839

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The Joda-Time library is upgraded to 2.13.0.

W-3300013

The Rhino library is upgraded to 1.7.15.1.

W-22805996

The Apache Neethi library is upgraded to 3.2.1.

W-22805997

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806011

The Apache CXF library is upgraded to 3.5.11.

W-23037585

The c3p0 library is upgraded to 0.14.1.

W-23012711

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

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 per_app_java_bean_cache compatibility flag.

W-22417507
## [](#june-8-2026)June 8, 2026 ### What’s New - Mule runtime engine 4.12.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **4.12.0, 4.11.5, 4.9.18, and 4.6.31 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.12.0, 4.11.5, 4.9.18, and 4.6.31** This release of 4.12.0, 4.11.5, 4.9.18, and 4.6.31 includes Runtime Manager Agent 2.7.15. For information, see [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15). **Composer and RPA Spaces** Composer and RPA spaces are patched during this cycle. Flows are rescheduled onto the updated infrastructure. ### Fixed Issues **4.12.0 Runtime Updates** For Mule runtime 4.12.0 Edge, the image name that corresponds with these fixes is 4.12.0:10e.
Issue Resolution ID

Mule

Upstream HTTP requests are now cancelled when a downstream client disconnects, preventing unnecessary data transfer.

W-20084343

The Netty HTTP client no longer throws NullPointerException when handling Expect 100-Continue responses.

W-21513490

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

The Apache CXF library is upgraded to 3.6.8.

W-20541600

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

Redelivery policy logging now includes additional context for troubleshooting.

W-20636028

The Tanuki Java Service Wrapper is upgraded to 3.6.4.

W-17051070

The RAML parser is upgraded to 1.1.10.

W-21768014

The OpenTelemetry SDK is upgraded to 1.60.1.

W-21808539

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

DataWeave now supports the private modifier on fun, var, ns, and type declarations to hide them from importers.

W-21148967

internal is no longer a reserved word and can now be used as an identifier in DataWeave scripts.

W-21508044

The compiler now reports an error when overloads of the same function declare different visibility modifiers.

W-21362539

StackOverflowError no longer occurs in the type checker when resolving intersections of unbound type parameters.

W-20124753

Runtime errors no longer occur when invoking overloaded functions across modules.

W-21811015

Spurious type-check errors no longer occur when an optional key-value pair is assigned to a required one.

W-21351058

deferred values passed to the write function now terminate correctly.

W-20925604

Out-of-memory errors no longer occur when reading large text or CDATA sections with the indexed XML reader.

W-21006104

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
**4.11.5 Runtime Updates** For Mule runtime 4.11.5 Edge, the image name that corresponds with these fixes is 4.11.5:4e.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

HTTP Server now supports Upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Test Connection for The HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the Host field.

W-21921687

The Spring Core library is upgraded to 6.2.18.

W-22169898

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
**4.9.18 Runtime Updates** For Mule runtime 4.9.18 LTS, the image name that corresponds with these fixes is 4.9.18:3.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507
**4.6.31 Runtime Updates** For Mule runtime 4.6.31 LTS, the image name that corresponds with these fixes is 4.6.31:3.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

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 per_app_java_bean_cache compatibility flag.

W-22417507
## [](#may-19-2026)May 19, 2026 The May 19 patch update (versions 4.9.17:5 and 4.6.30:5) addresses a regression introduced in the May 5 update (versions 4.9.17:4 and 4.6.30:4) and includes all associated fixes. ### Fixed Issues **4.9.17 Runtime Updates** For Mule runtime 4.9.17, the image name that corresponds with these fixes is 4.9.17:5.
Issue Resolution ID

Incoming header names no longer use strict CRLF validation when an HTTP configuration without a listener receives an HTTPS request, avoiding out-of-memory errors. In this scenario, Mule logs a warning entry in mule_ee.log, but the warning doesn’t affect application behavior.

W-22571733
**4.6.30 Runtime Updates** For Mule runtime 4.6.30, the image name that corresponds with these fixes is 4.6.30:5.
Issue Resolution ID

Incoming header names no longer use strict CRLF validation when an HTTP configuration without a listener receives an HTTPS request, avoiding out-of-memory errors. In this scenario, Mule logs a warning entry in mule_ee.log, but the warning doesn’t affect application behavior.

W-22571733
## [](#may-5-2026)May 5, 2026 ### What’s New **4.6, 4.9, and 4.11 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.30, 4.9.17, and 4.11.4** This release of 4.6.30, 4.9.17, and 4.11.4 includes Runtime Manager Agent 2.7.13. For information, see [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13). **Composer and RPA Spaces** Composer and RPA spaces are patched during this cycle. Flows are rescheduled onto the updated infrastructure. ### Fixed Issues **4.11.4 Runtime Updates** For Mule runtime 4.11.4 Edge, the image name that corresponds with these fixes is 4.11.4:4e.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

Netty HTTP client NTLM authentication no longer fails due to missing TCP connection affinity during the handshake.

W-21615520

The plexus-utils library is upgraded to 4.0.3.

W-21774430

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21913252

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

Netty HTTP client no longer sends an incorrect WWW-Authenticate header during the NTLM authentication handshake.

W-21762949

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

A serialization error that could occur when deserializing data after a Mule runtime upgrade no longer occurs.

W-21951097

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
**4.9.17 Runtime Updates** For Mule runtime 4.9.17 LTS, the image name that corresponds with these fixes is 4.9.17:4.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21795152

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
**4.6.30 Runtime Updates** For Mule runtime 4.6.30 LTS, the image name that corresponds with these fixes is 4.6.30:4.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
## [](#april-7-2026)April 7, 2026 ### What’s New **4.6, 4.9, and 4.11 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.29, 4.9.16, and 4.11.3** This release of 4.6.29, 4.9.16, and 4.11.3 includes Runtime Manager Agent 2.7.11. For information, see [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11). **Composer and RPA Spaces** Composer and RPA spaces are patched during this cycle. Flows are rescheduled onto the updated infrastructure. ### Fixed Issues **4.11.3 Runtime Updates** For Mule runtime 4.11.3 Edge, the image name that corresponds with these fixes is 4.11.3:4e.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

OpenTelemetry Direct streaming now supports FIPS-compatible keystore format.

W-20623905

A warning now appears when an OpenTelemetry property is incorrectly used as a deployment property.

W-21018072

NullPointerException 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.

W-20192960

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

HTTP Netty implementation performance is now improved.

W-20969515

HTTP Server no longer logs an error when a client closes an idle keep-alive connection.

W-21431822

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
**4.9.16 Runtime Updates** For Mule runtime 4.9.16 LTS, the image name that corresponds with these fixes is 4.9.16:4.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

The Jackson Core library is upgraded to 2.18.6.

W-21420104

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
**4.6.29 Runtime Updates** For Mule runtime 4.6.29 LTS, the image name that corresponds with these fixes is 4.6.29:6.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
## [](#march-3-2026)March 3, 2026 ### What’s New **4.6, 4.9, 4.10, and 4.11 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.28, 4.9.15, 4.10.5, and 4.11.2** This release of 4.6.28, 4.9.15, 4.10.5, and 4.11.2 includes Runtime Manager Agent 2.7.10. For information, see [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10). **Composer and RPA Spaces** Composer and RPA spaces are patched during this cycle. Flows are rescheduled onto the updated infrastructure. ### Fixed Issues **4.11.2 Runtime Updates** For Mule runtime 4.11.2 Edge, the image name that corresponds with these fixes is 4.11.2:3e.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

XSD validations are now enabled by default during deployment.

W-21139633

Errors that are not MessagingException errors are no longer silenced.

W-21043969

The reactor.netty.version library is upgraded to 1.3.2.

W-3300013

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501

The Mapping Editor API now supports attributes in Anypoint Code Builder.

W-20662336

Updating the expression model in the Mapping Editor API now works correctly.

W-20611263
**4.10.5 Runtime Updates** For Mule runtime 4.10.5 Edge, the image name that corresponds with this fix is 4.10.5:2e.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

Streaming manager initialization failures no longer occur in certain scenarios.

W-20641469

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
**4.9.15 Runtime Updates** For Mule runtime 4.9.15 LTS, the image name that corresponds with these fixes is 4.9.15:3.
Issue Resolution ID

Mule

The jakarta.mail library is upgraded to 1.6.8.

W-21138257

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

Errors that are not MessagingException errors are no longer silenced.

W-21043969

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." errors no longer occur when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
**4.6.28 Runtime Updates** For Mule runtime 4.6.28 LTS, the image name that corresponds with these fixes is 4.6.28:3.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The tika-core library is upgraded to 3.2.3.

W-21179465

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
## [](#february-14-2026)February 14, 2026 ### Fixed Issues **4.11.1 Edge Runtime Updates** For Mule runtime 4.11.1 Edge, the image name that corresponds with these fixes is 4.11.1:2e. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. **4.10.4 Edge Runtime Updates** For Mule runtime 4.10.4 Edge, the image name that corresponds with these fixes is 4.10.4:1e. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. **4.9.14 Edge Runtime Updates** For Mule runtime 4.9.14 Edge, the image name that corresponds with these fixes is 4.9.14:1e. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. **4.9.14 LTS Runtime Updates** For Mule runtime 4.9.14 LTS, the image name that corresponds with these fixes is 4.9.14:1. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. **4.6.27 LTS Runtime Updates** For Mule runtime 4.6.27 LTS, the image name that corresponds with these fixes is 4.6.27:1. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ## [](#february-4-2026)February 4, 2026 ### What’s New - Mule runtime engine 4.11.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **Runtime Manager Agent versions included in Runtime 4.11.0** This release of 4.11.0 includes Runtime Manager Agent 2.7.9. For information, see [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues **4.11.0 Runtime Updates** For Mule runtime 4.11.0 Edge, the image name that corresponds with these fixes is 4.11.0:10e.
Issue Resolution ID

Mule

HTTP/2 connections now correctly multiplex when processing concurrent requests, reducing connection creation and latency.

W-19860076

The runtime now leverages the AST file for applications with the until-successful component instead of parsing configuration XML files.

W-20283146

Batch record deserialization no longer fails when a Netty exception occurs.

W-20552358

Inbound HTTP/2 header validation is now improved.

W-19873453

The org.apache.logging.log4j:log4j-core dependency is upgraded to 2.25.3.

W-20679050

DataWeave

AST scope navigation now works correctly for cross-file references when using the Tooling API.

W-20212809

A specific overload for isEmpty on binaries is now available to prevent implicit coercion to other types.

W-20049958

Materialized Java values are now cached to allow multiple executions using the same value.

W-20091279

Semantic tokens are now supported in the Tooling API.

W-19846990

NullPointerException no longer occurs when handling annotation types.

W-19853000

LogLevel documentation is now included directly in the code.

W-17800393

The commons-beanutils library is upgraded.

W-3300013

Base64 encoding and decoding now support payloads larger than memory.

W-18575719

Eager materialization is now supported on values, enabling caching of all exceptions inside the try function.

W-19717874

Avro enum, map, union, and fixed types are now supported as top-level elements.

W-19596039

WeaveCompiler now allows precompiling mappings and modules without validation or type checking.

W-19667273

Type check errors are now correctly reported when resolving type checking on subgraphs.

W-19564697

Lazy loading of source files is now enabled during binary compilation, avoiding unnecessary memory usage.

W-19594703

Type inference now works correctly when using the -- operator to subtract a key from an object.

W-19595907

Warning and error messages now propagate correctly between compilation phases.

W-19386849

Base types are now used to validate accepted values, preventing premature materialization.

W-18943395

Optional types now propagate correctly through chains of value selectors.

W-19272070

The syntax version is now added to TypeGraph and WeaveTypeResolution.

W-19271992

The classloader resource resolver now resolves paths correctly on Windows systems.

W-19407283
## [](#february-3-2026)February 3, 2026 ### What’s New **4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.26, 4.9.13, and 4.10.3** This release of 4.6.26, 4.9.13, and 4.10.3 includes Runtime Manager Agent 2.7.9. For information, see [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues **4.10.3 Runtime Updates** For Mule runtime 4.10.3 Edge, the image name that corresponds with this fix is 4.10.3:2e.
Issue Resolution ID

Mule

HTTP/2 handling now correctly multiplexes connections during concurrent request processing. Previously, a failure to multiplex caused excessive connection creation and significantly increased latency.

W-19860076

Improved the validation logic for inbound HTTP/2 headers to ensure better protocol compliance and security.

W-19873453

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

The org.apache.cxf:cxf-core library is upgraded to 3.6.9.

W-20659822

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

Applications no longer experience infinite restart loops when CloudHub log files contain corrupted records.

W-20396002

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
**4.9.13 Runtime Updates** For Mule runtime 4.9.13 Edge, the image name that corresponds with these fixes is 4.9.13:2e.
Issue Resolution ID

Mule

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

Fastutil is now replaced with fastutil-core.

W-20729870

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
For Mule runtime 4.9.13 LTS, the image name that corresponds with these fixes is 4.9.13:2.
Issue Resolution ID

Mule

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

Fastutil is now replaced with fastutil-core.

W-20729870

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
**4.6.26 Runtime Updates** For Mule runtime 4.6.26 LTS, the image name that corresponds with these fixes is 4.6.26:2.
Issue Resolution ID

Mule

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Fastutil is now replaced with fastutil-core.

W-20729870
## [](#january-6-2026)January 6, 2026 ### What’s New **4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.25, 4.9.12, and 4.10.2** This release of 4.6.25, 4.9.12, and 4.10.2 includes Runtime Manager Agent 2.7.9. For information, see [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues **4.10.2 Runtime Updates** For Mule runtime 4.10.2 Edge, the image name that corresponds with these fixes is 4.10.2:5e.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing not longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

A memory leak after application undeployment no longer occurs when using connections from configurations defined in a domain.

W-13521171

Connections now close properly on the server side after an HTTP/2 client disconnects.

W-19861068

The JMS connector no longer closes XA-enlisted connections.

W-20266983

Connections from providers that implement both CachedConnectionProvider and XaTransactionalConnectionProvider are no longer cached if the provided connection is XA.

W-20267068

The alert context in the DIAF file is now reset after the configured time interval expires.

W-20140036

The HTTP Server now returns a 400 error when the HTTP/1 to HTTP/2 upgrade mechanism receives an invalid HTTP2-Settings header.

W-19895731

ERROR StatusLogger Attempted to append to non-started appender AnypointMonitoringFileAppender errors no longer occur when Anypoint Monitoring is enabled.

W-15577414

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The Apache Commons Lang library included in the distribution is upgraded.

W-20004786

DataWeave grammar transformation performance is improved.

W-19840284

Memory usage is improved for binary compilation and AST-related utilities.

W-19706956
**4.9.12 Runtime Updates** For Mule runtime 4.9.12 Edge, the image name that corresponds with these fixes is 4.9.12:5e.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

ERROR StatusLogger Attempted to append to non-started appender AnypointMonitoringFileAppender errors no longer occur when Anypoint Monitoring is enabled.

W-15577414

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549
For Mule runtime 4.9.12 LTS, the image name that corresponds with these fixes is 4.9.12:5.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

ERROR StatusLogger Attempted to append to non-started appender AnypointMonitoringFileAppender errors no longer occur when Anypoint Monitoring is enabled.

W-15577414

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549
**4.6.25 Runtime Updates** For Mule runtime 4.6.25 LTS, the image name that corresponds with these fixes is 4.6.25:5.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

DataWeave

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20618375

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
## [](#november-7-2025)November 7, 2025 The November 7 patch update (versions 4.10.1, 4.9.11, 4.6.24 and 4.4.0) addresses a regression introduced in the November 4 update (versions 4.10.1, 4.9.11 and 4.6.24) and includes all associated fixes. ### Fixed Issues **4.10.1 Runtime Updates** For Mule runtime 4.10.1 Edge, the image name that corresponds with these fixes is 4.10.1:12e.
Issue Resolution ID

Mule

The diagnostic file now generates correctly.

W-20139801

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
**4.9.11 Runtime Updates** For Mule runtime 4.9.11 Edge, the image name that corresponds with these fixes is 4.9.11:6e.
Issue Resolution ID

Mule

The diagnostic file now generates correctly.

W-20139801

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
For Mule runtime 4.9.11 LTS, the image name that corresponds with these fixes is 4.9.11:6.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

Starvation no longer occurs when sending HTTP responses that are generated slowly.

W-1982570

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.9, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
**4.6.24 Runtime Updates** For Mule runtime 4.6.24 LTS, the image name that corresponds with these fixes is 4.6.24:7.
Issue Resolution ID

Mule

The diagnostic file now generates correctly.

W-20139801

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
**4.4.0 Runtime Updates** For Mule runtime 4.4.0, the image name that corresponds with these fixes is 4.4.0:20250919-6.
Issue Resolution ID

Mule

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
## [](#november-4-2025)November 4, 2025 ### What’s New **4.4.0, 4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.4.0, 4.6.24, 4.9.11, and 4.10.1** This release of 4.4.0, 4.6.24, 4.9.11, and 4.10.1 includes Runtime Manager Agent 2.7.8. For information, see [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8). ### Fixed Issues **4.10.1 Runtime Updates** For Mule runtime 4.10.1 Edge, the image name that corresponds with these fixes is 4.10.1:10e.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.10, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.1.127.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

The Bump handlebars library is upgraded to 4.4.0.

W-1906465

The HTTP listener now correctly populates attributes.queryParams when using HTTP/2.

W-19802358

close_notify events sent by a server are now properly handled by the HTTP/2 client.

W-19973575

DataWeave

Materialization errors no longer occur in run function.

W-19884071

The org.apache.commons:commons-lang3 library is upgraded to 3.18.

W-19803454

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

The SnakeYAML library is upgraded.

W-19749213

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283

The -- operator now returns the correct type without the subtracted keys.

W-19595907

Debug logging is now enabled for DefaultLoggingService.

W-19650046

The take function no longer fails in streaming mode when n is larger than the array length.

W-19168279

The Java Module now supports object field access with different capitalizations.

W-19477334

The Runtime Compiler now uses the Parser Manager to look for resources provided as parameters.

W-19376888

A null check is now performed before closing the InputStream.

W-19395982

Parsing metrics printing now includes a missing line ending.

W-19440583

Constants are now used to prevent incorrect loader identifiers for binary compiled scripts.

W-18455133

Generated POM files now include license information.

W-19439330

SchemaProvider resolution on Types is improved to prevent Execution reference leaks.

W-19389019

The classloader weave resource resolver now uses the correct path in Windows environments.

W-19407283
**4.9.11 Runtime Updates** For Mule runtime 4.9.11 Edge, the image name that corresponds with these fixes is 4.9.11:4e.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

Starvation no longer occurs when sending HTTP responses that are generated slowly.

W-1982570

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.9, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
For Mule runtime 4.9.11 LTS, the image name that corresponds with these fixes is 4.9.11:4.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

Starvation no longer occurs when sending HTTP responses that are generated slowly.

W-1982570

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.9, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
**4.6.24 Runtime Updates** For Mule runtime 4.6.24 LTS, the image name that corresponds with these fixes is 4.6.24:4.
Issue Resolution ID

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now properly honors the graceful shutdown timeout. In versions earlier than 4.11.0, you must enable this behavior using these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19340663

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.6, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException no longer thrown when DW serializes error.errorMessage in Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071
**4.4.0 Runtime Updates** For Mule runtime 4.4.0, the image name that corresponds with these fixes is 4.4.0-20250919-5. - The operating system is updated to the latest security patches. ## [](#october-2-2025)October 2, 2025 ### What’s New - Mule runtime engine 4.10.0 is now available. For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **4.4, 4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.4.0, 4.6.22, 4.9.9, and 4.10.0** This release of 4.4.0, 4.6.23, 4.9.10, and 4.10.0 includes Runtime Manager Agent 2.7.7. For information, see [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues **4.10.0 Runtime Updates** For Mule runtime 4.10.0 Edge, the image name that corresponds with these fixes is 4.10.0:23e.
Issue Resolution ID

Mule

The org.quartz-scheduler:quartz library is upgraded to 2.5.0.

W-17406808

The org.vibur:vibur-object-pool library is upgraded to 26.

W-17570586

The commons-beanutils:commons-beanutils library is upgraded to 1.10.0.

W-17571116

The jakarta-annotation library is upgraded to 2.1.1.

W-17927646

The Mockito monorepo is upgraded to 5.

W-18685961

The Log4j2 monorepo is upgraded to 2.25.1.

W-18834079

The Netty library is upgraded to 4.1.127.Final.

W-19559645

The Rhino library is upgraded to 1.8.0.

W-17636627

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
**4.9.10 Runtime Updates** For Mule runtime 4.9.10 Edge, the image name that corresponds with these fixes is 4.9.10:4e.
Issue Resolution ID

Mule

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The Handlebars library is upgraded to 4.4.0.

W-19064659

The org.apache.commons : commons-lang3 library is upgraded to 3.17.0.

W-19383955

The io.netty : netty-codec library is upgraded to 4.1.127.Final.

W-19568278

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

Scheduler name generation no longer breaks the platform logging aggregator when processor chains have null or empty names.

W-19432758

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
For Mule runtime 4.9.10 LTS, the image name that corresponds with these fixes is 4.9.10:4.
Issue Resolution ID

Mule

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The Handlebars library is upgraded to 4.4.0.

W-19064659

The org.apache.commons : commons-lang3 library is upgraded to 3.17.0.

W-19383955

The io.netty : netty-codec library is upgraded to 4.1.127.Final.

W-19568278

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

Scheduler name generation no longer breaks the platform logging aggregator when processor chains have null or empty names.

W-19432758

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
**4.6.23 Runtime Updates** For Mule runtime 4.6.23 LTS, the image name that corresponds with these fixes is 4.6.23:4.
Issue Resolution ID

The org.springframework library is upgraded to 5.3.45.

W-18603096

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

This release reverts the changes introduced in W-17340911.

W-17340911

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

Batch queuestore files now clean up correctly in rare load failure scenarios, such as out of memory errors.

W-17935223

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334

Module compilation performance is improved when running concurrently.

W-19376546
**4.4.0 Runtime Updates** For Mule runtime 4.4.0, the image name that corresponds with these fixes is 4.4.0:20250919-3.
Issue Resolution ID

BufferOverFlowException errors no longer occur when inter-node communication gets stuck in clusters with encryption under heavy load.

W-16517561

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164
## [](#september-2-2025)September 2, 2025 ### What’s New **4.4, 4.6, and 4.9 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.4.0, 4.6.22, and 4.9.9** This release of 4.4.0, 4.6.21, and 4.9.8 includes Runtime Manager Agent 2.7.7. For information, see [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues **4.9.9 Runtime Updates** For Mule runtime 4.9.9 Edge, the image name that corresponds with these fixes is 4.9.9:5e.
Issue Resolution ID

Mule

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

io.projectreactor.netty : reactor-netty-http is upgraded to 1.2.8.

W-19074903

Component annotations, such as location, are no longer overwritten by other components.

W-18269859

org.apache.commons : commons-lang3 is upgraded to 3.18.0.

W-19059553

DataWeave

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

W-19376546
For Mule runtime 4.9.9 LTS, the image name that corresponds with these fixes is 4.9.9:5.
Issue Resolution ID

Mule

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

io.projectreactor.netty : reactor-netty-http is upgraded to 1.2.8.

W-19074903

Component annotations, such as location, are no longer overwritten by other components.

W-18269859

org.apache.commons : commons-lang3 is upgraded to 3.18.0.

W-19059553

DataWeave

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

W-19376546
**4.6.22 Runtime Updates** For Mule runtime 4.6.22 LTS, the image name that corresponds with these fixes is 4.6.22:4.
Issue Resolution ID

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
**4.4.0 Runtime Updates** For Mule runtime 4.4.0, the image name that corresponds with these fixes is 4.4.0:20250829-1.
Issue Resolution ID

Performance degradation no longer occurs when using repeatable streaming.

W-19175330
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for CloudHub (CloudHub Connector) enables you to connect to the CloudHub API from your Mule application. Guide: [CloudHub Connector User Guide](https://docs.mulesoft.com/jp/cloudhub-connector/latest/) ## [](#1-2-0)1.2.0 **January 11, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.4.0 or later

OpenJDK

8, 11, and 17
## [](#1-1-1)1.1.1 **April 26, 2023** ### Compatibility
Application/Service Version

Mule

4.4.0 or later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The com.google.code.gson library is upgraded to version 2.10.1 to address reported security vulnerabilities.

W-12980396

The connector no longer throws an invalid permission error when there are consecutive calls for the authorization check.

W-12980396
## [](#1-1-0)1.1.0 **October 6, 2022** ### What’s New - CloudHub Connector now supports Connected Apps Credentials through OAuth Client Credentials authentication. For more information, refer to [Connected Apps](https://docs.mulesoft.com/jp/access-management/connected-apps-overview) and [OAuth Client Credentials](https://docs.mulesoft.com/jp/cloudhub-connector/latest/cloudhub-connector-ref#Config_OauthClientCredentials). - The com.google.code.gson library is upgraded to version 2.9.0 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.4.0 or later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Mapping fields when creating a notification now works as intended.

W-11741367
## [](#1-0-2)1.0.2 **August 9, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 or later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.google.code.gson library is upgraded to version 2.8.9 to address reported security vulnerabilities.

W-11488986
## [](#1-0-1)1.0.1 **October 22, 2018** ### [](#minimum-mule-version)Minimum Mule Version Mule 4.1.1 ### [](#new-features)New Features - Improved reliability when creating notifications ## [](#1-0-0)1.0.0 **August 23, 2018** ### [](#minimum-mule-version-2)Minimum Mule Version Mule 4.1.1 ### [](#new-features-2)New Features - CloudHub Connector for Mule 4, gives the capability of create, consume and manage notifications. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub Dedicated Load Balancer Release Notes These release notes describe monthly Dedicated Load Balancer updates starting in July 2023, which include OS and security updates. For more information about these monthly scheduled updates, see [DLB Monthly Scheduled Update FAQ](https://help.salesforce.com/s/articleView?id=001117562&type=1). This table shows the current schedule for monthly updates. These dates are subject to change.
Month Release Available Sandbox Environment Auto-Update Production Environment Auto-Update

December

December 1

December 15-19

December 20-21

November

November 3

November 16-20

November 21-22

October

October 6

October 19-23

October 24-25

September

September 4

September 21-25

September 26-27
All releases occur in GMT-3 time. All automatic updates occur in the local time zone of the app’s deployment region. For example, CloudHub applies updates to apps deployed in the Asia-Pacific (Sydney) region in the AEST time zone and to apps deployed in the US West region in the PST time zone. ## [](#october-6-2026)October 6, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#september-4-2026)September 4, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#august-4-2026)August 4, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#july-7-2026)July 7, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#june-2-2026)June 2, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#may-5-2026)May 5, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#april-7-2026)April 7, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#march-3-2026)March 3, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#february-3-2026)February 3, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#january-6-2026)January 6, 2026 ### What’s New - Updated to the latest operating system security patches. ## [](#december-2-2025)December 2, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#november-4-2025)November 4, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#october-2-2025)October 2, 2025 ### What’s New - Updated to the latest operating system security patches. ### Fixed Issues
Issue Resolution ID

DLB workers now deploy evenly across different availability zones.

W-18343871
## [](#september-2-2025)September 2, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#august-5-2025)August 5, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#july-8-2025)July 8, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#june-3-2025)June 3, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#may-16-2025)May 16, 2025 ### What’s New - Updated to the latest operating system security patches. ### Fixed Issues

Issue

ID

An internal issue has been fixed to enhance DLB operations.

W-18512043
## [](#may-6-2025)May 6, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#april-8-2025)April 8, 2025 ### What’s New - Updated to the latest operating system security patches. ### Fixed Issues

Issue

ID

A Nginx issue regarding SSL Certificate Caching has been fixed.

W-16936789
## [](#march-5-2025)March 5, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#february-6-2025)February 6, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#january-7-2025)January 7, 2025 ### What’s New - Updated to the latest operating system security patches. ## [](#december-9-2024)December 9, 2024 ### What’s New - Updated to the latest operating system and security patches. ## [](#november-5-2024)November 5, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#october-8-2024)October 8, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#september-3-2024)September 3, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#august-6-2024)August 6, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#july-2-2024)July 2, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#june-4-2024)June 4, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#may-7-2024)May 7, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#april-8-2024)April 8, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#march-5-2024)March 5, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#february-6-2024)February 6, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#january-9-2024)January 9, 2024 ### What’s New - Updated to the latest operating system security patches. ## [](#november-28-2023)November 28, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#november-7-2023)November 7, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#october-12-2023)October 12, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#october-3-2023)October 3, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#september-1-2023)September 1, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#august-8-2023)August 8, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#july-4-2023)July 4, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#may-8-2023)May 8, 2023 ### What’s New - Updated to the latest operating system security patches. ## [](#december-1-2022)December 1, 2022 ### What’s New - Updated to the latest operating system security patches. - Updated internal infrastructure observability and reliability components. ## [](#sept-12-2022)Sept 12, 2022 ### What’s New - Increased DLB request header’s size limit from 8kb to 32kb. ## [](#sept-5-2022)Sept 5, 2022 ### Fixed Issues

Issue

ID

Fixed issue for DLB Client Certificate Forwarding.

W-11439083
## [](#august-18-2022)August 18, 2022 ### What’s New - Added TLS 1.3 support for Dedicated Load Balancers. ## [](#august-8-2022)August 8, 2022 ### What’s New - Updated to the latest operating system security patches. - Added reliability and resiliency enhancements. ## [](#july-4-2022)July 4, 2022 ### What’s New - Updated to the latest operating system security patches. ## [](#june-3-2022)June 3, 2022 ### What’s New - Updated to the latest operating system security patches. ## [](#may-11-2022)May 11, 2022 ### What’s New - Added Dedicated Load Balancer(DLB) support for Certificate Forwarding. - Added DLB support for HTTP Streaming. - Added new inclusive language to Allowlist IP addresses for Cloudhub. ## [](#december-14-2021)December 14, 2021 ### What’s New - Updated to the latest operating system security patches to address potential security vulnerabilities. ## [](#december-7-2021)December 7, 2021 ### What’s New - Updated to the latest operating system security patches. ## [](#november-05-2021)November 05, 2021 ### What’s New - Updated to the latest operating system security patches. ## [](#older-dlb-updates)**Older DLB Updates** ## [](#1-6-0)1.6.0 **October 14, 2021** ### What’s New - Updated the static IP functionality of the Dedicated Load Balancer to enhance restart functionality. This update increases the number of static IPs allocated to the Dedicated Load Balancer. New Dedicated Load Balancers default to dynamic IPs. You can choose static IPs via the **Update** button on the UI. See [Dedicated Load Balancer Updates](https://docs.mulesoft.com/cloudhub/lb-updates) ## [](#1-5-0)1.5.0 **December 10, 2020** ### [](#features-and-updates)Features and Updates - OS patches and security updates No feature updates. ## [](#1-4-0)1.4.0 **November 14, 2020** ### [](#features-and-updates-2)Features and Updates - This release includes a new default cipher list. All newly created DLBs use the new default cipher list. Existing DLBs retain their current default list until they update the default cipher list. ## [](#1-3-0)1.3.0 **October 13, 2020** ### [](#features-and-updates-3)Features and Updates - Added a security enhancement to prevent MIME sniffing on DLB headers. This update takes effect on DLB restart and has no impact on existing traffic or applications. (SE-17660) ## [](#1-2-0)1.2.0 **February 25, 2020** ### [](#features-and-updates-4)Features and Updates - OS patches and security updates No feature updates. ## [](#1-1-9)1.1.9 **February 20, 2020** Changes made in this release were reverted. ## [](#1-1-8)1.1.8 **December 12, 2019** ### [](#features-and-updates-5)Features and Updates - Improved capacity limits for Dedicated Load Balancer (DLB) The DLB connection capacity has been improved. This improvement increases the resiliency of the DLB in scenarios when a degraded, high-volume, backend CloudHub application exhausts resources on the DLB. - Mule application response timeout feature A **Timeout in Seconds** field has been added to the DLB configuration settings. You can use this setting to specify the response timeout value from the Mule runtime engine. The default is 300 seconds. ## [](#1-1-7)1.1.7 **October 5, 2019** ### [](#features-and-updates-6)Features and Updates - User-initiated updates When an update is available, the **Update** button appears on the load balancers page and on the details page for the individual load balancer. See [Dedicated Load Balancer Updates](https://docs.mulesoft.com/cloudhub/lb-updates). - Updated dedicated load balancer server Security updates and patches ## [](#1-1-6)1.1.6 **July 2019** ### [](#features-and-updates-7)Features and Updates - Upstream TLS 1.2 functionality - WS and WSS support added to existing HTTP and HTTPS support - Updated dedicated load balancer server Security updates and patches, which occur when the load balancer restarts ## [](#1-1-5)1.1.5 ### [](#updates)Updates - Improved log rotation - Security updates and patches - Performance and resiliency improvements ## [](#1-1-4)1.1.4 ### [](#updates-2)Updates - Remove deprecated 3DES ciphers from the accepted cipher suite. - Entitlements for load balancers are now enforced per business group. - Introduce TLS keepalives to upstream HTTPS applications, improving performance. ## [](#1-1-2)1.1.2 ### [](#updates-3)Updates - Static IPs are no longer required for load balancers. - Improved reliability and monitoring of load balancers. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub Release Notes These release notes describe updates to CloudHub. ## [](#1-31-1)1.31.1 **April 20, 2026** ### What’s New This release includes these changes: - You can now run Mule Diagnostic Agent to collect diagnostics data from your applications and analyze it with Einstein through Runtime Manager. For details, refer to [Run the MuleSoft Diagnostics Agent](https://docs.mulesoft.com/cloudhub/ch-diagnostics-agent#run-the-mulesoft-diagnostics-agent). ## [](#1-130-0)1.130.0 **February 5, 2026** ### What’s New This release includes these changes: - CloudHub now includes reliability and resiliency enhancements. ## [](#1-129-0)1.129.0 **January 13, 2026** ### What’s New This release includes these changes: - CloudHub now includes reliability and resiliency enhancements. ## [](#1-128-0)1.128.0 **November 18, 2025** ### What’s New This release includes these changes: - CloudHub now includes reliability and resiliency enhancements. ## [](#1-127-0)1.127.0 **October 27, 2025** ### What’s New This release includes these changes: - You can now use the MuleSoft diagnostics agent to collect diagnostics data from your applications and analyze them with Einstein. See [Generate Apps Diagnostics and Analyze with Einstein](https://docs.mulesoft.com/cloudhub/ch-diagnostics-agent). - Added reliability and resiliency enhancements. ## [](#1-126-0)1.126.0 **September 25, 2025** ### What’s New This release includes the these changes: - Added reliability and resiliency enhancements. ### Fixed Issues
Issue Resolution ID

DLB workers now deploy evenly across different availability zones.

W-18343871
## [](#1-125-0)1.125.0 **July 10, 2025** ### What’s New This release includes this change: - Added reliability and resiliency enhancements. ## [](#1-124-0)1.124.0 **April 4, 2025** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-123-0)1.123.0 **January 28, 2025** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-122-0)1.122.0 **November 6, 2024** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-121-0)1.121.0 **October 1, 2024** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-120-0)1.120.0 **August 27, 2024** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ### Fixed Issues

Issue Resolution

ID

HTTP Request Connector no longer ignores the requestStreamingMode value when using followRedirects.

W-10868877
## [](#1-119-1)1.119.1 **August 17, 2024** ### Fixed Issues

Issue Resolution

ID

Starting August 17th, 2024, the CloudHub API now returns timestamp without square brackets when extracting logs.

W-13550201
## [](#1-119-0)1.119.0 **July 12, 2024** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-118-0)1.118.0 **June 13, 2024** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ### Fixed Issues

Issue Resolution

ID

The ConnectionPoolTimeoutException error no longer occurs at deployment.

W-15062332
## [](#1-117-0)1.117.0 **April 4, 2024** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-116-0)1.116.0 **March 6, 2024** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. - Application logs now show the Java version during deployment. ### Fixed Issues

Issue Resolution

ID

The Runtime Manager UI now shows CloudHub workers' heap memory size correctly.

W-12032181

The releaseChannel and javaVersion flags are now honored when passing the full runtime version name.

W-14983643

The latest build for each Mule version is no longer applied if not specified.

W-15084292
## [](#1-115-1)1.115.1 **February 6, 2024** ### What’s New This release includes the following changes: - CloudHub now supports Mule 4.6 and Java 17. ### Known Issues
Known Issue Workaround ID

When creating or updating applications using CloudHub API, the version field values 4.6-e-java8 and 4.6-e-java17 are not compatible with releaseChannel and javaVersion.

Don`t provide the releaseChannel and javaVersion values when using the versions 4.6-e-java8 and 4.6-e-java17. The version itself is sufficient to determine the correct Mule runtime version for your application.

W-14983643
## [](#1-115-0)1.115.0 **January 17, 2024** ### What’s New This release includes the following changes: - Added all available static IPs in the `ipAddresses` array in the Dedicated Load Balancer response request. ## [](#1-114-0)1.114.0 **December 4, 2023** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-113-0)1.113.0 **October 31, 2023** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-112-0)1.112.0 **October 4, 2023** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-111-0)1.111.0 **September 18, 2023** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-110-0)1.110.0 **August 28, 2023** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-109-0)1.109.0 **August 2, 2023** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-108-0)1.108.0 **June 13, 2023** ### What’s New This release includes the following changes: - You can now use the `type` property in DLB GET requests to determine if the DLB is Sandbox or Production. ## [](#1-107-0)1.107.0 **May 8, 2023** ### What’s New This release includes the following changes: - DLB responses to GET requests now contain `masterOrgId` and `orgId`. - You can now automatically pass in all Mule application properties as system properties. - Added reliability and resiliency enhancements. ## [](#1-106-0)1.106.0 **January 17, 2023** ### What’s New This release includes the following changes: - The Dedicated Load Balancer API provides previous image information after restarts or updates. - Beginning February 7, 2023, you can use queries to search application logs in Runtime Manager. ### Fixed Issues

Issue Resolution

ID

You can no longer configure firewall rules for ports below 1024. This is strictly enforced. For more information, see VPC Firewall Rules.

W-10569133
## [](#1-105-0)1.105.0 **November 15, 2022** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-104-1)1.104.1 **September 12, 2022** ### What’s New This release includes the following changes: - You can now migrate legacy VPNs to Anypoint VPNs. For more information, see [Legacy VPN Migration to Anypoint VPNs](https://docs.mulesoft.com/cloudhub/vpn-about). ### Fixed Issues

Issue

ID

Notification processing time is improved to handle intermittent failures.

W-11311651
## [](#1-104-0)1.104.0 **September 5, 2022** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-103-6)1.103.6 **August 18, 2022** ### What’s New This release includes the following changes: - Added backend support for upcoming features. - Added reliability and resiliency enhancements. ## [](#1-103-5)1.103.5 **July 14, 2022** ### What’s New This release includes the following changes: - You can now use VPN Initiator Mode on the **VPN Edit** page. - **VPN Edit** page UX is improved. ## [](#1-103-4)1.103.4 **July 11, 2022** ### What’s New This release includes the following changes: - Added backend support for VPN Initiator Mode. - Added reliability and resiliency enhancements. ### Fixed Issues

Issue

ID

CloudHub no longer allows DLB names that start with internal-.

W-10647482
## [](#1-102-0)1.102.0 **April 28, 2022** ### What’s New This release includes the following changes: - Added backend support for upcoming features. - Added reliability and resiliency enhancements. ## [](#1-101-0)1.101.0 **February 23, 2022** ### What’s New This release includes the following changes: - Added backend support for upcoming features. - Added reliability and resiliency enhancements. ## [](#1-100)1.100 **December 9, 2021** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. - Added caching to `/cloudhub/api/organizations/{orgid}/vpcs` API GET calls to improve response time. ### Fixed Issues

Issue

ID

Fixed a static IP validation issue.

SE-22679
## [](#1-99-0)1.99.0 **October 13, 2021** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. - Added backend support for upcoming features. ## [](#1-98-0)1.98.0 **September 13, 2021** ### What’s New - CloudHub Anypoint VPCs can now attach to your AWS Transit Gateways. For information about transit gateway attachments, see [Transit Gateway Attachments](https://docs.mulesoft.com/cloudhub/tgw-about). - In Access Management, the **VPN** Business Groups settings have been changed to **Network Connections**, since this entitlment can now be used for an Anypoint VPN connection or an attachment to your AWS Transit Gateway. For information about Business Groups, see [Business Groups](https://docs.mulesoft.com/jp/access-management/business-groups). ## [](#1-97-0)1.97.0 **August 16, 2021** ### What’s New This release includes the following changes: - Added reliability and resiliency enhancements. - Added backend support for upcoming features. ### Fixed Issues

Issue

ID

Added the Mule release version to application start logs.

SE-17821

Fixed an issue related to changing the log level in application settings.

SE-20357
## [](#1-96-0)1.96.0 **July 26, 2021** This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-95-0)1.95.0 **July 19, 2021** This release includes the following changes: - Added VPN Update performance and security enhancements. - Added UI feature to upgrade Anypoint VPN. ## [](#1-94-0)1.94.0 **July 14, 2021** ### [](#whats-new-40)What’s New - Schedules Adapted the minimum supported schedule frequency to match our SLA from `1` to `10` seconds. This change applies to all new schedules and when modifying existing schedules. See [Manage Schedules](https://docs.mulesoft.com/cloudhub/managing-schedules). ## [](#1-93-3)1.93.3 **June 30, 2021** This release includes the following changes: - Added backend support for upcoming enhancement to dedicated load balancers. - Added reliability and resiliency enhancements. ## [](#1-93-2)1.93.2 **June 16, 2021** This release includes the following changes: - Added reliability and resiliency enhancements. ## [](#1-93-1)1.93.1 **June 3, 2021**
This release is available only on the US control plane.
This release includes the following change: - Improved performance of the Anypoint VPC API to avoid possible timeouts in the Runtime Manager console. (SE-19665) ## [](#1-93-0)1.93.0 **April 28, 2021**
This release is available only on the EU control plane.
This release includes the following changes: - Improved performance of the Anypoint VPC API to avoid possible timeouts in the Runtime Manager console. (SE-19665) - Added backend support for upcoming enhancement to dedicated load balancers. - Added reliability and resiliency enhancements. ## [](#1-92-2)1.92.2 **April 20, 2021** This release includes the following changes: - Added the ability to view and download Mule runtime engine logs from the **Logs** page. See [Download Mule Logs](https://docs.mulesoft.com/cloudhub/viewing-log-data#download-mule-logs). ## [](#1-92-1)1.92.1 **March 23, 2021** This release includes the following changes: - Increased the console timeout value when retrieving VPN information to prevent communication errors. (SE-14788) ## [](#1-92-0)1.92.0 **March 9, 2021** This release includes the following changes: - Added reliability and resiliency enhancements. - Added the runtime distribution number and release date to the application startup log message. (SE-17821) Worker(): Starting your application on mule=- Release date - Fixed improperly handled responses in which CloudHub returned `500` instead of `400` or `401`. - Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app fails to deploy multiple times in a row. (SE-14788) ## [](#1-91-1)1.91.1 **March 4, 2021** This release includes the following changes: - The CloudHub API for performing bulk application updates now has a limit of 100 application domains per API call. ## [](#1-91-0)1.91.0 **January 26, 2021** This release includes the following changes: - Added reliability and resiliency enhancements. - Fixed an issue in which the CloudHub API sometimes failed to update apps due to a race condition and returned `409 Application not updated`. (SE-18659) - Fixed an issue in which calls to the `cloudhub/api/v2/applications/` endpoint failed if the worker type was not specified. (SE-19234) ## [](#1-90-1)1.90.1 **January 21, 2021** This release includes the following change: - If an application exceeds the rate limit for a shared load balancer, the load balancer now returns response code `429` instead of `503`. (SE-15733) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [Troubleshoot Transit Gateway Attachments](https://docs.mulesoft.com/cloudhub/tgw-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub Release Notes - [CloudHub Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes) - [CloudHub Runtime and OS Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes) - [CloudHub Dedicated Load Balancer Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes) - [Anypoint VPN Updates Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/anypoint-vpn-release-notes) ## [](#see-also)See Also - [CloudHub Documentation](https://docs.mulesoft.com/cloudhub/) - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub Release Notes - EU Cloud In addition to these release notes, see the complete [CloudHub](https://docs.mulesoft.com/cloudhub/) documentation. ## [](#1-72-3-december-6-2018)1.72.3 - December 6, 2018 This release includes the following changes and improvements: - A series of reliability and resiliency enhancements - Bug fixes and performance improvements ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # CloudHub Runtime and Operating System Patch Update Release Notes These release notes describe monthly date-patch updates to Mule runtime engine and security updates to the underlying operating system for CloudHub. In addition to these release notes, see: - [CloudHub Runtime Continuous Updates](https://docs.mulesoft.com/cloudhub/cloudhub-app-runtime-version-updates) - [CloudHub Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes) - [CloudHub documentation](https://docs.mulesoft.com/cloudhub/) ## [](#mulesoft-commercial-and-government-cloud-schedule)MuleSoft Commercial and Government Cloud Schedule This table shows the current schedule for monthly updates. These dates are subject to change.
Month Release Available Sandbox Environment Auto-Update Production Environment Auto-Update

December

December 1

December 15-19

December 20-21

November

November 3

November 16-20

November 21-22

October

October 6**

October 19-23

October 24-25

September

September 4*

September 21-25

September 26-27
The release notes for an update are published in the same week in which the runtime patch is released for all Mule versions on CloudHub.
All releases occur in GMT-3 time. All automatic updates occur in the local time zone of the app’s deployment region. For example, CloudHub applies updates to apps deployed in the Asia-Pacific (Sydney) region in the AEST time zone and to apps deployed in the US West region in the PST time zone.
** The October 2026 Government Cloud monthly patch release was rescheduled from October 6 to October 7. All subsequent update windows remain unchanged.
* The September 2026 monthly patch release is rescheduled from September 8 to September 4. All subsequent update windows remain unchanged.
Using a runtime version that is more than three months old can introduce security vulnerabilities. If your application doesn’t update automatically within two monthly patching cycles, CloudHub stops the application and force-updates the application to the latest patch version. If an application doesn’t automatically start after the forced patch update, make sure the patch is applied and start the application. For more information, see Failed Automated Updates.
CloudHub doesn’t auto-upgrade apps when the target Mule runtime version introduces incompatibilities with the application configuration, such as TLS or Java version changes. For example, apps that use TLS 1.1 in Mule 4.9 aren’t auto-upgraded to Mule 4.10 because Mule 4.10 doesn’t support TLS 1.1. Similarly, apps aren’t auto-upgraded across incompatible Java versions.
## [](#october-15-2026)October 15, 2026 ### What’s New **4.13.1, 4.12.5, 4.9.23, and 4.6.36 Runtime Updates** This update addresses regressions introduced in the October release. **Runtime Manager agent versions included in Runtime 4.13.1, 4.12.5, 4.9.23, and 4.6.36** This release of 4.13.1, 4.12.5, and 4.9.23 includes Runtime Manager agent 2.8.5, and 4.6.36 includes Runtime Manager agent 2.7.20. For information, see [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) and [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20). ### Fixed Issues **4.13.1 Runtime Updates** For Mule runtime 4.13.1 on CloudHub, the image name that corresponds with this update is 4.13.1:2e.
Issue Resolution ID

Mule

Applications no longer fail to deploy when the type of an on-error-propagate or on-error-continue is a property placeholder and the flow contains a component that supports streaming and requires a connection, such as an HTTP Request or Kafka operation.

W-24456406

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

Polling sources that use a CloudHub Object Store v2 for watermarks now track processed items in the object store’s configured partition instead of the default partition.

W-24459240

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
**4.12.5 Runtime Updates** For Mule runtime 4.12.5 on CloudHub, the image name that corresponds with this update is 4.12.5:2e.
Issue Resolution ID

Mule

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
**4.9.23 Runtime Updates** - For Mule runtime 4.9.23 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.9.23:4. - For Mule runtime 4.9.23 on Government Cloud with FIPS 140-3, the image name that corresponds with this update is 4.9.23:4-fips1403.
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
**4.6.36 Runtime Updates** For Mule runtime 4.6.36 on CloudHub, the image name that corresponds with this update is 4.6.36:2.
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
## [](#october-6-2026)October 6, 2026 ### What’s New - Mule runtime engine 4.13.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **4.13.0, 4.12.4, 4.9.22, and 4.6.35 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager agent versions included in Runtime 4.13.0, 4.12.4, 4.9.22, and 4.6.35** This release of 4.13.0, 4.12.4, and 4.9.22 includes Runtime Manager agent 2.8.5, and 4.6.35 includes Runtime Manager agent 2.7.20. For information, see [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) and [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20). ### Fixed Issues **4.13.0 Runtime Updates** For Mule runtime 4.13.0 on CloudHub, the image name that corresponds with this update is 4.13.0:16e.
Issue Resolution ID

Mule

The jsoup library is upgraded to 1.23.2.

W-23987955

The Jackson library is upgraded to 2.22.3.

W-24335732

The Reactor Core library is upgraded to 3.8.7.

W-23987958

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

The raml-parser-2 library is upgraded to 1.2.1.

W-23570110

Error-mapping preservation during error propagation is now enabled by default. An error whose type was already resolved inside a scope, including any remapping by an error mapping, now keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type. You can disable this behavior by setting the mule.honourErrorMappingsOnErrorPropagation system property to false.

W-23955755

OpenTelemetry metric exporters now support per-exporter view enrichment and resource attribute overrides.

W-23367495

JSON schema validation is migrated from the everit library to networknt, with everit retained as a fallback.

W-16530105

HTTP header values containing CR/LF characters are now sanitized instead of causing the request to be rejected.

W-22252135

minMuleVersion values are now normalized when loaded, preventing the patch or revision portion from being truncated.

W-24231362

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

Logging export reconfiguration is fixed for single application mode.

W-20908857

The ObjectStore API is extended with an upsert operation and an isThreadSafe indicator.

W-23090592

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809

A java.lang.UnsupportedClassVersionError thrown when a connector’s compiled target doesn’t match the running JVM is now handled gracefully.

W-24193358

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

A source policy that uses Async, Parallel For Each, or Scatter-Gather no longer builds its response from the failure response parameters instead of the success response parameters, and no longer silently drops the forked route’s response processing.

W-23938349

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

The commons-beanutils library and its transitive commons-collections 3.2.2 dependency are removed from Mule Runtime modules.

W-16918287

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

An unresolved placeholder in the meter-exporter configuration now degrades to its default value at tracer startup instead of causing a failure.

W-23650358

Dynamic reload of the metrics exporter configuration is now supported.

W-21921629

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

OutputHandler is deprecated and its support is removed.

W-23660888

A SerializationException now raises a MULE:SERIALIZATION error, instead of MULE:UNKNOWN.

W-21381359

The exporter-health backpressure-alert cadence for OpenTelemetry tracing, metrics, and logging is now configured through a single system property, mule.openTelemetry.meter.exporter.healthMetrics.alertingFrequency, instead of the separate per-signal metricsLogFrequency properties, which are deprecated and no longer consumed.

W-22193713

MULE:INVALID_INPUT_PARAM is now preserved as a suppressed error when a MULE:SOURCE_RESPONSE_GENERATE error occurs.

W-22293407

SDK parameter validation errors are now mapped to the MULE:INVALID_INPUT_PARAM error type.

W-2227652

Mule-generated tracing spans no longer truncate attribute values at OpenTelemetry’s default 128-character limit. Attribute values are now preserved up to 4096 characters before truncation.

W-20091299

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

SQSQueueManagementService is added to the serialization allowlist.

W-24197744

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401

DataWeave

Memory usage for text/plain output is reduced.

W-20063270

Eagerly materialize executable Weave reader results.

W-23837275

Thread safety is improved when processing Java map values.

W-23661641

DataWeave tooling now reports design-time warnings when Java classes referenced in application/java schemas can’t be found or are inaccessible through JPMS.

W-22797049

DataWeave now filters Java classes in JPMS-unexported packages during Java module resolution, preventing runtime IllegalAccessException failures. This behavior is enabled by default on JDK 17 and later with DataWeave language version 2.13 and later. To keep the previous behavior, set mule.dw.filter_jpms_inaccessible_modules=false.

W-22779527

Cryptographic security warnings and errors now include call stacks.

W-22144340
**4.12.4 Runtime Updates** For Mule runtime 4.12.4 on CloudHub, the image name that corresponds with this update is 4.12.4:9e.
Issue Resolution ID

Mule

The Log4j library is upgraded to 2.26.1.

W-24061648

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

Network information listening ports are now scoped to the Mule process.

W-24043880

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

On CloudHub 2.0 and Runtime Fabric deployments, container logs exported through OpenTelemetry now correctly use the deployed application’s configured service name, instead of the generic mule-container name.

W-23734353

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809
**4.9.22 Runtime Updates** - For Mule runtime 4.9.22 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.9.22:8. - For Mule runtime 4.9.22 on Government Cloud with FIPS 140-3, the image name that corresponds with this update is 4.9.22:8-fips1403.
Issue Resolution ID

Mule

The Reactor Core library is upgraded to 3.8.7.

W-23953702

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
**4.6.35 Runtime Updates** - For Mule runtime 4.6.35 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.6.35:4. - For Mule runtime 4.6.35 on Government Cloud with FIPS 140-3, the image name that corresponds with this update is 4.6.35:4-fips1403.
Issue Resolution ID

Mule

The Reactor Core library is upgraded to 3.8.7.

W-3300013

The Jackson library is upgraded to 2.22.2.

W-23947149

The jsoup library is upgraded to 1.23.2.

W-23987949

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

An SDK API for queues (VM usage) and core adapters is added.

W-19439432

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. To change the behavior, configure the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
## [](#september-23-2026)September 23, 2026 ### What’s New **4.12.3 and 4.11.6 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager agent versions included in Runtime 4.12.3 and 4.11.6** This release of 4.12.3 and 4.11.6 includes Runtime Manager agent 2.8.4. For information, see [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4). **4.12.3 Runtime Updates** For Mule runtime 4.12.3 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.12.3:6e.
Issue Resolution ID

Workers running Mule runtime Edge versions on non-micro instance sizes now correctly allocate JVM heap memory.

W-22534602
**4.11.6 Runtime Updates** For Mule runtime 4.11.6 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.11.6:7e.
Issue Resolution ID

Workers running Mule runtime Edge versions on non-micro instance sizes now correctly allocate JVM heap memory.

W-22534602
## [](#september-4-2026)September 4, 2026 ### What’s New **4.12.3, 4.9.21, and 4.6.34 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager agent versions included in Runtime 4.12.3, 4.9.21, and 4.6.34** This release of 4.12.3 and 4.9.21 includes Runtime Manager agent 2.8.4, and 4.6.34 includes Runtime Manager agent 2.7.16. For information, see [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4) and [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). ### Fixed Issues **4.12.3 Runtime Updates** For Mule runtime 4.12.3 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.12.3:5e.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23671475

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

DataWeave

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
**4.9.21 Runtime Updates** - For Mule runtime 4.9.21 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.9.21:4. - For Mule runtime 4.9.21 on Government Cloud with FIPS 140-3, the image name that corresponds with this update is 4.9.21:4-fips1403.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

The HTTP client configurer now includes a method to control whether sensitive headers are filtered when a request is redirected to a different domain.

W-21045658

A forward-proxy client no longer sends a malformed, path-only request line.

W-23384645

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540341

The RAML Parser library is upgraded to 2-1.2.1.

W-23328348

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

DataWeave

Vulnerable dependencies are upgraded to address reported security vulnerabilities.

W-23924223

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160

Additional fixes for Government Cloud with FIPS 140-2

Worker TLS configuration for Government Cloud is strengthened.

W-23819316

TLS hostname verification no longer falls back to the certificate’s Common Name (CN) when a DNS Subject Alternative Name (SAN) isn’t present. The server hostname must now be included in the certificate’s DNS SAN. Otherwise, hostname verification fails and the TLS connection may be rejected with certificate_unknown(46).

W-23730329

Additional fixes for Government Cloud with FIPS 140-3

Worker TLS configuration for Government Cloud is strengthened.

W-23819316
**4.6.34 Runtime Updates** - For Mule runtime 4.6.34 on CloudHub and Government Cloud with FIPS 140-2, the image name that corresponds with this update is 4.6.34:6. - For Mule runtime 4.6.34 on Government Cloud with FIPS 140-3, the image name that corresponds with this update is 4.6.34:6-fips1403.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Apache Commons Compress library is upgraded to 1.26.0.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540335

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

DataWeave

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160

Additional fixes for Government Cloud with FIPS 140-2

Worker TLS configuration for Government Cloud is strengthened.

W-23819316

TLS hostname verification no longer falls back to the certificate’s Common Name (CN) when a DNS Subject Alternative Name (SAN) isn’t present. The server hostname must now be included in the certificate’s DNS SAN. Otherwise, hostname verification fails and the TLS connection may be rejected with certificate_unknown(46).

W-23730329

Additional fixes for Government Cloud with FIPS 140-3

Worker TLS configuration for Government Cloud is strengthened.

W-23819316
## [](#august-4-2026)August 4, 2026 ### What’s New **4.12.2, 4.9.20, and 4.6.33 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager agent versions included in Runtime 4.12.2, 4.9.20, and 4.6.33** This release of 4.12.2 and 4.9.20 includes Runtime Manager agent 2.8.3, and 4.6.33 includes Runtime Manager agent 2.7.18. For information, see [Runtime Manager Agent 2.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-3) and [Runtime Manager Agent 2.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-18). ### Fixed Issues **4.12.2 Runtime Updates** For Mule runtime 4.12.2, the image name that corresponds with this fix is 4.12.2:5e.
Issue Resolution ID

Mule

Lazy initialization no longer fails with a NullPointerException when an application using the VM connector’s publish operation also configures a global error handler.

W-23156632

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

An HTTP request client connecting through a proxy no longer hangs when the proxy responds with a 407 (Proxy Authentication Required) response during the CONNECT tunnel handshake.

W-23384719

The HTTP request client now sends a correctly formed request line when connecting through a forward proxy.

W-23384645

A NullPointerException no longer occurs when the HTTP request client reuses a pooled connection to a forward proxy.

W-23384744

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Batch module now provides a public API to configure a custom queue manager and queue timeout.

W-23371797

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Sec-WebSocket-Protocol header is now forwarded on outbound WebSocket connections, so subprotocol negotiation with the server succeeds.

W-23071781

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API Gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23165634

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

Type metadata processing now correctly handles sibling references that target the same type, preventing duplicate annotations.

W-23424037

DataWeave now handles Java Platform Module System (JPMS) access restrictions more gracefully when running on Java 17 and later in Mule runtime 4.6.0 and later.

W-23354139

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
**4.9.20 Runtime Updates** For Mule runtime 4.9.20, the image name that corresponds with this fix is 4.9.20:6.
Issue Resolution ID

Mule

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23131090

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
**4.6.33 Runtime Updates** For Mule runtime 4.6.33, the image name that corresponds with this fix is 4.6.33:7.
Issue Resolution ID

Mule

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23121654

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592
## [](#july-7-2026)July 7, 2026 ### What’s New **4.12.1, 4.11.6, 4.9.19, and 4.6.32 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.12.1, 4.11.6, 4.9.19, and 4.6.32** This release of 4.12.1, 4.11.6, 4.9.19, and 4.6.32 includes Runtime Manager Agent 2.7.16. For information, see [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). ### Fixed Issues **4.12.1 Runtime Updates** For Mule runtime 4.12.1, the image name that corresponds with this fix is 4.12.1:4e.
Issue Resolution ID

Mule

Clustered applications deployed with two or more replicas no longer fail to start with a NullPointerException error during cluster node discovery.

W-22843942

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Object Store retrieved from the registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

The error type in the EE cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Test Connection for the HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the host field.

W-21921687

HTTP Server now supports upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

In-memory Object Store partitions are now created correctly when an application is deployed to a cluster with the Object Store plugin enabled.

W-17714668

Deserialization errors no longer occur in the Object Store during a runtime patch upgrade.

W-20880559

Applications deployed with a serialized AST now include all Mule error types in the error type repository.

W-22399271

Applications that use HTTP request attributes no longer fail annotation processing due to default constructor validation.

W-22385620

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

OpenTelemetry flow statistics now report metrics correctly for applications with more than one flow.

W-23051614

The artifact type (domain, policy, or application) is now included as an OpenTelemetry resource attribute.

W-21768636

OpenTelemetry metric attribute names now use a consistent notation.

W-21921584

The mule.openTelemetry.logging.exporter.resource.container.service.name system property is now available to set the service name that the Mule container reports for OpenTelemetry telemetry.

W-22861497

Event dumps now include a state for events that are waiting on a non-blocking operation.

W-22142952

The Netty library is upgraded to 4.2.15.Final.

W-22831076

The c3p0 library is upgraded to 0.14.1.

W-22990155

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The Reactor Netty library is upgraded to 1.3.6.

W-3300013

The Jackson Core library is upgraded to 2.21.1.

W-22839747

The Apache Neethi library is upgraded to 3.2.1.

W-22839752

The OpenTelemetry API library is upgraded to 1.62.0.

W-22849469

The Spring Framework is upgraded to 6.2.19.

W-22939417

Concurrent polling sources no longer fail with ConcurrentModificationException when creating Cloud Object Store partitions during application startup.

W-22809694

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344
**4.11.6 Runtime Updates** For Mule runtime 4.11.6, the image name that corresponds with this fix is 4.11.6:4e.
Issue Resolution ID

Mule

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The c3p0 library is upgraded to 0.14.1.

W-22990152

The Spring Framework is upgraded to 6.2.19.

W-3300013

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806044

The Netty library is upgraded to 4.2.15.Final.

W-22888966

The Reactor Netty library is upgraded to 1.3.6.

W-22939412

Concurrent polling sources no longer fail with ConcurrentModificationException when creating Cloud Object Store partitions during application startup.

W-22809694

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
**4.9.19 Runtime Updates** For Mule runtime 4.9.19, the image name that corresponds with this fix is 4.9.19:8.
Issue Resolution ID

Mule

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

The Content-Length header is now removed based on the actual entity byte length.

W-22570070

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

The Jackson Databind library is upgraded to 2.21.4.

W-3300013

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806027

The c3p0 library is upgraded to 0.14.1.

W-23012713

The Apache Neethi library is upgraded to 3.2.1.

W-22939389

The Apache CXF library is upgraded to 3.6.11.

W-23037617

The Rhino library is upgraded to 1.8.1.

W-22939391

The Log4j library is upgraded to 2.25.4.

W-22939403

The Reactor Netty library is upgraded to 1.2.18.

W-22939384

The Spring Framework is upgraded to 6.2.19.

W-22956997

The Netty library is upgraded to 4.2.15.Final.

W-22956998

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007

Concurrent polling sources no longer fail with ConcurrentModificationException when creating Cloud Object Store partitions during application startup.

W-22809694

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
**4.6.32 Runtime Updates** For Mule runtime 4.6.32, the image name that corresponds with this fix is 4.6.32:4.
Issue Resolution ID

Mule

A NullPointerException error no longer occurs in event context handling when a flow times out while a non-blocking operation is still in flight.

W-22902839

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The Joda-Time library is upgraded to 2.13.0.

W-3300013

The Rhino library is upgraded to 1.7.15.1.

W-22805996

The Apache Neethi library is upgraded to 3.2.1.

W-22805997

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806011

The Apache CXF library is upgraded to 3.5.11.

W-23037585

The c3p0 library is upgraded to 0.14.1.

W-23012711

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007

Concurrent polling sources no longer fail with ConcurrentModificationException when creating Cloud Object Store partitions during application startup.

W-22809694

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

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 per_app_java_bean_cache compatibility flag.

W-22417507
## [](#june-18-2026)June 18, 2026
Update for image 4.9.18:1-fips1403 applies to Government Cloud only.
### What’s New **4.9.18 Runtime Updates** For Mule runtime 4.9.18, the image name that corresponds with this release is 4.9.18:1-fips1403. The patch update now supports FIPS 140-3 compliance. ## [](#june-2-2026)June 2, 2026 ### What’s New - Mule runtime engine 4.12.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **4.12.0, 4.11.5, 4.9.18, and 4.6.31 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.12.0, 4.11.5, 4.9.18, and 4.6.31** This release of 4.12.0, 4.11.5, 4.9.18, and 4.6.31 includes Runtime Manager Agent 2.7.15. For information, see [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15). ### Fixed Issues **4.12.0 Runtime Updates** For Mule runtime 4.12.0, the image name that corresponds with this fix is 4.12.0:10e.
Issue Resolution ID

Mule

Upstream HTTP requests are now cancelled when a downstream client disconnects, preventing unnecessary data transfer.

W-20084343

The Netty HTTP client no longer throws NullPointerException when handling Expect 100-Continue responses.

W-21513490

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

The Apache CXF library is upgraded to 3.6.8.

W-20541600

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

Redelivery policy logging now includes additional context for troubleshooting.

W-20636028

The Tanuki Java Service Wrapper is upgraded to 3.6.4.

W-17051070

The RAML parser is upgraded to 1.1.10.

W-21768014

The OpenTelemetry SDK is upgraded to 1.60.1.

W-21808539

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

DataWeave now supports the private modifier on fun, var, ns, and type declarations to hide them from importers.

W-21148967

internal is no longer a reserved word and can now be used as an identifier in DataWeave scripts.

W-21508044

The compiler now reports an error when overloads of the same function declare different visibility modifiers.

W-21362539

StackOverflowError no longer occurs in the type checker when resolving intersections of unbound type parameters.

W-20124753

Runtime errors no longer occur when invoking overloaded functions across modules.

W-21811015

Spurious type-check errors no longer occur when an optional key-value pair is assigned to a required one.

W-21351058

deferred values passed to the write function now terminate correctly.

W-20925604

Out-of-memory errors no longer occur when reading large text or CDATA sections with the indexed XML reader.

W-21006104

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
**4.11.5 Runtime Updates** For Mule runtime 4.11.5, the image name that corresponds with this fix is 4.11.5:4e.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

HTTP Server now supports Upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Test Connection for The HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the Host field.

W-21921687

The Spring Core library is upgraded to 6.2.18.

W-22169898

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
**4.9.18 Runtime Updates** For Mule runtime 4.9.18, the image name that corresponds with this fix is 4.9.18:3.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507
**4.6.31 Runtime Updates** For Mule runtime 4.6.31, the image name that corresponds with this fix is 4.6.31:3.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

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 per_app_java_bean_cache compatibility flag.

W-22417507
## [](#may-19-2026)May 19, 2026 The May 19 patch update for Mule versions 4.11.4, 4.10.5, 4.9.17, and 4.6.30 addresses a regression in the May 5 patch update. This patch includes all fixes from May 5 patch. ### Fixed Issues **4.11.4 Runtime Updates** For Mule runtime 4.11.4, the image name that corresponds with these fixes is 4.11.4:5e.
Issue Resolution ID

Workers running Edge Mule runtime versions on non-micro instance sizes now correctly allocate JVM heap memory.

W-22534602
**4.10.5 Runtime Updates** For Mule runtime 4.10.5, the image name that corresponds with these fixes is 4.10.5:8e.
Issue Resolution ID

Workers running Edge Mule runtime versions on non-micro instance sizes now correctly allocate JVM heap memory.

W-22534602
**4.9.17 Runtime Updates** For Mule runtime 4.9.17, the image name that corresponds with these fixes is 4.9.17:5.
Issue Resolution ID

Incoming header names no longer use strict CRLF validation when an HTTP configuration without a listener receives an HTTPS request, avoiding out-of-memory errors. In this scenario, Mule logs a warning entry in mule_ee.log, but the warning doesn’t affect application behavior.

W-22571733
**4.6.30 Runtime Updates** For Mule runtime 4.6.30, the image name that corresponds with these fixes is 4.6.30:5.
Issue Resolution ID

Incoming header names no longer use strict CRLF validation when an HTTP configuration without a listener receives an HTTPS request, avoiding out-of-memory errors. In this scenario, Mule logs a warning entry in mule_ee.log, but the warning doesn’t affect application behavior.

W-22571733
## [](#may-5-2026)May 5, 2026 ### What’s New **4.6, 4.9, and 4.11 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.30, 4.9.17, and 4.11.4** This release of 4.6.30, 4.9.17, and 4.11.4 includes Runtime Manager Agent 2.7.13. For information, see [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13). ### Fixed Issues **4.11.4 Runtime Updates** For Mule runtime 4.11.4, the image name that corresponds with this fix is 4.11.4:4e.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

Netty HTTP client NTLM authentication no longer fails due to missing TCP connection affinity during the handshake.

W-21615520

The plexus-utils library is upgraded to 4.0.3.

W-21774430

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21913252

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

Netty HTTP client no longer sends an incorrect WWW-Authenticate header during the NTLM authentication handshake.

W-21762949

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

A serialization error that could occur when deserializing data after a Mule runtime upgrade no longer occurs.

W-21951097

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
**4.9.17 Runtime Updates** For Mule runtime 4.9.17, the image name that corresponds with this fix is 4.9.17:4.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21795152

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
**4.6.30 Runtime Updates** For Mule runtime 4.6.30, the image name that corresponds with this fix is 4.6.30:4.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
## [](#april-7-2026)April 7, 2026 ### What’s New **4.6, 4.9, and 4.11 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.29, 4.9.16, and 4.11.3** This release of 4.6.29, 4.9.16, and 4.11.3 includes Runtime Manager Agent 2.7.11. For information, see [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11). ### Fixed Issues **4.11.3 Runtime Updates** For Mule runtime 4.11.3, the image name that corresponds with this fix is 4.11.3:4e.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

OpenTelemetry Direct streaming now supports FIPS-compatible keystore format.

W-20623905

A warning now appears when an OpenTelemetry property is incorrectly used as a deployment property.

W-21018072

NullPointerException 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.

W-20192960

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

HTTP Netty implementation performance is now improved.

W-20969515

HTTP Server no longer logs an error when a client closes an idle keep-alive connection.

W-21431822

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
**4.9.16 Runtime Updates** For Mule runtime 4.9.16, the image name that corresponds with this fix is 4.9.16:4.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

The Jackson Core library is upgraded to 2.18.6.

W-21420104

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
**4.6.29 Runtime Updates** For Mule runtime 4.6.29, the image name that corresponds with this fix is 4.6.29:6.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
## [](#march-3-2026)March 3, 2026 ### What’s New **4.6, 4.9, 4.10, and 4.11 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.28, 4.9.15, 4.10.5, and 4.11.2** This release of 4.6.28, 4.9.15, 4.10.5, and 4.11.2 includes Runtime Manager Agent 2.7.10. For information, see [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10). ### Fixed Issues **4.11.2 Runtime Updates** For Mule runtime 4.11.2, the image name that corresponds with this fix is 4.11.2:3e.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

XSD validations are now enabled by default during deployment.

W-21139633

Errors that are not MessagingException errors are no longer silenced.

W-21043969

The reactor.netty.version library is upgraded to 1.3.2.

W-3300013

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501

The Mapping Editor API now supports attributes in Anypoint Code Builder.

W-20662336

Updating the expression model in the Mapping Editor API now works correctly.

W-20611263
**4.10.5 Runtime Updates** For Mule runtime 4.10.5, the image name that corresponds with this fix is 4.10.5:2e.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

Streaming manager initialization failures no longer occur in certain scenarios.

W-20641469

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
**4.9.15 Runtime Updates** For Mule runtime 4.9.15, the image name that corresponds with this fix is 4.9.15:3.
Issue Resolution ID

Mule

The jakarta.mail library is upgraded to 1.6.8.

W-21138257

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

Errors that are not MessagingException errors are no longer silenced.

W-21043969

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." errors no longer occur when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
**4.6.28 Runtime Updates** For Mule runtime 4.6.28, the image name that corresponds with this fix is 4.6.28:3.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The tika-core library is upgraded to 3.2.3.

W-21179465

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
## [](#february-14-2026)February 14, 2026 ### Fixed Issues **4.11.1 Runtime Updates** For Mule runtime 4.11.1, the image name that corresponds with these fixes is 4.11.1:2e. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. **4.10.4 Runtime Updates** For Mule runtime 4.10.4, the image name that corresponds with these fixes is 4.10.4:1e. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. **4.9.14 Runtime Updates** For Mule runtime 4.9.14, the image name that corresponds with these fixes is 4.9.14:1. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. **4.6.27 Runtime Updates** For Mule runtime 4.6.27, the image name that corresponds with these fixes is 4.6.27:1. - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ## [](#february-6-2026)February 6, 2026 ### Fixed Issues **4.11.0 Runtime Updates** For Mule runtime 4.11.0, the image name that corresponds with this fix is 4.11.0:11e.
Issue Resolution ID

Anypoint Monitoring now processes logs with reduced latency.

W-20876620
**4.10.3 Runtime Updates** For Mule runtime 4.10.3, the image name that corresponds with this fix is 4.10.3:3e.
Issue Resolution ID

Anypoint Monitoring now processes logs with reduced latency.

W-20876620
**4.9.13 Runtime Updates** For Mule runtime 4.9.13, the image name that corresponds with this fix is 4.9.13:3.
Issue Resolution ID

Anypoint Monitoring now processes logs with reduced latency.

W-20876620
**4.8.6 Runtime Updates** For Mule runtime 4.8.6, the image name that corresponds with this fix is 4.8.6:13e.
Issue Resolution ID

Anypoint Monitoring now processes logs with reduced latency.

W-20876620
**4.6.26 Runtime Updates** For Mule runtime 4.6.26, the image name that corresponds with this fix is 4.6.26:3.
Issue Resolution ID

Anypoint Monitoring now processes logs with reduced latency.

W-20876620
## [](#february-4-2026)February 4, 2026 ### What’s New - Mule runtime engine 4.11.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **Runtime Manager Agent versions included in Runtime 4.11.0** This release of 4.11.0 includes Runtime Manager Agent 2.7.9. For information, see [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues **4.11.0 Runtime Updates** For Mule runtime 4.11.0, the image name that corresponds with this fix is 4.11.0:10e.
Issue Resolution ID

Mule

HTTP/2 connections now correctly multiplex when processing concurrent requests, reducing connection creation and latency.

W-19860076

The runtime now leverages the AST file for applications with the until-successful component instead of parsing configuration XML files.

W-20283146

Batch record deserialization no longer fails when a Netty exception occurs.

W-20552358

Inbound HTTP/2 header validation is now improved.

W-19873453

The org.apache.logging.log4j:log4j-core dependency is upgraded to 2.25.3.

W-20679050

Applications no longer experience infinite restart loops when CloudHub log files contain corrupted records.

W-20396002

DataWeave

AST scope navigation now works correctly for cross-file references when using the Tooling API.

W-20212809

A specific overload for isEmpty on binaries is now available to prevent implicit coercion to other types.

W-20049958

Materialized Java values are now cached to allow multiple executions using the same value.

W-20091279

Semantic tokens are now supported in the Tooling API.

W-19846990

NullPointerException no longer occurs when handling annotation types.

W-19853000

LogLevel documentation is now included directly in the code.

W-17800393

The commons-beanutils library is upgraded.

W-3300013

Base64 encoding and decoding now support payloads larger than memory.

W-18575719

Eager materialization is now supported on values, enabling caching of all exceptions inside the try function.

W-19717874

Avro enum, map, union, and fixed types are now supported as top-level elements.

W-19596039

WeaveCompiler now allows precompiling mappings and modules without validation or type checking.

W-19667273

Type check errors are now correctly reported when resolving type checking on subgraphs.

W-19564697

Lazy loading of source files is now enabled during binary compilation, avoiding unnecessary memory usage.

W-19594703

Type inference now works correctly when using the -- operator to subtract a key from an object.

W-19595907

Warning and error messages now propagate correctly between compilation phases.

W-19386849

Base types are now used to validate accepted values, preventing premature materialization.

W-18943395

Optional types now propagate correctly through chains of value selectors.

W-19272070

The syntax version is now added to TypeGraph and WeaveTypeResolution.

W-19271992

The classloader resource resolver now resolves paths correctly on Windows systems.

W-19407283
## [](#february-3-2026)February 3, 2026 ### What’s New **4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.26, 4.9.13, and 4.10.3** This release of 4.6.26, 4.9.13, and 4.10.3 includes Runtime Manager Agent 2.7.9. For information, see [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues **4.10.3 Runtime Updates** For Mule runtime 4.10.3, the image name that corresponds with this fix is 4.10.3:2e.
Issue Resolution ID

Mule

HTTP/2 handling now correctly multiplexes connections during concurrent request processing. Previously, a failure to multiplex caused excessive connection creation and significantly increased latency.

W-19860076

Improved the validation logic for inbound HTTP/2 headers to ensure better protocol compliance and security.

W-19873453

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

The org.apache.cxf:cxf-core library is upgraded to 3.6.9.

W-20659822

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

Applications no longer experience infinite restart loops when CloudHub log files contain corrupted records.

W-20396002

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
**4.9.13 Runtime Updates** For Mule runtime 4.9.13, the image name that corresponds with this fix is 4.9.13:2e.
Issue Resolution ID

Mule

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

Fastutil is now replaced with fastutil-core.

W-20729870

Applications no longer experience infinite restart loops when CloudHub log files contain corrupted records.

W-20396002

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
**4.6.26 Runtime Updates** For Mule runtime 4.6.26, the image name that corresponds with this fix is 4.6.26:2.
Issue Resolution ID

Mule

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Fastutil is now replaced with fastutil-core.

W-20729870

Applications no longer experience infinite restart loops when CloudHub log files contain corrupted records.

W-20396002
## [](#january-6-2026)January 6, 2026 ### What’s New **4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.25, 4.9.12, and 4.10.2** This release of 4.6.25, 4.9.12, and 4.10.2 includes Runtime Manager Agent 2.7.9. For information, see [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues **4.10.2 Runtime Updates** For Mule runtime 4.10.2, the image name that corresponds with this fix is 4.10.2:5e.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing not longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

A memory leak after application undeployment no longer occurs when using connections from configurations defined in a domain.

W-13521171

Connections now close properly on the server side after an HTTP/2 client disconnects.

W-19861068

The JMS connector no longer closes XA-enlisted connections.

W-20266983

Connections from providers that implement both CachedConnectionProvider and XaTransactionalConnectionProvider are no longer cached if the provided connection is XA.

W-20267068

The alert context in the DIAF file is now reset after the configured time interval expires.

W-20140036

The HTTP Server now returns a 400 error when the HTTP/1 to HTTP/2 upgrade mechanism receives an invalid HTTP2-Settings header.

W-19895731

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The Apache Commons Lang library included in the distribution is upgraded.

W-20004786

DataWeave grammar transformation performance is improved.

W-19840284

Memory usage is improved for binary compilation and AST-related utilities.

W-19706956
**4.9.12 Runtime Updates** For Mule runtime 4.9.12, the image name that corresponds with this fix is 4.9.12:5e.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549
**4.6.25 Runtime Updates** For Mule runtime 4.6.25, the image name that corresponds with this fix is 4.6.25:5.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

DataWeave

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20618375

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
## [](#december-2-2025)December 2, 2025 ### What’s New **4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.6.24, 4.9.11, and 4.10.1** This release of 4.6.24, 4.9.11, and 4.10.1 includes Runtime Manager Agent 2.7.8. For information, see [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8). ### Fixed Issues **4.10.1 Runtime Updates** For Mule runtime 4.10.1, the image name that corresponds with this fix is 4.10.1:13e. - The operating system is updated to the latest security patches. **4.9.11 Runtime Updates** For Mule runtime 4.9.11, the image name that corresponds with this fix is 4.9.11:7. - The operating system is updated to the latest security patches. **4.6.24 Runtime Updates** For Mule runtime 4.6.24, the image name that corresponds with this fix is 4.6.24:8. - The operating system is updated to the latest security patches. ## [](#november-4-2025)November 4, 2025 ### What’s New **4.4, 4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.4.0, 4.6.24, 4.9.11, and 4.10.1** This release of 4.4.0, 4.6.24, 4.9.11, and 4.10.1 includes Runtime Manager Agent 2.7.8. For information, see [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8). ### Fixed Issues **4.10.1 Runtime Updates** For Mule runtime 4.10.1, the image name that corresponds with these fixes is 4.10.1:10e.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.10, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.1.127.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

The Bump handlebars library is upgraded to 4.4.0.

W-1906465

The HTTP listener now correctly populates attributes.queryParams when using HTTP/2.

W-19802358

close_notify events sent by a server are now properly handled by the HTTP/2 client.

W-19973575

DataWeave

Materialization errors no longer occur in run function.

W-19884071

The org.apache.commons:commons-lang3 library is upgraded to 3.18.

W-19803454

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

The SnakeYAML library is upgraded.

W-19749213

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283

The -- operator now returns the correct type without the subtracted keys.

W-19595907

Debug logging is now enabled for DefaultLoggingService.

W-19650046

The take function no longer fails in streaming mode when n is larger than the array length.

W-19168279

The Java Module now supports object field access with different capitalizations.

W-19477334

The Runtime Compiler now uses the Parser Manager to look for resources provided as parameters.

W-19376888

A null check is now performed before closing the InputStream.

W-19395982

Parsing metrics printing now includes a missing line ending.

W-19440583

Constants are now used to prevent incorrect loader identifiers for binary compiled scripts.

W-18455133

Generated POM files now include license information.

W-19439330

SchemaProvider resolution on Types is improved to prevent Execution reference leaks.

W-19389019

The classloader weave resource resolver now uses the correct path in Windows environments.

W-19407283
**4.9.11 Runtime Updates** For Mule runtime 4.9.11, the image name that corresponds with these fixes is 4.9.11:4e.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

Starvation no longer occurs when sending HTTP responses that are generated slowly.

W-1982570

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.9, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
**4.6.24 Runtime Updates** For Mule runtime 4.6.24, the image name that corresponds with these fixes is 4.6.24:4.
Issue Resolution ID

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now properly honors the graceful shutdown timeout. In versions earlier than 4.11.0, you must enable this behavior using these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19340663

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.6, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException no longer thrown when DW serializes error.errorMessage in Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071
**4.4.0 Runtime Updates** For Mule runtime 4.4.0, the image name that corresponds with these fixes is 4.4.0-20250919-5. - The operating system is updated to the latest security patches. ## [](#october-2-2025)October 2, 2025 ### What’s New - Mule runtime engine 4.10.0 is now available. For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **4.4, 4.6, 4.9, and 4.10 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.4.0, 4.6.23, 4.9.10, and 4.10.0** This release of 4.4.0, 4.6.23, 4.9.10, and 4.10.0 includes Runtime Manager Agent 2.7.7. For information, see [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues **4.10.0 Runtime Updates** For Mule runtime 4.10.0, the image name that corresponds with these fixes is 4.10.3:2e.
Issue Resolution ID

Mule

The org.quartz-scheduler:quartz library is upgraded to 2.5.0.

W-17406808

The org.vibur:vibur-object-pool library is upgraded to 26.

W-17570586

The commons-beanutils:commons-beanutils library is upgraded to 1.10.0.

W-17571116

The jakarta-annotation library is upgraded to 2.1.1.

W-17927646

The Mockito monorepo is upgraded to 5.

W-18685961

The Log4j2 monorepo is upgraded to 2.25.1.

W-18834079

The Netty library is upgraded to 4.1.127.Final.

W-19559645

The Rhino library is upgraded to 1.8.0.

W-17636627

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
**4.9.10 Runtime Updates** For Mule runtime 4.9.10, the image name that corresponds with these fixes is 4.9.10:4e.
Issue Resolution ID

Mule

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The Handlebars library is upgraded to 4.4.0.

W-19064659

The org.apache.commons : commons-lang3 library is upgraded to 3.17.0.

W-19383955

The io.netty : netty-codec library is upgraded to 4.1.127.Final.

W-19568278

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

Scheduler name generation no longer breaks the platform logging aggregator when processor chains have null or empty names.

W-19432758

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
**4.6.23 Runtime Updates** For Mule runtime 4.6.23, the image name that corresponds with these fixes is 4.6.23:4.
Issue Resolution ID

The org.springframework library is upgraded to 5.3.45.

W-18603096

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

This release reverts the changes introduced in W-17340911.

W-17340911

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

Batch queuestore files now clean up correctly in rare load failure scenarios, such as out of memory errors.

W-17935223

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334

Module compilation performance is improved when running concurrently.

W-19376546
**4.4.0 Runtime Updates** For Mule runtime 4.4.0, the image name that corresponds with these fixes is 4.4.0:20250919-3.
Issue Resolution ID

BufferOverFlowException errors no longer occur when inter-node communication gets stuck in clusters with encryption under heavy load.

W-16517561

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164
## [](#september-5-2025)September 5, 2025
Updates for images 4.9.9:6e and 4.6.22:5 apply to Government Cloud only.
### Fixed Issues **4.9.9 Runtime Updates** For Mule runtime 4.9.9, the image name that corresponds with these fixes is 4.9.9:6e.
Issue Resolution ID

Anypoint Monitoring metrics are now generated correctly.

W-19548148
**4.6.22 Runtime Updates** For Mule runtime 4.6.22, the image name that corresponds with these fixes is 4.6.22:5.
Issue Resolution ID

Anypoint Monitoring metrics are now generated correctly.

W-19548148
## [](#september-2-2025)September 2, 2025 ### What’s New **4.4, 4.6, and 4.9 Runtime Updates** - Updated to the latest operating system security patches. **Runtime Manager Agent versions included in Runtime 4.4.0, 4.6.22, and 4.9.9** This release of 4.4.0, 4.6.21, and 4.9.8 includes Runtime Manager Agent 2.7.7. For information, see [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues **4.9.9 Runtime Updates** For Mule runtime 4.9.9, the image name that corresponds with these fixes is 4.9.9:5e.
Issue Resolution ID

Mule

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

io.projectreactor.netty : reactor-netty-http is upgraded to 1.2.8.

W-19074903

Component annotations, such as location, are no longer overwritten by other components.

W-18269859

org.apache.commons : commons-lang3 is upgraded to 3.18.0.

W-19059553

DataWeave

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

W-19376546
**4.6.22 Runtime Updates** For Mule runtime 4.6.22, the image name that corresponds with these fixes is 4.6.22:4.
Issue Resolution ID

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
**4.4.0 Runtime Updates** For Mule runtime 4.4.0, the image name that corresponds with these fixes is 4.4.0:20250829-1.
Issue Resolution ID

Performance degradation no longer occurs when using repeatable streaming.

W-19175330
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Coda Connector Release Notes Anypoint Connector for Coda (Coda Connector) enables Mule applications to access the Coda API. Guide: [Coda Connector User Guide](https://docs.mulesoft.com/coda-connector/latest/) ## [](#0-1-23)0.1.23 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-22)0.1.22 **August 19, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-21)0.1.21 **June 30, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **December 16, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/coda-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [Coda Connector User Guide](https://docs.mulesoft.com/coda-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
## [](#see-also)See Also - [Coda Connector User Guide](https://docs.mulesoft.com/coda-connector/latest/) - [Coda Connector Reference](https://docs.mulesoft.com/coda-connector/latest/coda-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Commerce Cloud B2C Shop Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Commerce Cloud B2C Shop APIs (B2C Shop Connector) provides a quick and easy way to integrate with Salesforce Commerce Cloud B2C Shop API endpoints. Unresolved include directive in modules/ROOT/pages/connector/shop-api-connector-release-notes-mule-4.adoc - include::connectors::partial$b2c-connectors-deprecated.adoc\[\] Guide: [Commerce Cloud B2C Shop Connector User Guide](https://docs.mulesoft.com/jp/commerce-cloud-shop-api-connector/latest/) ## [](#2-1-2)2.1.2 **April 25, 2025** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.6.14 and later

OpenJDK

8, 11, and 17
## [](#2-1-1)2.1.1 **March 7, 2024** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Internal dependencies are upgraded.

W-13607753
## [](#2-1-0)2.1.0 **February 27, 2023** ### What’s New - B2C Shop Connector now supports the following new operations: - **Authenticate Customer** - **Get Access Token** - **Logout Customer** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

JDK

1.8.x
## [](#2-0-1-deprecated)2.0.1 (Deprecated) **March 8, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

JDK

1.8.x
### Fixed Issues
Issue ID

Minor security bugs.

W-10362098
## [](#2-0-0-deprecated)2.0.0 (Deprecated) **March 2, 2021** ### [](#compatibility-5)Compatibility B2C Shop Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

JDK

1.8.x
### [](#features)Features - B2C Shop Connector provides access to Salesforce Commerce Cloud B2C Shop APIs for the below workflows:
Workflow Version

Shopper Customer

0.0.24

Shopper Baskets

0.2.1

Shopper Orders

0.0.27

Shopper Promotions

1.0.18

Shopper Search

1.0.23

Shopper Product

0.0.13

Shopper Gift Certificates

1.0.9
- The connector is updated with the latest Salesforce Commerce B2C Shop APIs. ### [](#fixed-in-this-release)Fixed In This Release - Fixed the broken Shopper Customer endpoints. ## [](#1-0-0-deprecated)1.0.0 (Deprecated) **January 4, 2021** New connector. ### [](#compatibility-6)Compatibility B2C Shop Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

JDK

1.8.x
### [](#features-2)Features B2C Shop Connector provides access to Salesforce Commerce Cloud B2C Shop APIs for the following workflows:
Workflow Version

Shopper Customer

0.0.23

Shopper Baskets

0.2.1

Shopper Orders

0.0.27

Shopper Promotions

1.0.18

Shopper Search

1.0.23

Shopper Product

0.0.13

Shopper Gift Certificates

1.0.9
### [](#fixed-issues-3)Fixed Issues None. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Compression Module Release Notes for Mule 4 Compression module provides functionality for compressing and decompressing data. Guide: [Compression Module User Guide](https://docs.mulesoft.com/jp/compression-module/latest/) ## [](#2-2-9)2.2.9 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

Open JDK

8, 11, and 17
## [](#2-2-8)2.2.8 **July 24, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

Open JDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Apache Commons Lang library is upgraded to version 3.20.0 to address reported security vulnerabilities.

W-23441567
## [](#2-2-7)2.2.7 **May 8, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Open JDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.19.0 to address CVE-2025-48924.

W-22373976

The Decompress operation now fully supports multi-member GZIP files, correctly returning the complete content across all concatenated streams.

W-21275433
## [](#2-2-6)2.2.6 **September 30, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Open JDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated org.apache.commons:commons-lang3 from 3.12.0 to 3.19.0.

W-19760502

Updated org.mule.sdk:mule-sdk-api from 0.7.0 to 0.11.9.

W-19760502
## [](#2-2-5-deprecated)2.2.5 (Deprecated) **September 19, 2025** This version is deprecated. All of the features and fixed issues for this version are in version 2.2.6. ## [](#2-2-4)2.2.4 **May 8, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

Open JDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Upgraded commons-compress to version 1.26.0.

W-15605215
## [](#2-2-3)2.2.3 **January 8, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

Open JDK

8, 11, and 17
## [](#2-2-2-skipped)2.2.2 (Skipped) This version is skipped. The features and fixed issues for this version are in version 2.2.3. ## [](#2-2-1)2.2.1 **August 23, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The Compression module now throws a RuntimeException error without error types during file compression. The module throws these exceptions from the function that consumes the output of the Compress and Archive operations.

W-11390500
## [](#2-2-0)2.2.0 **July 8, 2022** ### What’s New - Compression module **Archive** and **Compress** operations have a new **Force ZIP64** parameter that enables you to archive or compress files and byte arrays greater than 4 GB. ### Compatibility
Software Version

Mule

4.1.1 and later
## [](#2-1-2)2.1.2 **January 28, 2022** ### [](#fixed-issues-6)Fixed Issues
Issue Description

COMPM-13

Upgraded commons-compress to 1.21.
## [](#2-1-1)2.1.1 **June 25, 2020** ### [](#fixed-issues-7)Fixed Issues
Issue Description

COMPM-10

Fixed leak in compression stream.

Upgraded commons-compress to 1.20.
## [](#2-1-0)2.1.0 **March 2020** ### [](#new-features-and-enhancements)New Features and Enhancements Enable the possibility of configuring the streaming strategy for extract operation. ### [](#fixed-issues-8)Fixed Issues
Issue Description

MULE-17898

Review all extensions that return maps of streams.
## [](#2-0-3)2.0.3 **October 2019** ### [](#fixed-issues-9)Fixed Issues
Issue Description

MULE-17413

Upgrade commons-compress to 1.19.
## [](#2-0-2)2.0.2 **December 2018** - Improvements to reduce memory footprint - Improved support for repeatable streaming ### [](#fixed-issues-10)Fixed Issues
Issue Description

MULE-16138

Compression module doesn’t return repeatable streams.
## [](#2-0-1)2.0.1 **October 2018** Fixed major issue when writting compressed streams. ### [](#fixed-issues-11)Fixed Issues
Issue Description

MULE-15858

Zip streams are not being closed after creation.
## [](#2-0-0)2.0.0 **September 2018** ### [](#new-features-and-enhancements-2)New Features and Enhancements To provide a better experience using this module, MuleSoft added a new API to support archiver compression formats with a new set of operations. It retains the experience for compressing and decompressing files for each of the available formats without losing any of the features that the format associated algorithm provides. This change enables the possibility of adding more compression formats in a simple way. This version now supports the most widely used compression format: ZIP. The Gzip format is still supported. ### [](#fixed-issues-12)Fixed Issues
Issue Description

MULE-15082

Upgrade commons-lang3 to 3.7
## [](#1-0-0)1.0.0 **May 2018** ### [](#new-features-and-enhancements-3)New Features and Enhancements This module provides functionality for compressing and uncompressing data in the gzip format. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Confluent Schema Registry Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Confluent Schema Registry (Confluent Schema Registry Connector) enables interaction with Confluent’s Schema Registry to save and retrieve avro schemas to reduce the size of an avro message while it transports through the network. Guide: [Confluent Schema Registry Connector User Guide](https://docs.mulesoft.com/confluent-schema-registry-connector/latest/) ## [](#1-2-4)1.2.4 **October 23, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson libraries are upgraded to version 2.22.4.

  • The json library is upgraded to version 20260814.

  • The connector now explicitly resolves the commons-lang3 library to version 3.21.0 to prevent a consumer-side version conflict.

W-24590619
## [](#1-2-3)1.2.3 **October 13, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

Equivalent dynamic configurations now reuse the same Mule cache key when their Avro schema parse-cache settings match, which prevents unnecessary HTTP-client resources.

W-24507323

These libraries are upgraded to address reported security vulnerabilities:

  • The guava library is upgraded to version 33.7.2-jre.

  • The commons-lang3 library is upgraded to version 3.21.0.

W-24373980
## [](#1-2-2)1.2.2 **September 29, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core library is upgraded to version 2.22.3.

  • The jackson-databind library is upgraded to version 2.22.3.

  • The guava library is upgraded to version 33.7.1-jre.

W-24309351
## [](#1-2-1)1.2.1 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
## [](#1-2-0)1.2.0 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - The **Replace id with AVRO schema** operation can now optionally cache parsed Avro schemas so that, when the cache is enabled, each schema is parsed only once instead of on every message. The cache is disabled by default; enable it in the connector configuration by setting **Maximum size** to the number of distinct schemas to retain (0, the default, keeps the cache disabled). Optionally set **Time to live** and **Time to live time unit** to evict schemas that go idle. Enabling the cache is recommended for high-throughput flows that repeatedly resolve a bounded set of schemas — whether a single schema or a fixed group of them — such as streaming Kafka records off one or a handful of subjects, where it avoids redundant parsing. Set **Maximum size** to at least the number of distinct schemas the flow handles so all of them stay cached. For more information, see [Config](https://docs.mulesoft.com/confluent-schema-registry-connector/latest/confluent-schema-registry-connector-reference#config). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

Avro schema processing is improved: the connector now avoids re-parsing Avro schemas on every message by caching parsed schemas, which reduces redundant work when a bounded set of schemas is resolved repeatedly under load.

W-22611211
## [](#1-1-5)1.1.5 **May 15, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core:jackson-core component is upgraded to 2.21.1.

W-22383185

The com.fasterxml.jackson.core:jackson-databind component is upgraded to 2.21.1.

W-22383185

The com.google.guava:guava component is upgraded to 33.5.0-jre.

W-22383187
## [](#1-1-4)1.1.4 **April 29, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

Avro messages are no longer incorrectly split when payload bytes happen to match the Confluent Wire Format header pattern. The connector now uses stream-based Avro decoding to determine record boundaries.

W-21892043

The org.apache.logging.log4j:log4j-* component is upgraded to 2.25.4.

W-22008656
## [](#1-1-3)1.1.3 **March 19, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core:jackson-databind component is upgraded to 2.21.1.

W-21466248

The com.fasterxml.jackson.core:jackson-core component is upgraded to 2.21.1.

W-21466248

The org.apache.kafka:kafka-clients component is upgraded to 3.9.2.

W-21466248
## [](#1-1-2)1.1.2 **February 25, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

The org.apache.avro:avro component is upgraded to 1.11.5.

W-21240549

The org.apache.commons:commons-compress component is upgraded to 1.28.0.

W-21240549

The commons-io:commons-io component is upgraded to 2.21.0.

W-21240549

The org.json:json component is upgraded to 20251224.

W-21240549

The org.apache.logging.log4j:log4j-* component is upgraded to 2.25.3.

W-21240549

The com.fasterxml.jackson.core:jackson-* component is upgraded to 2.20.1.

W-21240549

The org.apache.commons:commons-lang3 component is upgraded to 3.20.0.

W-21240549
## [](#1-1-1)1.1.1 **May 16, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-16206150
## [](#1-1-0)1.1.0 **March 24, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17137979

The log4j dependency is upgraded to version 2.17.1 to address reported security vulnerabilities.

W-17983831
## [](#1-0-13)1.0.13 **July 12, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

The Replace AVRO schema with id and Replace id with AVRO schema operations no longer face issues when the Schema ID field is null.

W-16206150
## [](#1-0-12)1.0.12 **June 27, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

The Replace AVRO schema with id and Replace id with AVRO schema operations now process lists of records correctly.

W-15282008
## [](#1-0-11)1.0.11 **April 29, 2024** ### What’s New - This connector is now compatible with Java 17. - This connector is now FIPS 140-2 compliant. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Confluent Schema Registry

6.0.x
## [](#1-0-10)1.0.10 **January 22, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

The org.json component is upgraded from version 20230227 to version 20231013 to address reported security vulnerabilities.

W-14462883

The org.apache.avro component is upgraded from version 1.11.0 to version 1.11.3 to address reported security vulnerabilities.

W-14462860

The com.fasterxml.jackson.core component is upgraded from version 2.14.2 to version 2.15.0 to address reported security vulnerabilities.

W-14462876
## [](#1-0-9)1.0.9 **May 15, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core library is upgraded to version 2.15.0 to address reported security vulnerabilities.

W-12665860
## [](#1-0-8)1.0.8 **April 13, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.11.3 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920499
## [](#1-0-7)1.0.7 **January 10, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9902
## [](#1-0-6)1.0.6 **December 21, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9677
## [](#1-0-5)1.0.5 **December 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9591
## [](#1-0-4)1.0.4 **December 13, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9559
## [](#1-0-3)1.0.3 **September 17, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue ID

There was a dependency issue in Design Center.

CONN-8849
## [](#1-0-2)1.0.2 **September 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### Fixed Issues
Issue ID

Updated dependencies.

CONN-8849
## [](#1-0-1)1.0.1 **August 11, 2021** ### [](#compatibility-24)Compatibility Confluent Schema Registry Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### [](#fixed-issues-22)Fixed Issues - Fixed all reported security vulnerabilities. ## [](#1-0-0)1.0.0 **August 2, 2021** ### [](#compatibility-25)Compatibility Confluent Schema Registry Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Confluent Schema Registry

6.0.x
### [](#new-features)New Features New connector. For a list of supported configurations and operations, see the Confluent Schema Registry Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Connector Builder Release Notes Use Connector Builder to create your own connectors easily. Connector Builder is an extension that streamlines and accelerates connector development by creating connectors either from an API specification (OAS 3.0), AI assistance (available when using Cursor), or MCP tools (available when using Cursor). These connectors integrate with SaaS applications that use HTTP-based connectivity. For more information, see [Connector Builder Overview](https://docs.mulesoft.com/connector-builder/). ## [](#1-5-2)1.5.2 **September 21, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule runtime engine

4.10 and later
## [](#1-5-0)1.5.0 **July 22, 2026** ### What’s New - Connector Builder now includes usage telemetry to help improve the product. For more information, see [Telemetry in Connector Builder](https://docs.mulesoft.com/connector-builder/telemetry). - After the latest pre-release (Connector Builder 1.4.0), Connector Builder again supports generating Anypoint connectors alongside Flow connectors. ### Compatibility
Software Version

Mule runtime engine

4.10 and later
## [](#1-4-0)1.4.0 **June 2, 2026**
Connector Builder 1.4 is a pre-release that supports creating Flow connectors only. To create Anypoint connectors, use any other version of Connector Builder.
### What’s New - You can now use Connector Builder to create Flow connectors that run in Salesforce Flow. All Connector Builder features are available for both Anypoint and Flow connectors. - These new MCP tools are available for use in Connector Builder. See [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). - `uc_get_test_generation_info` See [Generate Tests With MCP Tools](https://docs.mulesoft.com/connector-builder/testing-connectors#generate-tests-with-mcp-tools). - `uc_generate_tests` See [Generate Tests With MCP Tools](https://docs.mulesoft.com/connector-builder/testing-connectors#generate-tests-with-mcp-tools). - These MCP tools are renamed in this version. - `uc_generate_api_spec` is renamed to `uc_manage_api_spec`. The renamed tool also supports research-only and validation modes. See [Generate Base Connectivity with MCP Tools](https://docs.mulesoft.com/connector-builder/base-connectivity#generate-base-connectivity-with-mcp-tools). - `uc_publish_connector` is renamed to `uc_connector_lifecycle`. The renamed tool supports both `build` and `publish` actions. See [Package Connectors with MCP Tools](https://docs.mulesoft.com/connector-builder/packaging-connectors#package-connectors-with-mcp-tools) and [Release Connectors to Anypoint Platform with MCP Tools](https://docs.mulesoft.com/connector-builder/releasing-connectors#release-connectors-to-anypoint-platform-with-mcp-tools). - You can now execute operations directly from the editor at design time using the Try It panel, without packaging or deploying the connector. The Try It panel is available for all operations, regardless of platform. See [Execute Operations Using the Try It Panel](https://docs.mulesoft.com/connector-builder/operations#execute-operations-try-it). ### Compatibility
Software Version

Mule runtime engine

4.10 and later
## [](#1-3-0)1.3.0 **March 6, 2026** ### What’s New - These new MCP tools are available for use in Connector Builder. See [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). - `uc_add_pagination` See [Define Pagination with MCP Tools](https://docs.mulesoft.com/connector-builder/pagination#define-pagination-with-mcp-tools). - `uc_list_connection_profiles` See [List Connection Profiles with MCP Tools](https://docs.mulesoft.com/connector-builder/connections#list-connection-profiles-with-mcp-tools). - `uc_manage_operations` See [Manage Operations with MCP Tools](https://docs.mulesoft.com/connector-builder/operations#manage-operations-with-mcp-tools). - `uc_publish_connector` See [Release Connectors to Anypoint Platform with MCP Tools](https://docs.mulesoft.com/connector-builder/releasing-connectors#release-connectors-to-anypoint-platform-with-mcp-tools). - You can now create connection profiles in Connector Builder. See [Use Connection Profiles](https://docs.mulesoft.com/connector-builder/connections#use-connection-profiles). - You can now generate tests for your Anypoint Connectors. See [Testing Connectors](https://docs.mulesoft.com/connector-builder/testing-connectors). - You can now specify your own base package and Maven group ID for connectors, rather than using the default values (`com::mulesoft::connectivity` for the base package and `com.mulesoft.connectivity` for the Maven group ID). - The UI for creating a new project is improved. See [Base Connectivity](https://docs.mulesoft.com/connector-builder/base-connectivity). ### Compatibility
Software Version

Mule runtime engine

4.10 and later
## [](#1-2-0)1.2.0 **December 18, 2025** ### What’s New - Connector Builder now automatically performs pre-publish validation tasks before publishing connectors to Anypoint Exchange. The improved publishing workflow checks and updates `pom.xml` files to validate group IDs and distribution management settings. It also checks `settings.xml` for Anypoint credentials configuration and provides code snippets to help you configure authentication. Any formatting errors in these files are now displayed directly in the UI for quick resolution. - Version information is now retrieved from the Language Server instead of the CLI, improving accuracy and reliability of dependency version management in project metadata. - Connector name validation now enforces a 20-character limit to prevent malfunction during connector operations. - The default Maven repository ID in the Anypoint `pom.xml` file is now set to `Repository`. - Maven profiles are added to configure private Exchange deployment and remove unnecessary artifacts during publishing. ### Compatibility
Software Version

Mule runtime engine

4.10 and later
### Fixed Issues
Issue Resolution ID

Text in operation types no longer overflows and is readable for all transformed operations, including paginated CCM operations.

W-20295471

Version comparison logic during project regeneration now properly detects version mismatches and displays correct values in comparison pop-ups.

W-20406985
## [](#1-1-1)1.1.1 **December 18, 2025** The features and fixed issues for this version are in version 1.2.0. ## [](#1-1-0)1.1.0 **November 20, 2025** ### What’s New - You can now use the MuleSoft MCP Server to build connectors with Connector Builder. For more information, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools) and [Generate Base Connectivity with MCP Tools](https://docs.mulesoft.com/connector-builder/base-connectivity#generate-base-connectivity-with-mcp-tools). These new MCP tools are available for use in Connector Builder. - `uc_create_connector_workflow` - `uc_generate_api_spec` - `uc_generate_connector` - You can now easily publish connectors to Anypoint Exchange with the improved UI, which clearly guides you through each step of the publishing process. For more information, see [Release Connectors to Anypoint Platform](https://docs.mulesoft.com/connector-builder/releasing-connectors#release-connectors-to-anypoint-platform). ### Compatibility
Software Version

Mule runtime engine

4.10 and later
## [](#1-0-0)1.0.0 **October 22, 2025** ### What’s New - Connector Builder is now generally available. ### Compatibility
Software Version

Mule runtime engine

4.10 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting Connector Builder](https://docs.mulesoft.com/connector-builder/troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Credential Injection API Key The Credential Injection API Key policy injects an API key or client credentials headers into outgoing requests. For configuration details, see [Credential Injection API Key Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-api-key). ## [](#september-09-2025)September 09, 2025 ### What’s New - Credential Injection API Key policy implementation version 1.0.1 is now supported by Omni Gateway. - Credential Injection API Key policy definition version 1.0.0 is now supported by Omni Gateway. # Credential Injection Basic Authentication The Credential Injection Basic Authentication policy injects a basic authorization header into outgoing requests. For configuration details, see [Credential Injection Basic Authentication Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-basic-auth). ## [](#february-24-2025)February 24, 2025 ### What’s New - Credential Injection Basic Authentication policy implementation version 1.0.0 is now supported by Omni Gateway. - Credential Injection Basic Authentication policy definition version 1.0.0 is now supported by Omni Gateway. # Credential Injection JWT Generation The Credential Injection JWT Generation policy generates and injects a JWT token into outgoing requests. For configuration details, see [Credential Injection JWT Generation Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-jwt-generation). ## [](#december-19-2025)December 19, 2025 ### What’s New - Credential Injection JWT Generation policy implementation version 1.0.0 is now supported by Omni Gateway. - Credential Injection JWT Generation policy definition version 1.0.0 is now supported by Omni Gateway. # Credential Injection OAuth 2.0 The Credential Injection OAuth 2.0 policy injects an OAuth 2.0 authorization header into outgoing requests. For configuration details, see [Credential Injection OAuth 2.0 Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-oauth). ## [](#september-2-2026)September 2, 2026 ### What’s New - The policy now supports adding custom parameters, such as `audience`, to the OAuth 2.0 token request body. Each parameter has a `name` and a `value`, where the `value` can be a static string or a DataWeave expression. - Credential Injection OAuth 2.0 policy implementation version 1.2.1 is now supported by Omni Gateway. - Credential Injection OAuth 2.0 policy definition version 1.2.1 is now supported by Omni Gateway. ## [](#november-20-2025)November 20, 2025 ### What’s New - Credential Injection OAuth 2.0 policy implementation version 1.2.0 is now supported by Omni Gateway. - Credential Injection OAuth 2.0 policy definition version 1.2.0 is now supported by Omni Gateway. # Cross-Origin Resource Sharing ## [](#1-3-3)1.3.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-2-2)1.2.2 **April 4, 2023** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed issues - Request payloads are no longer returned in the response when the policy is applied with specific origins and a request is performed with an unknown origin. ## [](#1-2-1)1.2.1 **June 6, 2022** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-2)Fixed issues When policy is configured with a wildcard origin (`*`) and allowing credentials, the Origin returned is the wildcard itself, and not the request’s origin as stated by the CORS specification. ## [](#1-3-1)1.3.1 **June 1, 2022** ### [](#fixed-issues-3)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-3-0)1.3.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-2-0)1.2.0 **October 8, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-4)Fixed issues The policy deployment fails when the CORS policy is applied to an API whose HTTP Listener configuration is deployed in a Mule domain, and that API uses Mule runtime engine v4.1.x. This is because both the domain and the policy export the same internal package. ### [](#new-features-and-enhancements-2)New Features and Enhancements - The CORS policy now supports an **value in the `Origins` and `Headers` fields. An** signifies that there are no restrictions in the origin and header fields of the API request. ## [](#1-1-5)1.1.5 **July 8, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-5)Fixed issues - When the CORS Policy is applied to an API whose HTTP Listener configuration is in a Mule Domain, the policy deployment fails. This is because both the domain and the policy export the same internal package. ## [](#1-1-4)1.1.4 **Apr 30, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - The CORS policy business logic is now completely modified to improve performance. - Several performance improvements are made to the header manipulation engine. ### [](#fixed-issues-6)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-1-3)1.1.3 **Jul 12, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Several performance improvements were introduced in this release. ### [](#fixed-issues-7)Fixed Issues - CORS policy does not try to duplicate Access-Controll-Allow-Origin header anymore. - CORS policy now only returns HTTP method selected as allowed in the Access-Control-Allow-Methods header. ## [](#1-1-2)1.1.2 **Apr 26, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Several performance improvements were introduced in this release. ## [](#1-1-1)1.1.1 **Dec 05, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - No new features were added in this version. ### [](#fixed-issues-8)Fixed Issues - The CORS Policy does not throw a 500 Server Error anymore if the content-type is not specified in the request. ## [](#1-1-0)1.1.0 **Jun 25, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Reduced error-handling verbosity in templates. - The transformations of HTTP attributes are now based on a specified output type. ### [](#fixed-issues-9)Fixed Issues - Fixed missing groupId for proxy samples dependency. ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-10)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [CORS Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-cors) - [Known Issues](https://help.salesforce.com/s/issues) # Cross-Origin Resource Sharing (CORS) The Cross-Origin Resource Sharing (CORS) policy enables access to resources residing in external domains. For configuration details, see [Cross-Origin Resource Sharing (CORS) Policy](https://docs.mulesoft.com/gateway/latest/policies-included-cors). ## [](#october-1-2026)October 1, 2026 ### What’s New - Cross-Origin Resource Sharing (CORS) policy definition version 1.3.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - Cross-Origin Resource Sharing (CORS) policy implementation version 1.2.1 is now supported by Omni Gateway. - Cross-Origin Resource Sharing (CORS) policy definition version 1.3.1 is now supported by Omni Gateway. # CrowdStrike AIDR Guardrails Policy The CrowdStrike AIDR Guardrails policy evaluates OpenAI-format LLM prompts and responses against CrowdStrike Falcon AI Detection and Response (AIDR), rejecting or redacting flagged content. For configuration details, see [CrowdStrike AIDR Guardrails Policy](https://docs.mulesoft.com/gateway/latest/policies-included-crowdstrike-aidr-guardrails). ## [](#october-15-2026)October 15, 2026 ### What’s New - CrowdStrike AIDR Guardrails policy implementation version 1.0.0 is now supported by Omni Gateway. - CrowdStrike AIDR Guardrails policy definition version 1.0.0 is now supported by Omni Gateway. # Cryptography Module Release Notes for Mule 4 Cryptography module provides cryptography capabilities to a Mule application. Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Cryptography Module User Guide](https://docs.mulesoft.com/cryptography-module/latest/) ## [](#2-2-2)2.2.2 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
## [](#2-2-1)2.2.1 **August 13, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - The Mule Encryption library is upgraded to 1.9.6. ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
## [](#2-2-0)2.2.0 **July 24, 2026** ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

PGP Encrypt, Decrypt, Sign, and Binary to Armored operations now report the security provider’s actual rejection reason (for example, a FIPS RSA PKCS1.5 encryption disallowed message) instead of a generic error, and a fatal error raised during background processing is no longer suppressed and returned as an empty successful result.

W-22503911

PGP key fingerprints shown in error messages now retain their leading zeros (for example, 05E124136361D538 instead of 5E124136361D538), matching the configured 16-character key ID.

W-22547796
## [](#2-1-3)2.1.3 **July 24, 2026** ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The XML Decrypt operation using asymmetric keys no longer fails with a null pointer error when it is the first XML operation to run after a Mule runtime starts.

W-22713999
## [](#2-1-2)2.1.2 **May 15, 2026** ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

JCE keystores located in absolute filesystem paths now load correctly.

W-22213108

JCE Sign and Validate operations now report CRYPTO:SIGNATURE and CRYPTO:VALIDATION errors (instead of MULE:CRITICAL) when the JCE provider rejects an algorithm, such as DSA signing in FIPS mode.

W-22502254
## [](#2-1-1)2.1.1 **April 14, 2026** ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Improved memory usage by processing InputStream data in chunks instead of loading entire payloads into memory at once, reducing heap pressure during JCE Sign, Verify, Encrypt, and Decrypt operations.

W-21312272

Improved InputStream handling in PGP Decrypt operations using an asynchronous piped stream approach, preventing resource leaks and ensuring proper cleanup on both success and error paths.

W-14996199

Enhanced resource loading to use a more reliable classpath resource resolution mechanism, improving compatibility across different deployment scenarios.

W-21348318
## [](#2-1-0)2.1.0 **January 23, 2026** ### What’s New Cryptography Module 2.1.0 enhances compatibility with FIPS 140-3 standards and Java 17, providing more robust validation and improved error handling for secure environments. - Improved FIPS 140-3 compatibility with Bouncy Castle FIPS security provider v2+. - Added proactive validation of cryptographic algorithms for PGP operations when running in FIPS environments to provide earlier and clearer errors when unsupported algorithms are detected. - Deprecated the global XMLDSig security provider registration mechanism which is no longer supported in Java 17 environments. - Preserved existing system properties for backward compatibility while marking them as deprecated and discouraged for use in FIPS-bound deployments. For details about migrating existing applications and understanding FIPS-related limitations, see [Upgrading Cryptography Module](https://docs.mulesoft.com/cryptography-module/latest/cryptography-module-upgrade). ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Enhanced validation and error reporting for PGP operations in FIPS-compliant environments ensure that you receive immediate and clear feedback regarding unsupported configurations. Additionally, global security provider registration issues no longer occur when running in Java 17 environments, which ensures stable cryptographic operations.

W-20347586

The org.apache.commons:commons-lang3 dependency is removed.

W-20671542
## [](#2-0-0)2.0.0 **May 28, 2025** ### What’s New Cryptography Module 2.0.0 brings important updates, including: - Updating default values for connector operations - Migrating your PGP Keyring to AES-Encrypted keys when operating in FIPS mode - Using different key pairs for Sign, Encrypt, and Decrypt operations to enhance security - Using password-based encryption - Using BCFKS as the required keystore and truststore type - Specifying algorithms dynamically - Registering the XMLDSig Security Provider - Enabling compatibility for Decrypt or Validate operations without KDF parameters For details, refer to [Upgrading Cryptography Module](https://docs.mulesoft.com/cryptography-module/latest/cryptography-module-upgrade). ### Compatibility
Software Version

Mule

4.4 and later

OpenJDK

8, 11, and 17
## [](#1-3-22)1.3.22 **November 13, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.17.0.

W-17024694

The org.apache.commons:commons-io library is upgraded to version 2.17.0.

W-17024694
## [](#1-3-21)1.3.21 **August 15, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer throws the No such provider BC error when running multiple flows in parallel.

W-15108894

The org.apache.commons:commons-lang3 library is upgraded to version 3.16.0.

W-15108894

The org.mule.sdk:mule-sdk-api library is upgraded to version 0.9.2.

W-15108894
## [](#1-3-20)1.3.20 **February 7, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

PGP operations now support large payloads.

W-14118536
## [](#1-3-19)1.3.19 **January 19, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The PGP Encrypt operation now works correctly.

W-14792113
## [](#1-3-18)1.3.18 **January 11, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.santuario:xmlsec library is upgraded to version 2.3.4 to address reported security vulnerabilities.

W-14668416
## [](#1-3-17)1.3.17 **January 9, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-3-16)1.3.16 **September 20, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The Out of memory error no longer occurs for files larger than 300MB on PGP Encrypt, PGP Encrypt and Sign, PGP Encrypt Binary, and PGP Decrypt operations.

W-13797282
## [](#1-3-15)1.3.15 **September 19, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The dependency org.bouncycastle:bcpg-jdk18on:1.74 replaces org.bouncycastle:bcpg-jdk15on:1.70.

W-13844863

The dependency org.bouncycastle:bcprov-ext-jdk15to18:1.7, which is no longer in use, is removed to fix security vulnerabilities.

W-13844863
## [](#1-3-14)1.3.14 **November 16, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The Pgp encrypt operation no longer fails when running in a FIPS environment.

W-11900235
## [](#1-3-13)1.3.13 **November 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Internal dependencies that fix vulnerability issues are updated.

W-12007146
## [](#1-3-12)1.3.12 **September 26, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Upgraded bcprov-jdk15on to version 1.70 and bcprov-ext-jdk15to18 to version 1.71

W-11676720
## [](#1-3-11)1.3.11 **August 16, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Security updates applied to internal dependecies.

W-11550826
## [](#1-3-10)1.3.10 **March 15, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Security updates applied to internal dependecies.

W-10583033
## [](#1-3-9)1.3.9 **December 22, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Cipher RSA/NONE/OAEPWithSHA1AndMGF1Padding is now supported.

CRYPT-22
## [](#1-3-8)1.3.8 **June 10, 2021** No new features were added in this version. ### [](#fixed-issues-19)Fixed Issues - Upgraded internal dependencies. ## [](#1-3-7)1.3.7 **June 1, 2021** No new features were added in this version. ### [](#fixed-issues-20)Fixed Issues - Upgraded internal dependencies. ## [](#1-3-6)1.3.6 **January 21, 2021** No new features were added in this version. ### [](#fixed-issues-21)Fixed Issues - Unable to locate a key inside the private keyring when decrypting a file that was encrypted using PGP with multiple recipients. ## [](#1-3-5)1.3.5 **February 28, 2020** No new features were added in this version. ### [](#fixed-issues-22)Fixed Issues
Issue Description

EE-7206

The issue that caused JCE decryption operation fails when both random IV and ECB algorithm was selected
## [](#1-3-4)1.3.4 **February 4, 2020** No new features were added in this version. ### [](#fixed-issues-23)Fixed Issues
Issue Description

EE-7197

The issue that caused the inability to create a cipher after deploying the app a second time is fixed.
## [](#1-3-3)1.3.3 **January 22, 2020** No new features were added in this version. ### [](#fixed-issues-24)Fixed Issues
Issue Description

EE-7187

The issue that caused loading secret keys from a keyring that contained both public and secret keys to fail is fixed.
## [](#1-3-1)1.3.1 **October 1, 2019** No new features were added in this version. ### [](#fixed-issues-25)Fixed Issues
Issue Description

EE-7024

XML sign operation honors the elementPath parameter.
## [](#1-3-0)1.3.0 **September 25, 2019** ### [](#features)Features - XML Signatures can be verified against certificates contained in the document. - It is possible to define an XPath expression to select and verify a signature in an XML document that contains multiple signatures. - JCE encryption and decryption use a random initialization vector (IV). ### [](#fixed-issues-26)Fixed Issues
Issue Description

EE-6975

Key principal can be recovered from fingerprint.
## [](#1-2-0)1.2.0 **August 23, 2019** ### [](#features-2)Features - Added support for the ECDSA XML Signing algorithm. No issues were fixed in this version. ## [](#1-1-0)1.1.0 **August 20, 2019** ### [](#features-3)Features - Implemented atomic encrypt and sign operation for PGP. - PGP decryption operation can validate signature if found. - All PGP encryption operations now include MDC (modification detection code) by default. Although this is unlikely to cause any issues, you can use the `disableMDC` parameter to revert to the previous behavior if needed. ### [](#fixed-issues-27)Fixed Issues
Issue Description

MULE-17337

Upgrade Commons Codec to 1.13
## [](#1-0-1)1.0.1 **May 23, 2019** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-28)Fixed Issues
Issue Description

MULE-16870

Upgrade BouncyCastle dependency to 1.61.

MULE-16870

Upgrade Commons Lang dependency to 3.8.1.

MULE-16870

Upgrade Commons Codec dependency to 1.12.

MULE-16870

Upgrade XML Sec dependency to 2.1.3.
## [](#1-0-0)1.0.0 **Mar 19, 2018** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # D2L Brightspace Connector Release Notes Anypoint Connector for D2L Brightspace (D2L Brightspace Connector) enables Mule applications to access the D2L Brightspace API. Guide: [D2L Brightspace Connector User Guide](https://docs.mulesoft.com/d2l-brightspace-connector/latest/) ## [](#0-1-2)0.1.2 **September 2, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-1)0.1.1 **September 2, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **April 14, 2026** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/d2l-brightspace-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [D2L Brightspace Connector User Guide](https://docs.mulesoft.com/d2l-brightspace-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [D2L Brightspace Connector User Guide](https://docs.mulesoft.com/d2l-brightspace-connector/latest/) - [D2L Brightspace Connector Reference](https://docs.mulesoft.com/d2l-brightspace-connector/latest/d2l-brightspace-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Database Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Database (Database Connector) enables you to connect to relational databases through the JDBC API. Guide: [Database Connector User Guide](https://docs.mulesoft.com/db-connector/latest/) ## [](#1-16-6)1.16.6 **October 23, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The recommended PostgreSQL JDBC driver is upgraded to version 42.7.14 to address CVE-2026-107314 and CVE-2026-107315. Because the driver is an external library, update the driver supplied to your application to use this version.

W-24468095

The com.google.guava:guava library is upgraded to version 33.7.2-jre.

W-24471653
## [](#1-16-5)1.16.5 **October 2, 2026** ### What’s New - You can opt in to surfacing errors from later statements in Microsoft SQL Server **Execute script** operations by setting the JVM system property `mule.db.connector.sqlserver.surface.script.errors=true`. The property is disabled by default to preserve existing behavior and affects only SQL Server **Execute script** operations. Because this is a JVM-level setting, it applies to all applications in the Mule runtime. Configure it consistently on every worker or replica and restart the runtime after changing JVM arguments. This option improves the visibility of errors within a script; it does not automatically resolve all SQL Server errors. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The recommended PostgreSQL JDBC driver is upgraded from 42.7.11 to 42.7.13 to address CVE-2026-54291. Because the driver is an external library, update the driver supplied to your application to use this version.

W-24141242

The com.mchange:c3p0 component is upgraded from 0.14.1 to 0.14.2.

W-3300013

The org.apache.commons:commons-collections4 component is upgraded from 4.5.0 to 4.6.0.

W-3300013

The com.google.guava:guava component is upgraded from 33.6.0-jre to 33.7.1-jre.

W-3300013
## [](#1-16-4)1.16.4 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-16-3)1.16.3 **August 25, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

On the Database On Table Row listener source, the useColumnNumbers setting is now honored both at runtime and at design time (DataSense). Previously the source ignored the flag: emitted rows were always keyed by column name and metadata always showed column names, even when useColumnNumbers was set to true. Rows and metadata are now keyed by column number when the option is enabled, matching the Select and Query Single operations.

W-21982686

The com.mchange:c3p0 component is upgraded to 0.14.1.

W-23664719

The com.mchange:mchange-commons-java component is upgraded to 0.6.1.

W-23664719
## [](#1-16-2)1.16.2 **July 23, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

On Oracle, metadata resolution no longer stalls or fails for a packaged stored procedure whose owning schema differs from the connection user. A two-part PACKAGE.PROCEDURE call to a foreign-owned package (for example, an Oracle E-Business Suite public-synonym topology) now returns its parameter metadata correctly.

W-22852899

On Oracle, inserting a value into an XMLTYPE column no longer fails with a ClassCastException error (surfaced as DB:QUERY_EXECUTION) when connection pooling is enabled. Pooled XMLTYPE inserts now succeed, as they already do without pooling.

W-22895195
## [](#1-16-1)1.16.1 **June 24, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

On Microsoft SQL Server, the connector no longer fails with a The statement is closed error when prepared-statement caching is enabled with connection pooling. The connector now defaults the markSessionBoundaries pool property to if-no-statement-cache for SQL Server when a statement cache is active, and an explicit user-provided value continues to take precedence.

W-22560183

The sql parameter now renders as a text input field in Anypoint Code Builder. Previously, the field was advertised with a metadata key resolver and appeared as an empty dynamic dropdown.

W-22901825

Stored-procedure calls that mix hardcoded literal arguments with named placeholders now bind each placeholder to its correct parameter position. Previously, a placeholder following a literal could be bound against the wrong column type, causing a NumberFormatException at runtime.

W-16842191

Stored-procedure connections are now released on the error path, preventing a connection leak when a stored-procedure call fails.

W-22940258

Backtick-quoted identifiers now correctly escape special characters.

W-17922848

The Oracle NLS timestamp String binding is restored, so Oracle timestamp values bind correctly.

W-21816663

ORA-17008 Closed Connection errors that could occur on Oracle in batch and streaming LOB workloads are resolved.

W-22311048

The com.google.guava:guava component is upgraded to 33.6.0-jre.

W-3300013

The commons-io:commons-io component is upgraded to 2.22.0.

W-3300013

The org.apache.commons:commons-lang3 component is upgraded to 3.20.0.

W-3300013
## [](#1-16-0)1.16.0 **May 20, 2026** ### What’s New - Database Connector now provides a configurable LOB (CLOB/BLOB) resource release strategy via the `mule.db.connector.lob.free.strategy` system property. Available strategies are `EAGER` (default), `DEFERRED`, and `NONE`, enabling users to tune performance for queries returning many LOB columns, particularly with Oracle databases. Refer to [Troubleshoot LOB Resource Release Performance](https://docs.mulesoft.com/db-connector/latest/database-connector-troubleshooting#troubleshoot-lob-resource-release-performance). (W-22181640) - The default value of the **Cache Query Template Size** configuration parameter is changed from `50` to `1000`, improving performance for applications that use a large number of distinct SQL queries. (W-21868167) ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The useColumnNumbers parameter now correctly influences metadata resolution (DataSense). Previously, setting this parameter to true did not affect the metadata keys returned by the connector.

W-21218595

The org.postgresql:postgresql driver is upgraded from 42.7.2 to 42.7.11.

W-3300013

High memory consumption and memory management degradation over time under load due to unclosed connections is resolved.

W-22311048
## [](#1-15-1)1.15.1 **April 15, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.mchange:c3p0 component is upgraded to 0.12.0.

W-21701822

The com.mchange:mchange-commons-java component is upgraded to 0.4.0.

W-21701822

The org.springframework.security:spring-security-core component is upgraded to 5.8.16.

W-21701822

The org.springframework.security:spring-security-config component is upgraded to 5.8.16.

W-21701822

The com.sun.xml.bind:jaxb-impl component is upgraded to 2.3.9.

W-21701822
## [](#1-15-0)1.15.0 **December 9, 2025** ### What’s New - Database Connector introduced the `useColumnNumbers` flag to allow operations to use column indices (1, 2, 3…​) as map keys instead of column labels, eliminating duplicate key issues when multiple columns share the same name. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly handles AbstractMethodError exceptions when calling stored procedures with CLOB type parameters using the jtds-1.3.1 driver for SQL Server. Previously, the connector would fail when the driver’s createClob method threw this error. The connector now catches this exception and falls back to the legacy CLOB handling approach.

W-13179282
## [](#1-14-17)1.14.17 **August 28, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly converts string values to data parameters for the Oracle provider.

W-19024421
## [](#1-14-16)1.14.16 **May 29, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now properly handles special characters in stored procedure names through the mule.db.commons.defaultParamTypeResolver.enable.fallback system property, providing an alternative configuration method when these characters are present. Refer to System Properties.

W-17967831
## [](#1-14-15)1.14.15 **April 30, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector correctly resolves the type field for output parameters.

W-17934321

The library commons-collections is upgraded to commons-collections4 version 4.5.0 to address reported security vulnerabilities.

W-18366767
## [](#1-14-14)1.14.14 **March 26, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector correctly resolves Datetime type parameters for the Oracle provider.

W-16623843

The connector correctly resolves Date type parameters for the Insert operation.

W-17099669
## [](#1-14-13)1.14.13 **October 29, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The DB client dependency is upgraded to version 1.6.16 to fix a performance bottleneck caused by a static modifier.

W-17013834

Database Connector no longer fails if it includes a UDT with a clob field as a stored procedure parameter.

W-16615688

Commons-IO is upgraded to version 2.17.0 to address reported security vulnerabilities.

W-17091979
## [](#1-14-12)1.14.12 **August 26, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The DB client dependency is upgraded to version 1.6.14 to remove the warn log of the ResolvedDbType class.

W-16425563
## [](#1-14-11)1.14.11 **July 18, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The timestamp input parameters are correctly converted to timestamp with local time zone, in OJDBC8 versions 22.x and later.

W-14492132
## [](#1-14-10)1.14.10 **May 22, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Numeric input parameters are converted correctly when the input is a string.

W-15660005
## [](#1-14-9)1.14.9 **March 4, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Cache is now used for the prepareArray and prepareStruct functions.

W-14379190

Database Connector now returns results in CaseInsensitiveLinkedMap, keeping items in order through multiple iterations.

W-14376795
## [](#1-14-8)1.14.8 **January 18, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Spring core is upgraded to version 5.3.29 to address reported security vulnerabilities.

W-11854682

Spring beans is upgraded to version 5.3.29 to address reported security vulnerabilities.

W-11854684

Spring security is upgraded to version 5.8.6 to address reported security vulnerabilities.

W-11854690
## [](#1-14-7)1.14.7 **December 7, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Database Connector no longer fails when a stored procedure has a $ in the name.

W-13210313
## [](#1-14-6)1.14.6 **October 30, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Database Connector no longer has a memory leak with Oracle getClobVal.

W-14200482
## [](#1-14-5)1.14.5 **October 24, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Stored Procedure operation now correctly recognizes custom types as IN/OUT parameters when the stored procedure is located within a package.

W-12516787
## [](#1-14-4)1.14.4 **October 4, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The On Table Row source now applies the Max rows field to its polling query.

W-13829389
## [](#1-14-3)1.14.3 **August 9, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now manages an unspecified input parameter for OJDBC8 version 23.2.

W-13577226
## [](#1-14-2)1.14.2 **July 12, 2023** ### What’s New - The commons-io library is upgraded to version 2.13.0. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Max Rows field is now properly handled if the value is set to 0.

W-12484975

The stored procedure metadata cache now works as intended.

W-13131343

The commons-io library is upgraded to version 2.13.0 to address reported security vulnerabilities.

W-13720405
## [](#1-14-1)1.14.1 **March 30, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Database Connector now reads BLOBs from Oracle stored procedures.

W-12545854
## [](#1-14-0)1.14.0 **January 10, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Database Connector now supports adding the template cache size in the Cache Query Template Size field of the connector configuration.

W-12167736
## [](#1-13-8)1.13.8 **October 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The XA Bitronix configuration pool no longer throws DB:QUERY_EXECUTION when the Store procedure operation has an output parameter.

W-11743085

The Store procedure operation no longer returns an issue with a CLOB output while using a local transaction.

W-11721963

The warn message at attempting to override property no longer have the braces with number ({0}.{1}..) displayed.

W-11755478

The MuleRuntimeException shown during resolving query will show the stack trace now.

W-11762357
## [](#1-13-7)1.13.7 **September 12, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Memory leaks no longer occur in transaction operations when using LOBs fields.

W-11582039

The XA Bitronix configuration pool no longer throws the createArray or createStruct unsupported exceptions when the Store procedure operation has an array as a parameter.

W-11425936
## [](#1-13-6)1.13.6 **August 3, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The DataWeave mapping input issue to a CLOB in the Insert operation no longer occurs.

W-11524839
## [](#1-13-5)1.13.5 **July 11, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Using the Select operation with CLOB output no longer causes a connection leak.

W-11259976
## [](#1-13-4)1.13.4 **June 6, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

When using stored procedures, connections no longer leak. Connections are now released at the end of the flow and when consuming CLOBs as an output parameter.

W-11098541
## [](#1-13-3)1.13.3 **May 26, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Database Connector no longer needs Oracle’s UDT scheme appended on the type name when you define the scheme on the connector’s global configuration Column types field or in the Parameter types section of the Stored procedure operation. Now, the connector searches the type name correctly.

W-11002486
## [](#1-13-2)1.13.2 **May 12, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Database Connector did not log enough information when the Connection Factory caught an exception during the connection creation. Now, the connector logs the proper stack trace with the error level.

W-10718271

Database Connector no longer throws a java.lang.OutOfMemoryError: Java heap space error when using the Insert operation to work with large CLOB files.

W-10911002
## [](#1-13-1)1.13.1 **April 25, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The output of prepareArray and prepareStruct functions are now properly converted into the actual JDBC objects. Also, when calling store procedures, the correct parameter type is inferred, which avoids breaking the creation of structs and arrays.

W-10673234
## [](#1-13-0)1.13.0 **April 11, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

To fix concurrency issues that occur when using the createArray and createStruct functions, Mule introduces the prepareStruct and prepareArray functions to use instead. These new functions enable Database Connector to defer JDBC values creation until the correct SQL connection is available. The createArray and createStruct functions continue to work as previously. Replace them manually in your code with the new functions.

W-10673234
## [](#1-12-1)1.12.1 **February 21, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Database Connector now supports the consumption of LOBs for the IBM’s DB2.

W-10673315
## [](#1-12-0)1.12.0 **February 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Support Oracle features even if the database connection is provided as a Spring bean reference to a DataSource or as a Generic Connection.

DBCON-329

Access Oracle’s proprietary createARRAY() function using a JDBC standard method to increase compatibility with custom connection pool managers.

DBCON-352

Added synchronization while invoking createArray functions to prevent deadlocks that occurred under high concurrency.

DBCLI-15
## [](#1-11-3)1.11.3 **January 31, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Database Connector now allows brackets in the Stored procedure operation query to support the MSSQL Server.

DBCON-360

Added a warning message when a timeout’s value is rounded up.

DBCON-318
## [](#1-11-2)1.11.2 **January 07, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Reversed a dependency in Database Connector versions 1.11.0 and 1.11.1 that prevented the deployment of apps.

DBCON-350
## [](#1-11-1)1.11.1 **January 05, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Reversed a change in the Database Connector version 1.11.0 API that prevented the deployment of apps.

DBCLI-25
## [](#1-11-0)1.11.0 **December 22, 2021** ### What’s New TLS support feature for Oracle’s connection provider. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Database Connector Select operation closed the connection at the end of the flow when its result contained a LOB stream. Now the consumption of the LOB streams is tracked, and the connection is closed when there are no more LOB streams to consume or at the end of the flow.

DBCON-304

Timeouts are now rounded up to whole seconds. Because timeouts are set in seconds (JDBC API), the connector rounds up values smaller than a second to avoid waiting indefinitely.

DBCON-318

When using JDBC’s REF_CURSOR type as a stored procedure out parameter, the error unsupported network datatype or representation was thrown. Now the type is handled correctly.

DBCON-319
## [](#1-10-6)1.10.6 **November 10, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Inserting data into an Oracle database returned an Invalid Column Type error. The variable used as input parameter should be of MIME type text/plain.

DBCON-311
## [](#1-10-5)1.10.5 **October 27, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Large NVarchar payloads failed with jTDS driver (MSSQL).

DBCLI-10
## [](#1-10-4)1.10.4 **August 20, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

ResultSets with active LobStreams are forcibly closed at the end of a flow.

DBCLI-12

Changed the record level to WARN when unable to determine if there are more records in the ResultSets.

DBCLI-14
## [](#1-10-3)1.10.3 **July 28, 2021** ### [](#compatibility-46)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-45)Fixed Issues - Database Connector threw an incorrect `QueryExecutionException` exception when the `SQLException` thrown by the driver didn’t have an SQLState nor a message related to the connection. Therefore, the reconnection strategy was not triggered. The correct throw message is `DB:CONNECTIVITY`. (DBCLI-11) ## [](#1-10-2)1.10.2 **July 19, 2021** ### [](#fixed-issues-46)Fixed Issues - Database Connector threw an `Invalid column type` message when using Oracle’s XMLTYPE as input for the **Stored Procedure** operation. The connector now manages the correct type. (DBCON-278) - Database Connector threw an incorrect `TransactionException` exception when the connection was lost during an XA transaction. Therefore, the reconnection strategy was not triggered. The correct throw message is `DB:CONNECTIVITY`. (DBCLI-7) - The Database Connector **Stored Procedure** operation incorrectly executed database functions with an IN OUT parameter. Now, the operation performs correctly. (DBCLI-8) - Database Connector did not log enough information when the Connection Factory caught an exception during the connection creation. Now, the connector logs the proper information. (DBCLI-9) ## [](#1-10-1)1.10.1 **July 05, 2021** ### [](#fixed-issues-47)Fixed Issues - Database Connector exported incorrect packages, now the connector exports the correct packages. (DBCON-283, DBCON-286) ## [](#1-10-0)1.10.0 **June 04, 2021** ### [](#features)Features Added new options for **Pooling profile** configuration: - The **Test connection on checkout** field enables you to disable connection testing on checkout in order to improve the connector’s performance. - The **Max statement** field enables you to define the total number of `PreparedStatements` a DataSource will cache. ## [](#1-9-4)1.9.4 **June 01, 2021** ### [](#fixed-issues-48)Fixed Issues - Database Connector logged an exception at **ERROR** level causing a large amount of content to be saved in the log registry. Now the connector uses the correct log level, **DEBUG**. (DBCLI-5) ## [](#1-9-3)1.9.3 **April 05, 2021** ### [](#fixed-issues-49)Fixed Issues - When using the **Insert** operation, Database Connector didn’t correctly resolve the NCLOB types, which resulted in a `DB:QUERY_EXECUTION` error with an `Invalid column type` message. (DBCON-265) ## [](#1-9-2)1.9.2 **March 22, 2021** ### [](#fixed-issues-50)Fixed Issues - Database Connector threw an incorrect `NoSuchElementException` Java exception for a connection reset while iterating a result, and produced a `noncatch` by the `try catch` block. The correct throw message is `DB:CONNECTIVITY`. (DBCON-253) - The **Stored Procedure** operation threw a `MULE:UNKONWN` error (with a `NullPointerException` message) when returning an empty array. (DBCON-255) - Database Connector closed the connection after reading the entire ResultSet of a **Select** operation despite having the LOB stream still open. This behavior prevented the LOB values from being read after the connection closure. (DBCON-256) ## [](#1-9-1)1.9.1 **November 30, 2020** ### [](#fixed-issues-51)Fixed Issues - Fixed an issue in which the **On Table Row** operation closed connections once rows were dispatched to the next processor, thus preventing the consumption of streams. (DBCON-234) ## [](#1-9-0)1.9.0 **November 17, 2020** ### [](#minimum-mule-version)Minimum Mule Version Mule 4.1.1 ### [](#features-2)Features - Introduced the **Query single** operation that enables you to select a single record from a database and access the result without any additional transformations to the payload. This operation doesn’t use streaming. ## [](#1-8-3)1.8.3 **September 30, 2020** ### [](#fixed-issues-52)Fixed Issues - Fixed an issue in which stored procedures were not closing connections when no stream was returned, nor any transaction performed. (DBCON-225) - When the `Bulk insert` operation used debug output, it logged a placeholder instead of the record number. (DBCON-228) ## [](#1-8-2)1.8.2 **August 12, 2020** ### [](#fixed-issues-53)Fixed Issues - Fixed "Struct cannot be cast to \[Ljava.lang.Object" issue that prevented the connector to create SQL Arrays or Structs containing BLOBs or CLOBs types. (DBCON-190) ## [](#1-8-1)1.8.1 **June 1, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version Mule 4.1.1 ### [](#features-3)Features None ### [](#fixed-issues-54)Fixed Issues - Fixed issue where connections were not closed if a stored procedure returned multiple result sets. (DBCON-182) - Fixed issue where dbCreateStruct performance introduced a regression since Mule 3.9.4. (DBCON-178) ## [](#1-8-0)1.8.0 **April 24, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version Mule 4.1.1 ### [](#features-4)Features Database Connector now accepts SQL Casting PostgreSQL and Snowflake syntax’s, through the double colon (::) expression. For example, `SELECT MAX(modified_date)::DATE FROM sales`, where `modified_date` is of type string. This feature does not change the existing behavior for the connector (MULE-18150). ### [](#fixed-issues-55)Fixed Issues - MySQL driver now logs to the Mule Log when using MySQL Driver 8.x and higher (MULE-18287). - Fixed issue that prevented the usage of the BulkInsert Operation within a ForEach scope (MULE-18260). - Fixed issue that prevented the logging of information about a BulkUpdate Operation when an Exception was thrown by it (MULE-18290). ## [](#1-7-0)1.7.0 **March 13, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version Mule 4.1.1 ### [](#features-5)Features You can now specify additional pooling profile properties using the additional-properties tab for any Database provider. This feature allows you to specify only additional properties and not to override the main ones (like maxPoolSize) if they were already specified. ### [](#fixed-issues-56)Fixed Issues Fixed issue where oracle DB connector was unable to use specific pooling profile configurations (such as `checkoutTimeout` or `idleConnectionTestPeriod`). (MULE-17949) Fixed issue where first stored procedure calls to database took a long time. (MULE-17808) Fixed issue where operation stored-procedure did not offer the parameter to configure repeatable streaming. (MULE-17898) ## [](#1-6-2)1.6.2 **January 9, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version Mule 4.1.1 ### [](#features-6)Features None ### [](#fixed-issues-57)Fixed Issues The infinite loop when using stored procedure with H2 Database issue is fixed. (MULE-17793) ## [](#1-6-1)1.6.1 **January 7, 2020** ### [](#minimum-mule-version-6)Minimum Mule Version Mule 4.1.1 ### [](#features-7)Features None ### [](#fixed-issues-58)Fixed Issues - The issue where connection leaks occurred when using dynamic configurations is fixed. (MULE-17792) - The issue where using stored procedures with a CLOB `In Out` parameter failed to execute on Oracle is fixed. (MULE-17846) ## [](#1-6-0)1.6.0 **October 11, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version Mule 4.1.1 ### [](#features-8)Features You can now reference the name of a package of stored procedures on Oracle. (MULE-17418) ### [](#fixed-issues-59)Fixed Issues Pooled DB connections maxIdleTime default 0 causes connections to remain open. (MULE-17601) ## [](#1-5-5)1.5.5 **September 24, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version Mule 4.1.1 ### [](#features-9)Features None ### [](#fixed-issues-60)Fixed Issues - Stored procedures took too long to execute with the Oracle Database. (MULE-17394) - Unable to retrieve responses with custom data types. (MULE-17470) - Unable to execute stored procedures defined within packages on an Oracle Database. (MULE-17418) ## [](#1-5-4)1.5.4 **June 6, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version Mule 4.1.1 ### [](#features-10)Features None ### [](#fixed-issues-61)Fixed Issues - On stored procedures where the output return variable is set to null, the output should not be processed further. (MULE-16961) - `db:select` operation fails to throw a connectivity error. (MULE-16950) ## [](#1-5-3)1.5.3 **May 7, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version Mule 4.1.1 ### [](#features-11)Features None ### [](#fixed-issues-62)Fixed Issues - Connector doesn’t ensure data is consumable by DataWeave if it has an encoding different from the one used by the runtime. (MULE-16460) - Clob in out parameters are not made consumable with Oracle DB. (MULE-16770) ## [](#1-5-2)1.5.2 **April 16, 2019** ### [](#minimum-mule-version-11)Minimum Mule Version Mule 4.1.1 ### [](#features-12)Features Add connector icon. ### [](#fixed-issues-63)Fixed Issues - Errors while transforming to JSON the output of Oracle SP call with custom types. (MULE-16589) - Can’t get parameter data types when store procedure name includes schema. (MULE-16685) - FlowListener callback retains too much state. (MULE-16366) - Errors when using Oracle’s UDT Table type. (MULE-16401) - Database connector not sending value of the IN-OUT parameter. (MULE-16484) - "Unable to convert between" error when using SP in MsSql. (MULE-16339) ## [](#1-5-0)1.5.0 **December 28, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version Mule 4.1.1 ### [](#features-13)Features The connector now supports the usage of Struct and Array types out of the box. ### [](#fixed-issues-64)Fixed Issues DB Connector doesn’t work OOTB with Struct and Array types. (MULE-16074) ## [](#1-4-3)1.4.3 **December 11, 2018** ### [](#minimum-mule-version-13)Minimum Mule Version Mule 4.1.1 ### [](#features-14)Features None ### [](#fixed-issues-65)Fixed Issues Database connector not releasing connections. (MULE-16072) ## [](#1-4-2)1.4.2 **October 18, 2018** ### [](#minimum-mule-version-14)Minimum Mule Version Mule 4.1.1 ### [](#features-15)Features None ### [](#fixed-issues-66)Fixed Issues Queries get cached without any TTL or limit, which causes memory to grow. (MULE-15869) ## [](#1-4-1)1.4.1 **October 16, 2018** ### [](#minimum-mule-version-15)Minimum Mule Version Mule 4.1.1 ### [](#features-16)Features None ### [](#fixed-issues-67)Fixed Issues - Can’t get stored procedure name from SQL query when there is whitespace before parentheses. (MULE-15793) - MySQL default driver causes a memory leak. (MULE-15748) - Database On Table Row should hint available columns for ID and Watermark using Value Providers. (MULE-15644) ## [](#1-4-0)1.4.0 **August 7, 2018** ### [](#minimum-mule-version-16)Minimum Mule Version Mule 4.1.0 ### [](#features-17)Features - Now in Generic Connections, the username and password can be configured outside the JDBC URL for improved security and support for multitenancy. - Improved New Row trigger, now hints with the available tables to retrieve rows. - Support for PostgreSQL type casting. ### [](#fixed-issues-68)Fixed Issues - Database On New Row listener should provide a hint to available tables. (MULE-15310) - Database Connector uses deprecated DriverClass when using new MySQL Drivers. (MULE-15218) - Database Connector doesn’t support PostgreSQL type casting. (MULE-15101) ## [](#1-3-4)1.3.4 **June 29, 2018** ### [](#minimum-mule-version-17)Minimum Mule Version Mule 4.1.0 ### [](#features-18)Features - Fixed issue that prevented inserting and updating CLOB types in Oracle Databases. - When using the newest MySQL Driver, the connector uses the new preferred Driver Class instead of the old deprecated one. - Fixed issue when consuming CLOB and BLOB types when using Derby databases. ### [](#fixed-issues-69)Fixed Issues - Database Connector should automatically transform CLOB types on Oracle Databases. (MULE-15240) - Database Connector uses deprecated DriverClass when using new MySQL Drivers. (MULE-15218) ## [](#1-3-3)1.3.3 **May 21, 2018** ### [](#minimum-mule-version-18)Minimum Mule Version Mule 4.1.0 ### [](#features-19)Features Fixed issue that makes the connector log the JDBC URL. ### [](#fixed-issues-70)Fixed Issues Database connector logs passwords. (MULE-15047) ## [](#1-3-2)1.3.2 **May 7, 2018** ### [](#minimum-mule-version-19)Minimum Mule Version Mule 4.1.0 ### [](#features-20)Features Minor internal changes. ### [](#fixed-issues-71)Fixed Issues - SQL Server Connection provider doesn’t communicate the library RegEx. (MULE-14876) - Upgrade c3p0 to Mule fork version. (MULE-14859) ## [](#1-3-1)1.3.1 **March 16, 2018** ### [](#minimum-mule-version-20)Minimum Mule Version Mule 4.1.0 ### [](#features-21)Features This release includes the following enhancements, changes, and fixes: - Now the Oracle Connection can be configured with a Service Name. - When doing a Select now the output metadata communicates correctly if the columns values can be have a null value or not. - In some scenarios when an error occurs the connection string with embedded credentials could be logged. ### [](#fixed-issues-72)Fixed Issues - Connectors doesn’t communicate correctly if their POJOs properties are nullable or not. (MULE-14701) - Credentials leak in error messages. (MULE-14740) - Add the capability of configuring the Service Name for an Oracle Connection. (MULE-14750) ## [](#1-3-0)1.3.0 **March 2, 2018** ### [](#minimum-mule-version-21)Minimum Mule Version Mule 4.1.0 ### [](#features-22)Features This release includes the following enhancements, changes, and fixes: - Added a new message source which triggers a flow per each row in a table. - When doing a SELECT over a CLOB column the value is retrieved as a InputStream. ### [](#upgrade-requirements)Upgrade Requirements Mule 4.1 ### [](#fixed-issues-73)Fixed Issues - Create Trigger for Database. (MULE-14657) - DB Connector returns ClLOB objects instead of InputStreams. (MULE-14615) ## [](#1-2-0)1.2.0 **January 19, 2018** ### [](#minimum-mule-version-22)Minimum Mule Version Mule 4.0.0 ### [](#features-23)Features This release includes the following enhancements, changes, and fixes: - Added out-of-the-box support for connecting to Microsoft SQL Server Databases. - Improved support for Derby sub-protocols. - Improved UX. ### [](#fixed-issues-74)Fixed Issues - ColumnTypes parameter should be placed on Advanced Tab. (MULE-14515) - Add Value Providers for SubSubProtocols in Derby Connection Provider. (MULE-13921) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave 2.11.0 Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-2.11.0-release-notes.adoc - include::dataweave::partial$dataweave-intro.adoc\[\] For more detail, see [DataWeave Language](https://docs.mulesoft.com/dataweave/latest/). ## [](#july-2026)July 2026 DataWeave 2.11.5 is bundled with the Mule 4.11.6 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). ## [](#june-2026)June 2026 DataWeave 2.11.4 is bundled with the Mule 4.11.5 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). ## [](#may-2026)May 2026 DataWeave 2.11.3 is bundled with the Mule 4.11.4 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). ## [](#april-2026)April 2026 DataWeave 2.11.2 is bundled with the Mule 4.11.3 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). ## [](#march-2026)March 2026 DataWeave 2.11.1 is bundled with the Mule 4.11.2 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501

The Mapping Editor API now supports attributes in Anypoint Code Builder.

W-20662336

Updating the expression model in the Mapping Editor API now works correctly.

W-20611263
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). ## [](#february-4-2026)February 4, 2026 DataWeave 2.11.0 is bundled with the Mule 4.11.0 release. For details about the Mule release, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). ### What’s New 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). ### Compatibility This table specifies which version of DataWeave is bundled with each Mule runtime engine release:
Mule Version DataWeave Version

4.13

2.13

4.12

2.12

4.11

2.11

4.10

2.10

4.9

2.9

4.8

2.8

4.7

2.7

4.6

2.6

4.5

2.5

4.4

2.4

4.3

2.3

4.2

2.2

4.1

2.1

3.9

1.2

3.8

1.1

3.7

1.0
### Fixed Issues The release addresses these DataWeave issues and incorporates all patch updates from the 2.10.0 DataWeave release through January 2026:
Issue Resolution ID

AST scope navigation now works correctly for cross-file references when using the Tooling API.

W-20212809

A specific overload for isEmpty on binaries is now available to prevent implicit coercion to other types.

W-20049958

Materialized Java values are now cached to allow multiple executions using the same value.

W-20091279

Semantic tokens are now supported in the Tooling API.

W-19846990

NullPointerException no longer occurs when handling annotation types.

W-19853000

LogLevel documentation is now included directly in the code.

W-17800393

The commons-beanutils library is upgraded.

W-3300013

Base64 encoding and decoding now support payloads larger than memory.

W-18575719

Eager materialization is now supported on values, enabling caching of all exceptions inside the try function.

W-19717874

Avro enum, map, union, and fixed types are now supported as top-level elements.

W-19596039

WeaveCompiler now allows precompiling mappings and modules without validation or type checking.

W-19667273

Type check errors are now correctly reported when resolving type checking on subgraphs.

W-19564697

Lazy loading of source files is now enabled during binary compilation, avoiding unnecessary memory usage.

W-19594703

Type inference now works correctly when using the -- operator to subtract a key from an object.

W-19595907

Warning and error messages now propagate correctly between compilation phases.

W-19386849

Base types are now used to validate accepted values, preventing premature materialization.

W-18943395

Optional types now propagate correctly through chains of value selectors.

W-19272070

The syntax version is now added to TypeGraph and WeaveTypeResolution.

W-19271992

The classloader resource resolver now resolves paths correctly on Windows systems.

W-19407283
### Upgrade This version of DataWeave is bundled with Mule. DataWeave upgrades take place through Mule. See [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb#mule-upgrades). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave 2.12.0 Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-2.12.0-release-notes.adoc - include::dataweave::partial$dataweave-intro.adoc\[\] For more detail, see [DataWeave Language](https://docs.mulesoft.com/dataweave/latest/). ## [](#september-2026)September 2026 DataWeave 2.12.3 is bundled with the Mule 4.12.3 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). ## [](#august-2026)August 2026 DataWeave 2.12.2 is bundled with the Mule 4.12.2 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

Type metadata processing now correctly handles sibling references that target the same type, preventing duplicate annotations.

W-23424037

DataWeave now handles Java Platform Module System (JPMS) access restrictions more gracefully when running on Java 17 and later in Mule runtime 4.6.0 and later.

W-23354139

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). ## [](#july-2026)July 2026 DataWeave 2.12.1 is bundled with the Mule 4.12.1 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). ## [](#june-2-2026)June 2, 2026 DataWeave 2.12.0 is bundled with the Mule 4.12.0 release. For details about the Mule release, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). ### What’s New The 2.12.0 version of DataWeave introduces these new features and enhancements: Scope Visibility: - DataWeave now supports `private`, `internal`, and `@VisibleTo` annotations for controlling directive access. This enables better code encapsulation and visibility management across DataWeave modules. See [Scope Visibility in DataWeave](https://docs.mulesoft.com/dataweave/latest/dataweave-scope-visibility). Component Metadata: - DataWeave introduces `dw::meta::Component` and related component types for working with component descriptors. This provides enhanced metadata handling capabilities. See [Component (dw::meta::Component)](https://docs.mulesoft.com/dataweave/latest/dw-component) and [Component Types (dw::meta::Component)](https://docs.mulesoft.com/dataweave/latest/dw-component-types). General Improvements: - The [UNLIMITED\_CONTEXT](https://docs.mulesoft.com/dataweave/latest/dw-math-variables) math variable now has the `precision=0` and `roundingMode=HALF_UP` properties. - The [Maven plugin for DataWeave](https://docs.mulesoft.com/dataweave/latest/dataweave-maven-plugin) now includes guidance for configuring cryptographic taint analysis during compilation. - The [DataWeave extension plugin](https://docs.mulesoft.com/dataweave/latest/dataweave-extension-plugin) now provides editor support for scope visibility validation and diagnostics. - DataWeave incorporates new system properties. See [DataWeave System Properties](https://docs.mulesoft.com/dataweave/latest/dataweave-system-properties). ### Compatibility This table specifies which version of DataWeave is bundled with each Mule runtime engine release:
Mule Version DataWeave Version

4.13

2.13

4.12

2.12

4.11

2.11

4.10

2.10

4.9

2.9

4.8

2.8

4.7

2.7

4.6

2.6

4.5

2.5

4.4

2.4

4.3

2.3

4.2

2.2

4.1

2.1

3.9

1.2

3.8

1.1

3.7

1.0
### Fixed Issues The release addresses these DataWeave issues and incorporates all patch updates from the 2.11.0 DataWeave release through May 2026:
Issue Resolution ID

DataWeave now supports the private modifier on fun, var, ns, and type declarations to hide them from importers.

W-21148967

internal is no longer a reserved word and can now be used as an identifier in DataWeave scripts.

W-21508044

The compiler now reports an error when overloads of the same function declare different visibility modifiers.

W-21362539

StackOverflowError no longer occurs in the type checker when resolving intersections of unbound type parameters.

W-20124753

Runtime errors no longer occur when invoking overloaded functions across modules.

W-21811015

Spurious type-check errors no longer occur when an optional key-value pair is assigned to a required one.

W-21351058

deferred values passed to the write function now terminate correctly.

W-20925604

Out-of-memory errors no longer occur when reading large text or CDATA sections with the indexed XML reader.

W-21006104

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
### Upgrade This version of DataWeave is bundled with Mule. DataWeave upgrades take place through Mule. See [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb#mule-upgrades). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave 2.13.0 Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-2.13.0-release-notes.adoc - include::dataweave::partial$dataweave-intro.adoc\[\] For more detail, see [DataWeave Language](https://docs.mulesoft.com/dataweave/latest/). ## [](#october-6-2026)October 6, 2026 DataWeave 2.13.0 is bundled with the Mule 4.13.0 release. For details about the Mule release, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). ### What’s New The 2.13.0 version of DataWeave introduces these new features and enhancements: JSON Web Token Signing: - DataWeave introduces the `dw::util::jwt::HMAC` module for creating signed JSON Web Tokens (JWTs) with the HS256, HS384, and HS512 algorithms. See [HMAC (dw::util::jwt::HMAC)](https://docs.mulesoft.com/dataweave/latest/dw-hmac). - DataWeave introduces the `dw::util::jwt::RSA` module for creating signed JWTs with the RS256, RS384, and RS512 algorithms using unencrypted PKCS#1 or PKCS#8 PEM private keys. See [RSA (dw::util::jwt::RSA)](https://docs.mulesoft.com/dataweave/latest/dw-rsa). ### Compatibility This table specifies which version of DataWeave is bundled with each Mule runtime engine release:
Mule Version DataWeave Version

4.13

2.13

4.12

2.12

4.11

2.11

4.10

2.10

4.9

2.9

4.8

2.8

4.7

2.7

4.6

2.6

4.5

2.5

4.4

2.4

4.3

2.3

4.2

2.2

4.1

2.1

3.9

1.2

3.8

1.1

3.7

1.0
### Fixed Issues The release addresses these DataWeave issues and incorporates all patch updates from the 2.12.0 DataWeave release through October 2026:
Issue Resolution ID

Memory usage for text/plain output is reduced.

W-20063270

Eagerly materialize executable Weave reader results.

W-23837275

Thread safety is improved when processing Java map values.

W-23661641

DataWeave tooling now reports design-time warnings when Java classes referenced in application/java schemas can’t be found or are inaccessible through JPMS.

W-22797049

DataWeave now filters Java classes in JPMS-unexported packages during Java module resolution, preventing runtime IllegalAccessException failures. This behavior is enabled by default on JDK 17 and later with DataWeave language version 2.13 and later. To keep the previous behavior, set mule.dw.filter_jpms_inaccessible_modules=false.

W-22779527

Cryptographic security warnings and errors now include call stacks.

W-22144340
### Upgrade This version of DataWeave is bundled with Mule. DataWeave upgrades take place through Mule. See [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb#mule-upgrades). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave 2.4.0 Release Notes ## [](#july-2024)July 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Unicode characters now render correctly at the beginning of the string when using the DataWeave writer function with the onlyData flag enabled.

W-14855645

The Apache POI library is now upgraded.

W-18253747
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#june-2024)June 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

A memory leak of the binding context no longer occurs when using the foreach scope.

W-18472194

DataWeave now correctly parses unquoted strings without raising a format error.

W-18118138
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#november-2024)November 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Apache POI folder used for temporal files is no longer deleted.

W-16899674
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#september-2024)September 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

DataWeave now preserves MimeType properties correctly.

W-16161736
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#july-2024-2)July 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The Flat File module now adds the substituteCharacterAsMissingValue reader property.

W-15571377

The Flat File module now adds the fillRedefinesByMaxLength writer property.

W-15973636
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#june-2024-2)June 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

The Excel writer now generates XLSX files using ZIP specification 2.0.

W-15534640
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#may-2024)May 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Internal libraries are now upgraded.

W-15296551
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#april-2024)April 2024 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The Excel reader no longer reads furigana characters.

W-14991276

Coercion of the third parameter on the ternary function executor now works as expected.

W-15061008
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#february-2024)February 2024 ### [](#patch-2-4-0-20240119-20240215)Patch 2.4.0-20240119-20240215 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Performance is now improved when coercing addition and subtraction operations.

W-14927555
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ### [](#patch-2-4-0-20240119)Patch 2.4.0-20240119 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Caching now works correctly when coercing for addition and subtraction operations.

W-14591653

do scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.

W-14514837
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#november-2023)November 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The cached function coercion now works correctly for a second time when an argument is constant.

W-13763138

The DataWeave sum function with a single numeric string arg now returns Number type instead of String.

W-14086694

Reading Avro schema with an array of enum type items no longer returns an error.

W-14252745

Inconsistent XML encoding detection no longer occurs between indexed and in-memory parsers.

W-13805995
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#october-2023)October 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

System property com.mulesoft.dw.xml_writer.declareXmlNamespace has been included to manage adding implicit namespaces like xml in the XML writer.

W-11965399

Temporary files are now closed for inputs bigger than 1.5 MB.

W-13868202

Milliseconds information is now preserved when converting the java.util.Date type.

W-14002706
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#september-2023)September 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

An invalid UUID logical type in Avro module now throws an exception as expected.

W-13943112
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#july-2023)July 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Multipart reader performance is enhanced by using the proper input stream implementation.

W-13099773
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#june-2023)June 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Streaming support now works correctly for JSON.

W-11790958
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#may-2023)May 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Closing resources immediately after reading when using text/plain MIME type.

W-12398584

Incorrect trimming of whitespaces no longer occurs when reading XML content.

W-12528980

Fixed splitBy management of large strings so String and Regex options are consistent with each other.

W-12452407
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#april-2023)April 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Added cache Java values evaluation to avoid consuming streams more than once.

W-12635909
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#march-2023)March 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Fixed IndexOutOfBoundsException that occurred when combining the usage of heap memory for internal buffering with a customized buffer size.

W-12247447
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#february-2023)February 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

dw::core::Dates::atBeginningOfWeek now works correctly when the input DateTime is Sunday.

W-11940166

The new com.mulesoft.dw.javaSqlDateToDate system property enables mapping java.sql.Date to Date instead of DateTime.

W-12043162

The Resource already closed exception no longer occurs when using the write function with a value bigger than 1.5MB with Avro format.

W-12067821

Cacheable overloaded functions, such as then, now dispatch to the correct function definition when called multiple times.

W-12073562

The default behavior now works correctly when having a null value coming from the Mule runtime.

W-12166609

High memory usage no longer occurs when using the dw::core::Arrays::divideBy function with an in-memory Array as input.

W-12167313
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#january-2023)January 2023 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The function dw::core::Dates::atBeginningOfHour now works as expected when an hour is represented as a single digit.

W-11620156

Escaped quote characters now work as expected in CSV Module.

W-12128349

The FlatFile module now provides a reader property, retainEmptyStringFieldsOnParsing, for handling fields that lack values. When set to true, this property makes the reader retain these fields and set their values to an empty string. The default behavior of the reader is to remove those fields.

W-12036336

Data payloads without line breaks no longer work when using lenient as the recordParsing property. The other options to recordParsing support records that lack line breaks. noTerminator is preferred for fixed-length records that lack a line break.

W-12472890
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#november-2022)November 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

onNull functions now work as expected.

W-11865849

Instead of returning an empty array in some scenarios, iterating flat file arrays now work as expected.

W-11932440
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#september-2022)September 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The Mule patch release addresses the following DataWeave issues:
Description Issue

Visual Studio Code extension no longer breaks with binary input format in the test scenario inputs directory.

W-11507190

Namespace is now added on elements when previously used at a deeper structure level.

W-11349764
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#august-2022)August 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The August Mule patch release addresses the following DataWeave issues:
Description Issue

The message for the StackOverflow script compilation error is no longer hidden.

W-11215958
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#july-2022)July 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The July Mule patch release addresses the following DataWeave issues:
Description Issue

Writing binary values with the JSON writer no longer outputs the base of the values.

W-11326859

This release fixes Avro property handling.

W-11324418

This release improves handling of streams that do not declare a size.

W-11277575

Fix write function so Avro format can be handled.

W-11047202

This release improves handling of string values in XML format.

W-11273037
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#june-2022)June 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The June Mule patch release addresses the following DataWeave issues:
Description Issue

DataWeave now parses Java objects without errors.

W-10832766

The text/plain reader now correctly ignores the byte order mark (BOM). The JSON writer now uses the encoding information available in Binary values when writing them as String values instead of using the writer configuration encoding. To restore the previous behavior, enable the system property com.mulesoft.dw.decode_binaries_with_writer_encoding.

W-10696255

Multiline string indentation on YAML now works correctly.

W-10955882

The FlatFile module now includes the allowLenientWithBinaryNotEndElement property to support existing behavior.

W-10935528

Fixed ClassCastException in multipart module.

W-10943884

DataWeave now shows a descriptive error when there is an unsupported output mime type.

W-10876534

The indexed XML reader no longer adds unnecessary text fields to XML objects.

W-10942171
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#march-2022)March 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The March Mule patch release addresses the following DataWeave issues:
Description Issue

A direct memory error no longer occurs when the com.mulesoft.dw.directbuffer.disable system property is enabled.

SE-24186

Duplicate declarations for namespace prefixes in XML no longer occur.

W-10648792 / DW-1081

Exceptions are no longer thrown due to use of the default operator with fromBase64.

W-10648825 / SE-23812

Avro unions with enums are now supported.

W-10706991
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#february-2022)February 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The February Mule patch release addresses the following DataWeave issues:
Description Issue

An endless loop issue no longer occurs when writing a CSV file with bufferSize=0.

DW-1074

Creating sample files using the binary type no longer causes an error.

DW-390

Corrected the documentation of the`Periods::between` function.

DW-1070

Upgraded some dependencies, including avro and jackson, and removed unused AWS dependencies (#1673).

DW-1080

Upgraded the edi-parser with SLF4J.

CONN-9598

Performing transformations from avro to other formats no longer causes an exception when the enum type field is present.

SE-23802
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#january-2022)January 2022 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The January Mule patch release addresses the following DataWeave issues:
Description Issue

Flow retyping inside dynamic functions now works as expected.

DW-677

DataWeave no longer incorrectly sets autostreaming.

DW-918

The UnsupportedTypeCoercionToLiteralException error is now caught when using the similar operator (~=).

DW-932

JSON streaming now works correctly.

DW-940

The AttributeDelegate function no longer causes a stack overflow error.

SE-23494

Removing objects by property name now works as expected.

SE-23444

When using arrays, the XML writer properly keeps namespaces.

SE-23299

DataWeave now correctly parses large strings in JSON transformations.

SE-23291

A Scatter Gather issue that caused DataWeave to throw the ArrayIndexOutOfBoundsException error no longer occurs.

SE-22431

Comparison operators for dateTime type now work as intended.

SE-22025

Local variable resolution now works as expected.

SE-21847

Avoid closing resources prematurely when using the write function, which affects MUnit tests.

SE-23483

Fix OutOfMemory error using writeLinesWith function, which affected the ndjson module.

SE-23759
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#november-2021)November 2021 DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The November Mule patch release addresses the following DataWeave issues:
Description Issue

Fixed a ClassCastException that occurred in the Avro module by correcting its generated MIME type.

SE-21869

Comments within YAML files processed in Mule applications are no longer erased.

DW-706

You can now disable the removal of self-referencing implicit variables.

DW-893

DataWeave now allows mixed content structures (text and nodes) when reading and writing XML content.

SE-21464

Functions in the Dates module now accept one-digit numbers for months and days.

DW-894

Improved the performance of splitting functionality.

DW-776

Improved the performance of the JSON module.

DW-706
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes). ## [](#october-5-2021)October 5, 2021 Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-2.4.0-release-notes.adoc - include::dataweave::partial$dataweave-intro.adoc\[\] For more detail, see [DataWeave Language](https://docs.mulesoft.com/dataweave/latest/). ## What’s New The 2.4.0 version of DataWeave introduces new features and enhancements. Release notes for previous versions of DataWeave are available within [Mule Runtime Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb). ### [](#new-features)New Features - Ability to read larger-than-memory strings automatically. When you are using the indexed reader strategy and processing a string with a size larger than 1.5 MB, DataWeave automatically splits the value in chunks to avoid out-of-memory issues. Related reader properties include `com.mulesoft.dw.max_memory_allocation` and `com.mulesoft.dw.buffered_char_sequence.enabled`. Refer to [Indexed Readers in DataWeave](https://docs.mulesoft.com/jp/dataweave/2.4/dataweave-indexed-readers#large-strings-management). - New reader and writer properties for working with data formats. For example, the XML writer now enables you to define namespaces at the root level. - Many new modules, functions, types, annotations, and variables. Some are experimental and subject to change in future releases. For additional detail, see [What’s New in DataWeave](https://docs.mulesoft.com/jp/dataweave/2.4/whats-new-in-dw) ### [](#enhancements)Enhancements A number of DataWeave functions are overloaded to introduce new helper functions for handling `null` values, including: - Core: - `entriesOf` - `namesOf` - `keysOf` - `valuesOf` - `replace` - `--` - `contains` - `sizeOf` - `endsWith` - `joinBy` - `scan` - `splitBy` - `startsWith` - `matches` - `match` - Arrays: - `countBy` - `sumBy` - `divideBy` - `take` - `drop` - `slice` - `indexWhere` - `splitAt` - `takeWhile` - `dropWhile` - `splitWhere` - `partition` - `firstWith` - Strings: - `charCode` - `charCodeAt` - `fromCharCode` - `repeat`
The default operator no longer captures null function calls because the functions themselves now manage the null value. Uses of these functions with the default operator might behave unexpectedly for this reason.
## Compatibility This table specifies which version of DataWeave is bundled with each Mule runtime engine release:
Mule Version DataWeave Version

4.13

2.13

4.12

2.12

4.11

2.11

4.10

2.10

4.9

2.9

4.8

2.8

4.7

2.7

4.6

2.6

4.5

2.5

4.4

2.4

4.3

2.3

4.2

2.2

4.1

2.1

3.9

1.2

3.8

1.1

3.7

1.0
## Fixed Issues The following table lists bug fixes that are specific to the initial release of DataWeave 2.4.0. This release also incorporates all fixes to DataWeave, including patch updates through the September 2021 release, that are listed in [Mule Runtime 4.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.3.0-release-notes).
Description Issue

Added the writeDeclaredNamespaces XML writer property to write all declared namespaces in the root element.

DW-16

Added the writeDeclaration YAML writer property to avoid writing the header declaration.

DW-162

Added a new Strings module for easier string data management.

DW-406

Added the constant folding functionality so that DataWeave replaces operations involving constant values with the actual result. For example, 1024*8 is replaced at compile time with the resulting value 8192.

DW-427

Added flow retyping to the type system, which enables better accuracy within flow-control structures featuring checks that involve typing.

DW-438

Added code inspectors so that quick fixes are suggested with best practices, such as replacing null checks with a default expression, or replacing sizeOf() == 0 with isEmpty().

DW-33/DW-632

Added an inspection to replace using with do blocks.

DW-771

Improved error messages when creating Java objects.

DW-565

Improved performance on floating point number parsing by identifying in advance if the number has a floating point or not.

SE-20614

Extended the common subexpression elimination process to work with index selectors.

SE-19934

Added functions that work with null values to the Core, Arrays, and String modules.

DW-425

Improved JSON performance by copying bytes from input to output directly during JSON-to-JSON data transformations.

DW-230

Improved YAML support of scalar types, string quotations, custom tags, and comment retention.

DW-687

Added the filterTree function to the Tree module to be able to filter any data structure.

DW-160

Added validations for index tokens in CSV format.

DW-577

Added support for the Java classes OptionalInt, OptionalDouble and OptionalLong.

DW-628

Added support for file:/example/file.txt as a valid URL.

DW-195

Added warning when using the design-time only format application/dw without dataOnly mode.

DW-873

Added experimental run and eval functions to dynamically execute scripts.

DW-170

Added the concept of optional function parameters in the type system.

DW-874

Improved CSV streaming to avoid unnecessary processing.

DW-876

Improved the mapObject function to avoid unnecessary processing.

DW-535

Improved the flatten function to avoid unnecessary processing.

DW-509

Improved code validation. Now an error returns when a variable is using the same name as an input.

DW-522

Improved the precision of math operations and added a property to retain the previous behavior: com.mulesoft.dw.math.exact_precision.

SE-16452

Improved handling of big XML files to fix potential I/O exceptions.

DW-250

Fixed error locations when scripts feature dynamic string selectors.

DW-875

Fixed a false negative error message when using multiple union types.

DW-297

The write function return types are now consistent with input types.

DW-298

The update operator no longer fails when working with repeated keys and attributes.

DW-306

Processing of XML documents with comments and streaming enabled now works as expected.

DW-307

DataWeave no longer fails to parse a single key-value pair with a conditional and parentheses.

DW-309

The type system now validates overloaded functions as parameters.

DW-316

Parallel processing on ndjson now works as expected.

DW-325

Fixed a materialization and streaming failure.

DW-368

Fixed the behavior of the slice function.

DW-409/DW-410

Fixed the ability to import namespaces from external modules.

DW-414

DataWeave now produces the error Division by Zero when dividing by 0.0 instead of an internal exception.

DW-415

DataWeave now properly validates that do blocks do not contain any reserved word declaration.

DW-416

Running flatten on flatten no longer causes loss of values.

DW-691

The update operator now works when no attribute is defined.

DW-216

Improved handling of binary data to prevent running out of memory when calculating sizes of processed data.

SE-16559

The com.mulesoft.dw.coercionexception.verbose property no longer logs data from coercion exceptions.

SE-15487

Using nested binary functions no longer produces a StackOverflow error.

SE-16092

DataWeave no longer returns UnsupportedOperationException when parsing an invalid script.

DW-294

Fixed a potential IndexOutOfBoundException when using overloaded functions with four parameters.

DW-159

Added support for dumping Flat File and Avro schemas when com.mulesoft.dw.dump_files is enabled.

DW-137

Improved code compilation. Implicit inputs are not added if a variable with the same name is explicitly defined.

DW-630
## Upgrade For upgrades to the 2.4.0 version of DataWeave, which is bundled within Mule runtime engine, see [Upgrading Mule Runtime Engine (Versions 4.x to 4.n)](https://docs.mulesoft.com/jp/release-notes/mule-runtime/updating-mule-4-versions). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave 2.6.0 Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-2.6.0-release-notes.adoc - include::dataweave::partial$dataweave-intro.adoc\[\] For more detail, see [DataWeave Language](https://docs.mulesoft.com/dataweave/latest/). ## [](#september-2026)September 2026 DataWeave 2.6.30 is bundled with the Mule 4.6.34 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#august-2026)August 2026 DataWeave 2.6.29 is bundled with the Mule 4.6.33 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#july-2026)July 2026 DataWeave 2.6.28 is bundled with the Mule 4.6.32 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

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 per_app_java_bean_cache compatibility flag.

W-22417507
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#june-2026)June 2026 DataWeave 2.6.27 is bundled with the Mule 4.6.31 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

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 per_app_java_bean_cache compatibility flag.

W-22417507
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#may-2026)May 2026 DataWeave 2.6.26 is bundled with the Mule 4.6.30 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#april-2026)April 2026 DataWeave 2.6.25 is bundled with the Mule 4.6.29 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#march-2026)March 2026 DataWeave 2.6.24 is bundled with the Mule 4.6.28 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#january-2026)January 2026 DataWeave 2.6.22 is bundled with the Mule 4.6.25 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20618375

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#november-2025)November 2025 DataWeave 2.6.20 is bundled with the Mule 4.6.24 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#october-2025)October 2025 DataWeave 2.6.19 is bundled with the Mule 4.6.23 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334

Module compilation performance is improved when running concurrently.

W-19376546
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#august-2025)August 2025 DataWeave 2.6.17 is bundled with the Mule 4.6.21 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

A stackOverflowException error no longer occurs during materialization.

W-18981240

The distinctBy function in dw::core::Core now works as expected when used with a CSV input.

W-18990604

DataWeave runtime types are now correctly written when outputting Java.

W-18942349

Access to multipart content raw value no longer reads the part content.

W-18892158

The sizeOf function now works correctly in DataWeave 2.6.14 and later.

W-18850597

The orderBy function now evaluates ordering criteria only when required.

W-18851259

The fromCharCode function now works as expected.

W-17204482
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#july-2025)July 2025 DataWeave 2.6.16 is bundled with the Mule 4.6.20 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

This patch update reverts the fix.

W-17167283

XML encoding detection now works correctly when the declaration header is missing.

W-18853667

The fromCharCode function in dw::core::Strings. now manages surrogate characters correctly.

W-17204482

Unicode characters now render correctly at the beginning of the string when using the DataWeave writer function with the onlyData flag enabled.

W-14855645

The Apache POI library is now upgraded.

W-18253747

Experimental warning messages are no longer logged on DataWeave SDK files.

W-16384926
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#june-2025)June 2025 DataWeave 2.6.15 is bundled with the Mule 4.6.18 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The performance of the orderBy function is now improved.

W-18439576

Reading a CSV file inside a MultiPart body now works correctly when performed more than once.

W-17147598

A memory leak of the binding context no longer occurs when using the foreach scope.

W-18472194
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#may-2025)May 2025 DataWeave 2.6.14 is bundled with the Mule 4.6.16 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Materialization issues no longer occur when using CSV content inside variables.

W-17167283

A compatibility flag is now added to address the different results produced by calling sizeOf with NumberType.

W-18020856

An unnecessary import is now removed from dw::util::Diff to eliminate a warning when running MUnit.

W-17670504

DataWeave no longer returns a format error on readUnquotedString.

W-18118138

Overflowing no longer occurs while reading large file on multipart format.

W-17644871

Performance issues no longer occur when using the Mule API Java class Message in DataWeave scripts.

W-18034217

DataWeave now preserves trailing zeroes of single-element sum.

W-17283050
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#march-2025)March 2025 DataWeave 2.6.12 is bundled with the Mule 4.6.14 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The Flat File Module now supports YAML files with nested depth greater than 50.

W-17495145

xerces-j is now updated to 2.12.2.

W-16918194
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#february-2025)February 2025 DataWeave 2.6.11 is bundled with the Mule 4.6.12 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#january-2025)January 2025 ### [](#january-17-2025)January 17, 2025 - The Mule 4.6.11 patch update reverts the fixes for the following DataWeave issues: W-16823030, W-17206423, and W-17372664. ### [](#patch-2-6-10)Patch 2.6.10 DataWeave 2.6.10 is bundled with the Mule 4.6.10 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030

The Java reflection lookup strategy is now improved for bean instances.

W-17206423
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#november-2024)November 2024 DataWeave 2.6.9 is bundled with the Mule 4.6.9 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The stripTrailingZeroes compatibility flag is now added to preserve the decimal format.

W-17030593

Apache POI folder used for temporal files is no longer deleted.

W-16899674
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#october-2024)October 2024 DataWeave 2.6.8 is bundled with the Mule 4.6.8 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

DataWeave descendant selector performance is now improved.

W-16343577

Streaming capability for arguments at sum, countBy, and sumBy functions is now enabled.

W-16125755

Input/output MimeType properties are now preserved as expected.

W-16161736

Access error for Java 17 encapsulation errors is now improved.

W-15705596

Coercion error is now caught inside try as expected.

W-15323897
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#september-2024)September 2024 DataWeave 2.6.7 is bundled with the Mule 4.6.7 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

DataWeave now preserves MimeType properties correctly.

W-16161736
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#august-2024)August 2024 DataWeave 2.6.6 is bundled with the Mule 4.6.6 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Argument materialization is now improved at the dw::Runtime::try function.

W-15323897

Streaming capability is now enabled for arguments of sum, countBy, and sumBy functions.

W-16125755
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#july-2024)July 2024 DataWeave 2.6.5 is bundled with the Mule 4.6.5 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Enforced Java accessibility restrictions only for Mule apps with DataWeave language level version 2.6 and later and executing with Java 17 and later.

W-15832793

Materialization issues no longer occur with schema properties.

W-15839190

The Flat File module now adds the substituteCharacterAsMissingValue reader property.

W-15571377

The Flat File module now adds the fillRedefinesByMaxLength writer property.

W-15973636
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#june-2024)June 2024 DataWeave 2.6.4 is bundled with the Mule 4.6.4 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

The Excel writer now generates XLSX files using ZIP specification 2.0.

W-15534640

When comparing a Date with a String representation of a date, the Date format is now used to coerce the String accordingly.

W-15478713

Access error messages for Java 17 encapsulation errors are now improved.

W-15705596
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#may-2024)May 2024 DataWeave 2.6.3 is bundled with the Mule 4.6.3 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

ArithmeticException no longer executes toHex with non-integer numbers.

W-15006840

Performance degradation no longer occurs when an array is concatenated.

W-15399854
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#april-2024)April 2024 DataWeave 2.6.2 is bundled with the Mule 4.6.2 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Inconsistent behavior no longer occurs between in-memory and streaming XML parsers for deciding document encoding.

W-15110015

Streaming for DataWeave-based data formats like ndjson now works as expected.

W-15262860

The Excel reader no longer reads furigana characters.

W-14991276

Coercion of the third parameter on the ternary function executor now works as expected.

W-15061008
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#march-2024)March 2024 DataWeave 2.6.1 is bundled with the Mule 4.6.1 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Performance is now improved when coercing addition and subtraction operations.

W-14927555
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ## [](#february-6-2024)February 6, 2024 DataWeave 2.6.0 is bundled with the Mule 4.6.0 release. For details about the Mule release, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). ### What’s New The 2.6.0 version of DataWeave introduces these new features and enhancements: Extended format support: - DataWeave now supports Java 17. See [Java Format](https://docs.mulesoft.com/dataweave/latest/dataweave-formats-java). - Mule expression language service are now modularized. ### Compatibility This table specifies which version of DataWeave is bundled with each Mule runtime engine release:
Mule Version DataWeave Version

4.13

2.13

4.12

2.12

4.11

2.11

4.10

2.10

4.9

2.9

4.8

2.8

4.7

2.7

4.6

2.6

4.5

2.5

4.4

2.4

4.3

2.3

4.2

2.2

4.1

2.1

3.9

1.2

3.8

1.1

3.7

1.0
### Fixed Issues The release addresses the following DataWeave issues and incorporates all patch updates from the 2.5.0 DataWeave release through January 2024:
Issue Resolution ID

Caching now works correctly when coercing for addition and subtraction operations.

W-14591653

do scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.

W-14514837

The minInflateRatio property is now added to Excel format to control the zip bomb check threshold.

W-14315728
### Upgrade This version of DataWeave is bundled with Mule. DataWeave upgrades take place through Mule. See [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb#mule-upgrades). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave 2.9.0 Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-2.9.0-release-notes.adoc - include::dataweave::partial$dataweave-intro.adoc\[\] For more detail, see [DataWeave Language](https://docs.mulesoft.com/dataweave/latest/). ## [](#september-2026)September 2026 DataWeave 2.9.18 is bundled with the Mule 4.9.21 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

Vulnerable dependencies are upgraded to address reported security vulnerabilities.

W-23924223

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#august-2026)August 2026 DataWeave 2.9.17 is bundled with the Mule 4.9.20 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#july-2026)July 2026 DataWeave 2.9.16 is bundled with the Mule 4.9.19 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#june-2026)June 2026 DataWeave 2.9.15 is bundled with the Mule 4.9.18 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#may-2026)May 2026 DataWeave 2.9.14 is bundled with the Mule 4.9.17 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#april-2026)April 2026 DataWeave 2.9.13 is bundled with the Mule 4.9.16 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#march-2026)March 2026 DataWeave 2.9.12 is bundled with the Mule 4.9.15 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#february-2026)February 2026 DataWeave 2.9.11 is bundled with the Mule 4.9.13 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#january-2026)January 2026 DataWeave 2.9.10 is bundled with the Mule 4.9.12 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#november-2025)November 2025 DataWeave 2.9.9 is bundled with the Mule 4.9.11 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#october-2025)October 2025 DataWeave 2.9.8 is bundled with the Mule 4.9.10 release. The Mule patch release addresses these DataWeave issues:
Issue Resolution ID

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#september-2025)September 2025 DataWeave 2.9.7 is bundled with the Mule 4.9.9 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

W-19376546
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#august-2025)August 2025 DataWeave 2.9.6 is bundled with the Mule 4.9.8 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

A stackOverflowException error no longer occurs during materialization.

W-18981240

The distinctBy function in dw::core::Core now works as expected when used with a CSV input.

W-18990604

DataWeave runtime types are now correctly written when outputting Java.

W-18942349

Access to multipart content raw value no longer reads the part content.

W-18892158

The sizeOf function now works correctly in DataWeave 2.6.14 and later.

W-18850597

The orderBy function now evaluates ordering criteria only when required.

W-18851259
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#july-2025)July 2025 DataWeave 2.9.5 is bundled with the Mule 4.9.7 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

This patch update reverts the fix.

W-17167283

XML encoding detection now works correctly when the declaration header is missing.

W-18853667

The fromCharCode function in dw::core::Strings. now manages surrogate characters correctly.

W-17204482

Unicode characters now render correctly at the beginning of the string when using the DataWeave writer function with the onlyData flag enabled.

W-14855645

The Apache POI library is now upgraded.

W-18253747

Experimental warning messages are no longer logged on DataWeave SDK files.

W-16384926
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#june-2025)June 2025 DataWeave 2.9.4 is bundled with the Mule 4.9.6 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

XML encoding is now detected before selecting a parser.

W-17637749

The performance of the orderBy function is now improved.

W-18439576

Reading a CSV file inside a MultiPart body now works correctly when performed more than once.

W-17147598

A memory leak of the binding context no longer occurs when using the foreach scope.

W-18472194

CompilationResult no longer retains a reference to the execution frame, which previously caused a memory leak.

W-18288980
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#may-2025)May 2025 DataWeave 2.9.3 is bundled with the Mule 4.9.4 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Materialization issues no longer occur when using CSV content inside variables.

W-17167283

DataWeave now preserves trailing zeroes of single-element sum.

W-17283050

A compatibility flag is now added to address the different results produced by calling sizeOf with NumberType.

W-18020856

An unnecessary import is now removed from dw::util::Diff to eliminate a warning when running MUnit.

W-17670504

DataWeave no longer returns a format error on readUnquotedString.

W-18118138

Overflowing no longer occurs while reading large file on multipart format.

W-17644871

Performance issues no longer occur when using Message in DataWeave scripts.

W-18034217
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#april-2025)April 2025 DataWeave 2.9.2 is bundled with the Mule 4.9.3 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

Concurrency issues no longer occur when loading modules.

W-17918619

The flat file module no longer fails when loading files with a nested depth greater than 50.

W-17495145

xerces-j is now updated to 2.12.2.

W-16918194
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#march-2025)March 2025 DataWeave 2.9.1 is bundled with the Mule 4.9.2 release. The Mule patch release addresses the following DataWeave issues:
Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Consuming values now work as expected when using overloaded materialized functions.

W-17588914
For details about the Mule release and patch updates, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ## [](#february-6-2025)February 6, 2025 DataWeave 2.9.0 is bundled with the Mule 4.9.0 release. For details about the Mule release, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). ### What’s New The 2.9.0 version of DataWeave introduces these new features and enhancements: Extended format support: - DataWeave introduces support for the Event Stream format. See [Event Stream Format](https://docs.mulesoft.com/dataweave/latest/dataweave-formats-eventstream). General improvements: - DataWeave incorporates new system properties. See [DataWeave System Properties](https://docs.mulesoft.com/dataweave/latest/dataweave-system-properties). ### Compatibility This table specifies which version of DataWeave is bundled with each Mule runtime engine release:
Mule Version DataWeave Version

4.13

2.13

4.12

2.12

4.11

2.11

4.10

2.10

4.9

2.9

4.8

2.8

4.7

2.7

4.6

2.6

4.5

2.5

4.4

2.4

4.3

2.3

4.2

2.2

4.1

2.1

3.9

1.2

3.8

1.1

3.7

1.0
### Fixed Issues The release addresses the following DataWeave issues and incorporates all patch updates from the 2.8.0 DataWeave release through January 2025:
Issue Resolution ID

Java module now honors Java bean accessor methods.

W-17142345
### Upgrade This version of DataWeave is bundled with Mule. DataWeave upgrades take place through Mule. See [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb#mule-upgrades). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave Body Transformation The DataWeave Body Transformation policy transforms the body of request or response traffic with a DataWeave script. For configuration details, see [DataWeave Body Transformation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-dataweave-body-transformation). ## [](#september-2-2026)September 2, 2026 ### What’s New - DataWeave Body Transformation policy implementation version 1.1.0 is now supported by Omni Gateway. - This policy’s implementation is updated to improve policy performance, delivering higher throughput and lower latency. ## [](#february-13-2026)February 13, 2026 ### What’s New - DataWeave Body Transformation policy definition version 1.0.0 is now supported by Omni Gateway. # DataWeave Extension Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-extension-release-notes.adoc - include::dataweave::partial$dataweave-extension-intro.adoc\[\] For more detail, see [DataWeave Extension](https://docs.mulesoft.com/dataweave/latest/dataweave-extension). ## [](#2-10-2)2.10.2 **March 21, 2025** ### What’s New DataWeave extension 2.10.2 introduces new features and enhancements: - DataWeave extension introduces support for multi-project workspaces. - DataWeave extension introduces support for DataWeave 2.9.0. - You can now integrate DataWeave extension with Anypoint Code Builder platform. ## [](#see-also)See Also - [DataWeave Extension](https://docs.mulesoft.com/dataweave/latest/dataweave-extension) - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave Headers Transformation The DataWeave Headers Transformation policy transforms headers of request or response traffic with a DataWeave script. For configuration details, see [DataWeave Headers Transformation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-dataweave-headers-transformation). ## [](#september-2-2026)September 2, 2026 ### What’s New - DataWeave Headers Transformation policy implementation version 1.0.1 is now supported by Omni Gateway. - This policy’s implementation is updated to improve policy performance, delivering higher throughput and lower latency. ## [](#february-13-2026)February 13, 2026 ### What’s New - DataWeave Headers Transformation policy definition version 1.0.0 is now supported by Omni Gateway. # DataWeave Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-release-notes.adoc - include::dataweave::partial$dataweave-intro.adoc\[\] - [DataWeave 2.13.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.13.0-release-notes) - [DataWeave 2.12.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.12.0-release-notes) - [DataWeave 2.11.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.11.0-release-notes) - [DataWeave 2.9.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.9.0-release-notes) - [DataWeave 2.6.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.6.0-release-notes) - [DataWeave 2.4.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.4.0-release-notes) (This version of the product has reached [End of Life](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf).) ## [](#dataweave-extension-release-notes)DataWeave Extension Release Notes Unresolved include directive in modules/ROOT/pages/dataweave/dataweave-release-notes.adoc - include::dataweave::partial$dataweave-extension-intro.adoc\[\] - [DataWeave Extension](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-extension-release-notes) ## [](#see-also)See Also - [Troubleshooting a Failing DataWeave Script](https://docs.mulesoft.com/dataweave/latest/dataweave-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # DataWeave Request Filter The DataWeave Request Filter policy filters requests by using a DataWeave script For configuration details, see [DataWeave Request Filter Policy](https://docs.mulesoft.com/gateway/latest/policies-included-dataweave-request-filter). ## [](#september-2-2026)September 2, 2026 ### What’s New - DataWeave Request Filter policy implementation version 1.0.1 is now supported by Omni Gateway. - This policy’s implementation is updated to improve policy performance, delivering higher throughput and lower latency. ## [](#february-13-2026)February 13, 2026 ### What’s New - DataWeave Request Filter policy definition version 1.0.0 is now supported by Omni Gateway. # Design Center Release Notes - [API Designer (Crowd)](https://docs.mulesoft.com/jp/release-notes/design-center/design-center-release-notes-api_specs) ## [](#see-also)See Also - [Troubleshooting](https://docs.mulesoft.com/design-center/design-troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Design Center Release Notes The following release notes are provided for Design Center: - [API Designer Release Notes](https://docs.mulesoft.com/jp/release-notes/design-center/design-center-release-notes) - [API Mocking Service Release Notes](https://docs.mulesoft.com/jp/release-notes/api-mocking-service/api-mocking-service-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Detokenization
This policy uses the legacy unified policy model. Therefore, the policy does not have implementation release notes in API Manager and all release notes are provided here.
## [](#1-2-1)1.2.1 **August 6, 2024** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### What’s New - Updated third party dependencies. ## [](#1-2-0)1.2.0 **February 07, 2024** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### What’s New - This policy is now compatible with Java 17 for Mule runtime versions 4.6.0 or later. ## [](#1-1-2)1.1.2 **January 06, 2021** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Added OAS 3.0 code snippet in the policy YAML file. - Improved error handling for WSDL APIs. ## [](#1-1-1)1.1.1 **Apr 30, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are made to the header manipulation engine. - Detokenization support is now provided for the `text/xml` and `application/soap+xml` payloads. ### [](#fixed-issues)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-1-0)1.1.0 **Mar 20, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Improved performance in header manipulation. ### [](#fixed-issues-2)Fixed Issues - Fixed error that caused the policy to apply the configuration in the response incorrectly. ## [](#1-0-0)1.0.0 **Jan 30, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.1** ## [](#see-also)See Also - [Detokenization Policy for Mule 4](#api-manager::policy-mule4-detokenization.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # DevKit Migration Tool (DMT) Release Notes The DMT enables the migration of a connector built with DevKit that runs on Mule 3.x to a Mule 4 SDK compatible project. ## [](#1-0-0)1.0.0 **May 18, 2018** ### [](#new-features-and-enhancements)New Features and Enhancements None ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds - `mule-devkit-maven-plugin` needs to be removed from the pom.xml file in connectors that override it. ### [](#upgrade-requirements)Upgrade Requirements None ### [](#fixed-issues)Fixed Issues
Issue Description

DEVKIT-2260

DMT should fail gracefully when Restcall annotations & Soap Connect are used
## [](#0-9-1)0.9.1 **April 17, 2018** ### [](#new-features-and-enhancements-2)New Features and Enhancements None ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds - `mule-devkit-maven-plugin` needs to be removed from the pom.xml file of Connectors that overrides it. ### [](#upgrade-requirements-2)Upgrade Requirements None ### [](#fixed-issues-2)Fixed Issues
Issue Description

DMT beta fails when DevKit plugin is redefined in the extension POM

DEVKIT-2257

DMT: Migrate BulkOperationResult

DEVKIT-2258

DMT: @Transformer is not being replaced/migrated

DEVKIT-2259

DMT: Replace processor XMLTypes output for InputStream
## [](#0-9-0)0.9.0 **Mar 26, 2018** ### [](#new-features-and-enhancements-3)New Features and Enhancements Supports: - Processors - Sources - Connection Management - Configurations - Paged Processors - Metadata (MetaData Objects are not migrated, manual migration to the MetadataTypes is required) - OAuth 2 - Display Annotations - OnException Handlers ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds - `mule-devkit-maven-plugin` needs to be removed from the pom.xml file in connectors that override it. ### [](#upgrade-requirements-3)Upgrade Requirements None ## [](#see-also)See Also - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) - [Known Issues](https://help.salesforce.com/s/issues) # DHL Tracking Connector Release Notes Anypoint Connector for DHL Tracking (DHL Tracking Connector) enables Mule applications to access the DHL Tracking API. Guide: [DHL Tracking Connector User Guide](https://docs.mulesoft.com/dhl-tracking-connector/latest/) ## [](#1-1-1)1.1.1 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-1-0)1.1.0 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **December 18, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/dhl-tracking-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [DHL Tracking Connector User Guide](https://docs.mulesoft.com/dhl-tracking-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [DHL Tracking Connector User Guide](https://docs.mulesoft.com/dhl-tracking-connector/latest/) - [DHL Tracking Connector Reference](https://docs.mulesoft.com/dhl-tracking-connector/latest/dhl-tracking-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # DocuSign Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for DocuSign (DocuSign Connector) enables you to access the DocuSign platform and exposes operations provided by the DocuSign eSignature API v2.1. Guide: [DocuSign Connector User Guide](https://docs.mulesoft.com/jp/docusign-connector/latest/) ## [](#1-1-5)1.1.5 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
## [](#1-1-4)1.1.4 **August 26, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Bouncy Castle FIPS (bcpkix-fips) library is upgraded to version 2.1.12.

  • The Google Gson library is upgraded to version 2.14.0.

  • The Apache Commons Lang3 library is upgraded to version 3.20.0.

W-23441654
## [](#1-1-3)1.1.3 **May 5, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
### Fixed Issues
Issue Resolution ID

The connector now correctly refreshes the token when you configure the Resource Owner Id field with a dynamic value. Previously, dynamic values prevented the connector from detecting token expiration, which caused the 401 Unauthorized error.

W-18512817
## [](#1-1-2)1.1.2 **April 19, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
### Fixed Issues
Issue Resolution ID

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21404084
## [](#1-1-1)1.1.1 **January 24, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
### Fixed Issues
Issue Resolution ID

The org.json:json library is upgraded to version 20251224 to address reported security vulnerabilities.

W-20834313
## [](#1-1-0)1.1.0 **April 1, 2025** ### What’s New - The connector now supports the JWT Connection Provider (JWT Grant) connection type. For more information, refer to [JWT Connection Provider (JWT Grant)](https://docs.mulesoft.com/jp/docusign-connector/latest/docusign-connector-reference#Config_Jwt). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
## [](#1-0-8)1.0.8 **July 17, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
### Fixed Issues
Issue Resolution ID

If an access token is invalid, the connector now generates a new access token using a refresh token.

W-16121817
## [](#1-0-7)1.0.7 **April 15, 2024** ### What’s New - Internal code structure changes to enable FIPS validation functionality (same as in version 1.0.6). ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
## [](#1-0-6)1.0.6 **April 8, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

DocuSign eSignature API

2.1
## [](#1-0-5)1.0.5 **March 7, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8 and 11

DocuSign eSignature API

2.1
### Fixed Issues
Issue Resolution ID

The connector now throws a DOCUSIGN:UNAUTHORIZED error instead of a MULE:UNKNOWN error when you don’t have the required permission or when a token has expired.

W-14193529
## [](#1-0-4)1.0.4 **October 2, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

DocuSign eSignature API

2.1
### Fixed Issues
Issue Resolution ID

The test connection functionality now works correctly because it uses the expected base URL and the correct DocuSign service.

W-13658556
## [](#1-0-3)1.0.3 **December 23, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

DocuSign eSignature API

2.1
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9682
## [](#1-0-2)1.0.2 **December 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

DocuSign eSignature API

2.1
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9558
## [](#1-0-1)1.0.1 **September 13, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

DocuSign eSignature API

2.1
### Fixed Issues
Issue ID

Modified the display names for authorization types to make them more suggestive.

CONN-8840, CONN-8841
## [](#1-0-0)1.0.0 **April 21, 2021** ### [](#compatibility-15)Compatibility DocuSign Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

DocuSign eSignature API

2.1
### [](#features)Features This is a new connector. For a list of supported configurations and operations, see the DocuSign Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Dropbox Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Dropbox (Dropbox Connector) enables you to execute Dropbox API operations in your Mule flows. Guide: [Dropbox Connector User Guide](https://docs.mulesoft.com/jp/dropbox-connector/latest/) ## [](#1-0-13)1.0.13 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17

Dropbox API

v2
## [](#1-0-12)1.0.12 **August 27, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17

Dropbox API

v2
## [](#1-0-11)1.0.11 **August 26, 2026** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17

Dropbox API

v2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core, jackson-annotations, jackson-databind, and jackson-datatype-jsr310 libraries are upgraded to version 2.22.2.

  • The org.json library is upgraded to version 20260814.

  • The commons-io library is upgraded to version 2.22.0.

W-23840869
## [](#1-0-10)1.0.10 **April 19, 2026** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17

Dropbox API

v2
### Fixed Issues
Issue Resolution ID

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21762063

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core library is upgraded to version 2.21.1.

  • The jackson-annotations library is upgraded to version 2.21.1.

  • The jackson-databind library is upgraded to version 2.21.1.

  • The jackson-datatype-jsr310 library is upgraded to version 2.21.1.

  • The commons-io library is added at version 2.21.0.

W-21508082
## [](#1-0-9)1.0.9 **April 7, 2025** ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17

Dropbox API

v2
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17871519
## [](#1-0-8)1.0.8 **May 24, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.4.0 and later

OpenJDK

8, 11, and 17

Dropbox API

v2
## [](#1-0-7)1.0.7 **October 26, 2022** ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.13.2.2 to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to address reported security vulnerabilities.

W-11845804
## [](#1-0-6)1.0.6 **April 11, 2022** ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920496
## [](#1-0-5)1.0.5 **February 17, 2022** ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
### Fixed Issues
Issue ID

Upgraded library dependencies.

W-10709987
## [](#1-0-4)1.0.4 **January 12, 2022** ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
### Fixed Issues
Issue ID

The connector could not read the access token. To fix this issue, the custom @AuthCode expressions for the access token, refresh token, and expire token have been removed.

SE-24116
## [](#1-0-3)1.0.3 **January 11, 2022** ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9852
## [](#1-0-2)1.0.2 **December 21, 2021** ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9635
## [](#1-0-1)1.0.1 **December 14, 2021** ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9565
## [](#1-0-0)1.0.0 **October 19, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Dropbox Connector reference. ### Compatibility
Software Version

Mule Runtime

4.4.0 and later

OpenJDK

8 or 11

Dropbox API

v2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Early Access RAML 1.0 With the latest releases of the tooling and Anypoint Platform, MuleSoft introduces early access based on the official [RAML 1.0 specification](https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md). The new version introduces a number of new features listed in the RAML.org [comparison of releases](https://github.com/raml-org/raml-spec/wiki/RAML-1.0-RC1-vs-RC2). After months of working closely with the RAML workgroup, MuleSoft is synchronizing the MuleSoft product releases with the RAML 1.0 GA release. MuleSoft customers can explore 1.0 concepts in Anypoint Platform using RAML release candidates. In most cases, customers should be able to write API definitions using RAML 1.0 without issues, despite known gaps in the early access version, which this document describes.
Mule 3.8.1 and later provides full RAML 1.0 support.
## [](#migration-notice)Migration Notice Since RAML 1.0 is early access, the default version used in the tooling is 0.8. To try version 1.0, you have to change the version. To migrate from RAML 0.8 to RAML 1.0, see the list of [breaking changes](https://github.com/raml-org/raml-spec/wiki/Breaking-Changes) between RAML 0.8 and RAML 1.0.
RAML proxies based on RAML files written using the 1.0 version are valid only for Mule 3.8.0 runtimes. Previous Gateway versions don’t support RAML 1.0.
## [](#underlying-parsers-and-known-gaps)Underlying Parsers and Known Gaps For RAML 1.0 a new version of the [JavaScript](https://github.com/raml-org/raml-js-parser-2/tree/0.2.10) and [Java](https://github.com/raml-org/raml-java-parser/tree/v2) parsers have been implemented. MuleSoft tooling relies on these parsers to validate the RAML and expose the required APIs. The following table shows the tooling dependencies for the parser implementations:
Parser Tooling

JavaScript

  • API Designer

  • Mocking Service

  • API Console

  • Notebook

  • API Console in Studio

Java

  • Mule 3.8.0

  • APIkit 3.8.0

  • RAML Editor in Studio

  • HTTP Connector
## [](#javascript-parser-known-gaps)JavaScript Parser Known Gaps The current JavaScript parser is 100% compliant with the specification, without any known gaps. ## [](#java-parser-known-gaps)Java Parser Known Gaps The current Java parser is not yet fully compliant with the specification. The following table lists feature gaps:
Text Parameter

uses key

The spec supports the uses node in any fragment. Currently, the parser only allows the uses node in root level RAML documents and libraries.

Annotations for scalar fields

The spec allows applying annotations to scalar nodes in addition to certain mapping nodes. Annotations at the scalar level are not supported.

Overlays restrictions

Overlay application is not enforcing all the required restrictions. The extra restrictions that Overlays enforce versus Extensions are not validated.

Security Schemes gaps

  • OAuth 1.0 signatures setting is not supported

  • OAuth 2.0 authorizationUri is always optional, regardless of authorization grants.

XML Examples validations against YAML types

Validation of XML examples against types defined in YAML are not supported. XML validations are only supported for schemas defined in XSD format.

type system gaps

These features, related to the definition, are not supported:

  • Inheritance of primitive types

  • discriminator field

  • Examples nested in a value

  • Xml Facet field

  • Additional properties

  • null type

  • Properties named with trailing question marks
Refer to [“RAML 1.0 Features Gap”](https://github.com/raml-org/raml-java-parser/blob/0.1.0-alpha-2/MISSING.md) for the latest list. ## [](#support-gaps-by-product)Support Gaps by Product ### [](#api-console-and-mocking-service)API Console and Mocking Service API Console and Mocking Service depends on the JavaScript parser for parsing out data types and overall API behaviors. API Console and Mocking Service currently don’t support [annotations](https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md#annotations). When you run a RAML file with RAML 1.0 annotations in API Console, annotations do not appear in the Console documentation and Try It tab. Annotations are visible only from the RAML definition in API Designer, and have no effect in API Console and Mocking Service tools. ### [](#api-notebook)API Notebook API Notebook supports RAML 1.0 with the following limitations: - Data types are not meaningful in this context. - Overlays are not meaningful in this context. ### [](#apikit)APIkit APIkit depends on the Java parser for validating and scaffolding the RAML file, therefore it inherits the limitations of the Java parser listed above in the “Java Parser Known Gaps” section. When you try to scaffold a RAML file that contains elements not yet supported by the Java parser, validation fails and the flows are not generated. OData APIkit extension beta does not support RAML 1.0 or the new APIkit integrated within Studio 6.0. Customers using the OData extension, should postpone upgrading and continue to use Studio 5.4. The GA version of the OData implementation feature with Studio will be released in the near future. ### [](#studio)Studio Studio’s embedded RAML editor depends on the Java parser for validating and suggesting RAML 1.0 syntax. The embedded APIkit also depends also on the Java parser for the scaffolding feature (see below). The embedded API Console depends on the JavaScript parser, and has parity with the standalone API Console: - Suggester for RAML 1.0 does not support RAML types or RAML files without a header. Users might not benefit fully from the editor suggesting certain tags and auto-completion. - The embedded RAML 1.0 editor validation feature has parity with the Java parser. Using the syntax related to RAML 1.0 listed above in the “Java Parser Known Gaps” section, might cause incorrect validations. - MUnit RAML-to-Test auto-generation feature does not support RAML 1.0. We are actively working to evolve the feature. - DataSense currently does not support RAML 1.0 types. When the customer uses RAML 1.0, the metadata is not passed and leveraged by DataSense. ### [](#api-manager)API Manager Mule 3.8.0 depends on the Java parser. API Manager relies on Mule 3.8.0 support for auto-generated proxies based on RAML 1.0. In most cases, the proxy generation feature works well on API Manager for RAML 1.0-defined APIs. However, if a user tries to auto-generate proxies based on a RAML 1.0 file, and definition has known gaps, which are not covered by the Java parser on API Manager, the deployed proxy fails. ## [](#details-on-known-validation-discrepancies-among-products)Details on Known Validation Discrepancies among Products API Designer supports RAML 1.0 based on the JavaScript (JS) parser, while Studio RAML editor and APIkit use the Java parser instead. Due to incomplete support of the Java parser in RAML 1.0, users might see discrepancies among products. The following sections describe known discrepancies in validation behavior. ### [](#a-annotating-scalar-annotations)A. Annotating scalar annotations The [spec](https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md#annotating-scalar-valued-nodes) allows applying annotations to scalar nodes in addition to certain mapping nodes. If a user specifies the following: baseUri: value: http://www.example.com/api (redirectable): true - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID ### [](#b-uses-in-any-fragment)B. uses in any fragment The [spec](https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md#applying-libraries) allows using uses in any fragment. The Java parser allows its use only in root level RAML documents and libraries. #%RAML 1.0 ResourceType # This file is located at files-resource.raml uses: files: libraries/files.raml get: is: files.drm - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID ### [](#c-null-type)C. Null type RAML 1.0 introduced the null type. If a user specifies the following: annotationTypes: deprecated: null testHarness: null | string badge: string? # equivalent to ‘null | string’ - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID ### [](#d-examples-example)D. Examples / Example RAML 1.0 loosened the syntax requirements for examples / example and replaced “content” with “value”. If a user specifies the following: types: Org: type: object properties: name: string address?: string examples: acme: name: Acme softwareCorp: value: name: Software Corp address: 35 Central Street ----- example: height: 12 width: 4 ----- example: (pii): true strict: false value: height: 12 width: 4 - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer, API Console): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID ### [](#e-additional-properties-pattern-properties)E. Additional properties (pattern properties) This is a change from RC1 to RC2 that changed the syntax from `[]` to `//` since because it introduced conflicts with YAML. If a user specifies the following: types: Person: properties: a: string \[a\]: number - In current RAML spec: INVALID - In JavaScript parser (i.e. API Designer, API Console): INVALID - In Java parser (i.e. RAML editor in Studio, APIkit): VALID If a user specifies the following: types: Person: properties: a: string //: number - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer, API Console): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID ### [](#f-question-mark)F. Question Mark If a user specifies the following: types: profile: properties: preference?: required: true - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer, API Console): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID ### [](#g-inheritance-of-primitive-values)G. Inheritance of primitive values If a user specifies the following: types: Number1: type: number minimum: 4 Number2: type: number maximum: 10 Number3: \[ Number1, Number2\] - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer, API Console): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID ### [](#h-discriminator)H. Discriminator If a user specifies the following: application/json: type: Phone | Notebook discriminator: kind - In current RAML spec: INVALID - In JavaScript parser (i.e. API Designer, API Console): INVALID - In Java parser (i.e. RAML editor in Studio, APIkit): VALID ### [](#i-type-within-types)I. Type within Types If a user specifies the following: types: Next: type: properties: another: string properties: name: string - In current RAML spec: VALID - In JavaScript parser (i.e. API Designer, API Console): VALID - In Java parser (i.e. RAML editor in Studio, APIkit): INVALID # Edge and LTS Releases for Mule Starting with Mule 4.5, MuleSoft introduces two new release channels, Edge and Long-Term Support (LTS). Both release channels are available in all our deployment models: Anypoint Runtime Fabric, CloudHub, CloudHub 2.0, and Hybrid Standalone. Release cadence refers to new Mule runtime versions. Patch updates for supported versions continue to follow the monthly patch update schedule. Consider these factors to determine the approach that best suits your requirements ahead of the Mule 4.4 End of Standard Support.
Channel Type Release Cadence Differentiators Support Coverage

Edge

Up to three times per year

  • Includes new features on a frequent release cadence with shorter maintenance coverage.

  • Versions aren’t FedRAMP approved.

For versions 4.9 and later:

  • Standard Support until one month after the next Edge version is released

  • 3 months of Extended Support

For version 4.8:

  • 5 months of Standard Support

  • 3 months of Extended Support

For versions 4.5 to 4.7:

  • 4 months of Standard Support

  • 4 months of Extended Support

LTS

Periodic (Scheduled for February)

  • Includes new features introduced in prior Edge releases, along with new features introduced in the February Edge release. This release is maintained for an extended period over being the first to adopt new capabilities.

For version 4.6 and later:

  • A minimum of 18 months of Standard Support

  • A minimum of 6 months of Extended Support
If an LTS version is released in February, both Edge and LTS share the same underlying version, including the same minor Mule runtime version and new features. To review the new support policy that aligns with the new release periods and types of releases, see [MuleSoft Support Policy](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf).
For information about the monthly patch update process, see Update Patches to Mule.
## [](#edge_channel)Edge Channel Starting with Mule 4.5, MuleSoft releases Edge versions up to three times a year. Use the Edge channel if you want to stay on top of the latest features and feel comfortable with a more frequent release cycle and auto-app upgrade cycle. The Edge channel includes the latest features and innovations available on the MuleSoft platform. ## [](#lts_channel)LTS Channel Starting with Mule 4.6, MuleSoft releases Long-Term Support (LTS) versions periodically, scheduled for February. If you’re on Mule 4.4, you aren’t required to upgrade to Mule 4.6. However, because Mule 4.5 was released in October 2023, Standard Support for Mule 4.4 ends in October 2024, followed by the end of Extended Support in October 2025. For CloudHub and CloudHub 2.0 customers, once Standard Support for Mule 4.4 ends, if you want to deploy new apps, you must do so on Mule 4.6 LTS or Mule 4.8 Edge. Use the LTS channel if you want to avoid maintaining new versions frequently. The LTS channel adopts new capabilities after they have been introduced via Edge releases. ## [](#switch-from-an-edge-version-to-an-lts-version)Switch from an Edge Version to an LTS Version You can switch from an Edge version to an LTS version and vice versa. However, when moving from Edge to LTS, you must choose a later LTS version. For example, if you choose Mule 4.6 LTS and you want to implement a specific new feature released on Mule 4.7 Edge, you can opt into that Edge release, then merge into Mule 4.9 LTS once it is available. MuleSoft does not support apps that are switched from Edge to an older LTS version. For example, switching an app from Mule 4.7 Edge to Mule 4.6 LTS might result in losing some of the new features in the older LTS version. ## [](#mule-runtime-release-cadence-support)Mule Runtime Release Cadence Support This table shows the Mule runtime release cadence support for each channel:
Mule Version Release Date Java Version End of Standard Support End of Extended Support

4.13 Edge

October 2026

17

March 2027

June 2027

4.12 Edge

June 2026

17

November 2026

February 2027

4.11 Edge

February 2026

17

July 2026

October 2026

4.10 Edge

October 2025

17

March 2026

June 2026

4.9 LTS

February 2025

17

August 2027

February 2028

4.9 Edge

February 2025

17

November 2025

February 2026

4.8 Edge

October 2024

8, 11, and 17

March 2025

June 2025

4.7 Edge

June 2024

8, 11, and 17

October 2024

February 2025

4.6 LTS

February 2024

8, 11, and 17

August 2026

February 2027

4.6 Edge

February 2024

8, 11, and 17

June 2024

October 2024

4.5 Edge

October 2023

8 and 11

February 2024

June 2024
MuleSoft provides an extended support window for version 4.6 LTS due to its compatibility with Java 8, 11, and 17.
## [](#deployment-models-and-application-lifecycle-management)Deployment Models and Application Lifecycle Management Application lifecycle management depends on the deployment model.
Action CloudHub and CloudHub 2.0 Runtime Fabric Hybrid Standalone

Deploy net new apps

Deploy to the latest minor-patch version available under Standard Support of each channel.

Deploy to any patch version of Mule runtime available under Standard or Extended Support. By default, the latest version of Mule runtime is selected.

Deploy while versions are in support period.

Auto-upgrade

MuleSoft applies two distinct types of automatic updates:

  • Auto-patching (within the same minor version): Every month, apps in both the Edge and LTS channels are automatically updated to the latest available patch of their current minor version, as long as the app’s TLS version is compatible with the new patch. For example, an app can be updated from Mule 4.9.19 to 4.9.20. Monthly auto-patching doesn’t change the minor version. Patches are backward compatible and include bug fixes and security updates. Security updates can also be applied outside the regular schedule to address critical vulnerabilities. See the patching schedule for CloudHub and CloudHub 2.0.

  • Auto-upgrade (to a new minor version): When a minor version reaches End of Standard Support, apps are handled differently depending on the release channel:

    • Edge: Apps are automatically upgraded to the latest minor version in the Edge channel. The auto-upgrade occurs six weeks after the version reaches End of Standard Support, during that month’s patching schedule. Before the auto-upgrade, you have a self-upgrade window to move to the new minor version yourself.

    • LTS: Apps aren’t automatically upgraded to a new minor version when the version reaches End of Standard Support. To move to a later LTS minor version, upgrade your application manually. Apps that remain on a version through End of Extended Support are subject to the forced-upgrade behavior described in End of Extended Support.

Runtime version compatibility: Apps running Mule runtime 4.9 or earlier aren’t auto-upgraded to Mule runtime 4.10 or later. Mule 4.10 removes support for TLS 1.0 and 1.1, which can cause compatibility issues and break existing applications if upgraded automatically. Apps running earlier versions, such as Mule 4.6, can be auto-upgraded only as far as the Mule 4.9 release line and are moved to the latest available Mule 4.9 patch. To use Mule runtime 4.10 or later, upgrade your application manually.

Applications aren’t auto-upgraded by MuleSoft without customer-initiated actions.

No auto-upgrade capabilities

Self-upgrade

For apps in the Edge channel, you can manually upgrade during the fixed window after the runtime version reaches End of Standard Support. See patching schedule for CloudHub and CloudHub 2.0.

  • Edge: Six weeks

  • LTS: Manual upgrade only (no automatic minor upgrade schedule)

Always available

Using the Mule Upgrade Tool

Rollback

Available to the previously used version

Available to the previously used version

Available to the previous used version using the Mule Upgrade Tool.

Restart apps

Always

Always

Always while the version is within the support period

Keep running applications

Until End of Extended Support

Always

Always

End of Extended Support

Shutdown running apps.
Starting with Mule 4.7, CloudHub and CloudHub 2.0 applications in the Edge or LTS channels that are still running End of Life versions will undergo a forced upgrade to the latest version during the monthly upgrade window (See upgrade window for CloudHub and CloudHub 2.0).

Cannot deploy new apps

Can deploy new apps

Retirement

Mule apps don’t reach End of Life because they’re always auto-upgraded.

When Mule apps reach End of Life, you can still restart or redeploy them using the same runtime version the apps are currently running on.

When Mule apps reach End of Life, MuleSoft reserves the right to close the connection of the Mule runtime server to Anypoint Platform.

Supportability

All Mule apps are under Standard Support.

Supported while Mule apps are within the assigned support period.

Supported while Mule apps are within the assigned support period.

Redeployment / Applying changes / Upgrades

Supported until End of Extended Support.

Supported when a build tag is provided. If a build tag isn’t provided, the application defaults to the latest patch of the minor version being used. If a wrong, invalid, or unsupported build tag is provided, the deployment fails.

Supported under Hybrid Stansalone.
## [](#mule-runtime-version-naming-changes)Mule Runtime Version Naming Changes The version naming convention depends on the deployment model you’re using. A version increments: - MAJOR when a release includes features that introduce breaking changes and backward incompatibility. - MINOR when a release includes all new features keeping backward compatibility with previous minors. - PATCH when a release includes bug fixes and security updates that include upgrades to libraries with reported vulnerabilities. We build a new runtime and do a full validation test. - BUILD when a release includes changes related to Image/AMI, including OS changes, OS security updates, and changes in products outside the runtime. It doesn’t include any runtime changes. ### [](#cloudhub-cloudhub-2-0-and-runtime-fabric)Cloudhub, Cloudhub 2.0, and Runtime Fabric The Mule runtime versioning schema for the new release channels is: _Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\] : Build\[numeric\] Channel\[e for edge, nothing for LTS\]_ Each February, MuleSoft releases both an Edge and an LTS release with the same _Major.Minor_ version. To distinguish the versions, they’re represented as: - Edge: 4.6.0:1e - LTS: 4.6.0:1 Unlike the Hybrid Standalone customer profile, CloudHub, CloudHub 2.0, and Runtime Fabric require regular OS updates, hence the addition of the build enumeration in the full runtime version schema. Here are examples of the version numbers: - Edge: 4.5.0:1e - Edge: 4.6.0:1e - LTS: 4.6.0:1 ### [](#hybrid-standalone)Hybrid Standalone The Mule runtime versioning changes from date-based, for example, `4.4.0-20230317` to semVer as: _Major.Minor.Patch_ Here are examples of the version numbers: - 4.5.1 - 4.5.2 - 4.5.3 Mule runtime does not introduce a semVer increment if there is a month with no fixes. Here is an example of the versioning schema using different patch and builds:
Hybrid Standalone CloudHub - AMI / CloudHub 2.0 / Runtime Fabric - Docker image

Case

Release Date

Description

Patch/Build

Mule Runtime

Runtime Manager/Maven/API Tag for New Deployment

1

Oct 3, 2023

First release of 4.5.0

0th patch and 1st build

4.5.0

4.5.0:1e

2

Nov 7, 2023

Second release of 4.5

1st patch and 1st build

4.5.1

4.5.1:1e

3

Nov 7, 2023

Another build on same day for CloudHub, CloudHub 2.0, and Runtime Fabric

1st patch and 2nd build

Not Available

4.5.1:2e

4

Nov 7, 2023

OS updates only for CloudHub, CloudHub 2.0, and Runtime Fabric

1st patch and 3rd build

Not Available

4.5.1:3e

5

Dec 5, 2023

Second patch version of 4.5

2nd patch and 1st build

4.5.2

4.5.2:1e

6

Jan 2, 2024

Hot fix for a Mule runtime regression

3rd patch & 1st build

4.5.3

4.5.3:1e

7

Feb 6, 2024

Release of new minor

0th patch and 1st build

4.6.0

4.6.0:1e (Edge) / 4.6.0:1 (LTS)
The Mule runtime versioning schema uses these conventions: - Patch number in schema - In the schema `4.5.X:2e`, the patch number is the X. - The patch number starts from `0`, introducing a new minor version. - The patch number increments when the release introduces new code changes, including hotfixes to regressions or other bug fixes. - Build number in schema - In the schema `4.5.1:Ye`, the build number is Y. - The build number starts from `1`, introducing the first AMI or Docker image build of the patch. - The build number increments whenever the release introduces a new build of the AMI or Docker image for the same Mule runtime version. This increment does not indicate code changes to Mule runtime. ## [](#see-also)See Also - [Deployment Options](https://docs.mulesoft.com/jp/runtime-manager/deployment-strategies) - [Known Issues](https://help.salesforce.com/s/issues) # EDIFACT EDI Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for EDIFACT EDI (EDIFACT EDI Connector) enables you to convert EDIFACT messages to and from DataWeave-compatible representations using lists and maps. Guide: [EDIFACT EDI Connector](https://docs.mulesoft.com/edifact-edi-connector/latest/) ## [](#3-0-0)3.0.0 **September 30, 2026** ### What’s New - EDIFACT EDI Connector now requires Mule 4.6.24 or later. - A new configuration, **Send UNA segment**, specifies whether to include a UNA segment in the generated EDIFACT interchange. This setting depends on the **Always send UNA** configuration. For more information, see [EDIFACT EDI Connector Reference](https://docs.mulesoft.com/edifact-edi-connector/latest/edifact-edi-connector-reference). ### Compatibility
Software Version

Mule

4.6.24 and later

OpenJDK

8, 11, and 17

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
## [](#2-10-2)2.10.2 **October 30, 2025** ### What’s New - The UCM segment now shows on the acknowledgement for all transactions when the new **Acknowledge every transaction** (`ackAllSets`) field is enabled, even if the EDIFACT message is sent successfully. For more information, see [EDIFACT EDI Connector 3.0 Reference](https://docs.mulesoft.com/edifact-edi-connector/latest/edifact-edi-connector-reference). ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
## [](#2-10-1)2.10.1 **August 29, 2025** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### Fixed Issues
Issue Resolution ID

The Initial interchange reference field in the Write operation now supports over 10 characters, which no longer causes the NumberFormatException error.

W-19438549
## [](#2-10-0)2.10.0 **September 25, 2024** ### What’s New - A **VERSION1** option is added to the **Syntax version** field for the Writer Configuration. For more information, see [EDIFACT EDI Connector Reference](https://docs.mulesoft.com/edifact-edi-connector/latest/edifact-edi-connector-reference). ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### Fixed Issues
Issue Resolution ID

The schemas from the D07B, D08A, D08B, D09A, D09A, D10A, D10B, and D14B releases now have the correct message structure.

W-16375246
## [](#2-9-1)2.9.1 **June 5, 2024** ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### Fixed Issues
Issue Resolution ID

The connector now returns the expected Section Identification (UNS01) field value.

W-15869275
## [](#2-9-0)2.9.0 **January 29, 2024** ### What’s New - This connector is now compatible with Java 17. - A new field named **Lock Mechanism** enables you to determine the mechanism used to manage locks for control number sequencing. For more information, see the [EDIFACT EDI Connector Reference](https://docs.mulesoft.com/edifact-edi-connector/latest/edifact-edi-connector-reference). ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
## [](#2-8-1)2.8.1 **November 08, 2023** ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### Fixed Issues
Issue Resolution ID

The connector no longer throws an ArrayIndexOutOfBoundsException error when the input has special characters.

W-14455323
## [](#2-8-0)2.8.0 **September 21, 2023** ### What’s New - The connector now supports functional groups (UNG-UNE segments). Use the following new fields to configure this option: - Group control number key - Initial group reference - Mule application sender/recipient ID - Mule application sender/recipient ID qualifier - Partner application sender/recipient ID - Partner application sender/recipient ID qualifier - Require unique groups - Unique group numbers - Use Functional Groups For more information, see the [EDIFACT EDI Connector Reference](https://docs.mulesoft.com/edifact-edi-connector/latest/edifact-edi-connector-reference). - The connector now supports EDIFACT version S93A. ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B, S93A

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### Fixed Issues
Issue Resolution ID

You can now use a space character as a repetition separator.

W-13643052

D93A messages now include the declaration of the PAYMENT TERMS (C110) composite element within the PAYMENT TERMS BASIS (PAT) segment.

W-13705051

The application flow no longer breaks when two messages have the same reference number (UNH.1) in the same interchange. EDIFACT Connector handles the error properly.

W-14038829
## [](#2-7-2)2.7.2 **June 8, 2023** ### What’s New - The org.scala-lang library is upgraded to version 2.12.15. - The org.yaml.snakeyaml library is upgraded to version 2.0 to address reported security vulnerabilities. ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### Fixed Issues
Issue Resolution ID

Flat file exceptions thrown by writer operations now specify the incorrect segment or element for invalid type values.

W-13498284
## [](#2-7-1)2.7.1 **October 25, 2022** ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### What’s New - The `org.yaml.snakeyaml` library is upgraded to version 1.32 to address reported security vulnerabilities. ### Fixed Issues
Issue ID

Flags signaling a fatal error, such as Enforce segment order value, now work for segment-level errors.

W-11719314

The error level and error type now match the intended error.

W-11748979

Error metadata now appears with the correct fields.

W-11749004
## [](#2-7-0)2.7.0 **August 8, 2022** ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D16A, D16B, D17A, D17B, D18A, D18B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### What’s New - The connector now supports EDIFACT versions D16, D17, and D18 in the provided schemas. ### Fixed Issues
Issue ID

Several dependency libraries are upgraded for the connector.

W-10735082

The scheduler no longer generates a thread leak in dynamic configuration situations.

W-10890675

EDIFACT error messages now include the message reference number (UNH01)

W-11036116

The UNB09 value is now empty when an acknowledgement request is set to FALSE and an interchange map is not present in the payload.

W-11286787

The Read operation now correctly processes composite elements that have repetitions.

W-11385891
## [](#2-6-0)2.6.0 **February 15, 2022** ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D96B, D97A, D98A, D98B, D99A, D99B

EANCOM

D01B.EAN003, D01B.EAN004, D01B.EAN005, D01B.EAN006, D01B.EAN007, D01B.EAN008, D01B.EAN01, D93A.EAN001, D93A.EAN002, D93A.EAN003, D93A.EAN004, D93A.EAN005, D93A.EAN007, D96A.EAN001, D96A.EAN002, D96A.EAN003, D96A.EAN004, D96A.EAN005, D96A.EAN006, D96A.EAN008
### What’s New - Added support for EANCOM in the provided schemas. - Added support for D96B in the provided schemas. - Added the **Use segment line ending in last line** field to specify if the segment line ending character needs to be added to the last segment in the generated EDIFACT payload of the **Write** and **Write batch** operations. - Added the **Use Version Association Code** field, which enables you to use UNH0205 (Version Association Code). ### Fixed Issues
Issue ID

The control characters CR, CRLF, or LF were not added at the end of the last segment in the generated payload. You can now use the new Use segment line ending in last line field to require that a segment line ending character be added.

CONN-9987

When messages failed the duplicate control number check, the error object did not explicitly specify the issue.

CONN-9411
## [](#2-5-2)2.5.2 **January 3, 2022** ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9588
## [](#2-5-1)2.5.1 **December 20, 2021** ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9588
## [](#2-5-0)2.5.0 **November 10, 2021** ### Compatibility
Software Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### What’s New - Added the **Enforce code set validations** field to optionally enforce codeset validations for the **Read**, **Write**, and **Write batch** operations. - Added support for code sets in the provided schemas. ### Fixed Issues
Issue ID

The control number was re-initialized after an application running in a customer-hosted Mule cluster restarted.

CONN-9017

The USE-DEFAULTS option of the Separators usage field in the global element did not work as expected for the Write and Write batch operations.

SE-23148

Mapping incoming EDIFACT messages to a target message type did not work correctly.

CONN-8848
## [](#2-4-0)2.4.0 **September 9, 2021** ### [](#compatibility-16)Compatibility
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#new-features)New Features - Added the new configuration property **Timezone offset**, which enables you to generate EDI payloads with date-times in the header segments in your chosen timezone. - Error details when EDIFACT messages fail in **Read** operations now contain additional information for easier troubleshooting. ### [](#fixed-issues-13)Fixed Issues - Acknowledgment request elements (UNB09) in the CONTRL acknowledgments were set to `1`. (CONN-8356) - Application reference elements (UNB07) in the CONTRL acknowledgments were incorrectly set to the application reference code of the incoming message that was being acknowledged. The element is now set to `CONTRL`. (CONN-8356) - Interchange date and time of preparation in CONTRL acknowledgments were incorrectly set to the date and time fields in the incoming EDIFACT message payloads. They are now set with the current date and time when the acknowledgment is generated. (CONN-8356) - When some messages in a batched inbound EDIFACT interchange fail in validation, individual errors were not reported in the top level Error object. They are now reported in the top level Error object. (CONN-8361) ## [](#2-3-0)2.3.0 **June 8, 2021** ### [](#compatibility-17)Compatibility
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#new-features-2)New Features - Added a new **Write batch** operation and a corresponding **Configuration** tab. The new operation receives an input containing multiple outbound EDIFACT messages for the same partner and merges them into a single UNB interchange. - Added a new configuration property, `Truncate values exceeding the length limits`, for **Read**, **Write**, and **Write batch** operations to optionally truncate data element values when ignoring length validations. ### [](#fixed-issues-14)Fixed Issues - Data element values are no longer truncated by default when enabling length validations in **Read** and **Write** operations (CONN-7723). ## [](#2-2-0)2.2.0 **January 20, 2021** ### [](#compatibility-18)Compatibility
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#new-features-3)New Features - Added configuration options for interchange and message control number keys in the EDIFACT Write operation, thus providing flexibility for managing control number sequencing. - Added the configuration option `writeEnforceLengthLimits` in the EDIFACT Write operation for turning off Length validations of data elements, if neeeded. - Control numbers generated in the EDIFACT Write operation are now passed as attributes in the Post request. ### [](#fixed-issues-15)Fixed Issues - Improved the handling of the Identity tab config values in the EDIFACT Write operation. - Improved how the `requestAck` (UNB09) and `testIndicator` (UNB11) setting handles the configuration for the EDIFACT Write operation (CONN-7293, CONN-7294). ## [](#2-1-4)2.1.4 **November 9, 2020** ### [](#compatibility-19)Compatibility
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#fixed-issues-16)Fixed Issues Removed the incorrect validation that resulted in conditional (usage= 'C') components being treated as mandatory (usage= 'M') components, which caused some `null` or `empty` values to throw exceptions. (SE-18151) ## [](#2-1-3)2.1.3 **September 17, 2020** ### [](#compatibility-20)Compatibility
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#fixed-issues-17)Fixed Issues Fixed the counter value issue for the UNH01 field. (SE-17563) ## [](#2-1-2)2.1.2 **July 22, 2020** ### [](#compatibility-21)Compatibility
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#fixed-issues-18)Fixed Issues - Fixed the infinite loop when missing a UNT segment. (SE-16630) ## [](#2-1-1)2.1.1 **June 1, 2020** ### [](#compatibility-22)Compatibility EDIFACT EDI Connector v2.1.1 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#new-features-4)New Features - Supports additional schema formats. (CONN-6047) (CONN-6048) ### [](#fixed-issues-19)Fixed Issues - Improved the handling of error lists (CONN-327) ### [](#libraries-version-update)Libraries Version Update
Library Previous Version Current Version

ScalaCompiler

2.12.7

2.12.10
## [](#2-1-0)2.1.0 **April 20, 2020** ### [](#compatibility-23)Compatibility EDIFACT EDI Connector v2.1.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D00A, D00B, D01A, D01B, D02A, D02B, D03A, D03B, D04A, D04B, D05A, D05B, D06A, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B, D11A, D11B, D12A, D12B, D13A, D13B, D14A, D14B, D15A, D15B, D93A, D95B, D96A, D97A, D98A, D98B, D99A, D99B
### [](#new-features-5)New Features - Added a parameter that uses values from supplied data as control segment identifiers UNB05, UNZ02 (SE-12547). - Supports additional schema formats. - Improved the error reporting of the reader and writer components (CONN-321). - The standard MIME type defined for EDIFACT data is now supported (CONN-4667) (13003). ## [](#2-0-1)2.0.1 **December 14, 2018** ### [](#compatibility-24)Compatibility EDIFACT EDI Connector v2.0.1 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D.93A, D.95B, D.96A, D.97A, D.98B, D.99A, D.99B, D.00A, D.01B, D.02A, D.03A
### [](#fixed-issues-20)Fixed Issues - Correct escape handling for release character (typically `?`) ## [](#2-0-0)2.0.0 **April 10, 2018** This release adapts EDIFACT for use with Mule 4 and Studio 7. ### [](#compatibility-25)Compatibility EDIFACT EDI Connector v2.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

EDIFACT

D.93A, D.95B, D.96A, D.97A, D.98B, D.99A, D.99B, D.00A, D.01B, D.02A, D.03A
### [](#known-issues)Known Issues Anypoint Studio may require more memory than allowed by the default settings to support EDIFACT schema definitions. See the EDIFACT EDI Connector Guide for details on changing the Studio memory settings. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Einstein AI Connector Release Notes Einstein AI Connector enables developers to connect their MuleSoft applications to Large Language Models (LLMs) via the Salesforce Einstein Trust Layer. Guide: [Einstein AI Connector User Guide](https://docs.mulesoft.com/einstein-ai-connector/latest/) ## [](#2-0-0)2.0.0 **September 24, 2026** ### What’s New - This connector is now compatible with Java 17 only. - Document parsing now uses Apache Tika 4.0.0, instead of Apache Tika 2.9.4. Text extraction for some document types can differ from Einstein AI Connector 1.2. - **File Type** and **Option Type** are now enumerations on [**Embedding Adhoc File Query**](https://docs.mulesoft.com/einstein-ai-connector/latest/einstein-ai-connector-reference#EmbeddingAdhocFileQuery), [**Embedding Generate From File**](https://docs.mulesoft.com/einstein-ai-connector/latest/einstein-ai-connector-reference#EmbeddingGenerateFromFile), and [**RAG Adhoc Load Document**](https://docs.mulesoft.com/einstein-ai-connector/latest/einstein-ai-connector-reference#RagAdhocLoadDocument). The values are unchanged: `PDF`, `TEXT`, and `CSV` for **File Type**, and `FULL` and `PARAGRAPH` for **Option Type**. For more information about how to upgrade, see [Upgrading and Migrating Einstein AI Connector to 2.x](https://docs.mulesoft.com/einstein-ai-connector/latest/einstein-ai-connector-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The tika-core and tika-parsers-standard-package libraries are upgraded to version 4.0.0.

  • The org.bouncycastle library is upgraded to version 1.86.

  • The log4j dependency is excluded.

  • The junrar library is upgraded to version 8.1.1.

  • The jackson library is upgraded to version 2.22.3.

  • The jsoup library is upgraded to version 1.23.2.

  • The commons-lang3 library is upgraded to version 3.20.0.

W-24255829
## [](#1-2-1)1.2.1 **August 21, 2025** ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Messages field in the Chat generate from messages operation now supports DataSense, which provides schema support.

W-18939404

Einstein AI Connector now correctly parses scientific and large decimal numbers for toxicity responses.

W-19027006

These libraries are upgraded to address reported security vulnerabilities:

  • The jacoco library is upgraded to version 0.8.13.

  • The org.apache.tika library is upgraded to version 2.9.4.

  • The munit.extensions.maven.plugin.version library is upgraded to version 1.5.0.

  • The munit.version library is upgraded to version 3.4.0.

  • The maven.surefire.version library is upgraded to version 3.5.3.

  • The commons-io library is upgraded to version 2.20.0.

  • The org.junit.jupiter library is upgraded to version 5.13.4.

  • The mockito-core library is upgraded to version 4.11.0.

W-19290719
## [](#1-2-0)1.2.0 **May 2, 2025** ### What’s New - Transport Layer Security (TLS) configuration support is added. - You can now configure an HTTP proxy for this connector. - The **Read Timeout** and **Read Timeout Unit** parameters are supported at both the configuration and operation levels. For more information, see [Einstein AI Connector Reference](https://docs.mulesoft.com/einstein-ai-connector/latest/einstein-ai-connector-reference). ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#1-1-1)1.1.1 **March 19, 2025** ### What’s New - Enhanced the connection validation step to verify that the appropriate Salesforce setup is complete. ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

New annotations fields coming from the Einstein Trust Layer in the response output of operations are now processed correctly.

N/A
## [](#1-1-0)1.1.0 **March 10, 2025** ### What’s New - Removed the **Chat Answer Prompt With Memory** operation to better align with Anypoint Platform best practices. ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#1-0-0)1.0.0 **February 20, 2025** ### What’s New - The open-source connector is now certified by MuleSoft and enhanced to adhere to development and security best practices. - You can now use Einstein AI Connector with Anypoint Code Builder and Java 17. - You can discover and import the connector from Anypoint Exchange directly into your IDE. For more information, see the [Einstein AI Connector User Guide](https://docs.mulesoft.com/einstein-ai-connector/latest/). ### Compatibility
Software Version

Mule

4.6.9 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [Einstein AI Connector User Guide](https://docs.mulesoft.com/einstein-ai-connector/latest/) - [Einstein AI Connector Reference](https://docs.mulesoft.com/einstein-ai-connector/latest/einstein-ai-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Email Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Email sends and retrieves email messages over the standard email protocols. Guide: [Email Connector User Guide](https://docs.mulesoft.com/email-connector/latest/) ## [](#1-8-0)1.8.0 **December 12, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Sending an email with a text or plain payload no longer fails with the java.io.IOException: mark/reset not supported error.

W-19105614

The On New Email - IMAP operation now correctly processes only un-read emails by default, rather than reading all existing emails from the starting point of the mailbox.

W-1638060

This release includes general security fixes.

w-20242890
## [](#1-7-7)1.7.7 **November 5, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.sun.mail:jakarta.mail library is upgraded to version 1.6.8.

  • The commons-io library is upgraded to version 2.20.0.

  • The commons-lang library is upgraded to version 3.19.0.

  • The org.jacoco:org.jacoco.core library is upgraded to version 0.8.14.

W-19898722
## [](#1-7-6)1.7.6 **May 15, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Send operation now retains the message body when a reconnection is necessary.

W-15401123
## [](#1-7-5)1.7.5 **March 21, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Send Email Connector operation successfully transforms javax.activation.DataHandler input when running on Java 17.

W-16844085

The org.apache.commons:commons-io library is upgraded to version 2.18.0.

W-16844085
## [](#1-7-4)1.7.4 **November 13, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.17.0.

W-17090425

The org.apache.commons:commons-io library is upgraded to version 2.17.0.

W-17090425
## [](#1-7-3)1.7.3 **January 9, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-7-2)1.7.2 **April 18, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Send Email Connector operation now respects the order in which attachments are made.

W-12682674
## [](#1-7-1)1.7.1 **November 29, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The On New Email source no longer stops processing emails in a pool with a BaseMailboxPollingSource message.

W-11770310
## [](#1-7-0)1.7.0 **July 11, 2022** ### What’s New - Email Connector now enables you to set the pagination offset and retrieve a certain record (or subset of records) within a particular page using the **Pagination offset** field both for **List - IMAP** and **List - POP3** operations. - Email Connector now provides the **Count messages - IMAP** and **Count messages - POP3** operations, which get the total amount of messages in a specified mailbox folder. ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8 and 11
## [](#1-6-0)1.6.0 **March 14, 2022** ### What’s New - Added new **Move to folder** operation for IMAP and IMAPS connection providers. ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
## [](#1-5-2)1.5.2 **January 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Added exception handling on the IMAP polling process.

EMAILC-70
## [](#1-5-1)1.5.1 **November 19, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Fixed IMAP poll process because it stopped when BaseMailboxPollingSource.getEmailContent method threw an exception.

EMAILC-69
## [](#1-5-0)1.5.0 **November 17, 2021** ### What’s New - Added a new system property called `parsing.text.attachment.as.body` that enables you to change the behavior for parsing attached text files when the file is the only content in the message. The possible values are: - `true` (default): Preserves the previous behavior and converts the text file attachment on the body message. - `false`: Adds the text file attachment to the attachment list in the payload. ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Incomplete attachment parsing over non-multipart messages, for example, some messages had no body and only contained an attachment file.

EMAILC-67

The number of emails retrieved didn’t match the configured value page size and limit.

EMAILC-68
## [](#1-4-2)1.4.2 **July 21, 2021** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#features)Features None ### [](#fixed-issues-11)Fixed Issues Fixed the treatment attachments to avoid missing attachments or their names (EMAILC-65) ## [](#1-4-1)1.4.1 **March 26, 2021** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#features-2)Features None ### [](#fixed-issues-12)Fixed Issues Email Connector now treats attachments for which it couldn’t recognize their type as mimeType=‘**/**’ instead of failing. (EMAILC-61) ## [](#1-4-0)1.4.0 **February 1, 2021** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#features-3)Features None ### [](#fixed-issues-13)Fixed Issues Email Connector now throws the correct exception for errors when accessing folders (EMAIL:ACCESING\_FOLDER). (EMAILC-55) ## [](#1-3-0)1.3.0 **October 19, 2020** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#features-4)Features The new **Enable Remote Search** parameter enables email search and filter for IMAP protocol configurations at the server-side when a matcher is used with the `On New Email - IMAP` component. Enabling the parameter decreases traffic by reducing the number of emails sent to the client-side for processing, which reduces the amount of time and resources required to process polled emails. ### [](#fixed-issues-14)Fixed Issues The IMAP protocol configurations are not applying filtering on the server-side, resulting in large amount of emails downloaded from the server. (EMAILC-54) ## [](#1-2-1)1.2.1 **February 19, 2020** ### [](#compatibility-18)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#fixed-issues-15)Fixed Issues - Fixed an issue when the connector retrieving an email overlapped attachments with the same name (MULE-17998) ## [](#1-2-0)1.2.0 **January 21, 2020** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#features-5)Features There is a new parameter called **Attachment Naming Strategy**, which enables you to set a strategy for naming attachments when their filename is not present or when the attachment is in a nested email. See the [Email Connector documentation](https://docs.mulesoft.com/email-connector/latest/email-trigger#naming-strategy-for-attachments) for further explanation and usage examples. ### [](#fixed-issues-16)Fixed Issues When email attachment names were any type other than MIME, the attachment names were not recognized and found. (MULE-17971) ## [](#1-1-9)1.1.9 **October 31, 2019** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#fixed-issues-17)Fixed Issues - Fixed broken CID URLs for inline images. (MULE-17678) ## [](#1-1-7)1.1.7 **August 14, 2019** ### [](#compatibility-21)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#fixed-issues-18)Fixed Issues - The issue where emails with multipart or alternative parts inside multipart or related parts failed to parse is fixed. (MULE-17318) ## [](#1-1-6)1.1.6 **June 28, 2019** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#fixed-issues-19)Fixed Issues - Updated Java mail to Jakarta 1.6.3, Java activation to Jakarta 1.2.1, and the parent version to 1.1.5 to be sure that the only transitive dependency is javax.activation 1.2.1. (MULE-17052) ## [](#1-1-5)1.1.5 **May 8, 2019** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#fixed-issues-20)Fixed Issues - Email as attachment is not recognized by the Email connector. (MULE-16617) ## [](#1-1-4)1.1.4 **April 22, 2019** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### [](#fixed-issues-21)Fixed Issues - Fixed an issue that caused a 'NullPointerException' when polling a mailbox folder. (MULE-16746) ## [](#1-1-3)1.1.3 **February 8, 2019** ### [](#fixed-issues-22)Fixed Issues - Fixed a bug that prevented the usage of email attachments if dispatched by an IMAP source. (MULE-16388) - Email connector now requests a socket factory directly. (MULE-16190) ## [](#1-1-2)1.1.2 **November 1, 2018** ### [](#fixed-issues-23)Fixed Issues - Email connector does not correctly communicate the structure of returned objects. (MULE-15921) ## [](#1-1-1)1.1.1 **October 22, 2018** ### [](#fixed-issues-24)Fixed Issues - NoClassDefFoundError of Guava Class. (MULE-15883) ## [](#1-1-0)1.1.0 **October 10, 2018** ### [](#features-6)Features Added the capability to poll emails from a mailbox for all the unread emails in it, generating a new message for each email that is found. Added Value Provider support for email folders, to display the possible folder values for the configured service. ### [](#fixed-issues-25)Fixed Issues - Email doesn’t handle correctly multipart/alternative parts. (MULE-14157) - Email Connector exports internal classes. (MULE-14454) - Email connector does not work with the Gmail SSL port. (MULE-14673) - Email connector "replyToAddresses" is not populated when sending an Email. (MULE-14965) - Remove unnecessary String.toLowerCase calls (email). (MULE-15252) - Upgrade javax.mail to javax.mail-api 1.6.2. (MULE-15331) **May 2018** ## [](#1-0-2)1.0.2 **May 8, 2018** ### [](#fixed-issues-26)Fixed Issues - Email connector "replyToAddresses" is not populated when sending an Email. (MULE-14965) - Email connector does not work with Gmail SSL port. (MULE-14673) - IMAP List operation not retrieving attachments. (MULE-14762) ## [](#1-0-1)1.0.1 **March 15, 2018** ### [](#fixed-issues-27)Fixed Issues - Email connector doesn’t work with IMAP Gmail OOTB. (MULE-14606) - Email Connector doesn’t communicate correctly if their output types fields can be null. (MULE-14701) ## [](#1-0-0)1.0.0 **January 19, 2018** ### [](#features-7)Features This release includes the following enhancements, changes, and fixes: - Seamless UX between email protocols. - Retrieving emails from POP3 and IMAP mailboxes. - Retrieving, deleting, and storing emails from IMAP mailboxes. - Sending emails over the SMTP protocol. - Supporting secure connections for all protocols over Transport Layer Security (TLS). ### [](#upgrade-requirements)Upgrade Requirements Mule 4.1 ### [](#fixed-issues-28)Fixed Issues - Email connector pop3 does not delete all emails with deleteAfterRetrieve. (MULE-13101) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Enhanced MuleSoft Experience Release Notes The enhanced MuleSoft experience is a unified workspace for managing, governing, and monitoring AI-connected integration assets, including agents, APIs, Model Context Protocol (MCP) servers, model proxies, and gateways. Teams use it to register services, apply governance strategies, monitor runtime health, and optimize costs from one portfolio view instead of working across disconnected tools. ## [](#october-22-2026)October 22, 2026 ### [](#whats-new)What’s New #### [](#features)Features - You can now monitor traffic through Omni Gateway by applying the Akamai API Security (Omni Gateway) policy to your API instances. This traffic includes: - Internal traffic between services (east-west traffic). - External traffic to endpoints you can’t register at the Akamai edge, such as MuleSoft-managed CloudHub endpoints. For more information, see [Monitor Traffic Through Omni Gateway](#general::exp-akamai-risk-correlation.adoc#monitor-traffic-through-omni-gateway). - When you apply an Amazon API Gateway policy from agentic tools through the Platform MCP server, you can now scope it to a path, an HTTP method, or an operation, which combines a path and a method. The agent shows the scopes that the policy supports and asks which scope and target you want. The policy details it returns now include the scope each policy applies to. #### [](#enhancements)Enhancements - The **Review** step of the governance strategy **Create Policy** wizard now tells you when a policy supports more granular scopes, which you can select in the instance-level policy experience. - MuleSoft Agent now returns catalog and governance assets from child business groups for users in the root business group. - MuleSoft Agent in Slack and Microsoft Teams now takes fewer steps to answer, so responses arrive faster. In Microsoft Teams, answers now appear as they’re generated instead of all at once. - MuleSoft Agent in Slack and Microsoft Teams now supports GraphQL and the additional tools available in the embedded MuleSoft Agent. - Third-party libraries are upgraded to address reported security vulnerabilities. ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

Agent detail pages no longer show Unknown in the Updated field.

W-23016618

The advanced options for policies that you apply to agents and MCP servers no longer include the option to apply the policy conditionally by HTTP method.

W-23267358

MuleSoft Agent now returns catalog and governance assets from child business groups for users in the root business group.

W-23926623

The See Benchmark view on the Optimizations tab now shows an indicator for additional models.

W-23953679

Users who don’t have access to Cost Management now see a permission message instead of a "No LLM proxies found for the selected filters" message.

W-23983310

Optimization cards now show the See Benchmark link and the Why this policy section, and show potential savings in dollars per month instead of tokens.

W-23998776

Searching model proxies on the Optimizations tab now matches instance IDs in addition to names.

W-24010016

The submit button on policy forms in the Platform MCP server now reads Apply policy instead of Request policy creation.

W-24027218

MuleSoft Agent in Slack and Microsoft Teams now tells you when it can’t find data instead of showing an empty card.

W-24105572

A2A policies now appear in the policy catalog for A2A v1.0 agent instances, so you can apply policies such as A2A Token Based Rate Limit.

W-24119017

The MuleSoft Agent welcome message in Microsoft Teams no longer appears twice when you add the agent to a channel or direct message.

W-24135116

The error message that appears when a user who isn’t an Anypoint Platform administrator grants access permissions is now clearer.

W-24159946

Assets discovered by scanners no longer appear as managed instances with options to apply policies or as deployed to the Production environment.

W-24276575

The Security tab now shows data from all environments instead of only the default environment.

W-24366135

Third-party libraries are updated to resolve reported security vulnerabilities.

W-24505378
## [](#october-14-2026)October 14, 2026 ### [](#whats-new-2)What’s New #### [](#features-2)Features - You can now create a ServiceNow AI agent scanner to discover agents from ServiceNow. - You can now create a Kong Gateway scanner to discover MCP servers from Kong Gateway. - You can now use OAuth 2.0 Authorization Code for Google Vertex AI scanners to create, authorize, and test the provider connection before you continue scanner setup. For more information, see [Scanner OAuth Authorization](#general::exp-scanners-add-from-providers.adoc#scanner-oauth-authorization). - You can now apply open policies at the path, operation, or HTTP method level for providers that require a finer scope than the API instance, such as Amazon API Gateway. When an open policy maps to more than one native policy, the **Review** step tells you, and the policy list shows the path or operation that each policy applies to. - The Platform MCP server now includes tools to apply open policies and to apply and edit native policies from agentic tools, such as Claude and Cursor. A new skill guides agents through applying an open policy. - You can now register remote MCP servers that require browser-based OAuth 2.1 Authorization Code with PKCE authentication. - You can now publish a custom LLM provider to Anypoint Exchange as an `llm-metadata.json` classifier asset and select it as the provider for a model proxy route. For more information, see [general::model-proxy-publish-custom-llm-metadata.adoc](#general::model-proxy-publish-custom-llm-metadata.adoc). #### [](#enhancements-2)Enhancements - Policy configuration forms now support conditional fields and mutually exclusive configuration options, such as the signing key length in JWT Validation and the JWKS source in Apigee Verify JWT. - The **Configure Policy** step of the governance strategy **Create Policy** wizard now shows the providers that support the selected open policy. - Policy validation errors now appear in Spanish when the UI language is Spanish. - Dropdowns now support type-ahead search, so you can quickly find items in long lists, such as AWS regions. - The **Session Token** field is now available for Amazon Bedrock routes in dynamic mode, so callers that use short-lived AWS credentials can route requests through a model proxy. - MuleSoft Agent in Microsoft Teams now shows the same loading, authentication, and error messages as in Slack, and suggests follow-up actions after each answer. - MuleSoft Agent now responds faster in Slack and Microsoft Teams. - The MuleSoft bot is now added to a Microsoft Teams channel automatically when you select the channel, and the bot name now includes the region, such as **MuleSoft (EU)**. - Instance detail, gateway, and policy template pages load faster. #### [](#changes)Changes - Universal policies are renamed to open policies, and the **Omni & MuleSoft** badge for advanced policies is renamed to **Omni & Mule Gateway**. - The **Policies** tab and activity log no longer appear for MCP server and agent instances that are managed by third-party gateways, such as Azure API Management or Amazon API Gateway, because applying policies isn’t supported for these providers. Previously, the tab showed an **Apply Policy** button that returned an error. - Azure OpenAI no longer appears as a provider option when you create a semantic service, because it isn’t supported. - The welcome dialog now reflects the Agent Fabric brand. ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

Public MuleSoft catalog assets no longer show a Not Validated conformance badge.

W-22108561

The create_omni_gateway MCP tool now marks runtimeVersion as required, so requests no longer fail with a 400 error.

W-22624722

The Gateways page no longer lists a self-managed gateway that doesn’t exist in Anypoint Platform.

W-22732162

The view_api_instance_policies MCP app now shows the name of the API instance whose policies it displays.

W-22831480

Filters on portfolio pages now narrow results consistently.

W-22848133

Governance strategies created with the prepare_automated_policy_creation MCP tool now appear in your organization’s governance strategies list.

W-22854736

Agent detail pages no longer show an unknown environment.

W-23017333

The list_governance_strategies MCP tool now labels controls as controls instead of guardrails.

W-23059789

MuleSoft Agent in Slack and Microsoft Teams now sends each response as one message instead of several messages.

W-23553477

Creating a Trusted MCP server through MuleSoft Agent in Slack no longer fails at gateway selection.

W-23640564

Installing the Slack app now succeeds for organizations that have an orphaned Slack connection.

W-23756773

Custom asset icons now appear in the portfolio catalog, not only on the asset detail page.

W-23815011

Adding or removing a model proxy route no longer resets the client identifier configuration in the LLM Proxy Core policy, so token tracking continues to work.

W-23824232, W-24138884

The Amount Saved card on the agent dashboard now includes only request compression savings.

W-23943885

The Saved column on the MCP Servers tab of the Optimizations page now shows a trend indicator.

W-23954561

The applied policy count for Payload Optimization now updates after you apply a subpolicy.

W-23955262

The MCP Servers tab on the Optimizations page now paginates results when there are more than 10 MCP servers.

W-23955499

API instance names on Cost Management opportunity cards now appear as links.

W-23974322

Bulk update failure messages for alerts are now shorter.

W-23980698

Selecting the MuleSoft logo in the navigation sidebar now opens the home page.

W-23997715

MCP clients no longer need the full OAuth scope to connect to the MCP server.

W-24006913

You can now use the keyboard to navigate table rows.

W-24015335

A provisioning failure banner no longer appears for a Trusted MCP server that provisioned successfully after a retry.

W-24046223

Editing a disabled open policy on a MuleSoft API instance now shows the saved configuration instead of empty fields.

W-24079553

The consumer endpoint of a model proxy is now always editable, and the port is editable on self-managed gateways and limited to 8081 or 8082 on managed gateways.

W-24087973

The model proxy configuration summary now shows the environment name instead of the environment type, and shows the input format.

W-24104747

Users who aren’t organization administrators can now select a model when configuring a model proxy fallback route.

W-24117065

Saving a model wallet that contains an Amazon Bedrock budget no longer fails with a "model isn’t recognized" error.

W-24119805

The cost and tokens toggle on the Optimizations tab now works without first using it on the Budgets tab.

W-24149250

MCP Bridge now recognizes roles that are assigned through teams when checking permissions.

W-24156034

The Performance page now loads available data when an optional query fails, instead of failing to load entirely.

W-24178872

Users who have the documented API Manager permissions can now create a model proxy without the Organization Administrator role.

W-24194029

Policy configuration fields that accept multiple values no longer split values that contain commas, such as Cedar rules in Attribute-Based Access Control.

W-24198588

Creating an automated policy for A2A v1 agents no longer fails with an "Invalid endpoint types" error.

W-24198627

MuleSoft Agent responses in Microsoft Teams no longer refer to Slack.

W-24215212

Model names now appear when users who have the documented permissions create model wallet budgets or configure model-based routing.

W-24247083

Model detail pages now list model wallets from all environments instead of only the default environment.

W-24254296

Numeric policy fields with fractional steps now show rounded values, such as 0.84, instead of values such as 0.8099999999999999.

W-24255976

Selecting View Optimization in the opportunities carousel now updates the page URL.

W-24269008

Logging in after a session times out no longer fails with an "Invalid OAuth state" error.

W-24276489

You can now edit AWS Signature Injection policies without field errors.

W-24276857

Selecting a model wallet on the Budgets tab now opens the wallet in its own environment.

W-24280601

The Request model override field is now optional for model-based and semantic routing.

W-24313182

An IP address validation error no longer remains after you replace an invalid IP address with a valid one in policy configuration.

W-24359644

Editing a policy on a model proxy route now opens the configuration for that route when more than one route has the same policy.

W-24360920

Model proxies that use the Gemini format now handle streaming responses correctly.

W-24363980

Model proxy descriptions are now limited to 256 characters to match Exchange, so creating a model proxy with a longer description no longer fails.

W-24377785

New model proxy routes no longer show NVIDIA as the provider when you haven’t selected one.

W-24387103

Model proxies with OpenAI and Mistral routes now save without a duplicated routing headers error.

W-24387105

Semantic routing is no longer available for model proxies that use the Anthropic or Gemini input format, because it isn’t supported for these formats.

W-24392230

Creating a model proxy with an Amazon Bedrock OpenAI route no longer fails with a 400 error.

W-24424271

Selecting a self-managed Omni Gateway when editing a model proxy no longer shows an endpoint retrieval error that blocks saving.

W-24440299
## [](#september-28-2026)September 28, 2026 ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

MuleSoft Agent responses are no longer truncated mid-sentence.

W-22511562

Third-party libraries are updated to resolve reported security vulnerabilities.

W-23323287

The Updated field on service and instance detail pages now uses the canonical Platform API timestamps instead of deployment or audit fallbacks.

W-23817531

The enhanced experience now loads after you select Go to enhanced experience.

W-23909031

The MuleSoft Agent now returns a response instead of failing to reply.

W-23926482

The agent chat no longer renders a blank turn when the LLM gateway returns a 5xx error mid-answer.

W-23942921

The MuleSoft Agent now calls the correct backend tool.

W-23973420

The Optimizations column now shows the correct number of applied optimizations.

W-24010562

Applying a policy through the Platform MCP server now succeeds instead of failing with a "policy apply failed (unknown)" error.

W-24027214

Payload compression savings now appear in Cost Management even when JWT client ID validation is skipped, so the Amount Saved and ROI dashboards no longer report zero savings.

W-24028032

The Playground now applies manually configured authentication, including API Key, Bearer, Basic, and OAuth 2.0, to outgoing requests when the API spec doesn’t declare a security scheme.

W-24061141

The Agents modal chart now loads data instead of appearing empty.

W-24091631

The Token Usage & Response Time chart now shows estimated usage without optimization separately from tokens used, so savings are visible.

W-24100260

Cost Management entitlement gating is now consistent with the Model Proxy backend fallback, so entitled customers are no longer blocked.

W-24128912

The Total Managed Spend, Total Spend on Agents, and Potential Savings values on the Optimization page now roll up correctly into the millions.

W-24149371

Policy descriptions for the Tool Mapping, MCP Tools Progressive Disclosure, and Request Compression policies no longer contain typos and grammar errors.

W-24160887

The Cost Management tab on an agent’s detail page now shows the correct optimization policy count and format.

W-24161316

The Policy Violation Count graph on the Performance tab now displays data.

W-24216820

Drill-downs on the Performance page now return data even when the environment filter isn’t selected.

W-24250463
## [](#september-7-2026)September 7, 2026 ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

Installing the Slack app now succeeds when a previous session wasn’t cleared, instead of failing.

W-23754100

Policy templates no longer return a proxy error.

W-23836725

The Cost Management tab no longer renders blank.

W-24007593

The policy-count column label is now consistent across the agent, model proxy, and MCP server dashboards.

W-24021273

Applying agent optimization policies from the Optimizations tab in Ask MuleSoft no longer fails silently.

W-24026346

Applying the MCP Tools Progressive Disclosure optimization policy in Ask MuleSoft no longer gets stuck in a loop.

W-24027064

Managing model wallets through the MuleSoft Agent no longer requires you to provide an environment ID.

W-24027144

Model wallets now appear in the model proxy route editor for organizations that have more than one environment.

W-24043182

The Tokens Saved column on the model proxy Optimizations tab now shows actual values instead of always showing 0.

W-24054184

Budget Management now includes an environment switcher, so you can view budgets across all your environments instead of only one.

W-24060216

The Organizations filter on the MCP server and agent catalogs now shows the correct count and pagination, applies the expected checkbox behavior, and no longer shows a stale empty state when you open it from a deep link.

W-24063692
## [](#august-31-2026)August 31, 2026 ### [](#whats-new-3)What’s New #### [](#features-3)Features - You can now connect the enhanced experience to AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault so API keys and other credentials stay in your secrets manager. MuleSoft stores only metadata, such as secret names and paths, not the secret values. It reads the secret from your vault when a model proxy or other service needs it. For more information, see [general::exp-vaults-manage.adoc](#general::exp-vaults-manage.adoc). - You can now contain a rogue AI agent before it leaks data, takes unauthorized actions, or runs up costs. Stop that agent’s requests from reaching your models, then restore access if the containment was a false positive. For more information, see [general::exp-detect-and-contain-rogue-agents.adoc](#general::exp-detect-and-contain-rogue-agents.adoc). - Cost Management now includes budget management. Set spending budgets for your model wallets, track spend against each budget, and manage budgets across providers and models from the **Budgets** tab. For more information, see [Budgets Tab](#general::exp-governance-view-cost-and-token-usage.adoc#budgets-tab). - The Cost Management **Optimizations** page now includes an **Agents** tab, so you can review token usage and optimization opportunities for your agents alongside model proxies and MCP servers. For more information, see [Filter and Search](#general::exp-governance-view-cost-and-token-usage.adoc#filter-and-search). - You can now create, edit, delete, and list model wallets, which allocate token budgets that are granted only when a request’s claims match the wallet’s required claims. Manage model wallets from the UI or through the MuleSoft Agent. For more information, see [general::exp-model-wallets-manage.adoc](#general::exp-model-wallets-manage.adoc). - You can now edit instances for model proxies, APIs, agents, and MCP servers from the service detail page or the instance detail page, without switching to Anypoint Platform. - Model Proxy now supports semantic caching, TLS security for provider connections, external vault–based provider authentication, and the Model Proxy Request Compression policy. For more details about updates to model proxy, see [Model Proxy Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/model-proxy-release-notes). - MCP Bridge now exposes tool output schemas as part of the MCP specification, so you can connect servers built with MCP Bridge to Agentforce. - These SaaS connectors are now available in the Trusted MCP catalog: Wix, WordPress.com, Hootsuite, Descript, Intercom, Front, and LiveChat. - You can now create an A2A bridge to make a non-A2A agent A2A-compliant so that Agent Fabric can discover, govern, and orchestrate it alongside native A2A agents. For more information, see [general::exp-services-create-a2a-bridge.adoc](#general::exp-services-create-a2a-bridge.adoc) - You can now use OAuth 2.0 Authorization Code for Microsoft Copilot Studio scanners to create, authorize, and test the provider connection before you continue scanner setup. For more information, see [Microsoft Copilot Studio OAuth Authorization](#general::exp-scanners-add-from-providers.adoc#microsoft-copilot-studio-oauth-authorization). - You can now apply universal policies to your API instances and manage the resulting native policies. A universal policy is defined once and applied as the correct native policy on each supported gateway. For more information, see: - [general::exp-governance-policy-library-apply.adoc](#general::exp-governance-policy-library-apply.adoc) - [general::exp-instances-add.adoc](#general::exp-instances-add.adoc) - [general::exp-policies-apply-manage.adoc](#general::exp-policies-apply-manage.adoc) - API scanners now write policies from these provider platforms: Google Apigee, Azure API Management, and Kong Gateway. For these providers, policy results are visible from each discovered API in Portfolio > APIs > Policies. For more information, see: - [general::exp-overview.adoc](#general::exp-overview.adoc) - [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc) - [general::exp-scanners-add-from-providers.adoc](#general::exp-scanners-add-from-providers.adoc) - [general::exp-scanners-prerequisites-reference.adoc](#general::exp-scanners-prerequisites-reference.adoc) - [general::exp-scanners-view-details.adoc](#general::exp-scanners-view-details.adoc) - [general::exp-scanners-manage.adoc](#general::exp-scanners-manage.adoc) - [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc) - You can now track remediation and scan status in the **Akamai Security Findings** table on the **Conformance** tab. For more information, see [Track Remediation and Scan Status](#general::exp-akamai-risk-correlation.adoc#track-remediation-and-scan-status). #### [](#enhancements-3)Enhancements - Cost Management optimization for MCP servers now includes policy recommendation cards with an **Apply** action, a sortable potential-savings column, savings framed in dollars per month, applied policies grouped by category, and a benchmark of the top MCP servers across the top models. - The **Optimizations** and **Budgets** dashboards now include a toggle to switch between dollar and token views. - MCP Bridge overview pages now group tools by the source API they were generated from, with a link to each API’s Exchange page. - MCP Bridge tool editing now includes a resource filter and instance-type badges, and you can add a TLS context and customize HTTP request mappings on a deployed MCP server. - You can now configure inbound and outbound TLS contexts when you create or modify an MCP Bridge, and Model Proxy now supports TLS context configuration for upstream connections. - You can now edit a model proxy’s deployment configuration inline, including its base path, gateway target, and consumer endpoint, with a warning when a change requires redeployment. - The Portfolio **Filters** menu now includes an **Organizations** group, so you can narrow the catalog to specific business groups and hide public MuleSoft catalog assets. - MuleSoft for Teams is now available as a limited availability feature. Install the MuleSoft for Teams app to interact with MuleSoft directly from your Microsoft Teams tenant, receive platform alerts in channels, and use MuleSoft Agent to list APIs, view MCP servers, check governance, and perform other management tasks. To request access, contact your account executive. For more information, see [general::exp-teams-integrate.adoc](#general::exp-teams-integrate.adoc). - The MuleSoft app for Microsoft Teams is now available in additional regions. - The MuleSoft Agent in Slack and Microsoft Teams now uses a refreshed set of cards for listing and viewing services, instances, and policies, and for applying a policy. - You can now filter your alerts and bulk-assign a Microsoft Teams channel as the delivery destination, with a confirmation step that lists the affected alerts. - When you ask the MuleSoft Agent to do something it doesn’t have a tool for, it now explains what it can do and offers to report the limitation. - MuleSoft Agent semantic search is recalibrated to return more accurate and relevant results. - Portfolio, service detail, instance detail, and policy pages load faster. #### [](#changes-2)Changes - In a model proxy route, the **Model** field is renamed to **Request model override**, and **Not applicable** is renamed to **Use model from request**, to clarify that the field overrides the model specified in the incoming request. - The MuleSoft Agent panel is now hidden by default unless the MuleSoft Agent feature is enabled for your organization, and it’s hidden in trial accounts. Previously, the panel could appear for users who couldn’t access the feature. ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

The MuleSoft Agent now returns results when you search for assets by type, instead of returning none.

W-23149216

The MuleSoft Agent no longer returns a "No generations found in stream" error in the agent panel, Slack, and Teams.

W-23927589

Switching to a child business group now returns correct results for the MuleSoft Agent in Microsoft Teams.

W-23927098

Your business group selection is now preserved when you refresh the page or open the enhanced experience in a new tab.

W-23444044

Installing and uninstalling the MuleSoft Slack app now works correctly.

W-23632725

A clearer error message now appears when a user who isn’t an organization admin tries to connect Slack to Anypoint Platform.

W-23360453

MuleSoft Agent notifications now deliver to Microsoft Teams instead of failing with an SSL error.

W-23649227

Reinstalling the MuleSoft app in Microsoft Teams now recovers automatically from an installation conflict, matching Slack behavior.

W-23651771

You can now connect Microsoft Teams to a second organization that uses the same Microsoft Entra tenant.

W-23972001

Notifications now display the tenant ID instead of the MuleSoft organization ID.

W-23902550

Toast messages are no longer truncated in the notification list.

W-23902562

Testing the connection to an unreachable or invalid MCP server URL now returns a clear validation message instead of a server error.

W-23480369

MCP server detail pages now show connected APIs, because connection metadata is preserved on MCP server upstreams.

W-23748233

Creating a model proxy from a child business group no longer redirects you to the parent business group.

W-23930690

The topics and model fields are now populated when you edit an existing model proxy that uses semantic caching.

W-23792167

The Omni Gateway dropdown in the model proxy wizard now lists all gateway targets instead of only the first page.

W-23845232

Permissions are now consistent between the model proxy gateway and route-configuration APIs.

W-23845221

The Fallback model dropdown in the model proxy route editor no longer renders empty when a model wallet is enabled.

W-23996495

The provider badge for Amazon Bedrock AgentCore now displays correctly.

W-23995654

The Smart Response Trimming payload optimization policy now saves a complete model proxy URL.

W-23561570, W-23956373

Payload optimization opportunities now appear for instances whose average token usage doesn’t cross the display threshold.

W-23653988

Testing credentials for an OpenAI model proxy in the payload optimization policy now works.

W-23688845

The Discovered tile on the home page no longer over-counts forked MuleSoft public templates.

W-23630949

The agents catalog count no longer includes agent-network rows, so the count matches the assets shown.

W-23631818
## [](#august-28-2026)August 28, 2026 ### [](#whats-new-4)What’s New #### [](#features-4)Features - The Kong Gateway scanner now detects gRPC and GraphQL protocols and assigns the correct service type for these services. Services that use other protocols are registered as service type REST for now. MuleSoft plans to support more protocols in a future release. For more information, see [general::exp-scanners-add-from-providers.adoc#kong-gateway-scanner-protocol-to-asset-type-mapping](#general::exp-scanners-add-from-providers.adoc#kong-gateway-scanner-protocol-to-asset-type-mapping). ## [](#august-24-2026)August 24, 2026 ### Fixed Issues The release addresses this enhanced MuleSoft experience issue:
Issue Resolution ID

The Expose as MCP Server action now appears for APIs that have a deployable instance, even without a configured consumer endpoint.

W-23922779
## [](#august-6-2026)August 6, 2026 ### [](#whats-new-5)What’s New #### [](#features-5)Features - Playgrounds are now available for APIs and MCP servers. Use the **Playground** tab on a service detail page to explore endpoints and tools, configure and send requests, and inspect responses without leaving the enhanced experience. For more information, see [general::exp-playground-overview.adoc](#general::exp-playground-overview.adoc), [general::exp-playground-api.adoc](#general::exp-playground-api.adoc), and [general::exp-playground-mcp.adoc](#general::exp-playground-mcp.adoc). - The Akamai scanner is now available to map external security findings to the right services in **Portfolio**. Add the scanner to scan APIs, surface security findings, and apply governance strategies from the portfolio. The scanner doesn’t import or register third-party services. It correlates risk scores, findings, and incidents in one governance workflow. For more information, see [general::exp-akamai-risk-correlation.adoc](#general::exp-akamai-risk-correlation.adoc) and [general::exp-governance-work-with-strategies.adoc](#general::exp-governance-work-with-strategies.adoc). - Additional Trusted MCP server SaaS integrations are now available, and ready-to-use MCP client configuration snippets help you connect popular MCP clients faster. - Model Proxy now supports the Anthropic API format and native Anthropic models. See [Supported LLM Providers](#general::model-proxy.adoc#supported-llm-providers). - API scanners now read policies from these provider platforms: Amazon API Gateway, Google Apigee, Azure API Management, and Kong Gateway. For these providers, policy results are visible from each discovered API in **Portfolio** > **APIs** > **Policies**. After connecting to a third-party API gateway provider, you can govern discovered APIs through the same governance workflow used for Anypoint Platform APIs. This enables unified governance across multiple gateway platforms. For more information, see: - [general::exp-scanners-add-from-providers.adoc](#general::exp-scanners-add-from-providers.adoc) - [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc) - [Create Governance Strategies with Your IDE](#general::exp-governance-create-strategy.adoc#create-with-ide) - [general::exp-governance-govern-third-party-apis.adoc](#general::exp-governance-govern-third-party-apis.adoc) - [general::exp-governance-monitor-cross-gateway-conformance.adoc](#general::exp-governance-monitor-cross-gateway-conformance.adoc) #### [](#enhancements-4)Enhancements - The Scanner details page now includes an Activity Log with a real-time timeline of scan progress events. For more information, see [general::exp-scanners-view-details.adoc](#general::exp-scanners-view-details.adoc). - MCP Bridge now lets you edit tool input schemas, customize tool HTTP request mappings and headers, and expose tool output schemas as part of the MCP specification. - Cost Management now lets you edit optimization policies and is available from the Ask MuleSoft sidebar. - The LLM proxy credential test now distinguishes between credentials that can’t be verified and credentials that are invalid. - LLM Proxy is now renamed to Model Proxy. ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

The MCP server creation success screen now displays a persistent runtime authentication warning banner instead of stacked notifications.

W-22323999

Agent detail policy views no longer show a misleading "No instances covered" message for environment types that have no instances.

W-22416846

Portfolio catalog and entity pages now load faster and filter more reliably.

W-22580671

The Anypoint MCP Bridge now returns tool input schemas in valid JSON Schema format in tools/list responses.

W-22602876

Platform MCP server tools now match filter values to stored display labels, returning correct results.

W-22850282

The Apply Policy agent action now displays available policies immediately instead of showing none during an initial delay.

W-23011916

The agent no longer directs you to a nonexistent automated policy creation page.

W-23012045

The agent no longer gets stuck on the Environment field when prefilling a governance strategy form.

W-23091457

The Ping operation now works correctly in MCP Bridge.

W-23128311

Cost Management now displays metrics for Twilio MCP server instances.

W-23141551

API catalog filter options now include values from all assets instead of only the first page of results.

W-23330370

Long LLM responses are no longer dropped mid-stream.

W-23366770

The policy version selector on the policy configuration page now lists versions in order.

W-23385993

Cost Management now surfaces Payload Optimization opportunity cards even when the Payload Optimization policy is not yet applied.

W-23402200

Correlation policies now apply correctly to instances.

W-23470169

Cost Management policy names no longer display underscores.

W-23475812

The MuleSoft Agent prompt now works for users who are granted agent permission only in a child business group.

W-23478614

The MCP server creation wizard now shows an accurate message when the blocker is a missing Exchange permission.

W-23495332

Cost Management Payload Optimization Smart Response Trimming now works regardless of sub-policy order.

W-23515804

Notification labels now match Anypoint Platform.

W-23522019

The agent no longer rejects legitimate platform questions as off-topic.

W-23528364

The agent no longer loops when discovering assets that include nested environment fields.

W-23564370

Cost Management now uses the latest policy version for Trusted MCP servers.

W-23574980

Cost Management now surfaces Payload Optimization opportunities in instance modals even when projected savings are below the display threshold.

W-23632337
## [](#july-15-2026)July 15, 2026 ### [](#whats-new-6)What’s New #### [](#features-6)Features - The new Payload Optimization policy page lets you configure token-reduction strategies, including payload sanitization and TOON encoding, as toggleable sub-policies. - Cost Management now surfaces Payload Optimization sub-policies as opportunity cards, so you can act on top token-savings recommendations directly from the Cost Management page. - The new MCP Tools Progressive Disclosure policy enables you to reduce context window token cost by exposing tools on demand through search. Apply the policy Cost Management. - Instance detail pages now display the consumer endpoint URL, including the base path, so you can copy a callable URL without switching to Anypoint Platform. #### [](#enhancements-5)Enhancements - Tool Mapping policy configuration now includes a version selector, so you can update the policy to a new version. - Applied policies now display a "New version available" indicator when a newer version is available. - The model proxy overview now shows the configured fallback route and semantic prompt guard as summary cards, so you can review them without entering edit mode. ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

The MCP server Create & Deploy button now displays progress notifications instead of internal provisioning steps.

W-22477443

The monitoring summary page now loads successfully and no longer times out because of backend connectivity failures.

W-22561882

MCP server creation no longer pre-selects a gateway without a public URL, preventing validation errors during review.

W-22569213

MCP server detail pages now open correctly even before the asset is fully indexed, instead of redirecting to the MCP server list.

W-22668860

Name and path validation is improved during MCP server creation.

W-22730633

Policy views for externally managed gateway instances now return an empty policy set instead of a 404 error.

W-22850289

The Run discovery scan quick action in the agent panel now performs the same scan as the Run discovery scan button on scanner pages.

W-22855741

MCP tool input schemas now display complete information.

W-22903101

Long text entered in the agent panel input box now stays within its container.

W-23012031

The Support Credentials toggle in Cross-Origin Resource Sharing policy configuration is now enabled, matching earlier behavior.

W-23050595

Health Check policy configuration now routes you to the alert builder to create an alert after the policy is applied.

W-23050597

Injection Protection policy configuration now provides a multi-select dropdown for built-in protections instead of a free-form text field.

W-23050599

Policy configuration forms with nested fields no longer add an empty row that caused save errors.

W-23050623

Navigation from the agent panel to a specific agent’s detail page now works correctly.

W-23091579

Availability drill-downs now display the availability metric instead of the reliability metric.

W-23111937

Time-series chart drill-downs now display the time bucket you select instead of an adjacent one.

W-23111946

Agent portfolio search now returns agents that also appear in the main UI search.

W-23113003

Tool-mapping descriptions are no longer duplicated when a tool’s summary and description match.

W-23130198

Agent responses now display consistently in chat history.

W-23131703

Cost Management token-savings projections in the instance detail modal now update to match the selected timeframe instead of always using the 30-day period.

W-23140133

The trusted MCP wizard footer now adjusts correctly when the sidebar is collapsed.

W-23176162

Cost Management tool optimization now displays an error message when your organization lacks Agentforce access instead of failing silently.

W-23178835

Acronis test-connection operations now succeed by using the correct tenant filter.

W-23181533

Editing a policy no longer disables or unchecks unrelated fields whose names end in header or headers.

W-23186039

Model Based Routing policy configuration now displays the selected version after you change and save it.

W-23200921

Cost Management tooltips now render with a solid background for better readability.

W-23312200

Cost Management now displays estimated saved tokens correctly when optimization strategies are active.

W-23319697
## [](#july-2-2026)July 2, 2026 ### What’s New - Model proxies now supports multiple routes to the same LLM provider and can filter requests to different routes with headers. ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

Manual API registration now processes uploaded .zip files without errors.

W-22441824

Manual API registration now processes uploaded JSON and YAML files without server errors.

W-22441846

Portfolio page headers and toolbars now remain fixed at the top when scrolling.

W-22454943

Newly created API instances now appear immediately in the instance list.

W-22461347

Basic Authentication policy password fields now mask input correctly.

W-22476294

Slack Agent now processes Omni Gateway requests without errors.

W-22518488

Pre-selected paths in MCP Server creation no longer display validation errors during review.

W-22599092

Slack Agent responses now focus on available actions instead of describing unavailable creation workflows.

W-22642526

MCP transcoding operations now correctly handle body literals without affecting upstream policies.

W-22642906

Gateway detail page links now redirect to Anypoint Runtime Manager with the correct environment scope.

W-22708401

Outbound OAuth 2.0 Credential Injection policies now allow setting Client ID and Secret.

W-22815084

Policy listing views now clearly distinguish between inbound and outbound policies.

W-22923681

Model proxy asset creation now handles Exchange API responses without HTTP 502 errors.

W-22927281

MCP Server tool lists now return all available tools without truncating results at 512 items.

W-22928504

Portfolio page provider filters now display all configured providers instead of a static list.

W-22928563

Portfolio page filters now handle large result sets without returning empty results.

W-22928667

OAuth 2.0 test connection operations now work correctly when creating an MCP server.

W-22965458

API specification overviews for gRPC APIs now populate correctly in the India region.

W-22966440

A2A PII Detector policy configuration now supports multi-select for PII types.

W-23050572

MCP PII Detector policy configuration now supports multi-select for PII types.

W-23050575

LLM PII Detection policy configuration now supports multi-select for PII types.

W-23050578

Model Based Routing policy configuration now includes Match Headers and isFallback Entry fields.

W-23050585

Client ID Enforcement policy configuration now displays Client ID Expression and Client Secret Expression fields when Custom Expression is selected.

W-23050592

JWT Validation policy configuration now includes JWT Signing Key Length, conditional JWT Key fields, and Client ID Expression.

W-23050601

Credential Injection API Key policy configuration now displays auth-type-dependent fields for custom headers, API keys, and client credentials.

W-23050605

Credential Injection OAuth 2.0 policy configuration now displays grant-type-dependent fields for Client Credentials and Password grant types.

W-23050608

OAuth 2.0 OBO Credential Injection policy configuration now displays all grant-type-dependent fields.

W-23050613

Agent registration workflow now uses correct naming conventions.

W-23064092

MCP Server creation now displays clear, actionable error messages when credential validation fails.

W-23073090

Acronis credential test operations now work correctly with network allowlist configurations.

W-23085376

Public Agent detail pages no longer display delete icons.

W-23090929

POST tools created from MCP bridge connections now correctly include all input parameters.

W-23128385

The MuleSoft Agent now displays correctly for users who have been enabled in child business groups.

W-23182443
## [](#june-22-2026)June 22, 2026 ### [](#whats-new-8)What’s New #### [](#enhancements-6)Enhancements - Notifications are now available, allowing you to configure and receive alerts for service health and governance events. For more information, see [general::exp-alerts-configure-notifications.adoc](#general::exp-alerts-configure-notifications.adoc). - MuleSoft Agent is now available. Manage your MuleSoft environment with MuleSoft Agent, an agentic experience available in the control plane. Use MuleSoft Agent to create scanners, apply policies, deploy instances, and perform other management tasks. To request access, contact your account executive. For more information, see [general::exp-ai-assistant-use.adoc](#general::exp-ai-assistant-use.adoc). - MuleSoft for Slack is now available. Install the MuleSoft Slack app to interact with the MuleSoft Platform directly from your Slack workspace, send platform notifications to Slack channels or direct messages, take platform actions, and ask questions about your MuleSoft organization. For more information, see [general::exp-slack-integrate.adoc](#general::exp-slack-integrate.adoc). ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

Inactive instances now display correctly across both pipeline and summary views.

W-22456216

Instance detail pages now display environment names correctly instead of showing only environment types.

W-22455820

Instance detail page headers now display correctly with proper styling and element positioning.

W-22455880

Governance strategy deletion now completes successfully without returning errors.

W-22476104

The MCP Server creation flow no longer displays premature "select at least one tool" warnings during loading or when no operations exist.

W-22490327

MCP Server creation now displays helpful error messages when incorrect credentials are provided.

W-22570827, W-22570738

Connected asset graph links on agent pages now navigate directly to entity detail pages instead of list pages.

W-22571289

Cost Management recommendation cards now display in strict descending order by projected savings.

W-22586604

Text overflow issues on MCP Server creation pages are resolved.

W-22598973, W-22622184

Auto-generated MCP tool names now follow snake_case convention and use operation names instead of API asset prefixes.

W-22601645

The Continue button now enables correctly after editing optimized tool names and descriptions in Tool Mapping policy imports.

W-22603960

The MCP Tool Response Sanitization policy now displays values that match Anypoint settings.

W-22692504

Chat input fields in Cost Management now handle long prompts without overflowing the container.

W-22692107

Consumer endpoints now display correctly and no longer intermittently show implementation URLs.

W-22696329

Gateway URLs in MCP Server creation now update correctly instead of remaining stuck at default demo URLs.

W-22696327

Scan summaries now correctly display skipped services in provider scan results.

W-22701129

Cost Management optimization estimations now correctly check input schemas.

W-22709243

Credential input fields in the MCP Server wizard now display correct validation messages.

W-22730686

Azure API Management providers now display correctly in the provider listing.

W-22730614

You can now delete MCP assets from the catalog when they have zero instances.

W-22732824

Model proxy Bedrock routes now correctly clear empty session tokens when switching from STS to long-term IAM credentials.

W-22769399

Scanner deletion operations now complete cleanly without displaying stale scanner data.

W-22779340

Cost Management optimization operations now display loading indicators correctly for individual rows instead of all rows.

W-22781792

Consumer endpoint URLs for trusted MCP servers now include the correct /mcp path.

W-22782195

Read-only operation selection in MCP bridge SaaS actions now correctly deselects PUT operations.

W-22784169

The JWT Validation policy configuration form now includes the JWT Key input parameter.

W-22795041

Service catalog counts now display consistently between the UI and MCP server counts.

W-22795809

Provider pages now reload correctly when switching Business Groups.

W-22795416

Provider filters on the Agents portfolio page now return correct results for all providers including Amazon Bedrock AgentCore and Azure AI Foundry.

W-22910173

HTTP Basic Authentication configuration for Client ID Enforcement policies now works correctly.

W-22923781

You can now edit policy configurations for all policy types.

W-22923643

Rate Limiting policy search now works as expected.

W-22923811

OAuth2 OBO Credential Injection now works correctly for outbound policies.

W-22924163

Cross Origin policy forms now properly disable the Support Credentials option when applicable.

W-22924051

Tool response size limits now prevent oversized responses from exceeding client token limits.

W-22947243

Scanner connection tests for Vertex AI now return descriptive error messages on failures.

W-22947245

API instance upstream URLs now update correctly when editing trusted MCP server configurations.

W-22971120

Monitoring and performance modules now load correctly without modularity errors.

W-22999188

The All Versions filter label now displays correctly on monitoring pages instead of showing MISSING_KEY errors.

W-23003583

MCP bridge instances now display availability status correctly.

W-23003437

Asset search now validates query parameters correctly and no longer accepts empty queries.

W-22962129

Agent and MCP detail pages now display enriched metadata correctly.

W-22992220
## [](#june-18-2026)June 18, 2026 ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

The Performance page now displays monitoring data correctly for organizations in the India cloud.

W-22997947

Monitoring data now resolves to the correct environment when organizations contain multiple environments of the same type.

W-23007726

The Instances column header now displays Env Type instead of Environment.

W-22418037

The Edit action now appears in the action menu on MCP Server detail pages in EU, Japan, and Canada clouds.

W-22693560

CloudFront URL access for file downloads now works correctly in Japan and Canada clouds.

W-22686958
## [](#june-11-2026)June 11, 2026 ### What’s New This release includes security updates and improvements to the enhanced MuleSoft experience. ### Fixed Issues The release addresses these enhanced MuleSoft experience issues:
Issue Resolution ID

You can now deploy, edit, and delete MCP servers that share the same name.

W-22603005

Auto-generated MCP tool names no longer contain spaces, ensuring compliance with the MCP specification.

W-22816476

You can now open service detail pages from the Services catalog while viewing the root Business Group context.

W-22696491

Governance Insights reports now display policy rulesets and instances correctly.

W-22710201

The Environment filter on the Gateways catalog page now correctly filters the displayed gateways by the selected environment.

W-22778035

The Provider filter on portfolio pages (Agents, APIs, MCPs) now correctly returns services associated with the selected provider.

W-22815822

The Vitest library is upgraded to 4.1.8 to address a reported security vulnerability.

W-22777847

Automated policies configured at both organization and environment levels now display correctly without duplicated policy activity.

W-22735582

Policy direction (inbound or outbound) now displays correctly under application methods instead of showing generic instance policy labels.

W-22801826

A cross-tenant security vulnerability that allowed unauthorized access to Kong gateway plugin configurations across organizations is resolved.

W-22803601

Public MCP Server and Agent assets no longer allow unmanaged instance creation.

W-22733185

MCP server provisioning status now updates more reliably while reducing unnecessary refresh cycles.

W-22725529

Third-party libraries are updated to resolve reported security vulnerabilities.

W-22618670
## [](#may-28-2026)May 28, 2026 ### What’s New - You can now manage agents, APIs, MCP servers, model proxies, and gateways from one portfolio experience, so teams can govern and operate AI integrations without switching between separate tools. For more information, see [general::learning-map-exp.adoc](#general::learning-map-exp.adoc) and [general::exp-overview.adoc](#general::exp-overview.adoc). - You can now add services through provider-based discovery or manual registration, so teams can onboard both cloud-managed and custom services faster. For more information, see [general::exp-services-add-to-portfolio.adoc](#general::exp-services-add-to-portfolio.adoc), [general::exp-services-connect-providers-to-add.adoc](#general::exp-services-connect-providers-to-add.adoc), and [general::exp-services-register-manually.adoc](#general::exp-services-register-manually.adoc). - You can now create MCP servers by selecting source systems and publishing tools and resources for MCP clients, so you can more easily expose existing APIs and SaaS systems through MCP workflows. For more information, see [general::exp-services-create-mcp-server.adoc](#general::exp-services-create-mcp-server.adoc). - You can now add semantic services with Basic and Advanced scale models, so LLM-driven requests route with improved context awareness as traffic grows. For more information, see [general::exp-services-add-semantic.adoc](#general::exp-services-add-semantic.adoc). - You can now apply governance strategies across supported service types, so teams can enforce conformance and cost controls more consistently. For more information, see [general::exp-governance-create-strategy.adoc](#general::exp-governance-create-strategy.adoc) and [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc). - Scanner operations now support lifecycle workflows for running, pausing, editing, and deleting scanners, so provider discovery stays current with less manual overhead. For more information, see [general::exp-scanners-add-from-providers.adoc](#general::exp-scanners-add-from-providers.adoc) and [general::exp-scanners-manage.adoc](#general::exp-scanners-manage.adoc). - Service detail pages now centralize instance creation and management workflows for supported catalogs, so teams can align deployment operations with governance and monitoring workflows. For more information, see [general::exp-instances-add.adoc](#general::exp-instances-add.adoc) and [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc). - Monitoring guidance now connects service health, detailed metrics, and token and response analysis, so responders can triage regressions faster. For more information, see [general::exp-services-monitoring.adoc](#general::exp-services-monitoring.adoc), [general::exp-services-view-detailed-metrics.adoc](#general::exp-services-view-detailed-metrics.adoc), and [general::exp-governance-view-cost-and-token-usage.adoc](#general::exp-governance-view-cost-and-token-usage.adoc). - You can now access the experience from Anypoint Platform, direct URLs, and supported coding assistants, so teams can work from existing workflow surfaces. For more information, see [general::exp-home-start.adoc](#general::exp-home-start.adoc) [general::exp-claude-desktop-connect.adoc](#general::exp-claude-desktop-connect.adoc). - Service detail pages now clarify tab availability by service type, so operators can more easily find instance, governance, and conformance data by catalog. For more information, see [general::exp-services-view-details.adoc](#general::exp-services-view-details.adoc). ## [](#see-also)See Also - [general::learning-map-exp.adoc](#general::learning-map-exp.adoc) - [general::exp-troubleshoot.adoc](#general::exp-troubleshoot.adoc) - [general::exp-ai-assistant-troubleshoot.adoc](#general::exp-ai-assistant-troubleshoot.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # External Authorization Policy The External Authorization Policy policy authenticates requests with an external gRPC or HTTP authorization service. For configuration details, see [External Authorization Policy](https://docs.mulesoft.com/gateway/latest/policies-included-external-authorization). ## [](#february-24-2025)February 24, 2025 ### What’s New - External Authorization Policy policy implementation version 1.2.0 is now supported by Omni Gateway. - External Authorization Policy policy definition version 1.2.0 is now supported by Omni Gateway. # External Processing The External Processing policy sends the incoming HTTP requests or outgoing HTTP responses requests to an external gRPC service for additional processing For configuration details, see [External Processing Policy](https://docs.mulesoft.com/gateway/latest/policies-included-external-processing). ## [](#february-24-2025)February 24, 2025 ### What’s New - External Processing policy implementation version 1.2.0 is now supported by Omni Gateway. - External Processing policy definition version 1.2.0 is now supported by Omni Gateway. # F5 Guardrails Policy The F5 Guardrails policy evaluates OpenAI, Anthropic, and Gemini format LLM prompts and responses against F5 AI Guardrails, blocking, flagging, or redacting flagged content. For configuration details, see [F5 Guardrails Policy](https://docs.mulesoft.com/gateway/latest/policies-included-f5-guardrails). ## [](#october-15-2026)October 15, 2026 ### What’s New - F5 Guardrails policy implementation version 1.0.0 is now supported by Omni Gateway. - F5 Guardrails policy definition version 1.0.0 is now supported by Omni Gateway. # File Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [File Connector User Guide](https://docs.mulesoft.com/jp/file-connector/latest/) ## [](#1-5-7)1.5.7 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-5-6)1.5.6 **July 24, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Commons IO library is upgraded to version 2.22.0.

  • The Apache Commons Lang library is upgraded to version 3.20.0.

W-23441637
## [](#1-5-5)1.5.5 **October 30, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The mule-module-file-extension-common library is upgraded to version 1.4.5 to address the CVE-2024-47554 security vulnerabilities.

W-20000386
## [](#1-5-4)1.5.4 **September 16, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The apache-common library is upgraded to version 3.18.0.

  • The commons-io library is upgraded to version 2.20.0.

W-19549266
## [](#1-5-3)1.5.3 **March 18, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-io library is upgraded to version 2.18.0 to address reported security vulnerabilities.

W-17919658
## [](#1-5-2)1.5.2 **December 14, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-5-1)1.5.1 **May 8, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8
### Fixed Issues
Issue Resolution ID

The On New or Updated File source now performs a file size check when the Redelivery Policy is not enabled.

W-12673321

The On New or Updated File source now performs a file size check three times instead of two times.

W-12705259
## [](#1-5-0)1.5.0 **Aug 19, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8
### Fixed Issues
Issue ID

The On New or Updated File operation now provides the Overwrite field, which enables you to overwrite the target file when the destination file has the same name.

W-11427407
## [](#1-4-1)1.4.1 **July 07, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8
### Fixed Issues
Issue ID

The Write operation now throws a FILE:ILLEGAL_PATH error when the file name is not valid.

W-11352447
## [](#1-4-0)1.4.0 **June 30, 2022** ### What’s New - The **List** operation now enables you to limit and sort the number of files returned using the **Subset** field. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8
## [](#1-3-5)1.3.5 **May 26, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8
### Fixed Issues
Issue ID

The Overwrite flag for File Connector Copy operation now works correctly.

W-10688508
## [](#1-3-4)1.3.4 **December 14, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-9)Fixed Issues - Improved stability (FILEC-59). ## [](#1-3-3)1.3.3 **August 31, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-10)Fixed Issues - Fixed an issue in which the File Connector Listener operation post action was not able to rename a file. (MULE-17446) - Removed the spring repo declaration in POM files. (MULE-18023) - Upgraded the file common version. ## [](#1-3-2)1.3.2 **October 15, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-11)Fixed Issues - Fixed a bug that made the streams created by the connector have the need to be finalized when disposed. (MULE-17521) - Updated Ant version to 1.10.5 (MULE-16646) ## [](#1-3-1)1.3.1 **August 8, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-12)Fixed Issues - File List operation and the File listener now only open File channels when retrieving the content of a file. (MULE-16655) - Fixed a race condition in the File listener that could led to File channels not being closed. (MULE-17260) ## [](#1-3-0)1.3.0 **July 15, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#features)Features - The `updatedInTheLast`, `notUpdatedInTheLast`, `timeUnit` parameters have been added to the File Matcher. These parameters enable you to have a List or Listener operation that filters files that are still being written to, or are too old. ### [](#fixed-issues-13)Fixed Issues - Added `(Not) Updated in the last…​` capability to File Matcher. (MULE-17103) ## [](#1-2-4)1.2.4 **May 10, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-14)Fixed Issues - The List operation fails to list files in a directory when encountering a file without read permissions. (MULE-16819) - In Windows, the List operation fails to list files in a directory where a file has been deleted just before the list operation is executed. (MULE-16827) - NoSuchFileExceptions with file listeners in clustered environment. (MULE-16766) - File Listener with watermark skips a file. (MULE-15792) ## [](#1-2-3)1.2.3 **April 29, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-15)Fixed Issues - The List operation failed when listing a directory that contained a file that had been moved or deleted. (MULE-16766) - The listener stopped polling when failing to list a file. Now the connector either lists all files, or fails entirely. (MULE-15792) ## [](#1-2-2)1.2.2 **April 3, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-16)Fixed Issues - File Connector should not gather attributes twice on the list operation. (MULE-16356) - File Connector doesn’t fail when a file lock is not obtained. (MULE-16353) - Removed Guava dependency. (MULE-14275) - Upgraded File Commons dependency to 1.2.1. - Upgraded Commons IO to 2.6. ## [](#1-2-1)1.2.1 **November 8, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-17)Fixed Issues - File Directory listener leaks open files. (MULE-15687) - Directory parameter should have path support. (MULE-14128) ## [](#1-2-0)1.2.0 **August 14, 2018** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.0** ### [](#features-2)Features - You can make use of `timeBetweenSizeCheck` to prevent the connector from processing files while they are being written. ### [](#fixed-issues-18)Fixed Issues - File getting partial files. (MULE-14881) - `file:listener` does not delete source file when moving to a file that already exists. (MULE-15030) - File Polling Source does not communicate their Attributes correctly. (MULE-15351) - When File connector listeners are configured to move to a directory, auto-delete deletes files but does not move them. (MULE-15448) - Encoding parameter should be removed from the write operation. (MULE-15503) ## [](#1-1-3)1.1.3 **May 7, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.0** ### [](#features-3)Features - Fixed an issue that happened when using a filter by filenamePattern, failing to search files recursively in folders. ### [](#fixed-issues-19)Fixed Issues - File Connector does not check for files recursively if a filenamePattern is given. (MULE-14863) ## [](#1-1-2)1.1.2 **March 14, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-20)Fixed Issues - Connectors doesn’t communicate correctly if their POJOs properties are nulleable or not. (MULE-14701) ## [](#1-1-1)1.1.1 **February 2, 2018** ### [](#fixed-issues-21)Fixed Issues - file:listener has undescriptive display name. (MULE-14584) ## [](#1-1-0)1.1.0 **January 19, 2018** ### [](#features-4)Features This release includes the following enhancements, changes, and fixes: - Added a message source that automatically polls for new files, while handling clustering, idempotency, post actions and watermark automatically. ### [](#upgrade-requirements)Upgrade Requirements Mule 4.1 ### [](#fixed-issues-22)Fixed Issues - Support processing files in all nodes of the cluster as we did in 3.x. (MULE-14128) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # FTP Connector Release Notes for Mule 4 Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for FTP (FTP Connector) provides access to files and folders on an FTP server. Guide: [FTP Connector User Guide](https://docs.mulesoft.com/jp/ftp-connector/latest/) ## [](#2-0-4)2.0.4 **May 18, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now validates reply codes across all operations and throws a ConnectionException when error code 451 occurs. This ensures that the pool discards stale connections and replaces them with fresh ones.

W-21477651

The On New or Updated File source now correctly invalidates a corrupted FTP connection if the server response fails to parse or if the control channel abruptly closes during file listing. Previously, the listener returned a malformed connection to the connection pool, causing subsequent polling cycles to fail until you restarted the application.

W-20316906
## [](#2-0-3)2.0.3 **December 10, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly compares file names when the FTP server returns the full path as part of the file name.

W-20347004

The connector now gracefully handles the MalformedServerReplyException: Truncated server reply: '550 ' error that some FTP servers return during file existence checks and falls back to listing the parent directory to confirm the file’s existence.

W-20307018

The connector now correctly handles the List operation when an FTP server supports the MLST command but doesn’t support the MLSD command.

W-19744198
## [](#2-0-2)2.0.2 **October 28, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address the reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The Commons-collections library is upgraded to version 4.5.0.

W-19578842
## [](#2-0-1)2.0.1 **September 28, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly processes file attributes when the MLSD command returns output containing blank folder names.

W-19754116
## [](#2-0-0)2.0.0 **September 23, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The mule-file-commons module dependency is removed to make FTP Connector a standalone connector.

W-15854291

The List operation now returns the file path instead of the file content.

W-16004666

The List operation no longer includes the Time Between Size Check and Time Between Size Check Unit fields because the file content is no longer read.

W-16280695
## [](#1-8-8)1.8.8 **March 6, 2024** ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Read operation now finds files that use some special characters while single-file listing.

W-14650859
## [](#1-8-7)1.8.7 **January 19, 2024** ### What’s New - The Commons Net library is upgraded to version 3.8.0. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Read operation now finds files even if the single-file listing is not supported.

W-14150759
## [](#1-8-6)1.8.6 **January 5, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8, 11, and 17
## [](#1-8-5)1.8.5 **July 11, 2023** ### What’s New - The Commons IO library is upgraded to version 2.13.0. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Read operation now takes less time to find files when the MLST command is not supported by a server.

W-13138208, W-13674423

The Commons IO library is upgraded to version 2.13.0 to address reported security vulnerabilities.

W-13512345
## [](#1-8-4-deprecated)1.8.4 (Deprecated) **June 13, 2023** This version is deprecated. All of the features and fixed issues for this version are in version 1.8.5. ## [](#1-8-3-deprecated)1.8.3 (Deprecated) **May 31, 2023** This version is deprecated. All of the features and fixed issues for this version are in version 1.8.5. ## [](#1-8-2)1.8.2 **April 27, 2023** ### Fixed Issues
Issue ID

FTP Connector now returns connections to the pool if you configure the pooling profile connection.

W-12969684
### Compatibility
Software Version

Mule

4.1.5 and later

JDK

8
## [](#1-8-1)1.8.1 **September 28, 2022** ### Compatibility
Software Version

Mule

4.1.5 and later

JDK

8
### Fixed Issues
Issue ID

FTP Connector no longer adds a slash / in front of file name when there is no working directory specified.

W-11633025
## [](#1-8-0)1.8.0 **September 14, 2022** ### What’s New - FTP Connector now supports an independent file system matcher that lists files following FTP RTF standards. Use the **Case sensitive** field to configure an external file system matcher as case sensitive or insensitive. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
## [](#1-7-1)1.7.1 **September 6, 2022** ### Compatibility
Software Version

Mule

4.1.5 and later

JDK

8
### Fixed Issues
Issue ID

FTP Connector no longer returns NullPointerException when reading and listing files from the FTP server hosted in an AS400 server.

W-11697993
## [](#1-7-0)1.7.0 **Aug 26, 2022** ### Compatibility
Software Version

Mule

4.1.5 and later

JDK

8
### Fixed Issues
Issue ID

The On New or Updated File operation now provides the Overwrite field, which enables you to overwrite the target file when the destination file has the same name.

W-11645841
## [](#1-6-2)1.6.2 **August 23, 2022** ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

FTP Connector now checks nulls to avoid errors while reading files from AS/400 servers.

W-11493458
## [](#1-6-1)1.6.1 **July 4, 2022** ### What’s New - Upgraded versions of dependencies. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
## [](#1-6-0)1.6.0 **May 30, 2022** ### What’s New - Added the **Proxy** parameter, which enables you to set the HTTP or HTTPS tunnel proxy in the FTPS Connector global configuration. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
## [](#1-5-5)1.5.5 **October 18, 2021** ### What’s New - When FTP Connector attempted to use the MLSD command to list the directory, the server responded with `Command Not Implemented (502)` and before the connector could retry the operation with a LIST command, the server closed the connection. A call to the FEAT command is now issued to validate that MLST/MLSD commands are supported by the server. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Added more error and debug level logging information.

FTPC-73
## [](#1-5-4)1.5.4 **June 26, 2021** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### [](#fixed-issues-15)Fixed Issues Fixed a reconnection issue when a connectivity exception is raised during the poll event. (FTPC-75) ## [](#1-5-3)1.5.3 **February 2, 2021** ### [](#minimum-mule-version)Minimum Mule Version **4.1.2** ### [](#fixed-issues-16)Fixed Issues - Fixed the issue that caused incorrect initialization of streams when connection errors occurred, and which caused the streams to remain dirty and resulted in mixed up file contents. (FTPC-70) - Fixed the issue that caused the move to post-action not to work. (FTPC-67) ## [](#1-5-2)1.5.2 **August 6, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **4.1.2** ### [](#fixed-issues-17)Fixed Issues Fixed an issue in which the FTP Connector waited indefinitely for command executions that took too much time or never ended. The connector now uses the response timeout parameter when executing FTP commands. (FTPC-57) ## [](#1-5-1)1.5.1 **January 24, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **4.1.2** ### [](#fixed-issues-18)Fixed Issues Fixed the issue that caused the connector’s `delete` operation, or any other operation that had the `lock` or `overwrite` flag set to `true`, to fail. (MULE-17963) ## [](#1-5-0)1.5.0 **January 10, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **4.1.2** ### [](#features)Features Added support to set the control encoding to use in the control channel with the remote server. This new parameter is located in the **Advanced** tab for any FTPS configuration dialog. ### [](#fixed-issues-19)Fixed Issues - Fixed an issue where the Write operation was incorrectly throwing a `MULE:UNKNOWN` error instead of `FTP:ILLEGAL_PATH`. (MULE-17797) - Fixed an issue where the connector was showing an incorrect reply code when throwing an FTP error. (MULE-17815) - Fixed the FTP Listener so it is able to rename files on a POST action when `renameTo` is set but `moveTo` is left blank. (MULE-17837) - Fixed a bug where FTP connection timeout was not working if it was set to a very low value. (MULE-17867) ## [](#1-4-2)1.4.2 **October 23, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.2** ### [](#fixed-issues-20)Fixed Issues - Improve validations on name and path parameters. (MULE-17680) ## [](#1-4-1)1.4.1 **September 25, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.2** ### [](#fixed-issues-21)Fixed Issues - Fixed an issue where the connector was failing to list or poll directories in some servers. (MULE-17434) - Solved an issue where the FTP Listener was trying to release connections that were never obtained. (MULE-17490) ## [](#1-4-0)1.4.0 **September 4, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **4.1.2** ### [](#features-2)Features - The parameters **Updated in the last**, **Not updated in the last**, and **Time unit** are added to the File Matcher. These parameters enable you to have a List or Listener operation that filters files by whether or not they have been updated in the specified time unit. - Adds the option to configure FTP Remote Verification. ### [](#fixed-issues-22)Fixed Issues - Fixed a bug that made the read operation take more than one connection to read the file content. (MULE-17315) - Allow configuring Remote Verification in FTP config. (MULE-17369) - Fixed a bug that made the read operation fail for certain FTP servers. (MULE-17347) - Add **(Not) Updated in the last** capability to File Matcher in the FTP Connector. (MULE-17219) ## [](#1-3-1)1.3.1 **June 28, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **4.1.1** ### [](#fixed-issues-23)Fixed Issues - Fixed a bug that caused the connector’s listener to skip a file due to a race condition. When the polling frequency of the listener was low, the autodelete flag was true, there was a burst of files to process, and the processing of each file took longer than the polling frequency, a file could be skipped. (MULE-16999) ## [](#1-3-0)1.3.0 **May 23, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **4.1.1** ### [](#features-3)Features - The `timeBetweenSizeCheck` setting prevents the connector from processing files while they are being written. ### [](#fixed-issues-24)Fixed Issues - FTP connector should not log the full stack trace in warn level when failing to log out a connection. (MULE-16825) - Fixed a regression that affected the use of `ftp:listener` without specifying a directory. (MULE-16818) ## [](#1-2-6)1.2.6 **April 22, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **4.1.1** ### [](#fixed-issues-25)Fixed Issues - Fixed an issue that prevented reading a file that had a space in its name. (MULE-16729) - Fixed an issue that prevented virtual directories to be listed or use the polling source in them. (MULE-16625) ## [](#1-2-5)1.2.5 **March 25, 2019** ### [](#minimum-mule-version-11)Minimum Mule Version **4.1.1** ### [](#fixed-issues-26)Fixed Issues - Improved the FTP Write operation’s performance when writing on remote servers. (MULE-16557) - Fixed a bug that prevented the usage of the list operation on some FTP server configurations. (MULE-16591) ## [](#1-2-4)1.2.4 **January 21, 2019** ### [](#minimum-mule-version-12)Minimum Mule Version **4.1.1** ### [](#fixed-issues-27)Fixed Issues - Fixed bug that made the List operation take too long when the listed directory contained a large number of files. (MULE-16346) ## [](#1-2-3)1.2.3 **January 4, 2019** ### [](#minimum-mule-version-13)Minimum Mule Version **4.1.1** ### [](#fixed-issues-28)Fixed Issues - Fixed bug that made the connector get stuck while reading files from a remote server, degrading performance. (MULE-16291) ## [](#1-2-2)1.2.2 **July 12, 2018** ### [](#minimum-mule-version-14)Minimum Mule Version **4.1.0** ### [](#fixed-issues-29)Fixed Issues - `FtpFileAttributes` threw NPE when FTPFile date was null. (MULE-15301) ## [](#1-2-1)1.2.1 **June 15, 2018** ### [](#minimum-mule-version-15)Minimum Mule Version **4.1.0** ### [](#fixed-issues-30)Fixed Issues - FTP:ILLEGAL\_PATH is thrown during FTP write. (MULE-15104) - FTP:Write deletes the directories and files when no filename is provided. (MULE-15172) ## [](#1-2-0)1.2.0 **April 24, 2018** ### [](#minimum-mule-version-16)Minimum Mule Version **4.1.0** ### [](#fixed-issues-31)Fixed Issues - FTP connector should better inform on connection errors. (MULE-14993) ## [](#1-1-1)1.1.1 **February 2, 2018** ### [](#minimum-mule-version-17)Minimum Mule Version **4.1.0** ### [](#fixed-issues-32)Fixed Issues - ftp:listener has undescriptive display name. (MULE-14585) ## [](#1-1-0)1.1.0 **January 19, 2018** ### [](#minimum-mule-version-18)Minimum Mule Version **4.1.0** ### [](#features-4)Features - Added a message source that automatically polls for new files, while handling clustering, idempotency, post actions, and watermark automatically. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # FTPS Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for FTPS (FTPS Connector) connects to FTP servers as FTP Connector but adds support for Transport Layer Security (TLS). Guide: [FTPS Connector User Guide](https://docs.mulesoft.com/ftps-connector/latest/) ## [](#2-1-3)2.1.3 **October 8, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind and jackson-core libraries are upgraded to version 2.22.3.

  • The bouncycastle libraries are upgraded to version 1.86.

W-24301295, W-24311562

These libraries are removed to address reported security vulnerabilities:

  • The jsoup library is removed to address the CVE-2026-75140 security vulnerability.

  • The log4j-core library is removed to address the sonatype-2026-006746 security vulnerability.

  • The log4j-api library is removed to address the CVE-2026-49844 security vulnerability.

  • The spring-context library is removed.

W-24134338, W-24311562, W-23946849
## [](#2-1-2)2.1.2 **June 15, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The spring-framework library is upgraded to version 5.3.39-spring-framework-5.3.45.

  • The bouncycastle library is upgraded to version 1.84.

  • The log4j-core library is upgraded to version 2.25.4.

W-22919701
## [](#2-1-1)2.1.1 **March 31, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jsoup library is upgraded to version 1.15.3.

  • The log4j library is upgraded to version 2.25.3.

W-21724760
## [](#2-1-0)2.1.0 **March 20, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-20606878
## [](#2-0-5)2.0.5 **December 17, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now gracefully handles the MalformedServerReplyException: Truncated server reply: '550 ' error that some FTPS servers return during file existence checks and falls back to listing the parent directory to confirm the file’s existence.

W-20307018
## [](#2-0-4)2.0.4 **November 3, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jsoup library is upgraded to version 1.15.3 to address reported security vulnerabilities.

W-19578778
## [](#2-0-2)2.0.2 **February 5, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Bouncy Castle libraries are now forcefully set to be the top security provider to prevent the NullPointerException error from occurring during connection.

W-17511814
## [](#2-0-1)2.0.1 **January 27, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded:

  • The org.dom4j:dom4j library is upgraded to version 2.1.3.

  • The org.jsoup:jsoup library is upgraded to version 1.14.2.

  • The org.apache.logging.log4j:log4j-core library is upgraded to version 2.17.1.

  • The org.json:json library is upgraded to version 20231013.

  • The org.apache.avro:avro library is upgraded to version 1.12.0.

  • The org.yaml:snakeyaml library is upgraded to version 2.0.

  • The org.springframework:spring-context library is upgraded to version 5.2.20.RELEASE.

W-14499139

The List operation now works with a false value for a case-sensitive flag.

W-17087833
## [](#2-0-0)2.0.0 **November 13, 2024** ### What’s New - This connector is now compatible with Java 17. - This connector is now FIPS 140-2 compliant. - This connector no longer relies on reflection to reuse the SSL session from the command channel to data channels. Instead, it now supports SSL session resumption between the client and host using externally provided Bouncy Castle libraries, which you can add with the new **Required Libraries** field in the connection type. For more information, refer to [Configure Java JDK for Session Reuse](https://docs.mulesoft.com/ftps-connector/latest/ftps-studio-configuration#configure-java) and [Configure Bouncy Castle Libraries and Security Provider](https://docs.mulesoft.com/ftps-connector/latest/ftps-studio-configuration#bouncycastle). Because Bouncy Castle security providers are required for running FTPS on Java 17, all Mule applications within the same JVM must adhere to its stricter cryptographic policies. This includes enforcing modern key sizes, secure algorithms, and updated TLS configurations—affecting keystores, truststores, and all TLS-based connectors. - The `mule-file-commons` module dependency is removed. - The **List** operation now returns the file path instead of the file content. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-8-7)1.8.7 **October 10, 2024** ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Updated the FTP Connector dependency to version 1.8.8.

W-16769250
## [](#1-8-6)1.8.6 **March 6, 2024** ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Read operation now finds files that use some special characters while single-file listing.

W-14650859
## [](#1-8-5)1.8.5 **January 19, 2024** ### What’s New - The Commons Net library is upgraded to version 3.8.0. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Read operation now finds files even if the single-file listing is not supported.

W-14150759
## [](#1-8-4)1.8.4 **July 11, 2023** ### What’s New - The Commons IO library is upgraded to version 2.13.0. - The SLF4J API library is upgraded to version 2.0.7. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Read operation now takes less time to find files when the MLST command is not supported by a server.

W-13138208

The Commons IO library is upgraded to version 2.13.0 to address reported security vulnerabilities.

W-13512345

The SLF4J API library is upgraded to version 2.0.7 to address reported security vulnerabilities.

W-13512345
## [](#1-8-3-deprecated)1.8.3 (Deprecated) **June 13, 2023** This version is deprecated. All of the features and fixed issues for this version are in version 1.8.4. ## [](#1-8-2-deprecated)1.8.2 (Deprecated) **June 1, 2023** This version is deprecated. All of the features and fixed issues for this version are in version 1.8.4. ## [](#1-8-1)1.8.1 **September 29, 2022** ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

FTPS Connector no longer adds a slash / in front of file name when there is no working directory specified.

W-11633034
## [](#1-8-0)1.8.0 **September 27, 2022** ### What’s New - FTP Connector now supports an independent file system matcher that lists files following FTP RTF standards. Use the **Case sensitive** field to configure an external file system matcher as case sensitive or insensitive. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
## [](#1-7-1)1.7.1 **July 4, 2022** ### What’s New - Upgraded versions of dependencies. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
## [](#1-7-0)1.7.0 **May 30, 2022** ### What’s New - Added the **Proxy** parameter, which enables you to set the HTTP or HTTPS tunnel proxy in the FTPS Connector global configuration. ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
## [](#1-6-5)1.6.5 **March 17, 2022** ### Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated internal dependencies.

W-10857851
## [](#1-6-4)1.6.4 **June 28, 2021** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.1.2 and later

OpenJDK

8 and 11
### [](#fixed-issues-15)Fixed Issues Fixed a reconnection issue when a connectivity exception is raised during the poll event. (FTPC-75) ## [](#1-6-3)1.6.3 **June 9, 2021** ### [](#minimum-mule-version)Minimum Mule Version **4.1.2** ### [](#fixed-issues-16)Fixed Issues Fixed issue that caused the connector to fail when using TLS session resumption with concurrent sessions. ## [](#1-6-2)1.6.2 **June 8, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **4.1.2** ### [](#fixed-issues-17)Fixed Issues Fixed issue that prevented the connector from reading or writing data to FTPS server with session reuse enabled. ## [](#1-6-1)1.6.1 **January 24, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **4.1.2** ### [](#fixed-issues-18)Fixed Issues Fixed the issue that caused the connector’s `delete` operation, or any other operation that had the `lock` or `overwrite` flag set to `true`, to fail. ## [](#1-6-0)1.6.0 **January 10, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **4.1.2** ### [](#features)Features Added support to set the control encoding to use in the control channel with the remote server. This new parameter is located in the **Advanced** tab for any FTPS configuration dialog. ### [](#fixed-issues-19)Fixed Issues - Fixed an issue where the Write operation was incorrectly throwing a `MULE:UNKNOWN` error instead of `FTPS:ILLEGAL_PATH`. - Fixed an issue where the connector was showing an incorrect reply code when throwing an FTPS error. - Fixed FTPS Listener so it is able to rename files on a POST action when `renameTo` is set but `moveTo` is left blank. - Fixed a bug where the FTPS connection timeout was not working if it was set to a very low value. ## [](#1-5-1)1.5.1 **September 25, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.2** ### [](#fixed-issues-20)Fixed Issues - Fixed an issue where some servers required additional commands to encrypt the data channel when using implicit mode. ## [](#1-5-0)1.5.0 **September 4, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.2** ### [](#features-2)Features - The parameters **Updated in the last**, **Not updated in the last** and **Time unit** are added to the File Matcher, which enables you to have a List or Listener operation that filters files based on whether or not they have been updated in the specified time unit. - Adds the option to configure FTP Remote Verification. - The **Time between size check** setting prevents the connector from processing files while they are being written. ### [](#fixed-issues-21)Fixed Issues - Fixed the issue where the read operation was taking more than one connection to read the file content. - Fixed a bug that made the read operation fail for certain FTPS servers. - Fixed a bug that caused the connector’s listener to skip a file due to a race condition. This happened when the polling frequency of the listener was low, the `autodelete` flag was true, there was a burst of files to process, and the processing of each file took longer than the polling frequency. - Changed log level so that when failing to log out a connection the stack trace is not logged at `WARN` level. - Fixed a regression that affected the use of `ftps:listener` without specifying a directory. ## [](#1-4-1)1.4.1 **April 22, 2019** ### [](#fixed-issues-22)Fixed Issues - Fixed an issue that prevented reading files that had a space on its name. - Improved FTPS Write operation performance when writing on remote servers. - Fixed a bug that prevented the usage of the list operation on some FTPS server configurations. - Fixed bug that made the list operation take too long when the listed directory contained a large number of files. - Fixed bug that made the connector get stuck while reading files from a remote server, degrading performance. ## [](#1-4-0)1.4.0 **September 14, 2018** ### [](#features-3)Features - The FTPS connector now lets you define FTPS Implicit or Explicit connections. In the latter, you can also define a CLEAR or PRIVATE Data Channel Protection level. ## [](#1-3-1)1.3.1 **July 12, 2018** ### [](#fixed-issues-23)Fixed Issues - FtpFileAttributes throws NPE when FTPFile date is null. (MULE-15301) **April 2018** ## [](#1-3-0)1.3.0 **April 24, 2018** ### [](#fixed-issues-24)Fixed Issues - FTPS error message for untrusted certificates is unclear. (MULE-14931) ## [](#1-2-0)1.2.0 **April 3, 2018** ### [](#features-4)Features Initial release. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Gmail Connector Release Notes Anypoint Connector for Gmail (Gmail Connector) enables the management of your Gmail account, including sending and receiving emails and reacting to received emails. Guide: [Gmail Connector User Guide](https://docs.mulesoft.com/jp/gmail-connector/latest/) ## [](#1-1-3)1.1.3 **October 5, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Send Message operation no longer leaks resources when it checks attachment size and reads the response.

W-23137560

These libraries are upgraded to address reported security vulnerabilities:

  • The javax.mail library version 1.6.2 is replaced with jakarta.mail version 2.0.2.

  • The jakarta.activation library is upgraded to version 2.0.1.

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.3.

  • The gson library is upgraded to version 2.14.0.

  • The jsoup library is upgraded to version 1.23.2.

  • The commons-io library is upgraded to version 2.21.0.

  • The commons-lang3 library is pinned to version 3.20.0.

  • The log4j libraries are upgraded to version 2.26.1.

  • The kryo library is upgraded to version 5.6.2.

  • The org.json library is upgraded to version 20240303.

W-22465802, W-24114061, W-24262985, W-3300013, W-23137560
## [](#1-1-2)1.1.2 **May 7, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-1)1.1.1 **June 26, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue Resolution ID

Package conflicts no longer occur when using this connector with other specific connectors in a project.

W-13311688
## [](#1-1-0)1.1.0 **March 9, 2023** ### What’s New - The Oauth2c connection now contains a new **Prompt** field, which asks for user consent even if the user is already logged in. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
## [](#1-0-7)1.0.7 **February 14, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12353541
## [](#1-0-6)1.0.6 **October 7, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11845803
## [](#1-0-5)1.0.5 **April 5, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920493
## [](#1-0-4)1.0.4 **March 28, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10813917
## [](#1-0-3)1.0.3 **January 4, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9854, CONN-9833
## [](#1-0-2)1.0.2 **December 20, 2021** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9687
## [](#1-0-1)1.0.1 **December 16, 2021** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9560
## [](#1-0-0)1.0.0 **August 6, 2021** ### [](#compatibility-12)Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### [](#new-features)New Features New connector. For a list of supported configurations and operations, see the Gmail Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Google BigQuery Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Google BigQuery (Google BigQuery Connector) gives you access to the Google BigQuery platform. This connector exposes operations provided by the Google BigQuery REST API. Guide: [Google BigQuery Connector User Guide](https://docs.mulesoft.com/google-bigquery-connector/latest/) ## [](#1-3-0)1.3.0 **October 9, 2026** ### What’s New - The connector now includes a [**Workload Identity Federation**](https://docs.mulesoft.com/google-bigquery-connector/latest/google-bigquery-connector-reference#Config_Wif) connection that uses MuleSoft as the identity provider. You can authenticate to Google BigQuery with an Anypoint Connected App and a Google `external_account` configuration instead of a service-account key. ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.3.

  • The org.apache.logging.log4j:log4j-core library is upgraded to version 2.26.1.

  • The io.netty:netty-codec-http library is upgraded to version 4.2.18.Final.

  • The commons-codec:commons-codec library is upgraded to version 1.22.1.

W-24262985, W-3300013
## [](#1-2-1)1.2.1 **August 14, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Get Query Results operation now applies the configured Max Results value to every page, instead of only the first page.

W-22397918

JWT connections no longer receive an HTTP 401 error on the operation that immediately follows a paginated Get Query Results call.

W-23091542

These libraries are upgraded to address reported security vulnerabilities:

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.18.6.

  • The log4j library is upgraded to version 2.25.4.

W-22397918, W-23471765
## [](#1-2-0)1.2.0 **February 10, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-20976447
## [](#1-1-9)1.1.9 **March 26, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The log4j dependency is upgraded to version 2.17.1 to address reported security vulnerabilities.

W-17235126
## [](#1-1-8)1.1.8 **August 12, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2

OpenJDK

8, 11, and 17
## [](#1-1-7)1.1.7 **June 25, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Google BigQuery Connector no longer hangs when an exception happens in an HTTP client.

W-14051457
## [](#1-1-6)1.1.6 **June 24, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
### Fixed Issues
Issue Resolution ID

Pagination in the Get Query Results operation now works as intended when the returned rows are greater than the Max Results value.

W-13157049
## [](#1-1-5)1.1.5 **Jan 17, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
### Fixed Issues
Issue Resolution ID

The access token creation configuration now works correctly.

W-14270208
## [](#1-1-4)1.1.4 **Oct 2, 2023** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
### Fixed Issues
Issue Resolution ID

The com.google.guava component is upgraded from version 25.0-jre to 32.0.1-jre.

W-13844852

The selenium-java component is upgraded from version 3.141.59 to 4.0.0.

W-13844852

The io.netty library is upgraded to version 4.1.94.Final.

W-13844852

The connector now returns the correct payload.status.errorResult.message in src/test/munit/jobs/operations/jwt/job-operation-cancel-test-suite.xml.

W-13844852
## [](#1-1-3)1.1.3 **May 12, 2023** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.13.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665459
## [](#1-1-2)1.1.2 **February 3, 2023** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
### Fixed Issues
Issue Resolution ID

The Query operation now regenerates the connection after the token expires.

W-12236804
## [](#1-1-1)1.1.1 **October 19, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
### Fixed Issues
Issue ID

Library dependencies are upgraded to address reported security vulnerabilities.

W-11913985
## [](#1-1-0)1.1.0 **August 25, 2022** ### What’s New - You can now view the schema in the attributes of the **Query** and the **Get Query Results** operations. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
### Fixed Issues
Issue ID

The Query operation now returns the correct API response.

W-11515614
## [](#1-0-0)1.0.0 **March 25, 2022** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Google BigQuery Connector Reference Guide. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

Google BigQuery REST API

v2
## Known Issues
Known Issue Workaround

It is not possible to use the Test connection feature for the OAuth2 connection in Anypoint Studio.

Use the JWT connection.

It is not possible to resolve metadata using the OAuth2 connection for the On Table Row source in Anypoint Studio.

Use the JWT connection.
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Google Calendar Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Google Calendar (Google Calendar Connector) gives you access to the Google Calendar platform. This connector exposes operations provided by the Google Calendar API. Guide: [Google Calendar Connector User Guide](https://docs.mulesoft.com/jp/google-calendar-connector/latest/) ## [](#1-2-3)1.2.3 **May 28, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.commons library is upgraded to version 1.10.0 to address reported security vulnerabilities.

W-11913981
## [](#1-2-2)1.2.2 **October 18, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The org.apache.commons library is upgraded to version 1.10.0 to address reported security vulnerabilities.

W-11913981
## [](#1-2-1)1.2.1 **October 7, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853421
## [](#1-2-0)1.2.0 **July 12, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The new Access Type and Prompt fields for the OAuth2 connection enable the connector to retrieve a refresh token. For more information, refer to the Google Calendar Connector Reference.

W-11381827
## [](#1-1-5)1.1.5 **April 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded com.fasterxml.jackson.core:jackson-databind:2.12.4 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920468
## [](#1-1-4)1.1.4 **March 29, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10894133
## [](#1-1-3)1.1.3 **January 5, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9848
## [](#1-1-2)1.1.2 **December 20, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9689
## [](#1-1-1)1.1.1 **December 16, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9567
## [](#1-1-0)1.1.0 **May 12, 2021** ### [](#compatibility-10)Compatibility Google Calendar Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features - Added the **On Updated Events** source. (CONN-7605) ## [](#1-0-0)1.0.0 **March 18, 2021** New connector ### [](#compatibility-11)Compatibility Google Calendar Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features-2)Features For a list of supported configurations and operations, see the Google Calendar Connector Reference Guide. ### [](#known-issues)Known Issues When using the watch operations, you can receive the wrong error message. If the address for a watch operation is not authorized, the connector refreshes the access token and returns the message `Access Token expired for resource owner id _resource_owner_id_`. The correct message is `Unauthorized WebHook callback channel: _address_`. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Google Drive Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Google Drive (Google Drive Connector) enables you to automate business processes between Google Drive (Drive) and other enterprise applications, either on-premises or in the cloud. You can programmatically access and upload content and relevant information to and from Drive using Google Drive Connector. Guide: [Google Drive Connector User Guide](https://docs.mulesoft.com/jp/google-drive-connector/latest/) ## [](#1-1-4)1.1.4 **June 11, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Sources now capture new items without setting the start date of the field.

W-15131209
## [](#1-1-3)1.1.3 **May 2, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-2)1.1.2 **September 20, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Drive changes list operation now sends the Page Token field in the input request as intended.

W-13921651
## [](#1-1-1)1.1.1 **April 19, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The rest-sdk-commons library is updated to version 0-1.4-HF1 to fix a Dataweave scripts issue.

W-12942849
## [](#1-1-0)1.1.0 **September 27, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

You can now download files with the new MEDIA type added to the alt field for all operations.

W-11489299
## [](#1-0-1)1.0.1 **January 3, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9574
## [](#1-0-0)1.0.0 **April 26, 2021** ### [](#compatibility-7)Compatibility Google Drive Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features New connector. For a list of supported configurations and operations, see the Google Drive Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Google Gemini Connector Release Notes Anypoint Connector for Google Gemini (Google Gemini Connector) enables Mule applications to access the Google Gemini API. Guide: [Google Gemini Connector User Guide](https://docs.mulesoft.com/google-gemini-connector/latest/) ## [](#1-0-21)1.0.21 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-0-20)1.0.20 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-0-19)1.0.19 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-0-18)1.0.18 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-0-0)1.0.0 **December 11, 2025** ### What’s New This is a new connector. For more information, see the [Google Gemini Connector User Guide](https://docs.mulesoft.com/google-gemini-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
## [](#see-also)See Also - [Google Gemini Connector User Guide](https://docs.mulesoft.com/google-gemini-connector/latest/) - [Google Gemini Connector Reference](https://docs.mulesoft.com/google-gemini-connector/latest/google-gemini-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Google Model Armor Guardrails Policy The Google Model Armor Guardrails policy evaluates OpenAI and Gemini format LLM prompts and responses against a Google Cloud Model Armor template, blocking or redacting flagged content. For configuration details, see [Google Model Armor Guardrails Policy](https://docs.mulesoft.com/gateway/latest/policies-included-google-model-armor-guardrails). ## [](#october-15-2026)October 15, 2026 ### What’s New - Google Model Armor Guardrails policy implementation version 1.0.0 is now supported by Omni Gateway. - Google Model Armor Guardrails policy definition version 1.0.0 is now supported by Omni Gateway. # Google Pub/Sub Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Google Pub/Sub (Google Pub/Sub Connector) enables you to access the Google Pub/Sub messaging platform. This connector exposes operations provided by the Google Pub/Sub client libraries. Guide: [Google Pub/Sub Connector User Guide](https://docs.mulesoft.com/google-pubsub-connector/latest/) ## [](#1-3-0)1.3.0 **October 4, 2026** ### What’s New - This release includes general security fixes. - The [**MuleSoft IdP Configuration**](https://docs.mulesoft.com/google-pubsub-connector/latest/google-pubsub-connector-reference#WifMuleSoftIdpConfig) type now includes the optional **Token Endpoint** field. Set **Token Endpoint** so a Workload Identity Federation connection requests tokens from the control plane where the app runs. If you leave **Token Endpoint** blank, the connector uses `https://anypoint.mulesoft.com/accounts/api/v2/oauth2/token`. For EU1, set `https://eu1.anypoint.mulesoft.com/accounts/api/v2/oauth2/token`. If the value is not an HTTPS URL with a host, token exchange fails with `Token Endpoint must be an https URL`. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.3.

  • The com.fasterxml.jackson.datatype:jackson-datatype-jsr310 library is upgraded to version 2.22.3.

  • The com.google.protobuf:protobuf-java library is upgraded to version 4.36.2.

  • The org.threeten:threetenbp library is upgraded to version 1.7.4.

  • The com.google.auth:google-auth-library-oauth2-http library is upgraded to version 1.52.0.

  • The com.google.auth:google-auth-library-credentials library is upgraded to version 1.52.0.

  • The io.grpc:grpc-bom and io.grpc:grpc-netty-shaded libraries are upgraded to version 1.84.0.

W-24262985, W-3300013
## [](#1-2-2)1.2.2 **August 26, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Workload Identity Federation connections that use a MuleSoft Connected App now remain authenticated past the 60-minute Anypoint OIDC token lifetime. Previously, publish, subscribe, and listener operations failed with authentication errors after approximately 60 minutes. No configuration change is required.

W-23766669

These libraries are upgraded to address reported security vulnerabilities:

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.2.

  • The io.grpc:grpc-bom and io.grpc:grpc-netty-shaded libraries are upgraded to version 1.82.2.

  • The com.google.cloud:libraries-bom library is upgraded to version 26.85.1.

  • The org.apache.logging.log4j:log4j-api library is upgraded to version 2.16.0.

W-23441803
## [](#1-2-1)1.2.1 **July 15, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The On message listener source now routes streaming-pull traffic through the host and port configured in the Override Host and Override Port fields, consistent with publish and unary subscribe operations. Previously, the source ignored these settings and connected to the default public endpoint.

W-23349394

The Create Snapshot, Delete Snapshot, Seek, and List Snapshots operations now automatically retry on transient errors, instead of failing immediately.

W-22579551

These libraries are upgraded:

  • The com.google.cloud:libraries-bom library is upgraded to version 26.85.0.

  • The com.google.cloud:google-cloud-pubsub library is upgraded to version 1.152.0.

  • The com.google.auth:google-auth-library-oauth2-http library is upgraded to version 1.49.0.

  • The com.google.auth:google-auth-library-credentials library is upgraded to version 1.49.0.

  • The grpc-api, grpc-netty-shaded, and grpc-core libraries are upgraded to version 1.81.0.

W-22579551
## [](#1-2-0)1.2.0 **November 16, 2025** ### What’s New - The connector now includes the new **Override Host** and **Override Port** fields to direct all API calls to the specified host and port instead of the default public endpoint. This allows you to configure custom host and port settings to route traffic through private endpoints, enabling compliance with security policies that require avoiding public internet connections. - The connector now includes the new **Acknowledge Message** and **NACK Message** operations to acknowledge or negatively acknowledge messages. The **On message listener** source now includes the new **Acknowledgment Mode** field, providing full control over the message processing lifecycle. This prevents infinite processing loops when downstream systems fail and provides better error recovery mechanisms. - The connector now includes the new **Authentication Method** and **MuleSoft IdP Configuration** fields to add Workload Identity Federation (WIF) support, enabling federated authentication through MuleSoft as an identity provider. For more information, see [Google Pub/Sub Connector 1.3 Reference](https://docs.mulesoft.com/google-pubsub-connector/latest/google-pubsub-connector-reference). ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-1)1.1.1 **November 4, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.google.protobuf library is upgraded to version 4.28.2 to address reported security vulnerabilities.

W-19881501
## [](#1-1-0)1.1.0 **September 3, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.avro library is upgraded to version 1.11.4 to address reported security vulnerabilities.

W-19324170
## [](#1-0-8)1.0.8 **May 5, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The google-cloud-pubsub dependency is upgraded to version 1.138.0.

W-18189383
## [](#1-0-7)1.0.7 **March 19, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-6)1.0.6 **December 5, 2023** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The component org.apache.avro:avro is upgraded from version 1.10.2 to version 1.11.3 to address reported security vulnerabilities.

W-14462886

The component com.google.guava:guava is upgraded from version 31.1-jre to version 32.0.1-jre to address reported security vulnerabilities.

W-14462911
## [](#1-0-5)1.0.5 **May 2, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Jackson-core and jackson-databind libraries are upgraded to version 2.15.0.

W-12665859
## [](#1-0-4)1.0.4 **October 31, 2022** ### What’s New - The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.13.4.2. - The com.google.cloud:libraries-bom library is upgraded to version 26.0.0. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.13.4.2 to address reported security vulnerabilities.

W-11853406

The com.google.cloud:libraries-bom library is upgraded to version 26.0.0 to address reported security vulnerabilities.

W-11872196
## [](#1-0-3)1.0.3 **July 14, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920494
## [](#1-0-2)1.0.2 **January 20, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.protobuf library due to a security vulnerability.

CONN-9977

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9813
## [](#1-0-1)1.0.1 **November 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9286
## [](#1-0-0)1.0.0 **October 18, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Google Pub/Sub Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Google Sheets Connector Release Notes Anypoint Connector for Google Sheets (Google Sheets Connector) synchronizes data and automates business processes between Google Sheets and third-party applications, either on-premises or in the cloud. Guide: [Google Sheets Connector User Guide](https://docs.mulesoft.com/jp/google-sheets-connector/latest/) ## [](#1-1-15)1.1.15 **September 23, 2024** ### Compatibility
Application/Service Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Downloading the latest version of Google Sheets Connector in Anypoint Studio now works correctly.

W-16584319
## [](#1-1-14)1.1.14 **June 13, 2024** ### Compatibility
Application/Service Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Google Sheets Connector in Anypoint Studio as intended.

W-15970760
## [](#1-1-13)1.1.13 **April 26, 2024** ### Compatibility
Application/Service Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

When using the Columns To Monitor configuration in the Updated Row source to specify the column name, the connector no longer throws a NullPointerException.

W-15519418
## [](#1-1-12)1.1.12 **March 8, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-11)1.1.11 **July 31, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue Resolution ID

If an authorization token is not available when starting a source, the source now reconnects as intended instead of stopping and disposing.

W-13661495

On early timeout, the connector no longer fails with a NullPointerException.

W-13601234
## [](#1-1-10)1.1.10 **March 9, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12391993, W-12378442
## [](#1-1-9)1.1.9 **October 5, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10887516, W-10933097, W-11719209
## [](#1-1-8)1.1.8 **March 30, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10899109, W-10574328
## [](#1-1-7)1.1.7 **January 25, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-910
## [](#1-1-6)1.1.6 **January 13, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Upgraded library dependencies.

COCN-894
## [](#1-1-5)1.1.5 **December 20, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Upgraded library dependencies.

COCN-883
## [](#1-1-4)1.1.4 **December 15, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

SE-22770, COCN-747, COCN-742, COCN-718, COCN-622, COCN-575
## [](#1-1-3)1.1.3 **July 27, 2021** ### [](#compatibility-13)Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### [](#fixed-issues-12)Fixed Issues - The **Row Number** field type was changed from String to Number. ## [](#1-1-2)1.1.2 **July 8, 2021** ### [](#compatibility-14)Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### [](#fixed-issues-13)Fixed Issues The display names for the following operations were updated for simplicity:
Previous Name New Name

On New Row Listener

New Row

On Updated Row Listener

Updated Row

On New Spreadsheet Listener

New Spreadsheet
## [](#1-1-1)1.1.1 **March 22, 2021** ### [](#compatibility-15)Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### [](#fixed-issues-14)Fixed Issues Attributes were removed from void operations. ## [](#1-1-0)1.1.0 **March 12, 2021** ### [](#compatibility-16)Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### [](#features)Features Added the Insert Data Option field to the Append Spreadsheets Values operation. ## [](#1-0-0)1.0.0 **March 8, 2021** New connector ### [](#compatibility-17)Compatibility
Application/Service Version

Mule

4.2.1 and later

JDK Version

1.8
### [](#features-2)Features For a list of supported configurations and operations, see the Google Sheets Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # GraphQL Access Control The GraphQL Access Control policy authorizes incoming GraphQL requests by evaluating Cedar rules. For configuration details, see [GraphQL Access Control Policy](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-access-control). ## [](#september-2-2026)September 2, 2026 ### What’s New - GraphQL Access Control policy implementation version 1.0.0 is now supported by Omni Gateway. - GraphQL Access Control policy definition version 1.0.0 is now supported by Omni Gateway. # GraphQL Introspection Control The GraphQL Introspection Control policy blocks or allows requests that access the `_schema_`_,_ `type`, and `__typename` GraphQL meta fields. For configuration details, see [GraphQL Introspection Control Policy](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-introspection-control). ## [](#march-09-2026)March 09, 2026 ### What’s New - GraphQL Introspection Control policy implementation version 1.0.0 is now supported by Omni Gateway. - GraphQL Introspection Control policy definition version 1.0.0 is now supported by Omni Gateway. # GraphQL Operation Limits The GraphQL Operation Limits policy limits GraphQL operation depth, aliases, root fields, and directives. For configuration details, see [GraphQL Operation Limits Policy](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-operation-limits). ## [](#march-09-2026)March 09, 2026 ### What’s New - GraphQL Operation Limits policy implementation version 1.0.1 is now supported by Omni Gateway. - GraphQL Operation Limits policy definition version 1.0.0 is now supported by Omni Gateway. # GraphQL Schema Validation The GraphQL Schema Validation policy validates incoming GraphQL operations against a GraphQL schema definition For configuration details, see [GraphQL Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-schema-validation). ## [](#march-18-2026)March 18, 2026 ### What’s New - GraphQL Schema Validation policy implementation version 1.0.0 is now supported by Omni Gateway. - GraphQL Schema Validation policy definition version 1.0.0 is now supported by Omni Gateway. # GraphQL Static Query Complexity The GraphQL Static Query Complexity policy calculates query complexity and blocks requests that exceed the defined budget For configuration details, see [GraphQL Static Query Complexity Policy](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-static-query-complexity). ## [](#march-20-2026)March 20, 2026 ### What’s New - GraphQL Static Query Complexity policy implementation version 1.0.0 is now supported by Omni Gateway. - GraphQL Static Query Complexity policy definition version 1.0.0 is now supported by Omni Gateway. # gRPC Connector Release Notes Anypoint Connector for gRPC (gRPC Connector) enables you to connect to the gRPC API. gRPC Connector enables Mule applications to communicate with gRPC services, providing both client and server capabilities for high-performance, cross-platform RPC communication. Guide: [gRPC Connector User Guide](https://docs.mulesoft.com/grpc-connector/latest/) ## [](#1-0-4)1.0.4 **September 7, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

When a gRPC server returned an error message containing non-ASCII characters, gRPC Connector displayed the raw percent-encoded bytes (for example, %C2%A0) instead of the actual text. Error messages with non-ASCII characters are now decoded correctly.

W-24045828
## [](#1-0-3)1.0.3 **August 31, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

gRPC Client connections to HTTP/2-only servers no longer silently fall back to HTTP/1.1, and connections configured with a custom TLS context no longer fail with UNIMPLEMENTED.

W-24021389

gRPC Server sources deployed on a domain-shared HTTP Listener no longer route requests to a disposed application after a hot redeployment, which previously caused UNIMPLEMENTED, DEADLINE_EXCEEDED, or HTTP 408 errors.

W-24006480
## [](#1-0-2)1.0.2 **August 11, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

Inbound gRPC request metadata (headers) is now accessible to Mule flows through attributes.headers for the gRPC server sources. Header keys are lowercased, and header values aren’t logged to prevent credential leakage. For more information, see gRPC Connector Reference.

W-23556268
## [](#1-0-1)1.0.1 **July 31, 2026** ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

gRPC server sources now return a configurable gRPC status code and description to the client through the Status Code and Description fields, instead of always returning UNKNOWN. For more information, see gRPC Connector Reference.

W-23537999
## [](#1-0-0)1.0.0 **March 18, 2026** ### What’s New This is a new connector. For more information, see the [gRPC Connector User Guide](https://docs.mulesoft.com/grpc-connector/latest/). ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17
## [](#see-also)See Also - [gRPC Connector User Guide](https://docs.mulesoft.com/grpc-connector/latest/) - [gRPC Connector Reference](https://docs.mulesoft.com/grpc-connector/latest/grpc-connector-reference) - [Salesforce Help](https://help.salesforce.com/s/) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # gRPC Support on Anypoint Platform Implement and consume gRPC APIs as part of your API-led strategy using gRPC support in Anypoint Platform. gRPC is a high-performance, open-source framework for remote procedure calls (RPCs) that uses Protocol Buffers (protobuf) as the interface definition language. gRPC uses HTTP/2 for transport and is well-suited for server-to-server communication and microservices architectures. Anypoint Platform supports gRPC in the following products and stages:
API-Led Journey Stage Product Versions Supported Learn More

Design Specs

Anypoint Code Builder

Protobuf 3

Design your gRPC specs (API Type: gRPC API, Protobuf 3) in Anypoint Code Builder and verify them in the API console.

Govern Specs

Anypoint API Governance

Protobuf 3

Validate your gRPC API specs against governance rulesets during the design phase. After you publish the specs to Exchange, govern them using API Governance.

Publish Specs

Anypoint Exchange

Protobuf 3

Publish your gRPC API specs to Exchange to share and promote collaboration. When implementing, you can filter by gRPC when searching for specs in Exchange.

Implement APIs

Anypoint Code Builder

Protobuf 3

Scaffold and implement gRPC specs in a Mule project using Anypoint Code Builder. Discover specs from Exchange; APIkit generates the implementation from your .proto file. The minimum Mule runtime engine requirement for this feature is Mule 4.11.

APIkit for gRPC

Protobuf 3

Scaffold and implement gRPC APIs in a Mule project from a .proto file using APIkit for gRPC. The minimum Mule runtime engine requirement for this feature is Mule 4.11.

Deploy

Runtime Fabric

Protobuf 3

Deploy your gRPC API to Runtime Fabric. When deploying a gRPC API, you must enable HTTP/2 ingress. The minimum Mule runtime engine requirement is Mule 4.11 or later.

Manage APIs

Anypoint API Manager

Protobuf 3

Create and manage your gRPC API instances and proxies; apply policies and SDLC for gRPC and HTTP/2.

Omni Gateway

Protobuf 3

Manage and govern your external gRPC services using Omni Gateway.

Connect to gRPC Services

Anypoint Connector for gRPC (gRPC Connector)

Protobuf 3

Call external gRPC services from your Mule applications using gRPC Connector
## [](#history-of-grpc-support)History of gRPC Support Following is a history of support for gRPC in Anypoint Platform. ### [](#march-18-2026)March 18, 2026 - Anypoint Platform supports gRPC in the following products and capabilities: - Anypoint Connector for gRPC (gRPC Connector) for connecting to gRPC services from Mule applications ### [](#march-17-2026)March 17, 2026 - Anypoint Platform supports gRPC in the following products and capabilities: - Anypoint Code Builder for designing gRPC API specifications (Protobuf 3) - Anypoint Code Builder for implementing and scaffolding gRPC APIs - APIkit for gRPC for scaffolding gRPC APIs from .proto specifications - Anypoint Exchange for publishing and discovering gRPC API specifications - Anypoint API Manager for managing gRPC API instances and applying policies - Omni Gateway for managing external gRPC services - Runtime Fabric and Hybrid Standalone (self-hosted deployments) for deploying gRPC APIs (HTTP/2 ingress; Mule runtime 4.11 or later required) - Anypoint API Governance for governing gRPC API specifications ## [](#see-also)See Also - [Anypoint Code Builder Release Notes](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#March16-2026) - [APIkit for gRPC Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-grpc-1.0.0) - [API Governance Release Notes](https://docs.mulesoft.com/jp/release-notes/api-governance/api-governance-release-notes#feb-20-2026) - [Anypoint Exchange Release Notes](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#march-2026) - [gRPC Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4) - [gRPC documentation at grpc.io](https://grpc.io/docs/) - [Known Issues](https://help.salesforce.com/s/issues) # HDFS Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for the Apache Hadoop Distributed File System (HDFS) is used as a bidirectional gateway between Mule applications and HDFS. Guide: [HDFS Connector User Guide](https://docs.mulesoft.com/jp/hdfs-connector/latest/) ## [](#6-0-33)6.0.33 **October 8, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The zookeeper library is upgraded to version 3.9.6.

  • The guava library is upgraded to version 33.7.2-jre.

  • The commons-lang3 library is upgraded to version 3.21.0.

  • The logback-core library is upgraded to version 1.6.5.

  • The commons-codec library is upgraded to version 1.22.1.

  • The jline library is upgraded to version 3.30.17.

  • The kerby library is upgraded to version 2.1.2.

W-24311579, W-24311589, W-24311587, W-24311585, W-24311582, W-24311577, W-24311612, W-24440483
## [](#6-0-32)6.0.32 **September 29, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The logback-core library is upgraded to version 1.5.35.

  • The kerby libraries are upgraded to version 2.1.2.

  • The netty libraries are upgraded to version 4.2.18.Final.

  • The jackson-databind library is upgraded to version 2.22.3.

  • The jline library is upgraded to version 3.30.15.

  • The jetty-security and snappy-java libraries are excluded.

W-24134449, W-24311575, W-24311586, W-24311590, W-24311593, W-24311595, W-24311611
## [](#6-0-31)6.0.31 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
## [](#6-0-30)6.0.30 **August 12, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The zookeeper library is upgraded to version 3.9.5.

  • The commons-configuration2 library is upgraded to version 2.15.1.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-compress library is upgraded to version 1.28.0.

  • The jackson-databind library is upgraded to version 2.22.0.

  • The guava library is upgraded to version 32.1.3-jre.

  • The gson library is upgraded to version 2.14.0.

  • The netty libraries are upgraded to version 4.2.17.Final.

  • The jetty libraries are upgraded to version 9.4.58.v20250814.

  • The httpclient library is upgraded to version 4.5.14.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-codec library is upgraded to version 1.22.0.

  • The commons-logging library is upgraded to version 1.4.0.

  • The logback-core library is upgraded to version 1.5.31.

  • The hadoop-shaded-guava library is upgraded to version 1.5.0.

W-23441615
## [](#6-0-29)6.0.29 **May 20, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues This release includes only non-user-impacting changes. ## [](#6-0-28)6.0.28 **April 22, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The netty-codec-http library is upgraded to version 4.2.12.Final.

  • The netty-codec-http2 library is upgraded to version 4.2.12.Final.

  • The jackson-core library is upgraded to version 2.21.1.

  • The zookeeper library is upgraded to version 2.8.6.

W-21919325
## [](#6-0-27)6.0.27 **January 10, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported 3PP vulnerabilities:

  • The avro library is upgraded to version 1.11.4.

  • The commons-compress library is upgraded to version 1.26.1.

  • The commons-io library is upgraded to version 2.15.0.

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The gson library is upgraded to version 2.12.0.

  • The guava library is upgraded to version 32.0.0-jre.

  • The jetty-util library is upgraded to version 9.4.57.v20241219.

  • The netty-codec library is upgraded to version 4.2.8.Final.

  • The netty-codec-http library is upgraded to version 4.2.8.Final.

  • The netty-codec-http2 library is upgraded to version 4.2.8.Final.

  • The netty-codec-smtp library is upgraded to version 4.2.8.Final.

  • The netty-common library is upgraded to version 4.2.8.Final.

  • The netty-handler library is upgraded to version 4.2.8.Final.

  • The woodstox-core library is upgraded to version 5.4.0.

W-20777054
## [](#6-0-26)6.0.26 **April 14, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Hadoop API is upgraded to version 3.4.1.

W-18225035

The json-smart library is upgraded to version 2.5.2.

W-18145218

The hadoop-shaded-guava library is upgraded to version 1.3.0.

W-18145218
## [](#6-0-25)6.0.25 **April 12, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8, 11, and 17
## [](#6-0-24)6.0.24 **October 10, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853405

The com.google.protobuf library is upgraded to version 3.21.7 to address reported security vulnerabilities.

W-11872195

The ch.qos.reload4j library is upgraded to version 1.2.22 to address reported security vulnerabilities.

N/A
## [](#6-0-23)6.0.23 **September 8, 2022** ### What’s New - The `ch.qos.reload4j` library is upgraded to version 1.2.22 to address reported security vulnerabilities. ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The ch.qos.reload4j library is upgraded to version 1.2.22 to address reported security vulnerabilities.

W-11702448
## [](#6-0-22)6.0.22 **August 25, 2022** ### What’s New - The `datatables:1.10.17` transitive dependency is excluded to address reported security vulnerabilities. - The `org.apache.hadoop:hadoop-yarn-common:3.3.3` transitive dependency is excluded to address reported security vulnerabilities. ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The datatables:1.10.17 transitive dependency is excluded to address reported security vulnerabilities.

W-11627692

The org.apache.hadoop:hadoop-yarn-common:3.3.3 transitive dependency is excluded to address reported security vulnerabilities.

W-11627693
## [](#6-0-21)6.0.21 **July 22, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by excluding the Jackson Mapper ASL transitive dependency org.codehaus.jackson:jackson-mapper-asl:1.9.2.

W-11430454
## [](#6-0-20)6.0.20 **July 14, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jetty HTTP package from org.eclipse.jetty:jetty-http:9.4.43.v20210629 to org.eclipse.jetty:jetty-http:9.4.48.v20220622.

W-11406696

Fixed reported security vulnerabilities by upgrading the Jetty IO package from org.eclipse.jetty:jetty-io:9.4.43.v20210629 to org.eclipse.jetty:jetty-io:9.4.48.v20220622.

W-11406697

Fixed reported security vulnerabilities by upgrading the Jetty Client package from org.eclipse.jetty:jetty-client:9.4.43.v20210629 to org.eclipse.jetty:jetty-client:9.4.48.v20220622.

W-11417271

Kerberos tickets are now auto-renewed once they expire.

W-11422521
## [](#6-0-19)6.0.19 **June 15, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Hadoop Common package from org.apache.hadoop:hadoop-common:3.3.1 to org.apache.hadoop:hadoop-common:3.3.3.

W-11195293
## [](#6-0-18)6.0.18 **March 31, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.13.2.1.

W-10920479
## [](#6-0-17)6.0.17 **January 14, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Protobuf library from com.google.protobuf:protobuf-java:2.5.0 to com.google.protobuf:protobuf-java:3.16.1.

CONN-9912
## [](#6-0-16)6.0.16 **January 7, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the XMLSec library from com.fasterxml.jackson.core:jackson-databind:2.11.0.rc1 to com.fasterxml.jackson.core:jackson-databind:2.12.6.

CONN-9824
## [](#6-0-15)6.0.15 **December 7, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the GSON library from com.google.code.gson:gson:2.8.5 to com.google.code.gson:gson:2.8.9.

CONN-9292
## [](#6-0-14)6.0.14 **August 11, 2021** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-18)Fixed Issues - Fixed all reported security vulnerabilities. ## [](#6-0-13)6.0.13 **July 12, 2021** ### [](#compatibility-21)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-19)Fixed Issues - Fixed all reported security vulnerabilities. ## [](#6-0-12)6.0.12 **June 24, 2021** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-20)Fixed Issues - Fixed all reported security vulnerabilities. ## [](#6-0-11)6.0.11 **April 21, 2021** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-21)Fixed Issues - Fixed all reported security vulnerabilities. ## [](#6-0-10)6.0.10 **March 19, 2021** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-22)Fixed Issues - Fixed all reported security vulnerabilities. ## [](#6-0-9)6.0.9 **February 9, 2021** ### [](#compatibility-25)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-23)Fixed Issues - The List Status operation did not return file length and block replicas. (SE-19511) - Fixed all reported security vulnerabilities. ## [](#6-0-8)6.0.8 **January 7, 2021** ### [](#compatibility-26)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-24)Fixed Issues Fixed all reported security vulnerabilities. ## [](#6-0-7)6.0.7 **November 12, 2020** ### [](#compatibility-27)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-25)Fixed Issues Fixed all reported security vulnerabilities. ## [](#6-0-6)6.0.6 **September 7, 2020** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-26)Fixed Issues - Fixed an issue in which the Kerberos Connection ignored the username set in the configuration. (SE-17321) - Fixed all reported vulnerabilities. ## [](#6-0-5)6.0.5 **July 14, 2020** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later
### [](#fixed-issues-27)Fixed Issues - Fixed an issue in which the `read` operation did not support XLSX and other multipart content types. (SE-16432) - Fixed all reported vulnerabilities. ## [](#6-0-4)6.0.4 **July 7, 2020** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later
### [](#fixed-issues-28)Fixed Issues - Fixed all reported vulnerabilities. ## [](#6-0-3)6.0.3 **May 5, 2020** ### [](#compatibility-31)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later
### [](#fixed-issues-29)Fixed Issues - Fixed all reported vulnerabilities. ## [](#6-0-2)6.0.2 **September 6, 2019** ### [](#compatibility-32)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later
### [](#features)Features - Upgraded Hadoop Client to version 3.2.0. ## [](#6-0-1)6.0.1 **June 21, 2019** ### [](#compatibility-33)Compatibility
Software Version

Mule

4.1.1 and later

Hadoop Distributed File System

2.8.1 and later
### [](#fixed-issues-30)Fixed Issues - Cannot install the HDFS connector in Anypoint Studio 7.3.4. (SE-12006) ## [](#6-0-0)6.0.0 **November 18, 2017** ### [](#compatibility-34)Compatibility
Software Version

Mule

4.0 and later

Hadoop Distributed File System

2.8.1 and later
### [](#features-2)Features - Migrated to Mule 4.0.0 runtime. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Header Injection ## [](#1-3-3)1.3.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-3-1)1.3.1 **May 26, 2022** ### [](#fixed-issues)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-3-0)1.3.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-2-1)1.2.1 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are made to the header manipulation engine. ### [](#fixed-issues-2)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-2-0)1.2.0 **September 12, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Several performance improvements were introduced in this release. ### [](#fixed-issues-3)Fixed Issues - An error occurred causing inbound and outbound headers to be set to lower case, ignoring the user input. ## [](#1-1-1)1.1.1 **July 12, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Several performance improvements were introduced in this release. ## [](#1-1-0)1.1.0 **April 26, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Introduced support for encrypting sensitive information related to the policy. The runtime version must be correctly configured to support encryption. Encryption support was introduced in Mule Runtime v4.2.0. - Several performance improvements were introduced in this release. - Policy weight was reduced. ## [](#1-0-1)1.0.1 **October 4, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-4)Fixed Issues - Policy parameters has an incorrect extra escaping issue. - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. ## [](#1-0-0)1.0.0 **March 23, 2018** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.0** ## [](#see-also)See Also - [Header Injection Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-header-injection) - [Header Removal Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-header-removal) - [Known Issues](https://help.salesforce.com/s/issues) # Header Injection Policy The Header Injection Policy policy adds headers to a request or response. For configuration details, see [Header Injection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-header-injection). ## [](#october-1-2026)October 1, 2026 ### What’s New - Header Injection Policy policy definition version 1.3.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - Header Injection Policy policy implementation version 1.2.2 is now supported by Omni Gateway. - Header Injection Policy policy definition version 1.3.1 is now supported by Omni Gateway. # Header Removal The Header Removal policy removes headers from a request or a response For configuration details, see [Header Removal Policy](https://docs.mulesoft.com/gateway/latest/policies-included-header-removal). ## [](#october-1-2026)October 1, 2026 ### What’s New - Header Removal policy definition version 1.1.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - Header Removal policy implementation version 1.2.1 is now supported by Omni Gateway. - Header Removal policy definition version 1.1.1 is now supported by Omni Gateway. # Header Removal ## [](#1-1-3)1.1.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-1-1)1.1.1 **May 26, 2022** ### [](#fixed-issues)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-1-0)1.1.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-0-3)1.0.3 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Performance improvements are made to the header manipulation engine. ### [](#fixed-issues-2)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). == 1.0.2 **Jul 12, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Several performance improvements were introduced in this release. ## [](#1-0-1)1.0.1 **Apr 26, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Several performance improvements were introduced in this release. ## [](#1-0-0)1.0.0 **Mar 23, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **4.1.0** ## [](#see-also)See Also - [Header Injection Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-header-injection) - [Header Removal Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-header-removal) - [Known Issues](https://help.salesforce.com/s/issues) # Health Check Policy The Health Check Policy policy monitors API upstream health at specific intervals For configuration details, see [Health Check Policy](https://docs.mulesoft.com/gateway/latest/policies-included-health-check). ## [](#february-27-2025)February 27, 2025 ### What’s New - Health Check Policy policy implementation version 1.0.0 is now supported by Omni Gateway. - Health Check Policy policy definition version 1.0.0 is now supported by Omni Gateway. # HL7 EDI Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Hl7 Connector User Guide](https://docs.mulesoft.com/hl7-connector/latest/) ## [](#5-0-0)5.0.0 **October 5, 2026** ### What’s New - HL7 EDI Connector now requires Mule 4.6.24 or later. - The **Enforce Acknowledgment ERR Segment Repeatability** field lets you enforce the repeatability of the Acknowledgment ERR segment. For more information, see the [Configurations section](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-reference#Configurations) of the HL7 EDI Connector Reference. ### Compatibility
Application/Service Version

Mule

4.6.24 and later

OpenJDK

8, 11, and 17

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue Resolution ID

The error location elements now use the correct data types when the connector is configured with a lax acknowledgment schema.

W-16684549
## [](#4-3-0)4.3.0 **December 4, 2025** ### What’s New - The connector can now accept empty arrays for optional repeatable fields in the input payload when writing HL7 messages. For more information, see [HL7 Connector Reference](https://docs.mulesoft.com/hl7-connector/latest/hl7-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
## [](#4-2-12)4.2.12 **January 22, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue Resolution ID

The connector can now read and write subcomponents of subcomponents.

W-14454305
## [](#4-2-11)4.2.11 **July 11, 2023** ### What’s New - The `org.yaml.snakeyaml` library is upgraded to version 2.0 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue Resolution ID

The carriage return and line feed characters are now escaped correctly.

W-13478241, W-13478259
## [](#4-2-10)4.2.10 **October 20, 2022** ### What’s New - The `org.yaml.snakeyaml` library is upgraded to version 1.32 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
## [](#4-2-9)4.2.9 **March 28, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue ID

The connector can now use custom ACK .esl files.

W-10801278
## [](#4-2-8)4.2.8 **March 3, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue ID

Extension segments are now written back into an HL7 message if they are present in the payload map.

W-10671665

The Disable numeric prefixes for data keys configuration field now works as expected for the Write operation when set to false.

W-10581096
## [](#4-2-7)4.2.7 **January 3, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9577
## [](#4-2-6)4.2.6 **December 20, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9577
## [](#4-2-5)4.2.5 **December 1, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue ID

When a segment was reused in an Lax schema, the parser sometimes incorrectly threw a segment out of order error.

SE-23264

When a segment had no position assigned in the schema, the parser sometimes assigned an incorrect position, which caused a segment out of order error.

SE-23264

When a too many segment loops error occurred, the segment and its position were not always accurate.

CONN-9426
## [](#4-2-4)4.2.4 **October 25, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue ID

When subcomponents were present in an element of the varies type, the index of the subcomponent did not reset correctly.

SE-22918

The segment position provided in the Errors list was not always correct.

SE-23050

When the MSH segment contained an error, the parser did not add it to the Errors list.

SE-23050

In some cases, the parser incorrectly added +1 to the Segment Sequence (ELD-02) in the Acknowledgment.

SE-23050

The parse property Fail when a value length is outside an allowed range did not work as expected.

CONN-8933

The parse property Fail when an invalid character is in a value did not work as expected.

CONN-8933

The parse property Fail when there are too many repeats of a value did not work as expected.

CONN-8933

The parse property Fail when an unused segment is included in a message did not work as expected.

CONN-8933

The parse property Fail when there are too many repeats of a segment did not work as expected.

CONN-8933

When an invalid character error was present, the parser duplicated it in the Acknowledgment (ERR).

CONN-8933
## [](#4-2-3)4.2.3 **October 4, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### Fixed Issues
Issue ID

When an element of type varies had a list of components and the first component was empty, the element was skipped and not parsed.

SE-22379

The connector did not report the error when the number of repeated segments or simple elements exceeded the count value.

SE-22794

The parser property Fail when there are too many repeats of a segment did not work as expected. Now the MSA01 (Acknowledgment Code) changes accordingly.

SE-22794
## [](#4-2-2)4.2.2 **July 15, 2021** ### [](#compatibility-13)Compatibility HL7 EDI Connector 4.2.2 is compatible with the following:
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issue)Fixed Issue - The **Write** operation did not generate error details in some cases. (SE-21190) ## [](#4-2-1)4.2.1 **November 12, 2020** ### [](#compatibility-14)Compatibility HL7 EDI Connector 4.2.1 is compatible with the following:
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issue-2)Fixed Issue - In certain error cases, the specific error was not displayed. (SE-18505) - An incorrect error message was generated when there was a field that contained a `~` character. (SE-18506) ## [](#4-2-0)4.2.0 **October 15, 2020** ### [](#compatibility-15)Compatibility HL7 EDI Connector v4.2.0 is compatible with the following:
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#features)Features - Added segment terminator character configuration support. Supported values: '\\r' (CR) (default) and '\\n' (LF) ## [](#4-1-1)4.1.1 **May 4, 2020** ### [](#compatibility-16)Compatibility HL7 EDI Connector v4.1.0 is compatible with the following:
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issue-3)Fixed Issue - When (~) arrays were sent with null values, the connector parser skipped the rest of the file. (SE-15176). - Upgraded Scala to version 2.12.10 - Upgraded Log4j to version 2.11.0 ## [](#4-1-0)4.1.0 **April 14, 2020** ### [](#compatibility-17)Compatibility HL7 EDI Connector v4.1.0 is compatible with the following:
Application/Service Version

Mule

4.1.1 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issue-4)Fixed Issue - Added support for repeated values in extensions segments (Z\* segments). (SE-15044) - Corrected parser handling of repeated values where some repeats are empty. (SE-15176) ## [](#4-0-4)4.0.4 **February 13, 2020** ### [](#compatibility-18)Compatibility HL7 EDI Connector v4.0.4 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issue-5)Fixed Issue - Incompatibilities with JRE 11 have been fixed. (SE-14449). ## [](#4-0-3)4.0.3 **December 14, 2019** ### [](#compatibility-19)Compatibility HL7 EDI Connector v4.0.3 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issues-11)Fixed Issues - Corrected the handling of eventMessageMap paths with a leading '/' character, as it was not found on the classpath. (SE-13668) - Corrected the MSH handling for versions 2.2 and 2.3 which resulted in the error: "com.mulesoft.flatfile.lexical.LexicalException: No message structure found in eventMessageMap for message null/null". (SE-13668) - All standard schemas now use a minimum length of 0 for simple values, rather than 1. Using a 1 caused empty strings to be padded with a blank when written to the output. (SE-12757) - Corrected the `ORU_R01` schema structure definition in version 2.4, as this was unusable due to repeated definitions. (SE-11806) The `hl7-simplify-4.0.2.jar` execution was not working properly. (SE-14016) ### [](#known-issues)Known Issues Schemas are present for message structures for older versions (up to and including 2.3.1) that are not used in HL7. HL7 reuses message structures for different event types. For example, there is no `ADT_A08` message structure because this is a combination of an ADT message type for `A08` event reuses the `ADT_A01` message structures. This issue is considered of low severity because it does not result in any errors in either sending or receiving data, but may mislead the user to set an incorrect message structure name for the `MSH.9/MSG.3` "message structure" field of the header. It is left as a known issue so as to avoid breaking existing applications. ## [](#4-0-2)4.0.2 **December 14, 2018** ### [](#compatibility-20)Compatibility HL7 EDI Connector v4.0.2 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issues-12)Fixed Issues - Corrected DataSense metadata. Removed the "Heading" level shown in DataSense that was not actually used in data. - Added support for all standard escape sequences. However escape sequences that change character encoding are not supported. - Fixed writing a String value to a timestamp field. By default this expects XMLGregorianCalendar, but a correctly formatted String is also supported. - Corrected handling of MSH-18 character encoding field, allowing either a simple String or a list of Strings, depending on the schema version. ## [](#4-0-1)4.0.1 **August 30, 2018** ### [](#compatibility-21)Compatibility HL7 EDI Connector v4.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

HL7

v2.1, v2.2, v2.3.1, v2.3, v2.4, v2.5, v2.5.1, v2.6, 2.7, 2.7.1, 2.8, 2.8.1
### [](#fixed-issues-13)Fixed Issues - Added delimiter character configuration support - Corrected writer to use delimiters from configuration if not supplied in write data map - Fixed issue with write exceptions being lost - Corrected ACK schema to use list for repeating composite values where appropriate. ### [](#known-issues-2)Known Issues - HL7 EDI Connector doesn’t support Design Center. ## [](#4-0-0)4.0.0 **January 31, 2018** This release adapts HL7 for use with Mule 4 and Studio 7. ### [](#known-issues-3)Known Issues - Setting default delimiter characters for writing is not supported in the configuration. You can set the delimiters in the output data. - Anypoint Studio requires more memory than allowed by the default settings to support HL7 schema definitions. See the Connector Guide for details on changing the Studio memory settings. - HL7 EDI Connector doesn’t support Design Center. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # HL7 MLLP Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) The Mule HL7 MLLP connector provides connectivity and parsing functionality for MLLP messages. Guide: [HL7 MLLP Connector Guide](https://docs.mulesoft.com/jp/hl7-mllp-connector/latest/) Reference: [HL7 MLLP Connector Reference](https://docs.mulesoft.com/jp/hl7-mllp-connector/latest/hl7-mllp-connector-reference) ## [](#2-2-4)2.2.4 **Aug 18, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Fixed an intermittent issue with a broken pipe in the HL7 MLLP requester when using a connection pool with reconnection.

W-22903021
## [](#2-2-3)2.2.3 **July 26, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

An intermittent race condition in the HL7 MLLP listener no longer interferes with message reading.

W-23563951
## [](#2-2-2)2.2.2 **February 26, 2026** ### What’s New - This connector is now FIPS 140-3 compliant. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-2-1)2.2.1 **August 28, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The MLLP Listener now closes the connections when exceptions are thrown due to network-related issues.

W-18283925
## [](#2-2-0)2.2.0 **October 16, 2024** ### What’s New - The connector now validates the TLS protocols that are configured to address security vulnerabilities and throws a security exception for protocols that aren’t supported. For more information, see the **Throws** section on the [HL7 MLLP Connector Reference](https://docs.mulesoft.com/jp/hl7-mllp-connector/latest/hl7-mllp-connector-reference) page. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The MLLP Listener now responds as expected to requests and no longer hangs when the incoming payload isn’t consumed.

W-16822060
## [](#2-1-6)2.1.6 **January 24, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-1-5)2.1.5 **April 1, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The Send operation now uses the standard (4 kb) chunk size.

W-10935871
## [](#2-1-4)2.1.4 **November 12, 2020** ### [](#compatibility-8)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features)Features Improved logs for debug and trace modes by adding more troubleshooting information at the byte level for inbound and outbound messages and for the state of the MLLP Listener. (CONN-7220) ### [](#fixed-issues-6)Fixed Issues Automatic restart is now enabled when the Listener throws errors. This fixes the issue that caused the Listener to not accept new connections after throwing errors. (SE-17603) ## [](#2-1-3)2.1.3 **May 18, 2020** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-7)Fixed Issues - Improved debug level logging to provide more detail. (SE-15711) ## [](#2-1-2)2.1.2 **December 12, 2019** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-8)Fixed Issues - Fixed the reconnection strategy implementation for outbound connections (SE-13271) - Changed to transmitting data as bytes to avoid any issues with character encoding (SE-13928) ## [](#2-1-1)2.1.1 **November 13, 2019** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-9)Fixed Issues TLS handling is fixed so that client authentication is optional and only used if a truststore is supplied. (SE-12545). ## [](#2-1-0)2.1.0 **February 11, 2019** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features-2)Features Source configuration allows specifying a connection count, and limiting the number of simultaneous connections to the supplied value. If not configured, the default behavior is to allow any number of simultaneous connections. ### [](#fixed-issues-10)Fixed Issues Closing a connection to the source caused an empty message to be sent through the flow, generally resulting in an exception. ## [](#2-0-4)2.0.4 **January 11, 2019** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features-3)Features The start-of-block character is now configurable. ### [](#fixed-issues-11)Fixed Issues - The end-of-block character was incorrectly marked as required. It is now optional. - Under certain scenarios, all messages received after the first one would fail, with the error message `Message does not start with 'MSH'`. This was fixed. ## [](#2-0-3)2.0.3 **November 16, 2018** This update fixes an response issue, and adds the new **sendAndReceive** operation. ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-12)Fixed Issues Mule 4 HL7 MLLP Connector does not wait for a response after sending a message out. Added new operation sendAndReceive. ## [](#2-0-2)2.0.2 **October 1, 2018** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-13)Fixed Issues Depending on the way messages were sent to the connector, it would stop receiving requests after the first one. This was fixed. ## [](#2-0-1)2.0.1 **September 20, 2018** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-14)Fixed Issues ACK like messages weren’t flowing back to sender. ## [](#2-0-0)2.0.0 **June 18, 2018** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features-4)Features - Receive Message - The HL7 MLLP connector provides the functionality to receive MLLP messages. - Send Message - The HL7 MLLP connector provides the functionality to send MLLP messages. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # HTTP and HTTPs Proxies ## [](#2-1-1)2.1.1 **October 24, 2024** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### What’s New - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.10.1. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#2-1-0)2.1.0 **February 7, 2024** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements)New Features and Enhancements - This proxy version is now compatible with Java 17. - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, is now upgraded to version 1.9.0. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#2-0-5)2.0.5 **November 17, 2022** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-2)New Features and Enhancements - HTTP Connector upgraded from version 1.6.0 to version 1.7.2. ## [](#2-0-4)2.0.4 **June 1, 2022** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues)Fixed Issues - Performing a POST request when the implementation times out no longer causes the original payload to be returned in the response. ## [](#2-0-3)2.0.3 **December 7, 2021** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-3)New Features and Enhancements - HTTP Connector upgraded from version 1.5.17 to version 1.6.0. ## [](#2-0-2)2.0.2 **April 6, 2021** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-2)Fixed Issues - Implementation path does not include a trailing slash when it is not explicitly called for. (SE-19062) ## [](#2-0-1)2.0.1 **August 12, 2020** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-3)Fixed Issues - When no cipher suite is selected for the TLS configuration in Secret Manager, the proxy is generated with `enabledCipherSuites=""`. This issue caused all requests to fail. (SE-15303) ## [](#2-0-0)2.0.0 **Apr 30, 2020** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-4)New Features and Enhancements - HTTP Connector upgraded from version 1.5.7 to version 1.5.17. - Several performance improvements introduced. - Added annotation to [ignore base path](#api-manager::configure-uri-template-regex.adoc#when-to-use-ignoringbasepath) when applying Resource-Level policies. ## [](#1-1-4)1.1.4 **Apr 30, 2020** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-5)New Features and Enhancements - HTTP Connector upgraded from version 1.5.7 to version 1.5.17. - Several performance improvements introduced. ## [](#1-1-3)1.1.3 **Sep 3, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-6)New Features and Enhancements - HTTP Connector upgraded from version 1.4.0 to version 1.5.7. ### [](#fixed-issues-4)Fixed Issues - Proxies no longer handle cookies by default. To re-enable proxies, you must import the proxy application to Anypoint Studio, and then modify the HTTP Request configuration. From **HTTP Request Configuration** > **Settings**, select the **Enable cookies** check box to access this feature. ## [](#1-1-2)1.1.2 **Nov 1, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Mule Maven Plugin upgraded from version 3.1.2 to version 3.2.0. - HTTP Connector upgraded from version 1.1.1 to version 1.4.0. - Improved DataWeave expression to handle implementation URLs ending with "/". ## [](#1-1-1)1.1.1 **May 14, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-8)New Features and Enhancements - Proxy is refactored so that it can be easily imported using MuleSoft Anypoint Studio. - Mule Maven Plugin upgraded from version 3.1.0 to version 3.1.2. - Light-weight proxies are introduced. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-13)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-9)New Features and Enhancements - Properties are parametrization and poperty names are normalized. - HTTPs request updated to include Keystore when making requests. ## [](#1-0-0)1.0.0 **Nov 16, 2017** Initial release ### [](#minimum-mule-version-14)Minimum Mule Version **Mule 4.0.0** ## [](#see-also)See Also - [HTTP Connector release notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http) - [Known Issues](https://help.salesforce.com/s/issues) # HTTP caching The HTTP caching policy caches HTTP responses from an API implementation. For configuration details, see [HTTP Caching Policy](https://docs.mulesoft.com/gateway/latest/policies-included-http-caching). ## [](#october-1-2026)October 1, 2026 ### What’s New - HTTP caching policy definition version 1.1.2 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - HTTP caching policy implementation version 1.2.2 is now supported by Omni Gateway. - HTTP caching policy definition version 1.1.0 is now supported by Omni Gateway. # HTTP Caching ## [](#1-1-2)1.1.2 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-1-1)1.1.1 **October 3, 2025** ### What’s New - Added metadata for using policies in Agent Fabric. ## [](#1-1-0)1.1.0 **July 29, 2022** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#0-9-0)0.9.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - Flex support for the Policy. ## [](#1-0-5)1.0.5 **November 10, 2021** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed issues - Fixed an issue where an authentication object was incorrectly cached. ## [](#1-0-4)1.0.4 **November 20, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-2)Fixed issues - When upgrading CloudHub Runtime version, policies that have the persistent cache enabled failed to deserialize elements. ## [](#1-0-3)1.0.3 **Apr 30, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-3)Fixed issues - A `ClassCastException` error occurred when another policy added a response header to the payload. This issue is now resolved. ## [](#1-0-2)1.0.2 **September 12, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **4.1.0** ### [](#fixed-issues-4)Fixed Issues - An Object Store repeatedly fails to store an event, resulting in a stack overflow. ## [](#1-0-1)1.0.1 **April 26, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.0** ### [](#fixed-issues-5)Fixed Issues - Previous version incompatible with Mule Runtime 4.2.0 and greater. - An error occurred when internal parameters were serialized. This is because these parameters are not serializable. - During a cache hit, the loaded event was using the old context, such as event Id and correlation Id), resulting in failed error handling and feedback loop. ### [](#known-issues)Known Issues - Upgrading from a previous policy version invalidates the existing cache. ## [](#1-0-0-deprecated)1.0.0 - Deprecated **July 03, 2018** ### [](#compatibility)Compatibility - v1.0.0 is compatible with v4.1.x and not compatible with v4.2.0 and greater of Mule Runtime. ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.0** ## [](#see-also)See Also - [Http Caching Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-http-caching) - [Known Issues](https://help.salesforce.com/s/issues) # HTTP Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for HTTP (HTTP Connector) enables you to declare HTTP servers that listen to requests and trigger flows, as well as HTTP clients that can communicate with any HTTP service. Guide: [HTTP Connector User Guide](https://docs.mulesoft.com/http-connector/latest/) ## [](#1-12-1)1.12.1 **August 18, 2026** ### Fixed Issues
Issue Resolution ID

The plugins used for packaging the connector are updated to generate complete and accurate metadata at build time.

W-23815437
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-12-0)1.12.0 **August 4, 2026** ### What’s New - The connector now reports a validation warning at deployment time when an `http:listener-config` is declared but isn’t referenced by any **Listener**, helping you detect orphaned listener configurations. ### Fixed Issues
Issue Resolution ID

The Response Timeout and the connection pool acquisition timeout no longer conflict.

W-23131874

HTTP request URL validation at deployment time no longer produces false warnings when the request path or URL is set using a property placeholder.

W-23049232

Carriage return and line feed (CR/LF) characters in HTTP header values are now sanitized instead of causing the message to be rejected.

W-22252135

Requests canceled because the graceful shutdown period expired now return an HTTP 503 (Service Unavailable) response instead of an HTTP 500 (Internal Server Error) response.

W-21580619

The HTTP Connector proxy configuration no longer logs unnecessary WARN messages on Mule 4.9 and earlier runtime versions.

W-21948326

The Grizzly library is upgraded to 2.3.36-MULE-031.

W-21337433

The Sockets Connector dependency is upgraded to 1.2.9.

W-21770069
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-11-3)1.11.3 **May 14, 2026** ### What’s New - The release 1.11.3 addresses a regression introduced in release 1.11.2, and includes all fixes from that release. ### Fixed Issues
Issue Resolution ID

Build failures caused by an incorrectly published pom.xml in Exchange for HTTP Connector 1.11.2 are now fixed. The malformed POM caused the mule-maven-plugin to incorrectly resolve dependencies, resulting in the package org.mule.extension.socket.api.socket.tcp being exported by both the HTTP and Sockets connectors.

W-22489693
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-11-2-deprecated)1.11.2 (Deprecated) **May 12, 2026** ### Fixed Issues
Issue Resolution ID

The plugins used for packaging are updated to fix a connector metadata generation issue related to Java 17 compatibility.

W-20903962
### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-11-1)1.11.1 **January 15, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Spring dependencies are now removed from HTTP Connector and are only present in internal test modules.

W-19774918

A potential NullPointerException error that occurred during Abstract Syntax Tree (AST) validations at deployment time is now resolved, ensuring more stable application deployments.

W-20064897

The HTTP Connector Listener operation now correctly enforces the protocol version setting. Previously, a configuration set to HTTP/1 only incorrectly allowed incoming HTTP/2 connections.

W-19889726

HTTP Connector no longer adds erroneous Transfer-Encoding headers to HTTP/2 responses.

W-19845365
## [](#1-11-0)1.11.0 **October 3, 2025** ### What’s New - The connector supports HTTP/2 (experimental in Mule runtime 4.10.0 and subject to change), enabling faster and more efficient HTTP communication. See [HTTP/2 Support](https://docs.mulesoft.com/http-connector/latest/http-2-support). ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-10-6)1.10.6 **September 30th, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now avoids unnecessary internal thread jumps when handling small payloads.

W-19545477

Request headers are now injected correctly for Visualizer.

W-19564419

Internal dependencies are upgraded.

W-19772921
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # HTTP Service Release Notes - Mule 4 Support Category: Select ## [](#1-7-15)1.7.15 **September 18, 2023** ### Compatibility
Software Version

Mule

4.4.0-20230918
### Fixed Issues
Issue Resolution ID

requestBuilders no longer leaks after response is received.

W-13754230
## [](#1-7-14)1.7.14 **August 22, 2023** ### Compatibility
Software Version

Mule

4.4.0-20230822
### Fixed Issues
Issue Resolution ID

The 'Expect: 100-Continue' header is now ignored in server responses and log warnings.

W-13806048

Pipe timeout default value is now increased to 20 seconds.

W-13821717
## [](#1-7-13)1.7.13 **June 16, 2023** ### Compatibility
Software Version

Mule

4.4.0-20230616
### Fixed Issues
Issue Resolution ID

The POST request body is no longer sent in a GET redirect.

W-12594415
## [](#1-7-12)1.7.12 **March 20, 2023** ### Compatibility
Software Version

Mule

4.4.0-20230320
### Fixed Issues
Issue Resolution ID

NullPointerException no longer occurs when adding a null value to the cookie header.

W-12666590
## [](#1-7-11)1.7.11 **February 17, 2023** ### Compatibility
Software Version

Mule

4.4.0-20230217
### Fixed Issues
Issue Resolution ID

Requests no longer fail with NullPointerException with applications using invalid cookies.

W-12528819
## [](#1-7-10)1.7.10 **January 23, 2023** ### Compatibility
Software Version

Mule

4.4.0-20230123
### Fixed Issues
Issue Resolution ID

The log level for HTTP response stream was closed before being read but response streams must always be consumed was changed from WARNING to ERROR.

W-12173136

Cookie headers are now correctly aggregated during the redirect mechanism.

W-12161504
## [](#1-7-9)1.7.9 **September 19, 2022** ### Compatibility
Software Version

Mule

4.4.0-20220919
### Fixed Issues
Issue Resolution ID

HTTP wire logging now provides the complete context of the request and response for 413 and 414 scenarios.

W-11410315
## [](#1-7-8)1.7.8 **July 18, 2022** ### Compatibility
Software Version

Mule

4.4.0-20220718
### Fixed Issues
Issue Resolution ID

HTTP_Request_configuration in Anypoint Connector for HTTP now honors proxy settings.

W-10863931
## [](#1-7-7)1.7.7 **May 23, 2022** ### Compatibility
Software Version

Mule

4.4.0-20220523
### Fixed Issues
Issue Resolution ID

The NullPointerException error no longer appears while refreshing an OAuth token.

W-11085107
## [](#1-7-6)1.7.6 **March 21, 2022** ### Compatibility
Software Version

Mule

4.4.0-20220321
### Fixed Issues
Issue Resolution ID

HTTP Connector no longer fails to send multipart/form-data.

W-10711033

The redirect implementation properly handles the "Preserve Header Case" configuration.

W-10822777
## [](#1-7-5)1.7.5 **February 21, 2022** ### Compatibility
Software Version

Mule

4.4.0-20220221
### Fixed Issues
Issue Resolution ID

The HTTP proxy path is now optimized.

EE-8118

Set-Cookie is now handled correctly after a redirect request.

MULE-19942
## [](#1-7-4)1.7.4 **January 24, 2022** ### Compatibility
Software Version

Mule

4.4.0-20211018
### Fixed Issues
Issue ID

Added new HTTP service system properties to set maximum sizes for HTTP request and response headers.

MULE-19837
## [](#1-6-18)1.6.18 **December 17, 2021** ### Compatibility
Software Version

Mule

4.3.0
### Fixed Issues
Issue ID

Added new HTTP service system properties to set maximum sizes for HTTP request and response headers.

MULE-19837
## [](#1-7-3)1.7.3 **December 01, 2021** ### Compatibility
Software Version

Mule

4.4.0-20211018
### Fixed Issues
Issue ID

Improved the error message shown when a Mule application attempts to read an HTTP request payload after sending its corresponding HTTP response.

MULE-19951
## [](#1-6-17)1.6.17 **December 01, 2021** ### Compatibility
Software Version

Mule

4.3.0
### Fixed Issues
Issue ID

Improved the error message shown when a Mule application attempts to read an HTTP request payload after sending its corresponding HTTP response.

MULE-19951
## [](#1-7-2)1.7.2 **November 05, 2021** ### Compatibility
Software Version

Mule

4.4.0-20211018
### Fixed Issues
Issue ID

Added a queue to the requester’s scheduler of the Grizzly client.

MULE-19774

Query parameters in a redirect URI are properly set.

MULE-19908
## [](#1-6-16)1.6.16 **November 05, 2021** ### Compatibility
Software Version

Mule

4.3.0
### Fixed Issues
Issue ID

Query parameters in a redirect URI are properly set.

MULE-19908
## [](#1-6-15)1.6.15 **October 26, 2021** ### Compatibility
Software Version

Mule

4.3.0
### Fixed Issues
Issue ID

NullPointerException errors no longer cause a decrease in performance when a Mule app uses FTP/FTPS read operations.

MULE-19727

Improved handling of HTTP redirects.

MULE-19830

Optimized graceful shutdown timeout.

MULE-19817

Added a queue to the requester’s scheduler of the Grizzly client.

MULE-19774
## [](#1-7-1)1.7.1 **October 19, 2021** ### Compatibility
Software Version

Mule

4.4.0-20211018
### Fixed Issues
Issue ID

Improved handling of HTTP redirects.

MULE-19830

Optimized graceful shutdown timeout.

MULE-19817

Added support for the new read timeout feature of the HTTP Listener operation.

MULE-19779
## [](#1-7-0)1.7.0 **September 21, 2021** ### Compatibility
Software Version

Mule

4.3.0
### Fixed Issues
Issue ID

NullPointerException errors no longer cause a decrease in performance when a Mule app uses FTP/FTPS read operations.

MULE-19727
## [](#1-6-14)1.6.14 **August 9, 2021** ### [](#mule-version)Mule Version **Mule 4.3.0** ### [](#fixed-issues-21)Fixed Issues - Fixed an issue closing the connection in case of timeout due to a payload not being sent (content-length > 0 and payload not sent) (MULE-19691) ## [](#1-6-13)1.6.13 **August 5, 2021** ### [](#mule-version-2)Mule Version **Mule 4.3.0** ### [](#fixed-issues-22)Fixed Issues - Fixed an issue that prevented HTTP Service from properly handling redirect requests (MULE-19622)
Install the patch found in the following link to avoid a known issue in this version: MULE-18343.
## [](#1-6-12)1.6.12 **July 26, 2021** ### [](#mule-version-3)Mule Version **Mule 4.3.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Updated `commons-io` to 2.11.0 and removed `guava` dependency. (EE-7932)
Install the patch found in the following link to avoid a known issue in this version: MULE-18343.
## [](#1-6-11)1.6.11 **May 31, 2021** ### [](#mule-version-4)Mule Version **Mule 4.3.0** ### [](#fixed-issues-23)Fixed Issues - Fixed the exception `NumberFormatException` when streaming is activated and the response has a length greater than the maximum integer value. (MULE-19334) ### [](#new-features-and-enhancements-2)New Features and Enhancements - Request handlers now use the creation class loader. (MULE-19181) - HTTP Wire logging now preserves the MDC (Mapped Diagnostic Context). (MULE-19243) - Added a new timeout to the Java read operation of a pipe used by the HTTP client to stream responses. (MULE-19232) **NOTE**: Install the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-10)1.6.10 **February 8, 2021** ### [](#mule-version-5)Mule Version **Mule 4.3.0** ### [](#fixed-issues-24)Fixed Issues - Fixed a race condition in which requester threads were getting stuck while streaming responses. (MULE-19208) ### [](#new-features-and-enhancements-3)New Features and Enhancements - The HTTP Requester pool used to stream responses now has a configurable queue size that you can disable. (MULE-19136) **NOTE**: You must install the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-9)1.6.9 **February 4, 2021** ### [](#mule-version-6)Mule Version **Mule 4.3.0** ### [](#fixed-issue)Fixed Issue - High CPU usage with HTTPS due to endless loop for requests. (MULE-19179) ## [](#1-6-8)1.6.8 **January 11, 2021** ### [](#mule-version-7)Mule Version **Mule 4.3.0** ### [](#fixed-issues-25)Fixed Issues - HTTP Client async operations now preserve class loader. (MULE-19099) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-5-14)1.5.14 **January 11, 2021** ### [](#mule-version-8)Mule Version **Mule 4.2.2** ### [](#fixed-issues-26)Fixed Issues - HTTP Client async operations now preserve class loader. (MULE-19099) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-7)1.6.7 **January 5, 2021** ### [](#mule-version-9)Mule Version **Mule 4.3.0** ### [](#fixed-issues-27)Fixed Issues - Fixed a regression in HTTP Service where an unexpected error was thrown on a SoapFault. (MULE-19111) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-5-13)1.5.13 **January 5, 2021** ### [](#mule-version-10)Mule Version **Mule 4.2.2** ### [](#fixed-issues-28)Fixed Issues - Fixed a regression in HTTP Service where an unexpected error was thrown on a SoapFault. (MULE-19111) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-6)1.6.6 **December 23, 2020** ### [](#mule-version-11)Mule Version **Mule 4.3.0** ### [](#fixed-issues-29)Fixed Issues - Fixed a deadlock when streaming responses in proxy scenarios by using a dedicated thread-pool. (MULE-19072) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-5)1.6.5 **December 9, 2020** ### [](#mule-version-12)Mule Version **Mule 4.3.0** ### [](#fixed-issues-30)Fixed Issues - The keep-alive header connection isn’t shown. (MULE-13973) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-5-11)1.5.11 **December 3, 2020** ### [](#mule-version-13)Mule Version **Mule 4.2.2** ### [](#fixed-issues-31)Fixed Issues - The keep-alive header connection isn’t shown. (MULE-13973) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-4)1.6.4 **December 1, 2020** ### [](#mule-version-14)Mule Version **Mule 4.3.0** ### [](#fixed-issues-32)Fixed Issues - Fixed a grizzly memory leak related with the SSLEngine. (MULE-18790) - Avoid adding 'Content-length: 0' header for HTTP Methods with undefined body semantic (GET, HEAD, and DELETE). (MULE-19019) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-5-10)1.5.10 **December 1, 2020** ### [](#mule-version-15)Mule Version **Mule 4.2.2** ### [](#fixed-issues-33)Fixed Issues - Fixed a grizzly memory leak related with the SSLEngine. (MULE-18790) - Avoid adding 'Content-length: 0' header for HTTP Methods with undefined body semantic (GET, HEAD, and DELETE). (MULE-19019) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-3)1.6.3 **October 6, 2020** ### [](#mule-version-16)Mule Version **Mule 4.3.0** ### [](#fixed-issues-34)Fixed Issues - Fixed a GrizzlyHttpServer memory leak on multiple redeploys. (MULE-18816) ### [](#new-features-and-enhancements-4)New Features and Enhancements - The start and stop methods of the GrizzlyHttpServer now log the host:port pair in INFO level. (MULE-18819) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-5-9)1.5.9 **October 6, 2020** ### [](#mule-version-17)Mule Version **Mule 4.2.2** ### [](#fixed-issues-35)Fixed Issues - Fixed a GrizzlyHttpServer memory leak on multiple redeploys. (MULE-18816) ### [](#new-features-and-enhancements-5)New Features and Enhancements - The start and stop methods of the GrizzlyHttpServer now log the host:port pair in INFO level. (MULE-18819) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-4-16)1.4.16 **October 6, 2020** ### [](#mule-version-18)Mule Version **Mule 4.2.1** ### [](#fixed-issues-36)Fixed Issues - Fixed a GrizzlyHttpServer memory leak on multiple redeploys. (MULE-18816) ### [](#new-features-and-enhancements-6)New Features and Enhancements - The start and stop methods of the GrizzlyHttpServer now log the host:port pair in INFO level. (MULE-18819) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-2)1.6.2 **July 24, 2020** ### [](#mule-version-19)Mule Version **Mule 4.3.0** ### [](#fixed-issues-37)Fixed Issues - Fixed an issue where Grizzly returns incorrect error codes with a long header request and a long URI request. (MULE-18455) - Fixed an issue where NTLM dance doesn’t finish when a renegotiation is triggered. (MULE-18591) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-5-8)1.5.8 **July 24, 2020** ### [](#mule-version-20)Mule Version **Mule 4.2.2** ### [](#fixed-issues-38)Fixed Issues - Fixed an issue where Grizzly returns incorrect error codes with a long header request and a long URI request. (MULE-18455) - Fixed issue where NTLM dance doesn’t finish when a renegotiation is triggered. (MULE-18591) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-4-15)1.4.15 **July 24, 2020** ### [](#mule-version-21)Mule Version **Mule 4.2.1** ### [](#fixed-issues-39)Fixed Issues - Fixed an issue where Grizzly returns incorrect error codes with a long header request and a long URI request. (MULE-18455) - Fixed an issue where NTLM dance doesn’t finish when a renegotiation is triggered. (MULE-18591) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-6-1)1.6.1 **June 1, 2020** ### [](#mule-version-22)Mule Version **Mule 4.3.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Use the graceful shutdown timeout to allow persistent connections to do a last request. (MULE-18396) - Add a tolerance time to use selectors for response streaming. (MULE-18028) ### [](#fixed-issues-40)Fixed Issues - Fixed issue where source is not notified of failure on ConnectionException in flow. (MULE-18343) - Encoded slash (%2F) is considered as part of URI in HTTP Service. (MULE-18308) - Fixed issue that generates a timeout in an HTTP request sent by several connectors. (MULE-18320) - Fixed issue that might cause a leak in HTTP requests. (MULE-18293) - Fixed issue where HTTP Service logs were in the wrong appender when using streaming (MULE-18185) - Fixed an issue when handling errors related to the loss of the client connection. (MULE-18191) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-2-8)1.2.8 **May 22, 2020** ### [](#mule-version-23)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-8)New Features and Enhancements - None. ### [](#fixed-issues-41)Fixed Issues - Fixed an issue that generates a timeout in an HTTP request that was sent by several connectors. (MULE-18320) - Fixed an issue that might cause a leak in HTTP requests. (MULE-18293) ## [](#1-5-7)1.5.7 **May 14, 2020** ### [](#mule-version-24)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-9)New Features and Enhancements - Use the graceful shutdown timeout to allow persistent connections to do a last request. (MULE-18396) ### [](#fixed-issues-42)Fixed Issues - Encoded slash (%2F) is being considered as part of URI in http service. (MULE-18308) - Source is not notified of failure on ConnectionException in flow. (MULE-18343) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-4-14)1.4.14 **May 14, 2020** ### [](#mule-version-25)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-10)New Features and Enhancements - Use the graceful shutdown timeout to allow persistent connections to do a last request. (MULE-18396) ### [](#fixed-issues-43)Fixed Issues - Encoded slash (%2F) is being considered as part of URI in http service. (MULE-18308) - Source is not notified of failure on ConnectionException in flow. (MULE-18343) **NOTE**: We need the following patch to avoid a known issue in this version: MULE-18343. ## [](#1-5-6)1.5.6 **April 17, 2020** ### [](#mule-version-26)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-11)New Features and Enhancements - None. ### [](#fixed-issues-44)Fixed Issues - Fixed an issue that generates a timeout in an HTTP request that was sent by several connectors. (MULE-18320) ## [](#1-4-13)1.4.13 **April 17, 2020** ### [](#mule-version-27)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-12)New Features and Enhancements - None. ### [](#fixed-issues-45)Fixed Issues - Fixed an issue that generates a timeout in an HTTP request that was sent by several connectors. (MULE-18320) ## [](#1-5-5)1.5.5 **April 13, 2020** ### [](#mule-version-28)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-13)New Features and Enhancements - None. ### [](#fixed-issues-46)Fixed Issues - Fixed an issue that might cause a leak in HTTP requests. (MULE-18293) ## [](#1-4-12)1.4.12 **April 13, 2020** ### [](#mule-version-29)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-14)New Features and Enhancements - Add a tolerance time to use selectors for response streaming (MULE-18028) ### [](#fixed-issues-47)Fixed Issues - Fixed an issue that might cause a leak in HTTP requests. (MULE-18293) - HTTP Service logs were in the wrong appender when using streaming (MULE-18185) ## [](#1-2-7)1.2.7 **April 9, 2020** ### [](#mule-version-30)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-15)New Features and Enhancements - None. ### [](#fixed-issues-48)Fixed Issues - The memory footprint of the closed TCPNIOConnection objects issue is fixed. (MULE-17887) ## [](#1-5-4)1.5.4 **April 1, 2020** ### [](#mule-version-31)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-16)New Features and Enhancements - Add a tolerance time to use selectors for response streaming (MULE-18028) ### [](#fixed-issues-49)Fixed Issues - HTTP Service logs were in the wrong appender when using streaming (MULE-18185) ## [](#1-2-6)1.2.6 **March 27, 2020** ### [](#mule-version-32)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-17)New Features and Enhancements - None. ### [](#fixed-issues-50)Fixed Issues - Fixed an issue that occurred when handling errors related to the loss of the client connection. (MULE-18191) ## [](#1-5-3)1.5.3 **March 25, 2020** ### [](#mule-version-33)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-18)New Features and Enhancements - None. ### [](#fixed-issues-51)Fixed Issues - Fixed an issue that occurred when handling errors related to the loss of the client connection. (MULE-18191) ## [](#1-4-11)1.4.11 **March 25, 2020** ### [](#mule-version-34)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-19)New Features and Enhancements - None. ### [](#fixed-issues-52)Fixed Issues - Fixed an issue that occurred when handling errors related to the loss of the client connection. (MULE-18191) ## [](#1-5-2)1.5.2 **February 17, 2020** ### [](#mule-version-35)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-20)New Features and Enhancements - None. ### [](#fixed-issues-53)Fixed Issues - Fixed an issue that resulted in the loss of the HTTP payload in the NTLM dance. (MULE-18057) ## [](#1-4-10)1.4.10 **February 17, 2020** ### [](#mule-version-36)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-21)New Features and Enhancements - None. ### [](#fixed-issues-54)Fixed Issues - Fixed an issue which resulted in the loss of the HTTP payload in the NTLM dance. (MULE-18057) ## [](#1-5-1)1.5.1 **February 12, 2020** ### [](#mule-version-37)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-22)New Features and Enhancements - None. ### [](#fixed-issues-55)Fixed Issues - Fixed corrupted payload issue that occurred with large request bodies when `http.requestStreaming.enabled` property was set. (MULE-18052) ## [](#1-4-9)1.4.9 **February 12, 2020** ### [](#mule-version-38)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-23)New Features and Enhancements - None. ### [](#fixed-issues-56)Fixed Issues - Fixed corrupted payload issue that occurred with large request bodies when `http.requestStreaming.enabled` property was set. (MULE-18052) ## [](#1-2-5)1.2.5 **January 24, 2020** ### [](#mule-version-39)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-24)New Features and Enhancements - None. ### [](#fixed-issues-57)Fixed Issues - The `onErrorSendingResponse` public method in the anonymous class is not accessible via reflection. (MULE-17693) - Added a debug log in HTTP server with `ip:port` where it is listening. (MULE-17473) - When a non-supported `cipherSuite` is set, Grizzly ignores restriction after first request. (MULE-16852) ## [](#1-4-8)1.4.8 **January 13, 2020** ### [](#mule-version-40)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-25)New Features and Enhancements - None. ### [](#fixed-issues-58)Fixed Issues - Fixed the MDC propagation issue that occurred when a callback was called in a different thread. (MULE-17907) - The memory footprint of the closed TCPNIOConnection objects issue is fixed. (MULE-17887) - Persistent connections are now closed when the HTTP listener is stopped. (MULE-17851) ## [](#1-5-0)1.5.0 **October 30, 2019** ### [](#mule-version-41)Mule Version **Mule 4.2.2** ### [](#new-features-and-enhancements-26)New Features and Enhancements - Websockets capabilities. ### [](#fixed-issues-59)Fixed Issues - None ## [](#1-4-7)1.4.7 **October 9, 2019** ### [](#mule-version-42)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-27)New Features and Enhancements - None. ### [](#fixed-issues-60)Fixed Issues - Upgrade Java Mail version. (MULE-16389) - HTTP Server lookup does not support domains. (MULE-17450) - Add a debug log in HTTP server with `ip:port` where it is listening. (MULE-17473) - HTTP Requester can’t handle large headers in Mule 4. (MULE-17480) ## [](#1-4-6)1.4.6 **September 17, 2019** ### [](#mule-version-43)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-28)New Features and Enhancements - None. ### [](#fixed-issues-61)Fixed Issues - Upgrade grizzly-ahc version to 1.14-MULE-012 (MULE-17428) ## [](#1-4-5)1.4.5 **This release does not contain any extra feature or bug fixes and is not used by the Mule Runtime** ## [](#1-4-4)1.4.4 **August 20, 2019** ### [](#mule-version-44)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-29)New Features and Enhancements - None. ### [](#fixed-issues-62)Fixed Issues - NTLM authentication with dynamic credentials is successful despite credentials changes. (MULE-17110) ## [](#1-4-3)1.4.3 **July 5, 2019** ### [](#mule-version-45)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-30)New Features and Enhancements - None. ### [](#fixed-issues-63)Fixed Issues - Avoid references to the application classloader in Grizzly static fields. (MULE-17108) ## [](#1-4-2)1.4.2 **May 24, 2019** ### [](#mule-version-46)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-31)New Features and Enhancements - None. ### [](#fixed-issues-64)Fixed Issues - When a non-supported CipherSuite is set, Grizzly ignores the restriction after the first request. (MULE-16852) ## [](#1-2-4)1.2.4 **May 24, 2019** ### [](#mule-version-47)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-32)New Features and Enhancements - None. ### [](#fixed-issues-65)Fixed Issues - When a non-supported CipherSuite is set, Grizzly ignores the restriction after the first request. (MULE-16852) ## [](#1-4-1)1.4.1 **May 3, 2019** ### [](#mule-version-48)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-33)New Features and Enhancements - None. ### [](#fixed-issues-66)Fixed Issues - HTTP request streaming throws out-of-memory exception. (MULE-16756) ## [](#1-2-3)1.2.3 **May 3, 2019** ### [](#mule-version-49)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-34)New Features and Enhancements - None. ### [](#fixed-issues-67)Fixed Issues - HTTP request streaming throws out-of-memory exception. (MULE-16756) ## [](#1-1-9)1.1.9 **May 3, 2019** ### [](#mule-version-50)Mule Version **Mule 4.1.4** ### [](#new-features-and-enhancements-35)New Features and Enhancements - None. ### [](#fixed-issues-68)Fixed Issues - HTTP request streaming throws out-of-memory exception. (MULE-16756) ## [](#1-1-8)1.1.8 **May 2, 2019** ### [](#mule-version-51)Mule Version **Mule 4.1.4** ### [](#new-features-and-enhancements-36)New Features and Enhancements - None. ### [](#fixed-issues-69)Fixed Issues - HTTP client should use the worker pool when streaming responses. (MULE-16597) ## [](#1-4-0)1.4.0 **April 22, 2019** ### [](#mule-version-52)Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-37)New Features and Enhancements - Miscellaneous performance improvements. (MULE-16101) - Introduce support for WebSockets. (MULE-15850) ### [](#fixed-issues-70)Fixed Issues - Local authentication doesn’t prevail when there are multiple authentication method headers. (MULE-16308) ## [](#1-2-2)1.2.2 **April 3, 2019** ### [](#mule-version-53)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-38)New Features and Enhancements - None. ### [](#fixed-issues-71)Fixed Issues - Source completion callback not called on failure. (MULE-16634) - HTTP client should use worker pool when streaming responses. (MULE-16597) - HTTP client throws NPE if not started. (MULE-15205) ## [](#1-2-1)1.2.1 **January 10, 2019** ### [](#mule-version-54)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-39)New Features and Enhancements - None. ### [](#fixed-issues-72)Fixed Issues - HTTP service client cannot do gzip response decompression. (MULE-16274) - URL exposed when URI can’t be created because it’s malformed. (MULE-16206) ## [](#1-1-7)1.1.7 **January 10, 2019** ### [](#mule-version-55)Mule Version **Mule 4.1.4** ### [](#new-features-and-enhancements-40)New Features and Enhancements - None. ### [](#fixed-issues-73)Fixed Issues - HTTP service client cannot do gzip response decompression. (MULE-16274) ## [](#1-1-6)1.1.6 ### [](#mule-version-56)Mule Version **Mule 4.1.4** **December 18, 2018** ### [](#new-features-and-enhancements-41)New Features and Enhancements - None. ### [](#fixed-issues-74)Fixed Issues - Fix vulnerability in AHC fork. (MULE-16154) - URL exposed when URI can’t be created because it’s malformed. (MULE-16206) ## [](#1-2-0)1.2.0 **December 6, 2018** ### [](#mule-version-57)Mule Version **Mule 4.1.5** ### [](#new-features-and-enhancements-42)New Features and Enhancements - Parameterize HTTP server’s path tree structure. (MULE-15632) - Enhance RequestMatcherRegistry. (MULE-15764) - Introduce support for WebSockets. (MULE-15850) ### [](#fixed-issues-75)Fixed Issues - Fix vulnerability in AHC fork. (MULE-16154) - Miscellaneous performance improvements. (MULE-16101) - Miscellaneous performance improvements for proxy scenario. (MULE-15924) - Malformed URL returns 500 instead of 400. (MULE-15888) - Some HTTP log entries go to the runtime log instead of to the app. (MULE-15871) - Update Grizzly version to MULE-005. (MULE-15853) ## [](#1-1-5)1.1.5 **November 20, 2018** ### [](#mule-version-58)Mule Version **Mule 4.1.4** ### [](#new-features-and-enhancements-43)New Features and Enhancements - None. ### [](#fixed-issues-76)Fixed Issues - HTTP EE Service overrides request address for properties proxy. (EE-6397) - Malformed URL returns 500 instead of 400. (MULE-15888) ## [](#1-1-4)1.1.4 **September 13, 2018** ### [](#mule-version-59)Mule Version **Mule 4.1.4** ### [](#new-features-and-enhancements-44)New Features and Enhancements None. ### [](#fixed-issues-77)Fixed Issues - Added configuration name to the loggers category to be able to filter them. (MULE-14148) - Grizzly prematurely closes the request stream. (MULE-15581) - Grizzly should reset requestInput stream in NTLM type3 message. (MULE-15667) - HTTP service should preserve POST request body on a dancing request. (MULE-15674) - Prevent request body closing in HTTP service. (MULE-15662) - Upgrade javax.mail to javax.mail-api 1.6.2. (MULE-15331) ## [](#1-1-3)1.1.3 **July 24, 2018** ### [](#mule-version-60)Mule Version **Mule 4.1.3** ### [](#new-features-and-enhancements-45)New Features and Enhancements None. ### [](#fixed-issues-78)Fixed Issues - Cannot replace a catch-all listener with another. (MULE-15246) - HTTP with one config and two listeners fails to find the correct resolution path. (MULE-14929) - HTTP: Reduce request creation overhead. (MULE-15419) - Infinite timeout conflicts with socket timeout. (MULE-15062) - Simultaneous reading and writing causes NPE in grizzly. (MULE-15145) - Upgrade notifications must be handled from mule as no HTTP/2. (MULE-15269) - Using serverTimeout has no effect. (MULE-15004) ## [](#1-1-2)1.1.2 **May 9, 2018** ### [](#mule-version-61)Mule Version **Mule 4.1.2** ### [](#new-features-and-enhancements-46)New Features and Enhancements None. ### [](#fixed-issues-79)Fixed Issues - Escape all error handlers. (MULE-13034) - HTTP request connection limit reached error is not descriptive. (MULE-14760) - If server is not initialized yet 503 response was not sent. (MULE-14959) ## [](#1-1-1)1.1.1 **March 16, 2018** ### [](#mule-version-62)Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-47)New Features and Enhancements None. ### [](#fixed-issues-80)Fixed Issues - HTTP service should support Java network properties to allow the usage of proxies during design time. (MULE-14644) - HTTP: Allow requester to keep provided headers case. (MULE-14530) - HTTP: Performance improvements in listener. (MULE-14519) - Load REMOTELY\_CLOSED\_EXCEPTION on service classloader. (MULE-14565) - Update minMuleVersion in the HTTP service and the HTTP EE service to 4.1.1 after changes in MULE-14530. (MULE-14624) - Upgrade Grizzly version 2.3.35. (MULE-14442) - Use content-id for setting part name, when name is not present. (MULE-14549). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Hybrid Standalone Release Notes These are the release notes for Hybrid Standalone deployments. ## [](#august-19-2026)August 19, 2026 ### What’s New - Hybrid Standalone Mule (HSA) is now available in all control planes: US Cloud, Canada Cloud, EU Cloud, Japan Cloud, India Cloud, and Australia Cloud. - Anypoint Monitoring adds support for Hybrid Standalone Deployments to more cloud control planes: - [Australia](https://au1.platform.mulesoft.com/monitoring) Cloud - [Canada](https://ca1.platform.mulesoft.com/monitoring) Cloud - [India](https://in1.platform.mulesoft.com/monitoring) Cloud - [Japan](https://jp1.platform.mulesoft.com/monitoring) Cloud For the required version of the Anypoint Monitoring agent installer and setup instructions, refer to [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#august-19-2026). ## [](#november-3-2025)November 3, 2025 ### What’s New - Hybrid Standalone documentation is now available. For more information, refer to [Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/). ## [](#see-also)See Also - [Hybrid Standalone Runtimes Overview](https://docs.mulesoft.com/hybrid-standalone/) - [Known Issues](https://help.salesforce.com/s/issues) # Hyperforce Release Notes These are the release notes for Salesforce Hyperforce (Hyperforce). ## [](#september-30-2026)September 30, 2026 ### What’s New - You can now deploy to United Kingdom Cloud control plane. United Kingdom Cloud co-locates the MuleSoft control plane and runtime plane in the United Kingdom, so customer and integration data remains in country. Local hosting helps organizations meet local data residency requirements and reduces latency. For more information, refer to [Features Supported](https://docs.mulesoft.com/hyperforce/#features-supported). ## [](#august-19-2026)August 19, 2026 ### What’s New - Hybrid Standalone Mule (HSA) is now available in all control planes: US Cloud, Canada Cloud, EU Cloud, Japan Cloud, India Cloud, and Australia Cloud. For more information, refer to [Features Supported](https://docs.mulesoft.com/hyperforce/#features-supported). - Visibility into Hybrid Standalone Deployments is now available in all control planes from Anypoint Monitoring. - [Australia Cloud](https://au1.platform.mulesoft.com/monitoring) - [Canada Cloud](https://ca1.platform.mulesoft.com/monitoring) - [EU Cloud](https://eu1.anypoint.mulesoft.com/monitoring) - [India Cloud](https://in1.platform.mulesoft.com/monitoring) - [Japan Cloud](https://jp1.platform.mulesoft.com/monitoring) - [US Cloud](https://anypoint.mulesoft.com/monitoring) For the required version of the Anypoint Monitoring agent installer and setup instructions, see [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#august-19-2026). For more information, refer to [Features Supported](https://docs.mulesoft.com/hyperforce/#features-supported). ## [](#august-5-2026)August 5, 2026 ### What’s New - You can now deploy to Australia Cloud control plane. Australia Cloud co-locates the MuleSoft control plane and runtime plane in Australia, so customer and integration data remains in country. Local hosting helps organizations meet data residency requirements, including Australian Privacy Principles (APPs) and Australian Prudential Regulation Authority (APRA) standards, and reduces latency. For more information, refer to [Features Supported](https://docs.mulesoft.com/hyperforce/#features-supported). ## [](#june-15-2026)June 15, 2026 ### What’s New - You can now deploy to India Cloud control plane. India Cloud co-locates the MuleSoft control plane and runtime plane in India, so customer and integration data remains in country. Local hosting helps organizations meet local data residency requirements, including in regulated industries such as financial services, capital markets, healthcare, and the public sector. India Cloud includes Agent Fabric, Omni Gateway, and MuleSoft Vibes. For more information, refer to [Features Supported](https://docs.mulesoft.com/hyperforce/#features-supported). ## [](#april-29-2026)April 29, 2026 ### What’s New - Anypoint Partner Manager is now available in US Cloud and EU Cloud control planes. - Agent Fabric and Agent Visualizer features are now available in Canada Cloud and Japan Cloud control planes.
Category Feature

Discoverability

Agent Registry: Agent Assets

Agent Registry: MCP Assets (Including Public MCP Assets)

Agent Registry: LLM Assets

Agent Scanners

Governance

Agent, MCP, LLM instances in API Management

A2A, MCP, LLM Flex policies

Managed Flex Gateway in CloudHub 2.0

Managed Flex Gateway in Anypoint Runtime Fabric

Trusted Agent Identity

MCP Bridge

Orchestration

Agent Broker authoring with MuleSoft Vibes (Anypoint Code Builder)

Agent Broker authoring via YAML (Anypoint Code Builder)

Agent Broker deployment to CloudHub 2.0

Agent Broker deployment to Anypoint Runtime Fabric

Observability

Agent Visualizer nodes

Agent Visualizer runtime edges

Agent Visualizer: Agent Metrics
For details, see [Agent Fabric Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes) and [Agent Visualizer Release Notes](https://docs.mulesoft.com/jp/release-notes/agent-visualizer/agent-visualizer-release-notes). ## [](#march-30-2026)March 30, 2026 ### What’s New - New charts and visualizations of app and API metrics in Anypoint Insights dashboards are now available in US Cloud, EU Cloud, Japan Cloud, and Canada Cloud control planes. These metrics bring Anypoint Insights dashboards into near parity with metrics displayed through the built-in dashboards in Anypoint Monitoring. For details, see [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#march-30-2026). ## [](#january-30-2026)January 30, 2026 ### What’s New - Telemetry Exporter is now available in Canada Cloud and Japan Cloud control planes to organizations with the Advanced subscription tier. Centralize observability with Telemetry Exporter by exporting audit log and trace data to your third-party monitoring ecosystem. Telemetry Exporter: [サードパーティ監視システムへのテレメトリーデータのエクスポート](https://docs.mulesoft.com/jp/monitoring/telemetry-exporter). For information about subscription tiers, see [Anypoint Platform Packages and Plans](https://docs.mulesoft.com/jp/monitoring/#billing). ## [](#december-18-2025)December 18, 2025 ### What’s New - [MuleSoft Accelerator for Healthcare](https://docs.mulesoft.com/healthcare/latest/) and [MuleSoft Accelerator for Life Sciences](https://docs.mulesoft.com/life-sciences/latest/) are now available in Canada Cloud control plane. ## [](#august-1-2025)August 1, 2025 ### What’s New - Anypoint Partner Manager is now available in Canada Cloud and Japan Cloud control planes. ## [](#december-9-2024)December 9, 2024 ### What’s New - MuleSoft is now available on Hyperforce. - You can now deploy to Canada Cloud control plane. Canada Cloud co-locates the MuleSoft control plane and runtime plane in Canada, so customer and integration data remains in country. Local hosting helps organizations meet data residency requirements, including the Personal Information Protection and Electronic Documents Act (PIPEDA), and reduces latency. - You can now deploy to Japan Cloud control plane. Japan Cloud co-locates the MuleSoft control plane and runtime plane in Japan, so customer and integration data remains in country. Local hosting helps organizations meet local data residency requirements and reduces latency. For more information, refer to [Salesforce Hyperforce (Hyperforce)](https://docs.mulesoft.com/hyperforce/). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # IBM CICS Transaction Gateway Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for IBM CICS Transaction Gateway (IBM CTG) provides integration with backend CICS applications using the CICS Transaction Gateway. For Java platforms, CTG implements the JCA resource adapter to connect Java applications to the CICS system. Guide: [IBM CICS Transaction Gateway Connector](https://docs.mulesoft.com/ibm-ctg-connector/latest/) ## [](#3-0-2)3.0.2 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

IBM CICS TG (for Multiplatforms and for z/OS)

9.1, 9.2 and 9.3

IBM CICS TG SDK

9.1, 9.2 and 9.3
## [](#3-0-1)3.0.1 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

IBM CICS TG (for Multiplatforms and for z/OS)

9.1, 9.2 and 9.3

IBM CICS TG SDK

9.1, 9.2 and 9.3
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The javax.resource-api library is upgraded to version 1.7.1.

W-23441711
## [](#3-0-0)3.0.0 **October 26, 2025** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

IBM CICS TG (for Multiplatforms and for z/OS)

9.1, 9.2 and 9.3

IBM CICS TG SDK

9.1, 9.2 and 9.3
### Fixed Issues
Issue Resolution ID

The IBM CTG connection no longer fails on the first request.

W-19184073

The .isPresent() check is added to the optional data field to prevent potential null pointer exceptions.

W-20020840

The org.apache.commons:commons-lang3 dependency is upgraded to version 3.18.0 to address security vulnerabilities.

W-20020852
## [](#2-3-10)2.3.10 **October 8, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM CICS TG (for Multiplatforms and for z/OS)

9.1, 9.2 and 9.3

IBM CICS TG SDK

9.1, 9.2 and 9.3
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded from version 3.6.0 to 3.17.0 due to library maintenance.

W-15177673
## [](#2-3-9)2.3.9 **June 23, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### Fixed Issues
Issue ID

Operations now reconnect after a connection is closed.

W-11015652
## [](#2-3-8)2.3.8 **March 31, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### Fixed Issues
Issue ID

Removed the atlantic-commons dependency.

W-10890152
## [](#2-3-7)2.3.7 **December 28, 2020** ### [](#compatibility-7)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#fixed-issues-6)Fixed Issues - Fixed security vulnerabilities. (CONN-7305) ## [](#2-3-6)2.3.6 **Aug 21, 2020** ### [](#compatibility-8)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#fixed-issues-7)Fixed Issues Fixed build error in Anypoint Studio. (SE-17178) ## [](#2-3-5)2.3.5 **May 21, 2020** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#fixed-issues-8)Fixed Issues Fixed reported security vulnerabilities. (CONN-6152) ## [](#2-3-4)2.3.4 **November 6, 2019** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#features)Features - You can now log the request and response with IBM CTG. Adding a logger of the class "org.mule.modules.ibmctg.internal.service.CTGServiceImpl" at DEBUG level (in the log4j2.xml file of the Mule App) ### [](#fixed-issues-9)Fixed Issues - None ## [](#2-3-3)2.3.3 **October 29, 2019** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#fixed-issues-10)Fixed Issues - Username and Password parameters are optional if security is not enabled in the CICS region. ## [](#2-3-2)2.3.2 **October 7, 2019** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#fixed-issues-11)Fixed Issues - Fixed compatibility with Mule 4.2.2. ## [](#2-3-1)2.3.1 **July 5, 2019** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.0 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#fixed-issues-12)Fixed Issues - The connector would sometimes incorrectly assume that the payload was empty for the **executeCommArea** and **executeMultipleChannels** operations. (SE-12156) ## [](#2-3-0)2.3.0 **June 27, 2019** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.0 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#features-2)Features - **Response Time** is now configurable. This field is located under **Additional Settings** in the connector’s configuration. This timeout is the maximum amount of time in milliseconds that a managed connection attempts to wait for a response to a request. A value of 0 represents no timeout. The default is 30000 milliseconds (30 seconds). ### [](#fixed-issues-13)Fixed Issues - The connector occasionally assumed incorrectly that the input payload was empty. This was fixed so that regardless of the type of InputStream the connector’s operations receive, the connector works correctly. (SE-12156) ## [](#2-2-0)2.2.0 **May 29, 2019** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.0 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#features-3)Features - `Pooling profile` was enabled for connections. ## [](#2-1-1)2.1.1 **November 29, 2018** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.0 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
### [](#features-4)Features - Added support for Multiple Containers, which are named references to a storage area managed by CICS that can hold any form of application data. ## [](#2-0-0)2.0.0 **January 19, 2018** IBM CICS Transactions Gateway (IBM CTG) connector is available in Mule 4.0.
Software Version

Mule

4.0 and later

Java

8

IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2

IBM CICS TG SDK

9.1 and 9.2
Notes: - The remote CICS TG must be at the same or a higher release level than the version of the JCA resource adapter. - The JCA resource adapter must match the CICS TG platform. For example, if you have CICS TG for Multiplatforms, you cannot connect to it from a CICS TG with the z/OS resource adapter. The following JAR files are required to set up a connector configuration: - ccf2.jar (CICS Common Connector Framework) - cicsjee.jar (CICS JEE) - ctgclient.jar (CTG Client Library) - ctgserver.jar (CTG Server Library) - geronimo-j2ee-connector\_1.6\_spec-1.0.jar (JCA 1.6 Specification)
JCA 1.6 is needed as a required library to overcome conflicts with JCA 1.5 shipped with Mule.
### [](#features-5)Features - Authentication - The connector uses under the hood, the IPIC (IP interconnectivity) protocol to establish communication with CICS regions over TCP/IP. This type of client also supports SSL authentication. - Execution of CICS Programs - The connector allows users to invoke CICS programs: - Using Channels and Containers. - Using a COMMAREA. Data transfers are limited to 32 KB. - Transactions - The connector leverages XA Transactions by means of Mule’s Transactional scope and the Bitronix Transaction Manager components. - DataSense - The connector supports adding metadata using through the Custom Metadata Tab option. Using the Copybook feature, a user can import a schema that describes the data structure going in and out of CTG so as to be used by a DataWeave component. ### [](#known-issues)Known Issues - Although the inclusion of JCA 1.6 as a required library is meant to solve compatibility conflicts with the JCA 1.5 shipped with Mule, it is yet unknown if this causes side effects. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # IBM MQ Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for IBM MQ (IBM MQ Connector) enables an app to do messaging to a IBM MQ Broker using the IBM MQ JMS implementation. Guide: [IBM MQ Connector User Guide](https://docs.mulesoft.com/ibm-mq-connector/latest/) ## [](#2-0-1)2.0.1 **October 13, 2026** ### Compatibility
Software Version

Mule

4.10 and later

OpenJDK

17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

JMSCC0111 errors no longer occur when a Client ID is configured and connection caching is enabled for the IBM MQ Connection or the IBM MQ XA Connection. The client ID is now applied to the cached connection only, instead of the cached connection and the IBM MQ connection factory.

W-14100275

Publishing to a full queue now raises an IBM-MQ:PUBLISHING error for MQRC_Q_FULL (2053), instead of treating the error as a lost connection and reconnecting, when the app uses the legacy IBM MQ client library (com.ibm.mq.allclient).

W-24012864

These libraries are upgraded to address reported security vulnerabilities:

  • The Spring Framework libraries spring-jms, spring-core, spring-beans, spring-context, spring-expression, and spring-messaging are upgraded to version 6.2.19.

  • The slf4j-api and jcl-over-slf4j libraries are upgraded to version 2.0.20.

  • The commons-codec library is upgraded to version 1.22.1.

  • The guava library is upgraded to version 33.7.2-jre.

  • The c3p0 library is upgraded to version 0.14.2.

  • The mchange-commons-java library is upgraded to version 0.6.0.

  • The ActiveMQ client library is upgraded to version 6.3.2.

W-24311628, W-24012864, W-24137088
## [](#2-0-0)2.0.0 **August 3, 2026** ### What’s New - This connector is now compatible with Java 17 only. - This connector uses the Jakarta Messaging (`jakarta.jms`) namespace, instead of `javax.jms`. The recommended IBM MQ client library is now `com.ibm.mq.jakarta.client` 9.4.5.1, instead of `com.ibm.mq.allclient`. If your app supplies the `com.ibm.mq.allclient` library, the connector wraps it to expose a `jakarta.jms` connection factory for backward compatibility only. See [Support for the Legacy javax.jms Client Library](https://docs.mulesoft.com/ibm-mq-connector/latest/#javax-client-library). - The `enableXa` attribute is removed from the connection configuration. - The connector provides separate connection types for XA and non-XA transactions. You can now select the new **IBM MQ XA Connection** type in the **IBM MQ Config** window. This new connection type replaces the previous `enableXa` attribute on a single connection. The existing **IBM MQ Connection** type is now used only for non-XA scenarios. See [Handling Transactions in IBM MQ](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-transactions). - The connection element is renamed from `` to ``. Apps that use the previous element name or the `enableXa` attribute don’t start until you update the configuration. See [Upgrading and Migrating IBM MQ Connector to Version 2.x](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-connector-upgrade-migrate). - The **XA connection pool** configuration (**Min Pool Size**, **Max Pool Size**, and **Max Idle Seconds**) applies only to the **IBM MQ XA Connection** type. ### Compatibility
Software Version

Mule

4.10 and later

OpenJDK

17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

These libraries are upgraded:

  • The jakarta.jms-api library is upgraded to version 3.1.0, replacing javax.jms-api.

  • The IBM MQ client library is upgraded to com.ibm.mq.jakarta.client version 9.4.5.1.

  • The Spring framework is upgraded to version 6.2.19.

  • The Mule JMS client library is upgraded to version 2.0.1.

W-21756343
## [](#1-9-0)1.9.0 **June 15, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

The On New Message source no longer leaks inactivity monitoring threads during reconnection cycles. The connector now cancels stale monitoring tasks before starting new ones, preventing thread accumulation and high resource usage.

W-22394423

The connector now logs NullPointerException errors that occur during message listener teardown as WARN instead of ERROR. This prevents unnecessary operator escalations for exceptions that do not impact application functionality.

W-21191825
## [](#1-8-3)1.8.3 **May 8, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The grizzly-http, grizzly-http-server, grizzly-framework, grizzly-websockets, and grizzly-connection-pool libraries are upgraded to version 2.4.4.

  • The grizzly-http-client library is upgraded to version 1.16.

  • The quartz library is upgraded to version 2.3.2.

  • The c3p0 library is upgraded to version 0.10.2.

  • The mchange-commons-java library is upgraded to version 0.3.2.

  • The guava library is upgraded to version 33.4.8-jre.

  • The commons-io library is upgraded to version 2.18.0.

  • The commons-text library is upgraded to version 1.14.0.

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The javax.mail library is upgraded to version 1.4.7.

W-22376257
## [](#1-8-2)1.8.2 **April 13, 2026** ### What’s New - The connector now supports Automatic Application Balancing in IBM MQ Uniform Clusters with the new **Client Reconnect Options** and **Client Reconnect Timeout** fields. When configured with a Connection Name List or CCDT, the connector enables dynamic client connection rebalancing across Queue Managers, allowing applications to automatically reconnect to available queue managers in the cluster. See [IBM MQ Connector Reference - Client](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-xml-ref#client). ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

The Publish operation no longer treats queue-full errors as connection errors, which previously caused unnecessary connection resets and flow hangs. The connector now throws the IBM-MQ:PUBLISHING error for queue-full conditions, enabling reliable error handling without disrupting the connection.

W-20427004
## [](#1-8-1)1.8.1 **January 24, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

The On New Message source now supports the Inactivity Timeout Minutes field, which allows the source to reconnect automatically if no message is received within the specified period. The default value is 0.

W-20609348

The commons-lang3 dependency is upgraded to version 3.18.0 to address CVE-2025-48924.

W-21054728

MQRC_DATA_LENGTH_ERROR (2010) is now treated as non-recoverable, so the connector stops retrying and surfaces the terminal validation failure.

W-18834134

IBM MQ Connector now converts MQJMS2007 errors to ConnectionException so the Publish and Publish consume operations reconnect automatically.

W-20527836
## [](#1-8-0)1.8.0 **December 3, 2025** ### What’s New - This connector now supports TLS 1.3 cipher suites as defined in RFC 8446, enabling secure channel negotiation using modern cryptographic protocols. Both IBM and Oracle JDKs implement TLS 1.3 cipher suites using standardized names, providing a unified configuration model across different runtime environments. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

MUnit tests no longer fail with HTTP 404 errors when deleting queues via the IBM MQ REST API while using the Netty HTTP service. Tests now properly stop listener flows and wait for connection cleanup to complete before proceeding with queue deletion.

W-20083097
## [](#1-7-8)1.7.8 **September 17, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The Publish operation now supports the ADMIN.QUEUE destination, which allows you to refresh the connection or reconnect listeners at runtime. This is useful for maintenance or error recovery without stopping the Mule application. For more information, see Configure ADMIN.QUEUE to Refresh Connections.

W-17295817, W-18756149, W-19024281
## [](#1-7-7)1.7.7 **July 15, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

In IBM MQ 1.7.4, memory leak issues were resolved for Mule runtime versions running on Java 8. However, Mule runtime versions running on Java 11 or 17 used reflection, which caused IllegalAccessException errors. These are resolved now, and the connector no longer experiences memory leaks or reflection-related errors on Java 11 or 17.

W-18591182
## [](#1-7-6)1.7.6 **May 28, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The mule-jms-client dependency is upgraded to 1.13.24.

W-17156082

Reconnection issues no longer occur when you use a connection list with the connector.

W-17156082

Reconnection issues no longer occur when you use the Publish Consume operation.

W-17780005

Memory leaks no longer occur in JmsListener.

W-17967138
## [](#1-7-5)1.7.5 **March 21, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

IBM MQ Connector now contains patched Spring 5.x to fix security vulnerabilities.

W-17968742
## [](#1-7-4)1.7.4 **March 3, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

A NullPointerException error no longer occurs when stopping the JMS connection resource.

W-16504615

There are no longer memory leaks caused by the Thread Context Class Loader (TCCL) of the JMSCCThreadPoolMaster ThreadGroup.

W-13521498, W-13521848
## [](#1-7-3)1.7.3 **February 21, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

IBM MQ Connector now automatically attempts to reconnect for the Publish, Publish consume, and Consume operations after a connection is lost.

W-15854054, W-17584793
## [](#1-7-2)1.7.2 **November 14, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.17.0.

W-17024625

The org.apache.commons:commons-io library is upgraded to version 2.17.0.

W-17024625
## [](#1-7-1)1.7.1 **August 15, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The connector now attempts to reconnect when the JMSWMQ0018 error occurs in the Publish operation.

W-15829872

The connector now throws all JMSException errors in the Publish operation.

W-16146401
## [](#1-7-0)1.7.0 **April 18, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
## [](#1-6-24)1.6.24 **March 19, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector no longer fails with NoSuchFieldException when an XA transaction exception occurs.

W-12099940
## [](#1-6-23)1.6.23 **January 30, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector now attempts to reconnect when MQRC_HOST_NOT_AVAILABLE or MQRC_CONNECTION_BROKEN errors occur.

W-14451111
## [](#1-6-22)1.6.22 **January 5, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
## [](#1-6-21)1.6.21 **November 7, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector no longer fails when the application is redeployed within a domain connection. The runtime version configuration must be upgraded to 4.3.0-20231026 or 4.4.0-20231026 or later.

W-12388528
## [](#1-6-20)1.6.20 **August 10, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

Bumped org.springframework:spring-jms to version 5.3.29 to address security vulnerabilities.

W-13830571

Bumped commons-io:commons-io to version 2.13.0 to address security vulnerabilities.

W-13830571

Bumped org.apache.commons:commons-lang3 to version 3.13.0 to address security vulnerabilities.

W-13830571

Bumped io.qameta.allure:allure-junit4 to version 2.23.0 to address security vulnerabilities.

W-13830571

Bumped org.apache.maven.plugins:maven-surefire-plugin to version 3.1.2 to address security vulnerabilities.

W-13830571
## [](#1-6-19)1.6.19 **April 05, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

Bumped spring-jms to version 5.3.26 at JMS Connector to address vulerabilities for spring-jms lower versions.

W-12950397
## [](#1-6-18)1.6.18 **March 23, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector now avoids thread leaks on disconnections.

W-12350716
## [](#1-6-17)1.6.17 **January 19, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector Publish operation no longer fails when a connectivity error occurs.

W-12189382
## [](#1-6-16)1.6.16 **November 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

IBM MQ Connector now avoids thread leaks in the IBM driver thread workers.

W-12003685
## [](#1-6-15)1.6.15 **October 6, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Update of dependencies.

W-11861100
## [](#1-6-14)1.6.14 **September 29, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

IBM MQ Connector no longer gets stuck when stopping a source that was processing messsages.

W-11476953
## [](#1-6-13)1.6.13 **July 7, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

The CCSID property of the connection provider now works correctly when configured.

W-10583435

Intermittent IBM MQ messages no longer error out with unprintable characters shown in messages written to the backout queue.

W-11337787
## [](#1-6-12)1.6.12 **June 29, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Updated visually in Anypoint Studio CSS ID field to CCS ID.

W-11267520
## [](#1-6-11)1.6.11 **June 8, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Bumped spring-jms to version 5.3.20 at JMS Connector to address vulerabilities for spring-jms lower versions.

W-11157721
## [](#1-6-10)1.6.10 **Jan 27, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Fixed internal tests.

IMC-53
## [](#1-6-9)1.6.9 **Jan 20, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Fixed Bitronix errors when a TransactionException occurs.

JMSCLI-26
## [](#1-6-8)1.6.8 **October 26, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Fixed a source reconnection issue when working with XA transactions.

IMC-97
## [](#1-6-7)1.6.7 **August 20, 2021** ### What’s New - Optimized the connector to improve its overall stability and performance. (IMC-93) ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
## [](#1-6-6)1.6.6 **May 6, 2021** ### [](#compatibility-35)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### [](#fixed-issues-32)Fixed Issues - A thread leaked when connections were validated on Mule runtime. (JMSCLI-20) - Connections did not recover when the Broker Queue Manager was restarted while publishing, in the context of an XA transaction. (JMSCLI-21) ## [](#1-6-5)1.6.5 **April 21, 2021** ### [](#fixed-issues-33)Fixed Issues - IBM MQ Connector did not forward messages to the configured backout or dead letter queue when the message processing failed during the XA transaction (JMSCLI-19). ## [](#1-6-4)1.6.4 **March 1, 2021** ### [](#fixed-issues-34)Fixed Issues - Fixed an issue that generated contention and affected the concurrency in the Publish Consume operation (JMSCLI-14). ## [](#1-6-3)1.6.3 **November 17, 2020** ### [](#fixed-issues-35)Fixed Issues - Fixed an issue that blocked listener threads when calling the recover-session twice (JMSCLI-9). ## [](#1-6-2)1.6.2 **October 21, 2020** ### [](#fixed-issues-36)Fixed Issues - Fixed an issue in which IBM MQ Connector caused a connection leak when using dynamic configurations (IMC-73). - Added a timeout verification to prevent connections from hanging indefinitely (JMSCLI-6). ## [](#1-6-1)1.6.1 **June 16, 2020** ### [](#fixed-issues-37)Fixed Issues Deadlock on stopping apps with on flight messages in WMQ listeners. (IMC-70) ## [](#1-6-0)1.6.0 **June 5, 2020** ### [](#new-features)New Features Added support to avoid automatic reply when the inbound message contains a ReplyTo header. (IMC-68) ## [](#1-5-9)1.5.9 **May 4, 2020** ### [](#fixed-issues-38)Fixed Issues Fixed issue that caused sessions to fail to close in cases where the listener was set to a nonexistent queue. (MULE-18377) ## [](#1-5-8)1.5.8 **May 4, 2020** ### [](#fixed-issues-39)Fixed Issues Fixed issue that caused IBM MQ Connector to trigger a `MULE:UNKNOWN` error instead of `IBM-MQ:PUBLISHING` (EE-7323). ## [](#1-5-7)1.5.7 **April 13, 2020** ### [](#fixed-issues-40)Fixed Issues Fixed issue that caused IBM MQ Connector to fail to reconnect to all queues after stopping and starting the channel (EE-7282). ## [](#1-5-6)1.5.6 **March 30, 2020** ### [](#fixed-issues-41)Fixed Issues IBM MQ uses the JMS API to get the correlation ID in the publish-consume operation (EE-7270). ## [](#1-5-5)1.5.5 **February 28, 2020** ### [](#fixed-issues-42)Fixed Issues Made changes so that IBM MQ operations should be blocking due to requirements in the IBM MQ driver (EE-7235). IBM MQ driver does not reestablish connections correctly (EE-7253). ## [](#1-5-4)1.5.4 **February 12, 2020** ### [](#fixed-issues-43)Fixed Issues The issue that caused mishandling of the correlation ID in MQ with a non JMS compliant target client in a publish-consume operation is fixed (EE-7214). ## [](#1-5-3)1.5.3 **November 27, 2019** ### [](#fixed-issues-44)Fixed Issues The issue where reconnection failed after stopping and restarting the Server Connection Channel is fixed (EE-7253). ## [](#1-5-2)1.5.2 **October 1, 2019** ### [](#fixed-issues-45)Fixed Issues - IBM MQ Connector fails to recover after connection error. - IBM MQ Connector is retrying with old session, which resulted in message loss when the message was sent with a `Reply To` header. - Upgrade mule-extensions-patent, mule-core-modules-parent, and mule-ee-core-modules-parent to 1.1.6 (MULE-17121). ## [](#1-5-1)1.5.1 **June 25, 2019** ### [](#fixed-issues-46)Fixed Issues IBM MQ messages are going into uncommitted state. ## [](#1-5-0)1.5.0 **June 13, 2019** ### [](#new-features-2)New Features Added support for different [request reply patterns](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-publish-consume) for the **Publish Consume** and **Listener** operations. ## [](#1-4-1)1.4.1 **June 12, 2019** ### [](#fixed-issues-47)Fixed Issues - The Consume operation didn’t roll back correctly on XA transactions. (MULE-16969) - Bridge scenario with XA hangs in some cases. ## [](#1-4-0)1.4.0 **May 29, 2019** ### [](#new-features-3)New Features - Make XA Connection pool configurable. - Fixed issue with Publish Consume Operation leaking connections. ## [](#1-3-0)1.3.0 **May 27, 2019** ### [](#new-features-4)New Features Fixed issue with XA transactions on reconnection scenarios. ## [](#1-2-6)1.2.6 **April 30, 2019** ### [](#new-features-5)New Features Fixed reconnection issues when using session caching. ## [](#1-2-5)1.2.5 **April 26, 2019** ### [](#new-features-6)New Features - Connector now implements its own reconnection logic. - Custom way of cleaning consumer’s listeners. ## [](#1-2-4)1.2.4 **April 4, 2019** ### [](#new-features-7)New Features Clean up the IBM MQ exception listener states so that they are now done silently. ## [](#1-2-3)1.2.3 **March 29, 2019** ### [](#new-features-8)New Features - Fixed reconnection issue when Queue Manager is shutdown while handling REPLY\_TO. - Fixed IBM MQ Client unhandled exception when cleaning a consumer’s message listener. - Cleanup of IBM MQ exception listener state, when a cached connection is not cleaned up. ## [](#1-2-2)1.2.2 **March 19, 2019** ### [](#new-features-9)New Features Fixed a bug that prevented the reconnection strategy to be triggered in the publish operation. ## [](#1-2-1)1.2.1 **February 22, 2019** ### [](#new-features-10)New Features Fixed a bug with the MQ Listener using Transactional Action Begin that stopped messages from being processed. ## [](#1-2-0)1.2.0 **February 5, 2019** ### [](#new-features-11)New Features Out of the box support for TLS/SSL configurations. ## [](#1-1-2)1.1.2 **January 14, 2019** ### [](#new-features-12)New Features Fixed connection leaks. These leaks could happen when a Publish action failed internally or when doing an automatic ReplyTo when using the "On New Message" source. ## [](#1-1-1)1.1.1 **November 7, 2018** ### [](#new-features-13)New Features Fixed issue that prevented the connector from setting a Client ID, required for durable subscriptions. ### [](#fixed-issues-48)Fixed Issues Unable to set the Client ID on an IBM MQ Connection. ## [](#1-1-0)1.1.0 **October 26, 2018** ### [](#new-features-14)New Features - Fixed issue that prevented correct execution when using XA Transactions. - Message Listener can be configured to propagate the correlation ID when doing a reply. ### [](#fixed-issues-49)Fixed Issues XA Transaction is not working for IBM MQ Connector. ## [](#1-0-0)1.0.0 **June 29, 2018** ### [](#features-and-enhancements)Features and Enhancements Release of IBM MQ Connector, which supports consuming and publishing messages through the JMS API. ### [](#mule-version)Mule Version Mule 4.1.1 ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # IDP Release Notes MuleSoft Intelligent Document Processing (IDP) enables you to read invoices, purchase orders, and other unstructured or semi-structured documents and then analyze and refine the extracted content using AI capabilities to create a structured response. ## [](#october-16)October 16, 2026 ## What’s New - You can now dismiss a review without approving the extracted results. For additional instructions, see [Dismiss a Review Without Approving the Results](https://docs.mulesoft.com/idp/reviewing-processed-documents#dismiss-review). - Removed Gemini 2.5 Flash model support. Google is deprecating this model. Update any document actions that use it to a supported model. IDP routes requests from Gemini 2.5 Flash to Gemini 3.5 Flash, until the model is retired from the product. For the list of available models, see [Supported Models](https://docs.mulesoft.com/idp/supported-models). ## [](#october-5)October 5, 2026 ## What’s New - You can now use AI to discover data in a document and automatically create the output schema for the document action. For additional instructions, see [Discover Data to Extract from Your Documents with AI](https://docs.mulesoft.com/idp/analyzing-documents-with-einstein#discover-with-ai) ## [](#september-2)September 2, 2026 ## What’s New - You can now import and export document action schemas as JSON files. - You can now filter the review list by reviewer and document type. ## [](#august-28)August 28, 2026 ## What’s New - IDP now supports analyzing documents in Japanese. ## [](#july-10)July 10, 2026 ## What’s New - IDP now supports larger documents through the API. You can now process documents up to 150 pages and 15 MB when using the API execution endpoint. For complete file size limits, see [Quotas and Limits](https://docs.mulesoft.com/idp/quotas-and-limits). - You can now use Gemini 3.5 Flash and Claude Opus 4.6 to analyze your documents. For additional details on model support and performance, see [Supported Models](https://docs.mulesoft.com/idp/supported-models). ## [](#june-5)June 5, 2026 ## What’s New - You can now use Claude Sonnet 4.6 to analyze your documents. For additional details on model support and performance, see [Supported Models](https://docs.mulesoft.com/idp/supported-models). - You can now view published document action versions. Open earlier versions of your document actions to review their configuration without making changes. For additional details and instructions, see [View Published Document Action Versions](https://docs.mulesoft.com/idp/publishing-document-actions#view-published-versions). - Removed Gemini 2.0 Flash 001 model support. Google retired this model on June 1, 2026, so you can no longer select Gemini 2.0 Flash 001 to analyze your documents. Update any document actions that use it to a supported model. For the list of available models, see [Supported Models](https://docs.mulesoft.com/idp/supported-models). ## [](#may-5)May 5, 2026 ## What’s New - You can now use OpenAI GPT 5.1 and 5.2 to analyze your documents. For additional details on model support and performance, see [Supported Models](https://docs.mulesoft.com/idp/supported-models). - You can now search and filter document actions in the **Document Actions** page. ## [](#april-2)April 2, 2026 ## What’s New - Updated OpenAI model names. - Einstein OpenAI GPT-4o Mini 0718 is now Einstein OpenAI GPT-4o Mini. - Einstein OpenAI GPT-4o 0806 is now Einstein OpenAI GPT-4o. ## [](#march-20)March 20, 2026 ## What’s New - Removed Gemini 3 model support. This feature isn’t quite ready, so we’re removing it for now. We’ll let you know when it’s back up. ## [](#march-10)March 10, 2026 ## What’s New - You can now enable location callouts in Generic document actions with customized schemas. For additional details about supported models and limitations, see [Configure Document Action Settings](https://docs.mulesoft.com/idp/creating-document-actions#document-action-settings) - You can now select Google’s GEMINI-3.0 Flash (Beta) model to analyze your documents. For additional usage details and considerations about this model, see [Supported Models](https://docs.mulesoft.com/idp/supported-models) ## [](#october-29)October 29, 2025 ## What’s New - You can now select Google’s GEMINI-2.5 Flash model to analyze your documents. ## [](#june-3)June 3, 2025 ## What’s New - You can now rotate documents in the document action builder preview and review task preview. The rotation is for visual assistance and does not modify the original file. ## Fixed Issues
Issue Resolution ID

For the emails field in Purchase Order and Invoice actions, IDP now returns null instead of an empty array [] in the execution response after reviewing the associated task.

W-17330495
## [](#may-20)May 20, 2025 ## What’s New - You can now **Submit** review tasks without having to scroll to the end of the fields list, improving accessibility. ## [](#may-8)May 8, 2025 ## What’s New - You can now enable image recognition in your document actions. To enable this feature, see [Configure Document Action Settings](https://docs.mulesoft.com/idp/analyzing-documents-with-einstein#settings). - You can now select Google’s GEMINI-2.0 Flash 001 model to analyze your documents. To select the model to use, see [Configure Document Action Settings](https://docs.mulesoft.com/idp/analyzing-documents-with-einstein#settings). For additional information about supported models, see [Supported Models](https://docs.mulesoft.com/idp/supported-models) - Einstein prompts now support up to 128,000 input tokens per request. For additional details about token consumption, see [Token Usage and Estimation](https://docs.mulesoft.com/idp/quotas-and-limits#tokens). - Data retention policies are updated: - For all successful executions, IDP now retains the data for 24 hours. - IDP now retains any incomplete tasks for 30 days. ## [](#february-5)February 5, 2025 ## What’s New - You can now analyze any type of document and fully customize the output structure by creating a Generic document action and enabling **Customize Schema**. For more information, see [Analyzing Documents With Custom User-Defined Schemas](https://docs.mulesoft.com/idp/analyzing-documents-with-einstein). - Generic document actions now support using non-English characters for prompt instructions when **Customize Schema** is enabled. - New document actions now support the `GPT-4o (gpt-4o-2024-08-06)` and `GPT-4o Mini (gpt-4o-mini-2024-07-18)` LLM Models. - New document actions now support masking any personally identifiable information from your documents before sending it to the predictive model. - The API portal documentation for IDP assets published to Exchange now includes the `valueOnly` query parameter. - You can now upload files in Base64 encoding for versioned action executions. For an example API call, see [Upload a Base64-encoded File](https://docs.mulesoft.com/idp/automate-document-processing-with-the-idp-api#upload-base64-file). - IDP can now detect signatures in document actions that use Einstein. ## Fixed Issues
Issue Resolution ID

Completed executions no longer stay in status ACKNOWLEDGED.

W-17064164

Failed executions that include Einstein prompts no longer show status IN_PROGRESS.

W-17465241

Required table columns are now shown in the corresponding page during reviews.

W-17485449
## [](#November-20)November 20, 2024 ## What’s New - IDP now fully supports analyzing documents in French, Italian, and Portuguese. - Organizations with Salesforce Einstein enabled now use Einstein as the default option for answering prompts. - IDP now supports non-latin characters in the file preview during document action creation. ## [](#November-7)November 7, 2024 ## What’s New - You can now analyze your documents with Salesforce Einstein. Use Einstein to analyze documents that don’t use a standard format or are difficult to read without performing a complex analysis of the extracted data. See [Analyze Documents with Einstein](https://docs.mulesoft.com/idp/creating-document-actions#einstein) for information about configuring Einstein in your document actions. ## [](#October-2)October 2, 2024 ## What’s New - IDP now supports analyzing TIFF files. ## [](#september-26)September 26, 2024 ## What’s New - Invoice and Purchase Order data extraction accuracy is improved for all supported languages. - Invoice and Purchase Order document actions now support extracting VAT and VAT Rate from tables. ## [](#august-22)August 22, 2024 ## What’s New - IDP now fully supports analyzing documents in Spanish and German. ## [](#may-8-2024)May 8, 2024 ## What’s New - You can now define a callback URL for your executions. See [Define a Callback URL](https://docs.mulesoft.com/idp/automate-document-processing-with-the-idp-api#callback-url) for details and configuration instructions. ## [](#april-29-2024)April 29, 2024 ## What’s New - MuleSoft announces the release of Intelligent Document Processing (IDP). ## [](#see-also)See Also - [IDP Overview](https://docs.mulesoft.com/idp/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Informatica Business 360 Connector Release Notes Anypoint Connector for Informatica Business 360 (Informatica B360 Connector) enables you to connect to the Informatica Business 360 (MDM) REST API. Informatica B360 Connector enables Mule applications to perform master data management operations including entity CRUD, search and fuzzy matching, and metadata discovery. Guide: [Informatica Business 360 Connector User Guide](https://docs.mulesoft.com/informatica-b360-connector/latest/) ## [](#1-0-1)1.0.1 **June 24, 2026** ### Compatibility
Software Version

Mule

4.6.0 and later

Java

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now works correctly for Informatica IICS tenants on the dmp- pod family, for example, usw1.dmp-us.informaticacloud.com. Connection refused, Unrecognized SSL message, and UnknownHostException errors no longer occur when performing any MDM operation on dmp- pods.

W-22943277
## [](#1-0-0)1.0.0 **April 19, 2026** ### What’s New This is a new connector. For more information, see the [Informatica Business 360 Connector User Guide](https://docs.mulesoft.com/informatica-b360-connector/latest/). ### Compatibility
Software Version

Mule

4.6.0 and later

Java

8, 11, and 17
## [](#see-also)See Also - [Informatica Business 360 Connector User Guide](https://docs.mulesoft.com/informatica-b360-connector/latest/) - [Informatica Business 360 Connector Reference](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-reference) - [Salesforce Help](https://help.salesforce.com/s/) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Injection Protection Policy The Injection Protection Policy policy scans incoming requests to protect against SQL, XSS, and custom injection attacks. For configuration details, see [Injection Protection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-injection-protection). ## [](#december-04-2025)December 04, 2025 ### What’s New - Injection Protection Policy policy implementation version 1.0.1 is now supported by Omni Gateway. - Injection Protection Policy policy definition version 1.0.0 is now supported by Omni Gateway. # Intercom Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Intercom (Intercom Connector) synchronizes data and automates business processes between Google Sheets and third-party applications, either on-premises or in the cloud. Google Sheets is a real-time spreadsheet tool with powerful functions to help teams efficiently perform many functions ranging from helping sales teams collaborate on leads or opportunities to aiding HR teams in collaborating on candidates for interviewing and hiring. Guide: [Intercom Connector User Guide](https://docs.mulesoft.com/jp/intercom-connector/latest/) ## [](#1-0-7)1.0.7 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-6)1.0.6 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The json library is upgraded to version 20260814.

  • The commons-io library is upgraded to version 2.22.0.

  • The Google Guava library is upgraded to version 33.7.1-jre.

W-23441658
## [](#1-0-5)1.0.5 **May 24, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-4)1.0.4 **June 16, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

Update dependencies org.apache.maven.plugins:maven-clean-plugin to v3.2.0, org.apache.maven.plugins:maven-resources-plugin to v3.3.1, com.mulesoft.munit:mtf-tools to v1.1.2, dependency org.json:json from 20201115 to 20230227, dependency org.mule.connectors:mule-http-connector to v1.7.3, dependency org.mule.connectors:mule-objectstore-connector to v1.2.1, dependency org.mule.connectors:mule-file-connector to v1.5.1, dependency org.mule.runtime.plugins:mule-extensions-shade-plugin to v1.0.4

W-13464643
## [](#1-0-3)1.0.3 **January 6, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9827
## [](#1-0-2)1.0.2 **December 22, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9692
## [](#1-0-1)1.0.1 **December 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9550
## [](#1-0-0)1.0.0 **March 9, 2021** New connector. ### [](#compatibility-8)Compatibility Intercom Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features - Qualify customer leads efficiently by automating a flow where any time a new customer reaches out via Intercom’s chat functionality, a new lead or opportunity is created in Salesforce for a sales representative follow-up. - Enhance customer experience by notifying the relevant teams (such as customer support, product) via Slack or MS Teams instantly any time a customer reaches out with an issue via Intercom’s chat. - Keep all your teams in sync with the most recent and relevant information around a customer synced across Intercom and your other IT systems via bi-directional sync automation. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # IP Allowlist The IP Allowlist policy allows a list or range of specified IP addresses to request access For configuration details, see [IP Allowlist Policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-allowlist). ## [](#october-1-2026)October 1, 2026 ### What’s New - IP Allowlist policy definition version 1.1.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - IP Allowlist policy implementation version 1.2.1 is now supported by Omni Gateway. - IP Allowlist policy definition version 1.1.1 is now supported by Omni Gateway. # IP Allowlist ## [](#1-1-3)1.1.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-1-1)1.1.1 **May 26, 2022** ### [](#fixed-issues)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-1-0)1.1.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-0-0)1.0.0 **Jul 30, 2021** ### [](#minimum-mule-version)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Introduced the IP Allowlist policy that fixes the inclusive terminology issues in the Legacy IP Allowlist policy. ## [](#see-also)See Also - [IP Allowlist](https://docs.mulesoft.com/gateway/latest/policies-included-ip-allowlist) - [Known Issues](https://help.salesforce.com/s/issues) # IP Blocklist The IP Blocklist policy blocks a single IP address or a range of IP addresses from accessing an API endpoint For configuration details, see [IP Blocklist Policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-blocklist). ## [](#october-1-2026)October 1, 2026 ### What’s New - IP Blocklist policy definition version 1.1.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - IP Blocklist policy implementation version 1.2.1 is now supported by Omni Gateway. - IP Blocklist policy definition version 1.1.1 is now supported by Omni Gateway. # IP Blocklist ## [](#1-1-3)1.1.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-1-1)1.1.1 **May 26, 2022** ### [](#fixed-issues)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-1-0)1.1.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-0-0)1.0.0 **Jul 30, 2021** ### [](#minimum-mule-version)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Introduced the IP Blocklist policy that fixes the inlcusive terminology issues in the Legacy IP Blocklist policy. ## [](#see-also)See Also - [IP Blocklist Policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-blocklist) - [Known Issues](https://help.salesforce.com/s/issues) # Java Adoption Starting with Mule runtime engine 4.6, MuleSoft is adopting Java’s long-term support (LTS) release cadence, which adds support for Java 17 LTS. ## [](#mule-runtime-java-support)Mule Runtime Java Support This table shows the timeline for Java 8, Java 11, and Java 17 support:
Mule Version Release Date Java Version End of Standard Support End of Extended Support

4.13 Edge

October 2026

17

March 2027

June 2027

4.12 Edge

June 2026

17

November 2026

February 2027

4.11 Edge

February 2026

17

July 2026

October 2026

4.10 Edge

October 2025

17

March 2026

June 2026

4.9 LTS

February 2025

17

August 2027

February 2028

4.9 Edge

February 2025

17

November 2025

February 2026

4.8 Edge

October 2024

8, 11, and 17

March 2025

June 2025

4.7 Edge

June 2024

8, 11, and 17

October 2024

February 2025

4.6 LTS

February 2024

8, 11, and 17

August 2026

February 2027

4.6 Edge

February 2024

8, 11, and 17

June 2024

October 2024

4.5 Edge

October 2023

8 and 11

February 2024

June 2024

4.4

September 2021

8 and 11

October 2024

October 2025

4.3

April 2020

8 and 11

March 2023

March 2025
Java 17 is recommended. The change has no immediate impact on Mule applications and Mule Gateway policies and proxies running on currently supported Mule versions, or on applications upgraded to Mule runtime 4.6. Mule apps that are currently running on Java 8 continue to be supported until August 2026. Support for Java 8 ends with the Mule runtime 4.9 release in February 2025, and Java 11 will no longer be available. For more information about the Java adoption, see [Java サポート](https://docs.mulesoft.com/jp/general/java-support) ## [](#upgrading-mule-apps)Upgrading Mule Apps
Before you upgrade your integration apps or Mule Gateway policies and proxies to Java 17, all extensions, modules, and connectors used within those apps and policies must first be Java 17-compatible.
Components (custom code, custom connectors, MuleSoft connectors) are now Java 17-compatible. Test and redeploy your apps to run with Java 17 on your runtime deployment model. If your app doesn’t have custom code, you can add Java-17 connectors to your app through Studio as usual. After apps are updated and Java 17-ready, test them in your Mule 4.6 and later runtime deployment environment. Mule Gateway API policies and proxies are now Java 17-compatible, so you can upgrade your API instances. ## [](#see-also)See Also - [Java サポート](https://docs.mulesoft.com/jp/general/java-support) - [FIPS 140-2 Compliance Support](https://docs.mulesoft.com/mule-runtime/latest/fips-140-2-compliance-support) - [Known Issues](https://help.salesforce.com/s/issues) # Java Module Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Use Java Module to invoke Java code. Guide: [Java Module User Guide](https://docs.mulesoft.com/jp/java-module/latest/) ## [](#2-0-8)2.0.8 **October 14, 2026** ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The spring-core library is removed to address reported security vulnerabilities.

W-24468177
## [](#2-0-7)2.0.7 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
## [](#2-0-6)2.0.6 **August 3, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
## [](#2-0-5)2.0.5 **June 30, 2026** ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The spring-core library is upgraded to version 6.2.19.

  • The mockito library is upgraded to version 5.23.0.

W-22944057
## [](#2-0-4)2.0.4 **December 18, 2025** ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The spring-core library is upgraded to version 6.2.15 to address the CVE-2025-41249 security vulnerability.

W-20593403
## [](#2-0-3)2.0.3 **October 29, 2025** ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.18.0 to address the CVE-2025-48924 security vulnerability.

W-19605039
## [](#2-0-2)2.0.2 **September 9, 2025** ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The Spring framework is upgraded to version 6.2.10 to address the CVE-2025-41242 security vulnerability.

W-19578317
## [](#2-0-1)2.0.1 **August 5, 2025** ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

Java Module no longer exhibits incorrect behavior when used in a shared domain configuration with multiple applications that contain Java classes with the same fully qualified name (FQN). Java Module incorrectly cached classloading results across applications, resulting in method invocations resolving to the wrong application’s class. Now, the caching logic includes context classloader or application identity as part of the cache key.

W-18492205
## [](#2-0-0)2.0.0 **June 30, 2025** ### What’s New - Java Module (and its dependencies) are now compilable and compatible only with Java 17. - To align with modern development practices and ensure continued compatibility with secure and supported libraries, Java Module is upgraded from Spring 5.x to Spring 6.x. For more information about how to upgrade the connector to version 2.0, refer to [Java Module のバージョン 2.x へのアップグレードおよび移行](https://docs.mulesoft.com/jp/java-module/latest/java-module-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
## [](#1-2-19)1.2.19 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-18)1.2.18 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commonsLang library is upgraded to version 3.20.0 to address reported security vulnerabilities.

W-23441694
## [](#1-2-17)1.2.17 **August 4, 2026** This version is deprecated. The new features and fixed issues for this version are in version 1.2.18. ## [](#1-2-16)1.2.16 **October 29, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.18.0 to address the CVE-2025-48924 security vulnerability.

W-19605039
## [](#1-2-15)1.2.15 **August 4, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Java Module no longer exhibits incorrect behavior when used in a shared domain configuration with multiple applications that contain Java classes with the same fully qualified name (FQN). Java Module incorrectly cached classloading results across applications, resulting in method invocations resolving to the wrong application’s class. Now, the caching logic includes context classloader or application identity as part of the cache key.

W-18492205
## [](#1-2-14)1.2.14 **March 21, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Java Module now contains patched Spring 5.x to fix security vulnerabilities.

W-17918454
## [](#1-2-13)1.2.13 **March 25, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The spring-core library is upgraded to version 5.3.33 to address reported security vulnerabilities.

W-15194448
## [](#1-2-12)1.2.12 **December 12, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-11)1.2.11 **June 21, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The spring-core library is upgraded to version 5.3.28 to address reported security vulnerabilities.

W-13622235
## [](#1-2-10)1.2.10 **June 28, 2022** ### What’s New - Upgraded versions of dependencies. ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
## [](#1-2-9)1.2.9 **August 17, 2021** ### What’s New - Optimized the connector to improve its overall stability and performance. (JM-35) ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
## [](#1-2-8)1.2.8 **April 8, 2021** ### [](#features)Features None. ### [](#fixed-issues-13)Fixed Issues - Removed dependencies included in the Mule runtime engine to avoid warning messages during startup (JM-34) ## [](#1-2-7)1.2.7 **November 4, 2020** ### [](#features-2)Features None. ### [](#fixed-issues-14)Fixed Issues - Upgraded Spring version to 5.3.0 (JM-31) ## [](#1-2-6)1.2.6 **December 9, 2019** ### [](#features-3)Features None. ### [](#fixed-issues-15)Fixed Issues - Wrong OutputType for a method that returns a java.lang.Object type. (JM-14) - MUnit tests for metadata validation. (MU-1529) - Upgrade mule-extensions-parent, mule-core-modules-parent and mule-ee-core-modules-parent to 1.1.6. (MULE-17121) - Upgrade MUnit version to 2.2.1. (MULE-17301) ## [](#1-2-5)1.2.5 **August 14, 2019** ### [](#features-4)Features - Change execution pool to CPU\_LITE for new instance operations. (MULE-17326) - Change execution pool to IO for invoke operations. (MULE-17329) ### [](#fixed-issues-16)Fixed Issues None. ## [](#1-2-4)1.2.4 **May 30, 2019** ### [](#features-5)Features None. ### [](#fixed-issues-17)Fixed Issues - Java module fails to invoke method that receives Optional (MULE-16932) ## [](#1-2-3)1.2.3 **May 29, 2019** ### [](#features-6)Features None. ### [](#fixed-issues-18)Fixed Issues - Java module fails to transform null into an empty Optional. (MULE-16918) ## [](#1-2-2)1.2.2 **April 26, 2019** ### [](#features-7)Features None. ### [](#fixed-issues-19)Fixed Issues - Upgrade Spring to 5.1.6. - Upgrade Apache Commons Lang to 3.8.1. ## [](#1-2-1)1.2.1 **January 14, 2019** ### [](#features-8)Features - Fixed an issue with invoking a method from a class that implements an interface with generics. This would produce a warning that there were multiple methods found that match the provided method. ### [](#fixed-issues-20)Fixed Issues - JavaModule: no longer throws WARN messages with Generic interface implementation. (MULE-16316) ## [](#1-2-0)1.2.0 **September 6, 2018** ### [](#features-9)Features - It’s now possible to configure the Output MimeType of the Invoke and Invoke Static Operations. - Improved error handling, the connector used to not show the real error that occurred when executing Java methods. - New functions `getRootCause` and `isCausedBy` are now available to introspect Throwables. - In the extreme case where two parameters have the same simple name, such as `some.Pojo` and `other.Pojo` the full qualifier name can be used to avoid issues. ### [](#fixed-issues-21)Fixed Issues - JavaModule: Support output MimeType parameter for runtime inference. (MULE-15283) - Java Module: Improve Error cause propagation. (MULE-15540) - Java Module: does not propagate execution error. (MULE-15262) - Java Module invokeStatic declares an error that is never thrown. (MULE-15461) - JavaModule: Support full qualifier name for parameter types to identify methods. (MULE-15009) - Migrate JavaModule tests to MTF. (MULE-15076) - Java Module: improve method not found error message. (MULE-15263) - Java Module: 'new' operation does not declare INVOCATION error. (MULE-15538) - Java Module: Fail to extract exception cause with default value. (MULE-15597) ## [](#1-1-2)1.1.2 **August 14, 2019** ### [](#features-10)Features - Provide proper classloading error information. (MULE-14938) - Improve error messages and exception propagation. (MULE-15263) - Change execution pool to CPU\_LITE for new instance operations. (MULE-17326) - Change execution pool to IO for invoke operations. (MULE-17329) ### [](#fixed-issues-22)Fixed Issues - InvokeStatic declares an error that is never thrown. (MULE-15461) ## [](#1-1-1)1.1.1 **May 11, 2018** ### [](#minimum-mule-version)Minimum Mule Version Mule 4.1.0 ### [](#features-11)Features - Fixed an issue that made it impossible to pass null as a parameter. - Now when the arguments are passed by with their canonical name (arg0, arg1, etc.), parameter matching will be done by position. ### [](#fixed-issues-23)Fixed Issues - JavaModule: Do best effort to do invocation with arg0, arg1…​ (MULE-15008) - null values causes Exception in parameterNeedsTransformation. (MULE-14990) ## [](#1-1-0)1.1.0 **May 7, 2018** ### [](#minimum-mule-version-2)Minimum Mule Version Mule 4.1.0 ### [](#features-12)Features - When argument types don’t match the java function arguments, a best effort will be done to transform these arguments. ### [](#fixed-issues-24)Fixed Issues - Java module doesn’t transform the arguments. (MULE-14861) ## [](#1-0-1)1.0.1 **March 23, 2018** ### [](#minimum-mule-version-3)Minimum Mule Version Mule 4.1.0 ### [](#features-13)Features - Fixed an issue that happened when calling static methods from different classes with the same signature. ### [](#fixed-issues-25)Fixed Issues - Invoke static second call wrong. (MULE-14785) ## [](#1-0-0)1.0.0 **January 23, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version Mule 4.1.0 ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # JavaScript Scripting Policy The JavaScript Scripting policy runs a user-supplied JavaScript module to inspect and modify requests and responses. For configuration details, see [JavaScript Scripting Policy](https://docs.mulesoft.com/gateway/latest/policies-included-javascript-scripting). ## [](#september-2-2026)September 2, 2026 ### What’s New - JavaScript Scripting policy implementation version 1.0.0 is now supported by Omni Gateway. - JavaScript Scripting policy definition version 1.0.0 is now supported by Omni Gateway. # Jira Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Jira (Jira Connector) gives you access to the Jira APIs. This connector exposes the most commonly used operations provided by the Jira API. Guide: [Jira Connector User Guide](https://docs.mulesoft.com/jp/jira-connector/latest/) ## [](#1-2-17)1.2.17 **July 8, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core library is upgraded to version 2.22.0.

  • The jackson-databind library is upgraded to version 2.22.0.

W-21919325, W-23136397
## [](#1-2-16)1.2.16 **February 28, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The On new issue trigger and On new and updated issue trigger sources now correctly update the watermark when multiple records share the same minute-level timestamp. The connector now uses cursor-based pagination to retrieve all records for a specific watermark before updating the watermark value. This prevents duplicate record retrieval and resolves issues where flows enter an indefinite waiting state.

W-21090825
## [](#1-2-15)1.2.15 **January 21, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The commons-collections library is upgraded to version 4.5.0.

W-20894512
## [](#1-2-14)1.2.14 **November 19, 2025** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The connector now correctly updates the watermark for the On new and updated issue trigger and On new issue trigger sources, and ensures to capture all subsequent new and updated issues.

W-20186115
## [](#1-2-13)1.2.13 **October 2, 2025** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-19586865
## [](#1-2-12)1.2.12 **September 14, 2025** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The Evaluate Jira Expression operation now uses the /rest/api/3/expression/evaluate endpoint instead of the /rest/api/3/expression/eval endpoint.

W-19470768

The Search For Issues Using Jql Post, (Deprecated) Search For Issues Using JQL, and Search For Issues Using JQL (Paginated) operations now use the /rest/api/3/search/jql endpoint instead of the /rest/api/3/search endpoint.

W-19470768

The Search For Issues Using JQL (Paginated) operation now uses marker-based pagination for its pagination strategy. This also means that the Start At field is deprecated and is not used for pagination.

W-19470768
## [](#1-2-11)1.2.11 **February 29, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

You can now install Jira Connector in Anypoint Studio as intended.

W-15070963
## [](#1-2-10)1.2.10 **February 15, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-14762371
## [](#1-2-9)1.2.9 **January 17, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The source’s watermark now uses the expected DateTime format and timezone for consistency.

W-14762371
## [](#1-2-8)1.2.8 **August 25, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13632302
## [](#1-2-7)1.2.7 **July 27, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The connection no longer fails when the Domain URL ends with / or whitespaces.

W-13664733
## [](#1-2-6)1.2.6 **June 26, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13498207
## [](#1-2-5)1.2.5 **May 15, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The exception message is now more clear when there is an invalid organization site URL.

W-13143023
## [](#1-2-4)1.2.4 **April 3, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12270412
## [](#1-2-3)1.2.3 **March 2, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12270412
## [](#1-2-2)1.2.2 **January 31, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The metadata output for the labels property now returns an array of strings instead of an array of empty objects.

W-11899482
## [](#1-2-1)1.2.1 **December 13, 2022** ### What’s New - The com.fasterxml.jackson.core library is upgraded to version 2.14.1. - The org.apache.commons-text library is upgraded to version 1.10.0. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.1 to address reported security vulnerabilities.

W-11933499

The org.apache.commons-text library is upgraded to version 1.10.0 to address reported security vulnerabilities.

W-12004679
## [](#1-2-0)1.2.0 **October 28, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11924747
## [](#1-1-16)1.1.16 **June 15, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Jira Cloud API

3.0.1
### Fixed Issues
Issue ID

The Add Attachment operation no longer returns a 200 OK status when an attachment is not created in the Jira board.

W-11260419
## [](#1-1-15)1.1.15 **May 19, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11107531
## [](#1-1-14)1.1.14 **May 18, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

In the Basic Auth Connection Provider, the new API Token field replaces the Password field since the Password field is deprecated by Atlassian.

W-10894621
## [](#1-1-13)1.1.13 **April 28, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10934109
## [](#1-1-12)1.1.12 **April 26, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11037529
## [](#1-1-11)1.1.11 **April 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920454
## [](#1-1-10)1.1.10 **April 7, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920454
## [](#1-1-9)1.1.9 **March 22, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

There were missing quotes in JQL for the Issue Type used in sources.

W-10830185
## [](#1-1-8)1.1.8 **January 10, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9853
## [](#1-1-7)1.1.7 **December 21, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9629
## [](#1-1-6)1.1.6 **December 14, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9566
## [](#1-1-5)1.1.5 **December 1, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-753
## [](#1-1-4)1.1.4 **November 3, 2021** ### [](#compatibility-31)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-31)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-1-3)1.1.3 **August 18, 2021** ### [](#compatibility-32)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-32)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-1-2)1.1.2 **July 21, 2021** ### [](#compatibility-33)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-33)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-1-1)1.1.1 **July 8, 2021** ### [](#compatibility-34)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#new-features)New Features - Updated the Apache Commons Collections library. ### [](#fixed-issues-34)Fixed Issues - The connector did not show standard fields for input or output metadata. (CONN-8324) - The **On updated issue trigger** used a hard-coded date. ## [](#1-1-0)1.1.0 **July 1, 2021** ### [](#compatibility-35)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#new-features-2)New Features - Add the **On New Issue Trigger** and **On Updated Issue Trigger** sources. ### [](#fixed-issues-35)Fixed Issues - Deprecated the **Search For Issues Using Jql** operation and added the **Search For Issues Using Jql** operation with pagination. (CONN-8149) ## [](#1-0-0)1.0.0 **March 19, 2021** New connector. ### [](#compatibility-36)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features For a list of supported configurations and operations, see the Jira Connector Reference Guide. ### [](#fixed-in-this-release)Fixed in This Release Not applicable. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # JMS Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for JMS (Java Message Service) (JMS Connector) enables sending and receiving messages to queues and topics for any message service that implements the JMS specification. Guide: [JMS Connector User Guide](https://docs.mulesoft.com/jms-connector/latest/) ## [](#2-0-2)2.0.2 **October 14, 2026** ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-24471767
## [](#2-0-1)2.0.1 **September 24, 2026** ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

A non-transactional JMS publish operation no longer hangs indefinitely when the JMS broker stops responding during session creation. The operation now fails as a connectivity error so the configured reconnection strategy can recover.

W-18913222

JMS listener and consumer creation no longer hang indefinitely when the JMS provider blocks during failover. The operation now reports a connectivity error so the configured reconnection strategy can recover.

W-22932102

JMS connection errors are now routed only to listeners consuming the affected destination, preventing a destination-specific failure from disrupting listeners on other destinations that share the same configuration.

W-23286173

JMS broker connections are now opened lazily in transactional and XA connection paths, preventing connections from being created and discarded during connection setup.

W-22790737

The Spring framework is upgraded to version 6.2.19.

W-24129987
## [](#2-0-0)2.0.0 **August 4, 2026** ### What’s New - This connector is now compatible with Java 17 only. - The **Enable xa** field is removed from the ActiveMQ connection factory configuration. - JMS Connector provides separate connection types for XA and non-XA transactions. You can now select the new **ActiveMQ XA Connection** or **Generic XA Connection** type in the **JMS Config** window. These new connection types replace the previous **Enable xa** toggle on a single connection. - The deprecated **ActiveMQ Connection - No Connectivity Test** connection type is removed. There is no replacement connection type. Use **ActiveMQ Connection** instead. For more information about how to upgrade the connector to version 2.0, refer to [Upgrading and Migrating JMS Connector to Version 2.x](https://docs.mulesoft.com/jms-connector/latest/jms-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded:

  • The jakarta.jms-api library is upgraded to version 3.1.0, replacing javax.jms-api.

  • The Spring framework is upgraded to version 6.2.15.

  • The Apache ActiveMQ library is upgraded to version 6.1.0.

  • The Apache ActiveMQ Artemis library is upgraded to version 2.50.0.

W-22761813
## [](#1-10-6)1.10.6 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#1-10-5)1.10.5 **August 12, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

A JMS connection that uses an invalid or duplicate client ID now fails immediately as a terminal error instead of retrying indefinitely, and the associated connection is closed to prevent a thread leak.

W-19332327

Blocking session and consumer creation calls to an unresponsive broker are now bounded by a configurable timeout (default 30 seconds) and surface a connectivity error so the configured reconnection strategy can recover, instead of hanging indefinitely.

W-22932102

A JMS exception that names a single registered destination is now routed only to that destination’s listeners, so unrelated listeners no longer receive the error.

W-23286173

JMS threads are now properly closed and cleaned up during application undeployment, preventing a thread leak when using the ActiveMQ and Artemis drivers.

W-18053810
## [](#1-10-4)1.10.4 **July 23, 2026** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

A non-transactional JMS publish operation no longer hangs indefinitely when the JMS broker stops responding during session creation. The operation now fails as a connectivity error so the configured reconnection strategy can recover.

W-18913222

Oracle Advanced Queuing (AQ) publish failures that report a connection timeout are now treated as connectivity errors, instead of terminal publishing errors, so the configured reconnection strategy can recover.

W-20264223
## [](#1-10-3)1.10.3 **January 30, 2026** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated commons-io from 2.15.0 to 2.21.0.

W-20834191

Updated commons-lang3 from 3.12.0 to 3.20.0.

W-20834191

Updated com.google.guava:guava from 32.1.3-jre to 33.5.0-jre.

W-20834191

Updated com.fasterxml.jackson:jackson from 2.14.2 to 2.15.0.

W-20834191
## [](#1-10-2)1.10.2 **June 30, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated org.apache.activemq:activemq-client from 5.16.7 to 5.16.8.

W-18223618

Updated com.google.guava:guava from 32.1.2-jre to 32.1.3-jre.

W-18223618

Updated org.mule.runtime:mule-sdk-api from 0.8.0 to 0.8.6.

W-18223618
## [](#1-10-1)1.10.1 **April 11, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

JMS Connector now contains patched Spring 5.x to fix security vulnerabilities.

W-18198070
## [](#1-10-0)1.10.0 **March 20, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

JMS Connector now supports query parameters in failover URLs for ActiveMQ connection configurations.

W-17286858

This release includes general security fixes.

W-17849663

JMS Connector now has a system property to set a delay in releasing resources, which helps prevent thread leaks when using Artemis as the JMS driver.

W-17327464
## [](#1-9-7)1.9.7 **August 13, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Message headers now have setters.

W-16116454
## [](#1-9-6)1.9.6 **June 28, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer sets the verifyHostName property for ActiveMQ Client versions prior to 5.15.6.

W-15122911

Connections with Failover configuration now support the verifyHostName parameter when the version of the ActiveMQ Client requires it.

W-15122911
## [](#1-9-5)1.9.5 **June 14, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Reconnection on publish when using Weblogic now works correctly.

W-15804613

Reconnection on consume when using Weblogic and Artemis now works correctly.

W-15837781
## [](#1-9-4)1.9.4 **May 8, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Reconnection when using Artemis Server now works correctly.

W-15211060
## [](#1-9-3)1.9.3 **January 19, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Thread leaks no longer occur when a reconnection is triggered.

W-14282515
## [](#1-9-2)1.9.2 **January 4, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-9-1)1.9.1 **November 29, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### What’s New - The `org.apache.activemq:activemq-client` library support is upgraded to version 5.15.16 to address reported security vulnerabilities. - SSL connections set **verifyHostName** to `false` by default to keep backwards compatibility. ### Fixed Issues
Issue Resolution ID

The ActiveMQ client is no longer affected by a malicious ActiveMQ broker.

W-14544171

TLS connections now require to set verifyHostName on the ActiveMQ client.

W-14544171
## [](#1-9-0)1.9.0 **August 18, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### What’s New - The `com.google.guava` library is upgraded to version 32.1.2-jre to address reported security vulnerabilities. ### Fixed Issues
Issue Resolution ID

You can now enable a secure connection for the Generic Connection.

W-13830306

The com.google.guava library is upgraded to version 32.1.2-jre to address reported security vulnerabilities.

W-13880316
## [](#1-8-8)1.8.8 **April 05, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Bumped spring-jms to version 5.3.26 at JMS Connector to address vulerabilities for spring-jms lower versions.

W-12950397
## [](#1-8-7)1.8.7 **January 18, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

The JMS Connector Publish operation no longer fails reconnecting on ConnectionFailedException.

W-12302934
## [](#1-8-6)1.8.6 **November 02, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

The JMS Connector Consume operation no longer duplicates messages when the operation stops consuming messages.

W-11786899

The JMS Connector Consume operation now stops correctly when it stops consuming messages.

W-11853709
## [](#1-8-5)1.8.5 **October 31, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

JMS Connector now uses correctly an SSL connection with Active MQ and XA.

W-11786346
## [](#1-8-4)1.8.4 **June 3, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

SessionCacheSize behavior now has impact on the total number of sessions that the connector creates.

W-11056232

Updated spring-jms to version 5.3.20 to address vulnerabilities for lower spring-jms versions.

W-11157710
## [](#1-8-3)1.8.3 **Apr 20, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Fixed JMS Connector concurrency limitation for the Consume operation.

W-10685928
## [](#1-8-2)1.8.2 **Dec 21, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Fixed Bitronix errors when a TransactionException occurs.

JMSCLI-26]
## [](#1-8-1)1.8.1 **Nov 4, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Reconnection did not work when using TLS because SslContext was lost between reconnection attempts.

JMSC-93
## [](#1-8-0)1.8.0 **Oct 18, 2021** ### What’s New - Added a new connection provider for ActiveMQ that does not perform pre-deployment connectivity testing, which avoids subscribing to topics with durable connections in simultaneous cloud deployments. ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
## [](#1-7-5)1.7.5 **May 06, 2021** ### [](#fixed-issues-25)Fixed Issues - A thread leaked when connections were validated on Mule runtime. (JMSCLI-20) ## [](#1-7-4)1.7.4 **April 14, 2021** ### [](#fixed-issues-26)Fixed Issues - Fixed an issue that caused the transaction error **A transaction is not available** when trying to publish a message inside of an Async scope component. (JMSC-83) - When performing an ACK or session recover over a message read using the **Consume** operation, with the ACK mode set to **MANUAL**, an `The Consumer is closed` error was thrown. (JMSCLI-16) - Fixed the issue that caused leaked connections when using dynamic parameters in the JMS Connector configuration. (JMSC-84) ## [](#1-7-3)1.7.3 **January 13, 2021** ### [](#fixed-issues-27)Fixed Issues Fixed a session leak that happened when listening to an inexistent queue. (JMSCLI-12) ## [](#1-7-2)1.7.2 **January 7, 2021** ### [](#fixed-issues-28)Fixed Issues Fixed a reconnection issue that occurred when an exception was thrown while publishing. (JMSCLI-10) ## [](#1-7-1)1.7.1 **August 12, 2020** ### [](#fixed-issues-29)Fixed Issues Fixed a connection leak that occurred when using DataWeave expressions on the connector configuration. (JMSC-70) ## [](#1-7-0)1.7.0 **June 8, 2020** ### [](#features)Features - Added support to avoid automatic reply when the inbound message contains a ReplyTo header. (JMSC-65) - Renamed the Listener operation to On New Message. (JMSC-68) ## [](#1-6-3)1.6.3 **October 15, 2019** ### [](#known-issues)Known Issues The `max-redelivery` parameter cannot be configured on the connector side, as it has no effect. It must be configured on the broker side. ### [](#fixed-issues-30)Fixed Issues - Fixed a bug that made apps fail to deploy, even when configured with `failsDeployment="false"`. (MULE-17602) ## [](#1-6-2)1.6.2 **August 9, 2019** ### [](#fixed-issues-31)Fixed Issues - JMS Connector now honors payload encoding when publishing message to a JMS queue. (MULE-17286) ## [](#1-6-0)1.6.0 **June 13, 2019** ### [](#features-2)Features - Added support for different [request reply patterns](https://docs.mulesoft.com/jms-connector/latest/) for the **Publish Consume** and **Listener** operations. ## [](#1-5-1)1.5.1 **June 12, 2019** ### [](#fixed-issues-32)Fixed Issues - The JMS Consume operation didn’t roll back correctly on XA transactions. (MULE-16969) - The JMS Bridge with XA hangs in some cases. ## [](#1-5-0)1.5.0 **May 29, 2019** ### [](#features-3)Features - Make XA pool configurable in the JMS connector. (MULE-16926) ### [](#fixed-issues-33)Fixed Issues - JMS Publish Consumer Operation leaks connection. (MULE-16927) ## [](#1-4-1)1.4.1 **May 28, 2019** ### [](#fixed-issues-34)Fixed Issues - Fix issue with reconnection ## [](#1-4-0)1.4.0 **May 27, 2019** ### [](#fixed-issues-35)Fixed Issues - Fix issue with XA transactions on reconnection scenarios. ## [](#1-3-7)1.3.7 **April 17, 2019** ### [](#features-4)Features - Upgraded Spring version from 5.1.5 to 5.1.6. - Fixed a bug that prevented using XA transactions with some brokers in case of rollbacks. ## [](#1-3-6)1.3.6 **April 3, 2019** ### [](#features-5)Features - Fixed a bug that prevented the usage of the connector as a proxy for some brokers. ## [](#1-3-5)1.3.5 **March 19, 2019** ### [](#features-6)Features - Fixed a bug that prevented the reconnection stategy to be triggered in the Publish operation. ## [](#1-3-4)1.3.4 **February 22, 2019** ### [](#features-7)Features - Added a new icon to the connector. - Fixed a bug around JNDI lookup destinations ## [](#1-3-3)1.3.3 **January 14, 2019** ### [](#features-8)Features - Fixed connection leaks. These leaks happened when a Publish action failed internally or when doing an automatic ReplyTo when using the "On New Message" source. ## [](#1-3-2)1.3.2 **November 27, 2018** ### [](#features-9)Features - Fixed a deadlock when using the JMS Listener on too quick flows, which caused listeners to stop receiving messages. ### [](#fixed-issues-36)Fixed Issues - Application hangs after receiving a few messages from ActiveMQ in Mule 4.x. (MULE-16087) ## [](#1-3-1)1.3.1 **Deprecated** **October 29, 2018** ### [](#features-10)Features - Fixed issue that prevent the usage of a TLS Context. ### [](#fixed-issues-37)Fixed Issues - JMS Connector doesn’t initialize the TLS Context if it is defined as a child element. (MULE-15930) ## [](#1-3-0)1.3.0 **Deprecated** **August 29, 2018** ### [](#features-11)Features - JMS is Non-Blocking for Publish, Consume, and Publish-Consume Operations, improving the scalability of Mule applications. - Support for XA Transactions. The connector can participate in multi-resource transactions, like DB, IBM MQ, and other XA compatible connectors. - ActiveMQ SSL Configuration Support. ActiveMQ Connections can be configured with SSL/TLS Configuration for secure connections. - JMS Listener. Can now configure how to propagate the Correlation ID on the JMS Listener Response. ### [](#fixed-issues-38)Fixed Issues - JMS Publish Consume operation throws JmsIllegalBodyException when returning ManagedCursorStreamProvider in the payload. (MULE-14852) - Support JMS Non-Blocking API. (MULE-14875) - JMS throws ClassCastException when receiving a message. (MULE-15431) - Add support for SSL in the JMS Connector. (MULE-12341) - Implement human-readable toString() implementations. (MULE-15477) - JmsHeaders is not Serializable but JmsAttributes is. (MULE-15455) - XA: NPE on JmsListener#onError after flow stop. (MULE-15488) - JMS: Cannot configure sendCorrelationId in a listener, for sending a response. (MULE-15502) ## [](#1-2-3)1.2.3 **August 7, 2018** ### [](#fixed-issues-39)Fixed Issues - Fixed issue that prevented receiving messages published through the Artemis Management Console. (MULE-15431) ## [](#1-2-2)1.2.2 **May 7, 2018** ### [](#features-12)Features Minor internal upgrades. ### [](#fixed-issues-40)Fixed Issues - Update Spring JMS to version 5.0.5.RELEASE. (MULE-14966) - Upgrade Jackson to 2.9.5. (MULE-14795) ## [](#1-2-1)1.2.1 **April 11, 2018** ### [](#features-13)Features This release includes the following enhancements, changes, and fixes: - JMS Listener failed to reply to a destination if the response was provided by a transformation inside the `Response Body`. ### [](#fixed-issues-41)Fixed Issues - JMS Publish Consume operation throws JmsIllegalBodyException when returning ManagedCursorStreamProvider in the payload. (MULE-14852) ## [](#1-2-0)1.2.0 **Mar 26, 2018** ### [](#features-14)Features This release includes the following enhancements, changes, and fixes: - JMS Listener when running on a cluster only starts in the main node. This setting is configurable: `primaryNodeOnly="false"` ### [](#upgrade-requirements)Upgrade Requirements Mule 4.1.1 ### [](#fixed-issues-42)Fixed Issues - jms:listener should only run on primary node when listening to a topic. (MULE-14678) - Upgrade Spring JMS to 5.0.4 release. (MULE-14633) ## [](#1-1-0)1.1.0 **January 19, 2018** ### [](#features-15)Features This release includes the following enhancements, changes, and fixes: - Added the capability to define allowed packages in ActiveMQ Configuration. - Added support for message correlation. - Improved UX. ### [](#upgrade-requirements-2)Upgrade Requirements Mule 4.1 ### [](#fixed-issues-43)Fixed Issues - JMS Config - ActiveMQ label incorrectly displayed. (MULE-14105) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # JSON Module Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) JSON module provides extra functionality for processing JSON documents. Guide: [JSON Module User Guide](https://docs.mulesoft.com/jp/json-module/latest/) ## [](#2-5-11)2.5.11 **September 25, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Jackson Databind and Jackson Dataformat YAML libraries are upgraded to version 2.22.3 to address the CVE-2026-68497 security vulnerability.

W-24259242
## [](#2-5-10)2.5.10 **September 21, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Validate Schema operation no longer consumes excessive memory when the schema doesn’t include a $schema keyword. When validation fails, the error description is now a short message, instead of the full validation report. The full report remains in the error payload.

W-23681129
## [](#2-5-9)2.5.9 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-5-8)2.5.8 **August 3, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Google Guava library is upgraded to version 33.6.0-jre.

  • The Jackson Databind and Jackson Dataformat YAML libraries are upgraded to version 2.22.1.

  • The Jackson Annotations library is upgraded to version 2.22.

W-23441743
## [](#2-5-7)2.5.7 **July 8, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.mozilla:rhino library is upgraded to version 1.7.15.1 to fix reported security vulnerabilities (CVE-2025-66453).

W-23137165

RejectedExecutionException errors no longer occur during JSON Schema validation when redeploying applications on CloudHub 1.0 fractional vCore workers.

W-18641806
## [](#2-5-6)2.5.6 **June 3, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.mozilla.rhino.version library is upgraded to version 1.7.14.1.

W-22468048
## [](#2-5-5)2.5.5 **February 9, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.sun.mail:jakarta.mail library is upgraded to version 2.0.2.

W-20622362, W-21012860
## [](#2-5-4)2.5.4 **September 2, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The json-schema-validator library is upgraded to version 1.2.0 to fix thread leak issues that caused hot redeployment failures in Windows environments with Java 17.

W-18368344
## [](#2-5-3)2.5.3 **September 11, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Validate schema operation now returns all validation errors for input content that is an array of objects.

W-15733508
## [](#2-5-2)2.5.2 **August 21, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The following libraries are upgraded:

  • The com.networknt:json-schema-validator library is upgraded to version 1.0.87.

  • The com.fasterxml.jackson.core:jackson-annotations, com.fasterxml.jackson.core:jackson-databind, and com.fasterxml.jackson.dataformat:jackson-dataformat-yaml libraries are upgraded to version 2.17.2.

  • The com.google.guava:guava library is upgraded to version 33.2.1-jre.

  • The org.apache.commons:commons-lang3 library is upgraded to version 3.16.0.

W-15939128
## [](#2-5-1)2.5.1 **June 26, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

JSON Module no longer throws ClassNotFoundException when using the Rhino library.

W-15241724
## [](#2-5-0)2.5.0 **March 20, 2024** ### What’s New - This connector is now compatible with Java 17. - The connector license changed from CPAL v1.0 to Apache v2.0. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-4-3)2.4.3 **March 13, 2024** ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The Jackson Dataformat YAML is upgraded to version 2.16.2.

W-15241724
## [](#2-4-2)2.4.2 **September 18, 2023** ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The Guava library is upgraded to version 32.1.2-jre, the Jackson-core and jackson-databind libraries are upgraded to version 2.15.2, and the com.networknt:json-schema-validator is upgraded to version 1.0.79.

W-13844854
## [](#2-4-1)2.4.1 **May 2, 2023** ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Jackson-core and jackson-databind libraries are upgraded to version 2.15.0.

W-12665447
## [](#2-4-0)2.4.0 **January 19, 2023** ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
### What’s New - The **Validate Schema** operation now supports these schema versions: Draft-06, Draft-07, Draft 2019-09, and Draft 2020-12. - JSON module now provides a more detailed error response that returns an array of validation errors. ## [](#2-3-0)2.3.0 **January 10, 2023** ### What’s New - The **Validate Schema** operation’s new field, **Schema Contents**, supports the direct text input of a schema. This enables you to perform a schema validation. ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
## [](#2-2-0)2.2.0 **November 14, 2022** ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The JSON module Validate schema operation now correctly detects an invalid JSON payload with trailing characters.

W-11998991
## [](#2-1-6)2.1.6 **March 28, 2022** ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Fixed reported vulnerability com.fasterxml.jackson.core:jackson-databind@2.12.4.

W-10900776
## [](#2-1-5)2.1.5 **Aug 25, 2021** ### Compatibility

Application/Service

Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Fixed a thread leak that was produced when undeploying an application.

JSONM-44
## [](#2-1-4)2.1.4 **May 26, 2021** ### [](#features)Features - Update dependency com.fasterxml.jackson.core:jackson-databind to 2.12.2. (JSONM-43) ## [](#2-1-3)2.1.3 **March 5, 2020** ### [](#features-2)Features - Update dependency com.fasterxml.jackson.core:jackson-annotations to v2.10.3. (MULE-17516) ## [](#2-1-2)2.1.2 **October 1, 2019** ### [](#features-3)Features - Update jackson-databind to 2.10.0. (MULE-17516) ## [](#2-1-1)2.1.1 **October 1, 2019** ### [](#features-4)Features - Update Jackson Version to 2.10.0.pr3. (MULE-17516) ## [](#2-1-0)2.1.0 **September 24, 2019** ### [](#features-5)Features - Add capability to allow arbitrary precision when deserializing JSON. (MULE-17481) ## [](#2-0-2)2.0.2 **August 9, 2019** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-17)Fixed Issues - Update Jackson Databind to 2.9.9.3. (MULE-17297) - Update Commons Lang3 to 3.8.1. (MULE-17297) ## [](#2-0-1)2.0.1 **June 26, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#features-6)Features - None. ### [](#fixed-issues-18)Fixed Issues - JSON Module throws NPE when the connector can’t load the schema. (MULE-15530) - Update Guava version to 27.1-jre. (MULE-16648) - Upgrade Jackson to 2.9.9. (MULE-17021) ## [](#2-0-0)2.0.0 **July 5, 2018** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#features-7)Features - Errors are no longer reported as a List of Strings. Errors are now reported as an actual JSON document. See [validating documents against a JSON schema with the JSON module](https://docs.mulesoft.com/jp/json-module/latest/json-schema-validation). ### [](#fixed-issues-19)Fixed Issues - JSON Schema Validator does not flag errors in identical JSON objects. (MULE-15303) ## [](#1-0-1)1.0.1 **May 7, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#features-8)Features - Input metadata is more accurate. The connector used to communicate that required any kind of structure. Now, it is more accurate and shows that it requires any **JSON** structure. - Upgraded Jackson version due to [the CVE-2018-7489 vulnerability](https://nvd.nist.gov/vuln/detail/CVE-2018-7489). ### [](#fixed-issues-20)Fixed Issues - Stream consumed when static input resolver is used. (MULE-14753) - Upgrade Jackson to 2.9.5. (MULE-14795) ## [](#1-0-0)1.0.0 **Jan 23, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # JSON Threat Protection ## [](#1-2-2)1.2.2 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-2-0)1.2.0 **March 15, 2023** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### What’s New - You can now write a sequence of numbers followed by a blank space when creating a policy. - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-1-5)1.1.5 **Jun 1, 2022** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed issues - Policy considered valid a payload containing multiple JSON objects. ## [](#1-1-4)1.1.4 **Apr 30, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Performance improvements are introduced to the header manipulation engine. ### [](#fixed-issues-2)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-1-3)1.1.3 **Jul 24, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements Several performance improvements are introduced in this release. ### [](#fixed-issues-3)Fixed Issues When a malformed JSON was provided, the JSON threat protection exposed the names of the internal classes. This issue is now resolved. ## [](#1-1-2)1.1.2 **Apr 26, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements Several performance improvements are introduced in this release. ## [](#1-1-1)1.1.1 **Jun 25, 2018** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Added `violationCategory` in the YAML configuration for Feedback Loop. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-7)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements Reduced error-handling verbosity in templates. ### [](#fixed-issues-4)Fixed Issues When a WSDL proxy received an empty payload, or an invalid XML, an ExpressionRuntimeException error was generated. This issue is now resolved. ## [](#1-0-0)1.0.0 **Nov 13, 2017** ### [](#minimum-mule-version-8)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [JSON Threat Protection for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-json-threat-protection) - [Known Issues](https://help.salesforce.com/s/issues) # JSON Threat Protection Policy The JSON Threat Protection Policy policy protects against malicious JSON in API requests. For configuration details, see [JSON Threat Protection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-json-threat-protection). ## [](#october-1-2026)October 1, 2026 ### What’s New - JSON Threat Protection Policy policy definition version 1.2.2 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - JSON Threat Protection Policy policy implementation version 1.0.2 is now supported by Omni Gateway. - JSON Threat Protection Policy policy definition version 1.2.0 is now supported by Omni Gateway. # JWT Validation The JWT Validation policy validates a JWT. For configuration details, see [JWT Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-jwt-validation). ## [](#september-2-2026)September 2, 2026 ### What’s New - You can now enable OAuth 2.0 Protected Resource Metadata ([RFC 9728](https://datatracker.ietf.org/doc/html/rfc9728)) in the JWT Validation policy. When enabled, the policy serves a protected resource metadata document at `{API_Path}/.well-known/oauth-protected-resource` and includes a `resource_metadata` hint in `401` responses, so that clients can discover the authorization server that protects the API. Enable this feature with the new `enableProtectedResourceMetadata` parameter and specify the authorization server to advertise with the new `protectedResourceMetadataAuthorizationServerUrl` parameter. For configuration details, see [JWT Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-jwt-validation). - JWT Validation policy implementation version 1.5.1 is now supported by Omni Gateway. - JWT Validation policy definition version 0.12.0 is now supported by Omni Gateway. # JWT Validation ## [](#1-4-1)1.4.1 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-4-0)1.4.0 **February 07, 2024** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-3-2)1.3.2 **August 14, 2023** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed issues - Dynamic configuration no longer fails due to heavy payloads. ## [](#1-3-1)1.3.1 **October 28, 2022** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-2)Fixed issues - Some parsing errors no longer cause the original payload to be returned in the response. ## [](#0-9-0)0.9.0 **June 06, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - Flex support for Connected Mode. ## [](#1-3-0)1.3.0 **August 2, 2022** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Introduced support for ES256, ES384, and ES512 signature validation algorithms. ### [](#fixed-issues-3)Fixed issues - A `Cannot parse the token` error message was logged with `ERROR` log level instead of `TRACE`. - Several logs were moved from `DEBUG` log level to `TRACE`. - The JWKS service URL was exposed in the HTTP response from policies. ## [](#1-2-0)1.2.0 **June 25, 2021** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Introduced the capability to configure timeouts when fetching the JSON web key sets (JWKS) from the service. - Implemented a retry mechanism for failed JWKS fetches from the service. ## [](#1-1-4)1.1.4 **January 06, 2021** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Added OAS 3.0 code snippet in the policy YAML file. ## [](#1-1-3)1.1.3 **Apr 30, 2020** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in error handling. ### [](#fixed-issues-4)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). - An error occurred when handling invalid header values of the Basic Authentication policy. - When requests are made to the protected API endpoint with the Client ID Enforcement policy that does not include the client ID and/or secret, a log entry is now created with the details. However, this logging occurs only when you have specified the Debug level in the log4j settings. ## [](#1-1-2)1.1.2 **November 27, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-5)Fixed Issues Escaping issues when setting DataWeave expressions for claim validation. ### [](#known-issues)Known Issues An error occurs in Mule runtime engine (Mule) versions 4.1.1, 4.1.2, 4.1.3, and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-1)1.1.1 **July 24, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements Several performance improvements are introduced in this release. ### [](#fixed-issues-6)Fixed Issues The JSON Web Key Set (JWKS) time-to-live (TTL) was not being changed default. This issue is now resolved. ### [](#known-issues-2)Known Issues - An error occurs in Mule runtime engine (Mule) versions 4.1.1, 4.1.2, 4.1.3, and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. - When JWT policy is applied to a flow running in Mule 4.2.0 or 4.2.1 Mule and the flow contains an operation that runs on a CPU\_INTENSIVE thread, like ee:transform, the flow stops responding under load. To resolve the issue, apply a patch to the Mule runtime engine. ## [](#1-1-0)1.1.0 **April 26, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Introduced support to encrypt sensitive information related to the policy. The Mule version must be properly configured and must support encryption. Encryption is supported starting with Mule v4.2.0. - Serveral performance improvements are introduced in this release. ### [](#known-issues-3)Known Issues An error occurs in Mule runtime engine (Mule) versions 4.1.1, 4.1.2, 4.1.3, and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ### [](#fixed-issues-7)Fixed Issues When uploading a Public key, the correct UI description was not being displayed. This issue is now resolved. ### [](#known-issues-4)Known Issues - When JWT policy is applied to a flow running in Mule 4.2.0 or 4.2.1 Mule and the flow contains an operation that runs on a CPU\_INTENSIVE thread, like ee:transform, the flow stops responding under load. To resolve the issue, apply a patch to the Mule runtime engine. == 1.0.2 **January 29, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-8)New Features and Enhancements Improved performance by using CPU intensive scheduler instead of CPU Light. ### [](#fixed-issues-8)Fixed Issues When using a custom claim with DataWeave, an out-of-memory error occurred. This issue is now resolved. ### [](#known-issues-5)Known Issues - When JWT policy is applied to a flow running in Mule 4.2.0 or 4.2.1 Mule and the flow contains an operation that runs on a CPU\_INTENSIVE thread, like ee:transform, the flow stops responding under load. To resolve the issue, apply a patch to the Mule runtime engine. ## [](#1-0-1)1.0.1 **January 10, 2019** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-9)New Features and Enhancements Improved the RAML and OAS snippets. ### [](#known-issues-6)Known Issues - When JWT policy is applied to a flow running in Mule 4.2.0 or 4.2.1 Mule and the flow contains an operation that runs on a CPU\_INTENSIVE thread, like ee:transform, the flow stops responding under load. To resolve the issue, apply a patch to the Mule runtime engine. ## [](#1-0-0)1.0.0 **December 21, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version **4.1.0** ### [](#known-issues-7)Known Issues - When JWT policy is applied to a flow running in Mule 4.2.0 or 4.2.1 Mule and the flow contains an operation that runs on a CPU\_INTENSIVE thread, like ee:transform, the flow stops responding under load. To resolve the issue, apply a patch to the Mule runtime engine. ## [](#see-also)See Also - [JWT Validation Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-jwt-validation) - [Known Issues](https://help.salesforce.com/s/issues) # Kerberos Module Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Use the Kerberos Module to add Kerberos (SPNEGO) proxy authentication support to the Mule HTTP Connector. Guide: [Kerberos Module User Guide](https://docs.mulesoft.com/kerberos-module/latest/) ## [](#1-0-1)1.0.1 **August 4, 2026** ### Fixed Issues
Issue Resolution ID

Kerberos proxy authentication no longer fails when the proxy requires the standard HTTP/host@REALM service principal. The service principal name is now built using the Kerberos principal name type, so authentication succeeds against proxies that expect the standard service principal name form.

W-22844997

Proxy authentication no longer fails intermittently on reused (keep-alive) connections, where repeated requests over the same connection could alternate between success and failure.

W-23384507

Proxy authentication no longer fails when the proxy returns the Negotiate authentication scheme in non-standard letter casing. The scheme is now recognized regardless of casing.

W-23384757
### Compatibility
Application/Service Version

Mule

4.12.2 and later

HTTP Connector

1.11.0 and later

OpenJDK

17

Netty HTTP Service

0.5.2 and later
## [](#1-0-0)1.0.0 **October 22, 2025** ### Compatibility
Application/Service Version

Mule

4.10.0 and later

HTTP Connector

1.11.0 and later

OpenJDK

17

Netty HTTP Service

0.3.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # LDAP Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Lightweight Directory Access Protocol (LDAP) is an open, vendor-neutral, industry standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. The LDAP connector allows Mule applications to interact with LDAP servers. Guide: [LDAP Connector User Guide](https://docs.mulesoft.com/ldap-connector/latest/) ## [](#3-7-3)3.7.3 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

LDAP

v3

OpenLDAP

2.4.x
## [](#3-7-2)3.7.2 **August 30, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

LDAP

v3

OpenLDAP

2.4.x
## [](#3-7-1)3.7.1 **July 20, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue Resolution ID

javax.naming.NameNotFoundException errors during attribute schema lookups no longer log full stack traces at the WARN level. They are now logged at the DEBUG level, and missing attribute definitions are cached to prevent repeated logging and excessive log growth.

W-23129795

These libraries are upgraded to address reported security vulnerabilities:

  • The com.google.guava:guava library is upgraded to version 33.6.0-jre.

  • The org.slf4j:slf4j-api library is upgraded to version 2.0.18.

  • The org.jetbrains:annotations library is upgraded to version 26.1.0.

W-23129795
## [](#3-7-0)3.7.0 **June 5, 2026** ### What’s New - You can now use the new **Secure SSL Configuration** type instead of **SSL Configuration** type to establish secure connections. The **SSL Configuration** type was deprecated because it relied on global JVM environment configurations and could not support FIPS-compliant truststore types required under FIPS 140-3 environments. - The **Secure SSL Configuration** type includes the new **TLS Context** field. Use this field to configure BCFKS truststores and the Bouncy Castle FIPS provider within your Mule applications. For more information, refer to [Secure SSL Configuration Type](https://docs.mulesoft.com/ldap-connector/latest/ldap-connector-reference#secure-ssl-configuration-type). ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-21526999
## [](#3-6-1)3.6.1 **November 7, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue Resolution ID

Connection management logging messages now reflect connection pooling behavior instead of indicating connections are closed.

W-19678434
## [](#3-6-0)3.6.0 **September 25, 2024** ### What’s New - LDAP Connector now returns `LDAP:SECURITY` error when attempting to establish an insecure connection (Basic Authentication configuration) in environments that require FIPS 140-2 compliance (mule.security.model=fips140-2). For sources or connection tests prior to deployment, an associated `LDAPException` message is thrown, ensuring LDAP connections meet advanced security requirements in regulated environments​. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

LDAP

v3

OpenLDAP

2.4.x
## [](#3-5-6)3.5.6 **January 26, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

LDAP

v3

OpenLDAP

2.4.x
## [](#3-5-5)3.5.5 **October 17, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue Resolution ID

The com.google.guava library is upgraded to version 32.0.1-jre to address reported security vulnerabilities.

W-13844853
## [](#3-5-4)3.5.4 **April 18, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue Resolution ID

The connector now handles pagination from the LDAP server.

W-12980985
## [](#3-5-3)3.5.3 **April 6, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue Resolution ID

The trust store custom configuration no longer overrides the default JVM trust store.

W-12282743
## [](#3-5-2)3.5.2 **February 13, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue Resolution ID

The Paged Result Search operation no longer throws an NPE when the operation uses MaxResult with SSL connections.

W-12233513
## [](#3-5-1)3.5.1 **November 22, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue ID

The Search operation no longer throws an NPE when the operation uses Page Size with SSL connections.

W-11987427
## [](#3-5-0)3.5.0 **March 14, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### What’s New - You can now configure a custom truststore for SSL and TLS configurations by using the new **Custom Truststore Path** and **Custom Truststore Password** fields. For information about using these new fields, see the [LDAP Connector Reference](https://docs.mulesoft.com/ldap-connector/latest/ldap-connector-reference). ### Fixed Issues
Issue ID

You can now configure a custom truststore with the connector.

SE-24432
## [](#3-4-2)3.4.2 **January 25, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue ID

The connector did not pick up the Truststore when a resource related path is provided.

SE-24211
## [](#3-4-1)3.4.1 **December 2, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### Fixed Issues
Issue ID

The Search operation now returns results that contain attributes with no values.

SE-23679
## [](#3-4-0)3.4.0 **June 30, 2021** ### [](#compatibility-16)Compatibility LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### [](#new-features)New Features - Added support for LDAPS (LDAP over SSL), which consists of a new connection provider called **SSL Connection Provider**. ## [](#3-3-2)3.3.2 **June 8, 2021** ### [](#compatibility-17)Compatibility LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-12)Fixed Issues - LDAP triggers were not receiving results after the first poll when using Open LDAP or MS AD. (SE-20905, SE-20906) ## [](#3-3-1)3.3.1 **March 31, 2021** ### [](#compatibility-18)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-13)Fixed Issues An NPE was thrown while getting total results in a paged search. (SE-20290) ## [](#3-3-0)3.3.0 **December 11, 2020** ### [](#compatibility-19)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-14)Fixed Issues Improved LDAP exception handling by adding an `LDAP:OPERATION_NOT_COMPLETED` error type. (SE-18048) ## [](#3-2-6)3.2.6 **September 18, 2020** ### [](#compatibility-20)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-15)Fixed Issues Fixed the issue that caused the connector to hang while trying to close the TLS context. (SE-17272) ## [](#3-2-5)3.2.5 **September 7, 2020** ### [](#compatibility-21)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-16)Fixed Issues - Fixed a security vulnerability. (CONN-6899) ## [](#3-2-4)3.2.4 **August 25, 2020** ### [](#compatibility-22)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-17)Fixed Issues - Several LDAP Connector operations did not escape metacharacters. (SE-17144) ## [](#3-2-3)3.2.3 **July 3, 2020** ### [](#compatibility-23)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-18)Fixed Issues - Fixed issue where BIND operation of LDAP Connector was not properly parsing MS Active Directory GUID and SID values. (SE-16010) ## [](#3-2-2)3.2.2 **June 16, 2020** ### [](#compatibility-24)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-19)Fixed Issues - Fixed issue where LDAP Connector was not properly processing MS Active Directory GUID and SID values. (SE-16010) ## [](#3-2-1)3.2.1 **May 4, 2020** ### [](#compatibility-25)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-20)Fixed Issues - The connector now filters the DN attributes correctly. (SE-15744) - Fixed all reported vulnerabilities. ## [](#3-2-0)3.2.0 **April 2, 2020** ### [](#compatibility-26)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#features)Features - The connector now supports the display of entity attributes as objects, containing the attribute metadata, depending on a property(Show attributes as objects) in the connector configuration(SE-15218). ## [](#3-1-6)3.1.6 **February 3, 2020** ### [](#compatibility-27)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-21)Fixed Issues Fixed the issue where type definitions were missing, which made search results different for Mule 3 and Mule 4. (SE-14621) ## [](#3-1-5)3.1.5 **October 22, 2019** ### [](#compatibility-28)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-22)Fixed Issues - Anypoint Studio displayed an error message when an optional field was left unspecified. (SE-12729) ## [](#3-1-4)3.1.4 **June 24, 2019** ### [](#compatibility-29)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-23)Fixed Issues - Mule LDAP Connector Search and Lookup Search didn’t return multi-value fields as arrays when they were built with a single value. (SE-11864) ## [](#3-1-3)3.1.3 **April 23, 2019** ### [](#compatibility-30)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-24)Fixed Issues - Fixed an issue regarding transformation of an LDAPEntry to a string which was causing java.lang.ArrayIndexOutOfBoundsException. ## [](#3-1-2)3.1.2 **February 20, 2019** Release notes for version 3.1.2 of the LDAP connector. ### [](#compatibility-31)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#features-2)Features This release improves the quality of the code by refactoring and adding comments. ## [](#3-1-1)3.1.1 **October 26, 2018** ### [](#compatibility-32)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#fixed-issues-25)Fixed Issues - The connector failed when the `authentication` parameter was not set. This was fixed and now it works as expected. ## [](#3-1-0)3.1.0 **September 13, 2017** ### [](#compatibility-33)Compatibility The LDAP Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8

LDAP

v3

OpenLDAP

2.4.x
### [](#features-3)Features - The connector now has 2 triggers one for new objects and one for modified objects. Using these 2 triggers one can receive notifications if ldap entries are created or updated since the app was started or since a configured timestamp that can be specified when configuring the trigger. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Legacy IP Allowlist **Jul 30, 2021** IP Whitelist policy has been deprecated after fixing inclusive terminology issues. It will still continue to execute properly in production. Fixes and new features will be released in the [IP Allowlist policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-allowlist). ## [](#1-2-2)1.2.2 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in the policy error handling. ### [](#fixed-issues)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). - Removed `commons-beanutils` dependency from the policy jar file to maintain security compliance. ## [](#1-2-1)1.2.1 **Jul 23, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Several performance improvements were introduced in this release. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ### [](#fixed-issues-2)Fixed Issues - Fixed parsing of remoteAddress for HTTP Connector versions greater than 1.4.0. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Introduces support to encrypt sensitive information related to the policy. The runtime version needs to support encryption and needs to be properly configured. Encryption is supported since Mule Runtime v4.2.0. - Performance improvements. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-1)1.1.1 **Jun 05, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Added `violationCategory` in the YAML configuration for Feedback Loop. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Reduced error-handling verbosity in templates. - Added default expression for IP Addresses in the YAML file instead of in the template. ### [](#fixed-issues-3)Fixed Issues - Fixed `ExpressionRuntimeException` error when a WSDL proxy receives an empty payload, or an invalid XML. ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-6)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [IP Allowlist Policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-allowlist) - [Known Issues](https://help.salesforce.com/s/issues) # Legacy IP Blocklist **Jul 30, 2021** Legacy IP Blocklist policy has been deprecated after fixing inclusive terminology issues. It will still continue to execute properly in production. Fixes and new features will be released in the [IP Blocklist policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-blocklist). ## [](#1-2-2)1.2.2 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in the policy error handling. ### [](#fixed-issues)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). - Removed `commons-beanutils` dependency from the policy jar file to maintain security compliance. ## [](#1-2-1)1.2.1 **Jul 23, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Several performance improvements are introduced in this release. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ### [](#fixed-issues-2)Fixed Issues - The remoteAddress for HTTP Connectors were not being parsed for versions greater than 1.4.0. This issue is now resolved. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Introduced support to encrypt sensitive information related to the policy. The Runtime version must be properly configured and must support encryption. Encryption is supported starting with Mule Runtime v4.2.0. - Several performance improvements are introduced in this release. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-1)1.1.1 **Jun 05, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements Added `violationCategory` in the YAML configuration for Feedback Loop. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Reduced error-handling verbosity in templates. - Added default expression for IP Addresses in the YAML file instead of in the template. ### [](#fixed-issues-3)Fixed Issues When a WSDL proxy received an empty payload, or an invalid XML, an ExpressionRuntimeException error was generated. This issue is now resolved. ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-6)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [IP Blocklist Policy](https://docs.mulesoft.com/gateway/latest/policies-included-ip-blocklist) - [Known Issues](https://help.salesforce.com/s/issues) # LLM PII Detection The LLM PII Detection policy detects personally identifiable information (PII) in OpenAI-format LLM requests and responses. For configuration details, see [LLM PII Detection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-llm-pii-detection). ## [](#july-10-2026)July 10, 2026 ### What’s New - LLM PII Detection policy implementation version 1.0.1 is now supported by Omni Gateway. - LLM PII Detection policy definition version 1.0.0 is now supported by Omni Gateway. # LLM Token Based Rate Limit The LLM Token Based Rate Limit policy rate limits model proxy usage based on token consumption. For configuration details, see [LLM Token Based Rate Limit Policy](https://docs.mulesoft.com/gateway/latest/policies-included-llm-token-rate-limit). ## [](#april-30-2026)April 30, 2026 ### What’s New - LLM Token Based Rate Limit policy implementation version 1.0.3 is now supported by Omni Gateway. ## [](#april-29-2026)April 29, 2026 ### What’s New - LLM Token Based Rate Limit policy definition version 1.0.2 is now supported by Omni Gateway. # Mailchimp Marketing Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Mailchimp Marketing (Mailchimp Marketing Connector) enables you to integrate your applications with the Mailchimp Marketing data and functionality. This connector exposes operations provided by the Mailchimp Marketing API. Guide: [Mailchimp Marketing Connector User Guide](https://docs.mulesoft.com/jp/mailchimp-marketing-connector/latest/) ## [](#1-0-9)1.0.9 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-8)1.0.8 **August 20, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The JSON library is upgraded to version 20260814 to address reported security vulnerabilities.

W-23441662
## [](#1-0-7)1.0.7 **March 19, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The json library is upgraded to version 20251224.

W-21506502
## [](#1-0-6)1.0.6 **July 10, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Mailchimp Marketing Connector in Anypoint Studio as intended.

W-16221353
## [](#1-0-5)1.0.5 **May 3, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-4)1.0.4 **June 28, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

Package conflicts no longer occur when using this connector with other specific connectors in a project.

W-13311688
## [](#1-0-3)1.0.3 **March 7, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

W-10740982
## [](#1-0-2)1.0.2 **January 28, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-10088
## [](#1-0-1)1.0.1 **December 17, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9640
## [](#1-0-0)1.0.0 **October 18, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Mailchimp Marketing Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Marketo Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Marketo Connector User Guide](https://docs.mulesoft.com/jp/marketo-connector/latest/) ## [](#3-0-11)3.0.11 **October 6, 2026** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

Marketo REST API

1.0
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-24405235, W-3300013
## [](#3-0-10)3.0.10 **February 26, 2026** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

Marketo REST API

1.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Google Guava library is upgraded to version 33.5.0-jre.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-io library is upgraded to version 2.21.0.

W-20592791
## [](#3-0-9)3.0.9 **November 14, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.0.0 and later

OpenJDK

8, 11, and 17

Marketo REST API

1.0
## [](#3-0-8)3.0.8 **August 21, 2024** ### Compatibility
Software Version

Mule

4.0.0 and later

OpenJDK

8 and 11

Marketo REST API

1.0
### Fixed Issues
Issue Resolution ID

The basepath now has a default value of /.

W-16327323
## [](#3-0-7)3.0.7 **May 26, 2023** ### Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### Fixed Issues
Issue Resolution ID

The org.mule.modules:mule-oauth-module library is upgraded to version 1.1.20 to fix reported security vulnerabilities.

W-13473428

The commons-codec:commons-codec library is upgraded to version 1.15 to fix reported security vulnerabilities.

W-13473428

The commons-io:commons-io library is upgraded to version 2.12.0 to fix reported security vulnerabilities.

W-13473428
## [](#3-0-6)3.0.6 **May 12, 2023** ### Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### Fixed Issues
Issue Resolution ID

The org.mule.connectors:mule-http-connector library is upgraded to version 1.7.3 to fix reported security vulnerabilities.

W-13179141
## [](#3-0-5)3.0.5 **October 14, 2022** ### Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### Fixed Issues
Issue ID

The connector now reconnects if the access token expires.

W-11900581
### Known Issues
Known Issue ID

When the connector reconnects, an error message is logged, without affecting functionality.

W-11902885
## [](#3-0-4)3.0.4 **June 2, 2022** ### Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### Fixed Issues
Issue ID

The connector now displays the correct error responses from Marketo.

W-11200188
## [](#3-0-3)3.0.3 **January 18, 2021** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### [](#fixed-issues-8)Fixed Issues - Fixed and issue in which the Import Custom Objects operation was throwing errors because the content type was not being properly specified. (SE-19222) ## [](#3-0-2)3.0.2 **September 21, 2020** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### [](#fixed-issues-9)Fixed Issues - The connector sent duplicate API requests for all operations (CONN-5729) ## [](#3-0-1)3.0.1 **August 30, 2018** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### [](#fixed-issues-10)Fixed Issues - Refresh token not working (SE-11759) ## [](#3-0-0)3.0.0 **May 7, 2018** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.0.0 and later

Marketo REST API

1.0
### [](#features)Features - Mule 4 and Anypoint Studio 7 compatible. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MCP Attribute-Based Access Control The MCP Attribute-Based Access Control policy controls access to tools, resources, and prompts based on user information such as Tiers, IP, Headers, or Claims. For configuration details, see [MCP Attribute-Based Access Control Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-attribute-access-control). ## [](#june-17-2026)June 17, 2026 ### What’s New - MCP Attribute-Based Access Control policy implementation version 1.0.6 is now supported by Omni Gateway. - MCP Attribute-Based Access Control policy definition version 1.0.2 is now supported by Omni Gateway. # MCP Connector Anypoint Connector for MCP (MCP Connector) uses the Model Context Protocol (MCP) to enable AI clients that support MCP to invoke and interact with APIs, connectors, and apps. Guide: [MCP Connector User Guide](https://docs.mulesoft.com/mcp-connector/latest/) ## [](#1-7-2)1.7.2 **October 2, 2026** ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

2.0.1

MCP Protocol

2025-06-18
### Fixed Issues
Issue Resolution ID

The MCP server no longer restores an idle-expired Streamable HTTP session from the L2 Object Store. Subsequent requests for the expired session now return the expected HTTP 404 response.

W-24003367

Server-initiated elicitation messages over Streamable HTTP now remain associated with the request that initiated them when concurrent requests use the same MCP session.

W-23859154

The Jackson 2 library is upgraded to version 2.22.3 and the Jackson 3 library is upgraded to version 3.2.3 to address reported security vulnerabilities.

W-3300013
## [](#1-7-1)1.7.1 **September 18, 2026** ### What’s New - The MCP Java SDK is upgraded from 2.0.0 to 2.0.1. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

2.0.1

MCP Protocol

2025-06-18
### Fixed Issues
Issue Resolution ID

The Streamable HTTP MCP client no longer fails with MCP:PARSE_ERROR and discards the server’s response when the server sends a keep-alive Server-Sent Events (SSE) frame while a response is pending.

W-24045650

The reactor-core library is upgraded to version 3.8.7 to address reported security vulnerabilities (CVE-2026-47857 and CVE-2026-47863).

W-24143109
## [](#1-7-0)1.7.0 **August 25, 2026** ### What’s New - The MCP Java SDK is upgraded from 1.0.1 to 2.0.0. Connector operations, sources, configuration, and error types are unchanged. - The MCP SDK’s JSON provider is migrated to Jackson 3. Connector operations, sources, configuration, and error types are unchanged. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

2.0.0

MCP Protocol

2025-06-18
### Fixed Issues
Issue Resolution ID

The Streamable HTTP transport no longer leaks resources by holding open a persistent Server-Sent Events (SSE) stream for every non-initialize request. Response framing is now deferred until an outbound message is actually sent: non-eliciting requests (such as tools/call, resources/read, and prompts/get) return a plain application/json response, and an SSE stream is opened only when the server must send a server-initiated message such as an elicitation.

As part of the Streamable HTTP framing change, a request that triggers a server-initiated message (an elicitation) now requires the client to advertise the SSE channel in its Accept header. Clients that call such operations must send:

Accept: application/json, text/event-stream

A client that sends only Accept: application/json and then triggers an elicitation receives an INVALID_REQUEST error. Spec-conformant MCP clients already send both media types and are unaffected. If you maintain a custom MCP client, ensure it advertises text/event-stream on requests that might elicit.

W-23293249
## [](#1-6-1)1.6.1 **July 17, 2026** ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

1.0.1

MCP Protocol

2025-06-18
### Fixed Issues
Issue Resolution ID

Session has not been initialized and Response was already initiated errors no longer occur with strict MCP clients that omit the session ID on the request following the initialize response.

W-23239922

The MCP server no longer accumulates a gradual memory leak in long-running server deployments.

W-22555872

The Jackson dependencies are upgraded to 2.22.1 to address security vulnerabilities.

W-3300013
## [](#1-6-0)1.6.0 **June 8, 2026** ### What’s New - MCP Connector now includes the **MCP Server - Create Elicitation** operation and the **MCP Client - Elicitation Listener** source. These capabilities implement the MCP elicitation protocol so servers can request additional structured input from clients during tool and resource execution. - Elicitation is opt-in through the new **Enable Elicitations** field on the client configuration. For multi-worker deployments, use Streamable HTTP server transport and configure an Object Store on the server connection so elicitation correlation is preserved across workers. SSE server transport is single-worker only. - Server connection configuration now includes the new **Elicitation Timeout Seconds**, **Elicitations Object Store**, and **Elicitation Polling Seconds** fields to route elicitation responses across replicas. - The **MCP Client - List Tools**, **MCP Client - List Resources**, and **MCP Client - List Prompts** operations now include the new **Additional Properties** field. Pass custom headers, correlation IDs, tenant identifiers, or other metadata on list calls. The values are propagated to the corresponding server-side listeners and are accessible from `attributes.additionalProperties`. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

1.0.1

MCP Protocol

2025-06-18
### Fixed Issues
Issue Resolution ID

The MCP client now refreshes the OAuth bearer token automatically when an outbound request receives an HTTP 401 response, and the resulting error is reclassified as a connectivity error so it is eligible for reconnection.

W-22677666

Events emitted by the MCP Server - On New Session Listener source are no longer counted toward Usage-Based Pricing metering. The source fires as a byproduct of the upstream HTTP listener trigger, so its events were being double-counted.

W-21663653
## [](#1-5-0)1.5.0 **May 1, 2026** ### What’s New - MCP Connector now includes the **MCP Client - Get Prompt** and **MCP Client - List Prompts** operations, and the **MCP Server - Prompt Listener** source. Expose server-side prompt templates with typed arguments and consume them from clients, with responses supporting text, image, embedded resource, and resource link content. - The **MCP Client - Call Tool** operation now includes the new **Extract Structured Content** field. Define tool parameter and output schemas using either inline JSON or external files, fully supported by robust design-time schema validation. With this, the connector now also includes the new `MCP:SCHEMA_VALIDATION_FAILED` error. - The connector now includes response attributes to support structured client-side error handling with HTTP response details. With this, the connector now also includes the new `MCP:UNAUTHORIZED` error. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

1.0.1

MCP Protocol

2025-06-18
## [](#1-4-0)1.4.0 **March 22, 2026** ### What’s New - The MCP Java SDK is upgraded to the latest release version (1.0.0). - Both the server and client transports now default to 2025-06-18 as the preferred version of the protocol. - Both the server and client transports now set the `Mcp-Protocol-Version` header to the version negotiated upon connection initialization. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

1.0.0

MCP Protocol

2025-06-18
### Fixed Issues
Issue Resolution ID

When no audience is defined in the Mule flow, TextContent responses for tool calls no longer serialize an empty audience array in annotations. An empty array could cause some MCP clients to interpret the content as being visible to nobody and filter it out.

W-21425262
## [](#1-3-1)1.3.1 **January 16, 2026** ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

0.11.2
### Fixed Issues
Issue Resolution ID

Nested objects are now properly serialized for downstream consumption.

W-20405721

In the MCP Server - On New Session Listener source, a NullPointerException error no longer occurs in the response builder when the header isn’t defined.

W-20437648

Tool parameters are now validated according to the JSON schema before execution.

W-20037056
## [](#1-3-0)1.3.0 **November 13, 2025** ### What’s New - The **MCP Server - On New Session Listener** source now supports custom rejection headers with the new **Reject With Headers** field. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

0.11.2
### Fixed Issues
Issue Resolution ID

In the MCP Server - On New Session Listener source, the Reject With Status Code field now correctly returns custom rejection status codes instead of defaulting to 500.

W-19387519

The connector now properly cleans up tracked inbound requests even when exceptions occur during message processing, preventing memory leaks that could accumulate over time.

W-20037035
## [](#1-2-1)1.2.1 **September 11, 2025** ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

0.11.2
### Fixed Issues
Issue Resolution ID

The MCP server now responds with HTTP 404 for expired sessions, and the MCP client now properly handles session expiration by creating a new session when receiving HTTP 404 responses.

W-19178802

Connection and disconnection handling is now improved because disconnect methods are now properly subscribed and executed.

W-19264682
## [](#1-2-0)1.2.0 **August 6, 2025** ### What’s New - MCP Connector now supports distributed tracing. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

0.10.0
## [](#1-1-0)1.1.0 **July 18, 2025** ### What’s New - A **Default Request Headers** parameter is added to both the SSE Client and Streamable HTTP Client connection types within the MCP Connector’s Client configuration. This parameter lets you specify custom headers to send with every request to the MCP server. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

0.10.0
### Fixed Issues
Issue Resolution ID

Serialization errors with ObjectStore v2 no longer occur.

W-19045311
## [](#1-0-0)1.0.0 **June 26, 2025** ### What’s New - MCP Connector 1.0.0 is not backward-compatible with the 0.1.0-BETA version of this connector. For more information, see [Upgrading MCP Connector to Version 1.0.0](https://docs.mulesoft.com/mcp-connector/latest/mcp-connector-upgrade-migrate). - Support for the Streamable HTTP transport method is added. - You can now add custom response headers on every exposed endpoint (including `/sse`, `/messages`, and the new `/mcp`). - You no longer need to add the `mule.http.service.implementation=NETTY` system property. ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17

MCP Java SDK

0.10.0
## [](#0-1-0-beta-deprecated)0.1.0-BETA (Deprecated) **April 15, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/mcp-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [MCP Connector User Guide](https://docs.mulesoft.com/mcp-connector/latest/). ### Compatibility
Software Version

Mule

4.9.3 and later

OpenJDK

17
## [](#see-also)See Also - [MCP Connector User Guide](https://docs.mulesoft.com/mcp-connector/latest/) - [MCP Connector Reference](https://docs.mulesoft.com/mcp-connector/latest/mcp-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MCP Global Access The MCP Global Access policy restricts which MCP tools are exposed by defining Allow and Block rules. For configuration details, see [MCP Global Access Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-global-access). ## [](#june-17-2026)June 17, 2026 ### What’s New - MCP Global Access policy implementation version 1.0.2 is now supported by Omni Gateway. - MCP Global Access policy definition version 1.0.1 is now supported by Omni Gateway. # MCP Payload Optimization The MCP Payload Optimization policy reduces tool response token consumption using one or more configurable methods: remove structural noise, trim oversized responses to match agent intent, or compress repeated structures into TOON. For configuration details, see [MCP Payload Optimization Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-payload-optimization). ## [](#july-11-2026)July 11, 2026 ### What’s New - MCP Payload Optimization policy implementation version 1.2.0 is now supported by Omni Gateway. - MCP Payload Optimization policy definition version 1.2.0 is now supported by Omni Gateway. ## [](#july-10-2026)July 10, 2026 ### What’s New - MCP Payload Optimization policy implementation version 1.0.2 is now supported by Omni Gateway. - MCP Payload Optimization policy definition version 1.0.1 is now supported by Omni Gateway. # MCP PII Detector The MCP PII Detector policy blocks elicitation responses containing personally identifiable information (PII) from reaching MCP servers. For configuration details, see [MCP Personally Identifiable Information (PII) Detector Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-pii-detector). ## [](#june-05-2026)June 05, 2026 ### What’s New - MCP PII Detector policy implementation version 1.0.2 is now supported by Omni Gateway. ## [](#may-13-2026)May 13, 2026 ### What’s New - MCP PII Detector policy definition version 1.0.1 is now supported by Omni Gateway. # MCP Schema Validation The MCP Schema Validation policy validates MCP requests to ensure they conform to the MCP specification For configuration details, see [MCP Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-schema-validation). ## [](#september-2-2026)September 2, 2026 ### Fixed Issues - MCP Schema Validation policy definition and implementation version 1.3.0 is now supported by Omni Gateway. - The policy no longer rejects valid MCP methods from the MCP `2025-06-18` and `2025-11-25` specifications. These methods are now correctly recognized: - `elicitation/create` - `sampling/createMessage` - `roots/list` - `notifications/message` - `notifications/resources/list_changed` - `notifications/resources/updated` - `notifications/prompts/list_changed` - `notifications/tools/list_changed` - `notifications/elicitation/complete` ## [](#august-10-2026)August 10, 2026 ### What’s New - MCP Schema Validation policy definition and implementation version 1.2.0 is now supported by Omni Gateway. - Added the **Tool Poisoning Detection** parameter, which detects tool-poisoning attacks against MCP `tools/list` responses by pinning the trusted tool set from the API’s Anypoint Exchange asset and comparing every backend `tools/list` response against it. ## [](#may-20-2026)May 20, 2026 ### What’s New - MCP Schema Validation policy implementation version 1.1.2 is now supported by Omni Gateway. ## [](#april-20-2026)April 20, 2026 ### What’s New - MCP Schema Validation policy definition version 1.1.1 is now supported by Omni Gateway. # MCP Support The MCP Support policy adds MCP support to an Omni Gateway MCP server instance. This policy is required for your MCP server instance to function properly. For configuration details, see [MCP Support Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-support). ## [](#august-12-2026)August 12, 2026 ### What’s New - MCP Support policy definition and implementation version 1.1.1 is now supported by Omni Gateway. - Added the **Inject MCP Element Headers** parameter, which injects the MCP primitive as request headers for downstream policy use. The policy sets `x-ms-mcp-element-id` to the identifier and `x-ms-mcp-element-type` to the kind (`tool`, `prompt`, or `resource`). ## [](#june-08-2026)June 08, 2026 ### What’s New - MCP Support policy implementation version 1.0.9 is now supported by Omni Gateway. ## [](#april-20-2026)April 20, 2026 ### What’s New - MCP Support policy definition version 1.0.1 is now supported by Omni Gateway. # MCP Tool Mapping The MCP Tool Mapping policy redefines tool names and descriptions to reduce prompt complexity and improve LLM comprehension. For configuration details, see [MCP Tool Mapping Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-tool-mapping). ## [](#june-04-2026)June 04, 2026 ### What’s New - MCP Tool Mapping policy implementation version 1.0.6 is now supported by Omni Gateway. ## [](#may-05-2026)May 05, 2026 ### What’s New - MCP Tool Mapping policy definition version 1.0.1 is now supported by Omni Gateway. # MCP Tools Progressive Disclosure The MCP Tools Progressive Disclosure policy reduces context window token cost by exposing tools on-demand through search. For configuration details, see [MCP Tools Progressive Disclosure Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-progressive-disclosure). ## [](#july-15-2026)July 15, 2026 ### What’s New - MCP Tools Progressive Disclosure policy implementation version 1.0.0 is now supported by Omni Gateway. - MCP Tools Progressive Disclosure policy definition version 1.0.0 is now supported by Omni Gateway. # Message Logging The Message Logging policy logs custom messages using information from incoming requests, responses from the backend, or information from other policies applied to the same API endpoint. For configuration details, see [Message Logging Policy](https://docs.mulesoft.com/gateway/latest/policies-included-message-logging). ## [](#october-1-2026)October 1, 2026 ### What’s New - Message Logging policy definition version 2.0.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#september-2-2026)September 2, 2026 ### What’s New - The policy now supports data masking to detect and mask personally identifiable information (PII), such as email addresses, in log messages before they are written. You can select built-in PII types (Email, US SSN, Credit Card, and Phone Number) or add custom regex patterns. Request and response bodies are forwarded to the upstream service unchanged. - Message Logging policy implementation version x.x.x is now supported by Omni Gateway. - Message Logging policy definition version x.x.x is now supported by Omni Gateway. ## [](#february-27-2025)February 27, 2025 ### What’s New - Message Logging policy implementation version 1.2.1 is now supported by Omni Gateway. - Message Logging policy definition version 2.0.1 is now supported by Omni Gateway. # Message Logging ## [](#2-0-3)2.0.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#2-0-1)2.0.1 **August 5, 2022** Important: The fixes implemented in this release are focused on the API Manager UI. Applying this policy using API Manager will continue to download the version 2.0.0 implementation for Mule Runtime Engine. ### [](#fixed-issues)Fixed issues - Renamed Mule Expression to DataWeave expression in the field descriptions of the policy schemas. - Removed the Java package structure from the Category field description of the policy schema. ## [](#2-0-0)2.0.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. - Changed policy configuration schema. ## [](#1-0-0)1.0.0 Mar 22, 2018 ### [](#minimum-mule-version)Minimum Mule Version 4.1.1 ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft .NET Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft .NET (Microsoft .NET Connector) lets you execute native .NET code in a Mule app. Guide: [Microsoft .NET Connector](https://docs.mulesoft.com/jp/microsoft-dotnet-connector/latest/) Reference: [Microsoft .NET Connector Reference](https://docs.mulesoft.com/jp/microsoft-dotnet-connector/latest/microsoft-dotnet-connector-reference) ## [](#3-1-14)3.1.14 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#3-1-13)3.1.13 **August 17, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#3-1-12)3.1.12 **July 21, 2026** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.1.

  • The log4j library is upgraded to version 2.26.1.

  • The netty library is upgraded to version 4.2.16-Final.

W-23452737
## [](#3-1-11)3.1.11 **June 25, 2026** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.0.

  • The log4j library is upgraded to version 2.26.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The netty library is upgraded to version 4.2.15-Final.

W-23136105
## [](#3-1-10)3.1.10 **May 26, 2026** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The guava library is upgraded to version 33.6.0-jre.

  • The log4j library is upgraded to version 2.25.4.

W-22406285
## [](#3-1-9)3.1.9 **March 22, 2026** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.21.0.

  • The log4j library is upgraded to version 1.2.17-atlassian-0.4.

W-21334686
## [](#3-1-8)3.1.8 **October 8, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#3-1-7)3.1.7 **May 2, 2023** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Upgraded the Jackson Core library from com.fasterxml.jackson.core:jackson-core:2.13.1 to com.fasterxml.jackson.core:jackson-core:2.15.0.

W-12665440
## [](#3-1-6)3.1.6 **October 11, 2022** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853430
## [](#3-1-5)3.1.5 **April 5, 2022** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920471
## [](#3-1-4)3.1.4 **January 5, 2022** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9841
## [](#3-1-3)3.1.3 **December 17, 2021** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9621
## [](#3-1-2)3.1.2 **August 26, 2021** ### Compatibility
App/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

N/A
## [](#3-1-1)3.1.1 **September 08, 2020** ### [](#compatibility-14)Compatibility Microsoft .NET Connector is compatible with:
App/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-11)Fixed Issues - Fixed commons-io vulnerability ## [](#3-1-0)3.1.0 **August 20, 2020** ### [](#compatibility-15)Compatibility Microsoft .NET Connector is compatible with:
App/Service Version

Mule

4.1.1 and later

Java

8 and 11
### [](#fixed-issues-12)Fixed Issues - Added support for Java 11. ## [](#3-0-4)3.0.4 **May 29, 2020** ### [](#compatibility-16)Compatibility Microsoft .NET Connector is compatible with:
App/Service Version

Mule

4.1.1 and later

Java

8
### [](#fixed-issues-13)Fixed Issues - Updated the `com.fasterxml.jackson.core:jackson-databind:2.9.0` dependency to `com.fasterxml.jackson.core:jackson-databind:2.11.0` to fix vulnerability issues. (CONN-6045) - Deleted the following dependencies to fix vulnerability issues (CONN-6045): - `log4j:log4j:1.2.17` - `dotnet:dotnetutils:1.0.0.0` ## [](#3-0-3)3.0.3 **February 14, 2020** ### [](#compatibility-17)Compatibility Microsoft .NET Connector is compatible with:
App/Service Version

Mule

4.1.1 and later

Java

8
### [](#fixed-issues-14)Fixed Issues - Test connection failed. (SE-14227) - Metadata was not populating. (SE-14228) - Leaving the Arguments input blank or setting it to null, always caused an error. (SE-14191) ## [](#3-0-2)3.0.2 **September 12, 2019** ### [](#compatibility-18)Compatibility Microsoft .NET Connector is compatible with:
App/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-15)Fixed Issues - Redeployment fails when using the .NET Connector in Windows. (SE-9882) ### [](#known-issues)Known issues - The .NET connector is not compatible with Mule 4.2.0 and later. ## [](#3-0-1)3.0.1 **August 14, 2019** ### [](#compatibility-19)Compatibility The Microsoft .NET Connector is compatible with:
App/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-16)Fixed Issues - Microsoft .NET connector was unable to handle complex objects and threw an Invalid JavaScript property identifier error. (SE-9730) ### [](#known-issues-2)Known issues - Redeployment fails when using the .NET connector on Windows. (SE-9882) - The .NET connector is not compatible with Mule 4.2.0 and later. ## [](#3-0-0)3.0.0 **June 22, 2018** This release provides Mule 4 support. ### [](#compatibility-20)Compatibility The Microsoft .NET Connector is compatible with:
App/Service Version

Mule

4.1.1 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Dynamics 365 Business Central Connector Release Notes Anypoint Connector for Microsoft Dynamics 365 Business Central (Microsoft Dynamics 365 Business Central Connector) enables you to manage entities for your companies in Microsoft Dynamics 365 Business Central. Guide: [Microsoft Dynamics 365 Business Central Connector User Guide](https://docs.mulesoft.com/jp/microsoft-dynamics-365-business-central-connector/latest/) ## [](#1-0-7)1.0.7 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-6)1.0.6 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-databind and jackson-core libraries are upgraded to version 2.22.1 to address reported security vulnerabilities.

W-23441818
## [](#1-0-5)1.0.5 **July 10, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Jackson library is upgraded to version 2.22.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

W-23265456
## [](#1-0-4)1.0.4 **March 22, 2026** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Jackson library is upgraded to version 2.18.6.

  • The commons-io library is added at version 2.21.0.

  • The commons-lang3 library is added at version 3.19.0.

W-21334699
## [](#1-0-3)1.0.3 **March 7, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-2)1.0.2 **January 19, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12134922
## [](#1-0-1)1.0.1 **June 14, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11207823
## [](#1-0-0)1.0.0 **January 5, 2022** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Microsoft Dynamics 365 Business Central Connector Reference Guide. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

JDK Version

1.8
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Dynamics 365 Cloud Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Dynamics 365 enables you to connect to the Microsoft Dynamics 365 Cloud instance. Guide: [Microsoft Dynamics 365 Connector](https://docs.mulesoft.com/jp/microsoft-dynamics-365-connector/latest/) ## [](#2-6-9)2.6.9 **October 5, 2026** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x

OpenJDK

8, 11, and 17
Additional information regarding available versions can be found here: - [Microsoft Dynamics CRM online releases](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [Business applications release notes](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue Resolution ID

Bulk operations now set the item exception message to Could not read error response body when the error response body can’t be read. Previously, that message was null.

W-22360305

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.3.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-lang3 library is pinned to version 3.20.0.

  • The commons-codec library is upgraded to version 1.22.1.

  • The gson library is upgraded to version 2.14.0.

  • The commons-collections library is replaced with commons-collections4 version 4.6.0.

  • The odata-commons-api and odata-client-api libraries are upgraded to version 4.10.0.

  • The Olingo OData2 API and core libraries are upgraded to version 2.0.13.

  • The Apache HttpClient library is upgraded to version 4.5.14.

W-24113940, W-24137088, W-24262985
## [](#2-6-8)2.6.8 **April 30, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x

OpenJDK

8, 11, and 17
Additional information regarding available versions can be found here: - [Microsoft Dynamics CRM online releases](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [Business applications release notes](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ## [](#2-6-7)2.6.7 **January 22, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [Microsoft Dynamics CRM online releases](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [Business applications release notes](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core library is upgraded to version 2.16.1 to address reported security vulnerabilities.

W-14837336
## [](#2-6-6)2.6.6 **July 19, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [Microsoft Dynamics CRM online releases](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [Business applications release notes](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue Resolution ID

The Retrieve multiple operation now supports predefined queries.

W-13771860
## [](#2-6-5)2.6.5 **May 15, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue Resolution ID

The On Modified Object source now fetches all records.

W-13189064
## [](#2-6-4)2.6.4 **October 7, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11845806
## [](#2-6-3)2.6.3 **October 3, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

The com.google.guava library is removed to address reported security vulnerabilities.

W-11817283
## [](#2-6-2)2.6.2 **September 27, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

The Delete Multiple operation now returns an Invalid property error message if one of the provided IDs is not valid when using a single transaction.

W-11492053

The output of the Delete Multiple operation now matches the expected outcome.

W-11768451

The On Modified Object source now polls new modified events when deployed locally.

W-11730039
## [](#2-6-1)2.6.1 **August 10, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

The Create Multiple, Delete Multiple, and Update Multiple operations now return an error message, when appropriate, from the Dynamics 365 Web API instead of a BadRequest error response.

W-11531241
## [](#2-6-0)2.6.0 **August 2, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

The Create Multiple, Delete Multiple, and Update Multiple operations now contain the new Continue On Error field.

W-11460016
## [](#2-5-5)2.5.5 **April 5, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920487
## [](#2-5-4)2.5.4 **February 11, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

Fixed reconnection and refresh token functionality for all of the sources, the Retrieve Multiple operation, and the Retrieve Multiple by Query operation.

SE-24323
## [](#2-5-3)2.5.3 **January 4, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9844
## [](#2-5-2)2.5.2 **December 17, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9544
## [](#2-5-1)2.5.1 **November 11, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### Fixed Issues
Issue ID

Fixed reported security vulnerabilities.

CONN-9262

The On Modified Object and On New Object sources retrieved only the first page of multiple records.

CONN-9142
## [](#2-5-0)2.5.0 **November 8, 2021** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.2.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#features)Features - Added support for the OAuth Client Credentials authentication mechanism. - Added the **On Deleted Object** source. - The **Expand** parameter is now supported by the **Retrieve Multiple By Query** operation. ## [](#2-4-10)2.4.10 **August 26, 2021** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-15)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#2-4-9)2.4.9 **March 18, 2021** ### [](#compatibility-18)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-16)Fixed Issues Fixed the issue that limited the Read Timeout parameter to a maximum of 30 seconds when using bulk-operations. (SE-19939) ## [](#2-4-8)2.4.8 **March 15, 2021** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-17)Fixed Issues - Fixed reported security vulnerabilities for the connector. ## [](#2-4-7)2.4.7 **January 26, 2021** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-18)Fixed Issues - Fixed the encoding issue with OData queries. (SE-19343) ## [](#2-4-6)2.4.6 **January 8, 2021** ### [](#compatibility-21)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-19)Fixed Issues - Fixed the encoding issue with OData queries. (SE-19033) ## [](#2-4-5)2.4.5 **November 9, 2020** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-20)Fixed Issues - Actions with bounded entities did not work for the **Do action** operation. (CONN-6391) - Fixed the output metadata for the **Do action** operation. (CONN-6391) - Upgraded the following dependency to fix vulnerability issues: - com.fasterxml.jackson.core » jackson-databind upgraded from 2.10.1 to 2.11.3 ## [](#2-4-4)2.4.4 **October 29, 2020** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-21)Fixed Issues - Fixed the output metadata for the **Retrieve multiple by query** operation. (CONN-6429) - Upgraded the following dependencies to fix vulnerability issues: - `org.apache.httpcomponents:httpclient` upgraded from 4.5.3 to 4.5.13 - `com.fasterxml.jackson.core:jackson-databind` upgraded from 2.10.1 to 2.11.3 ## [](#2-4-3)2.4.3 **October 21, 2020** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-22)Fixed Issues Fixed the DataSense Query Language special character issue. ## [](#2-4-2)2.4.2 **September 18, 2020** ### [](#compatibility-25)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-23)Fixed Issues Fixed Apache Commons IO vulnerability ## [](#2-4-1)2.4.1 **September 16, 2020** ### [](#compatibility-26)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-24)Fixed Issues - Fixed the reconnection mechanism for the OAuth username password connection provider for the following operations: - Invoke - DoAction - CreateMultiple - DeleteMultiple - UpdateMultiple - Disassociate ## [](#2-4-0)2.4.0 **September 10, 2020** ### [](#compatibility-27)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-25)Fixed Issues - Sending special characters (such as ®, è, and so forth) to Microsoft Dynamics 365 in an Invoke operation resulted in errors. (SE-16447) ### [](#features-2)Features - Added a field for global encoding at the configuration level. The same field is in the Anypoint Studio Advanced tab for the following operations: Invoke, DoAction, CreateMultiple, UpdateMultiple, Update, and Create. ### [](#known-issues)Known Issues - The refresh token mechanism does not work for the OAuth2 connection type when using the On new object and On modified object input sources. (CONN-6139) ## [](#2-3-9)2.3.9 **May 20, 2020** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-26)Fixed Issues - Using the OAuth Username Password connection type for the On new object and On modified object input sources resulted in connectivity errors. (SE-14048) - Error messages were not logged when performing an invalid operation. (CONN-6073) ### [](#known-issues-2)Known Issues - The refresh token mechanism does not work for the OAuth2 connection type when using the On new object and On modified object input sources. (CONN-6139) ## [](#2-3-8)2.3.8 **May 4, 2020** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-27)Fixed Issues - Upgraded the following dependencies to fix vulnerability issues: - com.fasterxml.jackson.core » jackson-core upgraded from 2.7.8 to 2.10.1 - com.fasterxml.jackson.core » jackson-databind upgraded from 2.7.8 to 2.10.1 - commons-codec » commons-codec upgraded from 1.6 to 1.14 ## [](#2-3-7)2.3.7 **April 29, 2020** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-28)Fixed Issues - The overall response time was too high for paginated operations (retrieveMultiple and retrieveMultipleByQuery). (SE-15699) The issue relates to an internal API call the connector performs to check if the connection is still valid. The API call was changed to a less expensive one in terms of time execution. All operations benefit from this performance improvement. ## [](#2-3-6)2.3.6 **March 23, 2020** ### [](#compatibility-31)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-29)Fixed Issues - The `Create multiple` operation threw an exception when one of the entities could not be created. (SE-14963) To fix this error, the `Scope` parameter for the OAuth connection was deprecated. Use the `Scopes` parameter instead. The `Scope` parameter was deprecated to keep backwards compatibility. It will be removed in future versions. ## [](#2-3-5)2.3.5 **January 31, 2020** ### [](#compatibility-32)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-30)Fixed Issues Fixed the issue where the read timeout was not taken into consideration. (SE-14233) ## [](#2-3-4)2.3.4 **January 21, 2020** ### [](#compatibility-33)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-31)Fixed Issues - Fixed the issue where reconnection did not work properly for paged operations. (SE-13767) - Fixed the issue where a `DYNAMICS:UNKNOWN` error occurred when trying to reconnect. (SE-14048) ## [](#2-3-3)2.3.3 **January 8, 2020** ### [](#compatibility-34)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-32)Fixed Issues Create Entity operation was failing when one of the entity fields was an array. (SE-14269) ## [](#2-3-2)2.3.2 **December 13, 2019** ### [](#compatibility-35)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-33)Fixed Issues The access token now correctly refreshes on the connector’s side (SE-13767), but this issue is still not fixed because it depends on a Mule runtime engine fix version (MULE-17812). Once MULE-17812 is released, the fix will work. ## [](#2-3-1)2.3.1 **February 19, 2019** ### [](#compatibility-36)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x, v9.x (latest supported 365 server is 9.1.0000.19865 - 2020 release wave 1)
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#features-3)Features The connector now supports API version 9.x, and potentially future ones, by making the version number configurable. The default in version 2.3.1 is 9.0. ## [](#2-2-1)2.2.1 **October 25, 2018** ### [](#compatibility-37)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-34)Fixed Issues Fixed issue regarding Edm.GUID types which were sent as a string and because of a header dynamics wasn’t able to parse the request. The header was changed and types are handled differently. ## [](#2-2-0)2.2.0 **August 28, 2018** ### [](#compatibility-38)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#features-4)Features - Create Modified Object trigger - Create New Object trigger ## [](#2-1-2)2.1.2 **October 25, 2018** ### [](#compatibility-39)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-35)Fixed Issues Fixed issue regarding Edm.GUID types which were sent as a string and because of a header dynamics wasn’t able to parse the request. The header was changed and types are handled differently. ## [](#2-1-1)2.1.1 **August 21, 2018** ### [](#compatibility-40)Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Dynamics 365 API

v8.x
Additional information regarding available versions can be found here: - [https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6](https://support.microsoft.com/en-us/topic/microsoft-dynamics-365-releases-17837bba-5689-2216-22c0-e8c7a032c3a6) - [https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce](https://learn.microsoft.com/en-us/business-applications-release-notes/dynamics/released-versions/dynamics-365ce) ### [](#fixed-issues-36)Fixed Issues Microsoft Dynamics 365 Connector didn’t renew the token. This issue was fixed by reimplementing error handling. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Dynamics 365 for Finance & Operations Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Dynamics 365 for Finance & Operations allows you to connect to a Microsoft Dynamics 365 for Finance & Operations instance. Guide: [Microsoft 365 Ops Connector User Guide](https://docs.mulesoft.com/jp/microsoft-365-ops-connector/latest/) ## [](#3-1-13)3.1.13 **May 20, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
## [](#3-1-12)3.1.12 **December 7, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue Resolution ID

The Retrieve Multiple operation now processes custom query parameters correctly.

W-14478124
## [](#3-1-11)3.1.11 **October 11, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue Resolution ID

The OAuth token is now properly refreshed when it expires.

W-14225689
## [](#3-1-10)3.1.10 **March 28, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue Resolution ID

The connector no longer throws an INVALID_INPUT error when using the DateTimeOffset type.

W-12664480

The Retrieve operation no longer returns only the first 10,000 records since the next page link is not available in the response.

W-12547821
## [](#3-1-9)3.1.9 **October 11, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853431
## [](#3-1-8)3.1.8 **June 29, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

The input for Execute operation is now sent properly to Microsoft Dynamics.

W-11307571
## [](#3-1-7)3.1.7 **May 19, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

The connector now contains custom logic to configure properties of complex types when creating entities. For more information, refer to Additional Configuration Information.

W-11112270
## [](#3-1-6)3.1.6 **April 5, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920488
## [](#3-1-5)3.1.5 **January 4, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9828
## [](#3-1-4)3.1.4 **December 17, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9545
### Known Issues
Known Issue ID

For Mule runtime engine 4.3.0-202104 and later, if the token expires, the Acknowledge Export From Recurring Job operation is not retried properly.

MULE-19262
## [](#3-1-3)3.1.3 **November 1, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

The connector received a 401 error code when a subsequent request used the same token.

SE-23238
### Known Issues
Known Issue ID

For Mule runtime engine 4.3.0-202104 and later, if the token expires, the Acknowledge Export From Recurring Job operation is not retried properly.

MULE-19262
## [](#3-1-2)3.1.2 **October 26, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

The response payload was not accessible when the connector received a 500 response code.

SE-22453
### Known Issues
Known Issue ID

For Mule runtime engine 4.3.0-202104 and later, if the token expires, the Acknowledge Export From Recurring Job operation is not retried properly.

MULE-19262
## [](#3-1-1)3.1.1 **August 26, 2021** ### Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

N/A
### Known Issues
Known Issue ID

For Mule runtime engine 4.3.0-202104 and later, if the token expires, the Acknowledge Export From Recurring Job operation is not retried properly.

MULE-19262
## [](#3-1-0)3.1.0 **August 23, 2021** ### What’s New - Added four new operations: - **Acknowledge Export From Recurring Job** - **Create** - **Dequeue Recurring Job** - **Export Data From Recurring Job** - Added the **Expand** parameter, which offers filtering for the **Retrieve Multiple By Query** operation. ### Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### Known Issues
Known Issue ID

For Mule runtime engine 4.3.0-202104 and later, if the token expires, the Acknowledge Export From Recurring Job operation is not retried properly.

MULE-19262
## [](#3-0-3)3.0.3 **June 15, 2021** ### [](#compatibility-15)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### [](#known-issues-6)Known Issues - For Mule 4.2.1 and 4.2.2, when using the OAuth 2.0 client credentials, you must install the Mule runtime engine patch from Microsoft Dynamics 365 for Finance & Operations Connector 3.0 so that the connector automatically reconnects for paged operations. (SE-20870) ### [](#fixed-issues-13)Fixed Issues - There was an error when calling an existing custom service with parameters that were not primitive types. (SE-21231) ## [](#3-0-2)3.0.2 **May 18, 2021** ### [](#compatibility-16)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### [](#known-issues-7)Known Issues The Mule runtime engine patch from version 3.0.0 is required for Mule 4.2.1 and 4.2.2 so that the connector automatically reconnects for paged operations when using OAuth 2.0 client credentials. (SE-20870) ### [](#fixed-issues-14)Fixed Issues Added four missing comparison operators (`gt`, `lt`, `ge`, `le`) to use in query operations. ## [](#3-0-1)3.0.1 **November 18, 2020** ### [](#compatibility-17)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### [](#known-issues-8)Known Issues The Mule runtime engine patch from version 3.0.0 is required for Mule 4.2.1 and 4.2.2 so that the connector automatically reconnects for paged operations when using OAuth 2.0 Client Credentials. ### [](#fixed-issues-15)Fixed Issues Fixed the reported vulnerabilities for the connector. ## [](#3-0-0)3.0.0 **October 30, 2020** ### [](#compatibility-18)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
### [](#features)Features - Added the OAuth 2.0 Client Credentials Grant authentication method. - The Connection Timeout and Read Timeout parameters can now have different Time Units. ### [](#known-issues-9)Known Issues - A patch is required for Mule runtime engine 4.2.1 and 4.2.2 so that the connector will automatically reconnect for paged operations when using OAuth 2.0 Client Credentials. ### [](#other)Other - Removed DYNAMICS365FOROPERATIONS:UNKNOWN Error type - Connection Timeout is now available only for OAuth Username Password connection type. ## [](#2-3-0)2.3.0 **September 24, 2020** ### [](#compatibility-19)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 Update 30 (November 2019)
The full list of the available Microsoft Dynamics 365 for Finance & Operations versions is available here: [https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page](https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page) ### [](#features-2)Features Support for Microsoft Dynamics 365 for Finance & Operations version 10.0.6 Update 30 ## [](#2-2-0)2.2.0 **September 16, 2020** ### [](#compatibility-20)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 (November 2019)
The full list of the available Dynamics 365 for Finance & Operations versions is available here: [https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page](https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page) ### [](#features-3)Features - TLS support was added for all the connection providers. ## [](#2-1-2)2.1.2 **July 13, 2020** ### [](#compatibility-21)Compatibility The Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 (November 2019)
The full list of the available Dynamics 365 for Finance & Operations versions is available here: [https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page](https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page) ### [](#fixed-issues-16)Fixed Issues Fixed reported vulnerabilities for the connector. ## [](#2-1-1)2.1.1 **May 4, 2020** ### [](#compatibility-22)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 (November 2019)
The full list of the available Dynamics 365 for Finance & Operations versions is available here: [https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page](https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page) ### [](#fixed-issues-17)Fixed Issues Upgraded commons-codec:commons-codec:1.10 to commons-codec:commons-codec:1.13 in order to fix vulnerability issues. ## [](#2-1-0)2.1.0 **March 20, 2020** ### [](#compatibility-23)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 (November 2019)
The full list of the available Dynamics 365 for Finance & Operations versions is available here: [https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page](https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page) ### [](#features-4)Features - Added the new error types TIMEOUT, INVALID\_INPUT, and NOT\_FOUND to enable a more granular exception handling. - When the OAuth2 token expires, the connector now automatically refreshes the token and retries the operation, whether or not there is a configured reconnection strategy. However, it is recommended that you configure a reconnection strategy, because Mule uses the configured reconnection strategy to handle connection issues, such as a lost internet connection. ### [](#fixed-issues-18)Fixed Issues - Anypoint Studio displayed only one value in Service group and Service name list for the Execute operation. - The output Data Sense for the Retrieve multiple and Retrieve multiple by Query operations displayed all fields for the specified entity. Now, the Data Sense displays only the fields mentioned in the SELECT part of the query. - The Read Timeout property is now set properly on the HTTP client used to make API requests. - The response for the Execute operation is now parsed correctly by the connector. - When using the OAuth Authorization Code Connection provider, the proxy parameters are now set correctly on the underlying HTTP client. - The Retrieve Multiple operation did not support the whole URL. Now you can use URLs like this one: `https://my-dynamics-instance/data/Customers?\$select=WarehouseId,AddressLatitude`. ### [](#deprecrated-connection-type)Deprecrated Connection Type The Oauth Username Password connection type has been deprecated. ## [](#2-0-1)2.0.1 **October 23, 2019** ### [](#compatibility-24)Compatibility The Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 (November 2019)
The full list of the available Dynamics 365 for Finance & Operations versions is available here: [https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page](https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page) ### [](#features-5)Features - None. ### [](#fixed-issues-19)Fixed Issues - Fixed a bug when a query used the equals comparison. \[SE-10937\] - Fixed a bug with the metadata in **Retrieve multiple by query** operation. \[SE-10937\] - Fixed upload file bug on the **Import data recurring job** operation. \[SE-13295\] ## [](#2-0-0)2.0.0 **January 27, 2018** ### [](#compatibility-25)Compatibility Microsoft Dynamics 365 for Finance & Operations Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

Microsoft Dynamics 365 for Finance & Operations

1611 (November 2016) up to 10.0.6 (November 2019)
The full list of the available Dynamics 365 for Finance & Operations versions is available here: [https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page](https://learn.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Dynamics AX 2012 Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Microsoft Dynamics AX Connector User Guide](https://docs.mulesoft.com/jp/microsoft-dynamics-ax-connector/latest/) ## [](#2-0-7)2.0.7 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The neethi library is upgraded to version 3.2.3 to address reported security vulnerabilities.

W-24113945
## [](#2-0-6)2.0.6 **August 17, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-0-5)2.0.5 **August 15, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-0-4)2.0.4 **September 20, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CONN-8802
## [](#2-0-3)2.0.3 **November 18, 2020** ### [](#compatibility-5)Compatibility Microsoft Dynamics AX 2012 Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-3)Fixed Issues - Fixed the Apache `cxf-rt-transports-http` vulnerability issue. ## [](#2-0-2)2.0.2 **May 8, 2020** ### [](#compatibility-6)Compatibility Microsoft Dynamics AX 2012 Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-4)Fixed Issues - Deleted the following dependency to fix vulnerability issues (CONN-5896): - `org.apache.servicemix.jbi:org.apache.servicemix.jbi.commands:1.6.1` ## [](#2-0-1)2.0.1 **May 4, 2020** ### [](#compatibility-7)Compatibility Microsoft Dynamics AX 2012 Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-5)Fixed Issues - Upgraded the following dependencies to fix vulnerability issues (CONN-5896): - `com.fasterxml.woodstox:woodstox-core:5.0.3` to `com.fasterxml.woodstox:woodstox-core:5.3.0` - `org.apache.cxf:cxf-core:3.2.2` to `org.apache.cxf:cxf-core:3.2.11` - Resolved potential XEE attacks (INFOSEC-13658) ## [](#2-0-0)2.0.0 **March 23, 2018** New release of the Microsoft Dynamics Ax version. Supported operations: - Query Table - Static Query - Invoke Document Service Operation ### [](#compatibility-8)Compatibility - Mule 4.1 and later - Anypoint Studio 7 and later ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Dynamics CRM Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Dynamics Customer Relationship Management (CRM Connector) lets you access the Microsoft Dynamics CRM SOAP organization service. You can add this connector to an Anypoint Studio flow. Guide: [Microsoft Dynamics CRM Connector](https://docs.mulesoft.com/jp/microsoft-dynamics-crm-connector/latest/) Reference: [Microsoft Dynamics CRM Connector Reference](https://docs.mulesoft.com/jp/microsoft-dynamics-crm-connector/latest/ms-dynamics-crm-connector-reference) ## [](#3-2-17)3.2.17 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.2.

  • The neethi library is upgraded to version 3.2.3.

  • The bcprov-jdk18on library is upgraded to version 1.86.

W-24113946
## [](#3-2-16)3.2.16 **August 17, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue Resolution ID

The Commons Codec library is upgraded to version 1.22.1 to address reported security vulnerabilities.

W-23441844
## [](#3-2-15)3.2.15 **August 19, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Dynamics CRM version

2013, 2015, 2016
## [](#3-2-14)3.2.14 **April 29, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue Resolution ID

When using the Execute operation with the Create option, the Request Name field now works as intended when the parent customer ID has multiple entities, such as Account and Contact.

W-15580876
## [](#3-2-13)3.2.13 **October 7, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853429
## [](#3-2-12)3.2.12 **September 14, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

The caching mechanism for the metadata multiple resolver now works as expected.

W-11700194
## [](#3-2-11)3.2.11 **June 29, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

The Enable logging option no longer prints the same requests and responses for both the true and false options.

W-11317889
## [](#3-2-10)3.2.10 **May 11, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

The connector no longer throws the incorrect error type for some corner cases in the Create, Create Multiple, Update, and Update Multiple operations.

W-11082572
## [](#3-2-9)3.2.9 **April 4, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

Upgraded com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920485
## [](#3-2-8)3.2.8 **January 13, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.12.6 to address security vulnerabilities.

CONN-9843
## [](#3-2-7)3.2.7 **October 14, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

Fixed reported vulnerabilities for the connector.

CONN-8932
## [](#3-2-6)3.2.6 **September 20, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CONN-8802
## [](#3-2-5)3.2.5 **December 8, 2020** ### [](#compatibility-13)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-12)Fixed Issues - Fixed an Apache CXF vulnerability. - Fixed a null pointer exception error that occurred when using null with a query. (SE-18464) ## [](#3-2-4)3.2.4 **September 16, 2020** ### [](#compatibility-14)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-13)Fixed Issues Fixed an Apache Commons IO vulnerability. ## [](#3-2-3)3.2.3 **May 13, 2020** ### [](#compatibility-15)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-14)Fixed Issues Fixed reported vulnerabilities for the connector. ## [](#3-2-2)3.2.2 **May 11, 2020** ### [](#compatibility-16)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-15)Fixed Issues Fix a connection timeout issue. (CONN-5887) ## [](#3-2-1)3.2.1 **November 29, 2019** ### [](#compatibility-17)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-16)Fixed Issues Added support for default realm detection. (SE-13332) ## [](#3-2-0)3.2.0 **September 23, 2019** ### [](#compatibility-18)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#features)Features Added the new **Enable logging** field in the Anypoint Studio **Advanced** tab. If set to **True**, requests and responses display in the Anypoint Studio console log. ### [](#fixed-issues-17)Fixed Issues CRM Connector now supports Java 11. ## [](#3-1-5)3.1.5 **September 5, 2019** ### [](#compatibility-19)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-18)Fixed Issues The connector now follows redirects when performing requests to the CRM API. (SE-12278) ## [](#3-1-4)3.1.4 **February 22, 2019** ### [](#compatibility-20)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-19)Fixed Issues Intermittent error when trying to load a policy for an online authentication. Fixed by forcing a reconnect when the error is thrown.
There was not a v3.1.3 release.
## [](#3-1-2)3.1.2 **January 15, 2019** ### [](#compatibility-21)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-20)Fixed Issues LoseOpportunity request was not supported. Fixed by adding specific handling for the request. ### [](#known-issues)Known Issues Execute operation may cause issues for different types of actions, depending on the structure of the request being sent to the CRM API. ## [](#3-1-1)3.1.1 **November 9, 2018** ### [](#compatibility-22)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#fixed-issues-21)Fixed Issues Failed LoseOpportunity request returned a generic error message. Fixed by enriching the error message with details. ## [](#3-1-0)3.1.0 **September 26, 2018** ### [](#compatibility-23)Compatibility
Application/Service Version

Mule

4.1.1 and later

Dynamics CRM version

2013, 2015, 2016
### [](#features-2)Features - Kerberos connection provider - Deleted Object trigger - Queries the audit table to retrieve all deleted objects of specified type - New Object trigger - Queries the specified field type table to retrieve all of the new created objects - Modified Object trigger - Queries the specified field type table to retrieve all of the fresh modified objects ### [](#fixed-issues-22)Fixed Issues WinOpportunity request was not supported. Fixed by adding specific handling of the request. ### [](#known-issues-2)Known Issues None ## [](#3-0-0)3.0.0 **April 10, 2018** ### [](#compatibility-24)Compatibility
Application/Service Version

Mule

4.1.0 and later

Dynamics CRM version

2013, 2015, 2016
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Dynamics GP Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Dynamics GP (Microsoft Dynamics GP Connector) enables Mule runtime engine (Mule) apps to interact with Microsoft Dynamics Great Plains (GP) Web Services. Guide: [Microsoft Dynamics GP Connector](https://docs.mulesoft.com/microsoft-dynamics-gp-connector/latest/) Reference: [Microsoft Dynamics GP Connector Reference](https://docs.mulesoft.com/microsoft-dynamics-gp-connector/latest/ms-dynamics-gp-connector-reference) ## [](#3-0-0)3.0.0 **October 21, 2026** ### What’s New - This connector is now compatible with Java 17 only. - Connector failures are now reported as `DYNAMICSGP:DYNAMICSGP_INTERNAL`, instead of `DYNAMICSGP:UNKNOWN`. A condition on `ANY` still matches `DYNAMICSGP:DYNAMICSGP_INTERNAL` and `DYNAMICSGP:XML_PARSING`. A handler that names `DYNAMICSGP:UNKNOWN` doesn’t match this release. - You can now set optional **Timeout unit**, **Connection timeout**, and **Read timeout** fields on the [Default Configuration](https://docs.mulesoft.com/microsoft-dynamics-gp-connector/latest/ms-dynamics-gp-connector-reference#config) Advanced tab. Each operation can override these values in the **Timeout Override** group on the Advanced tab. An override applies when you set **Connection Timeout** or **Read Timeout**. When you don’t set those values, the Kerberos Authentication **Timeout Configuration** values remain in effect. - Generated sources and WSDL bindings now use Jakarta XML packages, instead of Java EE packages. Operation names, the XML namespace, and the `dynamicsgp` configuration prefix are unchanged. For more information about how to upgrade, see [Upgrading and Migrating Microsoft Dynamics GP Connector to 3.x](https://docs.mulesoft.com/microsoft-dynamics-gp-connector/latest/ms-dynamics-gp-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Apache CXF library is upgraded to version 4.2.4.

  • The Web Services Security library is upgraded to version 4.0.2.

  • The Apache XML Security (Santuario) library is upgraded to version 4.0.4.

  • The Apache Commons Lang library is upgraded to version 3.21.0.

  • The Apache Neethi library is upgraded to version 3.2.4.

  • The Apache Xerces library is upgraded to version 2.12.2.

These libraries are added to address reported security vulnerabilities:

  • The Guava library is added at 33.7.2-jre.

  • The Apache XMLSchema Core library is added at 2.3.3.

  • The Jakarta XML Binding API library is added at 4.0.5.

  • The Jakarta XML Web Services library is added at 4.0.3.

  • The Jakarta XML SOAP Binding library is added at 3.0.2.

  • The Jakarta annotation API library is added at 2.1.1.

  • The JAXB runtime library is added at 4.0.9.

  • The SAAJ implementation library is added at 3.0.6.

  • The ASM library is added at 9.11. This pin replaces ASM 9.10.1 from Apache CXF 4.2.4 and addresses CVE-2026-110257, CVE-2026-110258, CVE-2026-110259, CVE-2026-110260, CVE-2026-110261, and CVE-2026-110263.

W-3300013, W-24406484
## [](#2-1-9)2.1.9 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The neethi library is upgraded to version 3.2.3.

  • The commons-codec library is upgraded to version 1.22.1.

  • The commons-lang3 library is upgraded to version 3.20.0.

W-24113947
## [](#2-1-8)2.1.8 **August 17, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Apache WSS4J library is upgraded to version 2.4.3.

  • The Apache Commons Lang3 library is upgraded to version 3.18.0.

W-23441844
## [](#2-1-7)2.1.7 **August 18, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
## [](#2-1-6)2.1.6 **October 14, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### Fixed Issues
Issue ID

Fixed reported vulnerabilities for the connector.

CONN-8932
## [](#2-1-5)2.1.5 **July 23, 2021** ### [](#compatibility-6)Compatibility
Software Version

Mule

4.1.1 and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### [](#fixed-issues-5)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#2-1-4)2.1.4 **February 18, 2021** ### [](#compatibility-7)Compatibility
Software Version

Mule

4.1.1 and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### [](#fixed-issues-6)Fixed Issues Fixed connectivity issues by using a cached connection pool. (SE-19488) ## [](#2-1-3)2.1.3 **January 27, 2021** ### [](#compatibility-8)Compatibility
Software Version

Mule

4.1.1 and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### [](#fixed-issues-7)Fixed Issues Fixed reported vulnerabilities for the connector. ## [](#2-1-2)2.1.2 **November 2, 2020** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.1.1 and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### [](#fixed-issues-8)Fixed Issues Fixed reported vulnerabilities for the connector. ## [](#2-1-1)2.1.1 **May 26, 2020** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.1.1 and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### [](#fixed-issues-9)Fixed Issues Fixed security vulnerabilities for the connector. ## [](#2-1-0)2.1.0 **December 20, 2019** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### [](#features)Features New Kerberos Authentication fields for **Timeout Unit**, **Connection Timeout**, and **Read Timeout**. (SE-12952) See [Microsoft Dynamics GP Connector Reference](https://docs.mulesoft.com/microsoft-dynamics-gp-connector/latest/ms-dynamics-gp-connector-reference) for descriptions. ## [](#2-0-0)2.0.0 **May 9, 2018** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.x and later

MS Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2
### [](#features-2)Features - Added support for Mule 4. - Only the Kerberos authentication method is supported. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Dynamics NAV Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Dynamics NAV Connector (NAV Connector) enables Mule apps to interact with the Microsoft Dynamics NAV Web Services versions 2013 R2, 2015, 2016, 2017. Guide: [Microsoft Dynamics NAV Connector User Guide](https://docs.mulesoft.com/jp/microsoft-dynamics-nav-connector/latest/) ## [](#4-0-0)4.0.0 **October 23, 2026** ### What’s New - This connector is now compatible with Java 17 only. - The SOAP stack now uses Apache CXF 4.2.4 and the Jakarta XML Bind, XML Web Services, JWS, and SOAP APIs. Applications that depend on Apache CXF 3 or the Java EE JAXB, JAX-WS, JWS, or SAAJ packages must be re-verified. Operation names and the `nav` configuration prefix are unchanged. - The NTLM and OAuth connection types now include optional **Response Timeout** and **Response Timeout Unit** fields on the Advanced tab. The default response timeout is 5000 milliseconds. Expressions aren’t supported for these fields. For more information, see [NTLM Connection Type](#ms-dynamics-nav-connector-reference.adoc#ntlm) and [OAuth Connection Type](#ms-dynamics-nav-connector-reference.adoc#dynamics-nav-config_oauth). - The JAXB-XJC external library for the NTLM and OAuth connection types is now `org.glassfish.jaxb:jaxb-xjc:4.0.9`. Version 3.x used `com.sun.xml.bind:jaxb-xjc:2.3.9`. For more information, see [NTLM Connection Type](https://docs.mulesoft.com/jp/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#ntlm) and [OAuth Connection Type](https://docs.mulesoft.com/jp/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#dynamics-nav-config_oauth). For more information about how to upgrade, see [Microsoft Dynamics NAV Connector のバージョン 3.0 へのアップグレードおよび移行](https://docs.mulesoft.com/jp/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17

Microsoft Dynamics NAV

  • 2013 R2

  • 2015

  • 2016

  • 2017
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Apache CXF library is upgraded to version 4.2.4.

  • The JAXB runtime and XJC libraries are upgraded to version 4.0.9.

  • The Jakarta XML Bind API is upgraded to version 4.0.5.

  • The Apache Commons Lang library is upgraded to version 3.21.0.

These libraries are added to address reported security vulnerabilities:

  • The Jakarta XML Web Services API is added at version 4.0.3.

  • The Jakarta XML SOAP API is added at version 3.0.2.

  • The Jakarta JWS API is added at version 3.0.0.

  • The SAAJ implementation is added at version 3.0.6.

  • The Bouncy Castle libraries are added at version 1.86.

W-24113950, W-3300013
## [](#3-0-2)3.0.2 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The guava library is upgraded to version 33.7.1-jre.

  • The neethi library is upgraded to version 3.2.3.

W-3300013
## [](#3-0-1)3.0.1 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Woodstox library is upgraded to version 7.2.2.

  • The Commons Codec library is upgraded to version 1.22.1.

W-23441858
## [](#3-0-0)3.0.0 **July 4, 2025** ### What’s New - To support Microsoft Dynamics NAV Connector in CloudHub 2.0, the client must provide SOAP requests in raw XML format instead of using Plain Old Java Objects (POJOs). For more information, refer to [Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 3.0](https://docs.mulesoft.com/jp/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17
## [](#2-1-0)2.1.0 **August 20, 2024** ### What’s New - This connector is now compatible with Java 17. - A new external library called JAXB-XJC is now required for the NTLM and OAuth connection types for Java 8, 11, and 17. For more information, refer to [NTLM Connection Type](https://docs.mulesoft.com/jp/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#ntlm) and [OAuth Connection Type](https://docs.mulesoft.com/jp/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#dynamics-nav-config_oauth). ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-0-12)2.0.12 **October 3, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The metadata for the Page Operation operation now works as intended.

W-11791738
## [](#2-0-11)2.0.11 **November 11, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities.

CONN-9261
## [](#2-0-10)2.0.10 **September 20, 2021** ### Compatibility
Application/Service Version

Mule

4.0.0 and later
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CONN-8802
## [](#2-0-9)2.0.9 **May 10, 2021** ### [](#compatibility-9)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issues-7)Fixed Issues Fixed reported security vulnerabilities for the connector. ## [](#2-0-8)2.0.8 **February 1, 2021** ### [](#compatibility-10)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issues-8)Fixed Issues Fixed reported security vulnerabilities for the connector. ## [](#2-0-7)2.0.7 **January 21, 2021** ### [](#compatibility-11)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issues-9)Fixed Issues Fixed DSQL query issues with LIMIT clauses and WHERE clauses that use date fields. (SE-18941, SE-18944) ## [](#2-0-6)2.0.6 **December 9, 2020** ### [](#compatibility-12)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issue)Fixed Issue The metadata for some operations didn’t display correctly. (SE-18609). ## [](#2-0-5)2.0.5 **November 25, 2020** ### [](#compatibility-13)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issue-2)Fixed Issue The format of the output fields did not match the format of the fields defined in the WSDL. (SE-17678). ## [](#2-0-4)2.0.4 **October 14, 2020** ### [](#compatibility-14)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issue-3)Fixed Issue The Page operation did not work poperly. (SE-17678). ## [](#2-0-3)2.0.3 **August 21, 2020** ### [](#compatibility-15)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issue-4)Fixed Issue The issue that caused the connector to incorrectly serialize the `Date` type is fixed. (SE-16340) ## [](#2-0-2)2.0.2 **May 12, 2020** ### [](#compatibility-16)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issues-10)Fixed Issues Fixed reported vulnerabilities for the connector ## [](#2-0-1)2.0.1 **June 10, 2019** ### [](#compatibility-17)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issues-11)Fixed Issues - NAV Connector **Test Connection** fails with Unable to create JAXBContext for generated packages - There were some issues with some dependencies of the connector that were causing this problem with Mule runtime 4.2.0 and later. This was fixed by upgrading some dependencies to newer versions: **org.apache.cxf:cxf-rt-transports-http:3.2.1** was updated to **org.apache.cxf:cxf-rt-transports-http:3.3.1** and **org.apache.cxf:cxf-rt-frontend-jaxws:3.2.1** was updated to **org.apache.cxf:cxf-rt-frontend-jaxws:3.3.1**. (SE-11902) ## [](#2-0-0)2.0.0 **March 23, 2018** ### [](#compatibility-18)Compatibility NAV Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#fixed-issues-12)Fixed Issues First Mule 4 release. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Excel Online Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Excel Online (Excel Online Connector) gives you access to the Microsoft Excel Online platform. This connector exposes operations provided by the Microsoft Excel Online API. For more information, refer to the [Overview of Microsoft Graph](https://learn.microsoft.com/en-us/graph/overview?view=graph-rest-1.0). Guide: [Microsoft Excel Online Connector User Guide](https://docs.mulesoft.com/jp/microsoft-excel-online-connector/latest/) ## [](#1-1-1)1.1.1 **April 30, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-0)1.1.0 **November 28, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now handles the Lifetime validation failed, the token is expired error correctly and refreshes the access token.

W-13903385

In the Get chart item at operation, the Index field is added and the Chart Name/Id and Request Body fields are deprecated. The Get chart item at operation now works as intended.

W-14242129

The Get range last cell operation no longer throws a NullPointerException when optional fields aren’t used.

W-14242158
## [](#1-0-5)1.0.5 **October 20, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.12.6.1 to com.fasterxml.jackson.core:jackson-databind:2.14.0-rc1 to fix reported security vulnerabilities.

W-11853433
## [](#1-0-4)1.0.4 **April 7, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920489
## [](#1-0-3)1.0.3 **January 6, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.fasterxml.jackson.core:jackson-databind library due to a security vulnerability.

CONN-9823
## [](#1-0-2)1.0.2 **November 19, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9282
## [](#1-0-1)1.0.1 **June 30, 2021** ### [](#compatibility-7)Compatibility Microsoft Excel Online Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-6)Fixed Issues - Fixed the latest detected vulnerabilities. ## [](#1-0-0)1.0.0 **June 2, 2021** ### [](#compatibility-8)Compatibility Microsoft Excel Online Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features New connector. For a list of supported configurations and operations, see the Microsoft Excel Online Connector Reference Guide. ### [](#known-issues)Known Issues - The reconnection mechanism for sources does not work due to a runtime issue. - The reconnection mechanism for operations works only when using Mule 4.2.2 and 4.3.0. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft MSMQ Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Message Queueing (MSMQ Connector) for Mule 4. Guide: [MSMQ Connector User Guide](https://docs.mulesoft.com/jp/msmq-connector/latest/) ## [](#2-1-3)2.1.3 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-1-2)2.1.2 **August 24, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Commons Codec library is upgraded to version 1.22.1 to address reported security vulnerabilities.

W-23441718
## [](#2-1-1)2.1.1 **April 15, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-1-0)2.1.0 **December 15, 2023** ### What’s New - The **Send** operation now contains the new **Additional Headers** field. ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The commons-io:commons-io library is upgraded to version 2.15.1.

W-14667021
## [](#2-0-10)2.0.10 **June 13, 2023** ### What’s New - The Apache HttpClient dependency is upgraded from org.apache.httpcomponents:httpclient:4.5.13 to org.apache.httpcomponents:httpclient:4.5.14. - The Commons Codec dependency is upgraded from commons-codec:commons-codec:1.14 to commons-codec:commons-codec:1.15. - The Commons IO dependency is upgraded from commons-io:commons-io:2.7 to commons-io:commons-io:2.13.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later
## [](#2-0-9)2.0.9 **February 2, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Removed the Atlantic Commons dependency.

CONN-10042
## [](#2-0-8)2.0.8 **July 23, 2021** ### [](#compatibility-7)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-4)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#2-0-7)2.0.7 **May 11, 2021** ### [](#compatibility-8)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-5)Fixed Issues Fixed the reported vulnerabilities for the connector. ## [](#2-0-6)2.0.6 **January 12, 2021** ### [](#compatibility-9)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-6)Fixed Issues The connector did not trigger the REDELIVERY\_EXHAUSTED exception. ## [](#2-0-5)2.0.5 **November 18, 2020** ### [](#compatibility-10)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-7)Fixed Issues Fixed the reported vulnerabilities for the connector. ## [](#2-0-4)2.0.4 **September 9, 2020** ### [](#compatibility-11)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-8)Fixed Issues Messages formatted with ActiveXMessageFormatter did not appear as intended. (SE-17029) ## [](#2-0-3)2.0.3 **July 8, 2020** ### [](#compatibility-12)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-9)Fixed Issues Fixed security vulnerabilities for the connector. ## [](#2-0-2)2.0.2 **May 8, 2020** ### [](#compatibility-13)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-10)Fixed Issues - Deleted the following dependencies to fix vulnerability issues (CONN-5911): - `com.google.guava:guava:19.0` - `assertions-1.0.2.jar` - `wlang-2.2.2.jar` ## [](#2-0-1)2.0.1 **May 4, 2020** ### [](#compatibility-14)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-11)Fixed Issues - Upgraded the following dependencies to fix vulnerability issues: - `org.apache.httpcomponents:httpclient:4.5` upgraded to `org.apache.httpcomponents:httpclient:4.5.9` - `commons-codec:commons-codec:1.9` upgraded to `commons-codec:commons-codec:1.13` ## [](#2-0-0)2.0.0 **February 2, 2018** ### [](#compatibility-15)Compatibility MSMQ Connector is compatible with:
Application/Service Version

Mule

4.1.0 and later
### [](#features)Features Supports Mule 4. ## [](#see-also)See Also - [Windows Gateway Services Guide](https://docs.mulesoft.com/connectors/windows-gateway-services/windows-gateway-services-guide-mule4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft OneDrive Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft OneDrive (OneDrive Connector) enables you to access Microsoft Graph APIs to provide a unified programmability model that you can use to access the tremendous amount of data in Microsoft 365, Windows 10, and Enterprise Mobility + Security. Guide: [Microsoft OneDrive Connector User Guide](https://docs.mulesoft.com/microsoft-onedrive-connector/latest/) ## [](#1-2-1)1.2.1 **October 5, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now uses absolute http or https @odata.nextLink URLs as-is and prefixes only relative locations with the connector base URL. This enables the List Children operation to page results when Microsoft Graph returns an absolute next link.

W-23455397

Failures while reading operation, upload-session, or paging responses now return a connector ModuleException with the SERVER_ERROR or CONNECTIVITY error type instead of a generic MuleRuntimeException.

W-23455397

The connector now refreshes the access token when Microsoft Graph returns HTTP 401 with the message Invalid token lifetime.

W-24358861

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.3.

  • The commons-codec library is upgraded to version 1.22.1.

  • The gson library is upgraded to version 2.14.0.

  • The Apache HttpClient library is upgraded to version 4.5.14.

W-24113995, W-24262985
## [](#1-2-0)1.2.0 **May 12, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The gson library is upgraded to version 2.12.0.

  • The jackson library is upgraded to version 2.18.6.

  • The commons-io library is upgraded to version 2.15.0.

  • The commons-lang3 library is upgraded to version 3.18.0.

W-20774568
## [](#1-1-2)1.1.2 **March 29, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-1)1.1.1 **August 15, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now handles the Lifetime validation failed, the token is expired error correctly and refreshes the access token.

W-13903401
## [](#1-1-0)1.1.0 **March 20, 2023** ### What’s New - The OAuth v2.0 Authorization Code and OAuth v2.0 Client Credentials connection types now contain the new **Base Url** field, which enables you to configure the value of the base URL instead of using the hardcoded value of the base URL. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
## [](#1-0-4)1.0.4 **October 25, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.13.2.2 to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to fix reported security vulnerabilities.

W-11853401
## [](#1-0-3)1.0.3 **April 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920492
## [](#1-0-2)1.0.2 **January 14, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9808
## [](#1-0-1)1.0.1 **December 1, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9257
## [](#1-0-0)1.0.0 **August 24, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, see the OneDrive Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Outlook 365 Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Outlook 365 (Outlook 365 Connector) enables you to integrate with the Microsoft Outlook 365 service. Guide: [Microsoft Outlook 365 Connector User Guide](https://docs.mulesoft.com/jp/microsoft-outlook-365-connector/latest/) ## [](#1-3-2)1.3.2 **July 24, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

INVALID_CREDENTIALS errors no longer occur when Microsoft Graph returns a 401 response with an empty body or a non-standard error message for an expired OAuth access token. The connector now correctly refreshes the expired token and retries the request.

W-18288759
## [](#1-3-1)1.3.1 **August 8, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-io dependency is upgraded to version 2.14.0 to address reported security vulnerabilities.

W-18561724
## [](#1-3-0)1.3.0 **April 1, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The OAuth v2.0 Authorization Code and OAuth v2.0 Client Credentials connection types now include the Base Url field.

W-15434750

The connector now has enhanced error handling for 503 errors.

W-14979235

The connector now has enhanced error handling for IOException errors.

W-14336916
## [](#1-2-4)1.2.4 **May 20, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now handles the The token has expired error correctly and refreshes the access token.

W-15755241
## [](#1-2-3)1.2.3 **April 30, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-2-2)1.2.2 **September 20, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector’s dependency commons-io:commons-io was updated to version 2.13.0 to fix a security vulnerability.

W-14103194
## [](#1-2-1)1.2.1 **August 1, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now handles the Lifetime validation failed, the token is expired error correctly and refreshes the access token.

W-13854155
## [](#1-2-0)1.2.0 **March 23, 2023** ### What’s New - The connector now throws the new `OUTLOOK365:APPLICATION_THROTTLED` error if the application exceeds its MailboxConcurrency limit when multiple parallel requests are executed to the Microsoft Graph API. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#1-1-5)1.1.5 **February 1, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The On New Email source now receives messages correctly when the Since field is blank.

W-12429278
## [](#1-1-4)1.1.4 **May 31, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The On New Email source now receives messages correctly when the poll returns an empty list.

W-11200829
## [](#1-1-3)1.1.3 **May 24, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The On New Email source no longer throws a NullPointerException when using a shared mailbox.

W-11137115
## [](#1-1-2)1.1.2 **April 26, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The Get Message Attachment operation now returns content as application/octet-stream instead of application/json when Get Raw Content is set to true.

W-11001868
## [](#1-1-1)1.1.1 **April 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

If the Outlook mailbox settings have no time zone, the connector defaults to the UTC time zone.

W-10906852
## [](#1-1-0)1.1.0 **March 24, 2022** ### What’s New - The **TLS configuration** parameters in the OAuth 2.0 Authorization Code and OAuth 2.0 Client Credentials connections are now deprecated. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#1-0-4)1.0.4 **March 7, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The Users.Read.All permission is no longer required to create a connection.

W-10736015
## [](#1-0-3)1.0.3 **February 16, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Added input metadata for the Update event, Forward event, Accept event, and Decline event operations.

CONN-10000

Added value provider support for calendar (Delete event attachment and Get event attachment operations).

CONN-10000

Added value provider support for email folders, to display the possible folder values.

CONN-10000

Added value provider support for events, to display the possible event values.

CONN-10046

The access token did not refresh for sources.

W-10693582
## [](#1-0-2)1.0.2 **January 14, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9985
## [](#1-0-1)1.0.1 **November 12, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities.

CONN-9289
## [](#1-0-0)1.0.0 **October 6, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Microsoft Outlook 365 Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Power BI Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Power BI (Power BI Connector) synchronizes data and automates business processes between Power BI and third-party applications, either on-premises or in the cloud. Power BI is a suite of analytics tools designed to visualize data from various systems and garner insights. Guide: [Microsoft Power BI Connector User Guide](https://docs.mulesoft.com/jp/microsoft-power-bi-connector/latest/) ## [](#1-0-7)1.0.7 **September 22, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-beanutils library is upgraded to version 1.11.0 to address reported security vulnerabilities.

W-24114414
## [](#1-0-6)1.0.6 **August 31, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The log4j-core library is upgraded to version 2.25.4.

  • The rest-sdk-commons library is upgraded to version 0.1.5-HF2.

W-23441737
## [](#1-0-5)1.0.5 **June 19, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Power BI Connector in Anypoint Studio as intended.

W-16044858
## [](#1-0-4)1.0.4 **May 3, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-3)1.0.3 **January 7, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9836
## [](#1-0-2)1.0.2 **December 20, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9684
## [](#1-0-1)1.0.1 **December 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9568
## [](#1-0-0)1.0.0 **March 30, 2021** ### [](#compatibility-8)Compatibility Power BI Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features New connector. For a list of supported configurations and operations, see the Power BI Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Service Bus Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Service Bus provides support for Microsoft Windows Service Bus (on-premises). Guide: [Microsoft Service Bus Connector User Guide](https://docs.mulesoft.com/jp/microsoft-service-bus-connector/latest/) To implement message integration scenarios with Microsoft Azure, use the [Microsoft Azure Service Bus Connector](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4). ## [](#2-2-10)2.2.10 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Microsoft Service Bus REST API

v2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The netty library is upgraded to version 4.1.137.Final.

  • The proton-j library is upgraded to version 0.35.0.

W-24113998
## [](#2-2-9)2.2.9 **August 20, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Microsoft Service Bus REST API

v2
### Fixed Issues
Issue Resolution ID

The netty library is upgraded to version 4.1.136.Final to address reported security vulnerabilities.

W-23441720
## [](#2-2-8)2.2.8 **July 21, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Microsoft Service Bus REST API

v2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.20.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The rome library is upgraded to version 1.19.0.

  • The netty library is upgraded to version 4.1.135.Final.

  • The azure-storage library is upgraded to version 5.5.0.

  • The jackson library is upgraded to version 2.22.1.

  • The guava library is upgraded to version 32.1.3-jre.

W-20597761
## [](#2-2-7)2.2.7 **May 2, 2024** ### What’s New - The connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Microsoft Service Bus REST API

v2
## [](#2-2-6)2.2.6 **February 7, 2024** ### What’s New
Software Version

Mule

4.1.1 and later

Microsoft Service Bus REST API

v2
### Fixed Issues | The netty-codec-http2 dependency is upgraded to version 4.1.100.Final to address a reported security vulnerability. | W-14462879. | | --- | --- | ## [](#2-2-5)2.2.5 **September 21, 2023** ### What’s New - The Guava library is upgraded from com.google.guava : guava : 23.6.1-jre to com.google.guava : guava : 32.0.1-jre. - The Jackson Core library is upgraded from com.fasterxml.jackson.core:jackson-core:2.8.6 to com.fasterxml.jackson.core:jackson-core:2.15.2. - The Netty Codec component is upgraded from library io.netty: netty-codec:4.1.50.Final to io.netty: netty-codec:4.1.94.Final. - The Netty Handler component is upgraded from library io.netty: netty-handler:4.1.50.Final to io.netty: netty-handler:4.1.94.Final. ### Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Service Bus REST API

v2
### Fixed Issues
Issue Resolution ID

The Guava library is upgraded from com.google.guava : guava : 23.6.1-jre to com.google.guava : guava : 32.0.1-jre.

W-13844872

The Jackson Core library is upgraded from com.fasterxml.jackson.core:jackson-core:2.8.6 to com.fasterxml.jackson.core:jackson-core:2.15.2.

W-13844857

The Netty Codec component is upgraded from library io.netty: netty-codec:4.1.50.Final to io.netty: netty-codec:4.1.94.Final.

W-13844837

The Netty Handler component is upgraded from library io.netty: netty-handler:4.1.50.Final to io.netty: netty-handler:4.1.94.Final.

W-13844841, W-13844878.
## [](#2-2-4)2.2.4 **May 27, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Microsoft Azure Storage Client SDK

5.0.0

Service Bus

Microsoft Windows Service Bus 1.1+
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the spring-beans package from org.springframework:spring-beans:5.2.21 to org.springframework:spring-beans:5.2.22.

W-11195302
## [](#2-2-3)2.2.3 **April 21, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the spring-context package from org.springframework:spring-context:4.3.17 to org.springframework:spring-context:5.2.21.

W-10996432
## [](#2-2-2)2.2.2 **July 23, 2021** ### [](#compatibility-8)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-8)Fixed Issues - Fixed internal security vulnerabilities. (CONN-8587) ## [](#2-2-1)2.2.1 **September 2, 2020** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-9)Fixed Issues Fixed a Null Pointer Exception that occurred when using the Raise error component with the Message listener in a flow. (SE-17315) ### [](#known-issues)Known Issues - The JMS selector that previously filtered incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus. - The `maxConnections` parameter is deprecated. ## [](#2-2-0)2.2.0 **July 27, 2020** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-10)Fixed Issues Fixed reported security vulnerabilities. (CONN-6252,CONN-6253,CONN-6254) ### [](#known-issues-2)Known Issues - The JMS selector that previously filtered incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus. - The `maxConnections` parameter is deprecated ## [](#2-1-15)2.1.15 **May 29, 2020** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
## [](#2-1-14)2.1.14 **May 8, 2020** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-11)Fixed Issues - An exception occurred when disposing an object. (SE-15278). ### [](#known-issues-3)Known Issues - The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus. ## [](#2-1-13)2.1.13 **April 21, 2020** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-12)Fixed Issues Fixed security vulnerabilities. (CONN-5680) ### [](#known-issues-4)Known Issues - The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus. ## [](#2-1-12)2.1.12 **March 9, 2020** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-13)Fixed Issues Mule 4.2.2 on-premises did not clear out metaspace when redeploying an application. (SE-14929) ### [](#known-issues-5)Known Issues - The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus. ## [](#2-1-11)2.1.11 **February 28, 2020** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-14)Fixed Issues The exposed SharedAccessSignatureProvider interface was fixed to allow the implementation of a SAS Token Provider. (SE-14685) ### [](#known-issues-6)Known Issues - The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus. ## [](#2-1-10)2.1.10 **January 20, 2020** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-15)Fixed Issues - Fixed the isssue in which a reconnection error occurred after producer inactivity. (SE-14544) ## [](#2-1-9)2.1.9 **January 9, 2020** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-16)Fixed Issues - Consumer error after redeploying an app is now fixed. (SE-14336) ## [](#2-1-8)2.1.8 **December 10, 2019** ### [](#compatibility-18)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-17)Fixed Issues - Fixed the unauthorized user error when using a SAS connection issue. (SE-14174) ## [](#2-1-7)2.1.7 **November 11, 2019** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+
### [](#fixed-issues-18)Fixed Issues - Fixed reconnection errors in a message producer. Previously, when using a cached producer, if a ConnectionException occurred, the connector tried to reconnect with the same state instead of re-establishing the connection. (CONN-4032) ## [](#2-1-6)2.1.6 **November 5, 2019** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-19)Fixed Issues - Added specific error types for JMS exceptions. The connector now throws SERVICEBUS:PUBLISHING, SERVICEBUS:ILLEGAL\_BODY, SERVICEBUS:DESTINATION\_NOT\_FOUND, or SERVICEBUS:SECURITY, depending on the case. (SE-13674) ## [](#2-1-5)2.1.5 **October 30, 2019** ### [](#compatibility-21)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-20)Fixed Issues - Improved connection exception handling. (SE-13581) - Added **Queue Prefetch** parameter in Advanced connection to limit the consumer buffer. (SE-13618) ## [](#2-1-4)2.1.4 **October 16, 2019** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-21)Fixed Issues - Fixed a typo in a logged message. ## [](#2-1-3)2.1.3 **October 16, 2019** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-22)Fixed Issues - Improved logging for send operations. (SE-13581) ## [](#2-1-2)2.1.2 **August 29, 2019** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-23)Fixed Issues - Fixed delivery delay functionality for send operations. (SE-12892) ## [](#2-1-1)2.1.1 **June 19, 2019** ### [](#compatibility-25)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features)Features - JMS 2.0 shared subscription - Added support for having multiple consumers subscribe to a single topic. This functionality distributes the topic’s message load among all subscribers. ## [](#2-1-0)2.1.0 **April 16, 2019** ### [](#compatibility-26)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features-2)Features - Redelivery policy options (maximum redeliveries and outcome) were added to the connector’s configuration. ### [](#fixed-issues-24)Fixed Issues - When dealing with manual ACK, if the flow failed with an error, the message could be reprocessed indefinitely. This is now fixed by the addition of the **Redelivery Policy** configuration. ### [](#known-issues-7)Known Issues - Automatic completion of queue/topic names, subscriptions and rules may not work in Design Center. - Under some scenarios, users can get an `InterruptedException` error on the Mule app startup. This does not affect the proper operation. To get rid of this message, check the **Skip Connectivity Test** checkbox in the connector’s configuration. ## [](#2-0-3)2.0.3 **February 22, 2019** ### [](#compatibility-27)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-25)Fixed Issues - Connection leaks were fixed. - The connector would stop receiving messages when the flow threw an error. This was fixed. ### [](#known-issues-8)Known Issues - Automatic completion of queue and topic names, subscriptions, and rules may not work in Design Center. ## [](#2-0-2)2.0.2 **December 5, 2018** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-26)Fixed Issues - Previously, the connector leaked connections while publishing a message to a topic using the default caching strategy. The connector uses one or two JMS connections based on the configuration. ### [](#known-issues-9)Known Issues - Automatic completion of queue or topic names, subscriptions, and rules may not work in Design Center. - In Design Center, the Live View feature does not work for most operations. In addition to this, the application log may be flooded with several `Could not serialize object` errors. ## [](#2-0-1)2.0.1 **October 23, 2018** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-27)Fixed Issues - Manual ACK not working - Previously, when attempting to do a manual acknowledge of a message, the connector would lock the flow. This was now fixed, and doing this works as expected. ### [](#known-issues-10)Known Issues - Automatic completion of queue and topic names, subscriptions and rules may not work in Design Center. - In Design Center, the Live View feature will not work for most operations. In addition to this, the application log may be flooded with several `Could not serialize object` errors. - The connector leaks connections while publishing a message to a topic using the default caching strategy. As a workaround, configure the connector to disable the caching strategy. ## [](#2-0-0)2.0.0 **May 28, 2018** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features-3)Features - Added support for Mule 4. ### [](#known-issues-11)Known Issues - Automatic completion of queue and topic names, subscriptions, and rules may not work in Design Center. - In Design Center, the Live View feature does not work for most operations. In addition to this, the application log may be flooded with several `Could not serialize object` errors. - The connector leaks connections while publishing a message to a topic using the default caching strategy. As a workaround, configure the connector to disable the caching strategy. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Teams Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Teams (Microsoft Teams Connector) gives you access to the Microsoft Teams APIs. This connector exposes the most commonly used operations provided by the Microsoft Teams API. Guide: [Microsoft Teams Connector User Guide](https://docs.mulesoft.com/jp/microsoft-teams-connector/latest/) ## [](#1-1-6)1.1.6 **October 5, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17

Microsoft Graph Rest API

v1

OData API

v4
### Fixed Issues
Issue Resolution ID

The Create message operation now declares JSON with strict = false, so the operation accepts a JSON payload whose media type isn’t exactly application/json.

W-22616076

Connection failures are now classified without mule-runtime-core. SSL, unresolved-address, and I/O failures still surface as INVALID_CONNECTION.

W-22616076

Channel, team, and group-member metadata reads now use explicit UTF-8 and fail with a clear error if the response body can’t be read.

W-22616076

The connector now refreshes the access token when Microsoft Graph returns HTTP 401 with the message Invalid token lifetime.

W-24355560

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core, jackson-databind, jackson-dataformat-xml, and jackson-annotations libraries are upgraded to version 2.22.3.

  • The commons-codec library is upgraded to version 1.22.1.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The gson library is upgraded to version 2.14.0.

  • The OData Client library is upgraded to version 4.10.0.

W-24114773, W-24262985
## [](#1-1-5)1.1.5 **May 8, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17

Microsoft Graph Rest API

v1

OData API

v4
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Jackson library is upgraded to version 2.18.6.

  • The Woodstox library is upgraded to version 6.7.0.

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The commons-codec library is upgraded to version 1.17.1.

  • The commons-io library is upgraded to version 2.18.0.

  • The Apache HttpClient library is upgraded to version 4.5.14.

W-21334627
## [](#1-1-4)1.1.4 **March 28, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17

Microsoft Graph Rest API

v1

OData API

v4
## [](#1-1-3)1.1.3 **August 23, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
### Fixed Issues
Issue Resolution ID

The connector now handles the Lifetime validation failed, the token is expired error correctly and refreshes the access token.

W-13903204
## [](#1-1-2)1.1.2 **October 13, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853414
## [](#1-1-1)1.1.1 **April 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
### Fixed Issues
Issue ID

Improved connection validation.

W-10887274

Fixed a security vulnerability.

W-10920474
## [](#1-1-0)1.1.0 **March 21, 2022** ### What’s New - The **TLS configuration** parameters in the OAuth 2.0 Authorization Code and OAuth 2.0 Client Credentials connections are now deprecated. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
## [](#1-0-3)1.0.3 **January 5, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9847
### Known Issues - When **offline\_scope** is not specified in the Microsoft OAuth Code Grant Config and the access token is expired, the connector throws a `MULE:UNKNOWN` error instead of a `TEAMS:INVALID_CONNECTION` error. ## [](#1-0-2)1.0.2 **December 7, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities.

CONN-9254
### Known Issues - When **offline\_scope** is not specified in the Microsoft OAuth Code Grant Config and the access token is expired, the connector throws a `MULE:UNKNOWN` error instead of a `TEAMS:INVALID_CONNECTION` error. ## [](#1-0-1)1.0.1 **June 4, 2021** ### [](#compatibility-10)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
### [](#fixed-issues-8)Fixed Issues - Optimized the connector to improve its overall stability and performance. ### [](#known-issues-3)Known Issues - When **offline\_scope** is not specified in the Microsoft OAuth Code Grant Config and the access token is expired, the connector will throw a MULE:UNKNOWN error instead of a TEAMS:INVALID\_CONNECTION error. ## [](#1-0-0)1.0.0 **February 26, 2021** New connector. ### [](#compatibility-11)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11

Microsoft Graph Rest API

v1

OData API

v4
### [](#features)Features For a list of supported configurations and operations, see the Microsoft Teams Connector Reference Guide. ### [](#fixed-in-this-release)Fixed in This Release Not applicable. ### [](#known-issues-4)Known Issues - This connector is not FIPS 140 compliant. - The TLS handshake does not work when performing access token retrieval. - The proxy configuration is not taken into account when performing access token retrieval. - The refresh token mechanism for the OAuth 2.0 authorization code grant type only works if the `offline_access` scope is added. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Microsoft Windows PowerShell Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Microsoft Windows PowerShell (PowerShell Connector) is a Windows command line shell for system administrators. Windows PowerShell includes an interactive prompt and a scripting environment that can be used independently or together. Guide: [Microsoft PowerShell Connector User Guide](https://docs.mulesoft.com/jp/windows-powershell-connector/latest/) ## [](#2-1-5)2.1.5 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Java SSH Client JSch

v0.1.54
## [](#2-1-4)2.1.4 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Java SSH Client JSch

v0.1.54
### Fixed Issues
Issue Resolution ID

The commons-io library is upgraded to version 2.22.0 to address reported security vulnerabilities.

W-23441719
## [](#2-1-3)2.1.3 **January 30, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Java SSH Client JSch

v0.1.54
## [](#2-1-2)2.1.2 **February 2, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java SSH Client JSch

v0.1.54

Java

1.8 and later
### Fixed Issues
Issue ID

Removed the Atlantic Commons dependency.

CONN-10040
## [](#2-1-1)2.1.1 **July 22, 2021** ### [](#compatibility-5)Compatibility The PowerShell Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8 and later
### [](#fixed-issues-3)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#2-1-0)2.1.0 **April 28, 2021** ### [](#compatibility-6)Compatibility The PowerShell Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8 and later
### [](#fixed-issues-4)Fixed Issues - Uncaught exception did not throw an error. (SE-20198) ### [](#features)Features - Added two new operations that mimic the functionality of the existing operations, **Execute command** and **Execute script file**, but also throw Mule exceptions if the execution of the PowerShell script file or command failed. ## [](#2-0-2)2.0.2 **May 8, 2020** ### [](#compatibility-7)Compatibility The PowerShell Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Java

1.8 and later
### [](#fixed-issues-5)Fixed Issues - Fixed reported vulnerability issues. (CONN-6025) ## [](#2-0-1)2.0.1 **June 13, 2019** ### [](#compatibility-8)Compatibility The PowerShell Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

Java

1.8 and later
### [](#fixed-issues-6)Fixed Issues - PowerShell error stopped logging anything on the console. (SE-11546) ## [](#2-0-0)2.0.0 **January 27, 2018** ### [](#compatibility-9)Compatibility The PowerShell Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

Java

1.8 and later
### [](#features-2)Features - PowerShell Connector is built with the new AnyPoint SDK v1.0.1-SNAPSHOT. - PowerShell Connector also works with Linux-based Ubuntu systems. - You can execute commands and scripts on Windows and Linux machines. - You can run commands and scripts on remote machines. - The following operations are supported: - ExecuteScriptFile - Executes Script file on remote machine or local machine based on given configuration. - ExecuteCommand - Executes command on remote machine or local machine based on given configuration. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Migration Guide to API Gateway 2.0.0 or later API Gateway version 2.0 introduces important changes that require transforming any proxy that was built for a prior gateway version. The main change is the adoption of the new high performance HTTP Connector, also the properties defined for the proxy are different. If your proxy was automatically generated by the Anypoint Platform and its code has not been modified since in any way, then the provided migration tool should make this change easy for you. If, on the other hand, you have modified your proxy after downloading it – to include HTTPS credentials or any other alteration – then you must modify your project manually. For these cases we recommend downloading the proxy from the platform in the latest version of the API Gateway, and then copying the changes you’ve made to it. To migrate from an older version of the API Gateway, you must first configure your API Gateway 2.0 correctly with all of the proxies in place, and only then shut down the old API Gateway and start up the new one. Both versions can’t run at the same time, due to ports overlapping. ## [](#using-the-api-gateway-2-0-migration-tool)Using the API Gateway 2.0 Migration Tool If you’re using proxies that have been automatically generated by the Anypoint Platform and haven’t modified them since you downloaded them, you can run this migration tool: 1. Download the Migration Tool by clicking [here.](https://docs.mulesoft.com/jp/release-notes/_attachments/api-gateway-migration-tool-2.0.4.jar.zip) 2. Go to the API Gateway 2.0 Standalone distribution folder. 3. Run the following script from the command line: ```java java -jar /api-gateway-migration-tool-2.0.4.jar -DagwSourceFolder= -DagwTargetFolder= ``` You must provide: - The location in your system and name of the JAR file that executes the migration - DagwSourceFolder: The parent folder of your API Gateway 1.x Standalone distribution. Below this folder you’ll find the apps and domains folders, where the files to transform are stored. - DagwTargetFolder: The parent folder of your API Gateway 2.0 Standalone distribution. Below this folder you’ll find the transformed apps and domains folders. The tool migrates all your Applications and Domains in your folders in a single sweep. Any applications or domains that have been modified in any way since downloading from off the Anypoint Platform will be ignored by the tool, these will have to be migrated manually. ## [](#migrating-your-proxy-or-api-gateway-app-manually)Migrating your Proxy or API Gateway App Manually Starting with API Gateway version 2.0.0, the endpoint model is not supported. You can continue to use HTTP Endpoints and connectors (which is not the recommended practise), but you will not be able to manage any policy associated to it, and you won’t obtain any usage statistics. Moreover, with API Gateway 2.0.0 and later, any inbound endpoints that use API Autodiscovery will cause a parse exception when the application/proxy is deployed to the API Gateway. If you are using an older auto-generated proxy, it is recommended that you use the Anypoint Platform to automatically generate a new one, and then configure the extra functionality that you need, copying the changes you had performed previously on the older proxy. If you are using the APIKit plugin, make sure that you are using version 1.7.0 or greater. Earlier versions of the plugin are not supported on API Gateway 2.0.0. These are the two main changes to take into account: ### [](#non-blocking-strategy)Non blocking strategy API Gateway 2.0.0 is optimized for non blocking processing strategy, that gives you a clear performance advantage when the application/proxy is run in a high load system. All proxies built for API Gateway 2.0 have a flag set up to enable this feature. To enable this feature, simply include the following line of code at the beginning of your proxy’s XML, along with other configuration elements, outside any of the flows. `` ### [](#use-of-listeners)Use of listeners The new transport that comes with Mule 3.7, which replaces the old inbound endpoint model, is the only supported for policy management and statistics generation. You must replace every instance of the HTTP Inbound Endpoint for the new HTTP Listener Connector, you must also add the corresponding XSD schemas to the app. # MMC Migrator Tool This tool enables you to migrate server configuration data in your Mule Management Console (MMC) instance to a Runtime Manager instance. MMC is in the process of being fully replaced by the Runtime Manager. [MMC has been deprecated](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf), so we advise that you carry out this migration at your soonest convenience. The migration process consists of executing two scripts and taking care of a couple of manual steps in between. Download the migration tool (**mmc-arm-migrationscripts**) from [Salesforce Help](https://help.salesforce.com). If you do not have credentials to log in, please contact your Customer Success Manager. ## [](#migration-scope)Migration Scope The steps explained in this doc enable you to migrate the following things from your MMC instance: - Server data, including current state. This is needed to match the servers registered on MMC with those on Runtime Manager. - [Server Groups](https://docs.mulesoft.com/jp/runtime-manager/managing-servers#create-a-server-group) - [Clusters](https://docs.mulesoft.com/jp/runtime-manager/managing-servers#create-a-cluster) - Mule Application .zip files - Information about Mule Application Deployments on servers, together with their current statuses The migration tool does NOT take care of migrating: - Alerts. - User Permissions. These two things must be handled manually as both platforms follow different conceptual models in regards to them. Please refer to Runtime Manager documentation about how to configure [email alerts](https://docs.mulesoft.com/jp/runtime-manager/alerts-on-runtime-manager) and [user roles](https://docs.mulesoft.com/jp/access-management/roles). ## [](#prerequisites-before-running-the-mmc-dump-script)Prerequisites (before running the MMC Dump Script) As MMC and Runtime Manager have some differences in their conceptual model, keep in mind that some corner cases can’t be migrated into Runtime Manager. In these cases you must first change your configuration in MMC before you can run the dump script. Make sure that **NONE** of the following conditions are met before running the dump script: - **Server groups contain nested clusters or other nested server groups**. - **A single server is a member of multiple server groups**, it can only belong to one. - **Servers that belong to a Server Group also have deployments that target them individually as single servers** - **Clusters in MMC are in a yellow state**. They must all be in OK state (all nodes running) Although all of the cases listed above are possible configurations in MMC, they aren’t supported on Runtime Manager by design. Please make the necessary adjustments to make these compatible. ## [](#things-to-consider)Things to consider - **The Mule instances that are registered in MMC must be named identically as what you name them when registering them on Runtime Manager**. If you wish to have them registered on Runtime Manager with a different name, you must do one of the following: - Rename them on MMC before running the MMC Dump Script - Initially register them on Runtime Manager with the same name they have on MMC and rename them only after completing the whole migration procedure - **Inactive servers won’t be migrated**. Their information will be dumped, but they won’t be taken into account when importing server information into Runtime Manager. - **Runtime Manager supports Mule Runtime versions 3.6.0 and newer**. If dealing with older Mule Runtime versions in MMC, you’ll need to upgrade these to newer Mule versions before migrating them. - **Applications that are not included in at least one active deployment in MMC won’t be migrated**. This means dump files won’t include the corresponding application .zip. ## [](#mmc-dump-contents)MMC Dump Contents - A folder that contains the deployable **.zip** file for every application that is currently active. - A Dump file with the extension **.dmp** , which includes information about Servers, Server Groups, Clusters, Applications in the repository, and Deployments. ## [](#step-by-step-migration)Step by Step Migration Migrating your Mule Runtime instances from MMC to Runtime Manager implies three high level steps: **Step 1**: Run the **MMC Dump Script** to extract structure information and application files from MMC In order run this script, follow these steps: 1. Download the script file from [Salesforce Help](https://help.salesforce.com). 2. Open the MMC console and navigate to **Administration → Admin Shell** ![mmc migrator tool 2601c](/mulesoft/current/ja-jp/release-notes/_images/mule-runtime/mmc-migrator-tool-2601c.png) Paste the content of the script file as text in the canvas Click the **Evaluate** button. ![mmc migrator tool 041f0](/mulesoft/current/ja-jp/release-notes/_images/mule-runtime/mmc-migrator-tool-041f0.png) This will create a dump from what’s in your MMC instance in your mmc-data folder (in a new folder called mmcDump). See [MMC Dump Contents](#mmc-dump-contents) for a reference of what you’ll find in it. **Step 2**: Manual handling of Mule Runtime instances to decouple them from MMC and register them on Runtime Manager 1. Stop the execution of all running Mule Runtime instances (either via MMC console or via the command line) 2. For each Mule Runtime instance, open its folder `$MULE_HOME/app`, then delete everything that’s in it.
You may want to take advantage of this opportunity to update your servers to a new version of Mule Runtime. If that’s the case, then this last step is irrelevant as you’d be using a fresh new installation of the Mule Runtime on your servers. Note that as long as these new Mule Runtime instances run are named identically when registered, the migration process should consider them the same, regardless of them running with a newer Mule Runtime version. If the instances are on servers with the same IP addresses, then all of the coupling of clusters and server groups should also be implemented by the script.
3. [Register](https://docs.mulesoft.com/jp/runtime-manager/managing-servers#add-a-server) your Mule Runtime instances in Runtime Manager (using the same names these had in MMC). For details on how to do this, see [installing and configuring Mule Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) 4. Via the command line, start your Mule Runtimes **Step 3**: Run the **Runtime Manager Import Script** to introduce the extracted information into Runtime Manager through the following command: java -jar rtm-import-1.0.0.jar -H anypoint.mulesoft.com -D /Users/your\_user/your\_folder/dump\_folder -V v1 -U your\_user -P your\_password -E your\_env\_id -O your\_org\_id The import process command may contain the following parameters:
param name Description

-D

--dump-path

MMC Dump Folder Path

-H

--anypoint-url

Anypoint Url

-V

--api-version

Api Version

-U

--anypoint-user

Anypoint Username

-P

--anypoint-pass

Anypoint Password

-E

--environment-id

Environment ID

-O

--organization-id

Organization ID
You can also execute the jar with an -h or -help argument to access help.
To obtain the required values of your Environment ID and your Organization ID, you’ll have to use the Runtime Manager CLI. Through this tool, run the commands account business-group list and account environment list. Each returns a list with all of the available business groups / environments in your organization, together with the corresponding IDs for each.
If you prefer, instead of running this script once to handle your entire set of servers in one go, you can run it over as many separate batches of servers as you want. If you only register a few of your servers on the Runtime Manager and then run this script, it will configure the registered servers and ignore data about the additional servers that exist in the dump file but not on the platform, without raising any errors. If you then register more of your servers and run the script again, those servers that are already configured in the platform will be ignored and the script will only configure the newly added servers.
# Model Proxy Release Notes These release notes reflect enhancements, changes, and bug fixes for model proxy. In addition to these release notes, see: - [Omni Gateway Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes) ## [](#august-31-2026)August 31, 2026 ### What’s New - Model proxy now supports semantic caching, which stores and reuses LLM responses based on semantic similarity to reduce latency and cost. Semantic caching supports Azure AI Search as the vector database. See [Semantic Caching](#general::model-proxy.adoc#semantic-caching) and [Configuring Semantic Caching Services](#general::model-proxy-semantic-caching-service.adoc). - You can now secure model proxy connections with TLS by configuring a TLS context on the proxy consumer endpoint and on connections to provider endpoints. See [Create a Model Proxy](#general::model-proxy-create-model-proxy.adoc#create-a-model-proxy). - Model proxy can now authenticate to LLM providers by using a secret stored in an external vault (AWS Secrets Manager, Microsoft Azure Key Vault, or HashiCorp Vault). See [Create a Model Proxy](#general::model-proxy-create-model-proxy.adoc#create-a-model-proxy). - The Model Proxy Request Compression policy is now available for model proxies. See [Model Proxy Request Compression Policy](https://docs.mulesoft.com/gateway/latest/policies-included-llm-proxy-request-compression) and [Model Proxy Request Compression](https://docs.mulesoft.com/jp/release-notes/gateway/policies/llm-proxy-request-compression-release-notes). ## [](#august-6-2026)August 6, 2026 ### What’s New - LLM Proxy is now renamed to model proxy. - Model proxy now supports the Anthropic API format and native Anthropic models. See [Supported LLM Providers](#general::model-proxy.adoc#supported-llm-providers). ## [](#may-9-2026)May 9, 2026 ### What’s New - Model proxy now supports Advanced Scale semantic services that use vector databases to store up to 2000 utterance vectors per prompt topic. See [Configure an Advanced Scale Semantic Service](#general::model-proxy-semantic-service.adoc#configure-an-advanced-scale-semantic-service). - Agent Network now supports model proxies as Agent Broker LLM providers. See [Broker Project File References](https://docs.mulesoft.com/agent-network/latest/af-project-files#llmproviders-section). - Model proxy can now dynamically extract API Keys (such as OAuth 2.0 tokens) from incoming requests to support dynamic LLM provider authentication. - Model proxies now support NVIDIA Nemotron models. See [Supported Models](#general::model-proxy.adoc#brokers-section) - Anypoint Monitoring now provides new dashboards for cost management. ## [](#march-30-2026)March 30, 2026 ### What’s New Model proxy provides a unified access layer for multiple Large Language Model (LLM) providers. Model proxies are deployed to Omni Gateway to enable governance, intelligent routing, and cost management for AI applications. To learn more, see [general::model-proxy.adoc](#general::model-proxy.adoc). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Model Proxy Request Compression The Model Proxy Request Compression policy compresses replayed tool-result strings in Model Proxy request bodies before they reach the upstream provider, reducing billed input tokens. For configuration details, see [Model Proxy Request Compression Policy](https://docs.mulesoft.com/gateway/latest/policies-included-llm-proxy-request-compression). ## [](#august-27-2026)August 27, 2026 ### What’s New - Model Proxy Request Compression policy implementation version 1.0.0 is now supported by Omni Gateway. - Model Proxy Request Compression policy definition version 1.0.0 is now supported by Omni Gateway. # MongoDB Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for MongoDB supports integration using the MongoDB Java driver. Guide: [MongoDB Connector User Guide](https://docs.mulesoft.com/mongodb-connector/latest/) ## [](#6-4-3)6.4.3 **October 15, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.12

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.google.guava:guava library is upgraded to version 33.7.2-jre.

  • The org.apache.commons:commons-lang3 library is upgraded to version 3.21.0.

W-24410382, W-3300013
## [](#6-4-2)6.4.2 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.8

OpenJDK

8, 11, and 17
## [](#6-4-1)6.4.1 **July 30, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.8

OpenJDK

8, 11, and 17
## [](#6-4-0)6.4.0 **July 17, 2026** ### What’s New - Added support for OAuth 2.0 client credentials authentication via the new `oauth-client-credentials-connection` connection provider. This enables OIDC integration with MongoDB Atlas for secure, token-based authentication. ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.8

OpenJDK

8, 11, and 17
## [](#6-3-13)6.3.13 **June 11, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.8

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Adds an opt-in system property com.mulesoft.connector.mongo.skipIsoCoercionUnderOperatorKeys to skip implicit ISO-8601 string-to-Date coercion under MongoDB operator keys ($and, $or, $expr, $lte, etc.). Default behavior is unchanged.

W-22435658

The com.google.guava:guava dependency is upgraded to version 33.6.0-jre.

W-3300013

The com.google.code.gson:gson dependency is upgraded to version 2.14.0.

W-3300013

The commons-io:commons-io dependency is upgraded to version 2.22.0.

W-3300013

The org.apache.commons:commons-lang3 dependency is upgraded to version 3.20.0.

W-3300013
## [](#6-3-12)6.3.12 **April 19, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.6

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated internal dependencies and licensing components.

W-20579412
## [](#6-3-11)6.3.11 **December 4, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.6

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 dependency is upgraded to version 3.18.0.

W-20325782

The org.mongodb:mongodb-driver-legacy dependency is upgraded to version 5.6.1.

W-20325782

The com.google.guava:guava dependency is upgraded to version 33.5.0-jre.

W-20325782
## [](#6-3-10)6.3.10 **April 14, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 5.4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.mongodb:mongodb-driver-legacy dependency is upgraded to version 5.4.0.

W-18147022

The com.google.guava:guava dependency is upgraded to version 33.4.7-jre.

W-18147022

The commons-io:commons-io dependency is upgraded to version 2.18.0.

W-18147022

The com.google.code.gson:gson dependency is upgraded to version 2.12.1.

W-18147022

The org.apache.commons:commons-lang3 dependency is upgraded to version 3.17.0.

W-18147022

The org.mule.connectors:mule-file-connector dependency is upgraded to version 1.5.3.

W-18147022
## [](#6-3-9)6.3.9 **February 13, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.5.1

OpenJDK

8, 11, and 17
## [](#6-3-8)6.3.8 **October 10, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.5.1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.google.guava library is upgraded to version 32.0.1-jre to address reported security vulnerabilities.

W-13844855
## [](#6-3-7)6.3.7 **May 27, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.5.1
### Fixed Issues
Issue ID

The Find Document operation now validates an empty parameter in Sort By.

W-10848611
## [](#6-3-6)6.3.6 **April 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.5.1
### Fixed Issues
Issue ID

The Find Document operation now accepts a JSON object in Order By.

W-10889640
## [](#6-3-5)6.3.5 **January 24, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.1.1
### Fixed Issues
Issue ID

The Upsert parameter in the Update Documents operation threw an unexpected error due to incorrect response mapping.

SE-24189
## [](#6-3-4)6.3.4 **November 12, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.1.1
### Fixed Issues
Issue ID

Fixed vulnerability issues.

CONN-9255
## [](#6-3-3)6.3.3 **June 1, 2021** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.1.1
### [](#fixed-issues-11)Fixed Issues - A collection of DateTime elements were saved as String objects instead of DateTime objects when inserted into an array. (SE-20881) ## [](#6-3-2)6.3.2 **April 27, 2021** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.1.1
### [](#fixed-issues-12)Fixed Issues Connection leaks sometimes occurred when using a dynamic configuration. (SE-20605) ## [](#6-3-1)6.3.1 **February 2, 2021** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.1.1
### [](#new-features)New features MongoDB driver 4.1.1 is now supported. ## [](#6-3-0)6.3.0 **August 31, 2020** ### [](#compatibility-18)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB, MongoDB Atlas

MongoDB Java driver 3.11 through 4.1
### [](#changes)Changes - Added the **Connection String** connection type, which is compatible with MongoDB Atlas and MongoDB on-premises. - The **Execute Command** operation now provides output metadata. ### [](#fixed-issues-13)Fixed Issues - The **Encoding** field was not shown in the connector configuration. - The **Read Preference**, **Read Concern**, and **Write Concern** options from the connector configuration were ignored. ## [](#6-2-1)6.2.1 **August 7, 2020** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11 through 4.0.4
### [](#fixed-issues-14)Fixed Issues - Fixed the `NoSuchMethodError` error in the Insert Document operation when using MongoDB Java driver 3.x. (CONN-6536) - Fixed the issue that caused the WriteConcernValueProvider to parse ENUM text as INT. (SE-16819) - Fixed the issue that caused connection leaks when using dynamic configuration. (SE-16959) ## [](#6-2-0)6.2.0 **June 30, 2020** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11 through 4.0.4
### [](#changes-2)Changes Added compatibility for MongoDB Driver Legacy 4.0.4 ## [](#6-1-1)6.1.1 **May 13, 2020** ### [](#compatibility-21)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11 and later
### [](#fixed-issues-15)Fixed Issues When you add the required MongoDB driver to the connector configuration, the `Add recommended libraries` option now works as expected. (CONN-5976) ## [](#6-1-0)6.1.0 **March 27, 2020** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11 and later
### [](#fixed-issues-16)Fixed Issues Using the Insert documents operation with the Write ordered field set to `true` resulted in an incorrect response. (SE-15222) ### [](#new-features-2)New Features At runtime, you can now overwrite the Write concern acknowledgement and Write concern timeout fields in the global element of the Find documents, Insert document, Insert documents, Update Documents, and Count documents operations. ## [](#6-0-0)6.0.0 **February 20, 2020** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11 and later
### [](#changes-3)Changes - Removed the Connection String connection type. There is now a single, unified generic connection. - Removed the Metadata configuration section. The connector uses the latest document in a collection to infer the metadata. - Added new parameters to the connector configuration. - Changed operation names, metadata, fields, and values. - Removed some operations. - Changed input sources. - Improved the error types. - Added the ability to specify which MongoDB Java driver to use. For more information, see [MongoDB - Upgrade and Migrate](https://docs.mulesoft.com/mongodb-connector/latest/mongodb-connector-upgrade-migrate). ## [](#5-4-2)5.4.2 **March 17, 2020** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11.0
### [](#fixed-issues-17)Fixed Issues - Fixed more issues related to the Insert Documents operation. (SE-15222) ## [](#5-4-1)5.4.1 **March 16, 2020** ### [](#compatibility-25)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11.0
### [](#fixed-issues-18)Fixed Issues - Using the insertDocuments operation with the flag `writeOrdered=true` resulted in an incorrect response. (SE-15222) ## [](#5-4-0)5.4.0 **February 20, 2020** ### [](#compatibility-26)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11.0
### [](#new-features-3)New Features MongoDB Connector now supports the retryWrites option. Use the **Retry writes** field when configuring a connection to enable this option. ## [](#5-3-3)5.3.3 **October 24, 2019** ### [](#compatibility-27)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11.0
### [](#fixed-issues-19)Fixed Issues - Fixed security vulnerability reported in Guava 18.0 library by upgrading to version 24.1.1-jre. (SE-3184) - Fixed security vulnerability reported in Jackson-Databind 2.9.2 library by replacing it with Gson 2.8.5. (SE-3183) ## [](#5-3-2)5.3.2 **August 23, 2019** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.11.0
### [](#new-features-4)New Features - Updated MongoDB Java driver to 3.11.0. ### [](#fixed-issues-20)Fixed Issues - Apps containing the MongoDB connector could not be redeployed in the Windows OS. (SE-12762) ## [](#5-3-1)5.3.1 **April 15, 2019** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.8
### [](#fixed-issues-21)Fixed Issues - MongoDB `get-file-content` operation expects user to pass internal type of connector. (SE-10073) - MongoDB triggers fails with `java.lang.NullPointerException`. (SE-11354) - Domain name did not have a recognized public suffix for the MongoDB connector. (SE-10149) ## [](#5-3-0)5.3.0 **September 26, 2018** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.0.0 and later

MongoDB

MongoDB Java driver 3.8
### [](#new-features-5)New Features - Added **New Object**, **Modified Object**, and **Deleted Object** triggers. These triggers allow you to execute a flow each time a MongoDB object is created, modified, or deleted. ## [](#5-2-0)5.2.0 **September 4, 2018** ### [](#compatibility-31)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.8
### [](#new-features-6)New Features - Added the new operation **Execute Generic Command** to run any MongoDB command using the connector. This command is supplied as a parameter in the form of a MongoDB document. - MongoDB Java Driver Update - The connector has been updated with the MongoDB Java Driver v3.8.0. ## [](#5-1-1)5.1.1 **June 28, 2018** ### [](#compatibility-32)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.6
### [](#fixed-issues-22)Fixed Issues - Connector did not work using the 3.6 driver when a TLS global context was not present. This error appeared: ```text 2018-06-28T18:07:06.764+0000 I NETWORK [conn262] Error receiving request from client: SSLHandshakeFailed: SSLHandshakeFailed. Ending connection from ... ``` ## [](#5-1-0)5.1.0 **June 28, 2018** ### [](#compatibility-33)Compatibility
Software Version

Mule

4.1.1 and later

MongoDB

MongoDB Java driver 3.6
### [](#new-features-7)New Features - MongoDB Java Driver Update - The connector has been updated with the MongoDB Java Driver v3.6.0. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Moodle Connector Release Notes Anypoint Connector for Moodle (Moodle Connector) enables Mule applications to access the Moodle API. Guide: [Moodle Connector User Guide](https://docs.mulesoft.com/moodle-connector/latest/) ## [](#0-1-3)0.1.3 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-2)0.1.2 **August 24, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **April 14, 2026** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/moodle-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [Moodle Connector User Guide](https://docs.mulesoft.com/moodle-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [Moodle Connector User Guide](https://docs.mulesoft.com/moodle-connector/latest/) - [Moodle Connector Reference](https://docs.mulesoft.com/moodle-connector/latest/moodle-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MQTT Connector Release Notes Anypoint Connector for MQTT (MQTT Connector) is an MQTT (Message Queuing Telemetry Transport) v3.x protocol-compliant MuleSoft extension. MQTT is a lightweight publish/subscribe messaging protocol designed for connecting remote devices with a small code footprint and minimal network bandwidth. Guide: [MQTT Connector User Guide](https://docs.mulesoft.com/mqtt3-connector/latest/) ## [](#1-1-1)1.1.1 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-0)1.1.0 **August 19, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.20.0 to address reported security vulnerabilities.

W-3300013
## [](#1-0-6)1.0.6 **July 28, 2025** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

MQTT Connector now uses deferred connections to avoid losing messages when reconnecting.

W-14248056

Updated org.apache.commons:commons-lang3 from 3.12.0 to 3.18.0.

W-19150162
## [](#1-0-5)1.0.5 **May 6, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-4)1.0.4 **December 28, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

When there are two On New Message sources using the same configuration, they now successfully reconnect.

W-14562276
## [](#1-0-3)1.0.3 **September 20, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 and later
### Fixed Issues
Issue Resolution ID

The On New Message listener source now successfully completes the reconnection.

W-13854587
## [](#1-0-2)1.0.2 **April 4, 2023** ### Compatibility
Application/Service Version

Mule

4.3.0 and later
### Fixed Issues
Issue ID

The Publish operation now reconnects successfully.

W-12413989
## [](#1-0-1)1.0.1 **March 2, 2022** ### Compatibility
Application/Service Version

Mule

4.3.0 and later
### Fixed Issues
Issue ID

External library not detected for the MQ connection configuration.

W-10582974
## [](#1-0-0)1.0.0 **September 10, 2021** ### What’s New New connector. For a list of supported configurations and operations, refer to the MQTT Connector Reference Guide. ### Compatibility
Application/Service Version

Mule

4.3.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.0.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.0.0 implements all security updates and bug fixes from 3.8.7. ## [](#october-26-2023)October 26, 2023 ## What’s New - Reported security vulnerabilities are now fixed. - This release drops support to Maven 3.8 and adopts Maven 3.9. If you are using a Mule Maven plugin version 3.8.x or earlier, ensure you upgrade your projects to use the plugin’s latest version. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple Mac OS X 10.15.0+ - Linux (tested on Ubuntu 15) - Java 8 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
To use the new Mule runtime version schema introduced with Mule 4.5 to deploy apps, you must use Mule Maven plugin version 4.1.0 or later.
## Fixed Issues
Issue Resolution ID

Mule runtime production deployment no longer fails when using Maven 3.9.

W-12544597
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.1.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.1.0 implements all security updates and bug fixes from 4.0.0. ## [](#february-6-2024)February 6, 2024 ## What’s New - Mule Maven plugin now supports Mule runtime version schema and all associated tags. This incorporation doesn’t break existing CI/CD pipelines. - Reported security vulnerabilities are now fixed. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple Mac OS X 10.15.0+ - Linux (tested on Ubuntu 15) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

disableCloudhubLogs now uses a default value, overriding the value configured if the parameter isn’t present in the POM file.

W-14653854

The error "Could not find imported resource" no longer occurs during the build.

W-14673992

NullPointerException in XSD parsing no longer occurs when a schema defines minVersion/maxVersion.

W-14748090

NullPointerException no longer occurs when deploying to CloudHub 2.0.

W-14853621

The plugin now allows you to configure the Java version and release channel in your CloudHub deployment.

W-14137736

Duplicate validations of the Mule version in Mule Maven plugin no longer occur. Validations are now done by the internal API, allowing you to configure the Java and channel versions when deploying.

W-14137714
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.1.1 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.1.1 implements all security updates and bug fixes from 4.1.0. ## [](#february-20-2024)February 20, 2024 ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple Mac OS X 10.15.0+ - Linux (tested on Ubuntu 15) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

The plugin now allows you to configure the javaVersion and releaseChannel in your CloudHub 2.0 deployment.

W-15060415

Null Validation is now removed for muleVersion.

W-15060386
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.1.2 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.1.2 implements all security updates and bug fixes from 4.1.1. ## [](#april-25-2024)April 25, 2024 ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple Mac OS X 10.15.0+ - Linux (tested on Ubuntu 15) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

A connector provider configuration is added to avoid issues in certain environments.

W-15186546
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.10.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.10.0 implements all security updates and bug fixes from 4.9.1. ## [](#june-2-2026)June 2, 2026 ## What’s New - Mule Maven Plugin 4.10.0 now supports building and deploying applications that target Mule runtime engine 4.12.0. For information about the release notes, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.15
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.10.1 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.10.1 implements all security updates and bug fixes from 4.10.0. ## [](#july-14-2026)July 14, 2026 ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.15
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

NoSuchMethodError errors no longer occur when running the process-classes goal with Mule Maven plugin.

W-23187928
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.10.2 Release Notes (Deprecated) Use the Mule Maven plugin to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.10.2 implements all security updates and bug fixes from 4.10.1. ## [](#october-7-2026)October 7, 2026 ## What’s New - Mule Maven plugin now supports building and deploying applications that target Mule runtime engine 4.13.0. To build and deploy these applications, upgrade to Mule Maven plugin 4.10.2 or later. For more information, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.15
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

Application properties configured in Runtime Manager are no longer cleared when you redeploy an application to on-premises servers by using armDeployment. The plugin now sends properties only when they’re defined in the plugin configuration.

W-24207441

The Mule Maven plugin now determines which Java versions are supported based on the minMuleVersion value declared in the mule-artifact.json file. The plugin uses this information to validate the javaSpecificationVersions value at build time.

W-24192837

The build now fails if javaSpecificationVersions in the mule-artifact.json file contains a Java version that the Mule version set in minMuleVersion doesn’t support. The plugin checks the Mule runtime engine support matrix, or a bundled copy for offline builds. To skip this validation, set -DskipJavaVersionValidation=true.

W-24192843
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.10.3 Release Notes Use the Mule Maven plugin to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.10.3 implements all security updates and bug fixes from 4.10.1. ## [](#october-19-2026)October 19, 2026 ## What’s New - Mule Maven plugin now supports building and deploying applications that target Mule runtime engine 4.13.1. To build and deploy these applications, upgrade to Mule Maven plugin 4.10.3 or later. For more information, see [mule-runtime/mule-4.13.1-release-notes.adoc](#mule-runtime/mule-4.13.1-release-notes.adoc). ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.15
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

Application properties configured in Runtime Manager are no longer cleared when you redeploy an application to on-premises servers by using armDeployment. The plugin now sends properties only when they’re defined in the plugin configuration.

W-24207441

The Mule Maven plugin now determines which Java versions are supported based on the minMuleVersion value declared in the mule-artifact.json file. The plugin uses this information to validate the javaSpecificationVersions value at build time.

W-24192837

The build now fails if javaSpecificationVersions in the mule-artifact.json file contains a Java version that the Mule version set in minMuleVersion doesn’t support. The plugin checks the Mule runtime engine support matrix, or a bundled copy for offline builds. To skip this validation, set -DskipJavaVersionValidation=true.

W-24192843
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.2.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.2.0 implements all security updates and bug fixes from 4.1.2. ## [](#may-31-2024)May 31, 2024 ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple Mac OS X 10.15.0+ - Linux (tested on Ubuntu 15) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

Mule Maven Plugin no longer fails when packaging mule-plugin with missing properties.

W-14998627

Log4j now works as expected in Mule Maven Plugin 4.

W-15252816

Redeploys to CloudHub 2.0 no longer remove the properties when there aren’t properties set in your POM file.

W-14550915
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.2.1 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.2.1 implements all security updates and bug fixes from 4.2.0. ## [](#august-22-2024)August 22, 2024 ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple Mac OS X 10.15.0+ - Linux (tested on Ubuntu 15) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

The plugin command maven mule:deploy now respects the Maven proxy settings defined in settings.xml.

W-16046872

Deployment to CloudHub 2.0 using Mule Maven plugin now correctly takes the application name into account.

W-16218223
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.3.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.3.0 implements all security updates and bug fixes from 4.2.1. ## [](#september-26-2024)September 26, 2024 ## What’s New Deployment to CloudHub 2.0 using Mule Maven plugin now enables the configuration of additional parameters: `persistentObjectStore`, `tracingEnabled`, and `autoscaling` (replaces `replicas`). See [Deploy Applications to CloudHub 2.0 Using the Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub-2). ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple Mac OS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

The command mule:deploy now takes maven PROXY settings into account. This function is available in Mule Maven plugin 4.

W-16046872
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Maven Plugin 4.3.1 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.3.1 implements all security updates and bug fixes from 4.3.0. ## [](#october-25-2024)October 25, 2024 ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

Apache5Connector no longer fails when deploying to CloudHub.

W-16911016

Mule Maven plugin 4.3.0 no longer fails with the java.lang.String cannot be cast to java.lang.Number error.

W-16909521
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.4.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.4.0 implements all security updates and bug fixes from 4.3.1. ## [](#february-6-2025)February 6, 2025 ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

The redeploy process on CloudHub 2.0 and Runtime Fabric is now improved.

W-17013325
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.5.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.5.0 implements all security updates and bug fixes from 4.4.0. ## [](#april-3-2025)April 3, 2025 ## What’s New - Mule Maven plugin now supports Horizontal Pod Autoscaling (HPA) for Runtime Fabric deployments. - Mule Maven plugin now automatically exports DataWeave files. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.8 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.5.1 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.5.1 implements all security updates and bug fixes from 4.5.0. ## [](#june-19-2025)June 19, 2025 ## What’s New - The `javaSpecificationVersions` property in `mule-artifact.json` is now supported. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.10 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.5.2 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.5.2 implements all security updates and bug fixes from 4.5.1. ## [](#september-2-2025)September 2, 2025 ## What’s New - This release includes fixes for vulnerabilities. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.10 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.5.3 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.5.3 implements all security updates and bug fixes from 4.5.2. ## [](#september-22-2025)September 22, 2025 ## What’s New - This release includes fixes for vulnerabilities. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, and 17 - Maven 3.9.0 to 3.9.10 ## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.6.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.6.0 implements all security updates and bug fixes from 4.5.2. ## [](#october-3-2025)October 3, 2025 ## What’s New - Mule Maven plugin now supports Java 21. - Mule Maven plugin now supports Universal Connectivity connectors. - Mule Maven plugin now compiles applications using the Mule framework. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.10
Mule Maven plugin 4.6.0 supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.6.1 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.6.1 implements all security updates and bug fixes from 4.6.0. ## [](#december-2-2025)December 2, 2025 ## What’s New - This release includes fixes for vulnerabilities. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.10
Mule Maven plugin 4.6.0 supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.7.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.7.0 implements all security updates and bug fixes from 4.6.1. ## [](#february-3-2026)February 3, 2026 ## What’s New - This release includes fixes for vulnerabilities. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.12
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.8.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.8.0 implements all security updates and bug fixes from 4.7.0. ## [](#march-12-2026)March 12, 2026 ## What’s New - This release includes fixes for vulnerabilities. - Mule Maven Plugin now supports configuring CloudHub 2.0 application endpoints by using `endpoint`. For configuration details, see [Deployment Settings](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub-2#deployment-settings). ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.12
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

Mule Maven Plugin now supports configuring application endpoints for CloudHub 2.0 deployments, including the access and pathRewrite attribute.

W-19431539

Mule Maven Plugin now uses the repository defined by the maven.repo.local property when validating the local repository, instead of defaulting to the .m2/repository directory.

W-20136936
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com/s/) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.9.0 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.9.0 implements all security updates and bug fixes from 4.8.0. ## [](#april-16-2026)April 16, 2026 ## What’s New - This release includes fixes for vulnerabilities. - You can now specify deployment properties using the `propertiesFile` parameter instead of defining them inline. This option is supported for deployments to [CloudHub](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub#cloudhub-deploy-reference), [CloudHub 2.0](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub-2#cloudhub2-deploy-reference), [Anypoint Runtime Fabric](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-rtf#rtf-deploy-reference), and [On-Premises](https://docs.mulesoft.com/mule-runtime/latest/deploy-on-premises#arm-deploy-reference). ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.14
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## Fixed Issues
Issue Resolution ID

Maven package execution now works correctly when defining classLoaderModelLoaderDescriptor in mule-artifact.

W-20051623
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com/s/) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin 4.9.1 Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. Mule Maven Plugin 4.9.1 implements all security updates and bug fixes from 4.9.0. ## [](#may-11-2026)May 11, 2026 ## What’s New - This release includes fixes for vulnerabilities. ## [](#hardware-and-software-requirements)Hardware and Software Requirements - Microsoft Windows 10 - Apple macOS X 10.15.0+ - Linux (tested on Ubuntu 22) - Java 8, 11, 17, and 21 - Maven 3.9.0 to 3.9.15
Mule Maven plugin supports Java 8, 11, 17, and 21. The minMuleVersion specified in your Mule application must be compatible with the Java version used to run the plugin.
## Compatibility
Software Version

Mule runtime engine

4.3 or later

Anypoint Studio

7.x
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) - [Mule Maven Plugin](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept) # Mule Maven Plugin Release Notes The Mule Maven plugin enables you to integrate the packaging and deployment of your Mule applications with your Maven lifecycle. - [Mule Maven Plugin 4.10.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.3-release-notes) - [Mule Maven Plugin 4.10.2 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.2-release-notes) - [Mule Maven Plugin 4.10.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.1-release-notes) - [Mule Maven Plugin 4.10.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.0-release-notes) - [Mule Maven Plugin 4.9.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.9.1-release-notes) - [Mule Maven Plugin 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.9.0-release-notes) - [Mule Maven Plugin 4.8.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.8.0-release-notes) - [Mule Maven Plugin 4.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.7.0-release-notes) - [Mule Maven Plugin 4.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.6.1-release-notes) - [Mule Maven Plugin 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.6.0-release-notes) - [Mule Maven Plugin 4.5.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.5.3-release-notes) - [Mule Maven Plugin 4.5.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.5.2-release-notes) - [Mule Maven Plugin 4.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.5.1-release-notes) - [Mule Maven Plugin 4.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.5.0-release-notes) - [Mule Maven Plugin 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.4.0-release-notes) - [Mule Maven Plugin 4.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.3.1-release-notes) - [Mule Maven Plugin 4.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.3.0-release-notes) - [Mule Maven Plugin 4.2.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.2.1-release-notes) - [Mule Maven Plugin 4.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.2.0-release-notes) - [Mule Maven Plugin 4.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.1.2-release-notes) - [Mule Maven Plugin 4.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.1.1-release-notes) - [Mule Maven Plugin 4.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.1.0-release-notes) - [Mule Maven Plugin 4.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.0.0-release-notes) ## [](#support)Support - Access the [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) to pose questions and get help from MuleSoft’s broad community of users. - To access MuleSoft’s expert support team, [subscribe to Mule ESB Enterprise](mailto:sales@mulesoft.com) and log in to MuleSoft’s Customer Portal. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime 4.3.0 Release Notes Initial Release: April 30, 2020 Mule 4.3.0 includes enhancements, changes, fixes, and patch update releases. This release is also focused on implementing several performance upgrades. ## [](#july-2024)July 2024 Patch release version: 4.3.0-20240619 This patch update addresses the following issues:
Description Issue

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws the groovy.lang.MissingMethodException exception.

W-15750766

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

Transactional edition and gatekeeper features are now added to version 4.3.0.

W-15641847

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas.

W-15769926

Logging for Gateway Analytics initialization is now improved.

W-15904845

Handling of connection errors with API platform is now improved.

W-15809377

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert.

W-15427352

Resiliency is now improved on policy application and updates.

W-15426528
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2024)May 2024 Patch release version: 4.3.0-20240424 This patch update addresses the following issues:
Description Issue

Jackson Databind is upgraded to version 2.13.5.

W-15427761

org.json:json is upgraded to version 20231013.

W-15428060

Snakeyaml is upgraded to version 2.0.

W-15428154

Jackson dependencies are upgraded to v2.15.0 in 4.3.x.

W-15575262
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2024)April 2024 Patch release version: 4.3.0-20240408 This patch update addresses the following issues:
Description Issue

Spring is upgraded to 5.3.33.

W-15260752

Explicit socket connection timeout for socket creation with the management plane no longer occurs.

W-14555248

Template parser validation is now improved.

W-15141905
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2023)November 2023 Patch release version: 4.3.0-20231026 This patch update addresses the following issues:
Description Issue

The org.apache.santuario:xmlsec library is upgraded to 2.3.4.

W-14358602

Multiple redeployments of applications linked to a domain project sharing IBM MQ Connector now works as expected.

W-12388528

OutOfMemoryError no longer occurs after multiple redeployments of applications with Scripting module and Groovy.

W-13038823
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2023)July 2023 Patch release version: 4.3.0-20230616 This patch update addresses the following issues:
Description Issue

Kryo is upgraded to version 4.0.3.

W-13499198

The java.lang.NullPointerException error no longer appears while refreshing an OAuth token.

W-12975498
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2023)May 2023 Patch release version: 4.3.0-20230417 This patch update addresses the following issues:
Description Issue

Added a new method for CoreServiceClient.

W-12659177

This release displays the policy definition version.

W-12733032
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2023)April 2023 Patch release version: 4.3.0-20230320 This patch update addresses the following issues:
Description Issue

Added Groovy to the default allowed scripting languages for logging.

W-12708905

Second Scatter Gather router does not execute when it has a Try scope for each component that raises an error handler within.

W-10619784

Parallel For Each gets stuck with global Error Handler operation.

W-12556497

Transactions in nested Try scope with global Error Handling.

W-12671732

Combinations of First Successful router and Raise Error component no longer causes executions to hang.

W-10619792 / MULE-19874
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2023)March 2023 Patch release version: 4.3.0-20230217 This patch update addresses the following issues:
Description Issue

DB Connector’s prepareArray and preparaStruct functions now work as expected when using them inside of a Scatter-Gather.

W-11932094

Requests no longer fail with NullPointerException: value with applications referencing a global Error Handler.

W-12535932

Log4j scripting now supports Nashorn languages by default.

W-12549148

This release updates snakeyaml to version 1.33.

W-12429030

This release updates org.json:json to version 20220924.

W-12450128
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2023)February 2023 Patch release version: 4.3.0-20230123 This patch update addresses the following issues:
Description Issue

Applications with an XML SDK connector now deploy correctly.

W-12362157

The Error Handler now contains the Event Id and Processor when handling issues from an HTTP Requester.

W-12245765

WSC connector with an HTTP Requester configuration no longer fails when using a domain project.

W-12407839

This release upgrades the log4j dependency to version 2.19.

W-12353442

This release upgrades the org.apache.cxf:cxf-core library to version 3.5.5.

W-12354020

This release upgrades the`com.hazelcast:hazelcast` dependency to version 3.12.13.

W-12354026

CloudHub applications no longer fail when using Global Error Handlers with a default configuration.

W-12218381

The insecure connection configuration in the TLS Configuration truststore now works as expected.

W-10822938

You can now start Mule in FIPS mode using any security provider.

W-12060316
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2023)January 2023 Patch release version: 4.3.0-20221212 This patch update addresses the following issues:
Description Issue

Distributed locks are now released properly when a policy is disabled.

W-11929632

The error Can’t perform operation on 'Object_store'. ObjectStore not initialized no longer occurs when a redelivery policy that points to an object store is declared as a top level element.

W-11985583

Setting a variable with a null value inside a Batch Aggregator component no longer fails with a NullPointerException.

W-11825409

The use of HTTP Insecure mode in a connector no longer fails with a NullPointerException.

W-12049036

The Idempotent Validation filter now cascades object store exceptions. Using the filter on Mule version 4.4 or earlier requires the property mule.rethrowExceptionsInIdempotentMessageValidator=true.

W-11529823

The XML SDK’s implicit configuration creation is disabled by default.

W-12113550

The Tanuki wrapper is upgraded to 3.5.51.

W-12068528
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. This patch release addresses the following DataWeave issues:
Description Issue

The FlatFile module now provides a reader property, retainEmptyStringFieldsOnParsing, for handling fields that lack values. When set to true, this property makes the reader retain these fields and set their values to an empty string. The default behavior of the reader is to remove those fields.

W-12036336

Data payloads without line breaks no longer work when using lenient as the recordParsing property. The other options to recordParsing support records that lack line breaks. noTerminator is preferred for fixed-length records that lack a line break.

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

November patch update 4.4.0-20221111 addresses a regression in the previous November patch update, 4.4.0-20221026, and includes the fixes in that patch.
### [](#patch-4-3-0-20221111)Patch 4.3.0-20221111 Patch release version: 4.3.0-20221111 This patch update addresses the following Mule issues:
Issue Resolution ID

Using the insecure="true" attribute of the trust-store no longer throws NullPointerException.

W-12049036
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-3-0-20221024)Patch 4.3.0-20221024 Patch release version: 4.3.0-20221024 This patch update addresses the following issues:
Issue Resolution ID

Applications that depend on a domain to load resources no longer fail with a "Couldn’t find resource: neither on classpath or in file system" error.

W-11625237

The insecure="true" attribute of the trust-store config is now honored when additional properties are defined. Use the system property mule.honour.insecure.tls.configuration=true to apply this behavior in Mule 4.4 or earlier.

W-10822938

Error mapping is no longer executed when an error occurs inside of an operation policy.

W-11861168

To avoid XML SDK implicit configuration creation, this release adds the system property mule.disableXmlSdkImplicitConfigurationCreation=true.

W-10634129

Transactions now honor the Transaction Timeout configured in the Try scope.

W-11741912

In API Gateway, SLA deletion no longer generates an inconsistent contract status.

W-11898295
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. This release includes only non-user-impacting changes. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2022)October 2022 Patch release version: 4.3.0-20220922 This patch update addresses the following issues:
Description Issue

Improved memory consumption when using global error handler.

W-11503016

HTTP connections no longer have a leak that prevents new connections from opening.

W-11622837

TransactionTimeout is now set correctly on XA Transactions, preventing stale connections.

W-11741912

Improved the compatibility of SQLServer when using XA Transactions with Bitronix.

W-11228596
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. This patch release addresses the following DataWeave issues:
Description Issue

The Could not read from file store caused by Negative seek offset error no longer occurs when transforming big XML files.

W-11620006
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2022)September 2022 Patch release version: 4.3.0-20220824 This patch update addresses the following issues:
Description Issue

Tanuki wrapper upgraded from 3.5.45 to 3.5.50 to support M1 (ARM) architecture.

W-11242363

Applications no longer fail to start with a Prefix URI must be not blank error.

W-11627710

XML SDK modules now support implicit configurations.

W-10634129

Log levels for successful source reconnections are now set to INFO.

W-11437305

Expired access tokens now refresh on connectors using OAuth2.

W-11535924
There is no DataWeave update for this version this month. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2022)August 2022 Patch release version: 4.3.0-20220725 This patch update addresses the following issues:
Description Issue

Global Error Handler configurations no longer roll back transactions that should not roll back.

W-11324530

CXF is upgraded to version 3.5.1.

W-11267666

Mule no longer duplicates lifecycle phases for global Error Handler configurations.

W-11117613

Mule runtime no longer produces the following warning: An expression value was given for parameter 'variableName' but it doesn’t support expressions".

W-10998630

Caching issues no longer cause a policy to use data from the wrong operation and produce Element and Element DSL mismatches with the flow stack.

W-11403067

A memory leak no longer occurs when using JMS Connector with ActiveMQ.

W-10583584

Error mapping now works while deploying a custom Header Injection policy.

W-11147961
There is no DataWeave update for this version this month. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2022)July 2022 Patch release version: 4.3.0-20220622 This patch update addresses the following issues:
Description Issue

Spring upgraded from 5.3.18 to 5.3.21.

W-11300535

Jackson upgraded to 2.13.3.

W-11139348
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The July patch release addresses the following DataWeave issues:
Description Issue

This releases fixes Avro property handling.

W-11324418

The DataWeave Avro module now correctly converts logical types.

W-10981989/SE-16167
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2022)June 2022 Patch release version: 4.3.0-20220523 This patch update addresses the following issues:
Description Issue

File attributes are no longer removed when using Parallel For Each.

W-10848628

FIPS enabled Mule Clusters no longer throw a java.nio.BufferUnderflowException warning when using the RetrieveAll operation on an Object Store.

W-10884325

The AS400 connector now properly receives a JSON response instead of org.mule.runtime.core.internal.util.message.stream.UnclosableCursorStream.

W-11093225

Added logging to AbstractQueueStoreDelegate to describe why a record was not successfully queued.

W-11086587

Updated the error message shown when a Batch component cannot queue records.

W-11086577

Mule now raises an ExceptionNotification error when ExtensionMessageSource fails to start.

W-10619908

Mule applications no longer crash due to an unhandled IllegalStateException error when processing a batch block.

W-10742153

Mule now fails as expected if the event source configuration for the application is incorrect.

W-10619908

Upgraded Spring dependency from 5.1.20 to 5.3.18.

W-10989650

Mule application deployment properties are no longer lost after domain redeployment.

W-10984029

A memory leak no longer occurs after redeploying multiple times an application that uses the IBM MQ connector.

W-10672197
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The June patch release addresses the following DataWeave issues:
Description Issue

The FlatFile module now includes the allowLenientWithBinaryNotEndElement property to support existing behavior.

W-10935528

DataWeave no longer throws exceptions when using the default operator with fromBase64.

W-10648825
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2022)April 2022 Patch release version: 4.3.0-20220321 This patch update addresses the following issues:
Description Issue

Race conditions no longer occur when running parallel deployments.

W-10672687/SE-23764

Custom connector POST requests no longer send the body as NULL when handling empty payloads.

W-10818822

The redirect implementation properly handles the "Preserve Header Case" configuration.

W-10822777
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2022)March 2022 Patch release version: 4.3.0-20220221 This patch update addresses the following issues:
Description Issue

Set-Cookie is now handled correctly after a redirect request.

W-10667146 / MULE-19942

When disposing of an application, Mule no longer throws an IOException error indicating that the underlying JAR file is in use.

W-10674462 / SE-23775

After a failed HTTP request, applications no longer stop when reading the error payload in the error handler.

W-10681471 / MULE-19537

LifecycleObjectSorter and dependency resolvers implemented in this release reduce application deployment time.

W-10745606 / W-10746226 / MULE-19984

Thread-local interference no longer occurs when a task is scheduled for execution on the same thread due to thread-pool exhaustion. One possible symptom was a transaction not being properly cleaned up under heavy load, followed by nested transaction errors.

W-10619599 / MULE-20072 / SE-24241
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2022)February 2022 Patch release version: 4.3.0-20220124 This patch update addresses the following issues:
Description Issue

Anypoint Connector for Box (Box Connector) no longer fails to recreate the input stream after an access token refresh, preventing a stream closed issue.

MULE-20001/SE-23666

A concurrent connection limitation in Anypoint Connector for NetSuite (NetSuite Connector) no longer occurs.

MULE-19937/SE-22359

The readiness check performed when deploying on Runtime Fabric is now processed correctly.

SE-22948/SE-22585

Running multiple MUnit cases together no longer causes a No bean named '_muleDefaultObjectSerializer' available error.

MULE-20012/SE-23407

Anypoint Connector for Google Calendar (Google Calendar Connector) no longer overwrites the access_token, which prevents generating incorrect results.

MULE-20019/SE-23584

Mule no longer returns an incorrect CONNECTIVITY error type when a ConnectionException is thrown when using the Java SDK.

MULE-19895/SE-24091

Mule no longer performs a thread switch in a transactional context that uses multithread and the same cache-key.

EE-8216/SE-23816

Global property values of a module are now accessible within a private operation that is invoked within a flow control component.

MULE-19962/MULE-19035/SE-22282
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The February patch release addresses the following DataWeave issues:
Description Issue

Corrected the documentation for the Periods::between function.

DW-1070

Upgraded the edi-parser with SLF4J.

CONN-9598
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2022)January 2022 Patch release version: 4.3.0-20211222 This patch update addresses the following issues:
Description Issue

The FlowProcessMediator no longer leaks the payload of the first request.

MULE-19869

If the redelivery policy is exhausted in a source configured with transactions, Mule no longer raises an error that runs in a loop.

MULE-19915

Processors in subflows now get the processing strategy of the root flow.

MULE-19924

MUnit tests now initialize object stores inside redelivery policies.

MULE-19928/SE-20765

Autogenerated Mule connectors no longer fail with NumberFormatException errors.

MULE-19871/SE-21463

Applications that implement a VM Listener source no longer raise java.lang.IllegalStateException: No connection has been bound errors and quit.

SE-22172

This releases fixes performance issues with the Web Service Consumer connector when deployed in CloudHub.

SE-22245

You can now redeploy applications that were in a stopped state when they were deleted.

MULE-19890/SE-22261

DataWeave now escapes the \ symbol when used in combination with the " symbol.

MULE-19900/SE-22346

The batch processing On Complete phase no longer fails if it encounters an error stream.

EE-8020/SE-22386

Logs no longer show reconnection successful messages when reconnection attempts to the FTP server are exhausted because the server is unavailable.

SE-22434

Transactions opened by the JMS Listener are no longer rolled back.

MULE-19919/SE-23039

You can now perform parallel deployments of apps that are linked to a domain and share a configuration.

MULE-19912/SE-23123

Mule now recognizes Eclipse Temurin by Adoptium (formerly Adopt OpenJDK project) as a recommended JDK Vendor and no longer raises an INFO-level log message.

MULE-19917/SE-23354

Apache Commons Compress upgraded to version 1.21.

EE-8088

GSON upgraded to version 2.8.9.

EE-8154

When a source is configured to use transactions, and the message ID for the redelivery policy is blank or null, the source no longer fails to find the redelivery attempts counter.

MULE-19921

You can now use the inline string array parameter on operations defined with the Mule XML SDK.

MULE-19853

Kryo updated to version 4.0.2.

EE-8153

Apache Velocity updated.

EE-8010

MUnit no longer fails with a RejectedExecutionException error.

SE-22728

Scheduler runs using cron expressions are no longer rejected if other scheduler components are under back pressure.

SE-22941

An issue that caused a No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available error no longer occurs.

MULE-19896/SE-23142

A performance degradation related to processing parallel requests for applications deployed to the latest Mule runtime version in Runtime Fabric no longer occurs.

EE-8150/SE-23510

The JMS Connector no longer leaks connections and now honors connection pools in XA mode with Solace JMS.

MULE-19848/SE-22284
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The January patch release addresses the following DataWeave issues:
Description Issue

DataWeave now shows the root cause of an error when an exception occurs while reading an input.

SE-22939

This release resolves an OutOfMemory error when using the writeLinesWith function, which affected the ndjson module.

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

November patch update 4.3.0-20211104 addresses a regression in the previous November patch update, 4.3.0-20211026, and includes the fixes in that patch.

  • If you installed the previous November patch, 4.3.0-20211026, install patch 4.3.0-20211104 to address the regression.

  • If you did not install the previous November patch, 4.3.0-20211026, skip that patch, and install the new patch, 4.3.0-20211104.
### [](#patch-4-3-0-20211104)Patch 4.3.0-20211104 Patch release version: 4.3.0-20211104 This November update addresses a regression introduced in the previous November patch, 4.3.0-20211026:
Description Issue

QueryParams are no longer lost when HTTP redirects take place.

MULE-19811

Addressed a regression in the initial November patch update.

SE-23349
### [](#patch-4-3-0-20211026)Patch 4.3.0-20211026 Patch release version: 4.3.0-20211026

Skip this patch, and install a later patch. Fixes in this patch are included in later patches.
This November patch update addresses the following issues:
Description Issue

The CachedConnectionProvider no longer returns the same connection to a source if sourceCallback.onConnectionException(e) is called.

MULE-19678/SE-21176

Fixed NullPointerException handling when serializing or transforming Mule errors from the Until Successful component.

MULE-19811/SE-20502

Fixed a ClassCastException that occurred in the Avro module by correcting its generated MIME type.

SE-21869

An issue with nesting referenced Flow Reference components no longer occurs.

MULE-19831/SE-22539

Fixed a memory leak in org.mule.runtime.core.internal.rx.FluxSinkRecorder.

MULE-19846/SE-22780

Applications now start correctly after the September patch update is applied.

MULE-19815/SE-22845

Caffeine cache now correctly processes large payloads with a VM queue.

MULE-19869/SE-22773

The Scheduler component no longer causes intermittent deployment failures.

MULE-19774/SE-22851

Mule now handles concurrent requests correctly when a Mule application makes an HTTP request that returns a 301 redirect.

SE-22922/SE-19944
DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The November patch release addresses the following DataWeave issues:
Description Issue

Fixed a ClassCastException that occurred in the Avro module by correcting its generated MIME type.

SE-21869
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2021)October 2021 Patch release version: 4.3.0-20210915 To include updated patching instructions, the patch update for the standalone version of Mule was republished as `mule-ee-patch-4.3.0-20210915-HF1-OCTOBER.zip` in your customer portal. The October patch update addresses the following issues:
Description Issue

Metadata now resolves correctly for components with multi-level keys.

MULE-19740/SE-22356

When using the #[flow.name] value in a Set Variable component, Mule now correctly recognizes flow.name.

MULE-19732/SE-20384

Applications now continue correctly when a dynamic flow reference resolves to non-existent flow.

MULE-19742/SE-20838

Mule runtime engine no longer stops accepting requests after a No listener error occurs.

MULE-19533/SE-20958/SE-21576

Applications that include the Dynamic Evaluate component in a sub-flow now deploy correctly.

EE-8018/SE-21777

Introduced a new mechanism for collecting API gateway usage statistics, which defaults to enabled.

To opt out, include anypoint.platform.metrics_enabled=false in wrapper.conf or as a parameter when starting Mule.

AGW-4823
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2021)September 2021 Patch release version: 4.3.0-20210823 The September patch update adddresses the following issues:
Issue Description

MULE-19707/SE-22200

Fixed an issue that caused some applications and connectors to become unresponsive due to a NullPointerException error.

MULE-19620/SE-21555

Applications now properly release resources allocated by the IBM MQ connector when the application stops.

MULE-19699/SE-21576

Fixed a race condition occuring during parallel deployments that caused deployments to fail.

MULE-19684/SE-22043

Fixed a default error handling issue in the error handler.

MULE-19680/SE-22129

Mule now masks sensitive data and secure properties (e.g. master password) in logs and UI.

MULE-19498

SDK: The @Export annotation now works with the Enum type.

MULE-19624/SE-21593

Restarting an on-premises Mule application with flows with initialState=stopped no longer leaks memory.

SE-21685/EE-7995

Fixed error conditions and messages for MUnit tests.

MULE-19562 /SE-21626

Fixed NullPointerException errors on nested VM Transactions.

MULE-19691/SE-21658

Closing the connection now works correctly if a timeout occurs when an empty payload is sent.

MULE-19622/SE-19944

When handling redirect responses, Mule no longer becomes unresponsive.

SE-21417

DataWeave Flatfile: Added the reader and writer property useMissCharAsDefaultForFill for the flat file format. When this property is set to true, DataWeave uses the fill character configured in the missingValues property to trim or pad elements. If useMissCharAsDefaultForFill is set to false, DataWeave uses the space character.

SE-22171

DataWeave: The distinctBy function now works as expected when used with mapObject or filter.

SE-21050

DataWeave: Fixed an issue that showed an internal exception instead of the expected InvalidUrlEncodingException error message.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2021)August 2021 Patch release version: 4.3.0-20210719 The August patch update adddresses the following issues:
Issue Description

MULE-19586/SE-21826

Introduces a mule.setVariable.WithNullValue=true property for the Set Variable component, which enables you to create a Mule variable with a null value. In Mule 4.4, this behavior will be the default.

MULE-19485/SE-21019

Incorrect status codes and error descriptions no longer occur when using policies.

EE-7907/SE-20588

Improves the handling of XA transactions when using Anypoint Connector for IBM MQ by fixing the error bitronix.tm.internal.BitronixSystemException - cannot delist an XAResourceHolderState.

EE-7890/SE-20153

Errors from a Batch Aggregator scope are now available within the Batch Step that handles errors.

SE-21198

DataWeave: Introduces a reader property (defaultContentType) and a system property (com.mulesoft.dw.multipart.defaultContentType) to change the default Content-Type for multipart parts.

SE-21632

DataWeave: Temporary files created during the Excel streaming process are now deleted.

SE-21585

DataWeave: Addresses the presence of big objects that are pending finalization.

SE-21873

DataWeave FlatFile: Fixes end-of-input data detection when Copybook structures have multiple segments with repeated composite and element components.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2021)July 2021 Patch release version: 4.3.0-20210622 The July patch update adddresses the following issues:
Issue Description

MULE-19226/SE-16379

When deploying policies that use extensions (such as connectors) that are also used in the target application, NoSuchBeanDefinitionException errors are no longer thrown.

MULE-19512/SE-20259

The Anypoint Studio 7.8 debugger no longer stops working unexpectedly when an error occurs in the flow execution.

MULE-19471/SE-20711

The Propagating completion default log level changed from WARN to DEBUG.

MULE-19431

If they are in the same scope or in a nested scope, you can now properly chain transaction interceptors that have different transactionalAction values.

MULE-19290

The initialization policy for pooling profiles now honors the selected option, and no longer initializes to none in all cases.

MULE-19430/SE-20576

Two or more nested XA (Extended Architecture) transactions no longer fail with NullPointerException errors.

MULE-19443/SE-20938

The Set Variable component now creates a variable when the value is null.

SE-20940

The contracts database for API Gateway now self-recovers after experiencing a Wrong index checksum or other errors.

MULE-19418/SE-20254

When the Anypoint Connector for AMQP (AMQP Connector) experiences connectivity errors, transactions are now rolled back, as expected.

SE-19983

DataWeave has improved error reporting for recursive imports.

SE-21133

DataWeave 0x025(LF) byte conversion for IBM037 encoding now works as expected.

SE-20880

DataWeave flat files now contain the property notTruncateDependingOnSubjectNotPresent to avoid truncating the group-item when the subject is not present or the length of the subject of an OCCURS clause is zero. Earlier versions contained this property.

SE-20878

DataWeave no longer raises Negative Index Exception errors when processing JSON files over 10 GB.

MULE-19442

Input stream parameters on a Parameter Group with showInDsl=true now resets after refreshing an expired OAuth token.

MULE-19426/SE-20477

Anypoint MQ connectors are now available in flows after non-transactional MQ publish operations to preserve backwards compatible behavior with Mule 4.2.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2021)June 2021 The following notification applies to each patch release in June.

The default for the DataWeave XML reader property supportDtd changes to false in this release. The new default is described in fixed issue DW-377.

This change affects Mule versions 4.3.0 for on-premises Mule, CloudHub, and other hosted or embedded runtimes, including Anypoint Runtime Fabric and Anypoint Studio. Future patches to these releases and future minor releases of Mule will also incorporate the new default.
The June update 4.3.0-20210609 addresses the following issues:
Issue Description

SE-20497

DataWeave: A StackOverflow error no longer occurs when concatenating arrays.

SE-20846

DataWeave: Applications that use multiple ++ operators no longer fail to deploy.
The June update 4.3.0-20210601 addresses the following issues:
Issue Description

MULE-19282/SE-17938

Deployments now take into account Maven profiles defined in the pom.xml file, preventing errors due to dependencies not loaded correctly, such as Cannot load class oracle.jdbc.driver.OracleDriver.

MULE-19328/SE-19407

EVENTS_ACCUMULATED error no longer occur after an application restart that caused app’s schedulers to stop working.

MULE-19319

A For Each scope that points to a Flow Reference component using max-concurrency no longer gets stuckt.

MULE-19315/SE-19762

The connector Reconnection Strategy is now correctly honored when running in debugging mode.

MULE-19220/SE-19580

Logging context entries are now propagated correctly to asynchronous SDK operations.

MULE-19297/SE-19166

Streams are no longer closed when consumed inside of a scope.

MULE-19279/SE-15347

Binary payloads are no longer corrupted when using VM queues.

MULE-19289

Logging now includes the original exception when managing reconnection scenarios.

MULE-19291/SE-20299

The timestamp reported by XA Bitronix Transaction is now output correctly.

MULE-19406

The system property name mule..enableStreamingStatistics was corrected to mule.enableStreamingStatistics.

MULE-19342/SE-20247

Scheduler jobs no longer get stuck due to a race condition.

SE-20356

Connection pool now behaves as expected when using a reconnection strategy or using #[] expressions in the connector config element.

MULE-19356/SE-20465

Mule runtime engine no longer shuts down with a NullPointerException error when encountering flows without sources.

MULE-19390/SE-20448

Using a @ParameterGroup annotation with an @ExclusiveOptionals annotation that references another parameter with the same name outside the group no longer causes the deployment to fail with the error the following parameters cannot be set at the same time.

MULE-19408/SE-20491

Error propagation with certain error types when using Mule runtime cluster now works correctly.

MULE-19409

The logs now include JAR files added to the class loader to facilitate troubleshooting server-plugin class loader creation.

MULE-19371/MULE-19370/SE-20386

TieredCompilation no longer prevents apps from working on 0.1 vCore when deployed on a worker with a higher vCore, such as 0.2 vCore.

MULE-19387/SE-20319

Using the Java Module in a policy no longer prevents the policy from deploying successfully.

MULE-19240/SE-20745

Deploying a custom policy on Windows no longer fails if the log file name contains : characters.

MULE-18580

Setting a Date with Time and TimeZone precision from a String value now works correctly without requiring a DataWeave expression. In addition, setting time-based parameters following the ISO-8601 standard is now supported.

MULE-19347/SE-19450

Anypoint Connector for JMS (Java Message Service) using XA Transactions with Bitronix now honors the reconnection strategy.

MULE-19010

Using the Scatter-Gather component with the Flow Reference component no longer causes MULE:UNKNOWN errors.

SE-20417

The logs now include only one Back Pressure error per exception.

SE-20952

Corrected information in the mule-ee-patch-4.3.0-20210427-MAY-2021.zip README.TXT file.

EE-6454

The Transform Message component now loads resources using the correct encoding.

EE-7739/SE-19692

Undeploying applications in a cluster with FIPS enabled no longer causes the process to hang.

EE-7524

The Cache Scope component no longer creates incompatible cache values during Mule runtime engine upgrades.

EE-7284

Clusters configured to use encrypted communication now work as expected.

AGW-4731

Closed sockets are now recovered correctly when an unexpected platform connection error occurs.

AGW-4747/SE-19546

The client secret of client credentials can now be hashed when storing the credentials in memory and when parsing incoming credentials from a request.

This functionality is disabled by default.

AGW-4797

Removed unused Jersey dependencies.

DW-377

DataWeave: Support for XML DTD validation is now disabled by default.

To enable XML DTD validation, use the com.mulesoft.dw.xml.supportDTD system property or the supportDtd XML reader property.

SE-19933

Schedule-based flows no longer stall after the first batch is processed when the value of maxConcurrency is 1.

SE-20129

DataWeave: The character reader property now correctly handles null as an empty value.

SE-20300

DataWeave: An OutOfMemory error no longer occurs when using MultiPart format.

SE-20372

DataWeave: A StackOverflow error no longer occurs when using StreamCapable check-recursive functions.

SE-16906

Event variables that are visible in a Try scope are now visible inside error handlers.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2021)April 2021 Patch release version: 4.3.0-20210322

For an upcoming release in May, the behavior of the DataWeave XML reader functionality will change.

This change will affect Mule versions 3.9.5, 4.1.6, 4.2.2, and 4.3.0 for on-premises Mule, CloudHub, and other hosted or embedded runtimes, including Anypoint Runtime Fabric and Anypoint Studio.
The April patch update adddresses the following issues:
Issue Description

SE-20108

Fixed a known issue that could cause a com.esotericsoftware.kryo.KryoException: Buffer underflow error to occur in CloudHub when using Object Store v2 after updating to the March 2021 release.

MULE-19272/SE-18122

Fixed the error Couldn’t find resource: script.dwl neither on classpath or in file system, which occurred when using the Transform Message component (ee:transform) in a subflow called from Parallel For Each (parallel-foreach), Scatter-Gather (scatter-gather), or Cache ee:cache components.

MULE-19262

Fixed an issue that occurred when retrying an operation after refreshing an OAuth token. Consumable values (such as streams) of parameters in the operation were already consumed and not reset upon retrying the operation.

MULE-19252

Improved the performance of persistent object stores.

MULE-19249/SE-19746

Fixed an issue that caused errors when referencing files on a network share path in a Windows environment.

MULE-19076

Fixed the log message for org.mule.runtime.core.internal.processor.simple.RemoveFlowVariableProcessor.

EE-7703/SE-16631/SE-17432

Fixed an issue that occurred when using XA transactions in the Anypoint Connector for Database (Database Connector).

The application did not resolve metadata correctly and failed when testing with MUnit.

MULE-19242/SE-18799

Fixed a file leak on Windows that prevented Mule from deleting the application’s folder when redeploying, which caused a failure.

SE-19846

DataWeave: To fix an OutOfMemory error that occurred when mapping many database records, DataWeave now releases resources on stream close.

SE-19257

DataWeave: Fixed flat file handling of records with values of variable length.

SE-20005

DataWeave: Increased the number of namespaces that can be handled by the XML module to avoid NoSuchElementException errors.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2021)March 2021 Patch release version: 4.3.0-20210304 Known Issues:
Issue Description

SE-20108

The Cache scope can fail when using a persistent Mule object store or Object Store v2 after upgrading to the March 2021 patch release for 4.3.0 from an older version.
The March patch update adddresses the following issues:
Issue Description

MULE-19127

Added the ability to redeploy a flow without starting it to enable the server to restart without starting the applications.

AGW-4551

Enhanced org.mule.runtime.api.healthcheck.ReadyStatus to provide more information.

AGW-4650

Fixed a problem in which removing a policy with contracts before the contracts were downloaded caused the gatekeeper to remain locked.

AGW-4619

Gatekeeper now waits for contracts to download.

DW-375

DataWeave: Prevented an overflow exception by getting a binary token offset.

SE-11046

Resolved an issue in which MUnit couldn’t run from behind an authenticated a Nexus repository.

SE-16673/EE-7664

Resolved a problem using Bitronix TM that caused the application to fail when the database was not reachable.

SE-19030/EE-7653

Fixed a problem that prevented XA MQ connections from committing if the flow used a cache element.

SE-18881/EE-7654

Fixed a validation issue that prevented setting preparedStatementCacheSize to 0.

SE-19090

DataWeave: Changed local imported modules to be cached to avoid CompilationResult class leaks.

SE-19157

DataWeave: Fixed an issue in which the splitter generated the wrong exception and caused Scala serialization issues.

SE-19266

DataWeave: Updated to use encoding when converting a string to a byte array.

SE-19442

DataWeave: Fixed an issue in which the pattern matcher didn’t work with comments, causing the script to fail.

MULE-19139

Fixed an issue in which mapped errors threw a MULE:UNKNOWN error, instead of the correct error name.

MULE-18663

When annotating parameters from OAuth-based connection providers with @OAuthParameter and requestAlias, the value of the parameter is now correctly sent when performing the OAuth dance.

MULE-19020

Fixed an issue in which connection errors were not computed in application error-count statistics.

MULE-19143

Fixed an issue that caused a NullPointerException error while using Parallel For Each combined with a For Each under high concurrency.

MULE-19160

Resolved a problem in which retrying policies for operations did not correctly override connection-provider policies.

MULE-19209/SE-19515

Fixed an issue in which a cache held a reference to a thread and a stream, which might cause high memory consumption.

MULE-19219

Fixed an issue in which MediaType did not correctly escape characters.

SE-16747

Resolved an issue that occurred when using the validation:all scope and a validation:is-not-null operation was triggered, the other items in the For Each weren’t processed.

SE-19213

Fixed a NullPointerException error that occurred while processing, under high concurrency, a Parallel For Each with either max-concurrency set to a value other than 1 or not set.

SE-19136

Resolved a problem in which the Add List operation in Anypoint Connector for NetSuite (NetSuite Connector) limited concurrent connections in the Batch Aggregator component.

SE-19515/MULE-19209

Fixed an issue that caused a memory leak when using a try block.

SE-19294

Resolved an issue in which the application received a rejected from Scheduler exception for HTTP request configurations when processing concurrent requests.

SE-19327

Fixed a SerializationException error that occurred when using the quote reader property (quote="\"") with a batch component.

SE-19557/MULE-19218

Resolved an issue that prevented opening a new cursor on a closed stream.

SE-19606

Fixed a problem in which database connections weren’t returned to the pool or were returned with a delay.

SE-19080/MULE-19157

Fixed an issue in which a connector with an operation that has a parameter group with exclusive optionals (one required) and one of the optional parameters is a POJO with dynamic fields caused the application deployment to fail. Affected connectors are the Cryptography module and Anypoint Connector for SAP (SAP Connector).
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2021)February 2021 Patch release version: 4.3.0-20210119 The February patch update adddresses the following issues:
Issue Description

MULE-19076

Added warning when the remove variable component tries to remove a non existing variable.

MULE-19038/SE-17832

Fixed a property {app.name} conflict when the application is deployed to CloudHub.

SE-18778

MUnit is unable to dynamic lookup flow references.

MULE-19122/SE-19029

Fixed an issue where different instances of a dynamic configuration containing an OAuth setup with Client Credentials could share the same token causing various errors (such as login fail or unauthorised access).

MULE-19129/SE-19069

Resolved a problem in which the CloudHub scheduler got stuck intermittently.

MULE-19118/SE-18583

Fixed an issue affecting the error handling of applications making use of the Try scope in subflows. This affected error propagation from subflows to their parent related flows.

MULE-18873

Resolved an issue in which routes dropped events during Flow Reference processing in applications that combined Scatter-Gather and Flow Reference components.

MULE-19113/SE-19102

Added logger to BackPressureStrategySelector for better debugging and tracing.

SE-18335

Fixed NullPointerException when using the HTTP Connector inside of a Connector built with XML SDK.

MULE-19097/SE-19126

Fixed issue that cuased CorrelationID to no be consistent throught the Event execution due to unwanted change in the used ClassLoader.

MULE-18159/SE-15096

Fixed an issue where plugins declared in domain could not load classes at application level.

MULE-19088/SE-18749

Fixed an issue that caused a Java.lang.NullPointerException error when trying to run MUnit tests on 4.3.0.

SE-17625

Fixed problem where the error handler component was called multiple times by Until Successful scope incorrectly.

MULE-19068/SE-18382

Fixed an issue that caused intermittent Cannot open a new cursor on a closed stream errors.

MULE-19049/SE-18521

Resolved incorrect behavior of the First Successful scope that occurred when the scope was within an Error Handler component.

MULE-18679

Fixed a ConcurrentModificationError on adding an startup listener while deploying an app.

EE-7624

Upgrade Tanuki wrapper to 3.5.45.

SE-18407

Fixed unexpected error The mapper returned a null value. within a Cache scope.

EE-7610/SE-18524

Fixed an issue that caused failures to deserialize file store based stream payload in batch.

AGW-4533

Fixed API reporting for requests with 0 size incoming requests (like GET requests).

DW-325

DataWeave: NDJson was not working when being executed in parallel.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-13423

DataWeave: Fixed an issue where FlatFile cannot write dw keys as values.

SE-14799

Fixed problem where the onErrorContinue cannot catch a mapped error thrown from a sub flow.

SE-17677

DataWeave: Added feature where the BinaryValue read buffer is now configurable with the property com.mulesoft.dw.buffersize.

SE-18882

DataWeave: Fixed the behavior of the substringBefore() and substringBeforeLast() functions which produced incorrect outputs.

SE-19000

DataWeave: Added a new reader property called tableLimit to control the boundaries of where to read data. Options are: HeaderSize, Unbounded, or the name of the column.

SE-19086

DataWeave: Fixed an issue where stream batching did not work in deferred mode.

SE-19094

DataWeave: Fixed an issue where using for each with batchsize caused the stream to close (StreamClose).

SE-19040

DataWeave: Fixed an issue that caused a NullPointerException when the message of the exception was null.

SE-16997/MULE-18675

Fixed an issue in which using dynamic configurations for paged or streaming operations caused a disconnection error when trying to consume the pages or the stream.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2021)January 2021 Patch release version: 4.3.0-20210105 The January patch update adddresses the following issues:
Issue Description

MULE-19014

Upgraded Bouncy Castle to version 1.67.

MULE-19026

Fixed incorrect reconnection behavior in sources, such as the Anypoint Connector for SFTP (SFTP Connector), which caused the sources to work incorrectly.

MULE-18599

Fixed an issue that produced an incorrect value for the partial fetching key resolution when a Parameter Group that is the MetadataKey used the setting showInDsl=true.

MULE-19016

Fixed an issue that could cause a "NullPointerError" when using the Post Message operation of Anypoint Connector for Slack (Slack Connector).

MULE-19006, SE-18378

Fixed an issue that produced a can’t get statistics before initialise() is invoked error when using a dynamic expiration configuration in a clustered environment.

MULE-19002, SE-17479

Fixed an issue in the XML SDK that ignored complex parameters defined as string arrays and with the behavior role.

MULE-18537

Mule now logs reconnection attempts when using the Standard Reconnection Strategy for any connector.

MULE-18929, SE-18107

Fixed an issue in which ActivePolicies set in DefaultPolicyManager retained multiple (weak) references to policies when expired policies renewed. The references were not collected. To avoid consuming more memory than necessary, the fix ensures that only one weak reference is retained per policy.

EE-7443, SE-16276

Fixed an issue in running Batch jobs that caused the jobs to get stuck and never finish.

SE-16965, AGW-4497

Fixed a metaspace classloader leak that occurred during the redeployment of an application.

SE-16372

Fixed an issue that prevented DataWeave from properly retrieving values when reading CSV files with Byte Order Mark (BOM) and Streaming enabled (streaming=true).

SE-18393

Fixed a DataWeave issue that resulted in a null value when using variables (vars) that were not resolved correctly.

SE-18136

Fixed a DataWeave issue that occurred when reading Excel files with empty columns, which caused rows to shift incorrectly to that empty space to fill in the empty column.

SE-18580

Fixed an issue that caused the Set Variable operation to fail with a MULE:EXPRESSION error when using a DataWeave expression that contained a function definition.

DW-289

Fixed an issue in which upserting an object with update duplicated key-value pairs in some cases.

DW-306

Fixed an issue that prevented the update operator from selecting attributes.

DW-307

Fixed an issue that prevented processing of XML documents when streaming mode was enabled.

MULE-18990

Added an optional warning with information about when an event is dropped.

MULE-19015

Fixed a Cannot open a new cursor on a closed stream error that occurred when using a nested foreach with a batch size larger than 1.

MULE-18949

Fixed a regression caused by a prior fix (MULE-18805) that made DataSense scenarios with error handling work improperly. With this fix, every scenario works properly, including the ones from MULE-18805.

SE-14750, MULE-19019

Fixed an issue that added a 'Content-length: 0' header for HTTP methods with undefined body semantics (GET, HEAD, and DELETE).

EE-7582

Fixed an HTTP service regression in which an unexpected error was thrown on a SoapFault.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2020)November 2020 Patch release version: 4.3.0-20201021 The November patch update adddresses the following issues:
Issue Description

Improved application network metric tracking.

SE-17806/MULE-18883

Fixed a CloudHub issue in which the Scheduler stopped but reported its status as Running.

SE-17445/MULE-18885

Fixed an issue in which the queue manager leaked queue configuration instances when using Anypoint Connector for Virtual Machine (VM Connector) in cluster deployment setups.

SE-16989/MULE-18805

Fixed an issue in which MUnit did not successfully execute due to improper functioning (caused by lazy loading logic) when using an On-Error component.

SE-17092/MULE-18777

Resolved a problem with Anypoint Connector for AMQP (AMQP Connector) that caused the channel count to increase incorrectly after force-closing connections.

SE-16853/MULE-18889

Resolved an execution problem that occurred when an application used Groovy with Scripting module version 2.0.0.

MULE-18884

Resolved a memory leak that caused Mule runtime engine to crash after multiple redeployments of an app.

SE-15000/MULE-18794

Fixed an issue in which DataSense was unable to find the WSDL file for APIkit for SOAP Project.

SE-16933/MULE-18698

Fixed a regression in which dynamic configurations were not properly disposed, which caused out of memory errors.

SE-17756/MULE-18803

Fixed an error that could cause a flow to stop when combining the Scatter-Gather component or Parallel For Each scope with the Choice or Round Robin routers.

SE-16596/DW-240

Fixed an issue in the DataWeave flat file component in which some null values were not transformed to zeroes in hexadecimal.

SE-17773

Added a new system property com.mulesoft.dw.valueSelector.selectsAlwaysFirst to avoid caching selected indexes in DataWeave.

SE-17873

Fixed the following DataWeave error that occurred while converting Instant to LocalDateTime with MIN and MAX:

An exception occurred while trying to access field function java.time.Instant.MIN. Caused by: java.time.DateTimeException: Invalid value for Year

FV-833

Fixed an issue in which joinBy failed to validate against signatures in DataWeave. //correct issue number?

SE-9907

Fixed an issue with DataWeave in which java.util.Timezone provided a ZoneInfo Java class, rather than the time zone ID, such as "America/Los Angeles".

SE-14220

Fixed a NullPointerException error that occurred when using the Flat File format in DataWeave.

SE-15970

Resolved an issue with the DataWeave diff function, which inverted the values of the expected and actual keys.

SE-16350

Fixed a DataWeave issue in which using header=false with bodyStartLineNumber, the CSV reader skipped lines.

SE-16883

Fixed an issue with the DataWeave Mule::causedBy function, which didn’t have the correct type defined for Error.

SE-17149

Resolved an issue in DataWeave conversion from Excel to CSV format, which did not print cells when the cell value was empty, resulting in an inconsistent output.

SE-17212

Resolved a problem in which defining a Client ID Enforcement policy failed with encrypted client credentials.

SE-17392

Fixed an issue in which DataWeave didn’t correctly handle an internal UnsupportedTypeCoercionException error while processing a batch of records.

SE-17446

Resolved an issue in DataWeave in which conversion from Excel to DataWeave didn’t correctly ignore empty lines in Excel.

SE-17520

Fixed a problem in which DataWeave didn’t correctly process keys that use a literal $ string value.

SE-17562

Fixed a problem in which a migrated MUnit test from a previous Mule version executed a mocked connector.

SE-17570

Resolved a DataWeave issue that caused a StackOverflow error when using some and every functions with large arrays.

SE-13715/MULE-18812

Fixed an issue that occurred after Mule runtime engine restarted, which caused Mule application deployment failures while parsing domain shared resources.

SE-12712/MULE-17880

Fixed multiple WARN log entries that occurred when using a caching strategy.

SE-15592/MULE-18573

Fixed an issue that occurred when an app transformed data using variables.

MULE-18872

Fixed an issue with the runtime logging that could cause out of memory issues.

SE-16439/MULE-18696

Resolved a problem that occurred when processing a large batch of records within a Parallel For Each scope, causing an exception and an unresponsive application.

SE-16823/MULE-18712

Resolved a problem in which it was not possible to mock scripting:execute processors when running MUnit tests.

SE-17554/MULE-18739

Fixed the default value resolution for the Scheduler component’s disallowConcurrentExecution attribute so that you don’t need to define it explicitly.

MULE-18742

Fixed a race condition that produced a ConcurrentModificationException error in Log4jContextFactory when canceling a registered callback while disposing an application.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2020)September 2020 Patch release version: 4.3.0-20200824 The September patch update adddresses the following issues:
Issue Description

MULE-18694/SE-16719

Resolved an issue that caused applications to fail due to memory consumption when referencing nested subflows (using <flow-ref>).

MULE-18666

Fixed an issue that caused a StackOverflowException error when using the following DataWeave script:

#[output application/json --- message]

MULE-18689/SE-16734

Corrected a memory leak referencing the following class in the runtime logs:

org.mule.runtime.core.privileged.exception.
TemplateOnErrorHandler$
OnErrorHandlerFluxObjectFactorytransactional

MULE-18682

Fixed a problem that caused a ClassNotFoundException after a policy upgrade affecting proxy applications.

MULE-18657/SE-14959

Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector).

MULE-18665/SE-16278

Fixed the RegistryLifecycleCallback logger so that it no longer prints the customer’s security key.

MULE-18542/SE-15818

Resolved a thread leak when redeploying an application that uses Anypoint Connector for Database (Database Connector) and references the Oracle JDBC driver.

MULE-18628/SE-16435

Resolved a problem in which applications were unable to retrieve objects from the cache due to serialization issues.

MULE-18623/SE-16933

Corrected a memory leak that occurred when using dynamic configurations.

SE-15453

DataWeave’s XML module now includes a new property to handle escaping > characters.

SE-15249

Fixed DataWeave attribute selector not dispatching to the correct implementation.

SE-15362

Fixed NullPointerException in DataWeave’s XML module.

DW-184/SE-15834

Fixed DataWeave inferred types when the output is undefined storage to recalculate output.

SE-15894

JSON binary values are now encoded into strings consistently across DataWeave versions.

SE-16462

DataWeave now parses single key-value pairs correctly when mixed with conditionals.

SE-16539

Fixed an error that occurred in DataWeave when parsing JSON with whitespace between array elements.

SE-16167

The DataWeave Avro module now correctly converts logical types.

AGW-4287/SE-16981

Fixed an issue that caused object-store deserialization errors when upgrading the internal version of Rate Limiting policy.

SE-17193

Fix a deployment issue that occurred for apps with multiple nested function calls, such as ++, in DataWeave.

SE-17270

Fixed an issue in which the primary node in a cluster remained primary after stopping the runtime, causing applications with a pooling processor on the primary node to stop working.

MULE-18604/SE-12900

Fixed an issue in which NTLM authentication-dancing failed when performing multiple parallel requests requiring renegotiation.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2020)August 2020 Patch release version: 4.3.0-20200727 The August patch update adddresses the following issues:
Issue Description

MULE-18535, SE-16524

Fixed incorrect behavior in which accessing message.message.exceptionPayload.info.Element returned null instead of an error.

MULE-18528

SDK OAuth authorization code-flow references do not have a stereotype making it fail when executed from MUnit.

MULE-18579

Resolved an issue in which when an object store expired, it loaded all deserialized entries into memory, doubling memory consumption.

MULE-18564

Fixed an issue in which using inline proxy configuration in the OAuth module failed to create the requestConfig configuration.

MULE-18569, SE-16282

Resolved an issue in which the Anypoint Connector for Kafka returned the java.nio.file.InvalidPathException: Illegal char <:> exception when accessing filesystem configuration files.

MULE-18548, SE-14272

Fixed an issue in which the Cache scope in a cluster configuration did not effectively monitor the cache in the secondary node.

MULE-18545

Resolved an IndexOutOfBoundsException error that occurred when handling a backpressure error in a source policy.

MULE-16688

Fixed a problem that occurred when using a property placeholder on an import tag with deploymentProperties that caused the placeholders to not be replaced.

MULE-18513

Fixed an issue in which a connector configuration using OAuth caused metadata-resolution problems.

MULE-18504

Resolved an SDK regression in which the component reference in an operation chain was wrongly calculated.

EE-7381

Fixed an issue in which creating a scheduledThreadPool with a coreSize value of 0 could cause high CPU utilization.

SE-16468

Fixed an issue in which DataWeave skipNullOn did not behave properly because the value null was ignored in maps.

SE-16915

Removed unnecessary log messages that appeared when using dynamic objects in DataWeave.

MULE-18196, SE-16894

The fix for the SE-15056 issue causes applications that use custom policies to fail when sharing the ErrorType repository if the app and policy bundle didn’t include all dependencies.

+ You can revert the behavior by setting the mule.share.errorTypeRepository system property to true.

SE-13603

Fixed an issue in which an application using more than one salesforce:replay-channel operation failed with status code 429.

SE-13603, SE-10677, SE-16728

Upgraded the Object Store v2 plugin to version 4.0.27.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2020)July 2020 Patch release version: 4.3.0-20200622 The July patch update adddresses the following issues:
Issue Description

AGW-4211, SE-16370

Fixed an issue in which applications using APIkit and policies with the autodiscovery component incorrectly returned 500 instead of 404.

MULE-18454

Resolved a problem generating XML when creating an artifact declaration that contains a platform-managed OAuth connection provider.

MULE-18475, SE-16232

Fixed a NullPointerException issue on the XML SDK framework when a parameter that has both CONTENT and OPTIONAL values is empty.

MULE-18491, SE-16370

Errors without location values no longer cause policy error handling to behave like a back-pressure error.

MULE-18506, SE-16470

Reverted MULE-18370 because it caused a key collision in the ManagedCursorProvider cache management.

SE-13383

Fixed an issue that occurred while moving corrupted domain object store files to the Garbage folder.

SE-15067

DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger.

MULE-18375, SE-15704

Fixed a problem in which a custom policy that applied an outbound request changed the behavior of an API by clearing attributes.

SE-15918

Added support for escaped Char sequences on DataWeave settings.

MULE-18458, SE-15925

Fixed a problem that occurred when resolving DataWeave errors and processing the flow stack.

MULE-18439, SE-15995

Fixed an application deployment failure with the loops not allowed error.

SE-16006

Fixed an issue that prevented debugging an application in Studio 7.5 and Mule runtime engine 4.3.

MULE-18462, SE-16038

Resolved an issue in which combining Cache and For Each scopes caused a java.lang.ArrayIndexOutOfBoundsException: 0 error during execution.

MULE-18501, MULE-18500, SE-16088

Fixed a regression with MUnit spy assertions (before-call and after-call) that was introduced in Mule 4.3.0.

MULE-18498, MULE-18480, SE-16095

Fixed an OutOfMemoryError: Metaspace error on applications with multiple concurrent deployments and some redeployments.

MULE-18453, SE-16119

Fixed an issue with backslash-character processing when running Studio on Windows, which caused Test Connection in Anypoint Connector for File to fail when the Configuration property was present.

MULE-18488, SE-16133

Fixed a NullPointerException error that occurred when using Anypoint Connector for Database in a Try scope and running it more than once.

MULE-18489, SE-16281

Resolved the ClassCastException: java.lang.Integer cannot be cast to java.lang.Long error when using Anypoint Connector for Kafka.

SE-16292

Fixed a JSON payload with spaces after an array value failed in DataWeave’s in-memory parser.

MULE-18490, SE-16317

Resolved a problem accessing flow.name in DataWeave transformations.

MULE-18492, SE-16365

Fixed a serialization problem with policies using the 'Rate limit SLA' policy.

SE-16379

Fixed an application start-up error NoSuchBeanDefinitionException: No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available.

SE-16381

Resolved a problem processing DataWeave date expressions when calculating year differences.

SE-16389

Fixed an issue in which DataWeave nested dynamic objects skipped elements.

SE-16431

Cached DataWeave compiled expressions based on string script to avoid an out-of-memory issue on deployment.

MDM-106, SE-16066

Fixed metadata that was not generated correctly when a <ROW> tag was duplicated.

MULE-18431

Corrected problems in which threads hung when using Anypoint Connector for Virtual Machine under load.

MULE-18294

Resolved an issue in which polling source Scheduler components incorrectly restarted on reconnection.

MULE-18440

Fixed a race condition that occurred when a thread looked for policies and invalidated the cache simultaneously.

MULE-18442

Mule no longer creates a default policy manager for each applied policy.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2020)June 2020 Patch release version: 4.3.0-20200521 This patch release consolidates fixes to Mule 4.3.0 since the initial release on April 30, 2020. The fixes extend through June 2020.
Issue Description

AGW-4199

Fixed an error that occurred when accessing Gatekeeper and Analytics policy templates.

SE-15935

Mule application threw the wrong HTTP response status code when api-gateway:autodiscovery was enabled.

MULE-18421

When using a logger to log a value, a result containing ##[ is no longer incorrectly reevaluated.

MULE-18416

Resolved ClassCastException when running an API using the Interception API.

MULE-18397

Fixed an error that occurred when an expression accessed a target-operation payload attribute.

MULE-18390

Fixed an OutOfMemory error that mentioned running out of Metaspace when running MUnit tests.

MULE-18378

When an HTTP Listener is source of the flow, trying to reference a flow variable from the flow’s error response builder, the variable could not be found if a source policy was applied to the Listener.

MULE-18371

Fixed a NullPointerException error that occurred when processing a request and all in-flight cursors were inappropriately closed.

MULE-18370

Fixed an issue that might rarely cause a key collision with the ManagedCursorProvider cache.

MULE-18369

MULE:OVERLOAD exception is thrown when first policy contains a Cache scope and second policy contains a Try scope error-handler.

MULE-18364

Fixed a problem that prevented an application from starting after stopping using Runtime Manager.

MULE-18312

A custom global error handler is no longer ignored when located after a failing flow.

MULE-18306

Fixed a race condition that occurred while disposing flows using a until-successful construct.

MULE-18284

Fixed an issue where a policy deployment failed under certain circumstances because the errorType could not be found when deploying a policy.

MULE-18264

Resolved open JAR file-leak when reading resources, such as keystore, when configuring TLS.

MULE-18255

OCSClient now supports configuring the API version of the service via system property.

MULE-18244

Fixed a classloading issue when connectors that use third-party libraries are not able to load classes if they rely on loadClass(s,b) from CompositeClassLoader.

MULE-18208

When resolving dependencies, a mule-service no longer includes the Test scope dependencies, which caused unnecessary service registrations.

MULE-18196

An application no longer fails to deploy if it has the same custom namespace as that of an applied custom policy.

MULE-18179

Resolved a possible stack overflow on RejectionCallbackExecutorServiceDecorator while trying to generate an XML response.

MULE-18102

Resolved concurrent subflow instantiation problem where the inner processors location was being corrupted.

MULE-16668

Optimized connection-pool validations to avoid excessive and costly checks.

EE-7097

Batch job summary is no longer incorrectly logged twice.

MULE-18310

Optimized application deployments, resulting in performance improvements.

MULE-18205

Optimized FlowProcessMediator#policySuccessError to now create a single router for all exceptions rather than one for each exception or error.

MULE-18172

Fixed ObjectStoreToMapAdapter thrown exceptions when used or accessed concurrently.

MULE-18202

Upgraded groovy dependency to version 3.0.2.

SE-15904

Fixed an issue in which DataWeave’s common subexpression elimination incorrectly reduced two expressions, ignoring middle nodes.

SE-13691

Fixed an issue in which the Scheduler incorrectly ran twice.

MULE-18369

Fixed an overload error that occurred when an API had a combination of two policies using caching and error-handler components.
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-30-2020)April 30, 2020 The initial 4.3.0 release includes new features, fixes, and some known limitations. ### [](#new-features-and-enhancements)New Features and Enhancements Mule 4.3.0 introduces several features and enhancements. #### [](#api_gateway)API Gateway API Gateway now includes a `disable Policies` annotation. Setting it to `true` enables you to block the application of policies to the requestor. In addition, the release introduces several enhancements to resiliency, including a better backoff mechanism and improvements of the policy deployer mechanism. #### [](#dataweave)DataWeave DataWeave introduces the following: - `update` operator: Creating modified versions of objects and arrays is now easier. The `update` operator enables you to select specific fields to change without changing others. - Streaming features and enhancements: - The XML reader now supports streaming. - The JSON reader now supports streaming for more than arrays. - Literal types: `String`, `Boolean`, and `Number` values can now be handled as literal types, which enables the definition of enumerations (Enums) and makes function overloading more dynamic. - `Period` and `DateTime` consistency: This feature adds an easy way to operate with periods, transform the result into different units, and decompose the period into its different parts. `Period` changes its behavior for dates in version 2.3.0. To restore the 2.2.0 behavior, set the `-M-Dcom.mulesoft.dw.date_minus_back_compatibility=true`. See [Add and Subtract Time](https://docs.mulesoft.com/jp/dataweave/2.3/dataweave-cookbook-add-and-subtract-time) for additional details. - DataWeave modules: - The new Types module enables type introspection at runtime. - DataWeave also introduces a number of new functions in existing modules. - Deprecated functions and replacements: The `entrySet`, `keySet`, `nameSet`, `valueSet` functions in the Objects module are deprecated in this release and replaced with the functions `entriesOf`, `keysOf`, `namesOf`, `valuesOf` in the Core module. - `withMaxSize` function: The Strings module has a new function that enables you to specify a maximum size for a given value. A value that exceeds the size limit will be truncated. If the size is no greater than the limit, the value remains the same. - `takeWhile` function: The Objects module has a new function that iterates over the items in an array items while a condition is true. - `dropWhile` function: The Objects module has a new function that iterates over and ignores the items in an array until the specified condition is true. - Reader and Writer properties: DataWeave introduces a number of new and enhanced reader and writer properties for supported DataWeave formats. - Custom MIME types: This feature adds a way to define the output MIME type separately from the output data format. It also provides a simpler way of defining output and input formats. - Intersection type: DataWeave introduces the `Intersection` type. The intersection type appends `Object` types. The type takes the form `TypeA & TypeB & …​`. - Performance: DataWeave performance is improved for memory usage, functions (like `groupBy`), and the internal execution engine. Improvements include: - Common Subexp Elimination To optimize scripts, DataWeave now eliminates common subexpressions by internally using implicit variables for them, meaning the subexpressions are only executed once regardless of how many times they are repeated. - Memory Service: Memory management is now centralized. Several memory management strategies are included, such as pooling direct memory or using heap memory exclusively. - Improvements to parsing error messages: Parsing errors now reflect more accurately missing tokens, incomplete definitions, and other common issues. Tips and examples of how to solve the issues are also included. For more detailed information about these changes, see [What’s New in Mule 4.3](https://docs.mulesoft.com/jp/mule-runtime/4.3/whats-new-in-mule#dataweave). #### [](#core-components)Core Components The following Core components have new features in this release. - Until Successful component: Max Retries (`maxRetries`) and Milliseconds Between Retries (`millisBetweenRetries`) now support a number or an expression that resolves to a number. - Batch Aggregator component: This component adds the `preserveMimeTypes` attribute to makes it easier to handle records from a payload that is in a structured text format, such as JSON or XML. For more detailed information about these changes, see [What’s New in Mule 4.3](https://docs.mulesoft.com/jp/mule-runtime/4.3/whats-new-in-mule#core_components). ### [](#changes)Changes - Threading Model - The three main thread pools have been combined into one unique thread pool. - You can select between the UBER pool strategy (default) or the DEDICATED pools strategy (legacy). - You can still customize the thread pools' configuration if necessary. - If you are upgrading from earlier Mule 4.x versions, see [Upgrading from Mule 4.2/4.1](https://docs.mulesoft.com/jp/mule-runtime/4.3/execution-engine#upgrading-from-4-x) For more detailed information about this change, see [What’s New in Mule 4.3](https://docs.mulesoft.com/jp/mule-runtime/4.3/whats-new-in-mule#threading_model). - Performance updates Mule 4.3.0 includes several updates to improve performance. Some processes are pre-calculated to reduce latency and increase throughput. However, these modifications cause a slight increase in memory consumption for Mule components. The increase is particularly important when using subflows because the content of a subflow replaces each Flow Reference component that references the subflow, causing several instances of the event processors inside a subflow to exist in the application at runtime. See [Using Subflows](https://docs.mulesoft.com/jp/mule-runtime/4.3/about-flows#using-subflows) for additional details about subflow behavior. For more detailed information about optimizing application performance, see [Performance Tuning Guide](https://docs.mulesoft.com/jp/mule-runtime/4.3/tuning-guide). ### [](#upgrade-requirements)Upgrade Requirements
Issue Description

MULE-16681

Updated cipher suites for FIPS140-2 mode (check tls-fips140-2.conf file)

MULE-15596

Added support to Error Handler for "when" filtering for a certain "type". Before 4.3.0 Setting "when" and "type" simple ignores "when" expression

MULE-17800

ParseTemplateProcessor Type Inconsistencies when setting target and target variable

MULE-17472

Use of backslash before Properties escapes the evaluation of them. To have the same behavior as before (backslash being a simple character) add the system property mule.properties.correct.backslash.use=false
### [](#known-limitations-and-workarounds)Known Limitations and Workarounds
Issue Description

MULE-18369

API fails when it applies the Caching Policy before the Message Logging Policy or Header Injection Policy.
### [](#fixed-issues)Fixed Issues
Issue Description

MULE-18305

XmlSdkConfigurationInstance does not delegate methods

MULE-18304

NPE in operations within dynamically invoked sub-flow

MULE-18299

Unexpected run/debug behavior - Flow was terminated abnormally

MULE-18295

Performance overhead in SdkInternalContext#locationSpecificContext

MULE-18286

Error mappings not honored while running application on LazyInit

MULE-18281

ArtifactAstDependencyGraph is not taking configRef parameters into account

MULE-18276

IllegalStateException cannot be cast to EventProcessingException

MULE-18269

XML SDK variables are sent as null with 4.3.0-RC2

MULE-18261

Processed wrapped in a Mono should always recognize itself with a child context

MULE-18259

Smart connector fails if http protocol is not defined for a config that contains another http config

MULE-18248

Illegal type name exception in AIX OS using JDK8

MULE-18240

Scatter Gather resulting in Exception reached PS subscriber for flow

MULE-18238

XmlSdkConfigurationProvider does not propagate Lifecycle methods

MULE-18236

Getting IndexOutOfBoundsException error for a mapping that works in 4.2.2

MULE-18234

App returns correct results, but "Test Connection" FAILS

MULE-18227

NPE with scatter-gather within parallel-foreach

MULE-18200

4.3.0: readUrl getting blocked when file resource is not present

MULE-18197

MUnit test fails when executing XML SDK module

MULE-18189

Interception API: Context Id are swapped for processors in scatter-gather

MULE-18183

Race condition on ProcessingStrategy#dispose

MULE-18178

Max Concurrency not honored in flow-ref

MULE-18177

Add current location to thread names

MULE-18164

Async scope not deploying in a policy

MULE-18161

Simple async operation not working

MULE-18157

Event modifications lost when setting a securityContext

MULE-18155

Dynamic flow-ref must explicitly expect a String on the expressionLanguage

MULE-18148

Memory leak on transactional try with error handlers

MULE-18145

Operation policies are not applied to requester when it is inside XML Connector

MULE-18140

PlatformManaged connection providers do not inject the config name to its delegate

MULE-18138

Every time a connection is created/autowired, its class is looked up in the app classloader

MULE-18129

Extensions-client times out operations after 5 seconds

MULE-18124

When an Exception is raised from a non-blocking SDK operation, an unexpected error is thrown

MULE-18123

Source not being intercepted when exception in smart connector

MULE-18115

Lazy init: Object store already defined with inline IdempotentRedeliveryPolicy

MULE-18094

Pooled Platform Managed Connection Providers fail to be created

MULE-18093

Add process id to the start up splash

MULE-18090

Flow stuck on JMS publish when connector trows an error

MULE-18089

Flow source stopped event if it was not started because of a ComponentInitialStateManager

MULE-18087

Processing strategy not propagated to chains of scopes in policies

MULE-18081

Remove scheduler warning

MULE-18078

DefaultExecutionContext constructor has too much performance overhead

MULE-18077

Performance issues with functional idioms

MULE-18076

Processing strategy not propagated to sub-flow

MULE-18073

Value is not being stored in queue

MULE-18064

Subscription context not propagated to error handlers

MULE-18059

Flow in initial state stopped is started when app is stopped and started

MULE-18040

Scatter-Gather router does not honor route order in aggregated response hashmap when there are 12 or more routes defined

MULE-18036

Error raised with incorrect type

MULE-18030

HttpPolicyPointcutParameters, only use the headers if a pointcut actually needs them

MULE-18025

OutOfMemoryError on multiple policy redeploys

MULE-18020

Fix reconnection for Paged Operations that fail after the first page.

MULE-18010

Spike: Use generated bytecode instead of reflection to invoke operations

MULE-18004

Make constants in AbstractComponent final

MULE-17994

Allow policy dispose to finish inflight events

MULE-17993

Response callback not called when source policy fails with Source policy already disposed

MULE-17992

MTF test timeout when two flow-ref are used

MULE-17987

Error when logging error for component with special characters in password

MULE-17975

Paging Provider is closed twice when it returns an empty page on the first call to getPage.

MULE-17970

Reduce verbosity of SpringRegistry

MULE-17952

Race condition when cloning a DefaultFlowCallStack

MULE-17950

For multi level metadata, same values are retrieved even when changing key parts on SOAP connectors

MULE-17942

Connection is not closed during Connection Exceptions on Paged Operations.

MULE-17939

Operation considers applied policies regarding thread switches

MULE-17933

PersistentXaTransactionContext#poll not honoring timeout

MULE-17929

Thread stucks when undeploying a failing operation policy

MULE-17917

Missing LegacyConnector class in the compatibility module.

MULE-17916

Error on returning a CoreEvent from Soapkit executor

MULE-17911

Application logging "FlowStack : <empty> " when LoggerContext.updateLoggers() is called

MULE-17908

Missing element in xsd for compatibility plugin

MULE-17906

Missing configuration for ConfigOverride parameter with implicit configuration

MULE-17905

OAuth token is not refreshed when a paged operation throws the exception when obtaining the second page.

MULE-17904

Policy execute-next throws error when inside transactional try

MULE-17903

CursorProvider not resolved for Object type parameters

MULE-17902

Version is not compliant with Semver 2.0

MULE-17901

AbstractCursorStreamProviderFactory class cast Exception

MULE-17888

ChoiceRouterObjectFactory is not aware of MuleContexts without validations

MULE-17885

DataWeave EL should not be lazy when not in tooling mode

MULE-17883

ParameterResolvers initialize a new AttributeEvaluator on each execution

MULE-17882

NoSuchBeanDefinitionException: No qualifying bean of type 'org.mule.runtime.extension.api.client.ExtensionsClient' when deploying a domain with a configuration for WSC

MULE-17874

SDK Should not reject dynamic metadata resolution when an optional key is null

MULE-17863

Avoid file leak in TlsConfiguration

MULE-17862

Avoid file leak in ParseTemplateProcessor

MULE-17856

Large overhead at ExecutionMediator

MULE-17849

Flow’s error response builder being executed twice

MULE-17845

NPE on MuleArtifactContext#resolveErrorType while resolving empty raise-error element

MULE-17843

When smart connector in a policy has a parameter with an invalid DW, it hangs

MULE-17833

Contention when instantiating a FileStoreInputStreamBuffer

MULE-17832

Flow’s error response builder being executed when a policy fails

MULE-17819

ComponentLocationVisitor creates wrong Locations for Connections

MULE-17814

Infinite Loop when setting -Dmule.classloading.verbose=true

MULE-17813

SourcePolicyContext is created and added even if no policies apply

MULE-17812

Refresh Dance not executed after TokenExpiredException

MULE-17800

ParseTemplateProcessor Type Inconsistencies when setting target and target variable

MULE-17791

Unneficient copying of variables and internal params in EventBuilder

MULE-1778]

Add a compile() method on the ExpressionLanguage

MULE-17770

Allow UTF-8 in disposition content headers for http request

MULE-17766

Race condition on recursive check in flowRef with scatterGather

MULE-17765

Validation module does not map MULE:EXPRESSION errors to custom application errors and error logging differs when error is raised in sub-flow

MULE-17763

Excesive contention on CursorManager#manage()

MULE-17762

MuleContext.getSecurityManager() accesses the registry on every invocation

MULE-17754

NoSuchElementException when using TransformationService with global errorHandler

MULE-17750

High contention on streaming ByteBuffer pool

MULE-17747

Event context termination callbacks not called on some situations

MULE-17741

FirstSuccessful implementation is blocking

MULE-17730

Fix lazyinit for email config in a domain

MULE-17726

LazyMuleArtifactContext is not disposing correctly components

MULE-17725

DomainClassLoaderFactory doesn’t remove cached class loaders on dispose

MULE-17698

OAuth 2 Client Credentials not resolving dynamic metadata

MULE-17696

Optional ParameterGroups are required to be exported

MULE-17692

TypedValue throws NPE when calling .toString() on null value.

MULE-17689

DefaultMetadataCacheManager is not reusing the ObjectStore partition

MULE-17686

NPE when stream is remanaged after previous managing decorator is collected

MULE-17671

NPE in Policy is producing mule to hang

MULE-17668

AST: Ref parameters with null values are marked as missing dependencies

MULE-17661

NPE when trying to retrieve metadata using JMS connector

MULE-17659

Custom Configuration Properties' parameters cannot depend on Deployment Properties

MULE-17588

Lazy init: <notifications ..> component not being initialized

MULE-17560

DefaultPersistentMetadataCacheManager is created per application context therefore the shared OS partitioned fails with concurrency

MULE-17541

Lazy init: <object class="…​" '/> not lazy initialized

MULE-17530

Remove flatMap from CompositeOperationPolicy#applyNextOperation

MULE-17529

Remove String.format from PolicyEventMapper

MULE-17524

Set instead of List generating inconsistencies resolving dependencies

MULE-17522

Fix case for domains in LazyInit on AST

MULE-17521

Avoid using an AutoCloseInputStream for streams

MULE-17518

Don’t generate schemas in test runner

MULE-17517

Source onTerminate callback should run on its own scheduler

MULE-17515

Create corrupted files directory before attempting to move files

MULE-17510

MetadataOutputDelegate always setting isDynamic to false for MetadataAttributes

MULE-17507

Remove unused legacy processing strategies

MULE-17505

Runtime is not starting ConnectionProviders during metadata resolution phase

MULE-17486

System.gc() called multiple times when disposing ClassLoaders

MULE-17480

Http requester can’t handle large headers in Mule 4

MULE-17472

Configuration property output not correct when prefix is escaped

MULE-17466

Maps should not be required to have getters

MULE-17451

Top level object stores should be started sooner

MULE-17449

ManagedCursors allow access to unmanaged provider

MULE-17431

ExtensionMessageSource requires FlowConstruct to be root element

MULE-17429

Workaround for MMP-499 in runtime

MULE-17426

Stacktrace is logged when undeploying a policy

MULE-17421

RoundRobin implementation is blocking

MULE-17416

ComponentModel equals/hashCode ignoring location

MULE-17415

Polling Sources fail to pick the same item multiple times (Regression)

MULE-17409

MetadataCacheIdGenerator for configuration elements is not taking into account parameters and only using DslTagId hash

MULE-17401

Scheduler source should route emitted message through FlowProcessMediator

MULE-17398

Operations that return a PagingProvider do not populate the type catalog properly

MULE-17390

MessageProcessPhase and MessageProcessTemplate are no longer used

MULE-17386

CommonSourcePolicy callback invoked twice when event is failed

MULE-17384

Extensions maven plugin not honoring extensions dependencies

MULE-17383

High CPU usage by VM Listeners with Persistent queues

MULE-17373

Final "catch-all" check for error handlers does not account for ANY matcher

MULE-17362

Top-level pojos from extensions do not have annotations

MULE-17359

CPU Light thread pool exhausted due to a testConnectivity when DynamicConfiguration is created

MULE-17346

Move ParameterDslDeclarationEnricher to extensions-api

MULE-17341

Referenced subflows are not being started after stop-start the application

MULE-17333

Missing hashCode method in TypedValueTypeAnnotation

MULE-17331

ParameterGroup with showInDsl property set and isOneRequired fails to instantiate operation

MULE-17330

Race condition when the same CursorProvider is managed twice

MULE-17322

ComponentResultJsonSerializer uses TCCL to load by SPI type annotations contributed by extensions-api

MULE-17313

Transaction began using TryScope are not switching to IO

MULE-17311

Services started by an app plugin retain app classloader after reploy/undeploy

MULE-17307

MetadataTypes from the extension model have different instances representing the same type

MULE-17300

DefaultArchiveDeployer#deployPackagedArtifact doesn’t redeploy when receives an URI

MULE-17298

Splash screen does not list odd named patches

MULE-17296

CursorProvider wrongly marked as a consumable class

MULE-17293

Stereotypes enrichment is done before all types are determined

MULE-17288

CacheId for fetching metadata keys should be broader

MULE-17277

Websockets dropped after 30 seconds idle

MULE-17267

Race condition on source shutdown and restart on connection exception

MULE-17264

Reintroduce the event buffering when dispatching to a flow

MULE-17250

POC on Remove flatMap in ModuleFlowProcessingPhase$FlowProcessor

MULE-17240

MultiMap is losing the order when converting to ImmutableMultiMap

MULE-17225

Loader constraint violation when trying to deploy application.

MULE-17223

MuleApp with Salesforce Connector leaking MuleApplicationClassLoader after undeploy or hotdeploy

MULE-17218

Mule SDK is leaking extensions configurations over the time

MULE-17210

Too many ephemeral events are created just to set a variable

MULE-17182

CursorProvider set in variables are not managed

MULE-17168

Remove softreferences for app classloaders to avoid OOM on redeploy

MULE-17166

Wrong group id for HTTP Connector in BundlePluginDependenciesResolver

MULE-17112

Internal libraries of a plugin are overridden by a sharedLib fron an app

MULE-17110

NTLM authentication with dynamic credentials is successful despite credentials changes

MULE-17105

Typo in 'secutiry' package

MULE-17096

NullPointerException when lazy initializing subflow with async scope

MULE-17091

Object streams not automatically closed if <non-repeatable-iterable> option is selected

MULE-17082

Race condition on test connectivity while deploying applications

MULE-17081

PipelineMessageNotificationListener returns a PipelineMessageNotification with null event when an exception is raised in the Mule flow.

MULE-17077

PersistentQueueTransactionContext#poll not honoring timeout

MULE-17065

Scatter gather and Parallel Foreach are not working inside error handler

MULE-17061

Optimization to avoid thread switch in PS is broken

MULE-17055

@OutputJsonType doesn’t work correctly with array operations

MULE-17051

Default Error Handler should be looked up after initialization

MULE-17050

SDK Non Blocking operation and policy is not returning a response under load

MULE-17048

Race condition when stopping a flow with an inflight event in an async block

MULE-17045

Connections are not closed when streaming operation fails

MULE-17025

ErrorHandler raising error not working

MULE-17023

Nested Try is rolling back tx created by outer try

MULE-17022

Transformation resolver failing to found transformer between byte array and inputStream

MULE-17019

Unauthorize operation does not reset ConnectionProviders

MULE-17007

@OutputJsonType does not set metadata type id

MULE-16995

Shared runtime deps in app mess up classloading

MULE-16994

Use of cache instead of WeakHashMap to avoid infinite loop in DefaultLifecycleInterceptor

MULE-16991

Race condition when invalidating cached connections

MULE-16987

Interception API: Parameters of smart connector not intercepted

MULE-16986

XA Transactions fail to rollback on ConnectionException

MULE-16983

Reconnection should not retry when resource has joined active transaction

MULE-16982

ArrayOutOfBoundException when creating custom scheduler

MULE-16979

Review choice

MULE-16974

FTP reconnection strategy repeat the "start delay" wait time

MULE-16965

MuleRuntimeException when creating namespace for custom error

MULE-16964

TryScope with no tx fails within subFlow+async

MULE-16952

Publisher returned by applyWithChildContext not completed when source is completed

MULE-16936

Mule 4 JMS Bridge (ActiveMQ) scenario stops working after a certain time

MULE-16920

"Cannot process event as 'flow' is stopped" when disposing and reinitializing source

MULE-16899

ClassCast exception when registry lookup finds no match

MULE-16896

Bound connections not released on TransactionException

MULE-16894

IllegalStateException in Polling Source when cluste node is shutting down

MULE-16892

Error handler being executed twice when flow ref is involved

MULE-16891

flowTrace OoM when using foreach with large collections

MULE-16890

AdoptJdk shown as un unsupported vendor

MULE-16889

DefaultDomainManager#getDomain should retrieve a compatible version of the required domain

MULE-16878

StringToEnum Transformer should have different names for each extensionModel

MULE-16872

Async in a transaction executes in the same thread as the transaction

MULE-16856

Starting a flow should fail when a task is rejected from scheduler.

MULE-16853

ConfigurationProperties does not honor properties hierarchy when having prop resolved with placeholder

MULE-16847

MessageProcessors.processWithChildContext must complete the EventContext

MULE-16841

Password mask regex does not consider dw and non-literal expressions.

MULE-16837

[Policy][OAuth] - Timeout and low TPS

MULE-16836

Cannot find snapshot artifact via resource loader when trying to scaffold an API

MULE-16831

Fix XA transactions with bitronix

MULE-16830

Global Properties are taking precedence over Application Properties

MULE-16824

LazyInit should initialize the Mule configuration at part of the component initializations phase

MULE-16817

Pooled connections are not removed from the pool when they should evict.

MULE-16790

Global ErrorHandler does not resolve transaction

MULE-16786

Dynamic configurations eviction should consider sources as in-flight operations

MULE-16784

MuleClassLoaderLookupPolicy wrongly assumming javax.xml.bind.attachment as system package in Java 11

MULE-16775

OnErrorPropagate in global error handler is not rollbacking tx

MULE-16758

Multithreaded sources are concurrently reconnected more than once

MULE-16753

A transaction is not available error related to execution on a cpuLight thread

MULE-16744

spring.schemas exported from runtime conflict with spring dependencies used in an app

MULE-16730

Interception API: Validation all throws NullPointerException

MULE-16725

Fix race condition in flow lifecycle handling

MULE-16633

Cool Mulesoft logo in splash screen looking bad in windows

MULE-16551

When Policy is present, Event is not serializable

MULE-16527

Remove flatMap in UntilSuccesful

MULE-16463

Remove flatMap in static <flow-ref>

MULE-16462

Remove flatMap in ModuleFlowProcessingPhase$FlowProcessor

MULE-16461

Remove concatMap in XML SDK chain execution

MULE-16285

Interception API: Smart connectors inside scopes are not skipped properly

MULE-16141

SDK is not validating input POJOs to have a default constructor

MULE-16129

Cannot deactivate streaming in operations that return lists/maps of streams.

MULE-15752

InjectParamsFromContextServiceMethodInvoker makes excessive registry lookups

MULE-15599

Serializing an artifact model constructed from serializing a JSON loses data

MULE-10702

Remove double check locking: StaticBulkQueryResolver

MULE-10347

Generics are not resolved for Map implementations

EE-7290

[IBMMQ][Bridge][Daily] TPS Degradation for all IBMMQ_Bridge apps

EE-7289

[JMS Bridge] jms_bridge_transactional app TPS lower than 1

EE-7283

OCS add system property for setting platfotm authentication url suffix

EE-7277

MuleLicenseInterrupter creates a thread named pool-n-thread-m

EE-7276

Regression on http connector

EE-7272

Cache scope storing unneeded data in the store

EE-7268

Possible memory leak when restarting batch applications

EE-7244

Getting "Cannot open a new cursor on a closed stream" error when 0 records are being processed

EE-7243

Batch Aggregator Out of Memory issue

EE-7239

Ambiguous PID when /mule start is Used

EE-7164

Batch Engine is no reinitialized in case app is restarted

EE-7135

TransactionalWrapper is not setting XAResources that are not DirectXASessions as resources to TransactionalManagerWrapper

EE-7100

BTI wrapper not returning XAConnection

EE-7061

Lingering Streaming aggregator input queue transactions while reading

EE-6927

EE version is loading mule-service-weave and mule-service-weave-ee

EE-6889

JdbcMapStore#loadAll(keys) should only load keys passed as parameter

EE-6866

When thread waiting in Hz is interrupted, InterruptedException is not thrown immediately

EE-6860

Escape table names in Microsoft SQL database store query builder strategy

EE-6857

File leak when getting dw file for transformation

EE-6852

Unlock hazelcast lock in the same thread where it was locked

EE-6834

Http Policy Module has no Extension Model

EE-6830

Tracking processors are marked as UNKNOWN instead of OPERATION

EE-6823

Automatically undeployed tooling apps are kept on memory for around an hour

EE-6804

Bitronix Proxy hides connectivity exceptions

EE-6797

Bitronix exception when redeploying an app using XA transactions

EE-6796

Dirty Bitronix transaction log

EE-6780

Corrupt patches not applied but logged as applied

EE-6779

BitronixTransactionManager built before QueueManager initialize causes NPE

EE-6774

Memory leak on com.mulesoft.mule.runtime.bti.internal.xa.QueueManagerXaResourceProducer

EE-6769

Possible race condition when registering ConnectionFactory in Bitronix

EE-6710

Batch RecordFilteringStrategy is not filtering correctly

EE-6682

Table name transforms in cluster object store are only working for postgresql

EE-6574

Organization credentials and encryption key are displayed in plain text in Cluster splash screen.

EE-6377

Batch Aggregator does not support JSON Payload

EE-6374

Sending large bodies causes OOM error in HTTP requester

EE-6338

A project using Netsuite fails with OOM after a few redeploys

EE-6108

Mule 4 Performance degradation on HTTP Proxy Scenarios

MULE-18288

Prevent memory leaks from plugins that use scala

MULE-18262

Allow to customize the default scheduler fixed frequency through a System Property

MULE-18141

Add warnings about not found classes for verbose classloading

MULE-18127

Provide a mechanism to disable log separation

MULE-18050

Improve performance of binding context

MULE-18049

Improve performance of policies lookup when no policies are applied

MULE-18047

Add the component that generated a cursor provider

MULE-18023

Remove spring repo declaration in poms

MULE-18021

Upgrade log4j to 2.13.1

MULE-18017

Improve performance of LifecycleFilterProxy

MULE-17988

Do not use Optional in Either

MULE-17985

Support policy application depending on request headers

MULE-17935

Support Platform Managed OAuth tokens in the SDK

MULE-17910

Remove distinct from child context processing

MULE-17909

Replace calls to flux.mergeWith

MULE-17889

Support repeatable streaming buffering from an existing file

MULE-17844

Remove append-string-transformer

MULE-17829

MessageProcessorNotification listeners not registered by default

MULE-17825

Group error handling internal parameters into unified pojos

MULE-17805

Remove child context used in try

MULE-17804

Remove child contexts uses in policies infrastructure

MULE-17801

Improve performance of MetadataType#hashCode

MULE-17780

Avoid creating an extra intercepting chain when there are no interceptors

MULE-17757

Migrate uses of MessagingExceptionResolver#resolve(MessagingException, MuleContext)

MULE-17743

Remove the use of the eventContext ResponsePublisher

MULE-17703

Validate preexisting config-ref parameter on ConfigRefDeclarationEnricher

MULE-17672

Make DefaultTypedComponentIdentifier#hashCode consistent across runs

MULE-17667

Automatically determine if a parameter is the ComponentId

MULE-17647

Allow domains to be redeployed without restarting its stopped applications

MULE-17536

FunctionalReadWriteLock: Provide withReadLock methods

MULE-17535

Performance improvements for MultiMap immutability

MULE-17525

Allow dynamic configuration for the proxy on the HTTP requester

MULE-17498

XML SDK: avoid container componentModel modification in config macroexpansion

MULE-17497

XML SDK: avoid container componentModel modification in operation macroexpansion

MULE-17487

Use OptionalInt instead of Optional<Integer> for building locations

MULE-17420

XML SDK: link with the inner models on the xml sdk component definition

MULE-17417

Add a method in DeploymentService interface to redeploy applications using a new URI

MULE-17334

Add missing exported/imported types in test extensions

MULE-17281

SDK needs to allow operations to obtain the effective retry policy

MULE-17257

Add more detail to FlowBackpressureException

MULE-17256

Add missing stereotypes to tls:context

MULE-17203

Properly add doc: attributes as component metadata

MULE-17185

Flowref flatmap removal leads to a notorious throughput decrease in the static-flow-ref-subflow case

MULE-17161

Allow SDK to specify that certain configs should never be used in an implicit way

MULE-17114

Add the notImported information from MULE-17112 into the plugins packager

MULE-17111

Create API to propagate a whole custom event when an error occurs in a Processor

MULE-17079

Remove flatMap from ProactorStreamProcessingStrategy#proactor

MULE-17078

Remove dependency of transactions infrastructure on the MuleContext

MULE-17066

ExecutableComponent api should provide a way to mutate the child event that is going to be created

MULE-17060

Use the default ProcessingStrategy for policies instead of a custom one

MULE-17001

Avoid unneeded message creation in source callback

MULE-16990

Improve troubleshooting logging for XA transaction

MULE-16980

Allow maven dependency resolution to always update snapshot dependencies

MULE-16954

Improve logging infrastructure performance

MULE-16937

SDK should no longer that at least one Content parameter to be primary

MULE-16928

Review and improve the change for MULE-16919

MULE-16909

Support custom parameters in OAuth Dance

MULE-16908

Support Client Credentials grant type in the SDK

MULE-16881

migrate app deployment file to 4.1

MULE-16871

Test performance improvement of backpressure check before policy execution

MULE-16861

Normalize namespace usage in ComponentIdentifier between runtime and DataSense

MULE-16860

Decouple DataSense from ComponentModel

MULE-16851

Implement CompositeConverter#toString to aid in transformers troubleshooting

MULE-16843

Move backpressure check before policy application

MULE-16838

until-successful attributes should support expressions

MULE-16755

ObjectStore expire: account for inconsistencies that may occur in cluster

MULE-16684

Make default processing strategy the same as the one for flows

MULE-16513

Perform flow backpressure check before source policies are applied

MULE-16491

pattern matching for error types in error handlers' type attribute

MULE-16215

Make infrastructure parameters to appear as not require for metadata

MULE-15645

Enable flowStack by default. This change can result in more detailed information when an error occurs in a Mule application.

MULE-15596

Error Handler: Add support for "when" filtering for a certain "type"

MULE-982

Logged error should suggest how to enable flowstack

EE-6898

Add a way to configure the hazelcast property MERGE_FIRST_RUN_DELAY_SECONDS

EE-6873

Replace slashes with underscores in TableNameNormalizer

EE-6867

HazelcastLockProvider should call MapNameNormalizer method to normalize map names

EE-6864

Escape table names in PostgresSQL database store query builder strategy

EE-6760

Make Bitronix XA connection pool configurable

AGW-3996

Operation policies are not applied to requester when it is inside XML Connector

AGW-3921

Failing to track an api might cause incomplete initialization.

AGW-3908

When an unhandled exception is thrown while deploying a policy, the deployer dies.

AGW-3816

Fix Mule OAuth authentication failure when Using Client-ID/Client-Secret of Child BG

AGW-3739

API is not getting unblocked by Gatekeeper when stopping and starting it from Runtime Manager.

AGW-3506

Analytics only being notified for one app.

AGW-3375

MapDB is corrupting and stops loading / storing contracts.

AGW-3181

Log indicating client id or secret are not provided is never shown.

AGW-3162

Stacktrace logged after redeploying offline policy with multiple api pointcuts.

AGW-3143

Fix Class Loader Issues generated by getLoggingClassLoader.

AGW-3142

Upgrading policy version is not using new policy jar.

AGW-3105

Requester policy hangs when headers in requester expression are null.

AGW-3004

Policy which does not need IdentityManagement still has it in config Data.

AGW-2215

In a policy, when using requester with url instead of request-config, it explodes.

AGW-4022

Remove runtime version from templates of default policies.

AGW-4008

Update jackson library to latest 2.10.x version

AGW-3990

Must upgrade handlebars library version to 4.5.3

AGW-3952

Added ability to ignore API’s base path when matching resource level policies.

AGW-3877

Improve performance in policies

AGW-3840

Add flow name and application name fields, when sending Analytics info to third party systems.

AGW-3749

Analytics engine improvements, data recollection.

AGW-3711

Enhance User-Agent sent by Gateway to Anypoint

AGW-3670

Enable blocking policies being applied to the requester by using "disablePolicies" annotation.

AGW-3550

Change Analytics Returning mechanism when no response is set.

AGW-2090

Add 400, 412 and 502 to the backoff status codes

DataWeave

  • Fix (SE-15642): Index based descendant selector should work as indexing from descendant selector.

  • Fix: Make error dumper include variables.

  • Fix (DW-133): Reuse instance of java when lazy value expressions.

  • Fix (DW-108): MappingCodeGenerator disregards order of arrow mappings when generating script.

  • Fix (SE-8056): Module is not correctly generated when there are recursive types.

  • Fix (SE-15159): Adding a property for security.

  • Fix (DW-126): Wrong type checking between close object and object with fields.

  • Fix: Wrong type checking when calling mapObject with null.

  • Fix (DW-104): Avoid indexWhere fo boxing and unboxing of char and booleans.

  • Fix (SE-14421): Avoid file leaks on indexed files.

  • Fix (SE-14606): Make fromBase64 and toBase64 not to propagate schema for Backwards compatibility.

  • Fix (DW-102): Substring after and Substring After Last should take into account the length of the text.

  • Fix (SE-14623): Fixing Enum Types in Avro.

  • Fix (DW-98): Selecting same part content of different types multiple times should return same content that is in the multipart.

  • Fix (SE-14561): Add support for union type of any kind in Avro.

  • Fix (SE-12726): Do not call to the get() function of a future.

  • Fix deferred mode leaving streams unclosed.

  • Fix (MDF-359): Make stack growable instead of fixed size to avoid unnecessary memory allocation.

  • Fix (MDF-358): Parsing error with single key value pair object.

  • Fix (MDF-357): Adding support for builder static methods for non interfaces.

  • Fix (SE-14264): If not content type is set then binary should be used.

  • Fix (SE-13571): Equal operator for object was affected by the change empty uri and none namespace should be the same.

  • Fix (SE-13571): Empty namespaces should be taken into account as they may be overriding default namespaces.

  • Fix (MDF-355): Avoid creating java writer settings when it is not necessary.

  • Fix: Improve string append performance.

  • Fix: Type parameters where not correctly instantiated when used inside a lambda.

  • Fix: Type resolution on dynamic return type should take into account a specified type.

  • Fix (MDF-352): Split function should take into account writer properties configuration and inferred mimeType properties.

  • Fix: Reduce object allocation in JSON String escaping also fix key length.

  • Fix: Add support for period coercion to number.

  • Fix: GC overhead issue with SeekableStream and EvaluationContext.

  • Fix (SE-13600): Avoid logging the amount of read bytes on range selector over binary.

  • Fix (SE-13440): Avoid registering InMemory DataSources as Closeables as it is not required.

  • Fix: GroupBy now keeps order and performance improvement on groupBy.

  • Fix: Improve performance of reduce array of objects into a single object.

  • Fix (SE-13334): Lower needs to say that works with Comparable types.

  • Fix (SE-13495): Output writer properties should be taken into account when expected data type is used.

  • Fix (SE-12381): Execute simple script on startup to warmup classloader.

  • Fix (SE-12381): Load DataFormats on startup and also load other modules too.

  • Fix (MDF-338): Add com.mulesoft.dw.directbuffer.disable to disable direct buffer.

  • Fix: Capture groups may return null on conditional groups.

  • Fix: Avoid memory leak when automatic coercion of operations.

  • Fix (SE-12381): Make Core to be loaded at statup time.

  • Fix (SE-13334): Fix documentation of max function.

  • Fix (SE-13172): CSV parser for files bigger than 2G.

  • Fix (SE-13071): DataWeaveTypeEmitter should escape literal strings.
This version of Mule runtime is bundled with the Runtime Manager Agent plugin version 2.4.5. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Engine 4.11.0 Release Notes 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/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2026)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/jp/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:
Issue Resolution ID

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The c3p0 library is upgraded to 0.14.1.

W-22990152

The Spring Framework is upgraded to 6.2.19.

W-3300013

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806044

The Netty library is upgraded to 4.2.15.Final.

W-22888966

The Reactor Netty library is upgraded to 1.3.6.

W-22939412
DataWeave 2.11.5 is bundled with the Mule 4.11.6 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2026)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/jp/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:
Issue Resolution ID

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

HTTP Server now supports Upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Test Connection for The HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the Host field.

W-21921687

The Spring Core library is upgraded to 6.2.18.

W-22169898

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971
DataWeave 2.11.4 is bundled with the Mule 4.11.5 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2026)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/jp/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:
Issue Resolution ID

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

Netty HTTP client NTLM authentication no longer fails due to missing TCP connection affinity during the handshake.

W-21615520

The plexus-utils library is upgraded to 4.0.3.

W-21774430

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21913252

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

Netty HTTP client no longer sends an incorrect WWW-Authenticate header during the NTLM authentication handshake.

W-21762949

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

A serialization error that could occur when deserializing data after a Mule runtime upgrade no longer occurs.

W-21951097

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339
DataWeave 2.11.3 is bundled with the Mule 4.11.4 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2026)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/jp/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:
Issue Resolution ID

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

OpenTelemetry Direct streaming now supports FIPS-compatible keystore format.

W-20623905

A warning now appears when an OpenTelemetry property is incorrectly used as a deployment property.

W-21018072

NullPointerException 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.

W-20192960

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

HTTP Netty implementation performance is now improved.

W-20969515

HTTP Server no longer logs an error when a client closes an idle keep-alive connection.

W-21431822
DataWeave 2.11.2 is bundled with the Mule 4.11.3 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2026)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/jp/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:
Issue Resolution ID

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

XSD validations are now enabled by default during deployment.

W-21139633

Errors that are not MessagingException errors are no longer silenced.

W-21043969

The reactor.netty.version library is upgraded to 1.3.2.

W-3300013

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900
DataWeave 2.11.1 is bundled with the Mule 4.11.2 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501

The Mapping Editor API now supports attributes in Anypoint Code Builder.

W-20662336

Updating the expression model in the Mapping Editor API now works correctly.

W-20611263
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2026)February 2026 ### [](#patch-4-11-1)Patch 4.11.1 - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ## [](#february-4-2026)February 4, 2026 ### [](#patch-4-11-0)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/jp/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)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:
Issue Resolution ID

HTTP/2 connections now correctly multiplex when processing concurrent requests, reducing connection creation and latency.

W-19860076

The runtime now leverages the AST file for applications with the until-successful component instead of parsing configuration XML files.

W-20283146

Batch record deserialization no longer fails when a Netty exception occurs.

W-20552358

Inbound HTTP/2 header validation is now improved.

W-19873453

The org.apache.logging.log4j:log4j-core dependency is upgraded to 2.25.3.

W-20679050
DataWeave 2.11.0 is bundled with the Mule 4.11.0 release. This release addresses these DataWeave issues:
Issue Resolution ID

AST scope navigation now works correctly for cross-file references when using the Tooling API.

W-20212809

A specific overload for isEmpty on binaries is now available to prevent implicit coercion to other types.

W-20049958

Materialized Java values are now cached to allow multiple executions using the same value.

W-20091279

Semantic tokens are now supported in the Tooling API.

W-19846990

NullPointerException no longer occurs when handling annotation types.

W-19853000

LogLevel documentation is now included directly in the code.

W-17800393

The commons-beanutils library is upgraded.

W-3300013

Base64 encoding and decoding now support payloads larger than memory.

W-18575719

Eager materialization is now supported on values, enabling caching of all exceptions inside the try function.

W-19717874

Avro enum, map, union, and fixed types are now supported as top-level elements.

W-19596039

WeaveCompiler now allows precompiling mappings and modules without validation or type checking.

W-19667273

Type check errors are now correctly reported when resolving type checking on subgraphs.

W-19564697

Lazy loading of source files is now enabled during binary compilation, avoiding unnecessary memory usage.

W-19594703

Type inference now works correctly when using the -- operator to subtract a key from an object.

W-19595907

Warning and error messages now propagate correctly between compilation phases.

W-19386849

Base types are now used to validate accepted values, preventing premature materialization.

W-18943395

Optional types now propagate correctly through chains of value selectors.

W-19272070

The syntax version is now added to TypeGraph and WeaveTypeResolution.

W-19271992

The classloader resource resolver now resolves paths correctly on Windows systems.

W-19407283
## [](#bundled-components)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/jp/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:
Module or Extension Version

APIkit for Mule 4

1.11.10

APIkit for OData

2.3.4

APIkit for OData 4

1.5.4

APIkit for SOAP

1.6.7

APIkit for GraphQL

1.1.1

Spring module

2.1.1

MUnit plugin

3.6.3
## [](#considerations-for-mule-extension-developers)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)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) # Mule Runtime Engine 4.12.0 Release Notes 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/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2026)October 2026 ### Fixed Issues ### [](#patch-4-12-5)Patch 4.12.5 The October patch update 4.12.5 addresses regressions in the October patch update 4.12.4.
Issue Resolution ID

Mule

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-12-4)Patch 4.12.4 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.12.4 includes Runtime Manager agent 2.8.5. See [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5). ### Fixed Issues Patch release version: 4.12.4 This patch update addresses these Mule issues:
Issue Resolution ID

The Log4j library is upgraded to 2.26.1.

W-24061648

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

Network information listening ports are now scoped to the Mule process.

W-24043880

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

On CloudHub 2.0 and Runtime Fabric deployments, container logs exported through OpenTelemetry now correctly use the deployed application’s configured service name, instead of the generic mule-container name.

W-23734353

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2026)September 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.12.3 includes Runtime Manager agent 2.8.4. See [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4). 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. - Health Signals: Evaluates a small set of fast host- and JVM-level health signals and reports those that triggered, including low memory, high CPU steal, and JVM crash logs. - Memory Detail: Provides a JVM memory-pool breakdown and garbage-collector statistics, showing heap and non-heap usage with metrics such as initial, used, committed, and maximum memory values. - Known Issues: Scans the runtime logs and deployed applications for well-known problem signatures, including out-of-memory conditions, abnormal terminations, and MUnit packaging issues. ### Fixed Issues Patch release version: 4.12.3 This patch update addresses these Mule issues:
Issue Resolution ID

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23671475

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531
DataWeave 2.12.3 is bundled with the Mule 4.12.3 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2026)August 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.12.2 includes Runtime Manager agent 2.8.3. See [Runtime Manager Agent 2.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-3). 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. - Network Info: Shows host-level network diagnostics, including the hostname, network interfaces with their assigned IP addresses and I/O counters, and active and listening network connections. - Agent Info: Reports the installation and health of the Mule agent that pairs the runtime with Anypoint Platform, including whether the agent is installed, its version, key configuration values, keystore certificate details, and the most recent connection status. - Platform Connectivity: Checks TCP connectivity from the Mule runtime host to the Anypoint Platform endpoints and dumps the TLS certificate chain presented by the platform. ### Fixed Issues Patch release version: 4.12.2 This patch update addresses these Mule issues:
Issue Resolution ID

Lazy initialization no longer fails with a NullPointerException when an application using the VM connector’s publish operation also configures a global error handler.

W-23156632

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

An HTTP request client connecting through a proxy no longer hangs when the proxy responds with a 407 (Proxy Authentication Required) response during the CONNECT tunnel handshake.

W-23384719

The HTTP request client now sends a correctly formed request line when connecting through a forward proxy.

W-23384645

A NullPointerException no longer occurs when the HTTP request client reuses a pooled connection to a forward proxy.

W-23384744

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Batch module now provides a public API to configure a custom queue manager and queue timeout.

W-23371797

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Sec-WebSocket-Protocol header is now forwarded on outbound WebSocket connections, so subprotocol negotiation with the server succeeds.

W-23071781

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API Gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23165634
DataWeave 2.12.2 is bundled with the Mule 4.12.2 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

Type metadata processing now correctly handles sibling references that target the same type, preventing duplicate annotations.

W-23424037

DataWeave now handles Java Platform Module System (JPMS) access restrictions more gracefully when running on Java 17 and later in Mule runtime 4.6.0 and later.

W-23354139

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2026)July 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.12.1 includes Runtime Manager agent 2.7.16. See [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). Feature Flagging Mechanism: - Mule 4.12 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.12.1 This patch update addresses these Mule issues:
Issue Resolution ID

Clustered applications deployed with two or more replicas no longer fail to start with a NullPointerException error during cluster node discovery.

W-22843942

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Object Store retrieved from the registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

The error type in the EE cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Test Connection for the HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the host field.

W-21921687

HTTP Server now supports upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

In-memory Object Store partitions are now created correctly when an application is deployed to a cluster with the Object Store plugin enabled.

W-17714668

Deserialization errors no longer occur in the Object Store during a runtime patch upgrade.

W-20880559

Applications deployed with a serialized AST now include all Mule error types in the error type repository.

W-22399271

Applications that use HTTP request attributes no longer fail annotation processing due to default constructor validation.

W-22385620

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

OpenTelemetry flow statistics now report metrics correctly for applications with more than one flow.

W-23051614

The artifact type (domain, policy, or application) is now included as an OpenTelemetry resource attribute.

W-21768636

OpenTelemetry metric attribute names now use a consistent notation.

W-21921584

The mule.openTelemetry.logging.exporter.resource.container.service.name system property is now available to set the service name that the Mule container reports for OpenTelemetry telemetry.

W-22861497

Event dumps now include a state for events that are waiting on a non-blocking operation.

W-22142952

The Netty library is upgraded to 4.2.15.Final.

W-22831076

The c3p0 library is upgraded to 0.14.1.

W-22990155

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The Reactor Netty library is upgraded to 1.3.6.

W-3300013

The Jackson Core library is upgraded to 2.21.1.

W-22839747

The Apache Neethi library is upgraded to 3.2.1.

W-22839752

The OpenTelemetry API library is upgraded to 1.62.0.

W-22849469

The Spring Framework is upgraded to 6.2.19.

W-22939417
DataWeave 2.12.1 is bundled with the Mule 4.12.1 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2-2026)June 2, 2026 ### What’s New The 4.12.0 version of Mule runtime introduces these enhancements: OpenTelemetry Direct Telemetry Stream: - Mule 4.12 adds OpenTelemetry metrics support to Direct Telemetry Stream, including message processing, flow inventory, error tracking, runtime alerts, and JVM instrumentation metrics. See [OpenTelemetry Support in Mule Runtime](https://docs.mulesoft.com/mule-runtime/latest/otel-support) for a detailed description of the feature. Feature Flagging Mechanism: - Mule 4.12 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.12.0 includes Runtime Manager agent 2.7.15. See [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15). General improvements: - To build applications for Mule runtime engine 4.12.0, use Mule Maven Plugin 4.10.0 or later. See [Mule Maven Plugin 4.10.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.0-release-notes). ## [](#dataweave-features)DataWeave Features The 2.12.0 version of DataWeave introduces these new features and enhancements: Scope Visibility: - DataWeave now supports `private`, `internal`, and `@VisibleTo` annotations for controlling directive access. This enables better code encapsulation and visibility management across DataWeave modules. See [Scope Visibility in DataWeave](https://docs.mulesoft.com/dataweave/latest/dataweave-scope-visibility). Component Metadata: - DataWeave introduces `dw::meta::Component` and related component types for working with component descriptors. This provides enhanced metadata handling capabilities. See [Component (dw::meta::Component)](https://docs.mulesoft.com/dataweave/latest/dw-component) and [Component Types (dw::meta::Component)](https://docs.mulesoft.com/dataweave/latest/dw-component-types). General Improvements: - The [UNLIMITED\_CONTEXT](https://docs.mulesoft.com/dataweave/latest/dw-math-variables) math variable now has the `precision=0` and `roundingMode=HALF_UP` properties. - The [Maven plugin for DataWeave](https://docs.mulesoft.com/dataweave/latest/dataweave-maven-plugin) now includes guidance for configuring cryptographic taint analysis during compilation. - The [DataWeave extension plugin](https://docs.mulesoft.com/dataweave/latest/dataweave-extension-plugin) now provides editor support for scope visibility validation and diagnostics. - 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.11.0 Mule release through June 2026:
Issue Resolution ID

Upstream HTTP requests are now cancelled when a downstream client disconnects, preventing unnecessary data transfer.

W-20084343

The Netty HTTP client no longer throws NullPointerException when handling Expect 100-Continue responses.

W-21513490

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

The Apache CXF library is upgraded to 3.6.8.

W-20541600

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

Redelivery policy logging now includes additional context for troubleshooting.

W-20636028

The Tanuki Java Service Wrapper is upgraded to 3.6.4.

W-17051070

The RAML parser is upgraded to 1.1.10.

W-21768014

The OpenTelemetry SDK is upgraded to 1.60.1.

W-21808539

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971
DataWeave 2.12.0 is bundled with the Mule 4.12.0 release. This release addresses these DataWeave issues:
Issue Resolution ID

DataWeave now supports the private modifier on fun, var, ns, and type declarations to hide them from importers.

W-21148967

internal is no longer a reserved word and can now be used as an identifier in DataWeave scripts.

W-21508044

The compiler now reports an error when overloads of the same function declare different visibility modifiers.

W-21362539

StackOverflowError no longer occurs in the type checker when resolving intersections of unbound type parameters.

W-20124753

Runtime errors no longer occur when invoking overloaded functions across modules.

W-21811015

Spurious type-check errors no longer occur when an optional key-value pair is assigned to a required one.

W-21351058

deferred values passed to the write function now terminate correctly.

W-20925604

Out-of-memory errors no longer occur when reading large text or CDATA sections with the indexed XML reader.

W-21006104

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
## [](#bundled-components)Bundled Components - DataWeave version 2.12.0 - Runtime Manager Agent plugin version 2.7.15 ### 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/jp/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:
Module or Extension Version

APIkit for Mule 4

1.11.17

APIkit for OData

2.4.0

APIkit for OData 4

1.6.0

APIkit for SOAP

2.1.0

APIkit for GraphQL

1.2.0

Spring module

2.1.2

MUnit plugin

3.7.1
## [](#considerations-for-mule-extension-developers)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)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/latest/mule-troubleshooting-plugin) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Engine 4.13.0 Release Notes 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/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2026)October 2026 ### Fixed Issues ### [](#patch-4-13-1)Patch 4.13.1 The October patch update 4.13.1 addresses regressions in the October patch update 4.13.0.
Issue Resolution ID

Mule

Applications no longer fail to deploy when the type of an on-error-propagate or on-error-continue is a property placeholder and the flow contains a component that supports streaming and requires a connection, such as an HTTP Request or Kafka operation.

W-24456406

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

Polling sources that use a CloudHub Object Store v2 for watermarks now track processed items in the object store’s configured partition instead of the default partition.

W-24459240

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-13-0)Patch 4.13.0 ## [](#october-6-2026)October 6, 2026 ### What’s New The 4.13.0 version of Mule runtime introduces these enhancements: Cache Scope: - Mule 4.13 updates the Cache scope so that it persists only the message payload and attributes instead of the full Mule event. The `mule.serialize.message.in.cache` feature flag controls this behavior, and Mule migrates existing cache entries from the full-event format on demand. As a result, the Key Generator, Response Generator, and Event Copy Strategy customizations are deprecated for applications that set `minMuleVersion` to 4.13.0 or later. See [Set Up a Caching Strategy](https://docs.mulesoft.com/mule-runtime/latest/cache-scope-strategy) for a detailed description of the feature. OpenTelemetry Direct Telemetry Stream: See [OpenTelemetry Support in Mule Runtime](https://docs.mulesoft.com/mule-runtime/latest/otel-support) for a detailed description of the feature. - Tracing: - You can now set the OpenTelemetry tracing level for specific components or flow locations, in addition to the application-wide level. See [Tracing Levels](https://docs.mulesoft.com/mule-runtime/latest/otel-support#tracing-levels) for more information. - Traces for the same API resource now share one span name. When APIkit Router routes a request, the root span name uses the HTTP method and the matched route template, such as `GET /api/books/{bookId}`, instead of the raw listener path. - The Mule Tracing module now includes the `add-root-span-attributes` operation, which adds custom attributes to a transaction’s root span from anywhere in the flow. See [Add Root Span Attributes](https://docs.mulesoft.com/tracing-module/latest/tracing-module-reference#add-root-span-attributes) for more information. - Metrics: - Flow statistics counters (`received.events`, `dispatched.messages`, `execution.errors`, `fatal.errors`, and `dispatched.primary.messages`) now report per-flow values by default through the `mule.flow.name` attribute. See [Message Processing Metrics](https://docs.mulesoft.com/mule-runtime/latest/otel-support#message-processing-metrics) for more information. - You can now set `service.name` and `service.namespace` for JVM metrics at the container level, separately from the application level. See [Custom Service Name and Service Namespace](https://docs.mulesoft.com/mule-runtime/latest/otel-support#custom-service-name) for more information. - You can now set the aggregation temporality for exported metrics through the `mule.openTelemetry.meter.exporter.aggregationTemporality` property. Supported values are `CUMULATIVE` (default), `DELTA_PREFERRED`, `LOW_MEMORY`, and `FULLY_DELTA`. See [Metrics Temporality](https://docs.mulesoft.com/mule-runtime/latest/otel-support#metrics-temporality) for more information. - Resource Attributes: - Mule runtime now adds a `mule.artifact.type` resource attribute (`app`, `domain`, or `policy`) to every exported span, log record, and metric data point. See [Automatically Added Resource Attributes](https://docs.mulesoft.com/mule-runtime/latest/otel-support#automatically-added-resource-attributes) for more information. - Anypoint Platform metadata resource attributes now use the `mule.anypoint.` prefix, for example, `mule.anypoint.org.id`. All Mule-generated attribute keys in traces, logs, and metrics now use dot notation. The previous unprefixed keys are deprecated, but Mule still exports them alongside the new keys. See [Automatically Added Resource Attributes](https://docs.mulesoft.com/mule-runtime/latest/otel-support#automatically-added-resource-attributes) for more information. Feature Flagging Mechanism: - Mule 4.13 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.13.0 includes Runtime Manager agent 2.8.5. See [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5). ## [](#dataweave-features)DataWeave Features The 2.13.0 version of DataWeave introduces these new features and enhancements: JSON Web Token Signing: - DataWeave introduces the `dw::util::jwt::HMAC` module for creating signed JSON Web Tokens (JWTs) with the HS256, HS384, and HS512 algorithms. See [HMAC (dw::util::jwt::HMAC)](https://docs.mulesoft.com/dataweave/latest/dw-hmac). - DataWeave introduces the `dw::util::jwt::RSA` module for creating signed JWTs with the RS256, RS384, and RS512 algorithms using unencrypted PKCS#1 or PKCS#8 PEM private keys. See [RSA (dw::util::jwt::RSA)](https://docs.mulesoft.com/dataweave/latest/dw-rsa). ### Fixed Issues The release addresses these Mule issues and incorporates all patch updates from the 4.12.0 Mule release through October 2026:
Issue Resolution ID

The jsoup library is upgraded to 1.23.2.

W-23987955

The Jackson library is upgraded to 2.22.3.

W-24335732

The Reactor Core library is upgraded to 3.8.7.

W-23987958

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

The raml-parser-2 library is upgraded to 1.2.1.

W-23570110

Error-mapping preservation during error propagation is now enabled by default. An error whose type was already resolved inside a scope, including any remapping by an error mapping, now keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type. You can disable this behavior by setting the mule.honourErrorMappingsOnErrorPropagation system property to false.

W-23955755

OpenTelemetry metric exporters now support per-exporter view enrichment and resource attribute overrides.

W-23367495

JSON schema validation is migrated from the everit library to networknt, with everit retained as a fallback.

W-16530105

HTTP header values containing CR/LF characters are now sanitized instead of causing the request to be rejected.

W-22252135

minMuleVersion values are now normalized when loaded, preventing the patch or revision portion from being truncated.

W-24231362

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

Logging export reconfiguration is fixed for single application mode.

W-20908857

The ObjectStore API is extended with an upsert operation and an isThreadSafe indicator.

W-23090592

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809

A java.lang.UnsupportedClassVersionError thrown when a connector’s compiled target doesn’t match the running JVM is now handled gracefully.

W-24193358

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

A source policy that uses Async, Parallel For Each, or Scatter-Gather no longer builds its response from the failure response parameters instead of the success response parameters, and no longer silently drops the forked route’s response processing.

W-23938349

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

The commons-beanutils library and its transitive commons-collections 3.2.2 dependency are removed from Mule Runtime modules.

W-16918287

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

An unresolved placeholder in the meter-exporter configuration now degrades to its default value at tracer startup instead of causing a failure.

W-23650358

Dynamic reload of the metrics exporter configuration is now supported.

W-21921629

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

OutputHandler is deprecated and its support is removed.

W-23660888

A SerializationException now raises a MULE:SERIALIZATION error, instead of MULE:UNKNOWN.

W-21381359

The exporter-health backpressure-alert cadence for OpenTelemetry tracing, metrics, and logging is now configured through a single system property, mule.openTelemetry.meter.exporter.healthMetrics.alertingFrequency, instead of the separate per-signal metricsLogFrequency properties, which are deprecated and no longer consumed.

W-22193713

MULE:INVALID_INPUT_PARAM is now preserved as a suppressed error when a MULE:SOURCE_RESPONSE_GENERATE error occurs.

W-22293407

SDK parameter validation errors are now mapped to the MULE:INVALID_INPUT_PARAM error type.

W-2227652

Mule-generated tracing spans no longer truncate attribute values at OpenTelemetry’s default 128-character limit. Attribute values are now preserved up to 4096 characters before truncation.

W-20091299

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

SQSQueueManagementService is added to the serialization allowlist.

W-24197744

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401
DataWeave 2.13.0 is bundled with the Mule 4.13.0 release. This release addresses these DataWeave issues:
Issue Resolution ID

Memory usage for text/plain output is reduced.

W-20063270

Eagerly materialize executable Weave reader results.

W-23837275

Thread safety is improved when processing Java map values.

W-23661641

DataWeave tooling now reports design-time warnings when Java classes referenced in application/java schemas can’t be found or are inaccessible through JPMS.

W-22797049

DataWeave now filters Java classes in JPMS-unexported packages during Java module resolution, preventing runtime IllegalAccessException failures. This behavior is enabled by default on JDK 17 and later with DataWeave language version 2.13 and later. To keep the previous behavior, set mule.dw.filter_jpms_inaccessible_modules=false.

W-22779527

Cryptographic security warnings and errors now include call stacks.

W-22144340
## [](#bundled-components)Bundled Components - DataWeave version 2.13.0 - Runtime Manager Agent plugin version 2.8.5 ### 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/jp/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:
Module or Extension Version

APIkit for Mule 4

1.11.17

APIkit for OData

2.4.0

APIkit for OData 4

1.6.0

APIkit for SOAP

2.1.0

APIkit for GraphQL

1.2.0

Spring module

2.1.2

MUnit plugin

3.7.1
## [](#considerations-for-mule-extension-developers)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)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/latest/mule-troubleshooting-plugin) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Engine 4.4.0 Release Notes Mule runtime engine (Mule) is a lightweight integration engine that runs Mule applications and supports domains and policies. ## [](#november-2025)November 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.8. See [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8). Patch release version: 4.4.0-20250919 - The operating system is updated to the latest security patches. There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2025)October 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues Patch release version: 4.4.0-20250919 This patch update addresses these Mule issues:
Description Issue

BufferOverFlowException errors no longer occur when inter-node communication gets stuck in clusters with encryption under heavy load.

W-16517561

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2025)September 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues Patch release version: 4.4.0-20250829 This patch update addresses the following Mule issues:
Description Issue

Performance degradation no longer occurs when using repeatable streaming.

W-19175330
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2025)July 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.5. See [Runtime Manager Agent 2.7.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-5). ### Fixed Issues Patch release version: 4.4.0-20250623 This patch update addresses the following Mule issues:
Description Issue

The com.google.code.gson:gson library is upgraded to v2.12.1.

W-17896347

The commons-beanutils:commons-beanutils library is upgraded to v1.11.0.

W-18687846

Schedulers are no longer triggered during graceful shutdown.

W-17981248

Repeatable streams now make data available before the buffer is full. To enable this behavior, set the system property mule.repeatableStreaming.bytes.eagerRead to true.

W-18716253
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Unicode characters now render correctly at the beginning of the string when using the DataWeave writer function with the onlyData flag enabled.

W-14855645

The Apache POI library is now upgraded.

W-18253747
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2025)June 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.4. See [Runtime Manager Agent 2.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-4). ### Fixed Issues Patch release version: 4.4.0-20250530 This patch update addresses the following Mule issues:
Description Issue

Spring Framework artifacts are replaced with vendor-supported equivalents to improve long-term compatibility.

W-18462316
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

A memory leak of the binding context no longer occurs when using the foreach scope.

W-18472194

DataWeave now correctly parses unquoted strings without raising a format error.

W-18118138
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2025)May 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.2. See [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2). ### Fixed Issues Patch release version: 4.4.0-20250423 This patch update addresses the following Mule issues:
Description Issue

org.apache.cxf:cxf-core is upgraded to 3.5.10.

W-18235963

licm is upgraded to 2.1.12.

W-18169698

Parallel For Each events no longer randomly timeout after a NullPointerException error.

W-17980769
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2025)April 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.2. See [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2). Enterprise Edition License: - The command `mule -verifyLicenseDetails [path_to_license]` that verifies the license before installing it is now added. See [Verify or Remove Enterprise Edition License](https://docs.mulesoft.com/on-premises/latest/installing-an-enterprise-license#verify-or-remove-enterprise-edition-license). ### Fixed Issues Patch release version: 4.4.0-20250403 This patch update addresses the following Mule issues:
Description Issue

You can now use the mule --verifyLicenseDetails [path-to-license.lic] command to verify a given license file.

W-17340620
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2025)March 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). Feature Flagging Mechanism: - Mule 4.4 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.4.0-20250217 This patch update addresses the following Mule issues:
Description Issue

Resources are now properly released after a timeout when using the Scatter-Gather or Parallel For Each routers. The mule.forkJoin.completeChildContextsOnTimeout feature flag is now added to enable this behavior.

W-16941297
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2025)February 2025 ### [](#patch-4-4-0-20250213)Patch 4.4.0-20250213 The February patch update 4.4.0-20250213 addresses a regression in the previous February patch update, 4.4.0-20250124, and includes the fixes in the patch. Patch release version: 4.4.0-20250213 This patch update addresses the following Mule issues:
Description Issue

ConfigurationException no longer occurs while performing Amazon DynamoDB Connector operations.

W-17801971
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20250124)Patch 4.4.0-20250124 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). ### Fixed Issues Patch release version: 4.4.0-20250124 This patch update addresses the following Mule issues:
Description Issue

A ClassCastException thrown when an error occurs within an on-error-continue component no longer prevents transactions from rolling back.

W-17430963

All transactions running within a global Error Handler are now committed as expected.

W-17431402

API metrics are now properly sent.

W-17529530
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2025)January 2025 ### [](#patch-4-4-0-20250116)Patch 4.4.0-20250116 - This patch update reverts the fixes for the following issue: W-17048606. ### [](#patch-4-4-0-20241210)Patch 4.4.0-20241210 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). ### Fixed Issues Patch release version: 4.4.0-20241210 This patch update addresses the following Mule issues:
Description Issue

Unnecessary internal blocking operations no longer occur when handling large streamed HTTP responses.

W-17048606

IllegalAccessException is no longer thrown during cache scope serialization with Kryo.

W-17089503
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2024)November 2024 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.6.6. See [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6). ### Fixed Issues Patch release version: 4.4.0-20241021 This patch update addresses the following Mule issues:
Description Issue

NullPointerException is no longer thrown when DataWeave transforms a RetryPolicyExhaustedException to a JSON format on a Java 17 runtime.

W-15643200

Web Service Consumer Connector and RosettaNet Connector no longer fail when there’s an HTTP TLS transport configuration.

W-16288302

A deadlock no longer occurs when consuming the payload in the completion callback of the HTTP client sendAsync method.

W-16640190

The commons-io:commons-io dependency is upgraded to 2.17.0.

W-16843119
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Apache POI folder used for temporal files is no longer deleted.

W-16899674
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2024)October 2024 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.6.6. See [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6). ### Fixed Issues Patch release version: 4.4.0-20241002 This patch update addresses the following Mule issues:
Description Issue

The configuration-properties encoding parameter is no longer ignored.

W-12228892

Spring Core is upgraded to 5.3.39.

W-16639433

Logging for the Analytics .db files cleanup is now improved.

W-16624763

nullPointerException now works as expected when the DefaultArchiveDeployer uses the SchedulerService injected.

W-16712841
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2024)September 2024 ### What’s New - `cxfVersion` is upgraded to 3.5.9. ### Fixed Issues Patch release version: 4.4.0-20240821 This patch update addresses the following Mule issues:
Description Issue

Debug logs for custom policies containing a custom extension/connector now work correctly.

W-15286605

cxfVersion is upgraded to 3.5.9.

W-16436783

Policies with minimum Mule version 4.4.0 now use the flow name as part of the artifact name, when the feature flag anypoint.platform.keep.default.policy.format=true is set.

W-16169887

NullPointerException is no longer thrown when API Gateway tries to dispose an empty cluster.

W-16540685

API Gateway pollers are no longer initialized when the API Gateway is started in offline mode.

W-16093885
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

DataWeave now preserves MimeType properties correctly.

W-16161736
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2024)August 2024 Patch release version: 4.4.0-20240724 This patch update addresses the following Mule issues:
Description Issue

Graal warning logs are now disabled.

W-15990399

Loaded native libraries are now copied into a separate temporary folder to avoid issues while redeploying applications in Windows OS.

W-15894519

Parameter resolution error handling is no longer affected when the parameterized operation is inside a dynamically referenced subflow.

W-15923581

The OAuth token invalidation status is now communicated to other nodes in a cluster when a token is invalidated on one node.

W-15154658

Flows now honour the state configured in flows.deployment.properties when restarting the app, regardless of the initial state. To enable this feature, use the mule.honour.persisted.flow.state system property. This only applies to Standalone and Hybrid deployments.

W-15750334

API Gateway initialization no longer fails if quorum isn’t reached in cluster mode.

W-15951155

Hard timeout for platform requests is now available by setting up the anypoint.platform.request_timeout in milliseconds.

W-16141554

A serializationId change no longer causes rolling updates to fail when in cluster mode.

W-16035332
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2024)July 2024 Patch release version: 4.4.0-20240619 This patch update addresses the following Mule issues:
Description Issue

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws groovy.lang.MissingMethodException exception.

W-15750766

Batch job instance queue store files are removed after completion.

W-15546969

Cache scope with multiple computations no longer occurs if events arrive concurrently for an absent key.

W-14604517

Tanuki wrapper configuration is now enabled for AArch64.

W-15839796

MDC context is reset after the XML SDK operation is executed.

W-15206528

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas.

W-15769926

Logging for Gateway Analytics initialization is now improved.

W-15904845

Handling of connection errors with API platform is now improved.

W-15809377

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert.

W-15427352
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

The Flat File module now adds the substituteCharacterAsMissingValue reader property.

W-15571377

The Flat File module now adds the fillRedefinesByMaxLength writer property.

W-15973636
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2024)June 2024 Patch release version: 4.4.0-20240520 This patch update addresses the following Mule issues:
Description Issue

jackson-databind is upgraded to 2.15.4.

W-15633480

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

Resiliency is now improved on policy application and updates.

W-15426519
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

The Excel writer now generates XLSX files using ZIP specification 2.0.

W-15534640
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2024)May 2024 Patch release version: 4.4.0-20240424 This patch update addresses the following Mule issues:
Description Issue

Apache CXF is upgraded to version 3.5.8.

W-15450362

Client, policy, and API names are now shown when logging Analytics Events.

W-15294568
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Internal libraries are now upgraded.

W-15296551
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2024)April 2024 Patch release version: 4.4.0-20240408 This patch update addresses the following Mule issues:
Description Issue

Spring is upgraded to 5.3.33.

W-15260752

Using vc:minVersion="1.1" in XSD schema no longer throws NullPointerException in XML SDK connectors.

W-15081363

MUnit tests using tracing module and "Set logging variable" now work as expected.

W-14773408

Template parser validation is now improved.

W-15141905
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

The Excel reader no longer reads furigana characters.

W-14991276

Coercion of the third parameter on the ternary function executor now works as expected.

W-15061008
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2024)March 2024 Patch release version: 4.4.0-20240219 This patch update addresses the following Mule issues:
Description Issue

Performance is now improved for certain For Each scenarios.

W-14678431

HTTP Request Connector no longer throws Connection limit exceeded, cannot process request when maxConnections is set to 1.

W-14686211

Disabling the enableNotifications flag on the On Error Continue component now works as expected.

W-14954677

Multi-step batch jobs can now be correctly resumed and finished after being stopped.

W-14726677

Transactions' timeout is now honored. When a transaction times out, it is rolled back, and an error is thrown that can be handled with error handling. To enable this, activate the mule.tx.error.when.timeout feature flag.

W-14128870
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2024)February 2024 ### [](#patch-4-4-0-20240215)Patch 4.4.0-20240215 - This patch update reverts the fixes for the following issue: W-14809031. DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Performance is now improved when coercing addition and subtraction operations.

W-14927555
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20240122)Patch 4.4.0-20240122 Patch release version: 4.4.0-20240122 This patch update addresses the following Mule issues:
Description Issue

Analytics Events and Policy Violations logging are now enabled.

W-14237017

Unapplied policy template deletion on startup is now enabled.

W-14407626

Native library dependencies are correctly loaded.

W-14497761

Fixed a leak when using expressions in parameters in OAuth Client Credentials configurations in connectors.

W-14391247

Timeout is now honored for local transactions.

W-14809031

An extra message field is now added when logging a message variable.

W-14723809

Timeout is now considered for local transactions and rollbacks are silently executed.

W-14608096

An extra message field is no longer added in the logs when logging the message variable.

W-14457630
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Caching now works correctly when coercing for addition and subtraction operations.

W-14591653

do scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.

W-14514837
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2024)January 2024 ### [](#patch-4-4-0-20240118)Patch 4.4.0-20240118 Patch release version: 4.4.0-20240118 This patch update addresses the following Mule issues:
Description Issue

This patch update reverts the fix.

W-14404918
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20231211)Patch 4.4.0-20231211 Patch release version: 4.4.0-20231211 This patch update addresses the following Mule issues:
Description Issue

Hazelcast is upgraded to 5.2.4.

W-14404918

An issue with explicit socket connection timeout for socket creation with the management plane was fixed.

W-14555248

XML SDK no longer fails to replace a complex parameter with a property value.

W-13681772

The nonProxyHosts setting now works correctly for HTTP Connector.

W-14161865
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2023)November 2023 ### [](#patch-4-4-0-20231110)Patch 4.4.0-20231110 The November patch update 4.4.0-20231110 addresses a regression in the previous November patch update, 4.4.0-20231026, and includes the fixes in the patch. Patch release version: 4.4.0-20231110 This patch update addresses the following Mule issues:
Description Issue

This patch update reverts the fix.

W-13681772
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20231026)Patch 4.4.0-20231026 Patch release version: 4.4.0-20231026 This patch update addresses the following Mule issues:
Description Issue

The org.bouncycastle.bcprov-jdk15on library is upgraded to 1.74.

W-14351263, W-14347982

The org.json.json library is upgraded to 20231013.

W-14347983

The org.apache.santuario.xmlsec library is upgraded to 2.3.4.

W-14347980

The Error Handler with attribute logException=false no longer logs the exception when using the Scheduler component.

W-13881167

Multiple redeployments of applications linked to a domain project sharing IBM MQ Connector now works as expected.

W-12388528

The Element DSL is now available in the exceptionPayload attribute.

W-14067135

XML SDK no longer fails to replace a complex parameter with a property value.

W-13681772
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

The cached function coercion now works correctly for a second time when an argument is constant.

W-13763138

The DataWeave sum function with a single numeric string arg now returns Number type instead of String.

W-14086694

Reading Avro schema with an array of enum type items no longer returns an error.

W-14252745

Inconsistent XML encoding detection no longer occurs between indexed and in-memory parsers.

W-13805995
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2023)October 2023 Patch release version: 4.4.0-20230918 This patch update addresses the following Mule issues:
Description Issue

OAuth token no longer fails to refresh leaving the source in an inconsistent state.

W-14029065

Parse Template no longer obtains a different output between 4.3.0 to 4.4.0.

W-13588449

Race conditions no longer occur in the Until Successful component when two until-successful elements are executed sequentially.

W-13858445

Log4j is upgraded to 2.20.0.

W-13792545

A memory leak in HTTP Service no longer occurs after a redirection.

W-13754230
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

System property com.mulesoft.dw.xml_writer.declareXmlNamespace has been included to manage adding implicit namespaces like xml in the XML writer.

W-11965399

Temporary files are now closed for inputs bigger than 1.5 MB.

W-13868202

Milliseconds information is now preserved when converting the java.util.Date type.

W-14002706
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2023)September 2023 Patch release version: 4.4.0-20230822 This patch update addresses the following Mule issues:
Description Issue

BouncyCastle is upgraded to version 1.7.

W-13701827

The 'Expect: 100-Continue' header is now ignored in server responses and log warnings.

W-13806048
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

An invalid UUID logical type in Avro module now throws an exception as expected.

W-13943112
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2023)August 2023 Patch release version: 4.4.0-20230724 This patch update addresses the following Mule issues:
Description Issue

Guava is upgraded to version 32.1.1-jre.

W-13701825
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2023)July 2023 Patch release version: 4.4.0-20230616 This patch update addresses the following Mule issues:
Description Issue

Kryo is upgraded to version to 4.0.3.

W-13498807

Context has been added to prevent policies' variables from being overridden in parallel scenarios.

W-13509911

Spring is upgraded to version 5.3.27.

W-13206644

Undeploying/redeploying multiple operation policies to the same non-blocking operations no longer fails when processing new events.

W-13563214

The POST request body is no longer sent in a GET redirect.

W-12594415

The java.lang.NullPointerException error no longer appears while refreshing an OAuth token.

W-12975498

OutOfMemoryError no longer appears when Mule applications are redeployed with Mule scripting and Groovy.

W-13038823

JCommander is upgraded to version 1.78.

W-13206643

java.lang.NullPointerException no longer appears when you create a user-defined metadata type.

W-13049851
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Multipart reader performance is enhanced by using the proper input stream implementation.

W-13099773
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2023)June 2023 Patch release version: 4.4.0-20230522 This patch update addresses the following Mule issues:
Description Issue

snakeyaml is upgraded to version 2.0.

W-12354025

jackson-core is upgraded to version 2.15.

W-13014584

StackOverflowError no longer occurs when processing a large map in a batch job.

W-13123339
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Streaming support now works correctly for JSON.

W-11790958
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2023)May 2023 Patch release version: 4.4.0-20230417 This patch update addresses the following Mule issues:
Description Issue

Upgraded org.json:json from 20220924 to 20230227.

W-13012142

Added support for native library dependencies at Mule applications and domains.

W-11855052

Added a new method for CoreServiceClient.

W-12659177

This release displays the policy definition version.

W-12733032
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Closing resources immediately after reading when using text/plain MIME type.

W-12398584

Incorrect trimming of whitespaces no longer occurs when reading XML content.

W-12528980

Fixed splitBy management of large strings so String and Regex options are consistent with each other.

W-12452407
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2023)April 2023 Patch release version: 4.4.0-20230320 This patch update addresses the following Mule issues:
Description Issue

Kryo Serializer now discards the microseconds value from a timestamp during the serialize and deserialize operation.

W-12516135

Second Scatter Gather router does not execute when it has a Try scope for each component that raises an error handler within.

W-10619784

First Successful router hangs with raise-error.

W-12552091

Batch Job no longer shuffles CSV column order in Mule 4.4.

W-12505969

Added Exception reached PS subscriber for error handler error on February 7, 2023 patch.

W-12535932

NullPointerException no longer occurs when adding a null value to the cookie header.

W-12666590

Added Groovy to the default allowed scripting languages for logging.

W-12708905

Scripts in logging configuration files are no longer supported by default.

W-12556954

This release fixes deadlock when redeploying with policies.

W-12622899
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Added cache Java values evaluation to avoid consuming streams more than once.

W-12635909
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2023)March 2023 The March patch update 4.4.0-20230313 addresses a regression in the previous March patch update, 4.4.0-20230217, and includes the fixes in that patch. ### [](#patch-4-4-0-20230313)Patch 4.4.0-20230313 Patch release version: 4.4.0-20230313 This patch update addresses the following Mule issue:
Description Issue

This patch update reverts the fix.

W-12161504
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20230217)Patch 4.4.0-20230217 Patch release version: 4.4.0-20230217 This patch update addresses the following Mule issues:
Description Issue

This release improves the behavior of chained subflows and XA Transactions that can lead to an application deadlock.

W-12128703

This release improves the handling of JDBC resources to prevent memory leaks on the redeployment of apps.

W-12460123

The with-correlation-id scope no longer modifies errors thrown by other components.

W-12439048

XML SDK modules now work as expected when using a raise-error inside of a subflow, which prevents an InitialisationException.

W-12377294

Log4j scripting now supports Nashorn languages by default.

W-12549148

Requests no longer fail with NullPointerException: value with applications referencing a global Error Handler.

W-12535932

The loggingVariables in batch job serialization now works as expected when upgrading Mule runtime version.

W-12411873

This release updates snakeyaml to version 1.33.

W-12429030

This release upgrades org.raml:raml-parser-2 to version 1.0.51.

W-11577522

This release updates org.json:json to version 20220924.

W-12450128

The log level for HTTP response stream was closed before being read but response streams must always be consumed was changed from WARNING to ERROR.

W-12245298

Cookie headers are now correctly aggregated during the redirect mechanism.

W-12161504

Requests no longer fail with NullPointerException with applications using invalid cookies.

W-12528819
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Fixed IndexOutOfBoundsException that occurred when combining the usage of heap memory for internal buffering with a customized buffer size.

W-12247447
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2023)February 2023 The February patch update 4.4.0-20230223 addresses a regression in the previous February patch update, 4.4.0-20230123, and includes the fixes in that patch. ### [](#patch-4-4-0-20230223)Patch 4.4.0-20230223 Patch release version: 4.4.0-20230223 - This patch update reverts the fixes for the following issues: W-12245298 and W-12161504. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20230123)Patch 4.4.0-20230123 Patch release version: 4.4.0-20230123 This patch update addresses the following Mule issues:
Description Issue

Applications with an XML SDK connector now deploy correctly.

W-12362157

Concurrency errors no longer occur when a flow is called multiple times using the lookup function.

W-12206167

The Error Handler now returns the Event Id and Processor as expected.

W-12245760

This release upgrades the log4j dependency to version 2.19.

W-12353440

This release upgrades the com.hazelcast:hazelcast dependency to version 3.12.13.

W-12354026

This release upgrades the Jackson Databind library to version 2.13.4.2.

W-12219126

This release upgrades the org.apache.cxf:cxf-core dependency to version 3.5.5.

W-12354008

Cookie headers are now correctly aggregated during the redirect mechanism.

W-12161504

The log level for HTTP response stream was closed before being read but response streams must always be consumed was changed from WARNING to ERROR.

W-12245298

CloudHub applications no longer fail when using Global Error Handlers with a default configuration.

W-12218381

The insecure connection configuration in the TLS Configuration truststore now works as expected.

W-10822938

HTTP API status code 422 now shows the correct reason phrase.

W-12293483

WSC connector with an HTTP Requester configuration no longer fails when using a domain project.

W-12129696

The Error Handler now returns the Event Id and Processor as expected.

W-11983138

Flow reference validations no longer fail when using XML SDK components that declare inner sub-flows during lazy initialization.

W-11681056
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

dw::core::Dates::atBeginningOfWeek now works correctly when the input DateTime is Sunday.

W-11940166

The new com.mulesoft.dw.javaSqlDateToDate system property enables mapping java.sql.Date to Date instead of DateTime.

W-12043162

The Resource already closed exception no longer occurs when using the write function with a value bigger than 1.5MB with Avro format.

W-12067821

Cacheable overloaded functions, such as then, now dispatch to the correct function definition when called multiple times.

W-12073562

The default behavior now works correctly when having a null value coming from the Mule runtime.

W-12166609

High memory usage no longer occurs when using the dw::core::Arrays::divideBy function with an in-memory Array as input.

W-12167313
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2023)January 2023 The January patch update 4.4.0-20230111 addresses a regression in the previous January patch update, 4.4.0-20230102, and includes the fixes in that patch. ### [](#patch-4-4-0-20230111)Patch 4.4.0-20230111 Patch release version: 4.4.0-20230111 This patch update addresses the following Mule issue:
Description Issue

Change mule.enable.byteBuddy.objectCreation default value to false. If set to true, it will prevent race conditions during parallel deployments.

W-11920598
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20230102)Patch 4.4.0-20230102 Patch release version: 4.4.0-20230102 This patch update addresses the following Mule issues:
Description Issue

Race conditions, which can make deployments fail, no longer occur when running parallel deployments.

W-11920598

The Scatter-Gather router no longer throws the exception UnsupportedOperationException when variables are set by Db::prepareArray or Db::prepareStruct.

W-11932094

Distributed locks are now released properly when a policy is disabled.

W-11929632

The error Can’t perform operation on 'Object_store'. ObjectStore not initialized no longer occurs when a redelivery policy that points to an object store is declared as a top level element.

W-11985583

An issue that prevented access to the SecureContext of a policy inside of a Batch component no longer occurs.

W-11493901

Setting a variable with a null value inside a Batch Aggregator component no longer fails with a NullPointerException.

W-11825409

The use of HTTP Insecure mode in a connector no longer fails with a NullPointerException.

W-12049036

Authorization of the OAuth dance no longer hangs when a custom object store uses a Redis cache.

W-11410770

The Idempotent Validation filter now cascades object store exceptions. Using the filter on Mule version 4.4 or earlier requires the property mule.rethrowExceptionsInIdempotentMessageValidator=true.

W-11529823

The XML SDK’s implicit configuration creation is disabled by default.

W-12113550

A fix to IllegalArgumentException handling prevents events from getting stuck in a For Each scope when an expression evaluates to a Map.

W-12234425

This release upgrades JSON to version 20220924.

W-11834878

This release upgrades the Tanuki wrapper version to 3.5.51.

W-12068528

In API Gateway, SLA deletion no longer generates an inconsistent contract status.

W-11898295
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The function dw::core::Dates::atBeginningOfHour now works as expected when an hour is represented as a single digit.

W-11620156

Escaped quote characters now work as expected in CSV Module.

W-12128349

The FlatFile module now provides a reader property, retainEmptyStringFieldsOnParsing, for handling fields that lack values. When set to true, this property makes the reader retain these fields and set their values to an empty string. The default behavior of the reader is to remove those fields.

W-12036336

Data payloads without line breaks no longer work when using lenient as the recordParsing property. The other options to recordParsing support records that lack line breaks. noTerminator is preferred for fixed-length records that lack a line break.

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

November patch update 4.4.0-20221111 addresses a regression in the previous November patch update, 4.4.0-20221026, and includes the fixes in that patch.
### [](#patch-4-4-0-20221111)Patch 4.4.0-20221111 Patch release version: 4.4.0-20221111 This patch update addresses the following Mule issues:
Issue Resolution ID

Using the insecure="true" attribute of the trust-store no longer throws NullPointerException.

W-12049036
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-4-0-20221026)Patch 4.4.0-20221026 Patch release version: 4.4.0-20221026 This patch update addresses the following Mule issues:
Issue Resolution ID

Flow executions containing a First Successful and a Raise Error no longer stop responding.

W-10619792

The insecure="true" attribute of the trust-store config is now honored when additional properties are defined. Use the system property mule.honour.insecure.tls.configuration=true to apply this behavior in Mule 4.4 or earlier.

W-10822938

Applications that depend on a domain to load resources no longer fail with a "Couldn’t find resource: neither on classpath or in file system" error.

W-11625237

Error mapping is no longer executed when an error occurs inside of an operation policy.

W-11861168

Applications with global functions no longer fail on startup with a ClassCastException error.

W-11603893

Transactions now honor the Transaction Timeout configured in the Try scope.

W-11741912

To avoid XML SDK implicit configuration creation, this release adds the system property mule.disableXmlSdkImplicitConfigurationCreation=true.

W-10634129
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

onNull functions now work as expected.

W-11865849

Instead of returning an empty array in some scenarios, iterating flat file arrays now work as expected.

W-11932440
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2022)October 2022 Patch release version: 4.4.0-20220922 This patch update addresses the following Mule issues:
Description Issue

Improved memory consumption when using a global error handler.

W-11503016

HTTP connections no longer have a leak that prevents new connections from opening.

W-11622837

TransactionTimeout is now set correctly on XA Transactions, preventing stale connections.

W-11741912

Improved the compatibility of Microsoft SQL Server when using XA Transactions with Bitronix.

W-11228596

Improved the performance of the execution of source events.

W-11676440

This release adds a feature flag that disables the error suppression feature. Error suppression prevents components such as the Web Service Consumer connector and the Until Successful scope from reporting errors outside their namespaces. Use the system property mule.suppress.mule.exceptions=false to apply this change.

W-11308645

The "Listener successfully reconnected" message no longer appears when the application starts.

W-10983306

HTTP wire logging now provides the complete context of the request and response for 413 and 414 scenarios.

W-11410315
There is no DataWeave update for this version this month. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2022)September 2022 Patch release version: 4.4.0-20220824 This patch update addresses the following Mule issues:
Description Issue

Applications using the latest Open JDK 11 version no longer produce invalid JVM vendor errors.

W-11265408

Tanuki wrapper upgraded from 3.5.45 to 3.5.50 to support M1 (ARM) architecture.

W-11242363

Applications no longer fail to start with a Prefix URI must be not blank error.

W-11627710
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

Visual Studio Code extension no longer breaks with binary input format in the test scenario inputs directory.

W-11507190

Namespace is now added on elements when previously used at a deeper structure level.

W-11349764
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2022)August 2022 Patch release version: 4.4.0-20220722 This patch update addresses the following Mule issues:
Description Issue

Global Error Handler configurations no longer roll back transactions that are not supposed to roll back.

W-11324527

CXF is upgraded to version 3.5.1.

W-11267666

Mule no longer duplicates lifecycle phases for global Error Handler configurations.

W-11117613

Error mapping now works while deploying a custom Header Injection policy.

W-11147961

Different ModuleException constructors now produce the same output messages.

W-11192984

Mule runtime no longer produces the following warning: "An expression value was given for parameter 'variableName' but it doesn’t support expressions".

W-10998630

Incorrect logs no longer appear for polling sources.

W-11398537

Caching issues no longer cause a policy to use data from the wrong operation and produce Element and Element DSL mismatches with the flow stack.

W-11403067

A memory leak no longer occurs when using JMS Connector with ActiveMQ.

W-10583584

Mule SDK now supports a List of java.math.BigDecimal/BigInteger parameters.

W-11348869

Log levels for successful source reconnections are now set to INFO.

W-11437305

The caching strategy no longer applies the lifecycle phases to the Object Store when it is defined in the domain.

W-11203794

HTTP_Request_configuration in Anypoint Connector for HTTP now honors proxy settings.

W-10863931
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. This patch release addresses the following DataWeave issues:
Description Issue

The message for the StackOverflow script compilation error is no longer hidden.

W-11215958
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2022)July 2022 Patch release version: 4.4.0-20220622 This patch update addresses the following Mule issues:
Description Issue

MUnit tests no longer fail when referencing the mule.home reserved property within the application on Windows OS.

W-11193698

Spring upgraded from 5.3.18 to 5.3.21.

W-11300535

Jackson upgraded to 2.13.3.

W-11139348

MuleArtifactAstCopyUtils no longer leaves mutable collections in generated artifacts or components.

W-11208606

AbstractForkJoinRouter-based processors, such as Parallel For Each and Scatter-Gather routers, can now show detailed error information for their failed routes. Use the system property mule.detailedCompositeRoutingExceptionLog=true to apply this change.

W-10965130

When using an XML SDK component that declares inner flows, flow-ref validation no longer fails with a flow "does not exist" error message during lazy initialization deployment.

W-11267062

Applications connected to the API Gateway no longer receive maximum concurrency reached errors.

W-10917220
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The July patch release addresses the following DataWeave issues:
Description Issue

Writing binary values with the JSON writer no longer outputs the base of the values.

W-11326859

This release fixes Avro property handling.

W-11324418

This release improves handling of streams that do not declare a size.

W-11277575

Fix write function so Avro format can be handled.

W-11047202

This release improves handling of string values in XML format.

W-11273037
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2022)June 2022 Patch release version: 4.4.0-20220523 This patch update addresses the following Mule issues:
Description Issue

Mule no longer fails with error DefaultFeatureFlaggingService after applying the 2022 May patch.

W-11172835

File attributes are no longer removed when using Parallel For Each.

W-10848628

FIPS enabled Mule Clusters no longer throw a java.nio.BufferUnderflowException warning when using the RetrieveAll operation on an Object Store.

W-10884325

ValueProvider parameters validations now work properly when combined with TypeResolver annotations.

W-10634121

Updated the error message shown when a Batch component cannot queue records.

W-11086577

Added logging to AbstractQueueStoreDelegate to describe why a record was not successfully queued.

W-11086587

The AS400 connector now properly receives a JSON response instead of org.mule.runtime.core.internal.util.message.stream.UnclosableCursorStream.

W-11093225

Mule now raises an ExceptionNotification error when ExtensionMessageSource fails to start.

W-10619908

Deserializing older SDK models no longer causes a NullPointerException error.

W-10815920

Polling frequency now works correctly when using the value 60000, which was previously incorrectly interpreted to poll every 1 second rather than every 1 minute.

W-10682121

XML SDK modules now properly access configurations defined at the domain level.

W-10719167

Upgraded Spring dependency from 5.1.20 to 5.3.18.

W-10989650

Mule applications no longer crash due to an unhandled IllegalStateException error when processing a batch block.

W-10742153

Mule now fails as expected if the event source configuration for the application is incorrect.

W-10619908

Mule application deployment properties are no longer lost after domain redeployment.

W-10984029

A memory leak no longer occurs after redeploying multiple times an application that uses the IBM MQ connector.

W-10672197

Mule now supports deploying applications that define a listener-config name based on an application property.

W-10923083

Connector parameters are now received properly instead of being null.

W-10920842
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The June patch release addresses the following DataWeave issues:
Description Issue

DataWeave now parses Java objects without errors.

W-10832766

The text/plain reader now correctly ignores the byte order mark (BOM). The JSON writer now uses the encoding information available in Binary values when writing them as String values instead of using the writer configuration encoding. To restore the previous behavior, enable the system property com.mulesoft.dw.decode_binaries_with_writer_encoding.

W-10696255

Multiline string indentation on YAML now works correctly.

W-10955882

The FlatFile module now includes the allowLenientWithBinaryNotEndElement property to support existing behavior.

W-10935528

Fixed ClassCastException in multipart module.

W-10943884

DataWeave now shows a descriptive error when there is an unsupported output mime type.

W-10876534

The indexed XML reader no longer adds unnecessary text fields to XML objects.

W-10942171
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2022)April 2022 Patch release version: 4.4.0-20220321 This patch update addresses the following Mule issues:
Description Issue

Race conditions no longer occur when running parallel deployments.

W-10672687/SE-23764

Custom connector POST requests no longer send the body as NULL when handling empty payloads.

W-10818822

The redirect implementation properly handles the "Preserve Header Case" configuration.

W-10822777
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2022)March 2022 Patch release version: 4.4.0-20220221 This patch update addresses the following Mule issues:
Description Issue

A direct memory error no longer occurs when the com.mulesoft.dw.directbuffer.disable system property is enabled.

SE-24186

Set-Cookie is now handled correctly after a redirect request.

W-10667387 / MULE-19942

Properties now resolve correctly for document attributes of the AST metadata.

W-10673280 / MULE-20090

Metadata type is no longer missing from the definition when present in the schema.

W-10674401 / SDK-48

When disposing of an application, Mule no longer throws an IOException error indicating that the underlying JAR file is in use.

W-10674436 / W-10674454 / SE-23775

After a failed HTTP request, applications no longer stop when reading the error payload in the error handler.

W-10681464 / MULE-19537

The warning Illegal reflective access by EfficientReflectionHashCode no longer occurs due to starting Mule when using JDK 11.

W-10730677 / EE-7990

LifecycleObjectSorter and dependency resolvers implemented in this release reduce application deployment time.

W-10745620 / W-10746222 / MULE-19984

Thread-local interference no longer occurs when a task is scheduled for execution on the same thread due to thread-pool exhaustion. One possible symptom was a transaction not being properly cleaned up under heavy load, followed by nested transaction errors.

W-10619599 / MULE-20072 / SE-24241
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The March patch release addresses the following DataWeave issues:
Description Issue

A direct memory error no longer occurs when the com.mulesoft.dw.directbuffer.disable system property is enabled.

SE-24186

Duplicate declarations for namespace prefixes in XML no longer occur.

W-10648792 / DW-1081

Exceptions are no longer thrown due to use of the default operator with fromBase64.

W-10648825 / SE-23812

Avro unions with enums are now supported.

W-10706991
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2022)February 2022 Patch release version: 4.4.0-20220124 This patch update addresses the following Mule issues:
Description Issue

Anypoint Connector for Box (Box Connector) no longer fails to recreate the input stream after an access token refresh, preventing a stream closed issue.

MULE-20001/SE-23666

A concurrent connection limitation in Anypoint Connector for NetSuite (NetSuite Connector) no longer occurs.

MULE-19937/SE-22359

The readiness check performed when deploying on Runtime Fabric is now processed correctly.

AGENT-466/SE-22948/SE-22585

Running multiple MUnit cases together no longer causes a No bean named '_muleDefaultObjectSerializer' available error.

MULE-20012/SE-23407

Anypoint Connector for Google Calendar (Google Calendar Connector) no longer overwrites the access_token, which prevents generating incorrect results.

MULE-20019/SE-23584

You can now use static values in a flow reference processor.

MULE-19987/SE-23634

Mule no longer performs a thread switch in a transactional context that uses multithread and the same cache-key.

EE-8216/SE-23816

Using a custom connector that includes enum types no longer prevents applications from deploying successfully.

MULE-19976/SE-24012

Mule no longer returns an incorrect CONNECTIVITY error type when a ConnectionException is thrown when using the Java SDK.

MULE-19895/SE-24091

Deploying a Mule application with unpaired namespaceUri in schemaLocations no longer causes an ArrayIndexOutOfBoundsException error.

MULE-20035/SE-24099

Global property values of a module are now accessible within a private operation invoked within a flow control component.

MULE-19962/MULE-19035/SE-22282
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The February patch release addresses the following DataWeave issues:
Description Issue

An endless loop issue no longer occurs when writing a CSV file with bufferSize=0.

DW-1074

Creating sample files using the binary type no longer causes an error.

DW-390

Corrected the documentation of the`Periods::between` function.

DW-1070

Upgraded some dependencies, including avro and jackson, and removed unused AWS dependencies (#1673).

DW-1080

Upgraded the edi-parser with SLF4J.

CONN-9598

Performing transformations from avro to other formats no longer causes an exception when the enum type field is present.

SE-23802
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2022)January 2022 Patch release version: 4.4.0-20211227 This patch update addresses the following Mule issues:
Description Issue

MUnit tests no longer fail after migration from Mule 4.2.1 to Mule 4.3.0 or higher versions.

MULE-19866/SE-21030

This release adds the mule.errorTypes.lax feature. When enabled, error types are enforced.

MULE-19879/SE-23207

MUnit no longer hangs as references to Spring schemas in the Mule XSD schema are removed.

MULE-19904/SE-23247

Applications that implement a VM Listener no longer raise java.lang.IllegalStateException: No connection has been bound errors and quit.

SE-22172

Application deployment no longer fails with Task [App].wsc-dispatcher rejected from Scheduler errors.

SE-22851

A null pointer exception error on ObjectBeanDefinitionCreator.processMuleProperties that prevented app deployment no longer occurs.

MULE-19886

FlowProcessMediator no longer leaks the payload of the first request.

MULE-19869

Mule no longer raises exception errors for a custom connector developed with Mule SDK for Java.

MULE-19936/SE-23408

If the redelivery policy is exhausted in a source configured with transactions, Mule no longer raises an error that runs in a loop.

MULE-19915

Processors in subflows now get the processing strategy of the root flow.

MULE-19924

Autogenerated Mule connectors no longer fail with NumberFormatException errors.

MULE-19871/SE-21463

You can now redeploy applications that were in a stopped state when they were deleted.

MULE-19890/SE-22261

DataWeave now escapes the \ symbol when used in combination with the " symbol.

MULE-19900/SE-22346

The batch processing On Complete phase no longer fails if it encounters an error stream.

EE-8020/SE-22386

Logs no longer show reconnection successful messages when reconnection attempts to the FTP server are exhausted because the server is unavailable.

SE-22434

Transactions opened by the JMS Listener are no longer rolled back.

MULE-19919/SE-23039

You can now perform parallel deployments of apps that are linked to a domain and share a configuration.

MULE-19912/SE-23123

Mule now recognizes Eclipse Temurin by Adoptium (formerly Adopt OpenJDK project) as a recommended JDK Vendor and no longer raises an INFO-level log message.

MULE-19917/SE-23354

Apache Commons Compress upgraded to version 1.21.

EE-8088

GSON upgraded to version 2.8.9.

EE-8154

Kryo updated to version 4.0.2.

EE-8153

Apache Velocity updated.

EE-8010

The JMS Connector no longer leaks connections and now honors connection pools in XA mode with Solace JMS.

MULE-19848/SE-2228

MUnit no longer fails with a RejectedExecutionException error.

SE-22728

Scheduler runs using cron expressions are no longer rejected if other scheduler components are under back pressure.

SE-22941

This releases fixes an issue that caused a No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available error.

MULE-19896/SE-23142

An issue that caused a No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available error no longer occurs.

MULE-19896/SE-23142

The JMS Connector no longer leaks connections and now honors connection pools in XA mode with Solace JMS.

MULE-19848/SE-22284

HTTP requests with 100-continue are now processed as expected.

MULE-19884/SE-22637
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The January patch release addresses the following DataWeave issues:
Description Issue

Flow retyping inside dynamic functions now works as expected.

DW-677

DataWeave no longer incorrectly sets autostreaming.

DW-918

The UnsupportedTypeCoercionToLiteralException error is now caught when using the similar operator (~=).

DW-932

JSON streaming now works correctly.

DW-940

The AttributeDelegate function no longer causes a stack overflow error.

SE-23494

Removing objects by property name now works as expected.

SE-23444

When using arrays, the XML writer properly keeps namespaces.

SE-23299

DataWeave now correctly parses large strings in JSON transformations.

SE-23291

A Scatter Gather issue that caused DataWeave to throw the ArrayIndexOutOfBoundsException error no longer occurs.

SE-22431

Comparison operators for dateTime type now work as intended.

SE-22025

Local variable resolution now works as expected.

SE-21847

Avoid closing resources prematurely when using the write function, which affects MUnit tests.

SE-23483

Fix OutOfMemory error using writeLinesWith function, which affected the ndjson module.

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

November patch update 4.4.0-20211104 addresses a regression in the previous November patch update, 4.4.0-20211026, and includes the fixes in that patch.

  • If you installed the previous November patch, 4.4.0-20211026, install patch 4.4.0-20211104 to address the regression.

  • If you did not install the previous November patch, 4.4.0-20211026, skip that patch, and install the new patch, 4.4.0-0211104.
### [](#patch-4-4-0-20211104)Patch 4.4.0-20211104 Patch release version: 4.4.0-20211104 This November update addresses a regression introduced in the previous November patch, 4.4.0-20211026:
Description Issue

QueryParams are no longer lost when HTTP redirects take place.

MULE-19811

Addressed a regression in the initial November patch update.

SE-23349
### [](#patch-4-4-0-20211026)Patch 4.4.0-20211026 Patch release version: 4.4.0-20211026

Skip this patch, and install a later patch. Fixes in this patch are included in later patches.
This November update addresses the following Mule issues:
Description Issue

Fixed NullPointerException handling when serializing or transforming Mule errors from the Until Successful component.

MULE-19811

Added missing copyStrategy elements to caching strategy the extension model.

EE-8112

The CachedConnectionProvider no longer returns the same connection to a source if sourceCallback.onConnectionException(e) is called.

MULE-19678

An issue with nesting referenced Flow Reference components no longer occurs.

MULE-19831/SE-22539

Fixed a memory leak in org.mule.runtime.core.internal.rx.FluxSinkRecorder.

MULE-19846/SE-22780

Applications now start correctly after the September patch update is applied.

MULE-19815/SE-22845

Fixed an issue with adding Anypoint Connector for Snowflake (Snowflake Connector) to Studio.

SE-23107

Fixed a scheduling mechanism issue in Anypoint MQ that appeared when the Subscriber operation used the Polling type.

MULE-19843/SE-23031

Fixed an invalid configuration error in custom connectors built with the XML SDK.

MULE-19858/SE-23113

Fixed a memory leak in FlowProcessMediator.

SE-22773

Fixed intermittent No listener errors during Studio deployments or flow restarts.

MULE-19533/SE-21576/SE-20958

Mule now handles concurrent requests correctly when a Mule application makes an HTTP request that returns a 301 redirect.

SE-22922/SE-19944
DataWeave 2.4.0 is bundled with the Mule 4.4.0 release. The November patch release addresses the following DataWeave issues:
Description Issue

Fixed a ClassCastException that occurred in the Avro module by correcting its generated MIME type.

SE-21869

Comments within YAML files processed in Mule applications are no longer erased.

DW-706

You can now disable the removal of self-referencing implicit variables.

DW-893

DataWeave now allows mixed content structures (text and nodes) when reading and writing XML content.

SE-21464

Functions in the Dates module now accept one-digit numbers for months and days.

DW-894

Improved the performance of splitting functionality.

DW-776

Improved the performance of the JSON module.

DW-706
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-5-2021)October 5, 2021 ## What’s New Mule 4.4.0 includes important enhancements and fixes. ### [](#enhancements)Enhancements - Correlation ID Management Mule 4.4 enables you to modify the correlation ID associated with a Mule event. You can also change the algorithm Mule uses to generate each correlation ID. See [Correlation ID](https://docs.mulesoft.com/mule-runtime/latest/correlation-id) for additional information and configuration instructions. - Improved Logging Capabilities Mule 4.4 incorporates the Mule Tracing module, which you can use to add, remove, and clear variables from the logging context for a given Mule event. See [MDC Logging](https://docs.mulesoft.com/mule-runtime/latest/logging-mdc) for additional information and configuration instructions. - Feature Flagging Mechanism Mule 4.4 incorporates a feature flagging mechanism, which enables you to disable certain features that change core functionality in Mule to avoid backward compatibility issues. The following are the feature flags introduced in this release and its corresponding fixed issue ID:
Feature Flag Issue ID

HONOUR_RESERVED_PROPERTIES_PROPERTY

MULE-17659

HANDLE_SPLITTER_EXCEPTION_PROPERTY

DW-383

BATCH_FIXED_AGGREGATOR_TRANSACTION_RECORD_BUFFER_PROPERTY

MULE-19218

COMPUTE_CONNECTION_ERRORS_IN_STATS_PROPERTY

MULE-19020

TO_STRING_TRANSFORMER_TRANSFORM_ITERATOR_ELEMENTS_PROPERTY

MULE-19323

ENABLE_POLICY_ISOLATION_PROPERTY

MULE-19226

ENTITY_RESOLVER_FAIL_ON_FIRST_ERROR_PROPERTY

EE-7827

ENABLE_PROFILING_SERVICE_PROPERTY

MULE-19588

SET_VARIABLE_WITH_NULL_VALUE_PROPERTY

MULE-19443
See [Feature Flagging](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed description of each feature flag and configuration instructions. ### [](#bundled-components)Bundled Components - Runtime Manager Agent plugin version 2.4.21 - Dataweave version 2.4.0 ## Fixed Issues
Mule Runtime Issue ID

The tooling service in Anypoint Studio now properly propagates metadata for DataWeave Intersection types.

SE-22333

Mule runtime engine uses the correct version of the disruptor.

SE-19387

Fixed a metaspace memory leak in Anypoint Connector for Database (Database Connector).

SE-15818

HTTP requests with OAuth now use a valid token.

SE-15667

Console logs do not produce repeated log messages for the completion of a single batch job.

SE-11533

Fixed the Illegal reflective access warnings for OpenJDK 11.

SE-13349

After a connection is re-established, SFTP files are now picked up properly.

MULE-18294/SE-13897

In Azure Service Bus Connector, when a flow is stopped, the message listener now stops polling.

SE-17389

API Manager now properly handles connection pool exhaustion and no longer shows APIs in INACTIVE state.

SE-15351

Anypoint Connector for NetSuite (NetSuite Connector) no longer makes excessive getServerTime calls.

SE-15200

An application no longer fails to deploy if it uses the same custom name space as an applied custom policy.

SE-15056

Applications using Anypoint Connector for Database (Database Connector) under heavy load no longer show StackOverflow errors.

SE-14663

Mule no longer produces an exception related to class loading when the class exists as a dependency and is configured as a shared library.

SE-14245

When an encoded slash is sent as the value of a URI parameter, the associated listener is now found.

SE-14046

Mule 4 no longer fails to stream the complete payload to the client.

SE-14012

The ErrorType no longer changes when entering an Error Handler scope.

SE-13673

Proxies no longer experience outages during redeployment in Anypoint Runtime Fabric configured with two replicas and rolling update.

SE-13596
DataWeave Issue ID

Added the writeDeclaredNamespaces XML writer property to write all declared namespaces in the root element.

DW-16

Added the writeDeclaration YAML writer property to avoid writing the header declaration.

DW-162

Added a new Strings module for easier string data management.

DW-406

Added the constant folding functionality so that DataWeave replaces operations involving constant values with the actual result. For example, 1024*8 is replaced at compile time with the resulting value 8192.

DW-427

Added flow retyping to the type system, which enables better accuracy within flow-control structures featuring checks that involve typing.

DW-438

Added code inspectors so that quick fixes are suggested with best practices, such as replacing null checks with a default expression, or replacing sizeOf() == 0 with isEmpty().

DW-33/DW-632

Added an inspection to replace using with do blocks.

DW-771

Improved error messages when creating Java objects.

DW-565

Improved performance on floating point number parsing by identifying in advance if the number has a floating point or not.

SE-20614

Extended the common subexpression elimination process to work with index selectors.

SE-19934

Added functions that work with null values to the Core, Arrays, and String modules.

DW-425

Improved JSON performance by copying bytes from input to output directly during JSON-to-JSON data transformations.

DW-230

Improved YAML support of scalar types, string quotations, custom tags, and comment retention.

DW-687

Added the filterTree function to the Tree module to be able to filter any data structure.

DW-160

Added validations for index tokens in CSV format.

DW-577

Added support for the Java classes OptionalInt, OptionalDouble and OptionalLong.

DW-628

Added support for file:/example/file.txt as a valid URL.

DW-195

Added warning when using the design-time only format application/dw without dataOnly mode.

DW-873

Added experimental run and eval functions to dynamically execute scripts.

DW-170

Added the concept of optional function parameters in the type system.

DW-874

Improved CSV streaming to avoid unnecessary processing.

DW-876

Improved the mapObject function to avoid unnecessary processing.

DW-535

Improved the flatten function to avoid unnecessary processing.

DW-509

Improved code validation. Now an error returns when a variable is using the same name as an input.

DW-522

Improved the precision of math operations and added a property to retain the previous behavior: com.mulesoft.dw.math.exact_precision.

SE-16452

Improved handling of big XML files to fix potential I/O exceptions.

DW-250

Fixed error locations when scripts feature dynamic string selectors.

DW-875

Fixed a false negative error message when using multiple union types.

DW-297

The write function return types are now consistent with input types.

DW-298

The update operator no longer fails when working with repeated keys and attributes.

DW-306

Processing of XML documents with comments and streaming enabled now works as expected.

DW-307

DataWeave no longer fails to parse a single key-value pair with a conditional and parentheses.

DW-309

The type system now validates overloaded functions as parameters.

DW-316

Parallel processing on ndjson now works as expected.

DW-325

Fixed a materialization and streaming failure.

DW-368

Fixed the behavior of the slice function.

DW-409/DW-410

Fixed the ability to import namespaces from external modules.

DW-414

DataWeave now produces the error Division by Zero when dividing by 0.0 instead of an internal exception.

DW-415

DataWeave now properly validates that do blocks do not contain any reserved word declaration.

DW-416

Running flatten on flatten no longer causes loss of values.

DW-691

The update operator now works when no attribute is defined.

DW-216

Improved handling of binary data to prevent running out of memory when calculating sizes of processed data.

SE-16559

The com.mulesoft.dw.coercionexception.verbose property no longer logs data from coercion exceptions.

SE-15487

Using nested binary functions no longer produces a StackOverflow error.

SE-16092

DataWeave no longer returns UnsupportedOperationException when parsing an invalid script.

DW-294

Fixed a potential IndexOutOfBoundException when using overloaded functions with four parameters.

DW-159

Added support for dumping Flat File and Avro schemas when com.mulesoft.dw.dump_files is enabled.

DW-137

Improved code compilation. Implicit inputs are not added if a variable with the same name is explicitly defined.

DW-630
## Known Issues
Issue ID

Mule AS2 Connector 5.x is not compatible with Mule 4.4. For any applications that use this version of the connector, upgrade the connector to the latest version available in Exchange.

EE-8071

WSDL Proxies on version 1.1.1 and 1.1.2 are not compatible with Mule 4.4. Before you upgrade to 4.4, upgrade the WSDL Proxies to a newer version.

EE-8070

Mule SAP Connector 5.3.4 is not compatible with Mule 4.4. For any applications that use this version of the connector, upgrade the connector to the latest version available in Exchange.

EE-8061
## Upgrade If you are upgrading to Mule 4.4 from an earlier Mule 4.x version, see [Upgrading Mule Runtime Engine (Versions 4.x to 4.n)](https://docs.mulesoft.com/jp/release-notes/mule-runtime/updating-mule-4-versions) for upgrade instructions. To ensure optimal performance with Mule 4.4 and avoid unexpected issues, update these modules and extensions to their latest version at the time of this release:
Module or Extension Version

APIkit for Mule 4

1.5.5

APIkit for SOAP

1.2.9

Spring module

1.3.6

MUnit plugin

2.3.6

Module Testing Framework (mtf-tools)

1.1.1
### [](#considerations-for-mule-extensions-developers)Considerations for Mule Extensions Developers If you update the version of your parent `pom.xml` file to 1.4.0 or later when you build a Mule extension, ensure that the dependencies in your `pom.xml` file do not override dependencies defined in the parent `pom.xml` file and declare only the dependencies you need. If you need to declare a dependency that is already declared in the parent `pom.xml` file, do not specify a version so it uses the version from the parent `pom.xml` file. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Engine 4.6.0 Release Notes 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. ## [](#october-2026)October 2026 ### Fixed Issues ### [](#patch-4-6-36)Patch 4.6.36 The October patch update 4.6.36 addresses regressions in the October patch update 4.6.35.
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-6-35)Patch 4.6.35 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.35 includes Runtime Manager agent 2.7.20. See [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20). ### Fixed Issues Patch release version: 4.6.35 This patch update addresses these Mule issues:
Issue Resolution ID

The Reactor Core library is upgraded to 3.8.7.

W-3300013

The Jackson library is upgraded to 2.22.2.

W-23947149

The jsoup library is upgraded to 1.23.2.

W-23987949

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

An SDK API for queues (VM usage) and core adapters is added.

W-19439432

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. To change the behavior, configure the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2026)September 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.34 includes Runtime Manager agent 2.7.16. See [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). 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. - Health Signals: Evaluates a small set of fast host- and JVM-level health signals and reports those that triggered, including low memory, high CPU steal, and JVM crash logs. - Memory Detail: Provides a JVM memory-pool breakdown and garbage-collector statistics, showing heap and non-heap usage with metrics such as initial, used, committed, and maximum memory values. - Known Issues: Scans the runtime logs and deployed applications for well-known problem signatures, including out-of-memory conditions, abnormal terminations, and MUnit packaging issues. ### Fixed Issues Patch release version: 4.6.34 This patch update addresses these Mule issues:
Issue Resolution ID

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Apache Commons Compress library is upgraded to 1.26.0.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540335

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531
DataWeave 2.6.30 is bundled with the Mule 4.6.34 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2026)August 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.33 includes Runtime Manager agent 2.7.18. See [Runtime Manager Agent 2.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-18). 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. - Network Info: Shows host-level network diagnostics, including the hostname, network interfaces with their assigned IP addresses and I/O counters, and active and listening network connections. - Agent Info: Reports the installation and health of the Mule agent that pairs the runtime with Anypoint Platform, including whether the agent is installed, its version, key configuration values, keystore certificate details, and the most recent connection status. - Platform Connectivity: Checks TCP connectivity from the Mule runtime host to the Anypoint Platform endpoints and dumps the TLS certificate chain presented by the platform. ### Fixed Issues Patch release version: 4.6.33 This patch update addresses these Mule issues:
Issue Resolution ID

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23121654
DataWeave 2.6.29 is bundled with the Mule 4.6.33 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2026)July 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.32 includes Runtime Manager agent 2.7.16. See [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). Feature Flagging Mechanism: - Mule 4.6 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.6.32 This patch update addresses these Mule issues:
Issue Resolution ID

A NullPointerException error no longer occurs in event context handling when a flow times out while a non-blocking operation is still in flight.

W-22902839

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The Joda-Time library is upgraded to 2.13.0.

W-3300013

The Rhino library is upgraded to 1.7.15.1.

W-22805996

The Apache Neethi library is upgraded to 3.2.1.

W-22805997

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806011

The Apache CXF library is upgraded to 3.5.11.

W-23037585

The c3p0 library is upgraded to 0.14.1.

W-23012711

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007
DataWeave 2.6.28 is bundled with the Mule 4.6.32 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

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 per_app_java_bean_cache compatibility flag.

W-22417507
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2026)June 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.31 includes Runtime Manager agent 2.7.15. See [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15). ### Fixed Issues Patch release version: 4.6.31 This patch update addresses these Mule issues:
Issue Resolution ID

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971
DataWeave 2.6.27 is bundled with the Mule 4.6.31 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

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 per_app_java_bean_cache compatibility flag.

W-22417507
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2026)May 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.30 includes Runtime Manager agent 2.7.13. See [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13). 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.6.30 This patch update addresses these Mule issues:
Issue Resolution ID

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339
DataWeave 2.6.26 is bundled with the Mule 4.6.30 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2026)April 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.29 includes Runtime Manager agent 2.7.11. See [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11). Feature Flagging Mechanism: - Mule 4.6 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.6.29 This patch update addresses these Mule issues:
Issue Resolution ID

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933
DataWeave 2.6.25 is bundled with the Mule 4.6.29 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2026)March 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.28 includes Runtime Manager agent 2.7.10. See [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10). Feature Flagging Mechanism: - Mule 4.6 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.6.28 This patch update addresses these Mule issues:
Issue Resolution ID

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The tika-core library is upgraded to 3.2.3.

W-21179465

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900
DataWeave 2.6.24 is bundled with the Mule 4.6.28 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2026)February 2026 ### [](#patch-4-6-27)Patch 4.6.27 - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-6-26)Patch 4.6.26 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.26 includes Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues Patch release version: 4.6.26 This patch update addresses these Mule issues:
Issue Resolution ID

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Fastutil is now replaced with fastutil-core.

W-20729870
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2026)January 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.25 includes Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). MUnit: - MUnit version 3.6.3 is now required. See [MUnit 3.6.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.3-release-notes). General improvements: - You can now view deployment information in the `diaf` file. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.6.25 This patch update addresses these Mule issues:
Issue Resolution ID

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469
DataWeave 2.6.22 is bundled with the Mule 4.6.25 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20618375

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2025)November 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.24 includes Runtime Manager agent 2.7.8. See [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8). General improvements: - You can now view CPU usage information in the `diaf` file. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.6.24 This patch update addresses these Mule issues:
Issue Resolution ID

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now properly honors the graceful shutdown timeout. In versions earlier than 4.11.0, you must enable this behavior using these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19340663

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.6, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException no longer thrown when DW serializes error.errorMessage in Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474
DataWeave 2.6.20 is bundled with the Mule 4.6.24 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2025)October 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.23 includes Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). Mule Troubleshooting Plugin: - Mule 4.6.23 introduces the Mule Troubleshooting plugin, which generates a structured diagnostic archive (DIAF) to simplify troubleshooting, consolidate runtime metrics, and provide consistent data for MuleSoft Support. It works across all deployment models and helps investigate performance issues, application errors, and scheduler activity. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.6.23 This patch update addresses these Mule issues:
Issue Resolution ID

The org.springframework library is upgraded to 5.3.45.

W-18603096

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

This release reverts the changes introduced in W-17340911.

W-17340911

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

Batch queuestore files now clean up correctly in rare load failure scenarios, such as out of memory errors.

W-17935223

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164
DataWeave 2.6.19 is bundled with the Mule 4.6.23 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334

Module compilation performance is improved when running concurrently.

W-19376546
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2025)September 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.22 includes Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues Patch release version: 4.6.22 This patch update addresses the following Mule issues:
Issue Resolution ID

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2025)August 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.21 includes Runtime Manager agent 2.7.6. See [Runtime Manager Agent 2.7.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-6). General improvements: - License Delivery Update: Starting with Mule 4.6.21, Enterprise licenses are now provided either as a single `license.lic` file or as a `.zip` that contains both FIPS and non-FIPS licenses. See [FIPS 140-2 Compliance Support](https://docs.mulesoft.com/mule-runtime/latest/fips-140-2-compliance-support) for details. General improvements: - When running Mule runtime in FIPS security mode with clustering enabled, the encryption key defined in `mule.cluster.network.encryption.key` must have a length of 16, 24, or 32 bytes. See [Enable Clustering in FIPS Mode](https://docs.mulesoft.com/on-premises/latest/mule-high-availability-ha-clusters#cluster_fips) for details. ### Fixed Issues Patch release version: 4.6.21 This patch update addresses the following Mule issues:
Issue Resolution ID

Silent errors and hangs no longer occur when a component fails to start within a foreach/subflow combination.

W-18589595

An incorrect error level message no longer shows during deployment when using APIKit with no flow mappings.

W-19004884

Performance degradation no longer occurs when using repeatable streaming.

W-19175330
DataWeave 2.6.17 is bundled with the Mule 4.6.21 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

A stackOverflowException error no longer occurs during materialization.

W-18981240

The distinctBy function in dw::core::Core now works as expected when used with a CSV input.

W-18990604

DataWeave runtime types are now correctly written when outputting Java.

W-18942349

Access to multipart content raw value no longer reads the part content.

W-18892158

The sizeOf function now works correctly in DataWeave 2.6.14 and later.

W-18850597

The orderBy function now evaluates ordering criteria only when required.

W-18851259

The fromCharCode function now works as expected.

W-17204482
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2025)July 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.20 includes Runtime Manager agent 2.7.5. See [Runtime Manager Agent 2.7.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-5). ### Fixed Issues Patch release version: 4.6.20 This patch update addresses the following Mule issues:
Issue Resolution ID

Schedulers are no longer triggered during graceful shutdown.

W-17981248

The commons-beanutils:commons-beanutils library is upgraded to v1.11.0.

W-18687846

The com.google.code.gson:gson library is upgraded to v2.12.1.

W-17896347

Repeatable streams now make data available before the buffer is full. To enable this behavior, set the system property mule.repeatableStreaming.bytes.eagerRead to true.

W-18716253

Serialization now works correctly with API Gateway internal classes.

W-18475283

The W-17340911 fix, which resolved loader constraint violation errors related to http-connector dependencies in both the domain and the policy, has now been reverted to restore the previous behavior.

W-18327141
DataWeave 2.6.16 is bundled with the Mule 4.6.20 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

This patch update reverts the fix.

W-17167283

XML encoding detection now works correctly when the declaration header is missing.

W-18853667

The fromCharCode function in dw::core::Strings. now manages surrogate characters correctly.

W-17204482

Unicode characters now render correctly at the beginning of the string when using the DataWeave writer function with the onlyData flag enabled.

W-14855645

The Apache POI library is now upgraded.

W-18253747

Experimental warning messages are no longer logged on DataWeave SDK files.

W-16384926
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2025)June 2025 ### [](#patch-4-6-19)Patch 4.6.19 - This patch update reverts the fixes for the following Mule issue: W-17703164 ### [](#patch-4-6-18)Patch 4.6.18 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.18 includes Runtime Manager agent 2.7.4. See [Runtime Manager Agent 2.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-4). ### Fixed Issues Patch release version: 4.6.18 This patch update addresses the following Mule issues:
Issue Resolution ID

Loader constraint violation errors no longer occur when http-connector dependencies exist in both the domain and the policy.

W-17340911

Serialization of result objects with Kryo no longer fails with InaccessibleObjectException in Java 17.

W-17774685

Class loading no longer results in deadlocks caused by a race condition.

W-18388443

Spring Framework artifacts are replaced with vendor-supported equivalents to improve long-term compatibility.

W-18462316

A serialization exception no longer occurs when using caching scope.

W-17703164
DataWeave 2.6.15 is bundled with the Mule 4.6.18 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The performance of the orderBy function is now improved.

W-18439576

Reading a CSV file inside a MultiPart body now works correctly when performed more than once.

W-17147598

A memory leak of the binding context no longer occurs when using the foreach scope.

W-18472194
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2025)May 2025 ### [](#patch-4-6-17)Patch 4.6.17 The May patch update 4.6.17 addresses a regression in the previous May patch update, 4.6.16, and includes the fixes in the patch. Patch release version: 4.6.17 This patch update addresses the following Mule issues:
Issue Resolution ID

Cluster discovery mechanism now works as expected on Runtime Fabric, CloudHub 2.0, and Anypoint Platform PCE environments, ensuring that schedulers are executed only on the primary node.

W-18528551
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-6-16)Patch 4.6.16 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.16 includes Runtime Manager agent 2.7.2. See [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2). ### Fixed Issues Patch release version: 4.6.16 This patch update addresses the following Mule issues:
Issue Resolution ID

Parallel For Each events no longer randomly timeout after a NullPointerException error.

W-17980769

The error message "Couldn’t parse instance of ReentrantReadWriteLock" in ReentrantReadWriteLockSerializer no longer occurs.

W-18057570

Parameters field isn’t serialized in InternalEventImplementation.

W-17703164

Connectivity tests in MTS are now fixed for Java 17.

W-18075077

Exceptions no longer occur when using WebSocket close codes outside a predefined subset. The code now correctly handles all standard or custom WebSocket close codes.

W-17846088

The expressionExecutor in adapter is no longer disposed more than once.

W-16263266

org.glassfish:jakarta.json was removed form the distribution.

W-17896357

xerces-j is upgraded to 2.12.2.

W-16980865

raml-parser is upgraded to v1.0.44-17.

W-17750714
DataWeave 2.6.14 is bundled with the Mule 4.6.16 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Materialization issues no longer occur when using CSV content inside variables.

W-17167283

A compatibility flag is now added to address the different results produced by calling sizeOf with NumberType.

W-18020856

An unnecessary import is now removed from dw::util::Diff to eliminate a warning when running MUnit.

W-17670504

DataWeave no longer returns a format error on readUnquotedString.

W-18118138

Overflowing no longer occurs while reading large file on multipart format.

W-17644871

Performance issues no longer occur when using the Mule API Java class Message in DataWeave scripts.

W-18034217

DataWeave now preserves trailing zeroes of single-element sum.

W-17283050
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2025)April 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.15 includes Runtime Manager agent 2.7.2. See [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2). Enterprise Edition License: - The command `mule -verifyLicenseDetails [path_to_license]` that verifies the license before installing it is now added. See [Verify or Remove Enterprise Edition License](https://docs.mulesoft.com/on-premises/latest/installing-an-enterprise-license#verify-or-remove-enterprise-edition-license). ### Fixed Issues Patch release version: 4.6.15 This patch update addresses the following Mule issues:
Issue Resolution ID

xerces-J is now updated to v2.12.2.

W-16980865

Error type in raise-error is now correctly resolved when defined with a static property.

W-17339304

DuplicateMessageException is now correctly serialized with Kryo.

W-17844603

You can now use the mule --verifyLicenseDetails [path-to-license.lic] command to verify a given license file.

W-17340620

org.apache.cxf:cxf-core is now upgraded to version 3.5.10.

W-17896358
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2025)March 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.14 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). Feature Flagging Mechanism: - Mule 4.6 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.6.14 This patch update addresses the following Mule issues:
Issue Resolution ID

Resources are now properly released after a timeout when using the Scatter-Gather or Parallel For Each routers. The mule.forkJoin.completeChildContextsOnTimeout feature flag is now added to enable this behavior.

W-16941297

MessagingException can now be converted to JSON using DataWeave.

W-16629236

grizzly-ahc is now upgraded in HTTP Service.

W-17667949

Performance degradation no longer occurs when the nonBlockingWriter is enabled for response streaming.

W-17627284

A race condition introduced by W-17048606 no longer occurs, where the last part of the response body was truncated when streamResponse flag is set to true in request-connection.

W-17617940

Serialization using Object Store V2 with OAuth2 Provider now works as expected.

W-16673760

Performance during cache scope execution is now improved.

W-17671126
DataWeave 2.6.12 is bundled with the Mule 4.6.14 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The Flat File Module now supports YAML files with nested depth greater than 50.

W-17495145

xerces-j is now updated to 2.12.2.

W-16918194
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2025)February 2025 ### [](#patch-4-6-13)Patch 4.6.13 The February patch update 4.6.13 addresses a regression in the previous February patch update, 4.6.12, and includes the fixes in the patch. Patch release version: 4.6.13 This patch update addresses the following Mule issues:
Issue Resolution ID

ConfigurationException no longer occurs while performing Amazon DynamoDB Connector operations.

W-17801971
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-6-12)Patch 4.6.12 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.12 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). ### Fixed Issues Patch release version: 4.6.12 This patch update addresses the following Mule issues:
Issue Resolution ID

InterceptionException is no longer thrown while running MUnit test containing a batch job.

W-17395302

The optimization to avoid sending body contents on NTLM type 1 requests added in W-17107281 is now controlled by the feature flag mule.ntlm.avoid.send.payload.on.type1.

W-17216089

A ClassCastException thrown when an error occurs within an on-error-continue component no longer prevents transactions from rolling back.

W-17430963

A corner case has been fixed and Anypoint Monitoring dashboard now correctly shows all metrics.

W-16828516

Kryo serialization issue no longer occurs in Java 17 when running with distributed cluster using authentication, caching policy, and persistent Object Store.

W-16912085

Transactions initiated before a flow-ref call are now rolled back in the correct place if an error propagates from the flow-ref.

W-17453707

API metrics are now properly sent.

W-17529530
DataWeave 2.6.11 is bundled with the Mule 4.6.12 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2025)January 2025 ### [](#patch-4-6-11)Patch 4.6.11 - This patch update reverts the fixes for the following Mule issues: W-17107281 and W-17048606. - This patch update reverts the fixes for the following DataWeave issues: W-16823030, W-17206423, and W-17372664. ### [](#patch-4-6-10)Patch 4.6.10 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.10 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). ### Fixed Issues Patch release version: 4.6.10 This patch update addresses the following Mule issues:
Issue Resolution ID

Windows no longer throws cannot delete file errors during application undeploy.

W-17050930

BufferOverFlowException with inter-node communication getting stuck no longer occurs when using clusters with encryption under heavy load.

W-16517561

Unnecessary internal blocking operations no longer occur when handling large streamed HTTP responses.

W-17048606

Body content is no longer sent on Type 1 requests during NTLM authentication.

W-17107281

Deploying applications that contain XML SDK connectors no longer causes application class loader memory leak.

W-16814280

An infinite loop no longer ocurrs when a redelivery policy is exhausted in a source configured with Transactions and contains an On Error Propagate.

W-17403761

ConnectionException no longer occurs when using batch processing.

W-17008722

A memory leak no longer occurs when using mule-validation-module.

W-16789548

MessageProcessorNotificationListener is no longer called multiple times when running MUnit suites.

W-11866494

A serialization error no longer occurs in Java 17 when using clustering mode or Object Store v2.

W-17218707

IllegalAccessException is no longer thrown during cache scope serialization with Kryo.

W-17089503

All transactions running within a global Error Handler are now committed as expected.

W-16619771
DataWeave 2.6.10 is bundled with the Mule 4.6.10 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030

The Java reflection lookup strategy is now improved for bean instances.

W-17206423
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2024)November 2024 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.9 includes Runtime Manager agent 2.6.6. See [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6). ### Fixed Issues Patch release version: 4.6.9 This patch update addresses the following Mule issues:
Issue Resolution ID

Memory leak in MuleApplicationClassloader no longer occurs while undeploying an application.

W-16823349

A batch serialization error no longer occurs in Java 17 when one of the steps throws SQLException.

W-16546951

A deadlock no longer occurs when consuming the payload in the completion callback of the HTTP client sendAsync method.

W-16640190

NullPointerException no longer occurs when undeploying an application with native libraries in Windows OS.

W-16712841

Log4j2 monorepo is upgraded to 2.24.1.

W-16889265

The commons-io:commons-io dependency is upgraded to 2.17.0.

W-16843119
DataWeave 2.6.9 is bundled with the Mule 4.6.9 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The stripTrailingZeroes compatibility flag is now added to preserve the decimal format.

W-17030593

Apache POI folder used for temporal files is no longer deleted.

W-16899674
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2024)October 2024 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.8 includes Runtime Manager agent 2.6.6. See [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6). ### Fixed Issues Patch release version: 4.6.8 This patch update addresses the following Mule issues:
Issue Resolution ID

Spring Core is upgraded to 5.3.39.

W-16519084

The configuration-properties encoding parameter is no longer ignored.

W-12228892

Web Service Consumer Connector and RosettaNet Connector no longer fails when there is an HTTP TLS transport configuration.

W-16288302

InitialisationException is no longer thrown when using the Raise Error component with an extra space at the end of the type field.

W-16237424

Kryo serialization now works as expected with ResourceOwnerOAuthContextWithRefreshState when using Java 17.

W-16533466

Kryo serialization now works as expected when executing the Rate Limit policy in Java17.

W-16843706

Fatal errors no longer occur when loading native libraries in Java 17.

W-16787783

java.lang.InstantiationError : java.util.Map is no longer thrown when applying an authentication policy.

W-16595277

When the feature flag anypoint.platform.keep.default.policy.format is set to true or the policy minimum Mule version is 4.5.0, the policy name format is now ${policyName} @ ${artifactName} - ${flowName}.

W-16169887

Logging for the Analytics .db files cleanup is now improved.

W-16624763

grizzly-ahc is now upgraded in the HTTP service.

W-16734361

Race condition now causes an infinite loop in Grizzly AHC.

W-16599945
DataWeave 2.6.8 is bundled with the Mule 4.6.8 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

DataWeave descendant selector performance is now improved.

W-16343577

Streaming capability for arguments at sum, countBy, and sumBy functions is now enabled.

W-16125755

Input/output MimeType properties are now preserved as expected.

W-16161736

Access error for Java 17 encapsulation errors is now improved.

W-15705596

Coercion error is now caught inside try as expected.

W-15323897
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2024)September 2024 ### What’s New - `cxfVersion` is upgraded to 3.5.9. - JaCoCo is upgraded to 0.8.11. - Maven JAR Plugin is upgraded to 3.3.0. ### Fixed Issues Patch release version: 4.6.7 This patch update addresses the following Mule issues:
Issue Resolution ID

NullPointerException is no longer thrown when DataWeave transforms a RetryPolicyExhaustedException to a JSON format on a Java 17 runtime.

W-15643200

Properties files are now located in the lib/user directory during application deployment.

W-16404468

com.google.gson.stream.MalformedJsonException is no longer thrown while deploying an application.

W-16343071

Debug logs for custom policies containing a custom extension/connector now work correctly.

W-15286605

The process of unloading native libraries in Windows OS running on Java 8 and Java 11 is now improved.

W-16375439

cxfVersion is upgraded to 3.5.9.

W-16436783

JaCoCo is upgraded to 0.8.11.

W-14866639

maven-jar-plugin is upgraded to 3.3.0.

W-14580541

Policies with minimum Mule version 4.4.0 now use the flow name as part of the artifact name, when the feature flag anypoint.platform.keep.default.policy.format=true is set.

W-16169887

NullPointerException is no longer thrown when API Gateway tries to dispose an empty cluster.

W-16540685

API Gateway pollers are no longer initialized when the API Gateway is started in offline mode.

W-16093885

Race condition no longer causes byte buffer disposal errors when deploying policies.

W-16450677
DataWeave 2.6.7 is bundled with the Mule 4.6.7 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

DataWeave now preserves MimeType properties correctly.

W-16161736
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2024)August 2024 Patch release version: 4.6.6 This patch update addresses the following Mule issues:
Issue Resolution ID

Loaded native libraries are now copied into a separate temporary folder to avoid issues while redeploying applications in Windows OS.

W-15894519

Parameter resolution error handling is no longer affected when the parameterized operation is inside a dynamically referenced subflow.

W-15923581

The OAuth token invalidation status is now communicated to other nodes in a cluster when a token is invalidated on one node.

W-15154658

Flows now honour the state configured in flows.deployment.properties when restarting the app, regardless of the initial state. To enable this feature, use the mule.honour.persisted.flow.state system property. This only applies to Standalone and Hybrid deployments.

W-15750334

Mule runtime startup no longer fails when MULE_HOME has a blank space on Windows OS.

W-15346051

A serialization exception is no longer thrown when a Batch Step fails with a ModuleException in Java 17.

W-15808825

mule-script-module is now improved to ensure that beans no longer contain invalid references to injected dependencies, whether they are directly or indirectly reliant on MuleConfiguration.

W-15832941

Jars in lib/user are now visible from jars in lib/opt. For example, using cluster persistence with the JDBC driver provided in lib/user no longer fails with a Could not load driverClass error.

W-16010357

Serialization now works as expected with Batch Job and Salesforce BulkOperationResult in Java 17.

W-16105403

Batch module no longer fails with a Could not serialize object error when client ID enforcement policy is enabled.

W-16124318

Deploying a policy no longer fails while using a mule directory with whitespaces.

W-15440100

ClassNotFoundException is no longer thrown when upgrading from Mule runtime 4.4.0 using the OAuth 2 authentication code and Object Store V2 stored tokens.

W-15595791

NullPointerException no longer occurs when having MQ connector as a dependency in MUnit 3.1.0.

W-15734679

API Gateway initialization no longer fails if quorum isn’t reached in cluster mode.

W-15951155

Hard timeout for platform requests is now available by setting up the anypoint.platform.request_timeout in milliseconds.

W-16141554
DataWeave 2.6.6 is bundled with the Mule 4.6.6 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Argument materialization is now improved at the dw::Runtime::try function.

W-15323897

Streaming capability is now enabled for arguments of sum, countBy, and sumBy functions.

W-16125755
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2024)July 2024 Patch release version: 4.6.5 This patch update addresses the following Mule issues:
Issue Resolution ID

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws the groovy.lang.MissingMethodException exception.

W-15750766

Batch job instance queue store files are removed after completion.

W-15546969

Cache scope with multiple computations no longer occurs if events arrive concurrently for an absent key.

W-14604517

Tanuki wrapper configuration is now enabled for AArch64.

W-15839796

MDC context is reset after the XML SDK operation is executed.

W-15206528

MUnit tests no longer fail with groupId cannot be null when using a parent POM for dependencies and plugins.

W-14998254

Maven plugin versions are updated to be compatible with Maven 3.9.

W-15554914

JRuby dependency is upgraded to 9.4.7.0.

W-15757000

Deploying a policy in Windows no longer fails in folders containing whitespaces.

W-16112611

Open Telemetry tracing support is now added to policies.

W-15633203

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas.

W-15769926

Logging for Gateway Analytics initialization is now improved.

W-15904845

Handling of connection errors with API platform is now improved.

W-15809377

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert.

W-15427352
DataWeave 2.6.5 is bundled with the Mule 4.6.5 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Enforced Java accessibility restrictions only for Mule apps with DataWeave language level version 2.6 and later and executing with Java 17 and later.

W-15832793

Materialization issues no longer occur with schema properties.

W-15839190

The Flat File module now adds the substituteCharacterAsMissingValue reader property.

W-15571377

The Flat File module now adds the fillRedefinesByMaxLength writer property.

W-15973636
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2024)June 2024 Patch release version: 4.6.4 This patch update addresses the following Mule issues:
Issue Resolution ID

Applications configured with OAuth and running on Java 17 are now correctly serialized.

W-15425364

You can now see the number of flows considered for UBP and what those flows are when the application starts.

W-14401338

plexus-archiver is upgraded to 4.9.1.

W-14821825

The version in the pom.xml file is now parsed when containing the property ${text}.

W-15228973

Events with statistics are now correctly serialized for applications running on Java 17.

W-15542604

The exception java.lang.IllegalAccessException no longer occurs when using itemSequenceInfo in DataWeave.

W-15617764

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

Batch job serialization now works as expected when running on Java 17.

W-15345812

Tracing variables inside XML operations are no longer propagated to the flows.

W-15206528

jackson-databind is upgraded to 2.15.4.

W-15628361

NullPointerException no longer occurs on AST-deserialized applications using Anypoint Custom Metrics Connector.

W-15677894

Resiliency is now improved on policy application and updates.

W-15426519
DataWeave 2.6.4 is bundled with the Mule 4.6.4 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

The Excel writer now generates XLSX files using ZIP specification 2.0.

W-15534640

When comparing a Date with a String representation of a date, the Date format is now used to coerce the String accordingly.

W-15478713

Access error messages for Java 17 encapsulation errors are now improved.

W-15705596
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2024)May 2024 Patch release version: 4.6.3 This patch update addresses the following Mule issues:
Issue Resolution ID

Client, policy, and API names are now shown when logging Analytics events.

W-15294568

When upgrading a policy, templates are now downloaded before the previous version is removed.

W-15212679

When applying a policy that initially failed but was later applied successfully, the retry initiated by the gateway no longer causes an exception error.

W-15186491

Joda-Time is upgraded to v2.12.7.

W-15511864

Apache CXF is upgraded to version 3.5.8.

W-15293232

Getting metadata from a XSD with vc:minVersion=1.1 no longer causes a NullPointerException error.

W-15193303
DataWeave 2.6.3 is bundled with the Mule 4.6.3 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

ArithmeticException no longer executes toHex with non-integer numbers.

W-15006840

Performance degradation no longer occurs when an array is concatenated.

W-15399854
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2024)April 2024 Patch release version: 4.6.2 This patch update addresses the following Mule issues:
Issue Resolution ID

NullPointerException no longer occurs when deploying domains.

W-15159880

Hazelcast is upgraded to 5.2.5.

W-15274674

Spring is upgraded to 5.3.33.

W-15260752

GraalJS is upgraded to 22.3.5.

W-15284493

MUnit tests using tracing module and "Set logging variable" now work as expected.

W-14773408

Using vc:minVersion="1.1" in XSD schema no longer throws NullPointerException in XML SDK connectors.

W-15081363

Template parser validation is now improved.

W-15141905
DataWeave 2.6.2 is bundled with the Mule 4.6.2 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Inconsistent behavior no longer occurs between in-memory and streaming XML parsers for deciding document encoding.

W-15110015

Streaming for DataWeave-based data formats like ndjson now works as expected.

W-15262860

The Excel reader no longer reads furigana characters.

W-14991276

Coercion of the third parameter on the ternary function executor now works as expected.

W-15061008
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2024)March 2024 Patch release version: 4.6.1 This patch update addresses the following Mule issues:
Issue Resolution ID

Performance is now improved for certain For Each scenarios.

W-14678431

HTTP Request Connector no longer throws Connection limit exceeded, cannot process request when maxConnections is set to 1.

W-14686211

Disabling the enableNotifications flag on the On Error Continue component now works as expected.

W-14954677

Multi-step batch jobs can now be correctly resumed and finished after being stopped.

W-14726677

The error message is now improved for exceptions that occur when loading an extension because of Java version incompatibility.

W-14934626

The error message namespace already exists is no longer thrown when using the same namespace with the current module or extension namespace for apps using the XML SDK component.

W-14559071

Transactions' timeout is now honored. When a transaction times out, it is rolled back, and an error is thrown that can be handled with error handling. To enable this, activate the mule.tx.error.when.timeout feature flag.

W-14128870

Memory leaks no longer occur when using the mule-scripting-module dependency with HTTP Connector.

W-14479158

Java JDK inlineDeclaration now resolves correctly for stateless subtypes.

W-14645134
DataWeave 2.6.1 is bundled with the Mule 4.6.1 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Performance is now improved when coercing addition and subtraction operations.

W-14927555
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-6-2024)February 6, 2024 ### What’s New The 4.6.0 version of Mule runtime introduces the following enhancements: Java adoption: - MuleSoft is adopting Java’s long-term support (LTS) release cadence, beginning with Mule runtime 4.6, which adds support for Java 17 LTS. See [Java Adoption](https://docs.mulesoft.com/jp/release-notes/mule-runtime/java-adoption).
The maximum supported version for running your applications is Java 17 for Mule runtime 4.6.x and later. During the packaging of your app, all code, including third-party dependencies, must be compiled for Java 8.
- Java 17 manages memory differently than Java 8. See [Application Performance](https://docs.mulesoft.com/jp/general/java-support#application-performance). - Mule runtime classes are now modularized per the Java module system introduced back in Java 9 (also known as JPMS or Project Jigsaw). Reflective introspection of Mule runtime classes is now limited. To maintain backward compatibility, reflective access to classes defined within the scope of your applications and domains remains open to access. - Java EE libraries are now removed from Mule runtime for Java 17. Mule Gateway improvements: - You can now upgrade your policies and API proxies to Java 17. See [Upgrading Policies](https://docs.mulesoft.com/jp/general/java-support#policies) and [Upgrading API Proxies](https://docs.mulesoft.com/jp/general/java-support#api-proxies). - Mule Gateway now supports API analytics event logging. To enable event logging, see [Log Analytics Event Data](https://docs.mulesoft.com/jp/mule-gateway/mule-gateway-metrics#log-analytics-event-data). - Mule Gateway now supports automatically deleting cached policy files. To enable this feature, see [Cached Policy Assets Deletion](https://docs.mulesoft.com/jp/mule-gateway/policies-policy-overview#cached-policy-assets-deletion). Mule SDK improvements: - Mule SDK (Java SDK and XML SDK) now support Java 17. See [Upgrading Custom Connectors](https://docs.mulesoft.com/jp/general/java-support#custom-connectors). - Java SDK now includes the new `@JavaVersionSupport` annotation. See [Supported Java Version Concept](https://docs.mulesoft.com/jp/general/customer-connector-upgrade#release-your-custom-connector). - XML SDK now supports TLS. See [XML SDK TLS Support](https://docs.mulesoft.com/mule-sdk/latest/xml-sdk#xml-sdk-tls). General improvements: - The Joda-Time library is upgraded to version 2.12.5. - The GraalJS library is upgraded to 22.3.3. ### [](#dataweave-features)DataWeave Features The 2.6.0 version of DataWeave introduces these new features and enhancements: Extended format support: - DataWeave now supports Java 17. See [Java Format](https://docs.mulesoft.com/dataweave/latest/dataweave-formats-java). - Mule expression language service are now modularized. ### Fixed Issues The release addresses the following Mule issues and incorporates all patch updates from the 4.5.0 Mule release through January 2023:
Issue Resolution ID

aspectj is now removed from distribution.

W-13913357

The Joda-Time library is upgraded to version 2.12.5.

W-13913362

The GraalJS library is upgraded to 22.3.3.

W-13961780

MUnit no longer fails with apps using Anypoint Connector for DotNet (DotNet Connector).

W-14747448

NullPointerException no longer occurs in XSD parsing when a schema has a minVersion/maxVersion.

W-14748090

Timeout is not considered for local transactions and rollbacks are silently executed.

W-14608096

MediaType cache now has a maximum size to prevent leaks.

W-14490182

DataWeave now uses objects as part of the Mule API.

W-14185880

License installation no longer fails with FileNotFoundException.

W-14542349

Legacy properties builder no longer reevaluates from root resolver placeholders.

W-14616618

JAVA_HOME is now properly handled by Surefire.

W-12082402

HTTP Redirect no longer works on Mule runtime 4.x on HTTP Post.

W-14619216

Race condition no longer results in NullPointerException when the Write Queue is full.

W-14543363

Container of the Embedded Runtime no longer stops if it wasn’t created.

W-14321634

Unnecessary MBeans for JMX management are no longer registered.

W-12422473

Internal dependency graph is now generated only once for all validations.

W-12421187

Extension model parsing no longer fails for extensions with dependencies declared as provided.

W-14646484
DataWeave 2.6.0 is bundled with the Mule 4.6.0 release. This release addresses the following DataWeave issues:
Issue Resolution ID

Caching now works correctly when coercing for addition and subtraction operations.

W-14591653

do scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.

W-14514837

The minInflateRatio property is now added to Excel format to control the zip bomb check threshold.

W-14315728
### [](#bundled-components)Bundled Components - DataWeave version 2.6.0 - Runtime Manager Agent plugin version 2.6.0 ### Upgrade If you are upgrading to this version of Mule from an earlier Mule 4.x version, see [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/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:
Module or Extension Version

APIkit for Mule 4

1.10.1

APIkit for OData

2.2.1

APIkit for OData 4

1.3.4

APIkit for SOAP

1.4.1

APIkit for GraphQL

1.0.0

Spring module

1.3.11

MUnit plugin

3.1.0
### [](#considerations-for-mule-extension-developers)Considerations for Mule Extension Developers If you update the version of your parent `pom.xml` file to 1.4.0 or later when you build a Mule extension, ensure that the dependencies in your `pom.xml` file do not override dependencies defined in the parent `pom.xml` file, and declare only the dependencies you need. If you need to declare a dependency that is already declared in the parent `pom.xml` file, do not specify a version so it uses the version from the parent `pom.xml` file. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [4.6@mule-runtime::mule-troubleshooting-plugin.adoc](#4.6@mule-runtime::mule-troubleshooting-plugin.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Engine 4.8.0 Release Notes 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. ## [](#june-2025)June 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.4.0 includes Runtime Manager agent 2.7.4. See [Runtime Manager Agent 2.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-4). ### Fixed Issues Patch release version: 4.8.6 This patch update addresses the following Mule issues:
Issue Resolution ID

A race condition introduced by W-17048606 no longer occurs, which caused the last part of the response body to be truncated when the streamResponse flag is set to true in request-connection.

W-17617940

Performance degradation no longer occurs when nonBlockingWriter is enabled for response streaming.

W-17627284

grizzly-ahc is upgraded in HTTP Service.

W-17667949

com.google.code.gson:gson is upgraded to 2.12.1.

W-17896347

Spring Framework artifacts are replaced with vendor-supported equivalents to improve long-term compatibility.

W-18462316

Performance during cache scope execution is now improved.

W-17671126

Serialization now works correctly with API Gateway internal classes.

W-16673760
DataWeave 2.8.4 is bundled with the Mule 4.8.6 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Performance issues no longer occur when using Message in DataWeave scripts.

W-18034217

The flat file module now supports YAML files with a nested depth greater than 50.

W-17495145

The warning message is now improved when a property isn’t defined on a given type.

W-16478114
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2025)February 2025 ### [](#patch-4-8-5)Patch 4.8.5 The February patch update 4.8.5 addresses a regression in the previous February patch update, 4.8.4, and includes the fixes in the patch. Patch release version: 4.8.5 This patch update addresses the following Mule issues:
Issue Resolution ID

ConfigurationException no longer occurs while performing Amazon DynamoDB Connector operations.

W-17801971
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-8-4)Patch 4.8.4 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.8.4 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). ### Fixed Issues Patch release version: 4.8.4 This patch update addresses the following Mule issues:
Issue Resolution ID

A ClassCastException thrown when an error occurs within an on-error-continue component no longer prevents transactions from rolling back.

W-17430963

The io.netty:netty-commonis is upgraded to 4.1.115.

W-17431962

InterceptionException is no longer thrown while running MUnit test containing a batch job.

W-17395302

The optimization to avoid sending body contents on NTLM type 1 requests added in W-17107281 is now controlled by the feature flag mule.ntlm.avoid.send.payload.on.type1.

W-17216089

Kryo serialization issue no longer occurs in Java 17 when running with distributed cluster using authentication, caching policy, and persistent Object Store.

W-16912085

The Xerces-J is upgraded to 2.12.2.

W-16980865

An infinite loop no longer occurs for a redelivery policy when the redelivery is exhausted in a source configured with transactions and On Error Propagate.

W-17405939

The installLicense option no longer fails to locate the license file when using a relative path.

W-17379726

API metrics are now properly sent.

W-17529530

Transactions initiated before a flow-ref call are now rolled back in the correct place if an error propagates from the flow-ref.

W-17453707

A corner case has been fixed and Anypoint Monitoring dashboard now correctly shows all metrics.

W-16828516
DataWeave 2.8.3 is bundled with the Mule 4.8.4 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2025)January 2025 ### [](#patch-4-8-3)Patch 4.8.3 - This patch update reverts the fixes for the following Mule issues: W-17107281 and W-17048606. - This patch update reverts the fixes for the following DataWeave issues: W-16823030, W-17206423, and W-17372664. ### [](#patch-4-8-2)Patch 4.8.2 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.8.2 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). ### Fixed Issues Patch release version: 4.8.2 This patch update addresses the following Mule issues:
Issue Resolution ID

Windows no longer throws cannot delete file errors during application undeploy.

W-17050930

BufferOverFlowException with inter-node communication getting stuck no longer occurs when using clusters with encryption under heavy load.

W-16517561

Unnecessary internal blocking operations no longer occur when handling large streamed HTTP responses.

W-17048606

Body content is no longer sent on Type 1 requests during NTLM authentication.

W-17107281

Deploying applications that contain XML SDK connectors no longer causes application class loader memory leak.

W-16814280

ConnectionException no longer occurs when using batch processing.

W-17008722

A memory leak no longer occurs when using mule-validation-module.

W-16789548

MessageProcessorNotificationListener is no longer called multiple times when running MUnit suites.

W-11866494

A serialization error no longer occurs in Java 17 when using clustering mode or Object Store v2.

W-17218707

IllegalAccessException is no longer thrown during cache scope serialization with Kryo.

W-17089503

All transactions running within a global Error Handler are now committed as expected.

W-16619771

NullPointerException no longer occurs when undeploying an application with native libraries in Windows OS.

W-16712841

com.hazelcast:hazelcast dependency is upgraded to 5.3.8.

W-16594688

NullPointerException is no longer thrown on HTTP requests that use config-ref with dynamic configuration.

W-16602622
DataWeave 2.8.2 is bundled with the Mule 4.8.2 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030

The Java reflection lookup strategy is now improved for bean instances.

W-17206423

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2024)November 2024 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.8.1 includes Runtime Manager agent 2.6.6. See [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6). ### Fixed Issues Patch release version: 4.8.1 This patch update addresses the following Mule issues:
Issue Resolution ID

Memory leak in MuleApplicationClassloader no longer occurs while undeploying an application.

W-16823349

A batch serialization error no longer occurs in Java 17 when one of the steps throws SQLException.

W-16546951

A deadlock no longer occurs when consuming the payload in the completion callback of the HTTP client sendAsync method.

W-16640190

Web Service Consumer Connector and RosettaNet Connector no longer fail when there’s an HTTP TLS transport configuration.

W-16288302

Log4j2 monorepo is upgraded to 2.24.1.

W-16889265

NullPointerException is no longer thrown when DataWeave transforms a RetryPolicyExhaustedException to a JSON format on a Java 17 runtime.

W-15643200

NullPointerException no longer occurs when undeploying an application with native libraries in Windows OS.

W-16712841

Kryo serialization issues no longer occur for rate limit policies using Java 17.

W-16843706
DataWeave 2.8.1 is bundled with the Mule 4.8.1 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The stripTrailingZeroes compatibility flag is now added to preserve the decimal format.

W-17030593

Apache POI folder used for temporal files is no longer deleted.

W-16899674

Using annotations without importing them now returns the corresponding error.

W-16853915
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-8-2024)October 8, 2024 ### What’s New The 4.8.0 version of Mule runtime introduces the following enhancements: Release cadence support coverage: - The LTS channel now offers 18 months of Standard Support and 6 months of Extended Support, with a six-month overlap between minor LTS versions, starting with Mule 4.6 LTS. The Edge channel now provides 5 months of Standard Support and 3 months of Extended Support, ensuring a one-month overlap between minor Edge versions, starting with Mule 4.8 Edge. See [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). Feature Flagging Mechanism: - Mule 4.8 incorporates new feature flags. See [Feature Flagging](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.8.0 includes Runtime Manager agent 2.6.5. See [Runtime Manager Agent 2.6.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-5). General improvements: - The `org.apache.maven.plugins:maven-compiler-plugin` dependency is upgraded to 3.13.0. - The `commons-io:commons-io` is upgraded to 2.16.1. - The `dependency org.jruby:jruby-complete` is upgraded to 9.4.7.0. - The `io.opentelemetry:opentelemetry-bom` is upgraded to 1.37.0. - The `org.springframework.security:spring-security-core` is upgraded to 5.7.12. - The `dependency com.google.code.gson:gson` is upgraded to 2.11.0. ### [](#dataweave-features)DataWeave Features The 2.8.0 version of DataWeave introduces these new features and enhancements: Reuse types: - DataWeave now supports reusing types from an Avro Schema. See [Reusing Types from an Avro Schema](https://docs.mulesoft.com/dataweave/latest/dataweave-type-reuse-avro-schema). General improvements: - DataWeave introduces support for metadata annotations. See [dataweave::dw-operators.adoc#metadata-annotations](https://docs.mulesoft.com/dataweave/latest/dw-operators#metadata-annotations). ### Fixed Issues The release addresses the following Mule issues and incorporates all patch updates from the 4.7.0 Mule release through September 2024:
Issue Resolution ID

The io.opentelemetry:opentelemetry-bom is upgraded to 1.37.0.

W-15478554

The org.springframework.security:spring-security-core is upgraded to 5.7.12.

W-15761385

The dependency com.google.code.gson:gson is upgraded to 2.11.0.

W-15838633

A validation is added to ensure that domains using the import target have the same top-level element as the importing file.

W-15509819

InitialisationException is no longer thrown when using the Raise Error component with an extra space at the end of the type field.

W-16237424

The configuration-properties encoding parameter is no longer ignored.

W-12228892

ChainInputResolver annotations are no longer ignored if there are no input, output, or metadata key resolvers.

W-16408471

Properties are now resolved during application packaging.

W-15959903

java.lang.InstantiationError : java.util.Map is no longer thrown when applying an authentication policy.

W-16595277

Fatal errors no longer occur when loading native libraries in Java 17.

W-16787783

When the feature flag anypoint.platform.keep.default.policy.format is set to true or the policy min Mule version is at least 4.5.0, the policy name format is ${policyName} @ ${artifactName} - ${flowName}.

W-16169887

The logging for the analytics .db files cleanup is now improved.

W-16624763

Mule Gateway applies Gatekeeper between editions of policy configuration.

W-16225792
DataWeave 2.8.0 is bundled with the Mule 4.8.0 release. This release addresses the following DataWeave issues:
Issue Resolution ID

Configuring a writer as deferred now requires Mule runtime privileges.

W-15398837

The avroschema! module loader is created to enable metadata extraction from Avro schemas.

W-15518930

Type error messages generated in Lambda functions are now improved.

W-16082839

Type inference is now improved when accessing properties of objects.

W-14222927

Type inference inside if/then branches is now improved.

W-15607520

The Avro type now maps to Java’s ArrayBuffer instead of BigDecimal.

W-15607759

The regression is now resolved allowing references to types defined later in the script.

W-15197016

Streaming capability for arguments at sum, countBy, and sumBy functions is now enabled.

W-16125755

Input/output MimeType properties are now preserved as expected.

W-16161736

Access error for Java 17 encapsulation errors is now improved.

W-15705596

Coercion error is now caught inside try as expected.

W-15323897
### [](#bundled-components)Bundled Components - DataWeave version 2.8.0 - Runtime Manager Agent plugin version 2.6.5 ### Upgrade If you are upgrading to this version of Mule from an earlier Mule 4.x version, see [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/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:
Module or Extension Version

APIkit for Mule 4

1.11.1

APIkit for OData

2.3.0

APIkit for OData 4

1.5.2

APIkit for SOAP

1.5.1

APIkit for GraphQL

1.1.0

Spring module

1.4.0

MUnit plugin

3.3.1
### [](#considerations-for-mule-extension-developers)Considerations for Mule Extension Developers If you update the version of your parent `pom.xml` file to 1.4.0 or later when you build a Mule extension, ensure that the dependencies in your `pom.xml` file do not override dependencies defined in the parent `pom.xml` file, and declare only the dependencies you need. If you need to declare a dependency that is already declared in the parent `pom.xml` file, do not specify a version so it uses the version from the parent `pom.xml` file. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Engine 4.9.0 Release Notes 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. ## [](#october-2026)October 2026 ### Fixed Issues ### [](#patch-4-9-23)Patch 4.9.23 The October patch update 4.9.23 addresses regressions in the October patch update 4.9.22.
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-9-22)Patch 4.9.22 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.22 includes Runtime Manager agent 2.8.5. See [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5). ### Fixed Issues Patch release version: 4.9.22 This patch update addresses these Mule issues:
Issue Resolution ID

The Reactor Core library is upgraded to 3.8.7.

W-23953702

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2026)September 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.21 includes Runtime Manager agent 2.8.4. See [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4). 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. - Health Signals: Evaluates a small set of fast host- and JVM-level health signals and reports those that triggered, including low memory, high CPU steal, and JVM crash logs. - Memory Detail: Provides a JVM memory-pool breakdown and garbage-collector statistics, showing heap and non-heap usage with metrics such as initial, used, committed, and maximum memory values. - Known Issues: Scans the runtime logs and deployed applications for well-known problem signatures, including out-of-memory conditions, abnormal terminations, and MUnit packaging issues. ### Fixed Issues Patch release version: 4.9.21 This patch update addresses these Mule issues:
Issue Resolution ID

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

The HTTP client configurer now includes a method to control whether sensitive headers are filtered when a request is redirected to a different domain.

W-21045658

A forward-proxy client no longer sends a malformed, path-only request line.

W-23384645

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540341

The RAML Parser library is upgraded to 2-1.2.1.

W-23328348

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

Worker TLS configuration for Government Cloud is strengthened.

W-23819316
DataWeave 2.9.18 is bundled with the Mule 4.9.21 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Vulnerable dependencies are upgraded to address reported security vulnerabilities.

W-23924223

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2026)August 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.20 includes Runtime Manager agent 2.8.3. See [Runtime Manager Agent 2.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-3). 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. - Network Info: Shows host-level network diagnostics, including the hostname, network interfaces with their assigned IP addresses and I/O counters, and active and listening network connections. - Agent Info: Reports the installation and health of the Mule agent that pairs the runtime with Anypoint Platform, including whether the agent is installed, its version, key configuration values, keystore certificate details, and the most recent connection status. - Platform Connectivity: Checks TCP connectivity from the Mule runtime host to the Anypoint Platform endpoints and dumps the TLS certificate chain presented by the platform. ### Fixed Issues Patch release version: 4.9.20 This patch update addresses these Mule issues:
Issue Resolution ID

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23131090
DataWeave 2.9.17 is bundled with the Mule 4.9.20 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2026)July 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.19 includes Runtime Manager agent 2.7.16. See [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). Feature Flagging Mechanism: - Mule 4.9 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.9.19 This patch update addresses these Mule issues:
Issue Resolution ID

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

The Content-Length header is now removed based on the actual entity byte length.

W-22570070

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

The Jackson Databind library is upgraded to 2.21.4.

W-3300013

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806027

The c3p0 library is upgraded to 0.14.1.

W-23012713

The Apache Neethi library is upgraded to 3.2.1.

W-22939389

The Apache CXF library is upgraded to 3.6.11.

W-23037617

The Rhino library is upgraded to 1.8.1.

W-22939391

The Log4j library is upgraded to 2.25.4.

W-22939403

The Reactor Netty library is upgraded to 1.2.18.

W-22939384

The Spring Framework is upgraded to 6.2.19.

W-22956997

The Netty library is upgraded to 4.2.15.Final.

W-22956998

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007
DataWeave 2.9.16 is bundled with the Mule 4.9.19 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2026)June 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.18 includes Runtime Manager agent 2.7.15. See [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15). ### Fixed Issues Patch release version: 4.9.18 This patch update addresses these Mule issues:
Issue Resolution ID

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971
DataWeave 2.9.15 is bundled with the Mule 4.9.18 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2026)May 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.17 includes Runtime Manager agent 2.7.13. See [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/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.9.17 This patch update addresses these Mule issues:
Issue Resolution ID

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21795152

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339
DataWeave 2.9.14 is bundled with the Mule 4.9.17 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2026)April 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.16 includes Runtime Manager agent 2.7.11. See [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11). Feature Flagging Mechanism: - Mule 4.9 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.9.16 This patch update addresses these Mule issues:
Issue Resolution ID

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

The Jackson Core library is upgraded to 2.18.6.

W-21420104

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340
DataWeave 2.9.13 is bundled with the Mule 4.9.16 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2026)March 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.15 includes Runtime Manager agent 2.7.10. See [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10). Feature Flagging Mechanism: - Mule 4.9 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.9.15 This patch update addresses these Mule issues:
Issue Resolution ID

The jakarta.mail library is upgraded to 1.6.8.

W-21138257

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

Errors that are not MessagingException errors are no longer silenced.

W-21043969

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." errors no longer occur when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900
DataWeave 2.9.12 is bundled with the Mule 4.9.15 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2026)February 2026 ### [](#patch-4-9-14)Patch 4.9.14 - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-9-13)Patch 4.9.13 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.13 includes Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues Patch release version: 4.9.13 This patch update addresses these Mule issues:
Issue Resolution ID

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

Fastutil is now replaced with fastutil-core.

W-20729870
DataWeave 2.9.11 is bundled with the Mule 4.9.13 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2026)January 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.12 includes Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). MUnit: - MUnit version 3.6.3 is now required. See [MUnit 3.6.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.3-release-notes). General improvements: - You can now view deployment information in the `diaf` file. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.9.12 This patch update addresses these Mule issues:
Issue Resolution ID

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469
DataWeave 2.9.10 is bundled with the Mule 4.9.12 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2025)November 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.11 includes Runtime Manager agent 2.7.8. See [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8). General improvements: - You can now view CPU usage information in the `diaf` file. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.9.11 This patch update addresses these Mule issues:
Issue Resolution ID

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

Starvation no longer occurs when sending HTTP responses that are generated slowly.

W-1982570

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.9, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953
DataWeave 2.9.9 is bundled with the Mule 4.9.11 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2025)October 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.10 includes Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). Mule Troubleshooting Plugin: - Mule 4.9.10 introduces the Mule Troubleshooting plugin, which generates a structured diagnostic archive (DIAF) to simplify troubleshooting, consolidate runtime metrics, and provide consistent data for MuleSoft Support. It works across all deployment models and helps investigate performance issues, application errors, and scheduler activity. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.9.10 This patch update addresses these Mule issues:
Issue Resolution ID

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The Handlebars library is upgraded to 4.4.0.

W-19064659

The org.apache.commons : commons-lang3 library is upgraded to 3.17.0.

W-19383955

The io.netty : netty-codec library is upgraded to 4.1.127.Final.

W-19568278

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

Scheduler name generation no longer breaks the platform logging aggregator when processor chains have null or empty names.

W-19432758

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164
DataWeave 2.9.8 is bundled with the Mule 4.9.10 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2025)September 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.9 includes Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues Patch release version: 4.9.9 This patch update addresses the following Mule issues:
Issue Resolution ID

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

io.projectreactor.netty : reactor-netty-http is upgraded to 1.2.8.

W-19074903

Component annotations, such as location, are no longer overwritten by other components.

W-18269859

org.apache.commons : commons-lang3 is upgraded to 3.18.0.

W-19059553
DataWeave 2.9.7 is bundled with the Mule 4.9.9 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

W-19376546
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2025)August 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.8 includes Runtime Manager agent 2.7.6. See [Runtime Manager Agent 2.7.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-6). General improvements: - License Delivery Update: Starting with Mule 4.9.8, Enterprise licenses are now provided either as a single `license.lic` file or as a `.zip` that contains both FIPS and non-FIPS licenses. See [FIPS 140-2 Compliance Support](https://docs.mulesoft.com/mule-runtime/latest/fips-140-2-compliance-support) for details. General improvements: - When running Mule runtime in FIPS security mode with clustering enabled, the encryption key defined in `mule.cluster.network.encryption.key` must have a length of 16, 24, or 32 bytes. See [Enable Clustering in FIPS Mode](https://docs.mulesoft.com/on-premises/latest/mule-high-availability-ha-clusters#cluster_fips) for details. ### Fixed Issues Patch release version: 4.9.8 This patch update addresses the following Mule issues:
Issue Resolution ID

Silent errors and hangs no longer occur when a component fails to start within a foreach/subflow combination.

W-18589595

An incorrect error level message no longer shows during deployment when using APIKit with no flow mappings.

W-19004884

Logging behavior when combining properties and expressions is reverted to the previous behavior.

W-18822321

Performance degradation no longer occurs when using repeatable streaming.

W-19175330

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
DataWeave 2.9.6 is bundled with the Mule 4.9.8 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

A stackOverflowException error no longer occurs during materialization.

W-18981240

The distinctBy function in dw::core::Core now works as expected when used with a CSV input.

W-18990604

DataWeave runtime types are now correctly written when outputting Java.

W-18942349

Access to multipart content raw value no longer reads the part content.

W-18892158

The sizeOf function now works correctly in DataWeave 2.6.14 and later.

W-18850597

The orderBy function now evaluates ordering criteria only when required.

W-18851259
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2025)July 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.7 includes Runtime Manager agent 2.7.5. See [Runtime Manager Agent 2.7.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-5). ### Fixed Issues Patch release version: 4.9.7 This patch update addresses the following Mule issues:
Issue Resolution ID

DataWeave now correctly serializes CompositeRoutingException to JSON.

W-16562974

The Parser Template now correctly resolves placeholder expressions.

W-16761707

The commons-beanutils:commons-beanutils library is upgraded to v1.11.0.

W-18687846

Repeatable streams now make data available before the buffer is full. To enable this behavior, set the system property mule.repeatableStreaming.bytes.eagerRead to true.

W-18716253

Schedulers are no longer triggered during graceful shutdown.

W-17981248

OAuth logging is now added when doing token update.

W-18622349

Serialization now works correctly with API Gateway internal classes.

W-18475283
DataWeave 2.9.5 is bundled with the Mule 4.9.7 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

This patch update reverts the fix.

W-17167283

XML encoding detection now works correctly when the declaration header is missing.

W-18853667

The fromCharCode function in dw::core::Strings. now manages surrogate characters correctly.

W-17204482

Unicode characters now render correctly at the beginning of the string when using the DataWeave writer function with the onlyData flag enabled.

W-14855645

The Apache POI library is now upgraded.

W-18253747

Experimental warning messages are no longer logged on DataWeave SDK files.

W-16384926
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2025)June 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.6 includes Runtime Manager agent 2.7.4. See [Runtime Manager Agent 2.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-4). General improvements: - Log4J is upgraded to 2.24.3. ### Fixed Issues Patch release version: 4.9.6 This patch update addresses the following Mule issues:
Issue Resolution ID

Loader constraint violation errors no longer occur when http-connector dependencies exist in both the domain and the policy.

W-17340911

Serialization of result objects with Kryo no longer fails with InaccessibleObjectException in Java 17.

W-17774685

Class loading no longer results in deadlocks caused by a race condition.

W-18388443

A serialization exception no longer occurs when using caching scope.

W-17703164

A classloader leak no longer occurs on undeployment when using lazy service initialization.

W-17750750

The mule.parse.template.use.legacy.default.targetValue compatibility switch is reintroduced to use the legacy default value for the targetValue parameter of the parse-template component. A one-time warning is now logged when enabled.

W-18324755

Preemtive analytics queue deletion is now added.

W-17529530
DataWeave 2.9.4 is bundled with the Mule 4.9.6 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

XML encoding is now detected before selecting a parser.

W-17637749

The performance of the orderBy function is now improved.

W-18439576

Reading a CSV file inside a MultiPart body now works correctly when performed more than once.

W-17147598

A memory leak of the binding context no longer occurs when using the foreach scope.

W-18472194

CompilationResult no longer retains a reference to the execution frame, which previously caused a memory leak.

W-18288980
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2025)May 2025 ### [](#patch-4-9-5)Patch 4.9.5 The May patch update 4.9.5 addresses a regression in the previous May patch update, 4.9.4, and includes the fixes in the patch. Patch release version: 4.9.5 This patch update addresses the following Mule issues:
Issue Resolution ID

Cluster discovery mechanism now works as expected on Runtime Fabric, CloudHub 2.0, and Anypoint Platform PCE environments, ensuring that schedulers are executed only on the primary node.

W-18528551
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-9-4)Patch 4.9.4 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.4 includes Runtime Manager agent 2.7.2. See [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2). ### Fixed Issues Patch release version: 4.9.4 This patch update addresses the following Mule issues:
Issue Resolution ID

Parallel For Each events no longer randomly timeout after a NullPointerException error.

W-17980769

The error message "Couldn’t parse instance of ReentrantReadWriteLock" in ReentrantReadWriteLockSerializer no longer occurs.

W-18057570

Parameters field isn’t serialized in InternalEventImplementation.

W-17703164

Connectivity tests in MTS are now fixed for Java 17.

W-18075077

Exceptions no longer occur when using WebSocket close codes outside a predefined subset. The code now correctly handles all standard/custom WebSocket close codes.

W-17846088

Configuration for preserveHeaderCase is now added in SseSource.

W-18085890

DefaultMessageBuilder no longer contains missing fields.

W-17607446

Contention between transaction and APIkit is now avoided due to tracing initialization.

W-18194349

A schedule is now added to consume the slowly populated pipe to an IO Executor.

W-17444122

org.glassfish:jakarta.json was removed form the distribution.

W-17896357

com.google.code.gson:gson is upgraded to 2.12.1.

W-17896347

com.google.protobuf:protobuf-java is upgraded to v3.25.6.

W-17986761

Custom notifications are now properly dispatched.

W-16091925
DataWeave 2.9.3 is bundled with the Mule 4.9.4 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Materialization issues no longer occur when using CSV content inside variables.

W-17167283

DataWeave now preserves trailing zeroes of single-element sum.

W-17283050

A compatibility flag is now added to address the different results produced by calling sizeOf with NumberType.

W-18020856

An unnecessary import is now removed from dw::util::Diff to eliminate a warning when running MUnit.

W-17670504

DataWeave no longer returns a format error on readUnquotedString.

W-18118138

Overflowing no longer occurs while reading large file on multipart format.

W-17644871

Performance issues no longer occur when using Message in DataWeave scripts.

W-18034217
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2025)April 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.3 includes Runtime Manager agent 2.7.2. See [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2). Enterprise Edition License: - The command `mule -verifyLicenseDetails [path_to_license]` that verifies the license before installing it is now added. See [Verify or Remove Enterprise Edition License](https://docs.mulesoft.com/on-premises/latest/installing-an-enterprise-license#verify-or-remove-enterprise-edition-license). MuleSoft Government Cloud support coverage: - Government Cloud now supports Mule runtime 4.9. See [Features Included in Government Cloud](https://docs.mulesoft.com/jp/gov-cloud/#features-included-in-government-cloud). ### Fixed Issues Patch release version: 4.9.3 This patch update addresses the following Mule issues:
Issue Resolution ID

The Netty codec library is now updated to 4.1.119.Final.

W-17980407

You can now use the mule --verifyLicenseDetails [path-to-license.lic] command to verify a given license file.

W-17340620

DuplicateMessageException is now correctly serialized with Kryo.

W-17844603

Error type in raise-error is now correctly resolved when defined with a static property.

W-17339304

org.apache.cxf:cxf-core is now upgraded to version 3.5.10.

W-17896358

The mule-sdk-api dependency now contains all the required license information.

W-18033237
DataWeave 2.9.2 is bundled with the Mule 4.9.3 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Concurrency issues no longer occur when loading modules.

W-17918619

The flat file module no longer fails when loading files with a nested depth greater than 50.

W-17495145

xerces-j is now updated to 2.12.2.

W-16918194
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2025)March 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.2 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). Feature Flagging Mechanism: - Mule 4.9 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.9.2 This patch update addresses the following Mule issues:
Issue Resolution ID

Resources are now properly released after a timeout when using the Scatter-Gather or Parallel For Each routers. The mule.forkJoin.completeChildContextsOnTimeout feature flag is now added to enable this behavior.

W-16941297

MessagingException can now be converted to JSON using DataWeave.

W-16629236

Performance degradation no longer occurs when the nonBlockingWriter is enabled for response streaming.

W-17627284

A race condition introduced by W-17048606 no longer occurs, where the last part of the response body was truncated when streamResponse flag is set to true in request-connection.

W-17617940

grizzly-ahc is now upgraded in HTTP Service.

W-17667949

When using sdk-api version of @Connection and ConnectionProvider in a source, a validation saying that @Connection can only be used with the extensions-api version of ConnectionProvider is no longer triggered.

W-17559243

Kryo serialization issue no longer occurs in Java 17 when running with distributed cluster using authentication, caching policy, and persistent Object Store.

W-16912085

Performance during cache scope execution is now improved.

W-17671126

The com.hazelcast:hazelcast dependency is downgraded to 5.2.5.

W-17905862
DataWeave 2.9.1 is bundled with the Mule 4.9.2 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Consuming values now work as expected when using overloaded materialized functions.

W-17588914
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2025)February 2025 ### [](#patch-4-9-1)Patch 4.9.1 The February patch update 4.9.1 addresses a regression in the previous February patch update, 4.9.0, and includes the fixes in the patch. Patch release version: 4.9.1 This patch update addresses the following Mule issues:
Issue Resolution ID

ConfigurationException no longer occurs while performing Amazon DynamoDB Connector operations.

W-17801971
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#february-6-2025)February 6, 2025 ### What’s New The 4.9.0 version of Mule runtime introduces the following enhancements: Java adoption: - In Mule 4.9.0 and later, you can compile any Mule project and additional dependencies for Java 17. - You can now run applications on Java 17 only. - This release supports auto minor upgrades for Java 17 apps between Mule 4.8 Edge and Mule 4.9 Edge, as well as from Mule 4.6 LTS to Mule 4.9 LTS. - Java 8 and 11 apps won’t be auto minor upgraded to Mule 4.9, so plan your upgrade path for apps that are running on Java 8 or 11 accordingly. Feature Flagging Mechanism: - Mule 4.9 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.9.0 includes Runtime Manager agent 2.6.7. See [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7). General improvements: - Mule 4.9 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. ### [](#dataweave-features)DataWeave Features The 2.9.0 version of DataWeave introduces these new features and enhancements: Extended format support: - DataWeave introduces support for the Event Stream format. See [Event Stream Format](https://docs.mulesoft.com/dataweave/latest/dataweave-formats-eventstream). General improvements: - DataWeave incorporates new system properties. See [DataWeave System Properties](https://docs.mulesoft.com/dataweave/latest/dataweave-system-properties). ### Fixed Issues The release addresses the following Mule issues and incorporates all patch updates from the 4.8.0 Mule release through January 2025:
Issue Resolution ID

Spring is upgraded to 6.2.0.

W-16639197

The org.jgrapht:jgrapht-core is upgraded to v1.5.2.

W-16494546

The com.github.ben-manes.caffeine:caffeine is upgraded to v3.

W-16494569

The plexus-component-annotations is upgraded to v2.2.0.

W-16541666

The org.apache.commons:commons-compress is upgraded to v1.27.0.

W-16515101

The com.hazelcast:hazelcast is upgraded to v5.4.0.

W-16594688

The Xerces-J is upgraded to v2.12.2.

W-16980865

The org.jetbrains:annotations is upgraded to v26.

W-16944403

The kotlin is upgraded to v2.

W-16908778

The org.togglz:togglz-core is upgraded to v4.

W-16881509

The graal-sdk is upgraded to v24.1.1.

W-16772392

The byteBuddy is upgraded to v1.15.1.

W-16778624

The org.apache.xmlbeans:xmlbeans is upgraded to v5.

W-15263392

The com.lmax:disruptor is upgraded to v4.

W-16514909

Compile target is now set to Java 17.

W-16045353

An error message now indicates if a classloader fails to be created for a service.

W-17244755
DataWeave 2.9.0 is bundled with the Mule 4.9.0 release. This release addresses the following DataWeave issues:
Issue Resolution ID

Java module now honors Java bean accessor methods.

W-17142345
### [](#bundled-components)Bundled Components - DataWeave version 2.9.0 - Runtime Manager Agent plugin version 2.6.7 ### Upgrade If you are upgrading to this version of Mule from an earlier Mule 4.x version, see [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/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:
Module or Extension Version

APIkit for Mule 4

1.11.3

APIkit for OData

2.3.0

APIkit for OData 4

1.5.2

APIkit for SOAP

1.6.0

APIkit for GraphQL

1.1.0

Spring module

1.4

MUnit plugin

3.4.0
### [](#considerations-for-mule-extension-developers)Considerations for Mule Extension Developers If you update the version of your parent `pom.xml` file to 1.4.0 or later when you build a Mule extension, ensure that the dependencies in your `pom.xml` file do not override dependencies defined in the parent `pom.xml` file, and declare only the dependencies you need. If you need to declare a dependency that is already declared in the parent `pom.xml` file, do not specify a version so it uses the version from the parent `pom.xml` file. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [4.9@mule-runtime::mule-troubleshooting-plugin.adoc](#4.9@mule-runtime::mule-troubleshooting-plugin.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Patch Update Release Notes for Mule Apps on Runtime Fabric These release notes describe monthly date-patch updates to the Mule runtime engine on Runtime Fabric. In addition to these release notes, see the [Anypoint Runtime Fabric release notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes) and the complete [Anypoint Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/) documentation. For further information on Mule runtime patch updates, see [Managing Mule runtime patch updates for Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/runtime-patch-updates). ## [](#mule-runtime-release-cadence-support)Mule Runtime Release Cadence Support This table shows the Mule runtime release cadence support for Runtime Fabric:
Mule Version Release Date Java Version End of Standard Support End of Extended Support

4.13 Edge

October 2026

17

March 2027

June 2027

4.12 Edge

June 2026

17

November 2026

February 2027

4.11 Edge

February 2026

17

July 2026

October 2026

4.10 Edge

October 2025

17

March 2026

June 2026

4.9 LTS

February 2025

17

August 2027

February 2028

4.9 Edge

February 2025

17

November 2025

February 2026

4.8 Edge

October 2024

8, 11, and 17

March 2025

June 2025

4.7 Edge

June 2024

8, 11, and 17

October 2024

February 2025

4.6 LTS

February 2024

8, 11, and 17

August 2026

February 2027

4.6 Edge

February 2024

8, 11, and 17

June 2024

October 2024

4.5 Edge

October 2023

8 and 11

February 2024

June 2024
MuleSoft provides an extended support window for version 4.6 LTS due to its compatibility with Java 8, 11, and 17.
Runtime Fabric doesn’t support Mule runtime engine version 4.6.x and later on Runtime Fabric 1.13.x appliance-based clusters. ## [](#runtime-fabric-release-monthly-cadence)Runtime Fabric Release Monthly Cadence This table shows the current schedule for monthly updates. Updates are packaged as `--`
Monthly updates 4.13 Edge Patch 4.12 Edge Patch 4.11 Edge Patch 4.9 LTS Patch 4.9 Edge Patch (EOL) 4.6 LTS Patch 4.6 Edge Patch (EOL) 4.4 Patch (EOL) 4.3 Patch (EOL)

October 2026

-

-

-

-

-

September 2026

-

4.12.3:4e-java17

-

4.9.21:4-java17

-

4.6.34:6-java17

4.6.34:6-java8

-

-

August 2026

-

4.12.2:8e-java17

4.11.6:7e-java17

4.9.20:9-java17

-

4.6.33:9-java17

4.6.33:9-java8

-

-

July 2026

-

4.12.1:4e-java17

4.11.6:4e-java17

-

-

-

June 2026

-

4.12.0:10e-java17

4.11.5:4e-java17

4.9.18:3-java17

-

4.6.31:3-java17

4.6.31:3-java8

-

-

May 2026

-

-

4.11.4:4e-java17

-

-

-

-

April 2026

-

-

4.11.3:4e-java17

4.9.16:4-java17

-

-

-

-

March 2026

-

-

4.11.2:3e-java17

4.9.15:3-java17

-

-

-

-

February 2026

-

-

-

-

-

January 2026

-

-

-

4.9.12:5-java17

4.9.12:5e-java17

-

-

-

December 2025

-

-

-

-

-

-

-

-

-

November 2025

-

-

-

-

-

October 2025

-

-

-

4.9.10:4-java17

4.9.10:4e-java17

-

4.4.0:20250919-3

-

September 2025

-

-

-

4.9.9:5-java17

4.9.9:5e-java17

-

4.4.0:20250829-1

-
- EOSS (End of Standard Support) - EOES (End of Extended Support) - EOL (End of Life)

The security fix SE-21834, from the August 3, 2021 patch release, disables TLS v1 and TLS v1.1 by default. When you deploy an application to Runtime Fabric, you can enable TLS v1 or TLS v1.1 using the following JVM args:

  • Enable TLS v1.0 and TLS v1.1: -Drtf.allow.TLSv1.0+

  • Enable TLS v1.1: -Drtf.allow.TLSv1.1

This change affects all Mule versions for Anypoint Runtime Fabric. Future patches to these releases and future minor releases of Mule will also incorporate this new default.
## [](#october-15-2026)October 15, 2026 ### What’s New **4.13.1, 4.12.5, 4.9.23, and 4.6.36 Runtime Updates** - This update addresses regressions introduced in the October release. - This release of 4.13.1, 4.12.5, and 4.9.23 includes Runtime Manager agent 2.8.5, and 4.6.36 includes Runtime Manager agent 2.7.20. For information, see [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) and [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20). ### Fixed Issues ### [](#patch-4-13-1-2e-java17)4.13.1:2e-java17 **4.13.1 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8
Issue Resolution ID

Mule

Applications no longer fail to deploy when the type of an on-error-propagate or on-error-continue is a property placeholder and the flow contains a component that supports streaming and requires a connection, such as an HTTP Request or Kafka operation.

W-24456406

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

Polling sources that use a CloudHub Object Store v2 for watermarks now track processed items in the object store’s configured partition instead of the default partition.

W-24459240

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-12-5-2e-java17)4.12.5:2e-java17 **4.12.5 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8
Issue Resolution ID

Mule

A JMS connection that doesn’t use XA transactions no longer logs an error, or fails application initialization, when the application doesn’t declare a bti:transaction-manager.

W-24443844

Configuring the DELTA aggregation temporality for metrics export now works when running on CloudHub, CloudHub 2.0, and Runtime Fabric.

W-24492022

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-9-23-4-java17)4.9.23:4-java17 **4.9.23 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-6-36-2-java17)4.6.36:2-java17 **4.6.36 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-6-36-2-java8)4.6.36:2-java8 **4.6.36 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452"
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
## [](#october-6-2026)October 6, 2026 ### What’s New - Mule runtime engine 4.13.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). - This release of 4.13.0, 4.12.4, and 4.9.22 includes Runtime Manager agent 2.8.5, and 4.6.35 includes Runtime Manager agent 2.7.20. For information, see [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) and [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20). ### Fixed Issues ### [](#patch-4-13-0-16e-java17)4.13.0:16e-java17 **4.13.0 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

The jsoup library is upgraded to 1.23.2.

W-23987955

The Jackson library is upgraded to 2.22.3.

W-24335732

The Reactor Core library is upgraded to 3.8.7.

W-23987958

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

The raml-parser-2 library is upgraded to 1.2.1.

W-23570110

Error-mapping preservation during error propagation is now enabled by default. An error whose type was already resolved inside a scope, including any remapping by an error mapping, now keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type. You can disable this behavior by setting the mule.honourErrorMappingsOnErrorPropagation system property to false.

W-23955755

OpenTelemetry metric exporters now support per-exporter view enrichment and resource attribute overrides.

W-23367495

JSON schema validation is migrated from the everit library to networknt, with everit retained as a fallback.

W-16530105

HTTP header values containing CR/LF characters are now sanitized instead of causing the request to be rejected.

W-22252135

minMuleVersion values are now normalized when loaded, preventing the patch or revision portion from being truncated.

W-24231362

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

Logging export reconfiguration is fixed for single application mode.

W-20908857

The ObjectStore API is extended with an upsert operation and an isThreadSafe indicator.

W-23090592

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809

A java.lang.UnsupportedClassVersionError thrown when a connector’s compiled target doesn’t match the running JVM is now handled gracefully.

W-24193358

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

A source policy that uses Async, Parallel For Each, or Scatter-Gather no longer builds its response from the failure response parameters instead of the success response parameters, and no longer silently drops the forked route’s response processing.

W-23938349

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

The commons-beanutils library and its transitive commons-collections 3.2.2 dependency are removed from Mule Runtime modules.

W-16918287

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

An unresolved placeholder in the meter-exporter configuration now degrades to its default value at tracer startup instead of causing a failure.

W-23650358

Dynamic reload of the metrics exporter configuration is now supported.

W-21921629

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

OutputHandler is deprecated and its support is removed.

W-23660888

A SerializationException now raises a MULE:SERIALIZATION error, instead of MULE:UNKNOWN.

W-21381359

The exporter-health backpressure-alert cadence for OpenTelemetry tracing, metrics, and logging is now configured through a single system property, mule.openTelemetry.meter.exporter.healthMetrics.alertingFrequency, instead of the separate per-signal metricsLogFrequency properties, which are deprecated and no longer consumed.

W-22193713

MULE:INVALID_INPUT_PARAM is now preserved as a suppressed error when a MULE:SOURCE_RESPONSE_GENERATE error occurs.

W-22293407

SDK parameter validation errors are now mapped to the MULE:INVALID_INPUT_PARAM error type.

W-2227652

Mule-generated tracing spans no longer truncate attribute values at OpenTelemetry’s default 128-character limit. Attribute values are now preserved up to 4096 characters before truncation.

W-20091299

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

SQSQueueManagementService is added to the serialization allowlist.

W-24197744

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401

DataWeave

Memory usage for text/plain output is reduced.

W-20063270

Eagerly materialize executable Weave reader results.

W-23837275

Thread safety is improved when processing Java map values.

W-23661641

DataWeave tooling now reports design-time warnings when Java classes referenced in application/java schemas can’t be found or are inaccessible through JPMS.

W-22797049

DataWeave now filters Java classes in JPMS-unexported packages during Java module resolution, preventing runtime IllegalAccessException failures. This behavior is enabled by default on JDK 17 and later with DataWeave language version 2.13 and later. To keep the previous behavior, set mule.dw.filter_jpms_inaccessible_modules=false.

W-22779527

Cryptographic security warnings and errors now include call stacks.

W-22144340
### [](#patch-4-12-4-9e-java17)4.12.4:9e-java17 **4.12.4 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

The Log4j library is upgraded to 2.26.1.

W-24061648

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

OpenTelemetry flow-statistics counters now emit one datapoint per flow, labeled with the mule.flow.name dimension, instead of a single artifact-level total. You can disable this behavior by setting the mule.enable.otel.flow.statistics.detailed system property to false.

W-23616483

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

Network information listening ports are now scoped to the Mule process.

W-24043880

OpenTelemetry metrics export now supports delta aggregation temporality.

W-23448781

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The OpenTelemetry exporter TLS property mule.openTelemetry.exporter.tls.certificatesStrategy is now properly resolved.

W-24009827

On CloudHub 2.0 and Runtime Fabric deployments, container logs exported through OpenTelemetry now correctly use the deployed application’s configured service name, instead of the generic mule-container name.

W-23734353

OpenTelemetry flow statistics counters now report total flow counts as well as per-flow totals.

W-23232729

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

Client-side read backpressure is now applied to streamed HTTP responses, preventing out-of-memory errors when consuming large response bodies.

W-24103497

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Unresolved placeholders in Batch AST properties no longer cause a ClassCastException during packaging validation.

W-24088827

In a clustered deployment, the DiscoverySPI HTTP client no longer fails to start when PCF or Kubernetes discovery is configured through the .mule/mule-cluster.properties file instead of a JVM system property.

W-24211100

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244

Netty’s Java Flight Recorder (JFR) integration is now disabled by default.

W-20926401

An omitted eagerRead attribute on <repeatable-in-memory-stream> now correctly takes its default value from the mule.repeatableStreaming.bytes.eagerRead system property, instead of a fixed value.

W-24043809
### [](#patch-4-9-22-8-java17)4.9.22:8-java17 **4.9.22 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

The Reactor Core library is upgraded to 3.8.7.

W-23953702

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. You can change this behavior by configuring the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
### [](#patch-4-6-35-4-java17)4.6.35:4-java17 **4.6.35 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

The Reactor Core library is upgraded to 3.8.7.

W-3300013

The Jackson library is upgraded to 2.22.2.

W-23947149

The jsoup library is upgraded to 1.23.2.

W-23987949

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

An SDK API for queues (VM usage) and core adapters is added.

W-19439432

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. To change the behavior, configure the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
### [](#patch-4-6-35-4-java8)4.6.35:4-java8 **4.6.35 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

The Reactor Core library is upgraded to 3.8.7.

W-3300013

The Jackson library is upgraded to 2.22.2.

W-23947149

The jsoup library is upgraded to 1.23.2.

W-23987949

Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.

W-23955755

A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

An SDK API for queues (VM usage) and core adapters is added.

W-19439432

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. To change the behavior, configure the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
## [](#september-4-2026)September 4, 2026 ### What’s New - This release of 4.12.3 and 4.9.21 includes Runtime Manager agent 2.8.4, and 4.6.34 includes Runtime Manager agent 2.7.16. For information, see [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4) and [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). ### Fixed Issues ### [](#patch-4-12-3-4e-java17)4.12.3:4e-java17 **4.12.3 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23671475

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

FileNotFoundException no longer happens when trying to load a BCFKS truststore in FIPS mode.

W-24059868

DataWeave

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
### [](#patch-4-9-21-4-java17)4.9.21:4-java17 **4.9.21 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

The HTTP client configurer now includes a method to control whether sensitive headers are filtered when a request is redirected to a different domain.

W-21045658

A forward-proxy client no longer sends a malformed, path-only request line.

W-23384645

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Netty library is upgraded to 4.2.17.Final.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540341

The RAML Parser library is upgraded to 2-1.2.1.

W-23328348

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

FileNotFoundException no longer happens when trying to load a BCFKS truststore in FIPS mode.

W-24059868

DataWeave

Vulnerable dependencies are upgraded to address reported security vulnerabilities.

W-23924223

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
### [](#patch-4-6-34-6-java17)4.6.34:6-java17 **4.6.34 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.18+8 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Apache Commons Compress library is upgraded to 1.26.0.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540335

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

FileNotFoundException no longer happens when trying to load a BCFKS truststore in FIPS mode.

W-24059868

DataWeave

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
### [](#patch-4-6-34-6-java8)4.6.34:6-java8 **4.6.34 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Apache Commons Compress library is upgraded to 1.26.0.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540335

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531

FileNotFoundException no longer happens when trying to load a BCFKS truststore in FIPS mode.

W-24059868

DataWeave

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
## [](#august-12-2026)August 12, 2026 ### What’s New - This release of 4.12.2, 4.11.6, and 4.9.20 includes Runtime Manager agent 2.8.3, and 4.6.33 includes Runtime Manager agent 2.7.18. For information, see [Runtime Manager Agent 2.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-3) and [Runtime Manager Agent 2.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-18). ### Fixed Issues ### [](#patch-4-12-2-8e-java17)4.12.2:8e-java17 **4.12.2 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

Lazy initialization no longer fails with a NullPointerException when an application using the VM connector’s publish operation also configures a global error handler.

W-23156632

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

An HTTP request client connecting through a proxy no longer hangs when the proxy responds with a 407 (Proxy Authentication Required) response during the CONNECT tunnel handshake.

W-23384719

The HTTP request client now sends a correctly formed request line when connecting through a forward proxy.

W-23384645

A NullPointerException no longer occurs when the HTTP request client reuses a pooled connection to a forward proxy.

W-23384744

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Batch module now provides a public API to configure a custom queue manager and queue timeout.

W-23371797

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Sec-WebSocket-Protocol header is now forwarded on outbound WebSocket connections, so subprotocol negotiation with the server succeeds.

W-23071781

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API Gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23165634

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

Type metadata processing now correctly handles sibling references that target the same type, preventing duplicate annotations.

W-23424037

DataWeave now handles Java Platform Module System (JPMS) access restrictions more gracefully when running on Java 17 and later in Mule runtime 4.6.0 and later.

W-23354139

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
### [](#patch-4-11-6-7e-java17)4.11.6:7e-java17 **4.11.6 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` - Updated to the latest operating system security patches. ### [](#patch-4-9-20-9-java17)4.9.20:9-java17 **4.9.20 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23131090

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

W-22417507
### [](#patch-4-6-33-9-java17)4.6.33:9-java17 **4.6.33 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23121654

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592
### [](#patch-4-6-33-9-java8)4.6.33:9-java8 **4.6.33 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` This release includes security updates.
Issue Resolution ID

Mule

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23121654

DataWeave

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592
## [](#july-14-2026)July 14, 2026 The July 14 patch update 4.9.19:9-java17, 4.6.32:5-java17, and 4.6.32:5-java8 addresses an issue in the previous July 7 patch update and includes the fixes in those patches. ### [](#patch-4-9-19-9-java17)4.9.19:9-java17 **4.9.19 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

The runtime no longer logs this warning:

Cannot start plugin 'rtf-cluster-server-plugin'. Plugin will be unregistered
java.lang.reflect.UndeclaredThrowableException

W-23373633
### [](#patch-4-6-32-5-java17)4.6.32:5-java17 **4.6.32 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

The runtime no longer logs this warning:

Cannot start plugin 'rtf-cluster-server-plugin'. Plugin will be unregistered
java.lang.reflect.UndeclaredThrowableException

W-23373633
### [](#patch-4-6-32-5-java8)4.6.32:5-java8 **4.6.32 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

The runtime no longer logs this warning:

Cannot start plugin 'rtf-cluster-server-plugin'. Plugin will be unregistered
java.lang.reflect.UndeclaredThrowableException

W-23373633
## [](#july-7-2026)July 7, 2026 ### What’s New - Runtime Manager agent 2.7.16. See [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). ### Fixed Issues ### [](#patch-4-12-1-4e-java17)4.12.1:4e-java17 **4.12.1 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Clustered applications deployed with two or more replicas no longer fail to start with a NullPointerException error during cluster node discovery.

W-22843942

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Object Store retrieved from the registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

The error type in the EE cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Test Connection for the HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the host field.

W-21921687

HTTP Server now supports upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

In-memory Object Store partitions are now created correctly when an application is deployed to a cluster with the Object Store plugin enabled.

W-17714668

Deserialization errors no longer occur in the Object Store during a runtime patch upgrade.

W-20880559

Applications deployed with a serialized AST now include all Mule error types in the error type repository.

W-22399271

Applications that use HTTP request attributes no longer fail annotation processing due to default constructor validation.

W-22385620

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

OpenTelemetry flow statistics now report metrics correctly for applications with more than one flow.

W-23051614

The artifact type (domain, policy, or application) is now included as an OpenTelemetry resource attribute.

W-21768636

OpenTelemetry metric attribute names now use a consistent notation.

W-21921584

The mule.openTelemetry.logging.exporter.resource.container.service.name system property is now available to set the service name that the Mule container reports for OpenTelemetry telemetry.

W-22861497

Event dumps now include a state for events that are waiting on a non-blocking operation.

W-22142952

The Netty library is upgraded to 4.2.15.Final.

W-22831076

The c3p0 library is upgraded to 0.14.1.

W-22990155

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The Reactor Netty library is upgraded to 1.3.6.

W-3300013

The Jackson Core library is upgraded to 2.21.1.

W-22839747

The Apache Neethi library is upgraded to 3.2.1.

W-22839752

The OpenTelemetry API library is upgraded to 1.62.0.

W-22849469

The Spring Framework is upgraded to 6.2.19.

W-22939417

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344
### [](#patch-4-11-6-4e-java17)4.11.6:4e-java17 **4.11.6 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The c3p0 library is upgraded to 0.14.1.

W-22990152

The Spring Framework is upgraded to 6.2.19.

W-3300013

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806044

The Netty library is upgraded to 4.2.15.Final.

W-22888966

The Reactor Netty library is upgraded to 1.3.6.

W-22939412

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
### [](#patch-4-9-19-8-java17)4.9.19:8-java17 **4.9.19 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

The Content-Length header is now removed based on the actual entity byte length.

W-22570070

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

The Jackson Databind library is upgraded to 2.21.4.

W-3300013

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806027

The c3p0 library is upgraded to 0.14.1.

W-23012713

The Apache Neethi library is upgraded to 3.2.1.

W-22939389

The Apache CXF library is upgraded to 3.6.11.

W-23037617

The Rhino library is upgraded to 1.8.1.

W-22939391

The Log4j library is upgraded to 2.25.4.

W-22939403

The Reactor Netty library is upgraded to 1.2.18.

W-22939384

The Spring Framework is upgraded to 6.2.19.

W-22956997

The Netty library is upgraded to 4.2.15.Final.

W-22956998

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
### [](#patch-4-6-32-4-java17)4.6.32:4-java17 **4.6.32 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

A NullPointerException error no longer occurs in event context handling when a flow times out while a non-blocking operation is still in flight.

W-22902839

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The Joda-Time library is upgraded to 2.13.0.

W-3300013

The Rhino library is upgraded to 1.7.15.1.

W-22805996

The Apache Neethi library is upgraded to 3.2.1.

W-22805997

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806011

The Apache CXF library is upgraded to 3.5.11.

W-23037585

The c3p0 library is upgraded to 0.14.1.

W-23012711

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

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 per_app_java_bean_cache compatibility flag.

W-22417507
### [](#patch-4-6-32-4-java8)4.6.32:4-java8 **4.6.32 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

A NullPointerException error no longer occurs in event context handling when a flow times out while a non-blocking operation is still in flight.

W-22902839

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate Host header, in compliance with RFC 9112.

W-23052713

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The Joda-Time library is upgraded to 2.13.0.

W-3300013

The Rhino library is upgraded to 1.7.15.1.

W-22805996

The Apache Neethi library is upgraded to 3.2.1.

W-22805997

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806011

The Apache CXF library is upgraded to 3.5.11.

W-23037585

The c3p0 library is upgraded to 0.14.1.

W-23012711

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007

DataWeave

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

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 per_app_java_bean_cache compatibility flag.

W-22417507
## [](#june-2-2026)June 2, 2026 ### What’s New - Mule runtime engine 4.12.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). - Runtime Manager agent 2.7.15. See [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15). ### Fixed Issues ### [](#patch-4-12-0-10e-java17)4.12.0:10e-java17 **4.12.0 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Upstream HTTP requests are now cancelled when a downstream client disconnects, preventing unnecessary data transfer.

W-20084343

The Netty HTTP client no longer throws NullPointerException when handling Expect 100-Continue responses.

W-21513490

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

The Apache CXF library is upgraded to 3.6.8.

W-20541600

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

Redelivery policy logging now includes additional context for troubleshooting.

W-20636028

The Tanuki Java Service Wrapper is upgraded to 3.6.4.

W-17051070

The RAML parser is upgraded to 1.1.10.

W-21768014

The OpenTelemetry SDK is upgraded to 1.60.1.

W-21808539

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

DataWeave now supports the private modifier on fun, var, ns, and type declarations to hide them from importers.

W-21148967

internal is no longer a reserved word and can now be used as an identifier in DataWeave scripts.

W-21508044

The compiler now reports an error when overloads of the same function declare different visibility modifiers.

W-21362539

StackOverflowError no longer occurs in the type checker when resolving intersections of unbound type parameters.

W-20124753

Runtime errors no longer occur when invoking overloaded functions across modules.

W-21811015

Spurious type-check errors no longer occur when an optional key-value pair is assigned to a required one.

W-21351058

deferred values passed to the write function now terminate correctly.

W-20925604

Out-of-memory errors no longer occur when reading large text or CDATA sections with the indexed XML reader.

W-21006104

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
### [](#patch-4-11-5-4e-java17)4.11.5:4e-java17 **4.11.5 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

HTTP Server now supports Upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Test Connection for The HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the Host field.

W-21921687

The Spring Core library is upgraded to 6.2.18.

W-22169898

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
### [](#patch-4-9-18-3-java17)4.9.18:3-java17 **4.9.18 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

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 per_app_java_bean_cache compatibility flag.

W-22417507
### [](#patch-4-6-31-3-java17)4.6.31:3-java17 **4.6.31 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

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 per_app_java_bean_cache compatibility flag.

W-22417507
### [](#patch-4-6-31-3-java8)4.6.31:3-java8 **4.6.31 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971

DataWeave

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 per_app_java_bean_cache compatibility flag.

W-22417507
## [](#may-19-2026)May 19, 2026 The May 19 patch update 4.9.17:5-java17, 4.6.30:5-java17, 4.6.30:5-java8 addresses a regression in the previous May 5 patch update and includes the fixes in those patches. ### [](#patch-4-9-17-5-java17)4.9.17:5-java17 **4.9.17 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Incoming header names no longer use strict CRLF validation when an HTTP configuration without a listener receives an HTTPS request, avoiding out-of-memory errors. In this scenario, Mule logs a warning entry in mule_ee.log, but the warning doesn’t affect application behavior.

W-22571733
### [](#patch-4-6-30-5-java17)4.6.30:5-java17 **4.6.30 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Incoming header names no longer use strict CRLF validation when an HTTP configuration without a listener receives an HTTPS request, avoiding out-of-memory errors. In this scenario, Mule logs a warning entry in mule_ee.log, but the warning doesn’t affect application behavior.

W-22571733
### [](#patch-4-6-30-5-java8)4.6.30:5-java8 **4.6.30 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Incoming header names no longer use strict CRLF validation when an HTTP configuration without a listener receives an HTTPS request, avoiding out-of-memory errors. In this scenario, Mule logs a warning entry in mule_ee.log, but the warning doesn’t affect application behavior.

W-22571733
## [](#may-5-2026)May 5, 2026 ### What’s New - Runtime Manager agent 2.7.13. See [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13). - The Anypoint Monitoring Sidecar now supports 64-bit systems. ### Fixed Issues ### [](#patch-4-11-4-4e-java17)4.11.4:4e-java17 **4.11.4 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

Netty HTTP client NTLM authentication no longer fails due to missing TCP connection affinity during the handshake.

W-21615520

The plexus-utils library is upgraded to 4.0.3.

W-21774430

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21913252

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

Netty HTTP client no longer sends an incorrect WWW-Authenticate header during the NTLM authentication handshake.

W-21762949

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

A serialization error that could occur when deserializing data after a Mule runtime upgrade no longer occurs.

W-21951097

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
### [](#patch-4-9-17-4-java17)4.9.17:4-java17 **4.9.17 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21795152

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
### [](#patch-4-6-30-4-java17)4.6.30:4-java17 **4.6.30 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
### [](#patch-4-6-30-4-java8)4.6.30:4-java8 **4.6.30 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.33` This release includes security updates.
Issue Resolution ID

Mule

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339

DataWeave

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
## [](#april-7-2026)April 7, 2026 ### What’s New Runtime Manager agent 2.7.11. See [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11). ### Fixed Issues ### [](#patch-4-11-3-4e-java17)4.11.3:4e-java17 **4.11.3 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

OpenTelemetry Direct streaming now supports FIPS-compatible keystore format.

W-20623905

A warning now appears when an OpenTelemetry property is incorrectly used as a deployment property.

W-21018072

NullPointerException 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.

W-20192960

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

HTTP Netty implementation performance is now improved.

W-20969515

HTTP Server no longer logs an error when a client closes an idle keep-alive connection.

W-21431822

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
### [](#patch-4-9-16-4-java17)4.9.16:4-java17 **4.9.16 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

The Jackson Core library is upgraded to 2.18.6.

W-21420104

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
### [](#patch-4-6-29-6-java17)4.6.29:6-java17 **4.6.29 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
### [](#patch-4-6-29-6-java8)4.6.29:6-java8 **4.6.29 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException 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 dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

DataWeave

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
## [](#march-3-2026)March 3, 2026 ### What’s New Runtime Manager agent 2.7.10. See [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10). ### Fixed Issues ### [](#patch-4-11-2-3e-java17)4.11.2:3e-java17 **4.11.2 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

XSD validations are now enabled by default during deployment.

W-21139633

Errors that are not MessagingException errors are no longer silenced.

W-21043969

The reactor.netty.version library is upgraded to 1.3.2.

W-3300013

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501

The Mapping Editor API now supports attributes in Anypoint Code Builder.

W-20662336

Updating the expression model in the Mapping Editor API now works correctly.

W-20611263
### [](#patch-4-10-5-2e-java17)4.10.5:2e-java17 **4.10.5 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

Streaming manager initialization failures no longer occur in certain scenarios.

W-20641469

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
### [](#patch-4-9-15-3-java17)4.9.15:3-java17 **4.9.15 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

The jakarta.mail library is upgraded to 1.6.8.

W-21138257

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

Errors that are not MessagingException errors are no longer silenced.

W-21043969

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." errors no longer occur when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
### [](#patch-4-6-28-3-java17)4.6.28:3-java17 **4.6.28 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The tika-core library is upgraded to 3.2.3.

W-21179465

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
### [](#patch-4-6-28-3-java8)4.6.28:3-java8 **4.6.28 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.24` This release includes security updates.
Issue Resolution ID

Mule

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The tika-core library is upgraded to 3.2.3.

W-21179465

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900

DataWeave

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501
## [](#february-14-2026)February 14, 2026 ### Fixed Issues ### [](#patch-4-11-1-2e-java17)4.11.1:2e-java17 **4.11.1 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-10-4-1e-java17)4.10.4:1e-java17 **4.10.4 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-9-14-1e-java17)4.9.14:1e-java17 **4.9.14 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-9-14-1-java17)4.9.14:1-java17 **4.9.14 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-6-27-1-java17)4.6.27:1-java17 **4.6.27 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-6-27-1-java8)4.6.27:1-java18 **4.6.27 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.41` - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ## [](#february-4-2026)February 4, 2026 ### What’s New - Mule runtime engine 4.11.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues ### [](#patch-4-11-0-10e-java17)4.11.0:10e-java17 **4.11.0 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.23` This release includes security updates.
Issue Resolution ID

Mule

HTTP/2 connections now correctly multiplex when processing concurrent requests, reducing connection creation and latency.

W-19860076

The runtime now leverages the AST file for applications with the until-successful component instead of parsing configuration XML files.

W-20283146

Batch record deserialization no longer fails when a Netty exception occurs.

W-20552358

Inbound HTTP/2 header validation is now improved.

W-19873453

The org.apache.logging.log4j:log4j-core dependency is upgraded to 2.25.3.

W-20679050

DataWeave

AST scope navigation now works correctly for cross-file references when using the Tooling API.

W-20212809

A specific overload for isEmpty on binaries is now available to prevent implicit coercion to other types.

W-20049958

Materialized Java values are now cached to allow multiple executions using the same value.

W-20091279

Semantic tokens are now supported in the Tooling API.

W-19846990

NullPointerException no longer occurs when handling annotation types.

W-19853000

LogLevel documentation is now included directly in the code.

W-17800393

The commons-beanutils library is upgraded.

W-3300013

Base64 encoding and decoding now support payloads larger than memory.

W-18575719

Eager materialization is now supported on values, enabling caching of all exceptions inside the try function.

W-19717874

Avro enum, map, union, and fixed types are now supported as top-level elements.

W-19596039

WeaveCompiler now allows precompiling mappings and modules without validation or type checking.

W-19667273

Type check errors are now correctly reported when resolving type checking on subgraphs.

W-19564697

Lazy loading of source files is now enabled during binary compilation, avoiding unnecessary memory usage.

W-19594703

Type inference now works correctly when using the -- operator to subtract a key from an object.

W-19595907

Warning and error messages now propagate correctly between compilation phases.

W-19386849

Base types are now used to validate accepted values, preventing premature materialization.

W-18943395

Optional types now propagate correctly through chains of value selectors.

W-19272070

The syntax version is now added to TypeGraph and WeaveTypeResolution.

W-19271992

The classloader resource resolver now resolves paths correctly on Windows systems.

W-19407283
## [](#february-3-2026)February 3, 2026 ### What’s New Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues ### [](#patch-4-10-3-2e-java17)4.10.3:2e-java17 **4.10.3 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.23` This release includes security updates.
Issue Resolution ID

Mule

HTTP/2 handling now correctly multiplexes connections during concurrent request processing. Previously, a failure to multiplex caused excessive connection creation and significantly increased latency.

W-19860076

Improved the validation logic for inbound HTTP/2 headers to ensure better protocol compliance and security.

W-19873453

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

The org.apache.cxf:cxf-core library is upgraded to 3.6.9.

W-20659822

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
### [](#patch-4-9-13-2e-java17)4.9.13:2e-java17 **4.9.13 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.23` This release includes security updates.
Issue Resolution ID

Mule

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

Fastutil is now replaced with fastutil-core.

W-20729870

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
### [](#patch-4-9-13-2-java17)4.9.13:2-java17 **4.9.13 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.23` This release includes security updates.
Issue Resolution ID

Mule

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

The org.apache.logging.log4j:log4j-core library is upgraded to 2.25.3.

W-20679050

Fastutil is now replaced with fastutil-core.

W-20729870

DataWeave

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
### [](#patch-4-6-26-2-java17)4.6.26:2-java17 **4.6.26 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.23` This release includes security updates.
Issue Resolution ID

Mule

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Fastutil is now replaced with fastutil-core.

W-20729870
### [](#patch-4-6-26-2-java8)4.6.26:2-java8 **4.6.26 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.23` This release includes security updates.
Issue Resolution ID

Mule

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Fastutil is now replaced with fastutil-core.

W-20729870
## [](#january-6-2026)January 6, 2026 ### What’s New Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). ### Fixed Issues ### [](#patch-4-10-2-5e-java17)4.10.2:5e-java17 **4.10.2 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing not longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

A memory leak after application undeployment no longer occurs when using connections from configurations defined in a domain.

W-13521171

Connections now close properly on the server side after an HTTP/2 client disconnects.

W-19861068

The JMS connector no longer closes XA-enlisted connections.

W-20266983

Connections from providers that implement both CachedConnectionProvider and XaTransactionalConnectionProvider are no longer cached if the provided connection is XA.

W-20267068

The alert context in the DIAF file is now reset after the configured time interval expires.

W-20140036

The HTTP Server now returns a 400 error when the HTTP/1 to HTTP/2 upgrade mechanism receives an invalid HTTP2-Settings header.

W-19895731

ERROR StatusLogger Attempted to append to non-started appender AnypointMonitoringFileAppender errors no longer occur when Anypoint Monitoring is enabled.

W-15577414

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The Apache Commons Lang library included in the distribution is upgraded.

W-20004786

DataWeave grammar transformation performance is improved.

W-19840284

Memory usage is improved for binary compilation and AST-related utilities.

W-19706956
### [](#patch-4-9-12-5e-java17)4.9.12:5e-java17 **4.9.12 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

ERROR StatusLogger Attempted to append to non-started appender AnypointMonitoringFileAppender errors no longer occur when Anypoint Monitoring is enabled.

W-15577414

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549
### [](#patch-4-9-12-5-java17)4.9.12:5-java17 **4.9.12 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

ERROR StatusLogger Attempted to append to non-started appender AnypointMonitoringFileAppender errors no longer occur when Anypoint Monitoring is enabled.

W-15577414

DataWeave

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

The stream reader now processes input with multi-byte characters correctly.

W-20016549
### [](#patch-4-6-25-5-java17)4.6.25:5-java17 **4.6.25 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

DataWeave

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20618375

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
### [](#patch-4-6-25-5-java8)4.6.25:5-java8 **4.6.25 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469

DataWeave

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20618375

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
## [](#november-7-2025)November 7, 2025 The November 7 patch update 4.10.1:12e-java17, 4.9.11:6e-java17, 4.9.11:6-java17, 4.6.24:7-java17, 4.6.24:7-java8, and 4.4.0:20250919-6 address a regression in the previous November 4 patch update and includes the fixes in those patches. ### [](#patch-4-10-1-12e-java17)4.10.1:12e-java17 **4.10.1 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

The diagnostic file now generates correctly.

W-20139801

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
### [](#patch-4-9-11-6e-java17)4.9.11:6e-java17 **4.9.11 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

The diagnostic file now generates correctly.

W-20139801

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
### [](#patch-4-9-11-6-java17)4.9.11:6-java17 **4.9.11 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

The diagnostic file now generates correctly.

W-20139801

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
### [](#patch-4-6-24-7-java17)4.6.24:7-java17 **4.6.24 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

The diagnostic file now generates correctly.

W-20139801

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
### [](#patch-4-6-24-7-java8)4.6.24:7-java8 **4.6.24 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
### [](#patch-4-4-0-20250919-6)4.4.0:20250919-6 **4.4.0 Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

Readiness and liveness probes now use HTTP GET checks instead of command-based checks, improving reliability.

W-19853421
## [](#november-4-2025)November 4, 2025 ### What’s New Runtime Manager agent 2.7.8. See [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8). ### Fixed Issues ### [](#patch-4-10-1-10e-java17)4.10.1:10e-java17 **4.10.1 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.10, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.1.127.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

The Bump handlebars library is upgraded to 4.4.0.

W-1906465

The HTTP listener now correctly populates attributes.queryParams when using HTTP/2.

W-19802358

close_notify events sent by a server are now properly handled by the HTTP/2 client.

W-19973575

DataWeave

Materialization errors no longer occur in run function.

W-19884071

The org.apache.commons:commons-lang3 library is upgraded to 3.18.

W-19803454

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

The SnakeYAML library is upgraded.

W-19749213

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283

The -- operator now returns the correct type without the subtracted keys.

W-19595907

Debug logging is now enabled for DefaultLoggingService.

W-19650046

The take function no longer fails in streaming mode when n is larger than the array length.

W-19168279

The Java Module now supports object field access with different capitalizations.

W-19477334

The Runtime Compiler now uses the Parser Manager to look for resources provided as parameters.

W-19376888

A null check is now performed before closing the InputStream.

W-19395982

Parsing metrics printing now includes a missing line ending.

W-19440583

Constants are now used to prevent incorrect loader identifiers for binary compiled scripts.

W-18455133

Generated POM files now include license information.

W-19439330

SchemaProvider resolution on Types is improved to prevent Execution reference leaks.

W-19389019

The classloader weave resource resolver now uses the correct path in Windows environments.

W-19407283
### [](#patch-4-9-11-4e-java17)4.9.11:4e-java17 **4.9.11 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

Starvation no longer occurs when sending HTTP responses that are generated slowly.

W-1982570

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.9, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
### [](#patch-4-9-11-4-java17)4.9.11:4-java17 **4.9.11 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

Starvation no longer occurs when sending HTTP responses that are generated slowly.

W-1982570

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.9, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
### [](#patch-4-6-24-4-java17)4.6.24:4-java17 **4.6.24 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now properly honors the graceful shutdown timeout. In versions earlier than 4.11.0, you must enable this behavior using these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19340663

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.6, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException no longer thrown when DW serializes error.errorMessage in Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071
### [](#patch-4-6-24-4-java8)4.6.24:4-java8 **4.6.24 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.19` This release includes security updates.
Issue Resolution ID

Mule

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now properly honors the graceful shutdown timeout. In versions earlier than 4.11.0, you must enable this behavior using these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19340663

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.6, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException no longer thrown when DW serializes error.errorMessage in Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

DataWeave

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071
### [](#patch-4-4-0-20250919-5)4.4.0:20250919-5 **4.4.0 Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` - The operating system is updated to the latest security patches. ## [](#october-2-2025)October 2, 2025 ### What’s New - Mule runtime engine 4.10.0 is now available. For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues ### [](#patch-4-10-0-23e-java17)4.10.0:23e-java17 **4.10.0 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

The org.quartz-scheduler:quartz library is upgraded to 2.5.0.

W-17406808

The org.vibur:vibur-object-pool library is upgraded to 26.

W-17570586

The commons-beanutils:commons-beanutils library is upgraded to 1.10.0.

W-17571116

The jakarta-annotation library is upgraded to 2.1.1.

W-17927646

The Mockito monorepo is upgraded to 5.

W-18685961

The Log4j2 monorepo is upgraded to 2.25.1.

W-18834079

The Netty library is upgraded to 4.1.127.Final.

W-19559645

The Rhino library is upgraded to 1.8.0.

W-17636627

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
### [](#patch-4-9-10-4e-java17)4.9.10:4e-java17 **4.9.10 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The Handlebars library is upgraded to 4.4.0.

W-19064659

The org.apache.commons : commons-lang3 library is upgraded to 3.17.0.

W-19383955

The io.netty : netty-codec library is upgraded to 4.1.127.Final.

W-19568278

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

Scheduler name generation no longer breaks the platform logging aggregator when processor chains have null or empty names.

W-19432758

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
### [](#patch-4-9-10-4-java17)4.9.10:4-java17 **4.9.10 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The Handlebars library is upgraded to 4.4.0.

W-19064659

The org.apache.commons : commons-lang3 library is upgraded to 3.17.0.

W-19383955

The io.netty : netty-codec library is upgraded to 4.1.127.Final.

W-19568278

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

Scheduler name generation no longer breaks the platform logging aggregator when processor chains have null or empty names.

W-19432758

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334
### [](#patch-4-6-23-4-java17)4.6.23:4-java17 **4.6.23 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

The org.springframework library is upgraded to 5.3.45.

W-18603096

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

This release reverts the changes introduced in W-17340911.

W-17340911

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

Batch queuestore files now clean up correctly in rare load failure scenarios, such as out of memory errors.

W-17935223

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334

Module compilation performance is improved when running concurrently.

W-19376546
### [](#patch-4-6-23-4-java8)4.6.23:4-java8 **4.6.23 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

The org.springframework library is upgraded to 5.3.45.

W-18603096

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

This release reverts the changes introduced in W-17340911.

W-17340911

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

Batch queuestore files now clean up correctly in rare load failure scenarios, such as out of memory errors.

W-17935223

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334

Module compilation performance is improved when running concurrently.

W-19376546
### [](#patch-4-4-0-20250919-3)4.4.0:20250919-3 **4.4.0 Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

BufferOverFlowException errors no longer occur when inter-node communication gets stuck in clusters with encryption under heavy load.

W-16517561

Gatekeeper deadlock errors no longer occur during race conditions between contract downloads and policy application.

W-19407164
## [](#september-2-2025)September 2, 2025 ### What’s New Runtime Manager agent 2.7.7. See [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7). ### Fixed Issues ### [](#patch-4-9-9-5e-java17)4.9.9:5e-java17 **4.9.9 Edge Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

io.projectreactor.netty : reactor-netty-http is upgraded to 1.2.8.

W-19074903

Component annotations, such as location, are no longer overwritten by other components.

W-18269859

org.apache.commons : commons-lang3 is upgraded to 3.18.0.

W-19059553

DataWeave

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

W-19376546
### [](#patch-4-9-9-5-java17)4.9.9:5-java17 **4.9.9 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

io.projectreactor.netty : reactor-netty-http is upgraded to 1.2.8.

W-19074903

Component annotations, such as location, are no longer overwritten by other components.

W-18269859

org.apache.commons : commons-lang3 is upgraded to 3.18.0.

W-19059553

DataWeave

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

W-19376546
### [](#patch-4-6-22-4-java17)4.6.22:4-java17 **4.6.22 LTS Runtime Updates** - Bundled JDK version: OpenJDK version 17.0.15+6 - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
### [](#patch-4-6-22-4-java8)4.6.22:4-java8 **4.6.22 LTS Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
### [](#patch-4-4-0-20250829-1)4.4.0:20250829-1 **4.4.0 Runtime Updates** - Bundled JDK version: OpenJDK "1.8.0\_452" - Sidecar version: `mulesoft/dias-anypoint-monitoring-sidecar:2.2.15` This release includes security updates.
Issue Resolution ID

Mule

Performance degradation no longer occurs when using repeatable streaming.

W-19175330
## [](#see-also)See Also - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Runtime Release Notes Mule follows semantic versioning to denote major, minor, and patch releases. MuleSoft releases enhance the quality, capabilities, and security of Mule runtime engine (Mule). To take advantage of these improvements, it’s important to adopt a strategy for upgrading your Mule version and to regularly update patches of your Mule deployments with the latest bug fixes and security enhancements. To upgrade to a new Mule version, see [Mule Upgrades and Patch Updates](#mule-upgrades). ## [](#mule-4-release-notes)Mule 4 Release Notes - [Mule Runtime 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes) - [Mule Runtime 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes) - [Mule Runtime 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes) - [Mule Runtime 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes) - [Mule Runtime 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes) - [Mule Runtime 4.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes) (This version of the product has reached [End of Life](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf).) - [Mule Runtime 4.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.3.0-release-notes) (This version of the product has reached [End of Life](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf).) ## [](#mule-upgrades)Mule Upgrades and Patch Updates For Mule 4 upgrades and patch updates: - [Java Adoption](https://docs.mulesoft.com/jp/release-notes/mule-runtime/java-adoption) - [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence) (for Mule versions 4.6 and later) - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) (for upgrading standalone Mule 4 instances, including minor versions and patch updates) - [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/upgrade-update-mule) (overview) - [Update Patches to Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions) - [Upgrading Mule Runtime Engine (Versions 4.x to 4.n)](https://docs.mulesoft.com/jp/release-notes/mule-runtime/updating-mule-4-versions) ## [](#mule-troubleshooting-plugin)Mule Troubleshooting Plugin - [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) ## [](#mule-services)Mule Services - [HTTP Service Release Notes - Mule 4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/service-http-release-notes) - [OAuth Service Release Notes - Mule 4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/service-oauth-release-notes) - [Scheduler Service Release Notes - Mule 4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/service-scheduler-release-notes) - [Mule SOAP Service Release Notes - Mule 4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/service-soap-release-notes) ## [](#anypoint-enterprise-security)Anypoint Enterprise Security - [Anypoint Security Release Notes](https://docs.mulesoft.com/jp/release-notes/anypoint-security/anypoint-security-rn-landing-page) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Mule SOAP Service Release Notes ## [](#1-3-2)1.3.2 Release date: June 15, 2021 - Updated Bouncy Castle to version 1.68. - Updated Apache CXF to version 3.4.1. - Updated Apache XML Security for Java (xmlsec) to version 2.2.1. - Updated Eclipse Jetty to version 9.4.39.v20210325. - Updated Spring Framework to version 5.3.6. - Updated JAX-WS API to version 2.3.1. - Updated Woodstox to version 6.2.5. - Updated Jakarta SOAP Implementation to version 1.5.3. ## [](#1-3-1)1.3.1 Release date: May 17, 2021 - Updated Apache Ant to version 1.10.9. ## [](#1-3-0)1.3.0 Release date: April 16, 2020 - Updated Bouncy Castle to version 1.64. - Updated Apache CXF to version 3.3.4. - Updated Cryptacular to version 1.2.4. ## [](#1-2-1)1.2.1 Release date: October 30, 2019 - Updated Apache XML Security for Java (xmlsec) to version 2.1.4. - Updated Bouncy Castle to version 1.61. ## [](#1-2-0)1.2.0 Release date: April 22, 2019 - Updated Apache CXF to version 3.3.1. - Updated dom4j to version 2.1.1. - Updated Apache Ant to version 1.10.5. - Updated mule-wsdl-parser to version 1.1.6. ## [](#1-1-4)1.1.4 Release date: May 30, 2018 ### [](#new-features-and-enhancements)New Features and Enhancements No new features were added in this version. ### [](#fixed-issues)Fixed Issues
Issue Description

MULE-15064

SOAP Service not adding Content-Disposition Header when using MTOM

MULE-15025

WSC doesn’t override HTTP headers when declaring custom transport headers

MULE-14978

WSDL Parser does not load schemas from WSDLs that contain multiple imports

MULE-8817

Upgrade Spring to 4.3.17
## [](#1-1-3)1.1.3 Release date: May 13, 2018 ### [](#new-features-and-enhancements-2)New Features and Enhancements No new features were added in this version. ### [](#fixed-issues-2)Fixed Issues | SE-7971 | Schema Collector fails reading schemas with encoding problem. | | --- | --- | ## [](#1-1-2)1.1.2 Release date: Mar 12, 2018 ### [](#new-features-and-enhancements-3)New Features and Enhancements Removed Jetty 9.4.x that is prone to a timing channel in util/security/Password.java, which makes it easier for remote attackers to obtain access by observing elapsed times before rejection of incorrect passwords. ## [](#1-1-1)1.1.1 Release date: Mar 5, 2018 ### [](#new-features-and-enhancements-4)New Features and Enhancements No new features were added in this version. ### [](#fixed-issues-3)Fixed Issues | MULE-14671 | MuleApplicationClassloader is leaked when through SOAP | | --- | --- | ## [](#1-1-0)1.1.0 Release date: Jan 22, 2018 GA version of the Soap Service. This version includes support for consuming SOAP Web Services through HTTP. - Custom HTTP transport (Connectivity is performed with the provided transport configuration). - Multipart operations support - MTOM Support - SOAP with Attachments (BASE64 encoded attachments) Support - WSS support (username, decrypt, encrypt, timestamp, signature). - Support for custom HTTP headers. - Extensible dispatching mechanism. This version of the Service runs with the latest CXF version. ### [](#fixed-issues-4)Fixed Issues
Issue Description

MULE-14388

Extensions Client must use the correct event when used in an operation

MULE-14382

Upgrade BouncyCastle to 1.59

MULE-14060

Upgrade CXF to 3.2.1

MULE-14008

Soap Service NPE if the config is not configured properly.
## [](#1-0-0)1.0.0 BETA version of the Soap Service. This BETA version includes support for consuming SOAP Web Services through HTTP. - Custom HTTP transport (Connectivity is performed with the provided transport configuration). - Multipart operations support - MTOM Support - SOAP with Attachments (BASE64 encoded attachments) Support - WSS support (username, decrypt, encrypt, timestamp, signature). - Added Web Service Security (WSS) configuration options. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.0.0 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#june-1-2022)June 1, 2022 ## What’s New MuleSoft announces the release of the Mule upgrade tool. See [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) for configuration and usage instructions. ## Compatibility
Application/Service Version

Mule

4.1.5 and later
- [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.0 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#september-8-2022)September 8, 2022 ## What’s New You can now upgrade Mule instances running version 4.1.1 or later. When updating your current Mule instance to a version between 4.1.1 and 4.1.4, use any patch update released after January 20, 2022. ## Compatibility
Application/Service Version

Mule

4.1.1 and later
## Fixed Issues
Issue ID

Help messages now display with no typing errors.

W-10854283

The list of known files is now updated.

W-11397729

A rollback now identifies and deletes files introduced in an upgraded Mule Runtime distribution.

W-10887753

The wrapper.ping.timeout property is now correctly updated in all Mule Runtime versions.

W-11091238

The Runtime Manager agent version is now correctly identified in Windows environments.

W-11386511

The upgrade process now deletes old directories.

W-11393439

The upgrade process now removes files added through a cumulative patch installation.

W-11526573
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.1 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#march-8-2023)March 8, 2023 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Anypoint Runtime Manager agent now upgrades correctly in the Windows environment.

W-12282226

Comparison of wrapper.conf properties no longer fails with a 'NullPointerException'.

W-12205752
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.2 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#september-15-2023)September 15, 2023 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Custom config files under ${MULE_HOME}/conf/ are no longer incorrectly deleted when one or more patches are applied.

W-13164828
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.3 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#november-17-2023)November 17, 2023 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The "No such file error" message no longer appears when upgrading Mule runtime 4.5.x versions.

W-14504237
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.4 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#august-28-2024)August 28, 2024 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Upgrading Mule runtime containing large files now works as expected.

W-15397689
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.5 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#october-20-2025)October 20, 2025 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Upgrade of Mule Agent now honors FIPS mode.

W-17928490

The upgrade tool now correctly parses arguments for custom LOG4J settings files.

W-17291103

The upgrade tool no longer removes empty directories unexpectedly.

W-18539935
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.6 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#february-18-2026)February 18, 2026 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Dry-run mode no longer fails in Windows environments.

W-20189619

The upgrade tool no longer fails to upgrade the Mule agent when running in FIPS mode.

W-21043229
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.8 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#april-22-2026)April 22, 2026 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Runtime Mananger Agent upgrades on Windows systems no longer fail because of improper file path handling.

W-21445583
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool 1.1.9 Release Notes The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. ## [](#september-23-2026)September 23, 2026 ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

wrapper-additional.conf is now regenerated after an upgrade.

W-23159037

Mule distribution paths with spaces and relative paths now work as expected.

W-21964600

Obsolete unzipped server-plugin directories are now removed during an upgrade.

W-24212237
## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrade Tool Release Notes - [Mule Upgrade Tool 1.1.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.9-release-notes) - [Mule Upgrade Tool 1.1.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.8-release-notes) - [Mule Upgrade Tool 1.1.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.6-release-notes) - [Mule Upgrade Tool 1.1.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.5-release-notes) - [Mule Upgrade Tool 1.1.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.4-release-notes) - [Mule Upgrade Tool 1.1.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.3-release-notes) - [Mule Upgrade Tool 1.1.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.2-release-notes) - [Mule Upgrade Tool 1.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.1-release-notes) - [Mule Upgrade Tool 1.1.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.0-release-notes) - [Mule Upgrade Tool 1.0.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.0.0-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Mule Upgrades and Patch Updates MuleSoft continuously improves the quality, capabilities, and security of Mule runtime engine (Mule). In addition to upgrading to later versions of Mule, it also is important to apply regular updates to the Mule versions (such as versions 3.9.5, 4.1.5, and 4.3.0) on which you are running your Mule applications. Be sure to review the information on updates, upgrades, versioning, and testing before attempting to upgrade or apply a patch update. ## [](#versioning)Mule Versioning Mule follows semantic versioning to denote major, minor, and patch releases. The version is specific to Mule applications that you deploy [on-premises](https://docs.mulesoft.com/mule-runtime/latest/deploy-on-premises), to [CloudHub](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub) and [CloudHub 2.0](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-cloudhub-2) through Anypoint Runtime Manager, or to [Anypoint Runtime Fabric](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-rtf). For Mule 4.5 and later, the version naming convention for CloudHub, CloudHub 2.0, and Runtime Fabric changes following the schema for the new release channels, Edge and Long-term Support (LTS). _Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\] : Build\[numeric\] Channel\[e for edge, nothing for LTS\]_ Here are examples of the version numbers: - Edge: 4.5.0:1e - Edge: 4.6.0:1e - LTS: 4.6.0:1 In the case of Standalone (On-Premises), the Mule runtime versioning changes from date-based, for example, `4.4.0-20230317` to semVer as: _Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\]_ Here are examples of the version numbers: - 4.5.1 - 4.5.2 - 4.5.3 See [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#update-or-upgrade)Update or Upgrade? Mule _update_ processes are cumulative releases that include the latest bug fixes and security enhancements to a specific patch (x.y.z) or build (x.y.z:1) version, plus all previously released features and fixes for that patch version. For updates, see [Update Patches to Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions). Unlike the update process, the Mule _upgrade_ process is for upgrading to a later minor version. For example, you can upgrade from Mule 4._x_ to 4._y_ (such as 4.3 to 4.4) or Mule 4.x._y_ to 4.x._z_ (such as 4.1.5 to 4.3.0). For minor and patch version upgrades or a major version migration, see: - [Upgrade Mule Runtime Engine (Versions 4.x to 4.n)](https://docs.mulesoft.com/jp/release-notes/mule-runtime/updating-mule-4-versions). ## [](#mule_upgrade_prep)Perform MUnit Tests Before Updating or Upgrading Though Mule guarantees compatibility with new minor, patch, or patch update versions, it is important to validate that your applications continue to run as expected in a testing environment before running them in a production environment. Run your [MUnit](https://docs.mulesoft.com/munit/latest/) tests on any new version of Mule to validate the application’s behavior with that version. ## [](#mule-upgrade-tool)Mule Upgrade Tool The Mule upgrade tool is a command line utility for updating and upgrading standalone instances of the Mule 4 runtime engine that are hosted on-premises. The tool can upgrade any supported Mule 4 version (minor, patch, or patch update versions) to a new version. MuleSoft recommends upgrading to the latest version of Mule. To incorporate the latest changes and bug fixes, MuleSoft also recommends using the latest version of the tool. See [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) for configuration and usage instructions. # MuleSoft Accelerator for Consumer Goods Release Notes ## [](#5-3)5.3 **February 13, 2024** ### What’s New This release introduces the [Pricing Data Integration for TPM](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/5.3/pages/3hl-pip/Use%20case%207%20-%20Pricing%20Data%20Integration%20for%20TPM/) use case, which enables consumer packaged goods companies to more effectively analyze and optimize promotional activities by integrating List Price and Cost of Goods Sold data with Hyperforce.
For previous versions of MuleSoft Accelerator for Consumer Goods, see the MuleSoft Accelerator for Consumer Goods Release Notes Archive.
## [](#see-also)See Also - [MuleSoft Accelerator for Consumer Goods](https://docs.mulesoft.com/consumer-goods/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Accelerator for Financial Services Release Notes ## [](#1-12)1.12 **March 12, 2025** ### What’s New All assets for MuleSoft Accelerator for Financial Services are now compatible with Java 17 except where noted in the asset documentation in Exchange. See [MuleSoft Accelerator for Financial Services on Exchange](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/) to download the latest versions.
For previous versions of MuleSoft Accelerator for Financial Services, see the MuleSoft Accelerator for Financial Services Release Notes Archive.
## [](#see-also)See Also - [Upgrade Notes](https://docs.mulesoft.com/financial-services/latest/upgrade-notes) - [MuleSoft Accelerator for Financial Services](https://docs.mulesoft.com/financial-services/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Accelerator for Healthcare Release Notes ## [](#2-24)2.24 **March 12, 2025** ### What’s New All assets for MuleSoft Accelerator for Healthcare are now compatible with Java 17 except where noted in the asset documentation in Exchange. See [FHIR R4 Assets](https://docs.mulesoft.com/healthcare/latest/fhir-r4-assets) for use case agnostic assets and [MuleSoft Accelerator for Healthcare on Exchange](https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/) for use case specific assets.
For previous versions of MuleSoft Accelerator for Healthcare, see the MuleSoft Accelerator for Healthcare Release Notes Archive.
## [](#see-also)See Also - [MuleSoft Accelerator for Healthcare](https://docs.mulesoft.com/healthcare/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Accelerator for Life Sciences Release Notes ## [](#1-2)1.2 **March 12, 2025** ### What’s New All assets for MuleSoft Accelerator for Life Sciences are now compatible with Java 17 except where noted in the asset documentation in Exchange. See [MuleSoft Accelerator for Life Sciences on Exchange](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-life-sciences/) to download the latest versions from the use cases.
For previous versions of MuleSoft Accelerator for Life Sciences, see the MuleSoft Accelerator for Life Sciences Release Notes Archive.
## [](#see-also)See Also - [MuleSoft Accelerator for Life Sciences](https://docs.mulesoft.com/life-sciences/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Accelerator for Manufacturing Release Notes ## [](#1-4)1.4 **October 25, 2023** ### What’s New The Run-Rate Business Management use case is updated to remove the dependency on MDM and optimize it for direct integration between ERP and CRM systems, such as connecting SAP S/4HANA data to Salesforce Manufacturing Cloud. As part of this update, the use case name is changed to ["Account and product and order sync"](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/1.4/pages/qrc-zzh/Use%20case%201%20-%20Account%20and%20product%20and%20order%20sync/).
For previous versions of MuleSoft Accelerator for Manufacturing, see the MuleSoft Accelerator for Manufacturing Release Notes Archive.
## [](#see-also)See Also - [MuleSoft Accelerator for Manufacturing](https://docs.mulesoft.com/jp/manufacturing/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Accelerator for Retail Release Notes ## [](#3-2)3.2 **March 8, 2024** ### What’s New This release includes the following updates to the [Product Sync](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/3.2/pages/Use%20case%203%20-%20Product%20sync/) and [Sales Order Sync](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/3.2/pages/Use%20case%202%20-%20Sales%20order%20sync/) use cases: - Salesforce Core is now the global data store, which simplifies the implementation process for both use cases. - The [Accelerator Products Process API](https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-global-product-prc-api-spec/) and [Accelerator SalesOrders Process API](https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slsorder-sync-prc-api-spec) now have a configuration based solution that includes System APIs of choice, which eliminates the major logic and processing that was needed for the previous solution.
For previous versions of MuleSoft Accelerator for Retail, see the MuleSoft Accelerator for Retail Release Notes Archive.
## [](#see-also)See Also - [MuleSoft Accelerator for Retail](https://docs.mulesoft.com/retail/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Accelerator for Salesforce OMS Release Notes ## [](#1-1)1.1 **May 20, 2024** ### What’s New This release introduces the [Salesforce OMS to ERP Integration](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-salesforce-oms/minor/1.1/pages/e74-ta9/Salesforce%20OMS%20to%20ERP%20Integration/) use case. You can now manage orders received via omnichannel sources within Salesforce Order Management System (OMS). In addition, SAP S/4HANA is now included as the Enterprise Resource Planning System (ERP) for the [B2B EDI Order Lifecycle Automation](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-salesforce-oms/minor/1.1/pages/7ij-1pd/B2B%20EDI%20Order%20Lifecycle%20Automation/) use case.
For previous versions of MuleSoft Accelerator for Salesforce OMS, see the MuleSoft Accelerator for Salesforce OMS Release Notes Archive.
## [](#see-also)See Also - [MuleSoft Accelerator for Salesforce OMS](https://docs.mulesoft.com/salesforce-oms/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Accelerators Release Notes Accelerators are a collection of technical assets (predominantly API specifications and implementation templates), reference architectures, and documentation that can be used to accelerate the implementation of multiple use cases supporting a larger business or industry problem. The following release notes are available for Accelerators: - [MuleSoft Accelerator for Consumer Goods Release Notes](https://docs.mulesoft.com/jp/release-notes/accelerators/consumer-goods/consumer-goods-release-notes) - [MuleSoft Accelerator for Financial Services Release Notes](https://docs.mulesoft.com/jp/release-notes/accelerators/financial-services/financial-services-release-notes) - [MuleSoft Accelerator for Healthcare Release Notes](https://docs.mulesoft.com/jp/release-notes/accelerators/healthcare/healthcare-release-notes) - [MuleSoft Accelerator for Life Sciences Release Notes](https://docs.mulesoft.com/jp/release-notes/accelerators/life-sciences/life-sciences-release-notes) - [MuleSoft Accelerator for Manufacturing Release Notes](https://docs.mulesoft.com/jp/release-notes/accelerators/manufacturing/manufacturing-release-notes) - [MuleSoft Accelerator for Retail Release Notes](https://docs.mulesoft.com/jp/release-notes/accelerators/retail/retail-release-notes) - [MuleSoft Accelerator for Salesforce OMS Release Notes](https://docs.mulesoft.com/jp/release-notes/accelerators/salesforce-oms/salesforce-oms-release-notes) ## [](#see-also)See Also - [MuleSoft Accelerators Overview](https://docs.mulesoft.com/jp/accelerators-home/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft AI Chain Connector Release Notes MuleSoft AI Chain Connector enables developers to design, develop, and manage AI agents from within Anypoint Platform. It provides the tools and support needed to integrate Large Language Models (LLMs), vector stores, and other advanced AI services into MuleSoft applications. Guide: [MuleSoft AI Chain Connector User Guide](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/) ## [](#2-0-0)2.0.0 **September 24, 2026** ### What’s New - This connector is now compatible with Java 17 only. - Java classes moved from `org.mule.extension.mulechain` to `com.mulesoft.connectors.mulechain`. Update custom Java code that imports the previous package. - `com.mulesoft.connectors.mulechain.internal.config.LangchainLLMConfiguration.getModel()` now returns `dev.langchain4j.model.chat.ChatModel`. In version 1.x, `org.mule.extension.mulechain.internal.config.LangchainLLMConfiguration.getModel()` returned `dev.langchain4j.model.chat.ChatLanguageModel`. - You can use tools with Ollama chat models. The embedded LangChain4j engine is upgraded from 0.34.0 to 1.20.0. For more information, see [Tools Use AI Service](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/mulesoft-ai-chain-connector-reference#ToolsUseAiService). - File paths that contain a `..` segment are rejected. A **Configuration Json** [File Path](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/mulesoft-ai-chain-connector-reference#Config) that contains `..` is not loaded. The [Image Read Scanned Documents](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/mulesoft-ai-chain-connector-reference#ImageReadScannedDocuments) **File Path** fails with `MS-AICHAIN:FILE_HANDLING_FAILURE`. For more information about how to upgrade, see [Upgrading and Migrating MuleSoft AI Chain Connector to 2.x](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/mulesoft-ai-chain-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The connector excludes log4j-api from the Apache Tika document parser and from mule-metadata-model-xml. Logging uses the SLF4J API.

W-24221152

These libraries are upgraded to address reported security vulnerabilities:

  • The bcprov-jdk18on, bcpkix-jdk18on, bcutil-jdk18on, and bcjmail-jdk18on libraries are upgraded to version 1.86.

  • The netty-codec, netty-codec-http, netty-codec-http2, and netty-codec-http3 libraries are upgraded to version 4.2.18.Final.

  • The opennlp-tools library is upgraded to version 2.5.12.

  • The Jsoup library is upgraded to version 1.23.2.

  • The jackson-databind and jackson-core libraries are upgraded to version 2.22.3.

  • The Reactor Netty HTTP library is upgraded to version 1.3.7.

  • The Reactor Core library is upgraded to version 3.8.7.

  • The DJL API library is upgraded to version 0.38.0.

W-23743561, W-24123994, W-3300013

These libraries are upgraded:

  • The Google Guava library is upgraded to version 33.7.1-jre.

  • The Apache Mime4j Core library is upgraded to version 0.8.15.

  • The SLF4J API is upgraded to version 2.0.19.

  • The Junrar library is upgraded to version 8.1.1.

  • The Kotlin kotlin-stdlib library is upgraded to version 2.4.20.

W-3300013
## [](#1-0-1)1.0.1 **August 17, 2026** ### Compatibility
Software Version

Mule

4.3 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Netty libraries are upgraded to version 4.2.17.Final.

  • The Reactor Netty HTTP library is upgraded to version 1.3.6, and the Reactor Core library to version 3.7.19.

  • The Jackson Databind and Jackson Core libraries are upgraded to version 2.22.1.

  • The Bouncy Castle libraries are upgraded to version 1.85 (bcprov-jdk18on to version 1.85.2).

  • The Apache POI libraries are upgraded to version 5.5.1.

  • The Google Gson library is upgraded to version 2.14.0.

  • The Apache Commons IO library is upgraded to version 2.22.0.

  • The Apache Commons Lang library is upgraded to version 3.20.0.

  • The Metadata Extractor library is upgraded to version 2.21.0.

  • The DJL API library is upgraded to version 0.36.0.

  • The Junrar library is upgraded to version 8.1.0.

  • The DD Plist library is upgraded to version 1.30.

  • The Apache Mime4j Core library is upgraded to version 0.8.14.

  • The Google Guava library is upgraded to version 33.6.0-jre.

W-23829549
## [](#1-0-0)1.0.0 **November 13, 2024** ### What’s New - The open-source connector is now certified by MuleSoft and enhanced to adhere to development and security best practices. - You can now use MuleSoft AI Chain Connector with Anypoint Code Builder and Java 17. - You can discover and import the connector from Anypoint Exchange directly into your IDE. For more information, see the [MuleSoft AI Chain Connector User Guide](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/). ### Compatibility
Software Version

Mule

4.3 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [MuleSoft AI Chain Connector User Guide](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/) - [MuleSoft AI Chain Connector Reference](https://docs.mulesoft.com/mulesoft-ai-chain-connector/latest/mulesoft-ai-chain-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Developer Hub Release Notes MuleSoft Developer Hub is a unified experience where humans and AI agents can discover, interact, and automate with MuleSoft APIs, skills, MCP servers, and Terraform. With everything in one place, you can find the right assets faster, reduce integration friction, and build with confidence. Visit [MuleSoft Developer Hub](https://dev-portal.mulesoft.com) to get started. ## [](#august-7-2026)August 7, 2026 ### What’s New - The Australia (`au1`) region is now available in the region selector, making it easier to configure and test APIs and MCP servers deployed in the Australia platform environment. - The authentication panel now uses a region-first selection experience. Selecting a region automatically configures the appropriate platform domain. You can still specify a custom region when needed. - API Try It panels, guided workflow steps, and MCP server endpoints now automatically use the selected region. If an API isn’t available in the selected region, the portal displays an availability message. - API operation pages now use concise operation summaries as their primary titles, making endpoints easier to scan and understand. - Try It forms now display prerequisite request parameters before parameters that depend on them. ### Fixed Issues
Issue Resolution ID

The Browse all services link now returns you to the catalog when an error occurs on a nested URL.

W-22617454

Operation titles now render identifiers that contain numbers more clearly.

W-23431001
## [](#june-26-2026)June 26, 2026 ### What’s New - India (in1) region support: The `in1` region is now selectable in the auth panel, enabling testing and configuration of APIs deployed to the India platform environment. - Catalog empty state: When home catalog filters or searches return no results, users now see a clear `We didn’t find any results` message instead of a silent blank grid. - Persistent tag suggestions: The tag-search dropdown on the home page now retains the last non-empty suggestion list when the current query matches nothing, so users are never left without selectable options. ### Fixed Issues
Issue Resolution ID

The try-it playground endpoint now respects the user’s region selection. Previously, the playground ignored the selected region and always used the default endpoint.

W-22945464

Nested scrollable containers on the detail page no longer trap scroll input or break keyboard or mouse wheel navigation.

W-22617450
## [](#may-28-2026)May 28, 2026 ### What’s New - The MuleSoft Developer Portal is now named MuleSoft Developer Hub. - [MCP Servers](https://dev-portal.mulesoft.com/index.html?filter=mcp): MuleSoft platform capabilities packaged as ready-to-use tools for AI agents - [Terraform](https://dev-portal.mulesoft.com/index.html?filter=terraform): MuleSoft Terraform Provider resources and data sources - [More skills](https://dev-portal.mulesoft.com/index.html?filter=skill): Expanded skills library with additional agent-executable workflows across the MuleSoft development lifecycle - Dark mode: New dark theme for the MuleSoft Developer Hub experience ## [](#may-8-2026)May 8, 2026 ### What’s New - [MuleSoft Developer Portal](https://dev-portal.mulesoft.com) is now generally available with these features: - 35 platform APIs organized by category across the MuleSoft development lifecycle - Skills layer for agent-executable workflows built on top of MuleSoft APIs - In-browser testing playground for trying APIs and skills - Searchable, tag-based directory for discovering APIs and skills - Detailed reference documentation with endpoints, versioning, and full API details - Feedback mechanism to report issues or contribute via GitHub PRs ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Government Cloud Release Notes These release notes describe updates to MuleSoft Government Cloud as from January 10, 2024. ## [](#june-19-2026)June 19, 2026 ### What’s New - MuleSoft Government Cloud now supports FIPS 140-3 compliance for Mule runtime engine 4.9. FIPS 140-3 replaces FIPS 140-2 as the supported cryptographic standard in Government Cloud. This update introduces support for Bouncy Castle 2.0.0 as the certified security provider, requires Java 17 or later, and mandates BCFKS keystore format and TLS 1.2 or TLS 1.3. For migration steps and configuration details, see [FIPS 140-3 Compliance Support](#gov-cloud::gov-cloud-fips-140-3-support.adoc). ## [](#april-8-2025)April 8, 2025 ### What’s New - MuleSoft Government Cloud now supports Mule runtime engine version 4.9.3. ## [](#may-8-2024)May 8, 2024 ### What’s New - MuleSoft Government Cloud now supports Java 17. For more information, visit [Java Support](https://docs.mulesoft.com/jp/general/java-support). ## [](#march-12-2024)March 12, 2024 ### What’s New - MuleSoft Government Cloud now supports Mule runtime engine version 4.6. The March CloudHub 1.0 release introduces patches for Runtime versions 4.3.0 and 4.4.0 and Runtime 4.6. This update is a breaking change as it enforces compliance with FIPS 140-2 on runtime versions 4.6, 4.4, and 4.3 for CloudHub applications within the MuleSoft Government Cloud. For more details about the impact of this update, check this article: - [GovCloud - March 2024 - Updates on FIPS Enforcement.](https://help.salesforce.com/s/articleView?id=001186489&type=1) ## [](#january-10-2024)January 10, 2024 ### What’s New - Trusted domains allowlisting is now available in MuleSoft Government Cloud. For more information, visit [Allowing Trusted Domains for API Platform Proxies](https://docs.mulesoft.com/jp/gov-cloud/gov-cloud-security#allowing-trusted-domains-for-api-platform-proxies). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Inference Connector Release Notes Anypoint Connector for MuleSoft Inference (MuleSoft Inference Connector) provides access to inference offerings for large language models (LLMs) from multiple providers including OpenAI, OpenAI Compatible Endpoints, OpenRouter, Heroku AI, Azure AI Foundry, Azure OpenAI, and many others. This connector provides operations to interface directly with the API of various inference providers, enabling seamless integration of AI capabilities into your Mule applications. Guide: [MuleSoft Inference Connector User Guide](https://docs.mulesoft.com/mulesoft-inference-connector/latest/) ## [](#1-2-1)1.2.1 **October 6, 2026** ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The [Image] Generate (only Base64) operation for OpenAI no longer sends the response_format parameter to GPT image models, which reject it. The operation now sends this parameter only for DALL-E models.

W-23827390

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-datatype-jsr310 library is upgraded to version 2.22.3.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-lang3 library is upgraded to version 3.21.0.

W-3300013
## [](#1-2-0)1.2.0 **September 29, 2025** ### What’s New - The new **\[MCP\] Tooling** operation enables the LLM to select and run tools based on prompts without requiring manual inputs. - The connector now supports the **Swisscom** connection type (beta) in **Text Generation Config**. - The new **Additional Request Attributes** field allows you to pass a JSON object with additional request attributes for all operations. These attributes flatten into the root level of the request payload, along with existing standard attributes. - All references to the NVIDIA company name now comply with the official NVIDIA brand name. For more information, see [MuleSoft Inference Connector Reference](https://docs.mulesoft.com/mulesoft-inference-connector/latest/mulesoft-inference-connector-reference). ### Compatibility
Software Version

Mule

4.9.6 and later

OpenJDK

17
## [](#1-1-0)1.1.0 **September 8, 2025** ### What’s New - The connector now supports the **Custom headers** field for all operations. Custom headers always take precedence over any existing headers passed as part of an implementation, overwriting values where the same key is used. - The **Nvidia** connection type now includes the custom **\[Nvidia\] Base URL** field for sending inference requests, with `https://integrate.api.nvidia.com` as the default. This supports custom and self-hosted URLs. - The **Messages** field in the **\[Chat\] Completions** operation now supports DataSense, which provides schema support. - The **Tools** field in the **\[Tools\] Native Template (Reasoning only)** operation now supports DataSense, which provides schema support. - The **\[Agent\] Define Prompt Template**, **\[Chat\] Answer Prompt**, **\[Chat\] Completions**, and **\[Tools\] Native Template (Reasoning only)** operations now provide default support for toxicity detection by returning the new `contentFilterResults` and `promptFilterResults` additional attributes in the response. - The connector now supports the **Gemini** connection type (beta) in **Text Generation Config** and **Vision Config**. - In the **Azure OpenAI** connection type: - The new **\[Azure OpenAI\] API Version** and **\[Azure OpenAI\] Endpoint** fields are added to the **General** tab. - In the **General** tab, there is a new section called **Required: Enter URL or Parameters** which has the **\[Azure OpenAI\] Endpoint**, **\[Azure OpenAI\] Resource Name**, and **\[Azure OpenAI\] Deployment ID** fields. In this section, you can either provide the default or a custom endpoint URL (which is used directly and overrides any parameter values), or provide the resource name and deployment ID (which are used to construct the base URL). - The **\[Azure OpenAI\] User** field is moved from the **General** tab to the **Advanced** tab. For more information, see [MuleSoft Inference Connector Reference](https://docs.mulesoft.com/mulesoft-inference-connector/latest/mulesoft-inference-connector-reference). ### Compatibility
Software Version

Mule

4.9.4 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The [Tools] Native Template (Reasoning only) operation now supports a full JSON schema for input parameters, including nested structures and tags such as items, minItems, and uniqueItems.

W-19271915

The [Chat] Completions operation using the Vertex AI Express connection type now supports OpenAI standard input template for chat messages.

W-19483173
## [](#1-0-0)1.0.0 **August 1, 2025** ### What’s New This is a new connector. For more information, see the [MuleSoft Inference Connector User Guide](https://docs.mulesoft.com/mulesoft-inference-connector/latest/). ### Compatibility
Software Version

Mule

4.9.4 and later

OpenJDK

17
## [](#see-also)See Also - [MuleSoft Inference Connector User Guide](https://docs.mulesoft.com/mulesoft-inference-connector/latest/) - [MuleSoft Inference Connector Reference](https://docs.mulesoft.com/mulesoft-inference-connector/latest/mulesoft-inference-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft MCP Servers Release Notes MuleSoft MCP Servers implement the Model Context Protocol (MCP) so AI assistants in your IDE can work with MuleSoft products and services. MuleSoft DX MCP Server supports API design, application deployment, and asset management. MuleSoft Platform MCP Server supports service discovery, policy enforcement, and traffic monitoring across your organization. ## [](#new-features-mcp-server-oct14-26)October 14, 2026 ### What’s New The following new tools and updates are available in MuleSoft Platform MCP Server. - Policy Management - New tool: `apply_universal_policy`. Apply a canonical policy to one or more API instances across supported gateway providers. - New tool: `edit_applied_policy`. Edit the configuration of an applied policy on an API instance. - New tool: `get_policy_operation_status`. Check the status of an asynchronous policy operation. - New tool: `list_instance_policy_operations`. List asynchronous policy operations for an external gateway API instance. - New tool: `list_universal_policies`. List the canonical policy templates available to an organization. - New tool: `remove_applied_policy`. Permanently remove an applied policy from a MuleSoft or external gateway API instance. - New tool: `toggle_applied_policy`. Enable or disable an applied policy on a MuleSoft or external gateway API instance. - Tool update: `apply_policy_to_instance`, `get_policy_template_form`, and `prepare_policy_creation` now support policy management for external gateway providers. For tool parameter details, see [MuleSoft Platform MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools-platform). ## [](#new-features-mcp-server-aug31-26)August 31, 2026 ### What’s New The following new tools and updates are available in MuleSoft Platform MCP Server. - Search and Discovery - New tool: `get_asset_lineage`. Get instance-rooted lineage, including design-time and runtime relationships, for an agent, MCP server, or API from the Context Catalog. - New tool: `get_data_asset_classification`. Get a data asset’s source-to-column hierarchy, classifications, descriptions, glossary terms, and PII state. - Cost Management - New tool: `create_model_wallet`. Create a model wallet with budget allocation for a specific LLM model. - New tool: `delete_model_wallet`. Delete a model wallet. - New tool: `edit_model_wallet`. Edit an existing model wallet configuration. - New tool: `fetch_model_wallet_details`. Fetch model wallet details for a given wallet ID and environment. - New tool: `fetch_model_wallets`. Fetch the list of model wallets for an environment. - Tool update: `fetch_cost_instances`, `fetch_cost_instance_timeseries`, `fetch_cost_optimization_recommendations`, and `fetch_cost_overview`. - Secrets Management - New tool: `check_secret`. Verify that a secret exists and retrieve its non-sensitive metadata without exposing secret material. - New tool: `describe_vault_auth_schema`. Discover supported vault providers and the credential fields required to onboard or edit a vault integration. - New tool: `edit_integration`. Modify an existing vault integration’s configuration with automatic credential validation and connectivity testing. - New tool: `list_integration_secrets`. List all secret references discovered by a specific vault integration. - New tool: `onboard_vault`. Register a new external vault provider integration with credential validation and live connectivity testing. - New tool: `search_secrets`. Search for secrets by name across all secret groups in an environment. - New tool: `test_integration_connection`. Validate vault connectivity and credential permissions before or after creating an integration. For tool parameter details, see [MuleSoft Platform MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools-platform). ## [](#new-features-mcp-server-june2-26)June 2, 2026 ### What’s New - New tool: `uc_get_test_generation_info`. Get information about which connector modules (CCM, ACM, FCM) are available and whether tests already exist before generating tests. - New tool: `uc_generate_tests`. Generate tests for connector modules using either mock or real connections. - Tool rename: `uc_generate_api_spec` is renamed to `uc_manage_api_spec`. The renamed tool also supports research-only and validation modes. - Tool rename: `uc_publish_connector` is renamed to `uc_connector_lifecycle`. The renamed tool supports both `build` and `publish` actions. - Tool update: `uc_generate_connector`. The `phases` parameter now accepts `flow` to generate a Flow Connector module in addition to the existing `ccm` and `anypoint` phases. For tool parameter details, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). ## [](#new-features-mcp-server-may28-26)May 28, 2026 ### What’s New - Introducing MuleSoft Platform MCP Server Get governed access to your entire IT landscape, including APIs, agents, MCP servers, and LLMs, and accelerate production-ready AI at scale. With remote access, use MuleSoft Platform MCP Server to scan, discover, govern, and monitor services across the infrastructure you already run. Typical platform areas you can address include: - Service scanning across agentic platforms - Discovery of APIs, agents, MCP servers, and LLMs in one place - Policy enforcement for PII detection, semantic routing, and token controls - Monitoring of traffic, cost, and performance across services For more information, see [Getting Started with MuleSoft Platform MCP Server](https://docs.mulesoft.com/mulesoft-mcp-server/getting-started-platform) - With the addition of MuleSoft Platform MCP Server, MuleSoft MCP Server is renamed to MuleSoft DX MCP Server. This is a non-breaking change and only cosmetically affects the UI and documentation. There are no changes to tool names. ## [](#new-features-mcp-server-mar16-26)March 16, 2026 ### What’s New - Tool update: `get_flex_gateway_policy_example`. You can now generate examples for these policy features. - `ip_filter`: Allow or block requests based on IP addresses and CIDR ranges - `jwt_generate`: Generate JSON Web Tokens - `oauth2_token_introspection`: Validate OAuth2 tokens - `rate_limiting`: Allow or block requests based on rate limits - `data_storage`: Store and retrieve data using the Data Storage Library - Installation namespace change: When installing MuleSoft MCP Server in your IDE, the installation command is now `npm install -g mulesoft-mcp-server`. Previously, it used `mulesoft/mcp-server`. ## [](#new-features-mcp-server-mar6-26)March 6, 2026 ### What’s New - New tool: `uc_add_pagination`. Add pagination support to a specific operation. - New tool: `uc_list_connection_profiles`. List all available connection profiles with their IDs, names, authentication types, and descriptions. - New tool: `uc_manage_operations`. Manage connector operations. - New tool: `uc_publish_connector`. Publish a connector to Anypoint Exchange. For tool parameter details, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). ## [](#new-features-mcp-server-feb17-26)February 17, 2026 Tool update: `search_asset`. Use the new `exchangeScope` parameter to set the search scope for either private or public assets. Additionally, the `search_asset` tool responses now use standardized relevance scores. ## [](#new-features-mcp-server-feb6-26)February 6, 2026 ### What’s New - Tool update: `implement_api_spec`. Use APIkit flows to implement an API specification in a new integration project. You can implement a specification from a local asset or an Anypoint Exchange asset. - New tool: `generate_or_modify_munit_test`. Generate, modify, or fix MUnit tests for Mule flows. Provide the flow XML, test scenario description, and dependencies for accurate test generation. Previously generating and modifying MUnit tests were different tools. For tool parameter details, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). ## [](#new-features-mcp-server-jan15-26)January 15, 2026 ### What’s New - New tool: `implement_api_spec`. Use APIkit flows to implement an API specification in a new integration project. You can implement a specification from an Anypoint Exchange asset. - New tool: `generate_munit_test`. Generate MUnit test cases for Mule flows, one test scenario at a time, with support for mocks, assertions, and dependencies. - New tool: `modify_munit_test`. Modify or fix an existing MUnit test case, including updating assertions, mocks, payloads, and test logic. For tool parameter details, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). ## [](#november-20-2025)November 20, 2025 ### What’s New You can now use the MuleSoft MCP Server to build connectors with Connector Builder. These new MCP tools are available for use in Connector Builder. - `uc_create_connector_workflow` - `uc_generate_api_spec` - `uc_generate_connector` For more information, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools) and [Generate Base Connectivity with MCP Tools](https://docs.mulesoft.com/connector-builder/base-connectivity#generate-base-connectivity-with-mcp-tools). ## [](#october-3-2025)October 3, 2025 ### What’s New Build Agent Fabric agent networks, manage governance rulesets, and more with new tools. All tools are available in MuleSoft MCP Server in Anypoint Code Builder; they aren’t available for use in other IDEs. - Tools to create, edit, publish, and deploy agent networks for Agent Fabric solutions. - Tools to list, add, and validate governance rulesets. - Tools to open, mock, and validate API specs. - Tool to get metadata and instructions for enabling topics and agent actions from an OpenAI spec. For more information, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). ## [](#august-11-2025)August 11, 2025 ### What’s New - New tool: `create_and_manage_metadata`. Define metadata for a flow component, attach metadata to Mule flow components, and update existing metadata. To define metadata, provide the Mule configuration file URI and sample data or schema. To apply metadata, specify existing metadata types. To update metadata, provide new schema or sample data. - New tool: `test_connection`. Test a connector configuration for a Mule project. For example, test connectivity for a HTTP listener connection. For more information, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools). ## [](#july-17-2025)July 17, 2025 ### What’s New - App Development - New tool: `create_api_spec`. Use AI to create an API specification. You must enable Agentforce in [Access Management](https://docs.mulesoft.com/jp/access-management/). - New tool: `create_api_spec_project`. Create and scaffold an API specification or fragment project. You can specify the project name, location, and language (RAML, OAS, and so on). - New tool: `create_MCP_server`. Create a MuleSoft MCP server. This tool uses Anypoint Connector for MCP (MCP Connector) to handle requests for creating MCP servers. - New tool: `create_mule_project`. Create an integration project. - New tool: `generate_mule_flow`. Use AI to create a flow. - New tool: `run_local_mule_application`. Deploy and run your app locally. - New tool: `search_asset`. Search for an asset in an organization and Anypoint Exchange. Returns the first asset in your organization that matches input criteria. If the tool doesn’t find any assets in your organization, then the tool returns assets in Anypoint Exchange that exactly or partially match `searchQuery`. - App Management - New tool: `create_and_manage_api_instances`. Create and configure API instances in Anypoint API Manager. - New tool: `list_api_instances`. Get information for instances in an environment. You can also filter by an instance ID or label and include applied or available policies. The tool paginates results using the page parameter. Prompt tip: To get information for all instances, revise the results by using the page parameter. - New tool: `list_applications`. Get information about all apps in the environment that you specify. You can also specify an optional deployment name. Results are sorted by last update date and time, in descending order. - New tool: `update_mule_application`. Update a Mule app deployed to CloudHub 2.0 or Anypoint Runtime Fabric. Update the runtime version, configuration, and other app settings. - Policy Management - New tool: `manage_api_instance_policy`. Apply a new policy to an API instance and update an existing policy configuration. - New tool: `manage_flex_gateway_policy_project`. Provide instructions to the LLM on how to manage an Anypoint Omni Gateway custom policy project. Instructions include how to create the project, set up the configuration, and build the project. The instructions also include how to publish a development version of the project and publish a release version of the project. See [Prerequisites for Omni Gateway Policy Development Kit (PDK)](https://docs.mulesoft.com/pdk/latest/policies-pdk-prerequisites). - New tool: `get_flex_gateway_policy_example`. Get an Anypoint Omni Gateway policy example to help you configure your Rust source code. You can get example policies that manipulate a request’s header and body, make HTTP calls to external services, share data between requests and responses, reject requests, and perform sleep operations. - Usage and Insights - New tool: `get_platform_insights`. See how your organization uses Anypoint Platform through operational insights. Insights include: - Usage trends for apps, such as flow count, message counts, and data throughput by business group and environment. Usage trends are for the current month. If it’s early in the month, you get usage for the last full month. - API and app call volume across consumers for the last 7 days. - API and app performance metrics such as errors and latency for the last 7 days. - New tool: `get_reuse_metrics`. Get visibility into how you reuse assets across your organization. Drive efficiency, consistency, and cost savings by reducing duplication. Includes sandbox and production environments. Metrics are a year-to-date snapshot. For more information, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools) ## [](#june-3-2025)June 3, 2025 ### What’s New - App Development - New tool: `create_mule_project`. Create an integration project. - New tool: `generate_mule_flow`. Use AI to create a flow. - New tool: `run_local_mule_application`. Deploy and run your app locally. - New tool: `search_asset`. Find an Anypoint Exchange asset by name or other parameters that you specify. Returns the first asset that matches the input criteria. - New tool: `create_and_manage_assets`. Create an asset in Anypoint Exchange, update some Anypoint Exchange asset properties without republishing the asset, and delete an asset in Anypoint Exchange. Asset properties are the asset name, description, icon, contact name, and contact email. - App Management - New tool: `deploy_mule_application`. Deploy your app to CloudHub 2.0 or Anypoint Runtime Fabric and run it. You can deploy from a local project or Anypoint Exchange asset. This tool supports security, high availability, and performance optimizations for deployments. - New tool: `list_applications`. Get information about all apps in the environment that you specify. You can also specify an optional deployment name. Results are sorted by last update date and time, in descending order. For more information, see [MuleSoft DX MCP Server Tool Reference](https://docs.mulesoft.com/mulesoft-mcp-server/reference-mcp-tools) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Terraform Provider Release Notes MuleSoft Terraform Provider release notes include information about changes, new features, improvements, and resolved issues in releases of the MuleSoft Terraform Provider. ## [](#v1-0-14)1.0.14 **June 22, 2026** ### What’s New - You can now read `anypoint_api_instance`, `anypoint_agent_instance`, and `anypoint_mcp_server` by composite ID using the new by-id data sources, without filtering the full list. - New read-only data sources are now available for `anypoint_connected_app_scopes`, `anypoint_api_policy`, `anypoint_api_policies`, per-known-policy `anypoint_api_policy_` variants, `anypoint_api_instance_sla_tier`, `anypoint_api_instance_sla_tiers`, `anypoint_private_space_config`, `anypoint_privatespace_advanced_config`, and `anypoint_vpn_connection`. Each data source accepts the same composite ID as the corresponding resource’s import format. - The provider version constraint in all bundled examples is updated to `~> 1.0.0`. ## [](#v1-0-13)1.0.13 **June 16, 2026** ### What’s New - The `upstream_uri` shorthand attribute on `anypoint_api_instance` is now deprecated. Existing configurations continue to work, but the attribute will be removed in a future major version. Migrate to a `routing` block with a single upstream entry instead. ### Fixed Issues
Issue Resolution ID

Routes in anypoint_api_instance can now be added, inserted, and reordered correctly.

W-22924093
## [](#v1-0-12)1.0.12 **June 10, 2026** ### Fixed Issues
Issue Resolution ID

anypoint_privatespace_advanced_config now sets the id and organization_id attributes correctly after an update, so Terraform no longer fails with a "Provider returned invalid result object after apply" error.

W-22363491

The type field in anypoint_secret_group_tls_context is now correctly read and written, resolving import and plan-diff issues for TLS contexts backed by PEM or JKS keystores.

W-22774371
## [](#v1-0-10)1.0.10 **June 08, 2026** ### Fixed Issues
Issue Resolution ID

Upstreams in anypoint_api_instance are now correctly updated when multiple upstreams are configured.

W-22774371

Policy-bound pointcut configurations in anypoint_api_instance are now correctly applied and read back from state when using known policies.

W-22721413
## [](#v1-0-9)1.0.9 **June 05, 2026** ### What’s New - You can now associate a TLS context with individual upstreams in `anypoint_api_instance` using the new `upstream_tls_context_id` field. ### Fixed Issues
Issue Resolution ID

anypoint_secret_group_tls_context import and apply operations no longer fail due to an incorrect API endpoint.

W-22721411

The associations attribute in anypoint_private_space_association is now optional, preventing unnecessary plan diffs when the attribute is not specified.

W-22721405

The default version of the message-logging-outbound policy has been reverted to 2.0.2 to match the version available in Anypoint Exchange.

W-22721410
## [](#v1-0-7)1.0.7 **June 01, 2026** ### Fixed Issues
Issue Resolution ID

Importing API policies using terraform import no longer fails.

W-22687456
## [](#v1-0-5)1.0.5 **May 29, 2026** ### What’s New - You can now import existing `anypoint_private_space_association` resources using `terraform plan -generate-config-out` to auto-generate Terraform configuration. The `associations` attribute is now optional, removing the error that occurred when the attribute was not known during import. - You can now import `anypoint_api_instance` resources for root-level organizations using the `/` format. - You can now import `anypoint_managed_omni_gateway` resources for root-level organizations using the `/` format. - You can now import `anypoint_private_space_upgrade` resources using the `:::` format. - You can now import `anypoint_tls_context` (CloudHub 2.0) resources using the `::` format. - You can now import `anypoint_vpn_connection` resources using the `//` format. - You can now import `anypoint_private_space_association` resources using the `/` format. ### Fixed Issues
Issue Resolution ID

Terraform state now correctly reflects both associations and created_associations after importing an anypoint_private_space_association resource.

W-22734343
## [](#v1-0-3)1.0.3 **May 27, 2026** ### Fixed Issues
Issue Resolution ID

Terraform no longer plans unnecessary changes after importing an existing anypoint_api_instance resource. The tls_context_id and gateway_id fields are now correctly restored during import.

W-22678732

Importing anypoint_private_space_config and anypoint_privatespace_advanced_config resources for private spaces in Business Groups no longer fails with "Cannot import non-existent remote object". The provider now correctly uses the sub-org context during import.

W-22678732
## [](#v1-0-2)1.0.2 **May 25, 2026** ### Fixed Issues
Issue Resolution ID

Creating and updating anypoint_team resources no longer produces errors or leaves the resource in an inconsistent state.

W-22677256
## [](#v1-0-1)1.0.1 **May 22, 2026** ### What’s New - You can now import existing `anypoint_api_instance` and related API management resources using `terraform import`. - All major resource documentation pages now include `import` block examples to help you bring existing Anypoint Platform resources under Terraform management without recreating them. ### Fixed Issues
Issue Resolution ID

A2A policy configurations are now applied correctly to ensure policies are created with the intended settings.

W-22574468
## [](#1-0-0)1.0.0 **May 11, 2026** ### What’s New - MuleSoft Terraform Provider is now available, enabling you to manage MuleSoft resources declaratively using Terraform. The provider supports resources across CloudHub 2.0, API Manager, Access Management, Secrets Manager, MCP servers, and A2A instances. - You can now provision and manage CloudHub 2.0 resources, including private spaces, network configuration, ingress and egress rules, VPN connections, and TLS contexts. For more information, see [CloudHub 2.0 Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/cloudhub2-resources). - You can now create and manage managed Omni Gateway resources in CloudHub 2.0. For more information, see [Managed Omni Gateway Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/managed-gateway-resources). - You can now manage Access Management resources, including business groups and teams. For more information, see [Access Management Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/access-management-resources). - You can now configure Secrets Manager resources, including secret groups, certificates, keystores, truststores, and shared secrets. For more information, see [Secrets Manager Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/secret-manager-resources). - You can now create and manage API Manager resources, including API instances and SLA tiers. For more information, see [API Manager Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/api-manager-resources). - You can now create and manage MCP servers and A2A instances. For more information, see [MCP and AI Agent Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/mcp-resources) and [API, MCP, and A2A Policy Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/a2a-resources). - You can now apply API, MCP, and A2A policies declaratively. For more information, see [Resources](https://docs.mulesoft.com/mulesoft-terraform-provider/resources). ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Terraform Provider Release Notes The MuleSoft Terraform Provider enables you to manage MuleSoft resources declaratively using Terraform, supporting infrastructure-as-code workflows for API Manager, Runtime Manager, and other Anypoint Platform components. These release notes are provided for the MuleSoft Terraform Provider: - [MuleSoft Terraform Provider Release Notes](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes) ## [](#see-also)See Also - [MuleSoft Terraform Provider](https://docs.mulesoft.com/mulesoft-terraform-provider/) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft Vectors Connector Release Notes Anypoint Connector for MuleSoft Vectors (MuleSoft Vectors Connector) provides access to a broad number of external vector stores and databases. MuleSoft Vectors Connector can be used with other connectors (for example, MuleSoft Inference Connector or Einstein AI Connector) and provides seamless access to vector stores for implementing smarter search or Retrieval Augmented Generation (RAG) use cases. Guide: [MuleSoft Vectors Connector User Guide](https://docs.mulesoft.com/mulesoft-vectors-connector/latest/) ## [](#1-1-1)1.1.1 **October 6, 2026** ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Apache Commons IO library is upgraded to version 2.22.0.

  • The TwelveMonkeys ImageIO core and JPEG libraries are upgraded to version 3.15.2.

W-3300013
## [](#1-1-0)1.1.0 **April 24, 2026** ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The langchain4j library is upgraded to version 1.12.1 to address reported security vulnerabilities.

W-21635005, W-21744486, W-21849948
## [](#1-0-0)1.0.0 **August 4, 2025** ### What’s New This is a new connector. For more information, see the [MuleSoft Vectors Connector User Guide](https://docs.mulesoft.com/mulesoft-vectors-connector/latest/). ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
## [](#see-also)See Also - [MuleSoft Vectors Connector User Guide](https://docs.mulesoft.com/mulesoft-vectors-connector/latest/) - [MuleSoft Vectors Connector Reference](https://docs.mulesoft.com/mulesoft-vectors-connector/latest/mulesoft-vectors-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MuleSoft WebCrawler Connector Release Notes Anypoint Connector for MuleSoft WebCrawler (MuleSoft WebCrawler Connector) is a highly customizable web-crawling connector that enables you to crawl websites, retrieve content, and automate web scraping processes within Mule flows. The connector is suited for gathering large-scale web data efficiently, with helper operations for fine-tuned crawling such as targeting specific content types and emitting referenced documents and images as Mule events. Use it to organize web data into structured formats for knowledge extraction, AI applications, and downstream processing. Guide: [MuleSoft WebCrawler Connector User Guide](https://docs.mulesoft.com/mulesoft-webcrawler-connector/latest/) ## [](#1-0-2)1.0.2 **October 16, 2026** ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.3.

  • The jsoup library is upgraded to version 1.23.2.

  • The guava library is upgraded to version 33.7.2-jre to address CVE-2026-102554.

W-24134399, W-24300208, W-24423997
## [](#1-0-1)1.0.1 **September 20, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The jackson library is upgraded to version 2.22.2 to address reported security vulnerabilities.

W-24134399
## [](#1-0-0)1.0.0 **July 29, 2026** ### What’s New - This is a new connector. - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. For more information, see the [MuleSoft WebCrawler Connector User Guide](https://docs.mulesoft.com/mulesoft-webcrawler-connector/latest/). ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17
## [](#see-also)See Also - [MuleSoft WebCrawler Connector User Guide](https://docs.mulesoft.com/mulesoft-webcrawler-connector/latest/) - [MuleSoft WebCrawler Connector Reference](https://docs.mulesoft.com/mulesoft-webcrawler-connector/latest/mulesoft-webcrawler-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 2.3.18 Release Notes MUnit is a Mule application testing framework that enables you to easily build automated tests for your integrations and APIs. ## [](#august-1-2023)August 1, 2023 ## What’s New - This release includes bug fixes and upgrades to dependencies. ## Compatibility
Application/Service Version

Maven

3.3.3, 3.3.9, 3.5.4, and 3.6.0

Mule runtime

4.1.1 and later

OpenJDK

8 and 11
## Fixed Issues
Issue Resolution ID

MUnit upgrades dependencies to improve compatibility with previous Mule Runtime versions.

W-13804158
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.5.0 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#june-26-2025)June 26, 2025 ## Compatibility
Application/Service Version

Maven

3.8.1 to 3.9.10

Mule runtime engine

4.3 and later

OpenJDK

8, 11, and 17
## Fixed Issues
Issue Resolution ID

The set-event processor is now working as expected in some scenarios.

W-17968564

The runtime-discovery-api MUnit dependency no longer misses the license information.

W-17985556

Munit assertion no longer fails if using assertions 2.9.0.

W-18438097

The mule-sdk-api dependency was updated to its latest version to fix the issue with license information.

W-18201379
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.6.0 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#october-3-2025)October 3, 2025 ## What’s New - MUnit 3.6.0 adds support for Java 21, so you can use the latest features and improvements in your testing framework. - This release includes fixes for vulnerabilities. ## Compatibility
Application/Service Version

Maven

3.8.1 to 3.9.10

Mule runtime engine

4.3 and later

OpenJDK

8, 11, 17, and 21
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.6.1 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#october-3-2025)October 3, 2025 ## What’s New - This release includes fixes for vulnerabilities. ## Compatibility
Application/Service Version

Maven

3.8.1 to 3.9.10

Mule runtime engine

4.3 and later

OpenJDK

8, 11, 17, and 21
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.6.2 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#december-2-2025)December 2, 2025 ## What’s New - This release includes fixes for vulnerabilities. ## Compatibility
Application/Service Version

Maven

3.8.1 to 3.9.10

Mule runtime engine

4.3 and later

OpenJDK

8, 11, 17, and 21
## Fixed Issues
Issue Resolution ID

Verify calls now work correctly if you define some attributes.

W-19826812
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.6.3 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#january-6-2026)January 6, 2026 ## What’s New - This release includes fixes for vulnerabilities. ## Compatibility
Application/Service Version

Maven

3.8.1 to 3.9.10

Mule runtime engine

4.3 and later

OpenJDK

8, 11, 17, and 21
## Fixed Issues
Issue Resolution ID

MUnit now correctly opens the java.naming module to the MUnit starter, preventing access errors when running tests on newer Mule runtime versions.

W-20335051
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.7.0 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#february-3-2026)February 3, 2026 ## What’s New - Standardized Assertion Error Mapping You can now catch and manage assertion failures using standard Mule on-error scopes. To better align with the Mule 4 error handling framework, MUnit now throws a native Mule error type, `MUNIT-TOOLS:ASSERTION_ERROR`, instead of the Java-based `java.lang.AssertionError` error. ## Compatibility
Application/Service Version

Maven

3.8.1 to 3.9.10

Mule runtime engine

4.3 and later*

OpenJDK

8, 11, 17, and 21
\* Compatibility includes support for the latest patch releases of Mule runtime 4.3 and later. ## Fixed Issues
Issue Resolution ID

Assertion failures are no longer incorrectly categorized as critical system errors in Mule runtime 4.11 and later.

W-20874825

XML parsing errors in test files are now properly reported.

W-20661580
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.7.1 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#may-11-2026)May 11, 2026 ## What’s New MUnit 3.7.1 updates some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Maven

3.8.1 to 3.9.15

Mule runtime engine

4.3 and later*

OpenJDK

8, 11, 17, and 21
\* Compatibility includes support for the latest patch releases of Mule runtime 4.3 and later. ## Fixed Issues
Issue Resolution ID

The avro dependency is updated to address a reported vulnerability.

W-22194212

The plexus-utils dependency is updated to address a reported vulnerability.

W-22180688

The transitive aircompressor dependency is updated to address a reported vulnerability.

W-21322135

The log4j dependency is updated to address a reported vulnerability.

W-21562458
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.7.2 Release Notes (Deprecated) MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs.
MUnit 3.7.2 contains a dependency issue. Do not use this version. Use MUnit 3.7.3 instead.
## [](#july-15-2026)July 15, 2026 ## What’s New - Distinct MUnit and MUnit Maven Plugin Properties The `munit.runtimeversion` property replaces the now-deprecated `runtimeVersion` property. The `runtimeVersion` property remains supported, and if you use it, MUnit displays a warning message indicating that it’s deprecated and that you must migrate to `munit.runtimeversion`. For more information, see the [MUnit Maven Plugin](https://docs.mulesoft.com/munit/latest/munit-maven-plugin). - MUnit 3.7.2 updates some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Maven

3.9.0 to 3.9.15

Mule runtime engine

4.3 and later*

OpenJDK

8, 11, 17, and 21
\* Compatibility includes support for the latest patch releases of Mule runtime 4.3 and later. ## Fixed Issues
Issue Resolution ID

The httpcore5 dependency is updated to address reported security vulnerabilities.

W-23333305

The plexus-utils dependency is updated to address a reported security vulnerability.

W-22180688

The transitive aircompressor dependency is updated to address a reported security vulnerability.

W-21322135

Other MUnit dependencies are updated to their latest versions to address reported security vulnerabilities.

W-3300013
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.7.3 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#july-21-2026)July 21, 2026 ## What’s New - MUnit 3.7.3 updates dependencies to fix a dependency issue introduced in [MUnit 3.7.2](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.2-release-notes). Use MUnit 3.7.3 instead of 3.7.2. ## Compatibility
Application/Service Version

Maven

3.9.0 to 3.9.15

Mule runtime engine

4.3 and later*

OpenJDK

8, 11, 17, and 21
\* Compatibility includes support for the latest patch releases of Mule runtime 4.3 and later. ## Fixed Issues
Issue Resolution ID

The httpcore5 dependency is updated to address reported security vulnerabilities.

W-23333305

The plexus-utils dependency is updated to address a reported security vulnerability.

W-22180688

The transitive aircompressor dependency is updated to address a reported security vulnerability.

W-21322135

Other MUnit dependencies are updated to their latest versions to address reported security vulnerabilities.

W-3300013
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.7.4 Release Notes MUnit is a Mule application testing framework that enables you to build automated tests for your integrations and APIs. ## [](#september-1-2026)September 1, 2026 ## What’s New - MUnit 3.7.4 updates some dependencies to address reported security vulnerabilities. ## Compatibility
Application/Service Version

Maven

3.9.0 to 3.9.15

Mule runtime engine

4.3 and later*

OpenJDK

8, 11, 17, and 21
\* Compatibility includes support for the latest patch releases of Mule runtime 4.3 and later. ## Fixed Issues
Issue Resolution ID

The jsoup dependency is updated to address a reported security vulnerability.

W-23887272

Quarantined MuleSoft dependencies are updated to address a reported security vulnerability and a missing license.

W-23799750

MUnit artifacts now declare the MuleSoft MSA license as expected.

W-23799718

The munit-jfr-default module is updated to address a reported issue.

W-20926401

Other MUnit dependencies are updated to their latest versions to address reported security vulnerabilities.

W-3300013
## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit 3.7.5 Release Notes MUnit is a Mule application testing framework for building automated tests for your integrations and APIs. ## [](#october-7-2026)October 7, 2026 ## What’s New - MUnit now supports Mule runtime engine 4.13.0, which includes new features and enhancements. For more information, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). ## Compatibility
Application/Service Version

Maven

3.9.0 to 3.9.15

Mule runtime engine

4.3 and later*

OpenJDK

8, 11, 17, and 21
\* Compatibility includes support for the latest patch releases of Mule runtime 4.3 and later. ## [](#see-also)See Also - [MUnit](https://docs.mulesoft.com/munit/latest/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.10 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#may-4-2023)May 4, 2023 ## What’s New - You can now select the XML files to ignore in the **MUnit Coverage Report**. ## Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.15.0 and later
## Fixed Issues
Issue Resolution ID

MUnit no longer ignores the Maven parameters set for the package in the base command line when configuring the build.

W-11747640

MUnit now correctly changes the configuration XML values after refactoring.

W-11822737
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.11 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#november-9-2023)November 9, 2023 ## Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.16.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.12 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#march-20-2024)March 20, 2024 ## What’s New - MUnit Studio Plugin now supports Java 17. ## Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.17.0 and later
## Fixed Issues
Issue Resolution ID

MUnit test recorder now correctly supports mediaType with parameters.

W-12211439
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.13 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#june-4-2024)June 4, 2024 ## Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.18.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.14 Release Notes The MUnit Anypoint Studio Plugin enables you to run MUnit tests and use the MUnit Test Recorder in Anypoint Studio. ## [](#october-8-2024)October 8, 2024 ## Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.19.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.15 Release Notes The MUnit Anypoint Studio Plugin enables you to run MUnit tests and use the MUnit Test Recorder in Anypoint Studio. ## [](#february-6-2025)February 6, 2025 ## Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.19.0 and later
## Fixed Issues
Issue Resolution ID

The test recorder no longer fails if used in Java 17 projects.

W-16478891
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.18 Release Notes The MUnit Anypoint Studio Plugin enables you to run MUnit tests and use the MUnit Test Recorder in Anypoint Studio. You can install this version of the MUnit Anypoint Studio Plugin using the [update site](https://studio.mulesoft.org/s23.1/munit). ## [](#january-9-2026)January 9, 2026 ## Compatibility
Application/Service Version

Mule runtime

4.3.0 and later

Anypoint Studio

7.21.0 and later
## Fixed Issues
Issue Resolution ID

MUnit now correctly opens the java.naming module to the MUnit starter, preventing access errors when running tests on newer Mule runtime versions.

W-20335051
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.2 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#april-29-2021)April 29, 2021 ## Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.9.0 and later
## Fixed Issues
Issue ID

MUnit Test Recorder no longer fails with a "There was a problem processing the interception" message when processing GET resources.

SE-18852

Running an MUnit test no longer clears the Run as configurations saved for the MUnit tests.

SE-19115

MUnit Test Recorder no longer fails when a Choice Router component has an empty default option

SE-18967
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.3 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#july-29-2021)July 29, 2021 ## Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.10.0 and later
## Fixed Issues
Issue ID

The groupId paremeter from the plugins used to build the projects no longer use a property placeholder.

MUSP-995

Fixed the plugin’s metadata description shown in Studio.

MUSP-994

Anypoint Studio no longer throws errors if org.mule.weave.assertions is not declared in pom file.

MUSP-990

Fixed an issue that prevented MUnit from working if no previous Run configurations existed.

STUDIO-16448
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.4 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. This version is deprecated. All of the features and fixed issues for this version are in version 2.7.8. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.5 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. This version is deprecated. All of the features and fixed issues for this version are in version 2.7.8. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.6 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. This version is deprecated. All of the features and fixed issues for this version are in version 2.7.8. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.7 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. This version is deprecated. All of the features and fixed issues for this version are in version 2.7.8. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.8 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#july-28-2022)July 28, 2022 ## Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.10.0 and later
## Fixed Issues
Issue ID

MUnit test recorder no longer copies mimetype parameters without checking if they are write or read parameters.

W-11094080

Now you can toggle comment the first or last part of the flow from the context menu.

W-11120694

The context menu components are no longer wrongly displayed when the first or the last processor in a flow is commented.

W-11359261
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Anypoint Studio Plugin 2.7.9 Release Notes The MUnit Anypoint Studio Plugin is a plugin that enables you to run MUnit tests from Anypoint Studio. It also enables you to use the MUnit Test Recorder in Studio. ## [](#october-27-2022)October 27, 2022 ## Compatibility
Application/Service Version

Mule

4.3.0 and later

Anypoint Studio

7.10.0 and later
## Fixed Issues
Issue ID

MUnit Test takes naming convention into consideration in custom headers.

W-11424317

MUnit Test Recorder no longer throws a NullPointerException error when using async scopes in the Choice Router case.

W-11418737

Some expression fields are now displayed with the appropriate expression icons and buttons in the Then Return section.

W-10624641
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Release Notes These release notes are provided for MUnit. ## [](#munit-3-x)MUnit 3.x - [MUnit 3.7.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.5-release-notes) - [MUnit 3.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.4-release-notes) - [MUnit 3.7.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.3-release-notes) - [MUnit 3.7.2 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.2-release-notes) - [MUnit 3.7.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.1-release-notes) - [MUnit 3.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.0-release-notes) - [MUnit 3.6.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.3-release-notes) - [MUnit 3.6.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.2-release-notes) - [MUnit 3.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.1-release-notes) - [MUnit 3.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.0-release-notes) ## [](#munit-2-x)MUnit 2.x - [MUnit 2.3.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit/munit-2.3.18-release-notes)
For previous versions of MUnit 1.x, 2.x, and 3.x that reached end of life, see the MUnit Release Notes Archive.
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Studio Plugin - [MUnit Studio Plugin 2.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.18-release-notes) - [MUnit Studio Plugin 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.15-release-notes) - [MUnit Studio Plugin 2.7.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.14-release-notes) - [MUnit Studio Plugin 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.13-release-notes) - [MUnit Studio Plugin 2.7.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.12-release-notes) - [MUnit Studio Plugin 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.11-release-notes) - [MUnit Studio Plugin 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.10-release-notes) - [MUnit Studio Plugin 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.9-release-notes) - [MUnit Studio Plugin 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.8-release-notes) - [MUnit Studio Plugin 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.7-release-notes) - [MUnit Studio Plugin 2.7.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.6-release-notes) - [MUnit Studio Plugin 2.7.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.5-release-notes) - [MUnit Studio Plugin 2.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.4-release-notes) - [MUnit Studio Plugin 2.7.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.3-release-notes) - [MUnit Studio Plugin 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.2-release-notes) - [MUnit Studio Plugin 2.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.7.0-release-notes) - [MUnit Studio Plugin 2.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.6.0-release-notes) - [MUnit Studio Plugin 2.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.5.1-release-notes) - [MUnit Studio Plugin 2.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.5.0-release-notes) - [MUnit Studio Plugin 2.4.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-2.4.2-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Studio Plugin 2.4.2 Release Notes **April 14, 2020** This release contains the beta version of the MUnit test recorder and fixes bugs. ## [](#compatibility)Compatibility
Software Version

Mule

Mule 4.1.1 or higher

Anypoint Studio

Anypoint Studio 7.4.2
## [](#features-and-functionality)Features and Functionality - Beta feature of MUnit test recorder. The test recorder enables you to record a processing flow and then configure a unit test based on the captured event. See [Test Recorder in Studio](https://docs.mulesoft.com/munit/latest/test-recorder) for more information. ## [](#known-issues)Known Issues - The test recorder does not support custom VM arguments. ## [](#bug-fixes)Bug Fixes - Changed `Attribute` to `Attributes` in the custom editors. - Fixed issue where `RunConfiguration` did not propagate the security settings path. - Fixed issue where the test recorder did not allow you to select or configure routers or scopes. - Fixed issue where the test recorder did not use a set event and assert output by default. - Fixed issue where a `doc:id` element was not added to the Spy, Mock, and Verify processors. - The test recorder now selects all elements for the set event by default. - Fixed issue where the test recorder prevented you from testing error handlers inside a flow. - Fixed issue where the test recorder did not select all trees when there were multiple interceptions. - Fixed issue where the test recorder did not allow you to define an action on a Parallel For-Each processor. - Fixed issue on the test recorder where a warning on a Spy processor with multiple events cut off the Action Selector view. - Fixed issue on the test recorder where the key of an entry inside a map with an empty map as a value was not shown as bold. - The Run Configuration view now uses the project’s name instead of the POM file name. - Fixed issue where MUnit always included the REST Connector `module-*.xml` for coverage rate report. ## [](#enhancements)Enhancements - The test recorder now creates a single Run Configuration option for each type of run. - Amplitude now displays the `payload` property. - The test recorder’s tree view no longer requires you to double-click the elements to expand them. - The `was called` key for the Verify processor option now shows a default value based on the intercepted events. - The test recorder now shows the saved configuration of a selected processor. - The test recorder now saves your configuration changes automatically every time you change views in the tree selector. - You can no longer define mocks on the `ee-transform` and `logger` processors. - The defined behaviors in the test recorder are now based on type of processor being configured. - The test recorder now validates the actions defined while recording and shows a summary before creating the test. ## [](#story)Story There are no stories for this release. ## [](#support)Support - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Studio Plugin 2.5.0 Release Notes **April 30, 2020** This release inclues the GA version of the MUnit test recoder feature on Studio ## [](#compatibility)Compatibility
Software Version

Mule

Mule 4.3.0 or higher

Anypoint Studio

Anypoint Studio 7.5.0
## [](#features-and-functionality)Features and Functionality - GA feature of MUnit test recorder. The test recorder enables you to record a processing flow and then configure a unit test based on the captured event. See [Test Recorder in Studio](https://docs.mulesoft.com/munit/latest/test-recorder) for more information. ## [](#known-issues)Known Issues - The test recorder does not support custom VM arguments. - Modifying an existing Mock processor in your canvas might duplicate the XML code of that processor. ## [](#fixed-issues)Fixed Issues - Improved error logs for when the test recorder fails. - You can now define your Maven repository when pre-packaging an app. ## [](#support)Support - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Studio Plugin 2.5.1 Release Notes **June 1, 2020** This releases focuses on bug fixes. ## [](#compatibility)Compatibility
Software Version

Mule

Mule 4.3.0 or higher.

Anypoint Studio

Anypoint Studio 7.5.0 or higher.
## [](#known-issues)Known Issues - Modifying an existing Mock processor in your canvas might duplicate the XML code of that processor. ## [](#fixed-issues)Fixed Issues - Added support for custom VM arguments for the test recorder. - Removed options to record tests for flows inside the `src/test/munit` directory. - Removed unnecessary `api/` value from the `raml` attribute in APIkit. - Console logs are no longer deleted after you cancel a test record, or after the test recorder finishes recording your flow. - Fixed issue that prevented Studio from using the same parameterization configuration, if a previous configuration already existed for a project. ## [](#support)Support - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Studio Plugin 2.6.0 Release Notes **July 30, 2020** This release focuses on bug fixes and introduces support for big payloads in the MUnit test recorder. ## [](#compatibility)Compatibility - Mule 4.3.0 or higher - Anypoint Studio 7.6.0 or higher ## [](#known-issues)Known Issues There are no known issues for this release. ## [](#fixed-issues)Fixed Issues - Fixed a potential XXE vulnerability in `mule-tooling-munit`. - Fixed an issue in which a big memory load caused the JVM to stop. - Fixed an issue in which the Mock editor introduced duplicate XML entries. ## [](#support)Support - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # MUnit Studio Plugin 2.7.0 Release Notes **October 29, 2020** This release fixes bugs. ## [](#compatibility)Compatibility - Mule 4.3.0 or higher - Anypoint Studio 7.7.0 or higher ## [](#known-issues)Known Issues There are no known issues for this release. ## [](#fixed-issues)Fixed Issues - Fixed an issue in which a `mock-when` processor caused a UI glitch when updating the Dataweave expression field. - Added the **Go to Node** menu option in the XML configuration tab of the MUnit source tab. ## [](#support)Support - [MuleSoft Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/neighborhoods/mulesoft) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Neo4j Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Neo4j (Neo4j Connector) provides the capability to execute Cypher Query Language (CQL) statements and run basic operations, such as create, update, delete, and select nodes in a Neo4j Graph database instance. Guide: [Neo4j Connector Guide](https://docs.mulesoft.com/neo4j-connector/latest/) ## [](#4-0-4)4.0.4 **October 21, 2026** ### Compatibility
Software Version

Mule

4.9.0 and later

Neo4j Bolt API

5.28.15

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The Guava library is upgraded to version 33.7.2-jre to address reported security vulnerabilities.

W-24542330
## [](#4-0-3)4.0.3 **September 18, 2026** ### Compatibility
Software Version

Mule

4.9.0 and later

Neo4j Bolt API

5.28.15

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Neo4j Java driver is upgraded to version 5.28.15.

  • The Netty Handler library is upgraded to version 4.2.18.Final.

  • The Reactor Core library is upgraded to version 3.8.7.

W-24117520
## [](#4-0-2)4.0.2 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.9.0 and later

Neo4j Bolt API

5.28.14

OpenJDK

17
## [](#4-0-1)4.0.1 **July 27, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - The Neo4j Java driver is upgraded to 5.28.14. ### Compatibility
Software Version

Mule

4.9.0 and later

Neo4j Bolt API

5.28.14

OpenJDK

17
## Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Guava library is upgraded to version 33.6.0-jre.

  • The Gson library is upgraded to version 2.14.0.

  • The Commons IO library is upgraded to version 2.22.0.

W-23441591
## [](#4-0-0)4.0.0 **September 14, 2025** ### What’s New - The connector is now fully compatible with modern Neo4j versions (4.4 and later) and the latest Mule runtime engines (4.9.0 and later), leveraging the updated Neo4j Java driver. - The connector simplifies configuration to only require a BOLT URL, as all metadata operations use native Cypher queries through a BOLT connection. The `REST URL` parameter is now removed. - The connector offers improved metadata resolution for a smoother experience in Anypoint Studio, providing access to new features such as reactive APIs, multi-database support, and enhanced security. - The connector no longer supports Neo4j 3.x servers, Mule runtime versions earlier than 4.9.0, or JDK versions earlier than 17. ### Compatibility
Software Version

Mule

4.9.0 and later

Neo4j Bolt API

5.28.8

OpenJDK

17
## [](#3-0-9)3.0.9 **October 21, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.6

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Guava library is upgraded to version 33.7.2-jre to address reported security vulnerabilities.

W-24542195
## [](#3-0-8)3.0.8 **September 29, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.6

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Commons IO library is upgraded to version 2.22.0.

  • The Gson library is upgraded to version 2.14.0.

W-24282053
## [](#3-0-7)3.0.7 **July 4, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.6

OpenJDK

8, 11, and 17
## [](#3-0-6)3.0.6 **June 14, 2023** ## Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.6
See the [Neo4j Java driver v1.7 change log](https://github.com/neo4j/neo4j-java-driver/wiki/1.7-changelog). ## Fixed Issues
Issue Resolution ID

Updated the following dependencies: Google Guava from 25.1-jre to 32.0.1-jre, Google Gson from 2.8.9 to 2.10.1, commons-io from 2.7 to 2.13.0, and neo4j-java-driver from 1.7.5 to 1.7.6.

W-13464607
## [](#3-0-5)3.0.5 **November 12, 2021** ## Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.5
See the [Neo4j Java driver v1.7 change log](https://github.com/neo4j/neo4j-java-driver/wiki/1.7-changelog). ## Fixed Issues
Issue ID

Fixed vulnerability issues.

CONN-9291
## [](#3-0-4)3.0.4 **September 7, 2020** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.5
See the [Neo4j Java driver v1.7 change log](https://github.com/neo4j/neo4j-java-driver/wiki/1.7-changelog). ### [](#features)Features - Fixed vulnerability issues (CONN-6883). ## [](#3-0-3)3.0.3 **November 6, 2019** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.5
See the [Neo4j Java driver v1.7 change log](https://github.com/neo4j/neo4j-java-driver/wiki/1.7-changelog). ### [](#features-2)Features - Downgraded parent to restore compatibility with Runtime version 4.1.1. ## [](#3-0-2)3.0.2 **November 4, 2019** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.2.0 and later

Neo4j Bolt API

1.7.5
See the [Neo4j Java driver v1.7 change log](https://github.com/neo4j/neo4j-java-driver/wiki/1.7-changelog). ### [](#features-3)Features - Internal improvements - Added logging to the DEBUG level to aid troubleshooting. ## [](#3-0-1)3.0.1 **August 27, 2019** This release updates the Neo4j Bolt API to version 1.7.5. ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later

Neo4j Bolt API

1.7.5
See the [Neo4j Java driver v1.7 change log](https://github.com/neo4j/neo4j-java-driver/wiki/1.7-changelog). ## [](#3-0-0)3.0.0 **January 31, 2018** This release updates Neo4j for Mule 4. ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.0 and later

Neo4j Bolt API

1.5
See the [Neo4j Java driver v1.5 change log](https://github.com/neo4j/neo4j-java-driver/wiki/1.5-changelog). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # NetSuite Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for NetSuite synchronizes data and automates business processes between NetSuite and third-party applications, either on-premises or in the cloud. Guide: [NetSuite Connector Guide](https://docs.mulesoft.com/netsuite-connector/latest/) Reference: [NetSuite Connector Reference](https://docs.mulesoft.com/netsuite-connector/latest/netsuite-reference) ## [](#12-0-3)12.0.3 **October 15, 2026** ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17

SuiteTalk API

2020.2, 2021.1, 2023.1, 2025.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind and jackson-dataformat-xml libraries are upgraded to version 2.22.3.

  • The groovy, groovy-xml, and groovy-json libraries are upgraded to version 3.0.25.

  • The cxf-core, cxf-rt-wsdl, cxf-rt-ws-rm, cxf-rt-ws-security, cxf-rt-frontend-simple, cxf-rt-frontend-jaxws, and cxf-rt-transports-http libraries are upgraded to version 4.1.9.

  • The bcprov-jdk18on, bcpkix-jdk18on, and bcutil-jdk18on libraries are upgraded to version 1.85.

W-24262985, W-24406484, W-24442565

spring-core and spring-expression 6.2.19 are no longer on the connector classpath. If your application uses those Spring classes from the connector, add Spring as an application dependency.

W-24442565
## [](#12-0-2)12.0.2 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17

SuiteTalk API

2020.2, 2021.1, 2023.1, 2025.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The cxf-core library is upgraded to version 4.1.8.

  • The cxf-rt-wsdl library is upgraded to version 4.1.8.

  • The httpclient5 library is upgraded to version 5.6.4.

  • The httpcore5 library is upgraded to version 5.4.3.

  • The httpcore5-h2 library is upgraded to version 5.4.3.

  • The spring-core library is upgraded to version 6.2.19.

  • The spring-expression library is upgraded to version 6.2.19.

  • The jaxb-api library is upgraded to version 2.3.1.

  • The groovy library is upgraded to version 2.5.23.

W-24137088
## [](#12-0-1)12.0.1 **August 31, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17

SuiteTalk API

2020.2, 2021.1, 2023.1, 2025.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The cxf-core library is upgraded to version 4.1.7.

  • The kotlin-stdlib library is upgraded to version 2.3.0.

  • The jakarta.annotation-api library is upgraded to version 2.1.1.

  • The log4j-core, log4j-api, log4j-1.2-api, and `log4j-slf4j-impl libraries are upgraded to version 2.25.5.

  • The jetty-http,jetty-io, jetty-security, jetty-ee10-webapp, and jetty-ee10-servlet libraries are upgraded to version 12.1.12.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-text library is upgraded to version 1.15.0.

  • The jackson-databind library is upgraded to version 2.21.6.

  • The jackson-dataformat-xml library is upgraded to version 2.22.2.

  • The httpclient library is upgraded to version 4.5.14.

W-23441885
## [](#12-0-0)12.0.0 **May 12, 2026** ### What’s New - This connector is now compatible with Java 17 only. ### Compatibility
Software Version

Mule

4.9.0 and later

OpenJDK

17

SuiteTalk API

2020.2, 2021.1, 2023.1, 2025.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The springframework library is upgraded to version 6.2.

  • The jakarta.activation-api library is upgraded to version 2.1.4.

  • The wiremock.server.dependency library is upgraded to version 3.0.1.

  • The PowerMock library is replaced by Mockito version 5.2.0.

  • The commons-io library is added at version 2.16.1.

  • The cxf-core library is upgraded to 3.6.8.

  • The commons-text library is upgraded to version 1.14.0.

  • The log4j library is upgraded to version 2.25.4.

W-21872201

The connector no longer supports the Omit the internal Id in the name of the custom field field because its functionality is now the default behavior of the connector.

W-21739489, W-22024490
## [](#11-11-2)11.11.2 **March 19, 2026** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1, 2025.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The cxf-core library is upgraded to version 3.5.11.

  • The jackson-databind library is upgraded to version 2.21.1.

  • The jackson-dataformat-xml library is upgraded to version 2.21.1.

  • The spring.version library is upgraded to version 5.3.39-spring-framework-5.3.49.

W-21522009
## [](#11-11-1)11.11.1 **December 20, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1, 2025.2
### Fixed Issues
Issue Resolution ID

The connector now correctly resolves metadata and no longer throws the java.lang.reflect.InaccessibleObjectException error when using Anypoint Studio 7.21 with Java 17.

W-19704550
## [](#11-11-0)11.11.0 **November 20, 2025** ### What’s New - The WSDL library is upgraded to version 2025\_2. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1, 2025.2
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The springframework.version library is upgraded to version 5.3.39-spring-framework-5.3.45.

W-20107375
## [](#11-10-1)11.10.1 **June 3, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
### Fixed Issues
Issue Resolution ID

The dependencies of the remaining runtime provided SOAP modules are removed.

W-18605074
## [](#11-10-0)11.10.0 **March 4, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
### Fixed Issues
Issue Resolution ID

The Get Deleted operation now works for a deleted record count greater than 1000.

W-17141016

The On Deleted Object source now supports page size.

W-17471322
## [](#11-9-4)11.9.4 **August 26, 2024** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
### Fixed Issues
Issue Resolution ID

The custom field list for the ESTIMATE object is now populated.

W-16469704
## [](#11-9-3)11.9.3 **July 19, 2024** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
### Fixed Issues
Issue Resolution ID

The Add operation no longer throws the java.io.IOException: Resetting to invalid mark error.

W-16208142
## [](#11-9-2)11.9.2 **July 1, 2024** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
### Fixed Issues
Issue Resolution ID

The Connection Timeout field now correctly uses its specified value.

W-16099635
## [](#11-9-1)11.9.1 **June 13, 2024** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
### Fixed Issues
Issue Resolution ID

The custom field list for input metadata is now populated.

W-15880323
## [](#11-9-0)11.9.0 **April 29, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
## [](#11-8-1)11.8.1 **January 31, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17

SuiteTalk API

2020.2, 2021.1, 2023.1
## [](#11-8-0)11.8.0 **October 6, 2023** ### What’s New - The WSDL library is upgraded to version 2023\_1. ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1, 2023.1
## [](#11-7-18)11.7.18 **August 17, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13896697
## [](#11-7-17)11.7.17 **July 12, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The overall performance is improved and custom fields support is extended.

W-13672602

The connection is now properly kept alive when request execution takes a long time.

W-13738929
## [](#11-7-16)11.7.16 **June 8, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13552619
## [](#11-7-15)11.7.15 **June 1, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13484699
## [](#11-7-14)11.7.14 **May 30, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13222742, W-13304252, W-13481333
## [](#11-7-13)11.7.13 **May 4, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The connector now retrieves the metadata for custom fields for the SALES_ORDER record type.

W-13096977
## [](#11-7-12)11.7.12 **April 24, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13001785
## [](#11-7-11)11.7.11 **March 30, 2023** ### What’s New - The mule-soap-engine library is upgraded to version 1.8.0 to address reported security vulnerabilities. ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The mule-soap-engine library is upgraded to version 1.8.0 to address reported security vulnerabilities.

W-12631710
## [](#11-7-10)11.7.10 **March 23, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The metadata for the FILE object in the Add operation now works as intended.

W-12243962

The Type dropdown in the Get all operation no longer causes a NETSUITE_SOAP_FAULT error.

W-12572300

The connector no longer fails to parse the com.sun.xml.internal.stream.events.EndElementEvent error response.

W-12573323
## [](#11-7-9)11.7.9 **January 26, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

Metadata load logging is now enhanced.

W-12412287, W-12244102
## [](#11-7-8)11.7.8 **January 20, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12135181, W-12135186, W-12244824
## [](#11-7-7)11.7.7 **December 16, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

The On New Record and On Modified Record sources no longer throw a NullPointerException when retrieving transaction objects.

W-12106243
## [](#11-7-6)11.7.6 **November 16, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue Resolution ID

Mapping now works properly when the same custom list field is between multiple items in one record.

W-12041041
## [](#11-7-5)11.7.5 **November 3, 2022** ### What’s New - The com.fasterxml.jackson.core library is upgraded to version 2.13.4.2. ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.13.4.2 to address reported security vulnerabilities.

W-11963381
## [](#11-7-4)11.7.4 **October 25, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

The jackson-databind package is upgraded to version 2.13.4 to fix reported security vulnerabilites.

W-11939647
## [](#11-7-3)11.7.3 **October 20, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

The apache commons-text package is upgraded from version 1.9 to 1.10.0 and the jackson-databind is upgraded from version 2.12.6.1 to 2.12.7.1 to fix reported security vulnerabilites.

W-11932287
## [](#11-7-2)11.7.2 **October 12, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11515696
## [](#11-7-1)11.7.1 **September 9, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

Mapping a large amount of custom fields of a response from NetSuite no longer causes performance degradation.

W-11680893
## [](#11-7-0)11.7.0 **August 4, 2022** ### What’s New - You can now control the **Run server SuiteScript and trigger workflows** field on a request level. To access this field, go to the **Preferences** section on the **Advanced** tab when configuring a connection. ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

Connections that use lower case values in the Account ID field no longer fail.

W-11385704

The ability to control the Run server SuiteSript and trigger workflows field on a request level is now restored.

W-11416782

Logging is now improved when parsing a SOAP failure.

W-11424966
## [](#11-6-0)11.6.0 **July 27, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### What’s New - NetSuite Connector now supports exponential retries which prevent concurrency limit errors. To enable this feature, go to NetSuite Config > General tab > Advanced tab and select **Edit inline** inside the **Concurrency Management Strategy** combo box to set values for **Max Retries** and **Max Waiting Time Between Retries**. For more information, refer to [NetSuite Connector Reference](https://docs.mulesoft.com/netsuite-connector/latest/netsuite-reference#RandomizedExponentialBackoff.adoc). - NetSuite Connector now supports concurrency management, which introduces the following new fields. For more information, refer to [NetSuite Connector Reference](https://docs.mulesoft.com/netsuite-connector/latest/netsuite-reference#Config_TokenBasedAuthentication.adoc). - **Concurrency Management Strategy** - **Show warnings as errors** - **Disable mandatory custom field validation** - **Disable system notes for custom fields** - **Ignore read-only fields** - **Run server SuiteScript and trigger workflows** ## [](#11-5-13)11.5.13 **July 25, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11302334
## [](#11-5-12)11.5.12 **May 27, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the spring-beans package from org.springframework:spring-beans:5.3.19 to org.springframework:spring-beans:5.3.20.

W-11195298
## [](#11-5-11)11.5.11 **May 25, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11090343
## [](#11-5-10)11.5.10 **May 19, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the spring-context package from org.springframework:spring-context:5.3.3 to org.springframework:spring-context:5.3.19.

W-11102933
## [](#11-5-9)11.5.9 **May 4, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10807846, W-10807856, W-10995359
## [](#11-5-8)11.5.8 **April 4, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Fixed vulnerabilities found in the jackson-databind, spring-expression, spring-beans, and soap-model-code dependencies.

W-10927725, W-10920507, W-10920506, W-10920486
## [](#11-5-7)11.5.7 **March 28, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10663982, W-10574265, W-10574268
## [](#11-5-6)11.5.6 **March 22, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

The saved search results did not return all the records when Page size was specified in the Search preferences tab.

W-10839437
## [](#11-5-5)11.5.5 **February 21, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10662701
## [](#11-5-4)11.5.4 **February 6, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-933
## [](#11-5-3)11.5.3 **February 2, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-898, COCN-891
## [](#11-5-2)11.5.2 **January 5, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-875
## [](#11-5-1)11.5.1 **December 1, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

SE-23496, SE-23128, SE-23068, SE-22936, SE-22758, COCN-703, COCN-735, SE-22726
## [](#11-5-0)11.5.0 **October 26, 2021** ### What’s New - Added the **Wsdl version** parameter, which enables you to choose which version of WSDL the connector uses. ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2, 2021.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
## [](#11-4-1)11.4.1 **October 7, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Fixed data transformation for the sources.

COCN-665
## [](#11-4-0)11.4.0 **October 6, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Added the Omit the internal Id in the name of the custom field parameter, which removes the obligatory use of an internal ID field in custom fields.

SE-22816
## [](#11-3-2)11.3.2 **September 24, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

SE-21514
## [](#11-3-1)11.3.1 **August 27, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

MCOM-482
## [](#11-3-0)11.3.0 **August 17, 2021** ### What’s New - Added support for custom fields and custom records with metadata. ### Compatibility
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### Fixed Issues
Issue ID

Displaying and calling a custom field no longer results in an error if you are not using custom field types.

CONN-7884
### Known Issues
Known Issue Workaround ID

The custom field type is missing.

Users must modify the reference to include the custom field type, for example, you must use StringCustomFieldRef__custcol_sf_line_item instead of __custcol_sf_line_item.

CONN-7884
## [](#11-2-6)11.2.6 **July 15, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-51)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#11-2-5)11.2.5 **June 30, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-52)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#11-2-4)11.2.4 **June 24, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-53)Fixed Issues - Optimized the connector to improve stability. ## [](#11-2-3)11.2.3 **June 7, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. If you are using this connector in a batch job in the on-premises environment, you must back up and remove the old batch cache folder <MULE_HOME>/.mule/<app>/.
### [](#fixed-issues-54)Fixed Issues - Could not deserialize the object when using NetSuite in a batch scope. (SE-21004) ## [](#11-2-2)11.2.2 **June 1, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-55)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#11-2-1)11.2.1 **May 27, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-56)Fixed Issues - Fixed the HTTP header case to match the format of the new changes in the NetSuite API. ## [](#11-2-0)11.2.0 **May 14, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#new-features)New Features - Improved the metadata resolution for the **Search** operation. - Implemented metadata for `RefType` in the **Get**, **Get List**, **Delete**, and **Delete List** operations. ### [](#fixed-issues-57)Fixed issues - Fixed the metadata keys to appear as lowercase in the **Get All** operation. - Fixed the invalid metadata keys in the **Get All** operation. ## [](#11-1-0)11.1.0 **April 28, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#features)Features - Enabled metadata for the **Attach** and **Detach** operations. - Improved the metadata resolution for the paginated operations (**Get deleted**, **Get select value**, and **Get posting transaction summary**). - Fixed the metadata keys to appear as lowercase in the **Get** operation. - Moved the **SOAP Port** parameter from the **Advanced** tab to the **General** tab in Connector configuration. - Fixed the incorrect error message when the SOAP port is invalid. ### [](#fixed-issues-58)Fixed Issues - The connector can now propagate error codes and messages to Mule. (SE-20239) ## [](#11-0-2)11.0.2 **April 14, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-59)Fixed Issues - Improved error handling to return better information about the cause of the error returned by NetSuite. (CCONN-775) ## [](#11-0-1)11.0.1 **April 08, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-60)Fixed Issues - Optimized the connector to improve its overall performance. ## [](#11-0-0)11.0.0 **March 16, 2021**
Software Version

Mule

4.2.0 and later

SuiteTalk API

2020.2
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#features-2)Features - The input and output of all operations are now in XML. - Implemented XML metadata for all operations. - Changed operation names and fields. - Improved the error types. - Removed the request-based connection type. For more information, see [Upgrade to NetSuite Connector 11.x](https://docs.mulesoft.com/netsuite-connector/latest/netsuite-connector-upgrade-migrate). ### [](#fixed-issues-61)Fixed Issues - Fixed timezone truncated when sent to NetSuite. (SE-18308) - Fixed DW transformation fails while resolving NetSuite classes. (SE-19040) - Fixed Record status is not being mapped on the response of Initialize List operation. (SE-17765) ## [](#10-0-10)10.0.10 **September 15, 2021**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-62)Fixed Issues - Sudden disconnections occurred due to high concurrency. (SE-22214) ## [](#10-0-9)10.0.9 **June 24, 2021**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-63)Fixed Issues - Fixed a `NoSuchMethod` exception in the REST operations caused by an old version of the Jackson dependency. (SE-21523) ## [](#10-0-8)10.0.8 **June 9, 2021**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-64)Fixed Issues - The **Internal Id** parameter in the **Get Custom Record** operation is now optional. (CONN-6761) ## [](#10-0-7)10.0.7 **May 6, 2021**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-65)Fixed Issues - The connector now sets the Signature Algorithm correctly. The Signature Algorithm also now includes two options with dashes instead of underscores (HMAC-SHA1 and HMAC-SHA256). (SE-20679) ## [](#10-0-6)10.0.6 **January 19, 2021**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-66)Fixed Issues - Fixed security issues. (CONN-7301) ## [](#10-0-5)10.0.5 **December 23, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-67)Fixed Issues - Fixed the issue that caused connections used an excessive amount of heap space. (SE-17302) - Fixed the issue that caused Netsuite Connector to not parse the `shipStatus` enum in Mule 4. (SE-16268) . ## [](#10-0-4)10.0.4 **November 30, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-68)Fixed Issues Fixed the issue in which signatures for RESTlet calls were not being created correctly when query parameters contained blank spaces. (SE-18374) ## [](#10-0-3)10.0.3 **November 27, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#features-3)Features Added a timezone parameter to the connector when specifying fields that are dates. ### [](#fixed-issues-69)Fixed Issues Fixed an issue of parsing the date with the timezone (SE-18308) ## [](#10-0-2)10.0.2 **September 16, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#features-4)Features None. ### [](#fixed-issues-70)Fixed Issues - Fixed security issues (CONN-6977) - Date fields were not sent to NetSuite on the SOAP request (SE-17112) ## [](#10-0-1)10.0.1 **August 3, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#features-5)Features None. ### [](#fixed-issues-71)Fixed Issues - Adding or updating custom records caused an exception to be thrown. (SE-16881) - No metadata was provided for custom record types. ## [](#10-0-0)10.0.0 **July 15, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2020.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#features-6)Features NetSuite Connector 10.0 includes the following new features: - SuiteTalk 2020.1 is now supported, and support for SuiteTalk 2019.1 is deprecated. - Two new operations were added: - **Get Account Governance Info** - **Get Integration Governance Info** ### [](#changed-features)Changed Features NetSuite 10.0 includes the following changes: - The Login and SSO authentication types were removed. If your integration is based on these authentication types, you must migrate to a Request or Token-Based authentication type. - Other nonfunctional changes were applied to the interface of the connector to make it more consistent with other Anypoint Connectors. This means that some of the operation calls in your existing application might not initially work until some minor migration tasks are performed. - Unknown errors are now thrown as `ANY` rather than `UNKNOWN`. Consequently, error codes `DISPOSE_ERROR`, `MAPPING_ERROR`, `CANT_READ_FILE`, and `TRIGGER` are now considered `ERROR_FAULT` errors instead of `UNKNOWN`. ### [](#fixed-issues-72)Fixed Issues - Some recently discovered vulnerabilities in underlying libraries were fixed. ## [](#9-3-5)9.3.5 **June 26, 2021**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-73)Fixed Issues - The connector now sets the Signature Algorithm correctly. The Signature Algorithm also now includes the HMAC-SHA1 and HMAC-SHA256 options with dashes instead of underscores. (SE-21504) ## [](#9-3-4)9.3.4 **November 30, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-74)Fixed Issues Fixed the issue in which signatures for RESTlet calls were not being created correctly when query parameters contained blank spaces. (SE-18374) ## [](#9-3-3)9.3.3 **November 24, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-75)Fixed Issues Fixed the issue in which connections used an excessive amount of heap space. (SE-17302) ## [](#9-3-2)9.3.2 **September 17, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-76)Fixed Issues Reported vulnerabilities are fixed (CONN-6978) ## [](#9-3-1)9.3.1 **August 11, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using.
### [](#fixed-issues-77)Fixed Issues - The issue that caused Netsuite Connector not to parse the `shipStatus` enum in Mule 4 is fixed. (SE-16268) . - Reported vulnerabilities are fixed. ## [](#9-3-0)9.3.0 **June 22, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
- The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#features-7)Features Improved the Netsuite metadata for operations as part of the fix for CONN-4945. ### [](#fixed-issues-78)Fixed Issues Improved keys for the default record types. (CONN-4585) Connections now use the `Read timeout` field set by the user for the `Get Data Center URLs` operation. ## [](#9-2-9)9.2.9 **June 11, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
- The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-79)Fixed Issues - Fixed a memory leak. (SE-15923) ## [](#9-2-8)9.2.8 **June 5, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
- The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-80)Fixed Issues - An intermittent authentication failure occurred due to the nonce used when performing token-based authentication with concurrent requests. (SE-15887) ## [](#9-2-7)9.2.7 **May 18, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
- The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-81)Fixed Issues - NetSuite Connector had missing values for RecordTypeEnum. (SE-15961) - Users could not insert a CUSTOMER\_SUBSIDIARY\_RELATIONSHIP through NetSuite Connector. (SE-15997) - An intermittent authentication failure occurred due to the nonce used when performing token-based authentication with concurrent requests. (SE-15887) - There was a metadata issue when using the `Get custom record` operation. (CONN-5623) To address SE-15961 and SE-15997, the following RecordTypeEnum values now work as designed: - ADV\_INTER\_COMPANY\_JOURNAL\_ENTRY - CUSTOMER\_SUBSIDIARY\_RELATIONSHIP - HCM\_JOB - INBOUND\_SHIPMENT - MERCHANDISE\_HIERARCHY\_NODE - PERIOD\_END\_JOURNAL ## [](#9-2-6)9.2.6 **April 02, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-82)Fixed Issues - Fixed connector security issues. (CONN-5613) ## [](#9-2-5)9.2.5 **March 05, 2020**
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-83)Fixed Issues Added the body of the message error to the RESTlet response in order to provide more information. (SE-15055) ## [](#9-2-4)9.2.4 **December 23, 2019** ### [](#compatibility-56)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-84)Fixed Issues Custom fields, list objects, and date attribute mappings were fixed in the input of record operations. The input metadata for list objects was also improved, to more accurately represent what the connector expects. (SE-14301, SE-14356) ## [](#9-2-3)9.2.3 **Deccember 11, 2019** ### [](#compatibility-57)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-85)Fixed Issues Fixed the RESTlet operations doesn’t return payload as JSON issue. (SE-14159) ## [](#9-2-2)9.2.2 **Deccember 10, 2019** ### [](#compatibility-58)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#fixed-issues-86)Fixed Issues Added the CUSTOM\_SEGMENT record type to fix the error in metadata generation. (SE-14215) ## [](#9-2-1)9.2.1 **November 25, 2019** ### [](#compatibility-59)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account can run on a version of NetSuite that differs from the version of the API you are using. ### [](#features-8)Features Added the NOT\_SUPPORTED option for the @ClusterSuppport annotation. This option indicates that the source does not support cluster node and only runs on the primary node. ### [](#fixed-issues-87)Fixed Issues Increased the default timeout values for `connectionTimeout` and `readTimeout`, which fixes a metadata generation error. (SE-13854) ## [](#9-2-0)9.2.0 **November 4, 2019** ### [](#compatibility-60)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account may be running on a version of NetSuite different than the version of the API you are using. ### [](#features-9)Features - New **TLS configuration** field - Protocol to use for communication. Valid values are HTTP and HTTPS. Default value is HTTP. When using HTTPS, the HTTP communication is secured using TLS/SSL. If HTTPS is configured as the protocol, configure at least the keystore in the `tls:context` child element of the listener configuration. - The TLS feature provides new attributes for `TLS`, `Trust Store`, `Key Store`, `Standard Revocation Check`, `Custom OCSP Responder`, and `CRL file`. - The **Max In Memory Size** field name changed to **In Memory Objects**. - **Page size** default value changed from `1` to `5`. Possible values now are 5 to 1000 for synchronous operations, and between 5 and 2000 for asynchronous operations. ### [](#fixed-issues-88)Fixed Issues - The connector now uses the Mule HTTP client and SOAP service to make calls, instead of third-party libraries. - Some operations presented incomplete metadata for some entities. This was fixed, and it now shows all attributes for the selected record types. ## [](#9-1-2)9.1.2 **September 10, 2019** ### [](#compatibility-61)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account may be running on a version of NetSuite different than the version of the API you are using. ### [](#features-10)Features None ### [](#fixed-issues-89)Fixed Issues The `ArrayIndexOutOfBoundException` exception was thrown randomly. (SE-12997) ## [](#9-1-1)9.1.1 **July 30, 2019** ### [](#compatibility-62)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account may be running on a version of NetSuite different than the version of the API you are using. ### [](#features-11)Features None ### [](#fixed-issues-90)Fixed Issues - Fixed security vulnerabilities. - Improved the documentation for the Async Search, Change Email, and Update Invitee Status List operations. (CONN-2903, CONN-2958) - Fixed input and output metadata for the Change Email, Change Password, Get Data Center URLs, Get Server Time, and Map SSO operations. (CONN-2958) - Fixed input and output metadata for the Async Add List, Async Delete List, Async Delete List Records, Async Get List, Async Get List Records, Async Initialize List, Async Search, Async Update List, and Async Upsert List operations. (CONN-2959) ## [](#9-1-0)9.1.0 **July 30, 2019** ### [](#compatibility-63)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2019.1
The NetSuite version is not the same as the SuiteTalk API version. Your account may be running on a version of NetSuite different than the version of the API you are using. ### [](#features-12)Features - Support for SuiteTalk API version 2019.1. For a detailed list of changes, log into NetSuite, open the Help Center and navigate to New Release > Release Notes > NetSuite 2019.1 Release Notes > SuiteTalk SOAP Web Services Integration. - Ability to log requests and responses. To enable this feature, add this line to the `Log4J` configuration file: ```xml ``` ## [](#9-0-1)9.0.1 **July 3, 2019** ### [](#compatibility-64)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2018.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may be running on a version of NetSuite different than the version of the API you are using. ### [](#fixed-issues-91)Fixed Issues Fixed potential XXE vulnerability. (CONN-2112) ## [](#9-0-0)9.0.0 **June 7, 2019** ### [](#compatibility-65)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2018.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may be running on a version of NetSuite different than the version of the API you are using. ### [](#features-13)Features - Support for SuiteTalk API version 2018.2. For a detailed list of changes, log into NetSuite, open Help Center and navigate to New Release > Release Notes > NetSuite 2018.2 Release Notes > SuiteTalk (Web Services) Integration. - The list operations (Add list, Delete list, Update list and Upsert list) now return information about the status of the result in each record. ### [](#fixed-issues-92)Fixed Issues None ### [](#migrate-from-an-older-version)Migrate from an Older Version In the older versions, the list operations returned a list of type `BaseRef`. Now they return a list of type `WriteResponse`. The `WriteResponse` has as fields: the `baseRef` (like the previous versions) and also the `status`. The `status` field is a structure that contains the information about whether the operation was successful (`isSuccess` Boolean) and details of the status (`statusDetail` structure). In case of error the structure of `statusDetail` indicates in the field `type` if it was an ERROR, in the field `code` indicates the type of error (for example: 'INVALID\_KEY\_OR\_REF') and finally in the field `message` contains details of the error (as the value and/or field involved). ## [](#8-3-12)8.3.12 **April 01, 2020** ### [](#compatibility-66)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#fixed-issues-93)Fixed Issues Fixed vulnerability issues. (CONN-5622) ## [](#8-3-11)8.3.11 **March 06, 2020** ### [](#compatibility-67)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#fixed-issues-94)Fixed Issues Added the body of the message error to the RESTlet response in order to provide more information. (SE-15055) ## [](#8-3-10)8.3.10 **December 19, 2019** ### [](#compatibility-68)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#fixed-issues-95)Fixed Issues Increased the default timeout values for `connectionTimeout` and `readTimeout`, which fixes a metadata generation error. (CONN-4367) ## [](#8-3-9)8.3.9 **December 5, 2019** ### [](#compatibility-69)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-14)Features None ### [](#fixed-issues-96)Fixed Issues Fixed the Search operation that did not return all the fields for custom objects. (SE-13622) ## [](#8-3-8)8.3.8 **November 14, 2019** ### [](#compatibility-70)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-15)Features None ### [](#fixed-issues-97)Fixed Issues Fixed "Unexpected error while consuming the web service operation (getDataCenterUrls)" when using a proxy server. (SE-13827) ## [](#8-3-7)8.3.7 **October 2, 2019** ### [](#compatibility-71)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-16)Features None ### [](#fixed-issues-98)Fixed Issues The metadata provided for non-custom entities had missing fields. This is no longer the case. (SE-13287) ## [](#8-3-6)8.3.6 **September 9, 2019** ### [](#compatibility-72)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-17)Features None ### [](#fixed-issues-99)Fixed Issues Fixed security vulnerabilities. ## [](#8-3-5)8.3.5 **September 6, 2019** ### [](#compatibility-73)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-18)Features None ### [](#fixed-issues-100)Fixed Issues The `ArrayIndexOutOfBoundException` exception was thrown randomly. (SE-12997) ## [](#8-3-4)8.3.4 **June 26, 2019** ### [](#compatibility-74)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-19)Features None ### [](#fixed-issues-101)Fixed Issues Fixed potential XXE Vulnerability. (CONN-2112) ## [](#8-3-3)8.3.3 **June 11, 2019** ### [](#compatibility-75)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-20)Features None ### [](#fixed-issues-102)Fixed Issues HTTP Proxy for RESTlet operations: a new fix was implemented. Previously, the proxy configuration was ignored by the dynamic endpoint resolution. It now works as expected. (SE-11716) ## [](#8-3-2)8.3.2 **May 22, 2019** ### [](#compatibility-76)Compatibility
Software Version

Mule

4.0.0 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a different NetSuite version than the version of the API you are using. ### [](#features-21)Features None ### [](#fixed-issues-103)Fixed Issues The HTTP Proxy for RESTlet operations now works in all scenarios. (SE-11716) ## [](#8-3-0)8.3.0 **March 29, 2019** ### [](#compatibility-77)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is _not_ the same as the SuiteTalk API version. Your account may run on a version of NetSuite different than the version of the API you are using. ### [](#features-22)Features Token authentication is now supported for RESTlet operations. (SE-11335) ### [](#fixed-issues-104)Fixed Issues Some metadata resolving routines were optimized. ## [](#8-2-1)8.2.1 **January 15, 2019** ### [](#compatibility-78)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a version of NetSuite different than the version of the API you are using. ### [](#features-23)Features Headers Preferences - Added a new parameter in the configuration to explicitly disable sending the `runServerSuiteScript` tag in Preferences header. ### [](#fixed-issues-105)Fixed Issues Name is null error - When performing an upsert record with a null Name, a NullPointerException would occur. Fixed by properly handling null names. ## [](#8-2-0)8.2.0 **August 4, 2018** ### [](#compatibility-79)Compatibility
Software Version

Mule

4.1.1 and later

SuiteTalk API

2017.2
The NetSuite version is _not_ the same as the SuiteTalk API version. Your account may run on a version of NetSuite different than the version of the API you are using. ### [](#features-24)Features Triggers - You can now start a flow with the NetSuite Connector every time an object of a specific type is created, updated, or deleted. ### [](#fixed-issues-106)Fixed Issues None ## [](#8-1-1)8.1.1 **July 13, 2018** ### [](#compatibility-80)Compatibility
Software Version

Mule

4.1.0 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a version of NetSuite different than the version of the API you are using.The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a version of NetSuite different than the version of the API you are using. ### [](#fixed-issues-107)Fixed Issues Search operation returned an empty response in Mac and a parsing error in Windows. ## [](#8-1-0)8.1.0 **March 13, 2018** ### [](#compatibility-81)Compatibility
Software Version

Mule

4.1.0 and later

SuiteTalk API

2017.2
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a version of NetSuite different than the version of the API you are using. ### [](#features-25)Features Support for SuiteTalk API version 2017.2. For a detailed list of changes, log into NetSuite, open Help Center and navigate to New Release > Release Notes > NetSuite 2017.2 Release Notes > SuiteTalk (Web Services) Integration. ## [](#8-0-0)8.0.0 **November 18, 2017** ### [](#compatibility-82)Compatibility
Software Version

Mule

4.1.0 and later

SuiteTalk API

2017.1
The NetSuite version is not the same as the SuiteTalk API version. Your account may run on a version of NetSuite different than the version of the API you are using. ### [](#features-26)Features - Support for SuiteTalk API version 2017.1. GA For a detailed list of changes, log into NetSuite, open Help Center and navigate to New Release > Release Notes > NetSuite 2017.1 Release Notes > SuiteTalk (Web Services) Integration. - Added support for Mule 4. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # NetSuite OpenAir Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for NetSuite OpenAir is a closed-source Enterprise connector that provides a connection between NetSuite OpenAir and third-party software. Guide: [NetSuite OpenAir Connector User Guide](https://docs.mulesoft.com/jp/netsuite-openair-connector/latest/) ## [](#2-0-14)2.0.14 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jsoup library is upgraded to version 1.23.2.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The guava library is upgraded to version 32.1.3-jre.

W-24137088
## [](#2-0-13)2.0.13 **August 6, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The guava library is upgraded to version 32.0.0-jre.

  • The xalan library is upgraded to version 2.7.3.

W-3300013
## [](#2-0-12)2.0.12 **August 19, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now uses http://www.openair.com/OAirService instead of https://sandbox.openair.com/OAirService for the namespace URI in all SOAP requests.

W-16091717
## [](#2-0-11)2.0.11 **March 18, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-0-10)2.0.10 **October 6, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The org.jsoup library is upgraded to version 1.15.3 to address reported security vulnerabilities.

W-11662367
## [](#2-0-9)2.0.9 **May 27, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The connector now deletes the WSDL files created when reconnection is triggered or when the Mule app stops.

W-11172980
## [](#2-0-8)2.0.8 **April 1, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Removed the atlantic-commons dependency.

W-10890159
## [](#2-0-7)2.0.7 **August 17, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The connector sent unnecessary requests. Now, it uses a cached connection that uses the same connection for subsequent requests.

SE-21635
### Known Issues - Do not use metadata as a guide in Flow Designer because some fields are not visible. ## [](#2-0-6)2.0.6 **August 21, 2020** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-8)Fixed Issues - Fixed the read response operation metadata. (CONN-6542) ### [](#known-issues-2)Known Issues - Do not use metadata as a guide in Flow Designer because some fields are not visible. ## [](#2-0-5)2.0.5 **July 13, 2020** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-9)Fixed Issues - Fixed the read response operation. (SE-15967) ### [](#known-issues-3)Known Issues - Do not use metadata as a guide in Flow Designer because some fields are not visible. ## [](#2-0-4)2.0.4 **May 21, 2020** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-10)Fixed Issues - Fixed reported security vulnerabilities. (CONN-6171) ### [](#known-issues-4)Known Issues - Do not use metadata as a guide in Flow Designer because some fields are not visible. ## [](#2-0-3)2.0.3 **July 3, 2019** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-11)Fixed Issues - Fixed potential XXE vulnerability. (CONN-2130) ### [](#known-issues-5)Known Issues - Do not use metadata as a guide in Flow Designer as not all fields are visible. ## [](#2-0-2)2.0.2 **May 17, 2019** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-12)Fixed Issues - Now working with Java 9 through Java 12, when using Mule 4.2.0. ### [](#known-issues-6)Known Issues - Do not use metadata as a guide in Flow Designer as not all fields are visible. ## [](#2-0-1)2.0.1 **March 7, 2019** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later
### [](#fixed-issues-13)Fixed Issues - Chunked transfer encoding was disabled, as it is not supported by OpenAir. ### [](#known-issues-7)Known Issues - Metadata in Flow Designer - Although metadata works under Anypoint Studio, Design Center displays incomplete structures. The connector can still be used, but metadata cannot be used as a guide. ## [](#2-0-0)2.0.0 **May 8, 2018** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.1 and later
### [](#features)Features - Added support for **Mule 4** and removed support for **Mule 3**. ### [](#known-issues-8)Known Issues - **Metadata in Flow Designer** - Although metadata works under Anypoint Studio, Flow Designer shows incomplete structures. The connector can still be used, but metadata cannot be used as a guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # NetSuite REST Connector Release Notes Anypoint Connector for NetSuite REST (NetSuite REST Connector) enables Mule applications to access the NetSuite REST API. Guide: [NetSuite REST Connector User Guide](https://docs.mulesoft.com/netsuite-rest-connector/latest/) ## [](#1-0-1)1.0.1 **September 22, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.6.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind library is upgraded to version 2.22.3.

  • The nimbus-jose-jwt library is upgraded to version 10.10.

W-24262517
## [](#1-0-0)1.0.0 **August 30, 2026** ### What’s New - This is a new connector. - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. For more information, see the [NetSuite REST Connector User Guide](https://docs.mulesoft.com/netsuite-rest-connector/latest/). ### Compatibility
Software Version

Mule

4.6.0 and later

OpenJDK

8, 11, and 17
## [](#see-also)See Also - [NetSuite REST Connector User Guide](https://docs.mulesoft.com/netsuite-rest-connector/latest/) - [NetSuite REST Connector Reference](https://docs.mulesoft.com/netsuite-rest-connector/latest/netsuite-rest-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # NetSuite Restlet Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for NetSuite Restlet (NetSuite Restlet Connector) synchronizes data and automates business processes between NetSuite and third-party applications, either on-premises or in the cloud. Guide: [NetSuite Restlet Connector User Guide](https://docs.mulesoft.com/jp/netsuite-restlet-connector/latest/) ## [](#1-0-11)1.0.11 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-10)1.0.10 **August 6, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.google.code.gson:gson library is upgraded to version 2.14.0.

  • The commons-codec:commons-codec library is upgraded to version 1.22.0.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.1.

W-3300013
## [](#1-0-9)1.0.9 **March 20, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-8)1.0.8 **January 17, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector no longer fails with an INVALID_LOGIN_ATTEMPT error if the data contains a space.

W-14799376
## [](#1-0-7)1.0.7 **December 7, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The query parameters are now encoded before initiating the signature creation process.

W-14556285
## [](#1-0-6)1.0.6 **October 6, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The jackson-databind library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853427
## [](#1-0-5)1.0.5 **March 30, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Removed the atlantic-commons dependency.

W-10890004

Updated the jackson-databind dependency.

W-10890004
## [](#1-0-4)1.0.4 **January 5, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed the encoding of the URL used to generate the signature.

SE-23489
## [](#1-0-3)1.0.3 **December 1, 2021** ### What’s New - The default value of the **Signature Algorithm** configuration parameter is now `HMAC-SHA256` since `HMAC-SHA1` is no longer supported by NetSuite. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9256
## [](#1-0-2)1.0.2 **July 22, 2021** ### [](#compatibility-10)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-8)Fixed Issues - The connector now configures the **Read Timeout** field properly for all operations. (SE-21888) - Updated the tooltip text for the **Read Timeout** field. ## [](#1-0-1)1.0.1 **May 11, 2021** ### [](#compatibility-11)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-9)Fixed Issues - The connector threw a NoSuchMethodError for the `jackson-core` library while making a Restlet POST request. (SE-20718) - Fixed internal Signature Algorithm configuration. ## [](#1-0-0)1.0.0 **March 8, 2021** New connector. ### [](#compatibility-12)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features For a list of supported configurations and operations, see the NetSuite Restlet Connector Reference Guide. ### [](#fixed-in-this-release)Fixed in This Release Not applicable. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Notion Connector Release Notes Anypoint Connector for Notion (Notion Connector) enables Mule applications to access the Notion API. Guide: [Notion Connector User Guide](https://docs.mulesoft.com/notion-connector/latest/) ## [](#1-0-22)1.0.22 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-1)0.1.1 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **January 6, 2026** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/notion-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [Notion Connector User Guide](https://docs.mulesoft.com/notion-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [Notion Connector User Guide](https://docs.mulesoft.com/notion-connector/latest/) - [Notion Connector Reference](https://docs.mulesoft.com/notion-connector/latest/notion-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider ## [](#1-6-1)1.6.1 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-6-0)1.6.0 **February 07, 2024** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-5-1)1.5.1 **March 15, 2022** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed Issues - Error handling responses revised for JSON compliance. ## [](#1-5-0)1.5.0 **June 24, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Introduced the capability to configure timeouts when validating OAuth2 tokens for incoming requests. ## [](#1-4-0)1.4.0 **December 22, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Added support for policies to validate one or all of the scopes defined in API Manager. - Added OAS3 code snippet in the policy YAML. ## [](#1-3-3)1.3.3 **September 28, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-2)Fixed Issues - Because the `Content-Type` header of the JSON response from the validate endpoint had additional information, such as charset, the response returned was interpreted as String instead of JSON. The additional modifier is now disregarded. - Responses from the validation endpoint in which the value of the `expires_in` field was equal to 0 were not being parsed as an expired token. ## [](#1-3-2)1.3.2 **Apr 30, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in error handling. ### [](#fixed-issues-3)Fixed Issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-3-1)1.3.1 **December 18, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.0** ### [](#fixed-issues-4)Fixed Issues - Authorization entity attributes that contain non-primitive values were not correctly parsed. These values are now ignored. - An error occured when an object within a JSON object was treated as String type instead of JSON type. This issue is now resolved. - The `Fault` element in the WSDL APIs now includes the `Detail` element, with additional error details. ## [](#1-3-0)1.3.0 **Sep 4, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Introduced a configuration flag to enable transport layer security (TLS) validation for the Authorization Servers certificates. - Added token rejection when the active field of the introspection endpoint response is 'false'. - Several performance improvements are introduced. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ### [](#fixed-issues-5)Fixed Issues - The Expiration Time field was mandatory. This issue is now resolved. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Introduced support to encrypt sensitive information related to policies. The Runtime version must be correctly configured to support encryption, which is availble with Mule Runtime v4.2.0 or later. - The default configuration has been modified to avoid propagating or returning policy headers, unless explicitly configured by checking the "Expose headers" option. - Several performance improvements are introduced. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-4)1.1.4 **Feb 22, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **4.1.0** ### [](#fixed-issues-6)Fixed Issues - Fixed scheduling related performance issues. ## [](#1-1-3)1.1.3 **Jan 11, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Improved the RAML and OAS snippets. ## [](#1-1-2)1.1.2 **Oct 9, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **4.0.0** ### [](#fixed-issues-7)Fixed Issues - A scope validation error was causing the OAuth 2.0 External Provider policy to return a "403 - The required scopes are not authorized error" response. - When a WSDL proxy receives an empty payload or an invalid XML, an `ExpressionRuntimeException` error was generated. ## [](#1-1-1)1.1.1 **Jun 27, 2018** ### [](#fixed-issues-8)Fixed Issues - When a Security Manager was defined in the same application with a tracked endpoint, an error occurred preventing the federated and client ID based policies to apply. ### [](#minimum-mule-version-12)Minimum Mule Version **4.0.0** ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#fixed-issues-9)Fixed Issues - An error occurred, causing federated policies to lose query and URI parameters of the requester. ### [](#minimum-mule-version-13)Minimum Mule Version **4.0.0** ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-14)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [Mule OAuth 2.0 Access Token enforcement for Mule 4](#api-manager::external-oauth-2.0-token-validation-policy.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # OAuth 2.0 OBO Credential Injection The OAuth 2.0 OBO Credential Injection policy exchanges incoming bearer tokens using OAuth 2.0 Token Exchange (RFC 8693), Microsoft Entra ID On-Behalf-Of, or OAuth 2.0 Token Exchange with CIBA. For configuration details, see [OAuth 2.0 OBO Credential Injection Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-oauth-obo). ## [](#april-30-2026)April 30, 2026 ### What’s New - OAuth 2.0 OBO Credential Injection policy support added to Omni Gateway. # OAuth 2.0 Protected Resource Metadata The OAuth 2.0 Protected Resource Metadata policy serves OAuth 2.0 Protected Resource Metadata at the well-known endpoint. For configuration details, see [OAuth 2.0 Protected Resource Metadata Policy](https://docs.mulesoft.com/gateway/latest/policies-included-oauth-protected-resource-metadata). ## [](#june-02-2026)June 02, 2026 ### What’s New - OAuth 2.0 Protected Resource Metadata policy implementation version 1.0.1 is now supported by Omni Gateway. - OAuth 2.0 Protected Resource Metadata policy definition version 1.0.1 is now supported by Omni Gateway. # OAuth 2.0 Token Introspection Policy The OAuth 2.0 Token Introspection Policy policy allows access only to authorized client applications. For configuration details, see [OAuth 2.0 Token Introspection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-oauth-token-introspection). ## [](#march-13-2026)March 13, 2026 ### What’s New - OAuth 2.0 Token Introspection Policy policy implementation version 1.2.0 is now supported by Omni Gateway. - OAuth 2.0 Token Introspection Policy policy definition version 1.1.0 is now supported by Omni Gateway. # OAuth Module Release Notes for Mule 4 Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) OAuth Module is an extension to hook OAuth2 to HTTP extension connectors. Guide: [OAuth Module User Guide](https://docs.mulesoft.com/jp/oauth-module/latest/) ## [](#1-1-30)1.1.30 **October 19, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Client credentials access token and refresh token requests now time out after 60 seconds, instead of waiting indefinitely when the authorization server doesn’t respond.

W-24465093
## [](#1-1-29)1.1.29 **September 24, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-28)1.1.28 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-27)1.1.27 **May 18, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

OAuth Module now enforces a configurable timeout on token-request futures so that stuck or slow authorization-server responses no longer block threads indefinitely. The new mule.oauth.token.request.timeout.millis system property sets the maximum time (in milliseconds) that OAuth Module waits for a token-request future to complete before cancelling it and raising an error.

  • Default: 60000 (60 seconds).

  • Recommended range: 30000–60000 ms. Set higher only if your authorization server is known to be slow.

  • Invalid values (non-numeric, zero, or negative) are ignored with a WARN log, and the default is used.

Set the property on the worker JVM, for example:

-Dmule.oauth.token.request.timeout.millis=45000

On CloudHub, add the property as a Properties entry on the deployment. No application redeploy of the runtime is needed.

W-22132137
## [](#1-1-26)1.1.26 **February 12, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address CVE-2024-38820:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The mule-http-connector library is upgraded to version 1.10.6.

W-19805507
## [](#1-1-25)1.1.25 **September 8, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Dynamic HTTP requester configurations now properly handle the OAuth dancer lifecycle to prevent race conditions during configuration expiration.

W-19449357
## [](#1-1-24)1.1.24 **May 27, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The proxy now works as intended.

W-18568237
## [](#1-1-23)1.1.23 **May 8, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

NullPointerException errors no longer occur with OAuth authentication when restarting the application intermittently in production.

W-18230789
## [](#1-1-22)1.1.22 **February 26, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-io dependency is updated to fix the CVE-2024-47554 vulnerability.

W-17412056

A ClassCastException is no longer thrown when using the OAuth Retrieve Access Token operation.

W-15832018
## [](#1-1-21)1.1.21 **December 15, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-20)1.1.20 **May 23, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1
### Fixed Issues
Issue Resolution ID

The internal libraries are upgraded.

W-11680326

The OAuth localCallbackConfig parameter is refactored to avoid different inconsistent behavior according to the configuration order.

MULE-14827
## [](#1-1-19)1.1.19 **September 13, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1
### Fixed Issues
Issue ID

OAuth module now responds when Token URL fails more than three times.

W-11680326
## [](#1-1-18)1.1.18 **March 3, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1
### Fixed Issues
Issue ID

Oauth token refresh issue no longer occurs in Mule 4.4.0.

W-10781856
## [](#1-1-17)1.1.17 **July 12, 2021** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-11)Fixed Issues The default object store of `oauth:token-manager-config` is no longer cleared on shut down. (OAMOD-6) ## [](#1-1-16)1.1.16 **March 15, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-12)Fixed Issues Fixed the `MULE:OVERLOAD` error that occurred concurrently when refreshing the token in dynamic HTTP configs. (OAMOD-4) ## [](#1-1-15)1.1.15 **March 2, 2021** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-13)Fixed Issues In MUnit, the OAuth module creates an object store twice and fails. (OAMOD-2) ## [](#1-1-141-1-13)1.1.14/1.1.13 **September 10, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-14)Fixed Issues - Fixed an issue in which using payload in an expression for the refreshTokenWhen property resulted in an error. (MULE-18307) ## [](#1-1-12)1.1.12 **December 19, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-15)Fixed Issues Fixed the leak of dynamic configs that resulted from the token manager not initializing in `AbstractGrantType`. (MULE-17827) ## [](#1-1-11)1.1.11 **October 18, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-16)Fixed Issues - Misnamed parameters in the OAuth module generated invalid extension model. (MULE-17662) - Upgraded Commons Codec to 1.13. (MULE-17337) ## [](#1-1-10)1.1.10 **August 13, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-17)Fixed Issues - HTTP updated to version 1.5.6. (MULE-17254) ## [](#1-1-9)1.1.9 **July 18, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-18)Fixed Issues - Removed dependencies on MuleContext on OAuth module. (MULE-11412) - OAuth uses the wrong access token when multiple concurrent refresh requests are sent. (MULE-17010) ## [](#1-1-8)1.1.8 **April 10, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-19)Fixed Issues - OAuth authenticators do not implement equals() and hashCode(). (MULE-16704) ## [](#1-1-7)1.1.7 **November 2, 2018** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-20)Fixed Issues - Setting `refreshTokenWhen=true` in oauth:authorization-code-grant-type fails with an exception. (MULE-15809) ## [](#1-1-6)1.1.6 **November 1, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-21)Fixed Issues - Support non-blocking in OAuth HTTP calls. (MULE-11272) - Remove \*-object-store elements (MULE-11724) ## [](#1-1-51-1-4)1.1.5/1.1.4 **August 14, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-22)Fixed Issues - OAuth: Provide option `encodeClientCredentialsInBody` in authCode. (MULE-15539) ## [](#1-1-3)1.1.3 **May 7, 2018** ### [](#minimum-mule-version-13)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-23)Fixed Issues - ConfigurationException: Element 'tokenManagerConfig-MyConfigName' is not defined in the Mule Registry. (MULE-14822) ## [](#1-1-2)1.1.2 **May 7, 2018** ### [](#minimum-mule-version-14)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-24)Fixed Issues - ConfigurationException: Element 'tokenManagerConfig-MyConfigName' is not defined in the Mule Registry. (MULE-14822) ## [](#1-1-1)1.1.1 **January 23, 2018** ### [](#minimum-mule-version-15)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-25)Fixed Issues - Provide a singleton MultiMap instance. (MULE-14544) ## [](#1-1-0)1.1.0 **January 23, 2018** ### [](#minimum-mule-version-16)Minimum Mule Version **Mule 4.1.0** ### [](#upgrade-requirements)Upgrade Requirements This version does not work with Mule 4.0.0, you need to move to 4.1.0 or a higher version to use it. ### [](#fixed-issues-26)Fixed Issues - OAuth Module exports internal classes. (MULE-14446) - Users should not be able to use an expression when configuring a proxy. (MULE-14379) - HTTP Connector does not route OAuth tokens request through proxy. (MULE-14160) ## [](#1-0-0)1.0.0 **November 27, 2017** ### [](#minimum-mule-version-17)Minimum Mule Version **Mule 4.0.0** ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # OAuth Service Release Notes - Mule 4 ## [](#1-1-8)1.1.8 **September 10, 2020** ### [](#new-features-and-enhancements)New Features and Enhancements - None ### [](#fixed-issues)Fixed Issues - Fixed an issue in which the `AuthorizationCodeState` type was not updated on certain circumstances. (MULE-16540) ## [](#1-3-3)1.3.3 **March 13, 2020** ### [](#new-features-and-enhancements-2)New Features and Enhancements - None ### [](#fixed-issues-2)Fixed Issues - Fixed a race condition that was generating a NullPointerException during OAuth token refresh. (MULE-18169) ## [](#1-3-1)1.3.1 **July 17, 2019** ### [](#new-features-and-enhancements-3)New Features and Enhancements - None ### [](#fixed-issues-3)Fixed Issues - OAuth uses wrong access token when multiple concurrent refresh requests are sent. (MULE-17010) - Reuse HTTP clients for an OAuth token request. (MULE-17006) ## [](#1-3-0)1.3.0 **July 5, 2019** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Support Client Credentials grant type in the SDK. (MULE-16908) ### [](#fixed-issues-4)Fixed Issues - AuthorizationCodeState not updated on certain circumstances. (MULE-16540) ## [](#1-2-1)1.2.1 **June 19, 2019** ### [](#new-features-and-enhancements-5)New Features and Enhancements - None. ### [](#fixed-issues-5)Fixed Issues - Reuse HTTO clients for an OAuth token request. (MULE-17006) ## [](#1-1-7)1.1.7 **June 19, 2019** ### [](#new-features-and-enhancements-6)New Features and Enhancements - None. ### [](#fixed-issues-6)Fixed Issues - Reuse HTTP clients for an OAuth token request. (MULE-17006) ## [](#1-2-0)1.2.0 **April 25, 2019** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Support non-blocking in OAuth HTTP calls (MULE-11272) - Send OAuth access token by `queryParams` - service support (MULE-15986) ### [](#fixed-issues-7)Fixed Issues
Issue Description

MULE-14544

Provide a singleton MultiMap instance

MULE-14012

Create HttpRequestOptions concept in HTTP service

MULE-14961

Make RequestOptions as large as possible

MULE-15251

Remove unnecessary String.toLowerCase calls (OAuth Service)

MULE-15201

Services take too long to discover and load

MULE-15539

OAuth: Provide option encodeClientCredentialsInBody in authCode

MULE-15738

HTTP request with OAuth client-credentials fails after token is invalidated

MULE-15871

Some HTTP log entries go to the runtime log instead of the app’s logg

MULE-16540

AuthorizationCodeState is not updated in certain circumstances
## [](#1-1-6)1.1.6 **December 11, 2018** ### [](#new-features-and-enhancements-8)New Features and Enhancements - None. ### [](#fixed-issues-8)Fixed Issues
Issue Description

MULE-15807

OAuth ClientCredentials: Race condition when two requests try to refresh the token at the same time

MULE-15871

Some HTTP log entries go to the runtime log instead of the app’s log
## [](#1-1-5)1.1.5 **October 9, 2018** ### [](#new-features-and-enhancements-9)New Features and Enhancements - Support non-blocking in OAuth HTTP calls (MULE-11272) ### [](#fixed-issues-9)Fixed Issues
Issue Description

MULE-15738

HTTP request with OAuth client-credentials fails after token is invalidated
## [](#1-1-4)1.1.4 **August 14, 2018** ### [](#new-features-and-enhancements-10)New Features and Enhancements - None. ### [](#fixed-issues-10)Fixed Issues
Issue Description

MULE-15539

OAuth: Provide option encodeClientCredentialsInBody in authCode
## [](#1-1-3)1.1.3 **August 13, 2018** ### [](#new-features-and-enhancements-11)New Features and Enhancements - None. ### [](#fixed-issues-11)Fixed Issues
Issue Description

MULE-15493

OAuth2 Request config always fetches token at startup
## [](#1-1-2)1.1.2 **July 24, 2018** ### [](#new-features-and-enhancements-12)New Features and Enhancements - None. ### [](#fixed-issues-12)Fixed Issues
Issue Description

MULE-15251

Remove unnecessary String.toLowerCase calls (OAuth Service)
## [](#1-1-1)1.1.1 **March 16, 2018** ### [](#new-features-and-enhancements-13)New Features and Enhancements - None. ### [](#fixed-issues-13)Fixed Issues
Issue Description

MULE-14544

Provide a singleton MultiMap instance
## [](#1-1-0)1.1.0 **January 30, 2018** Initial Release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # OAuth2 Provider Module Release Notes The OAuth2 Provider module enables a Mule runtime engine (Mule) app to be configured as an Authentication Manager in an OAuth2 dance. Guide: [OAuth2 Provider User Guide](https://docs.mulesoft.com/jp/oauth2-provider-module/latest/) Reference: [OAuth2 Provider Reference](https://docs.mulesoft.com/jp/oauth2-provider-module/latest/oauth2-provider-module-reference) ## [](#1-2-4)1.2.4 **October 22, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

A custom Spring security provider configured in Resource Owner Security Provider now receives the HTTP request headers when it authenticates a resource owner with the Supported Grant Types value RESOURCE_OWNER_PASSWORD_CREDENTIALS. Previously, that provider did not receive the request headers. A provider that already sets Spring authentication details keeps those details.

W-15615692

The module no longer uses the Atlassian-forked spring-security library. The spring-security library is now version 5.8.16-spring-security-5.8.19. The spring-framework library is now version 5.3.39-spring-framework-5.3.45 and is shaded into the module’s Mule plugin.

W-23993430
## [](#1-2-3)1.2.3 **July 21, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The log4j library is upgraded to version 2.26.1 to address CVE-2026-34478.

  • The spring-security library is upgraded to version 5.8.17-atlassian-1.

  • The spring-framework library is upgraded to version 5.3.39-spring-framework-5.3.49.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-text library is upgraded to version 1.15.0.

  • The gson library is upgraded to version 2.14.0.

  • The apache-velocity library is upgraded to version 2.4.1.

W-23274319
## [](#1-2-2)1.2.2 **January 26, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-collections library is migrated to commons-collections4 version 4.5.0 to address sonatype-2024-3350.

  • The commons-lang3 library is upgraded to version 3.20.0 to address CVE-2025-48924, and the commons-lang library version 2.6 is excluded to address CVE-2025-48924.

  • The commons-io library is added at version 2.21.0 to override the outdated version in mule-service-http to address CVE-2024-47554.

  • The gson library is upgraded to version 2.13.2 to address CVE-2025-53864.

  • The log4j library is upgraded to version 2.25.3 to address CVE-2025-68161.

  • The spring-core library is upgraded to version 6.2.11 to address CVE-2025-41242 and CVE-2025-41249.

  • The muleHttpConnectorVersion library is upgraded to version 1.10.6.

W-20358376
## [](#1-2-1)1.2.1 **September 11, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The Spring framework is upgraded to version 5.3.39-spring-framework-5.3.45 to address reported security vulnerabilities.

W-18704894
## [](#1-2-0)1.2.0 **March 26, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-16889148

The log4j dependency is upgraded to version 2.17.1 to address reported security vulnerabilities.

W-16889148
## [](#1-1-0)1.1.0 **May 14, 2024** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-13)1.0.13 **March 8, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-12)1.0.12 **June 14, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Improved the performance of the Validate operation.

W-13101424
## [](#1-0-11)1.0.11 **June 12, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Upgraded internal dependencies.

W-13568991

Refactored code to improve security.

W-13145661
## [](#1-0-10)1.0.10 **October 18, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Upgraded internal dependencies.

W-11639029
## [](#1-0-9)1.0.9 **August 23, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Upgraded internal dependencies.

W-11577652
## [](#1-0-8)1.0.8 **December 16, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Fixed inconsistencies in OAuth2 token expiry time.

OPM-31
## [](#1-0-7)1.0.7 **September 24, 2021** ### [](#fixed-issues-11)Fixed Issues - Added debug logs in the connector to troubleshoot properly. (OPM-29) ## [](#1-0-6)1.0.6 **February 18, 2021** ### [](#fixed-issues-12)Fixed Issues - Fixed an issue that prevented LDAP authentication. (OPM-20) - Fixed the `Already exists a listener matching that path and methods` error that occurred when restarting an application using the OAuth2 Provider Module. (OPM-21) - Fixed the `Provider already registered` error that occurred when starting a stopped application when using the OAuth2 Provider Module. (OPM-22) ## [](#1-0-5)1.0.5 **September 15, 2019** ### [](#fixed-issues-13)Fixed Issues - `ClassCastException` was incorrectly thrown in an error scenario. This has been replaced by `OAuth2ProviderSecurityException`. (MULE-17445) ## [](#1-0-4)1.0.4 **August 13, 2019** ### [](#fixed-issues-14)Fixed Issues - HTTP updated to version 1.5.6. (MULE-17254) - Upgraded commons-io to version 2.6. (MULE-16582) ### [](#compatibility-13)Compatibility The OAuth2 Provider Module is compatible with:

Application or Service

Version

Mule

4.1.1 and later
## [](#1-0-3)1.0.3 **January 23, 2019** ### [](#fixed-issues-15)Fixed Issues - HTTP request parameters are validated twice. (EE-6529) - Missing default login page files. (EE-6528) ### [](#compatibility-14)Compatibility The OAuth2 Provider Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#1-0-2)1.0.2 **January 21, 2019** ### [](#fixed-issues-16)Fixed Issues The OAuth2 Provider Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#1-0-1)1.0.1 **January 8, 2019** ### [](#fixed-issues-17)Fixed Issues - Token response content-type header is not application/json (EE-6224) - ClientCredential grants inconsistent error codes. This broke compatibility, so use system property: `mule.oauth.provider.oldErrors=true` if wanting to get the previous error codes. (EE-6521) - `clientSecurityProvider` is no longer mandatory. (EE-6488) - Static login page is now being exported. (EE-6519) ### [](#compatibility-15)Compatibility The OAuth2 Provider Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#1-0-0)1.0.0 **June 15, 2018** ### [](#compatibility-16)Compatibility The OAuth2 Provider Module is compatible with:

Application/Service

Version

Mule

4.1.1 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Object Store Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Object Store Connector User Guide](https://docs.mulesoft.com/object-store-connector/latest/) ## [](#1-3-4)1.3.4 **October 22, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer includes unused JAXB dependencies.

W-23351690
## [](#1-3-3)1.3.3 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-3-2)1.3.2 **August 26, 2026** ### What’s New - Object Store Connector now has new **Lock Timeout** and **Lock Timeout Unit** fields, which control the maximum lock time. - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now validates its object store configuration during application initialization instead of at start, so a duplicate object store name is detected earlier and reported with a clearer error.

W-18932759
## [](#1-3-1)1.3.1 **July 23, 2026** This version is deprecated. All of the features and fixed issues for this version are in version 1.3.2. ## [](#1-3-0)1.3.0 **March 27, 2026** This version is deprecated. All of the features and fixed issues for this version are in version 1.3.2. ## [](#1-2-5)1.2.5 **December 19, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded:

  • The net.bytebuddy:byte-buddy library is upgraded to version 1.17.7.

  • The org.mule.sdk:mule-sdk-api library is upgraded to version 0.13.0.

  • The org.glassfish.jaxb:jaxb-runtime library is upgraded to version 2.3.9.

W-20461495
## [](#1-2-4-deprecated)1.2.4 - (Deprecated) **September 16, 2025** This version is deprecated. All of the features and fixed issues for this version are in version 1.2.5 ## [](#1-2-3)1.2.3 **June 13, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Object Store Connector now delegates the test connection from underlying connectors.

W-17985624
## [](#1-2-2)1.2.2 **December 13, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-1)1.2.1 **July 1, 2021** ### [](#compatibility-7)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-5)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-2-0)1.2.0 **April 21, 2021** ### [](#fixed-issues-6)Fixed Issues - Fixed a bug that caused the application to throw a generic `MULE:UNKNOWN` Mule error instead of the connector specific Mule errors `OS:KEY_NOT_FOUND` or `OS:KEY_ALREADY_EXISTS`. (COBJCON-6) ## [](#1-1-7)1.1.7 **March 22, 2021** ### [](#fixed-issues-7)Fixed Issues - Fixed a bug that caused the application to fail when the ObjectStore v2 rate limit was reached inside a parallel for-each. (COBJCON-5) ## [](#1-1-6)1.1.6 **November 3, 2020** ### [](#fixed-issues-8)Fixed Issues - Fixed a bug that caused two applications within the same domain couldn’t define top level object stores with the same name if the Object Store Connector dependency was declared in the domain. (MULE-18947) ## [](#1-1-5)1.1.5 **April 13, 2020** ### [](#fixed-issues-9)Fixed Issues - Rely on underlying lock on store operation. (MULE-18232) ## [](#1-1-4)1.1.4 **March 30, 2020** ### [](#fixed-issues-10)Fixed Issues - Fixed a race condition where ObjectStore store operation could throw ObjectAlreadyExistsException even when failIfPresent was set to false. (MULE-18232) - Avoid duplicated operations in order to improve performance. (MULE-16631) ## [](#1-1-3)1.1.3 **January 31, 2019** ### [](#fixed-issues-11)Fixed Issues - Object Store operations should execute in the IO pool. (MULE-16409) ## [](#1-1-2)1.1.2 **October 22, 2018** ### [](#fixed-issues-12)Fixed Issues - Message in exceptions references "null" as the ObjectStore name. (MULE-15285) - Top level ObjectStore throws NPE if used before application Start. (MULE-15210) - MUnit test fails with duplicated ObjectStore when running multiple suites. (MULE-15779) ## [](#1-1-1)1.1.1 **May 17, 2018** ### [](#fixed-issues-13)Fixed Issues - Add name identifier to ObjectStoreManager injection to support CloudHub deployments. (MULE-14987) ## [](#1-1-0)1.1.0 **January 27, 2018** ### [](#fixed-issues-14)Fixed Issues - ObjectStore connector does not work properly with MUnit tests when referencing a global. (MULE-14335) ## [](#0-8-1)0.8.1 **July 29, 2017** ### [](#compatibility-8)Compatibility | Software | Version | | --- | --- | ### [](#features)Features - Enables applications to store data for access by other applications - Stores key/value pair content ## [](#see-also)See Also - [Object Store v2 Release Notes](https://docs.mulesoft.com/jp/release-notes/object-store/anypoint-osv2-release-notes) - [CloudHub Runtime and Operating System Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Object Store v2 Release Notes

可能な場合は、Equality の会社の値に一致するように、含めない用語を変更しました。顧客の実装に対する影響を回避するために、一部の用語は変更されていません。
Support Category: Select Object Store v2 enables applications and users to share data and share states across batch processes, Mule components, and multiple distributed applications. Object Store v2 works with all Mule runtime engine 4.x versions. ## [](#december-9-2024)December 9, 2024 ### What’s New - This product is now available on Hyperforce. Anypoint Platform instances on the Hyperforce infrastructure are: - [Canada Cloud](https://ca1.platform.mulesoft.com) - [Japan Cloud](https://jp1.platform.mulesoft.com) For more information, see [Object Store v2 on Hyperforce](https://docs.mulesoft.com/jp/object-store/#osv2-on-hyperforce) and [Salesforce Hyperforce Overview](https://docs.mulesoft.com/hyperforce/). ## [](#october-17-2024)October 17, 2024 ### What’s New - The **Object Store Usage** page in access management now shows usage stats for the current and previous month. This change aligns with an initiative to adopt the new [Usage Reports](https://docs.mulesoft.com/jp/general/usage-reports), which enhances the user experience, provides clearer usage insights, and enables more queries for data analysis. For information, see [Access Object Store Effective API Request Usage Charts](https://docs.mulesoft.com/jp/object-store/osv2-usage#access-usage-charts). Although the UI shows only two months of data, you can query up to two years of usage data by calling the [Object Store v2 Statistics API](https://dev-portal.mulesoft.com/apis/object-store-v2-stats.html) directly. For information, see [Object Store v2 REST API](https://docs.mulesoft.com/jp/object-store/osv2-apis). ## [](#march-31-2023)March 31, 2023 ### What’s New - Anypoint Platform and this product now use system fonts, which improves legibility, adds native support for localization and character subsets at the operating-system level, and increases performance because the browser no longer has to download custom fonts. ## [](#september-15-2022)September 15, 2022 ### What’s New - Object Store v2 now supports the Connected Apps feature. For information, see [Configure a Connected App](https://docs.mulesoft.com/jp/object-store/osv2-guide#configure-os-conn-app). ## [](#june-20-2022)June 20, 2022 ### What’s New - The Object Store v2 backend server is upgraded to address security vulnerabilities and update the framework that handles client connections. ## [](#june-3-2022)June 3, 2022 ### What’s New - The documentation now uses more inclusive language. ## [](#may-9-2022)May 9, 2022 ### What’s New - The Object Store v2 backend no longer supports the Transport Layer Security (TLS) deprecated versions 1.1 and 1.0. ## [](#march-7-2022)March 7, 2022 ### What’s New - Added two endpoints to the [Object Store v2 Statistics API](https://dev-portal.mulesoft.com/apis/object-store-v2-stats.html): - Retrieve usage statistics by region - Retrieve usage statistics by store For information, see [Object Store v2 REST APIs](https://docs.mulesoft.com/jp/object-store/osv2-apis). ## [](#february-1-2022)February 1, 2022 ### What’s New - Removed the default TTL (seconds) from the **Object Store** page in Runtime Manager. ## [](#september-17-2021)September 17, 2021 - Made internal changes to the Object Store v2 infrastructure for the regions listed in [September 2, 2021](#sept_2_2021). ## [](#sept_2_2021)September 2, 2021 Object Store v2 has been migrated to a new infrastructure in the following regions:
Migration Date Control Plane Location Region

September 2

EU

Europe

Frankfurt (eu-central-1)

September 4

US

North America

Oregon (us-west-2)

Central Canada (ca-central-1)

Europe

Frankfurt (eu-central-1)

APAC

Sydney (ap-southeast-2)
As part of this infrastructure change, the SSL certificate for Object Store v2 changed. Applications won’t experience downtime with this change unless a client application includes certificate pinning, which Object Store v2 doesn’t support. ## [](#2-5-27)2.5.27 **March 25, 2021** ### [](#fixed-issues)Fixed Issues - Added the optional `isMaster` query parameter to the Object Store Stats API. (SE-18525) By default, the Object Store Stats API `organizationId` endpoint retrieves statistics only for the specified organization ID. To get the usage data for the root organization and all sub-organizations, set `isMaster` to `true`. Use `isMaster=true` only when querying the root organization. If you use it to query a sub-organization, the endpoint returns no results. - Changed the queries on the **Object Store Usage** page to include usage data for sub-organizations. - Internal bug fixes. ## [](#2-5-26-mule-4-3-0-4-2-2-and-4-2-1)2.5.26 (Mule 4.3.0, 4.2.2, and 4.2.1) **September 21, 2020** ### [](#updated-feature)Updated Feature - If the `entryTtl` value is greater than 30 days, TTL is set to the maximum value (2592000 seconds/30 days) without returning an error. ## [](#see-also)See Also - [Object Store v2](https://docs.mulesoft.com/jp/object-store/) - [Object Store Connector Release Notes (for Mule 4)](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4) - [CloudHub Runtime and Operating System Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes) - [Known Issues](https://help.salesforce.com/s/issues) # Object Store v2 Release Notes Object Store provides temporary storage for application data. These release notes are provided for Object Store: - [Object Store v2 Release Notes](https://docs.mulesoft.com/jp/release-notes/object-store/anypoint-osv2-release-notes) - [Object Store Connector Release Notes (for Mule 4)](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4) ## [](#see-also)See Also - [Object Store v2 の概要](https://docs.mulesoft.com/jp/object-store/) - [CloudHub Runtime and Operating System Patch Update Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes) - [Known Issues](https://help.salesforce.com/s/issues) # Omni Gateway Policy Development Kit (PDK) Release Notes ## [](#1-10-0)1.10.0 **August 20, 2026** ### What’s New - The Cache library now supports the Least Recently Used (LRU) eviction strategy and a time-to-live (TTL) for cache entries. Previously, the cache supported only first-in, first-out (FIFO) eviction. See [Configure a Cache Eviction Strategy](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-caching#configure-a-cache-eviction-strategy) and [Configure a Cache TTL](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-caching#configure-a-cache-ttl). - For policies generated with PDK 1.10.0, you can now run a single integration test by passing the `TEST` parameter to the `make test` command. See [Run an Integration Test](https://docs.mulesoft.com/pdk/latest/policies-pdk-integration-tests#run-integration-test). - For policies generated with PDK 1.10.0, policy projects now register an Omni Gateway automatically when no `registration.yaml` file is provided for the debugging playground or integration tests. See [Debugging Custom Policies with the PDK Debugging Playground](https://docs.mulesoft.com/pdk/latest/policies-pdk-debug-local) and [Writing Integration Tests](https://docs.mulesoft.com/pdk/latest/policies-pdk-integration-tests). - For policies generated with PDK 1.10.0, the debugging playground `docker-compose` configuration is now parameterized with the same environment variables as `pdk-test`. - For new policies generated with PDK 1.10.0, PDK now skips republishing a policy definition that is unchanged from the published version and reuses the existing definition when using `make publish` or `make release`. See [Skip Republishing an Unchanged Definition](https://docs.mulesoft.com/pdk/latest/policies-pdk-publish-policies#skip-republishing-an-unchanged-definition). - The Token Introspection library now provides a standalone RFC 9728 protected resource metadata (PRM) builder. See [Using OAuth 2.0 Token Introspection Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-token-introspection). - PDK unit testing now supports policy chaining and setting the log level on test constructors. - The WebSocket library now supports HTTP calls and timer ticks within WebSocket flows, and you can now share references to structs from the `configure` context with WebSocket filters. See [Support WebSocket APIs](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-websocket).
The WebSocket library is currently in open beta.
- PDK script evaluation setup is now optimized. ### Fixed Issues
Issue Resolution ID

HTTP calls triggered after awaiting timer ticks are now correctly routed to the request context instead of the root context handler.

W-23652660

JSON string escape validation now matches the RFC 8259 specification.

W-23510751

The Contracts library now includes improved internal error handling and a retry mechanism for the contracts collector.

W-23460693

The WebSocket FilterBuilder now provides the build() method for response-only filters and supports on_done chaining for response-only filters.

W-23048381
## [](#1-9-2)1.9.2 **July 21, 2026** ### What’s New - Third-party testing and development dependencies are now updated to address security vulnerabilities and unmaintained-crate advisories. These dependencies affect only the PDK testing framework and aren’t included in the compiled WASM of policies. ## [](#1-9-1)1.9.1 **July 15, 2026** ### What’s New - PDK updated third-party dependencies to address reported security vulnerabilities. - The XML Validator and JWT libraries are now gated behind Cargo features so you can remove them from the compiled WASM of policies that don’t require the libraries. Both features are still enabled by default. To disable them, see [Configure PDK Features in Cargo.toml](https://docs.mulesoft.com/pdk/latest/policies-pdk-create-project#configure-pdk-features). - PDK now provides the `jwt-fips` feature to select the FIPS-compliant JWT backend, which delegates cryptography to the proxy-wasm host instead of bundling native RustCrypto. To enable `jwt-fips`, see [FIPS-Compliant JWT](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-jwt#fips-compliant-jwt). ## [](#1-9-0)1.9.0 **June 18, 2026** ### What’s New - PDK now supports FIPS 140-3 compliance to enable use of FIPS-compliant cryptographic modules. Add the `--fips` flag to PDK CLI `create` command to create a FIPS-compliant policy project. For more information, see [Create a New Policy Project](https://docs.mulesoft.com/pdk/latest/policies-pdk-create-project#create-a-new-policy-project). - PDK project folders now include an AGENTS.md file to provide guidance for AI coding agents such as Claude Code, GitHub Copilot, or other AI assistants. See [AGENTS.md](https://docs.mulesoft.com/pdk/latest/policies-pdk-create-project-split#agents-md). - PDK now provides the WebSocket library to write policies for WebSocket APIs. See [Support WebSocket APIs](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-websocket).
The WebSocket library is currently in open beta.
- PDK unit now provides support for testing WebSocket policies. See [Test WebSocket Policies](https://docs.mulesoft.com/pdk/latest/policies-pdk-unit#test-websocket-policies). - PDK unit testing now supports testing for any policy created with `proxy-wasm`. Use PDK Unit to test non-PDK policies before migrating them to PDK. See [Enable pdk-unit for Non-PDK Policies](https://docs.mulesoft.com/pdk/latest/policies-pdk-unit#enable-pdk-unit-for-non-pdk-policies). - \* PDK unit testing now better matches Envoy’s proxy-wasm host behavior, with added validations and bug fixes. - The PDK unit testing default chunk size increased from 3 bytes to 30KB to align with Envoy’s behavior and reduce event overhead when testing policies with regular-sized payloads. ### Fixed Issues
Issue Resolution ID

The JWT library no longer panics due to an unguarded unwrap.

W-22691626

Duplicated names in config.rs no longer occur in valid GCL.

W-22710786
## [](#1-8-0)1.8.0 **April 21, 2026** ### What’s New - PDK now provides the `PDK-Unit` testing framework to quickly test policies without deploying to an Omni Gateway. See [Writing Unit Tests](https://docs.mulesoft.com/pdk/latest/policies-pdk-unit). - PDK now automatically applies outbound policies to the service in the PDK debugging playground. - The `Clock` and `Timer` now expose the `now` method that returns the current SystemTime to provide more control than `SystemTime::now` for unit testing. See [Configuring Delayed, Periodic, and Synchronous Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-timer). - PDK now provides the Spike Control library for implementing spike arrest and smoothing rate limiting patterns. For more information, see: - [Using Spike Control Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-spike-control) - [Spike Policy Example](https://github.com/mulesoft/pdk-custom-policy-examples/blob/1.8.0/spike/README.md) - PDK now provides the XML Validator library to validate and process XML payloads with configurable rules. For more information, see: - [Using XML Validator Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-xml-validator) - [XML Validation Policy Example](https://github.com/mulesoft/pdk-custom-policy-examples/blob/1.8.0/xml-validation/README.md) - PDK now provides the JSON Validator library to validate and process JSON payloads with configurable validation rules. For more information, see: - [Using JSON Validator Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-json-validator) - [JSON Validation Policy Example](https://github.com/mulesoft/pdk-custom-policy-examples/blob/1.8.0/json-validation/README.md) - Custom Policies can now read and write to headers and bodies at the same time by using the `enable_stop_iteration` feature. See [Reading and Writing Request Headers and Bodies with Stop Iteration](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-headers-stop). - The PDK Token Introspection Library now supports Microsoft Entra ID and the RFC 9728 specification. The token validator now provides these methods for configuration: - `with_client_id`: Sets the client ID credential to talk with the introspection service. - `with_client_secret`: Sets the client secret credential to talk with the introspection service. - `with_protected_resource_metadata` Enables RFC 9728 protected resource discovery with the given authorization server URL. - `with_protected_resource_metadata_with_properties`: Enables RFC 9728 protected resource discovery with the given authorization server URL and additional metadata properties (such as `scopes_supported` or `bearer_methods_supported`). See [Using OAuth 2.0 Token Introspection Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-token-introspection). ### Fixed Issues
Issue Resolution ID

PDK policies now properly handle distributed rate limiting quotas.

W-22108203

PDK message logging policies now properly resolve dw::Core::-- expressions. -- functions are supported only in Flex Gateway versions 1.2.0 or later.

W-21643871
## [](#1-7-0)1.7.0 **February 12, 2026** ### What’s New - The name of the Anypoint CLI PDK plugin was changed from `anypoint-cli-pdk-plugin` to `anypoint-pdk-plugin`. To develop 1.7.0 policies, ensure you install the new plugin. See [Install the 1.7.0 Anypoint CLI PDK plugin](https://docs.mulesoft.com/pdk/latest/policies-pdk-upgrade-pdk#upgrade-anypoint-cli-pdk-plugin-earlier-1.7.0). - The Anypoint CLI PDK Plugin now supports split model policies to enable you to update policy definitions and implementations independently. See [Create a Split Model Policy Project](https://docs.mulesoft.com/pdk/latest/policies-pdk-create-project-split). - The JWT library now provides the functionality to create JWT tokens. See [Create a JWT Token](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-jwt#create-jwt-token). - You can now send an early response during the HTTP response event to terminate the execution flow early. See [Stop Response Execution](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-stop#stop-response-execution). - The IP-filter library now provides functionality to create allowlists or blocklists of IP addresses and CIDR ranges. See [Filter IP Addresses](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-ip-filter). - The OAuth 2.0 library now provides functionality to validate incoming OAuth 2.0 with OAuth 2.0 servers. See [Using OAuth 2.0 Token Introspection Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-token-introspection). ### Fixed Issues
Issue Resolution ID

There is no longer inconsistent store creation behavior across Object Store v2 and in-memory or Redis backends for the Rate Limiting library.

W-20223396

There is no longer a type mismatch error when extracting JWT objects from Bearer tokens.

W-20435785
## [](#1-6-0)1.6.0 **November 18, 2025** ### What’s New - PDK rust libraries are now hosted on [crates.io](https://crates.io/crates/pdk). You can now download the crates without a connection to Anypoint Platform. Creating, publishing, and releasing policies still requires Anypoint Platform connection. To upgrade your policies created before PDK v1.6.0, see [Upgrade Policies with Versions Earlier Than v1.6.0](https://docs.mulesoft.com/pdk/latest/policies-pdk-upgrade-pdk#upgrade-versions-earlier-1.6.0). - The minimum Rust version is now v1.88.0 to meet dependency requirements. To update your policy’s Rust version, see [Upgrade a Policy’s Rust Version](https://docs.mulesoft.com/pdk/latest/policies-pdk-upgrade-pdk#anypoint-rust-version). - PDK now uses `proxy_wasm` v0.2.4 to fix a memory leak in the crate. ### Fixed Issues
Issue Resolution ID

For Windows, the Makefile commands no longer fail due to the unrecognized command “export”. You must create a new policy to fix this issue.

W-19991510

Data storage Time To Live (TTL) values are now correctly converted from milliseconds to seconds when creating stores, and the maximum TTL upper bound of 30 days is now enforced.

W-20148366
## [](#1-5-0)1.5.0 **October 22, 2025** ### What’s New - PDK now provides data storage functionality to store and retrieve data across workers and replicas. Data storage supports both in-memory and shared storage. For shared storage, stored data can persist across API Gateway restarts. See [Configuring Data Storage](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-data-storage). - PDK now provides rate limiting functionality to control request rates. PDK rate limiting supports both single Flex Replicas and multi-replica clustered deployments. See [Rate Limiting Requests](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-rate-limiting). ## [](#1-4-1)1.4.1 **June 30, 2025** ### What’s New - PDK policies are now built with Rust Version 1.87.0 and require the `wasm32-wasip1` target. To update your Device’s rust version and download the `wasm32-wasip1` target, see [Rust Requirements for Using PDK](https://docs.mulesoft.com/pdk/latest/policies-pdk-prerequisites#rust-requirements). To update your existing policy’s rust version and WASI target, see [Upgrade a Policy’s Rust Version](https://docs.mulesoft.com/pdk/latest/policies-pdk-upgrade-pdk#anypoint-rust-version) and [Upgrade a Policy’s WASI Crate](https://docs.mulesoft.com/pdk/latest/policies-pdk-upgrade-pdk#anypoint-wasi-crate). - PDK can now develop Mule Gateway custom policies. See [Creating Mule Gateway PDK Policies](https://docs.mulesoft.com/pdk/latest/policies-pdk-mule-policies). - PDK now provides the Policy Violation framework to report policy violations to Anypoint Monitoring. See [Reporting Policy Violations](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-violations). - PDK now supports streaming payload bodies to read payload bodies larger than 1MB. See [Streaming Bodies](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-headers#streaming-bodies). - PDK now provides these new example policies: - [Stream Payload Policy Example](https://github.com/mulesoft/pdk-custom-policy-examples/blob/1.4.0/stream-payload/README.md): Use the Stream Payload Policy as an example of how to [read payload bodies larger than 1MB](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-headers#streaming-bodies). - [DataWeave Policy Example](https://github.com/mulesoft/pdk-custom-policy-examples/blob/1.4.0/dataweave/README.md): Use the DataWeave Policy as an example of how to handle [custom DataWeave expressions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-dataweave) in your custom policy. To learn more about example policies, see [Custom Policy Examples](https://docs.mulesoft.com/pdk/latest/policies-pdk-policy-templates). - The `payload` DataWeave Schema parameter now supports the `xml` `mimeType`. See [DataWeave Expressions Schema Definition](https://docs.mulesoft.com/pdk/latest/policies-pdk-create-schema-definition#dataweave-expressions). ### Fixed Issues
Issue Resolution ID

HTTP calls from timers are now isolated from regular HTTP operations to avoid interference between them.

W-18121316
### [](#compatibility)Compatibility Policies created with PDK might be compatible with Omni Gateway versions that aren’t compatible with PDK’s integration testing framework. The Omni Gateway version used for testing doesn’t affect the functionality of the policy when deployed to a different Omni Gateway version. See the following table to ensure your Omni Gateway’s compatibility:
Component Minimum Omni Gateway Version Maximum Omni Gateway Version

Policies

1.6.1

Latest

Testing Framework

1.6.1

Latest
## [](#1-3-0)1.3.0 **March 18, 2025** ### What’s New - PDK now provides a Contract Validation library to help with creating custom client ID enforcement policies. See [Using Contracts Validation Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-contracts). - PDK is now built with Rust Version 1.83.0 - Integration testing performance is improved for `pdk-test` with desktop configurations. - PDK can now develop outbound policies. See [Define Outbound Policies](https://docs.mulesoft.com/pdk/latest/policies-pdk-create-schema-definition#define-outbound-policies). ### Fixed Issues
Issue Resolution ID

GrpcClient now handles optional empty values instead of failing. Previously GrpcClient raised a GrpcClientError::EmptyContent error for some conditions with an empty optional field.

W-16486150
### [](#compatibility-2)Compatibility Policies created with PDK might be compatible with Omni Gateway versions that aren’t compatible with PDK’s integration testing framework. The Omni Gateway version used for testing doesn’t affect the functionality of the policy when deployed to a different Omni Gateway version. See the following table to ensure your Omni Gateway’s compatibility:
Component Minimum Omni Gateway Version Maximum Omni Gateway Version

Policies

1.6.1

Latest

Testing Framework

1.6.1

Latest
## [](#1-2-0)1.2.0 **August 28, 2024** ### What’s New - PDK now provides a CORS library to help create policies that process cross-origin requests. See [Using CORS Library Functions](https://docs.mulesoft.com/pdk/latest/policies-pdk-configure-features-cors). - The PDK integration testing framework is improved for easier test configuration. See [Writing Integration Tests](https://docs.mulesoft.com/pdk/latest/policies-pdk-integration-tests). - Incorrect conditional parameter schema configurations are now rejected when the policy is compiled instead of when the policy is deployed. - Conditional parameters can now depend on `boolean` and `integer` parameters. See [Define Conditional Parameters](https://docs.mulesoft.com/pdk/latest/policies-pdk-create-schema-definition#define-conditional-parameters). ### [](#compatibility-3)Compatibility Policies created with PDK might be compatible with Omni Gateway versions that aren’t compatible with PDK’s integration testing framework. The Omni Gateway version used for testing doesn’t affect the functionality of the policy when deployed to a different Omni Gateway version. See the following table to ensure your Omni Gateway’s compatibility:
Component Minimum Omni Gateway Version Maximum Omni Gateway Version

Policies

1.6.1

Latest

Testing Framework

1.6.1

Latest
## [](#see-also)See Also - [PDK Troubleshooting](https://docs.mulesoft.com/pdk/latest/policies-pdk-troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Omni Gateway Policy Development Kit (PDK) Release Notes Omni Gateway Policy Development Kit (PDK) is a software development kit that enables you to develop Omni Gateway custom policies with ease. PDK provides instructions to guide you through the policy development lifecycle, from implementing your Rust source code to releasing your policy on Exchange. Like included policies, you can apply custom policies to Omni Gateway running in Connected Mode by using API Manager or to Omni Gateway running in Local Mode by using YAML configuration files. The following release notes are provided for PDK: - [Omni Gateway Policy Development Kit (PDK) Release Notes](https://docs.mulesoft.com/jp/release-notes/pdk/pdk-release-notes) ## [](#see-also)See Also - [Omni Gateway Policy Development Kit (PDK) Overview](https://docs.mulesoft.com/pdk/latest/policies-pdk-overview) - [Omni Gateway Overview](https://docs.mulesoft.com/gateway/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # Omni Gateway Release Notes These release notes reflect enhancements, changes, and bug fixes for Omni Gateway. In addition to these release notes, see: - [Model Proxy Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/model-proxy-release-notes) ## [](#1-14-4)1.14.4 **October 23, 2026** MuleSoft announces the release of Omni Gateway 1.14.4. ### What’s New - Custom PDK policies can now access an API instance’s configured consumer URL through `api.consumerUri` in API Context. ### Fixed Issues
Issue Resolution ID

Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates.

W-24628768

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-35189

  • CVE-2026-35191

  • CVE-2026-42772

  • CVE-2026-54872

  • CVE-2026-54873

  • CVE-2026-54875

  • CVE-2026-72897

  • CVE-2026-75804

  • CVE-2026-75805

  • CVE-2026-75806

  • CVE-2026-77696

  • CVE-2026-78659

  • CVE-2026-78660

  • CVE-2026-78663

  • CVE-2026-78669

  • CVE-2026-84782

  • CVE-2026-84784

  • CVE-2026-97032

  • CVE-2026-111943

W-24624014
## [](#1-14-3)1.14.3 **October 20, 2026** MuleSoft announces the release of Omni Gateway 1.14.3. ### What’s New - Envoy is now upgraded to version 1.37.8. - Tracing custom labels now support integer, floating-point, and boolean OpenTelemetry attributes, and values resolved through Envoy substitution expressions. - The Credential Injection API Key policy now supports DataWeave expressions to resolve the API key from request attributes or payloads at runtime. ### Fixed Issues
Issue Resolution ID

Path normalization is now disabled by default. To enable it, set FLEX_PATH_NORMALIZATION_ENABLED to true.

W-24443266

Helm deployments now preserve a configured API address trailing slash and enable base-path canonicalization by default. APIs configured with a slashless base path can accept requests to that exact base path.

W-24541915

Omni Gateway now uses /var/tmp for temporary files, avoiding failures in containers with a read-only root filesystem.

W-24279051

Runtime Fabric Helm deployments now normalize wildcard-prefixed forward-proxy exclusions and omit unsupported CIDR entries.

W-24460337

Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener.

W-24511699

Gateway-agent configuration generation now uses less memory when multiple distinct WebAssembly policies are applied.

W-24390601

The Injection Protection policy no longer incorrectly rejects legitimate multipart SOAP requests with binary attachments when body scanning is enabled.

W-24361237

The JWT Validation policy now accepts RSA keys with padded base64url parameters in JWKS responses.

W-24309516

Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error.

W-24580345

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-48521

  • CVE-2026-50572

  • CVE-2026-56857

  • CVE-2026-56866

  • CVE-2026-73511

  • CVE-2026-73512

  • CVE-2026-73513

  • CVE-2026-73546

  • CVE-2026-73547

  • CVE-2026-73548

  • CVE-2026-73549

  • CVE-2026-73550

  • CVE-2026-73551

  • CVE-2026-73552

  • CVE-2026-73553

  • CVE-2026-78667

  • CVE-2026-94439

  • CVE-2026-94440

  • CVE-2026-94448

  • CVE-2026-97030

  • CVE-2026-97031

W-24456219, W-24578725
## [](#1-14-2)1.14.2 **October 1, 2026** MuleSoft announces the release of Omni Gateway 1.14.2. ### Fixed Issues
Issue Resolution ID

The JWT Validation, OpenID Connect OAuth 2.0 Token Enforcement, and OAuth 2.0 Token Introspection policies now preserve path segments and trailing slashes from consumer URLs when generating protected resource metadata URLs.

W-24119444

Omni Gateway now preserves percent-encoded reserved characters, such as %2F and %3A, in upstream URL paths when forwarding requests to backend services.

W-24135806

Per-API message logs in API Manager now populate correctly for Omni Gateway registrations that use v1 URLs.

W-24332213
## [](#1-14-1)1.14.1 **September 25, 2026** MuleSoft announces the release of Omni Gateway 1.14.1. ### What’s New - Managed Omni Gateway deployments on Runtime Fabric now support forward proxy configuration. - `Configuration` resources now support environment variable expansion in string and scalar values. - Self-Managed Omni Gateway can now internally rewrite requests that exactly match a configured slashless API base path, such as `/api`, to its slash-terminated form (`/api/`). Set `FLEX_BASE_PATH_CANONICALIZER_ENABLED` to `true` to enable this behavior. - The Message Logging policy now supports masking regex capture groups while preserving the rest of the matched value. ### Fixed Issues
Issue Resolution ID

Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization.

W-22456427

Log records larger than 32 KB no longer split into separate lines that lose their logging metadata. Oversized records are truncated instead.

W-24055090

Omni Gateway running in Connected Mode no longer sends duplicate runtime logs to Anypoint Platform after logging configuration changes.

W-24037601

Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied twice.

W-24195540

The Basic Authentication: LDAP policy no longer includes sensitive authentication data in logs.

W-24118398

The OpenID Connect OAuth 2.0 Token Enforcement policy now correctly applies defaultTLS.outboundPolicyCalls to identity-provider token requests without applying those settings to Anypoint Platform connections.

W-24268807

Tracing now preserves custom server span names without forwarding the x-envoy-decorator-operation header to upstream services. Upstream-only span tags no longer appear on server spans.

W-23923463

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-5450

  • CVE-2026-5928

  • GHSA-2v4p-qf9q-27wj

  • GHSA-8wmf-6v46-5gfg

W-24126253
## [](#1-14-0)1.14.0 **September 2, 2026** MuleSoft announces the release of Omni Gateway 1.14.0. ### What’s New - The JavaScript Scripting policy is added to run a user-supplied JavaScript module that can inspect and modify requests and responses directly from the gateway. See [JavaScript Scripting Policy](https://docs.mulesoft.com/gateway/latest/policies-included-javascript-scripting). - The GraphQL Access Control policy is added to authorize incoming GraphQL requests by evaluating Cedar-based access-control rules. See [GraphQL Access Control Policy](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-access-control). - Local storage is now file-based instead of in-memory. State used by policies such as Rate Limiting and HTTP Caching are now retained when Omni Gateway is stopped or restarted. - Configuration caching (control node) is now enabled by default. The `FLEX_DATASOURCE_CONTROL_NODE_ENABLED` environment variable now defaults to `true`. To disable it, set the variable to `false`. See [Configuring Omni Gateway Configuration Caching in Connected Mode](https://docs.mulesoft.com/gateway/latest/conn-replica-caching). - The OpenID Connect OAuth 2.0 Token Enforcement policy now exposes the **Validated Token TTL** (`maxFederationExpirationTime`) and **Maximum Cache Entries** (`maxCacheSize`) settings in Connected Mode to control how long validated tokens are cached and how many entries are stored. See [OpenID Connect OAuth 2.0 Token Enforcement Policy](https://docs.mulesoft.com/gateway/latest/policies-included-openid-token-enforcement). - The JWT Validation policy now supports OAuth 2.0 Protected Resource Metadata (RFC 9728). When enabled, the policy serves a discovery document at the `.well-known/oauth-protected-resource` endpoint and adds a `resource_metadata` hint to the `WWW-Authenticate` header of `401` responses, so clients can locate the authorization server that protects the API. See [JWT Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-jwt-validation). - The Credential Injection OAuth 2.0 policy now supports adding custom parameters, such as `audience`, to the OAuth 2.0 token request body. See [Credential Injection OAuth 2.0 Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-oauth). - The Message Logging policy now supports data masking to detect and mask personally identifiable information (PII), such as email addresses, in log messages before they are written. You can select built-in PII types (Email, US SSN, Credit Card, and Phone Number) or add custom regex patterns. Data masking is available for both inbound and outbound message logging, and request and response bodies are forwarded to the upstream service unchanged. See [Message Logging Policy](https://docs.mulesoft.com/gateway/latest/policies-included-message-logging) and [Outbound Message Logging Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-message-logging). - The Schema Validation policy now validates `multipart/form-data` requests against their OAS schema definitions, in addition to `application/json` request bodies. See [Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-schema-validation). - You can now configure the DNS refresh rate for upstream service clusters by setting the `FLEX_DNS_REFRESH_RATE` environment variable. The value is clamped between `5s` and `60s`, and defaults to `5s`. - The `flexctl dump` CLI command now collects a full snapshot of the gateway’s runtime state into a single ZIP file, including resources, logs, and Envoy statistics. You can write the snapshot to a specific path or stream it to standard output. See [Troubleshooting with the CLI](https://docs.mulesoft.com/gateway/latest/troubleshoot-admin-api). - The implementation of the DataWeave and SOAP policies is updated to improve policy performance, delivering higher throughput and lower latency. - The `flexctl check http` command now produces curl-style verbose output, logging request and response headers with `>` and `<` prefixes and writing the response body to standard output for easier scripting and inspection. - Flex Gateway deployments managed by Runtime Fabric for Kubernetes now support pod scheduling customizations (node selectors, tolerations, and affinity rules) defined through a KubernetesTemplate custom resource. Customizations take precedence over the corresponding chart-level settings when both are present. - Omni Gateway Docker images are now based on Debian 13 Distroless. ### Fixed Issues
Issue Resolution ID

The SOAP Validation policy no longer leaks temporary directories during configuration delivery. It now loads schema files whose paths contain spaces.

W-23442789

The WebSocket Connection Limit policy no longer omits rejected connections from the policy violations reported to Anypoint Monitoring.

W-23173354

Flex Gateway no longer rejects valid requests when an API specification (OAS) uses a decimal multipleOf constraint (such as 0.01, 0.001, or 0.1).

W-23192298

Omni Gateway no longer reports as ready when a deployment has failed (for example, when assets could not be downloaded), even when --allow-envoy-errors, --allow-api-errors, or --allow-policy-errors is set to true.

W-23543048

Flex Gateway no longer hangs when its shared storage configuration changes while the gateway is running.

W-23573044

Flex Gateway no longer fails to generate a valid FluentBit log configuration when a label used for log metadata (on the gateway, an API instance, or a service) has an empty value or contains spaces.

W-23147140

Flex Gateway no longer panics when the status and dump endpoints are called before the gateway configuration is fully available during startup.

W-23950422

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-33818

  • CVE-2026-39821

  • CVE-2026-46600

  • CVE-2026-56853

  • CVE-2026-56858

  • CVE-2026-56859

  • CVE-2026-56860

  • CVE-2026-56862

  • CVE-2026-56864

  • CVE-2026-56865

W-22733262
## [](#1-13-8)1.13.8 **October 23, 2026** MuleSoft announces the release of Omni Gateway 1.13.8. ### What’s New - Custom PDK policies can now access an API instance’s configured consumer URL through `api.consumerUri` in API Context. ### Fixed Issues
Issue Resolution ID

Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates.

W-24628768

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-35189

  • CVE-2026-35191

  • CVE-2026-42772

  • CVE-2026-54872

  • CVE-2026-54873

  • CVE-2026-54875

  • CVE-2026-72897

  • CVE-2026-56857

  • CVE-2026-56866

  • CVE-2026-78667

  • CVE-2026-84782

  • CVE-2026-75804

  • CVE-2026-75805

  • CVE-2026-75806

  • CVE-2026-77696

  • CVE-2026-84784

  • CVE-2026-94439

  • CVE-2026-94440

  • CVE-2026-94448

  • CVE-2026-97030

  • CVE-2026-97031

  • CVE-2026-111943

W-24624014
## [](#1-13-7)1.13.7 **October 21, 2026** MuleSoft announces the release of Omni Gateway 1.13.7. ### What’s New - Envoy is now upgraded to version 1.37.8. - The Credential Injection API Key policy now supports DataWeave expressions to resolve the API key from request attributes or payloads at runtime. ### Fixed Issues
Issue Resolution ID

Path normalization is now disabled by default. To enable it, set FLEX_PATH_NORMALIZATION_ENABLED to true.

W-24443266

Omni Gateway now uses /var/tmp for temporary files, avoiding failures in containers with a read-only root filesystem.

W-24279051

Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener.

W-24511699

Omni Gateway no longer crashes during startup in disconnected Runtime Fabric deployments when platform logging, monitoring, or metering endpoints are unavailable.

W-24525793

The Header Injection policy no longer crashes Omni Gateway when a DataWeave string literal contains Unicode characters outside the Latin-1 range on AMD64 and ARM64 platforms.

W-24090265

The JWT Validation, OpenID Connect OAuth 2.0 Token Enforcement, and OAuth 2.0 Token Introspection policies now preserve path segments and trailing slashes from consumer URLs when generating protected resource metadata URLs.

W-24119444

The Injection Protection policy no longer incorrectly rejects legitimate multipart SOAP requests with binary attachments when body scanning is enabled.

W-24361237

The JWT Validation policy now accepts RSA keys with padded base64url parameters in JWKS responses.

W-24309516

Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error.

W-24580345

Omni Gateway now preserves component output during shutdown and no longer waits indefinitely when a descendant process keeps output streams open.

W-24129984, W-24141774

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-48521

  • CVE-2026-50572

  • CVE-2026-73511

  • CVE-2026-73512

  • CVE-2026-73513

  • CVE-2026-73546

  • CVE-2026-73547

  • CVE-2026-73548

  • CVE-2026-73549

  • CVE-2026-73550

  • CVE-2026-73551

  • CVE-2026-73552

  • CVE-2026-73553

W-24456219, W-24578725
## [](#1-13-6)1.13.6 **September 24, 2026** MuleSoft announces the release of Omni Gateway 1.13.6. ### Fixed Issues
Issue Resolution ID

Updating gateway.configuration through the Omni Gateway Helm chart no longer causes a full pod rollout or removes the active configuration.

W-23969934

Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization.

W-22456427

The FLEX_FLUENTBIT_OUTPUT_STORAGE_TOTAL_LIMIT_SIZE environment variable now limits filesystem buffering for all Fluent Bit outputs.

W-24062935

Log records larger than 32 KB no longer split into separate lines that lose their logging metadata. Oversized records are truncated instead.

W-24055090

Omni Gateway running in Connected Mode no longer sends duplicate runtime logs to Anypoint Platform after logging configuration changes.

W-24037601

Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied twice.

W-24195540

The OpenID Connect OAuth 2.0 Token Enforcement policy now correctly applies defaultTLS.outboundPolicyCalls to identity-provider token requests without applying those settings to Anypoint Platform connections.

W-24268807

The Basic Authentication: LDAP policy no longer includes sensitive authentication data in logs.

W-24118398

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-14456

  • CVE-2026-14457

  • CVE-2026-18798

  • CVE-2026-33818

  • CVE-2026-39821

  • CVE-2026-46600

  • CVE-2026-5450

  • CVE-2026-54874

  • CVE-2026-56853

  • CVE-2026-56854

  • CVE-2026-56855

  • CVE-2026-56858

  • CVE-2026-56859

  • CVE-2026-56860

  • CVE-2026-56862

  • CVE-2026-5928

  • CVE-2026-63072

  • CVE-2026-63073

  • CVE-2026-63074

  • CVE-2026-63075

  • CVE-2026-63076

  • CVE-2026-75803

  • CVE-2026-78662

  • CVE-2026-81870

  • CVE-2026-81871

  • CVE-2026-84303

  • CVE-2026-84304

  • CVE-2026-84445

  • GHSA-w67g-5rqw-f597

W-24126253, W-24267883
## [](#1-13-5)1.13.5 **August 27, 2026** MuleSoft announces the release of Omni Gateway 1.13.5. ### Fixed Issues
Issue Resolution ID

Omni Gateway running in Connected Mode no longer disconnects unexpectedly from Anypoint Platform under high-traffic conditions or when the remote server sends data without replying with protocol-level pong frames.

W-23560278

Custom policies no longer crash Omni Gateway with a segmentation fault when a response payload is larger than the buffer limit (1 MB by default). Use the FLEX_DOWNSTREAM_CONNECTION_BUFFER_LIMIT_BYTES environment variable to increase the buffer limit.

W-23692178

The Basic Authentication: LDAP policy no longer lets specially crafted usernames to manipulate the underlying LDAP search filter.

W-23573199

Resetting Redis shared storage no longer fails with a cross-slot error in cluster-mode deployments (such as AWS ElastiCache).

W-23687400

Control node no longer discards synchronization state after 14 days to prevent inconsistencies when a gateway reconnects following an extended outage.

W-23692384

Control node Redis shared storage no longer grows without bound over time from historical configuration-change data.

W-23748466

Omni Gateway running in Connected Mode no longer disrupts running pods when its registration credentials are renewed.

W-23820257

Control node no longer delays propagating a configuration update or logs a false inconsistency warning after a transient failure while committing that update.

W-23754016

Control node no longer fails to apply deployment updates when multiple replicas write to the same resource at nearly the same time.

W-23748463, W-23748465

Custom policies no longer cause a memory leak that can increase memory usage over time.

W-23941703

Omni Gateway no longer produces a malformed path predicate (such as a duplicate or missing slash) when a negative-lookahead path pattern is combined with an API base path.

W-23912976

Omni Gateway running in Connected Mode no longer sends duplicate deployment-status updates to Anypoint Platform.

W-23862236

The JWT Validation policy no longer bypasses the configured forward proxy when fetching JWKS keys.

W-23840697

The Credential Injection OAuth 2.0 policy no longer ignores the configured caching duration when the OAuth 2.0 provider’s token response omits the token expiration value.

W-23705875

The Rate Limiting SLA policy with distributed rate limiting enabled no longer crashes the gateway (WASM trap, returning a 503 error instead of 429) under Redis latency and high concurrency on the same SLA tier.

W-23652660

The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer forward the raw error response from the introspection server to the client.

W-23665332

The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a 503 error on all requests when the exposeHeaders option is enabled and a token claim’s name contains characters that aren’t valid in an HTTP header name.

W-23940967

The OAuth 2.0 Token Introspection policy no longer fails when the introspection URL includes an explicit default port.

W-23471294

These vulnerabilities detected by scanners are now fixed:

  • CVE-2022-27943

  • CVE-2025-27587

  • CVE-2026-41178

  • CVE-2026-42767

  • CVE-2026-56852

  • CVE-2026-73500

  • GHSA-259r-337f-4rfw

  • GHSA-hrxh-6v49-42gf

W-23490974, W-23559915, W-23735964, W-23862957
## [](#1-13-4)1.13.4 **July 23, 2026** MuleSoft announces the release of Omni Gateway 1.13.4. ### Fixed Issues
Issue Resolution ID

Policy initialization during Envoy configuration generation is now faster. Wasm module inspection and compilation are now cached across policies that share the same module.

W-23480384

Configuration caching (control node) now works with AWS ElastiCache Serverless. Redis shared storage now uses the non-blocking SCAN command instead of KEYS. If your Redis access policy allows the KEYS command, update it to allow SCAN.

W-23399906

The SOAP Validation policy no longer leaks temporary directories during configuration delivery. It now loads schema files whose paths contain spaces.

W-23442789

The contract collector now honors the Retry-After header and properly waits between polls when downloading API configurations.

W-23460693

The JSON Threat Protection policy now accepts valid JSON containing an escaped forward slash (\/), per RFC 8259.

W-23510751

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-34182

  • CVE-2026-34180

  • CVE-2026-45445

  • CVE-2026-45447

  • CVE-2026-7383

  • CVE-2026-9076

  • CVE-2026-39822

  • CVE-2026-42504

  • CVE-2026-27145

  • CVE-2026-42766

  • CVE-2026-45446

  • CVE-2026-42505

  • CVE-2026-42507

  • CVE-2026-42770

W-22698091
## [](#1-13-3)1.13.3 **July 8, 2026** MuleSoft announces the release of Omni Gateway 1.13.3. ### What’s New - Envoy is now upgraded to version 1.37.5. ### Fixed Issues
Issue Resolution ID

Omni Replicas no longer fail to receive configuration updates in Connected Mode when the hostname changed.

W-23123632

Omni Gateway now supports deployments in environments using non-standard IP address ranges (240.0.0.0/4).

W-22771253

The handling of rate-limited responses when downloading API configurations is now improved to reduce failures during high-traffic periods.

W-23202349

The readiness probe accuracy is now improved to ensure Omni Gateway only reports as ready when all API configurations are successfully loaded and available for processing traffic. Set --allow-api-errors to false to enable this behavior.

W-23297348

The XML Threat Protection policy now correctly validates and processes XML payloads.

W-18172654

SLA tier tracking across authentication policies (Client ID Enforcement, JWT Validation) and Rate Limiting SLA policy is now improved for better analytics and governance.

W-22937088

The Injection Protection policy pattern matching is now improved for better threat detection accuracy.

W-22693332

The SOAP Schema Validation policy now correctly processes requests containing nested XOP elements in MTOM payloads

W-21779437

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-34182

  • CVE-2026-45447

  • CVE-2026-34180

  • CVE-2026-7383

  • CVE-2026-45445

  • CVE-2026-9076

  • CVE-2026-47774

  • CVE-2026-47220

  • CVE-2026-48706

  • CVE-2026-48042

  • CVE-2026-48044

  • CVE-2026-47204

  • CVE-2026-47221

  • CVE-2026-48497

  • CVE-2026-48743

  • CVE-2026-27145

  • CVE-2026-42504

W-22698091
## [](#1-13-2)1.13.2 **June 6, 2026** MuleSoft announces the release of Omni Gateway 1.13.2. ### Fixed Issues
Issue Resolution ID

Logging for the flexctl readiness probe is now improved.

W-21615708

The statsEvictionInterval configuration is now added to Envoy bootstrap.

W-22545512

The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies now properly populate the authentication.principal property.

W-22696442

The Injection Protection Policy now allows you to apply a policy that uses only custom protections.

W-22491337

These vulnerabilities detected by scanners are now fixed:

  • VE-2025-15281

  • CVE-2026-0861

  • CVE-2026-0915

  • CVE-2026-25680

  • CVE-2026-25681

  • CVE-2026-27136

  • CVE-2026-32952

  • CVE-2026-33814

  • CVE-2026-39821

  • CVE-2026-39824

  • CVE-2026-39827

  • CVE-2026-39828

  • CVE-2026-39829

  • CVE-2026-39830

  • CVE-2026-39831

  • CVE-2026-39832

  • CVE-2026-39833

  • CVE-2026-39834

  • CVE-2026-39835

  • CVE-2026-4046

  • CVE-2026-42502

  • CVE-2026-42506

  • CVE-2026-42508

  • CVE-2026-4437

  • CVE-2026-4438

  • CVE-2026-46595

  • CVE-2026-46597

  • CVE-2026-46598

  • CVE-2026-4878

W-22698091
## [](#1-13-1)1.13.1 **May 20, 2026** MuleSoft announces the release of Omni Gateway 1.13.1. ### Fixed Issues
Issue Resolution ID

The OpenTelemetry Collector now correctly starts in environments (such as Google Cloud Run) that were previously failing.

W-22419420

The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed.

W-21484884

The flexctl dump error message is now improved when redis is unavailable.

W-22365034

Contract resiliency for PDK now improves resource usage.

W-22048194

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-33811

  • CVE-2026-33814

  • CVE-2026-39820

  • CVE-2026-39836

  • CVE-2026-42499

  • CVE-2026-42501

  • CVE-2026-39817

  • CVE-2026-39819

  • CVE-2026-39823

  • CVE-2026-39825

  • CVE-2026-39826

  • GHSA-8rm2-7qqf-34qm

  • GHSA-wg65-39gg-5wfj

  • GHSA-fw8g-cg8f-9j28

  • GHSA-vffh-x6r8-xx99

  • GHSA-wg65-39gg-5wfj

W-22478633, W-22478649, W-22478660, W-22478666, W-22478702, W-22509993, W-22509992, W-22477420, W-22477544, W-22509994, W-22509995
## [](#1-13-0)1.13.0 **May 11, 2026** MuleSoft announces the release of Omni Gateway 1.13.0. ### What’s New - Flex Gateway is now named to Omni Gateway. Currently, this is a non-breaking change and only cosmetically affects the UI and documentation. This change shouldn’t affect CI/CD pipelines. There are no changes to these areas: - Anypoint Platform CLI - Anypoint Platform APIs - Logging - Environment variables - Documentation URL links - MCP tool names - Omni Gateway now supports GraphQL APIs. To add a GraphQL API to Omni Gateway, see [Flex Gateway API インスタンスの追加](https://docs.mulesoft.com/jp/api-manager/latest/create-instance-task-flex). - Omni Gateway now provides these policies to support GraphQL APIs: - [GraphQL Schema Validation](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-schema-validation): Validates incoming GraphQL operations against a GraphQL schema definition - [GraphQL Introspection Control](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-introspection-control): Blocks or allows requests that access the `_schema_`_,_ `type`, and `__typename` GraphQL meta fields - [GraphQL Operation Limits](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-operation-limits): Limits GraphQL operation depth, aliases, root fields, and directives - [GraphQL Static Query Complexity](https://docs.mulesoft.com/gateway/latest/policies-included-graphql-static-query-complexity): Calculates query complexity and blocks requests that exceed the defined budget - Omni Gateway now supports WebSocket APIs. To add a WebSocket API to Omni Gateway, see [Flex Gateway API インスタンスの追加](https://docs.mulesoft.com/jp/api-manager/latest/create-instance-task-flex). - Omni Gateway now provides the [WebSocket Connection Limit](https://docs.mulesoft.com/gateway/latest/policies-included-websocket-connection-limit) to limit the number of simultaneous WebSocket connections that each API instance allows. - Omni Gateway is now supported in CloudHub 2.0 shared spaces. To deploy a gateway to a shared space, see [Deploy a Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up). - Managed Omni Gateways deployed to CloudHub 2.0 private spaces now provide the **Cluster endpoint** for traffic internal to the cluster to bypass the CloudHub 2.0 ingress. See [Managed Omni Gateway Endpoints](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up#managed-omni-gateway-endpoints). - MCP Bridge now provides an improved creation experience. See [api-manager::create-instance-task-mcp-bridge.adoc](#api-manager::create-instance-task-mcp-bridge.adoc). - Omni Gateway now supports conditional policy application for inbound policies to apply policies to specific methods, URI paths, hosts, and headers. Outbound policies support conditional policy application for specific methods and headers. See [Apply Inbound Omni Gateway Policies](https://docs.mulesoft.com/gateway/latest/gateway-secure-conn#apply-inbound-policy). - Envoy is now upgrade to version 1.37.2. ### Fixed Issues
Issue Resolution ID

Contracts are no longer dropped when the client secret is null.

W-21177259

The OAuth 2.0 Token Introspection policy now correctly retrieves contracts when skip_client_id_validation is true.

W-21371313

Readiness signal errors in the OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies are now fixed.

W-21526778

When FLEX_DATASOURCE_CONTROL_NODE_ENABLED=true, Connected Mode Omni Gateway can now scale up if Anypoint is unavailable.

W-22300290

CORS policy now supports wildcard (*) origins.

W-19971117
## [](#1-12-12)1.12.12 **October 23, 2026** MuleSoft announces the release of Omni Gateway 1.12.12. ### What’s New - Custom PDK policies can now access an API instance’s configured consumer URL through `api.consumerUri` in API Context. ### Fixed Issues
Issue Resolution ID

Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates.

W-24628768

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-35189

  • CVE-2026-35191

  • CVE-2026-42772

  • CVE-2026-54872

  • CVE-2026-54873

  • CVE-2026-54875

  • CVE-2026-72897

  • CVE-2026-56857

  • CVE-2026-56866

  • CVE-2026-78667

  • CVE-2026-84782

  • CVE-2026-75804

  • CVE-2026-75805

  • CVE-2026-75806

  • CVE-2026-77696

  • CVE-2026-84784

  • CVE-2026-94439

  • CVE-2026-94440

  • CVE-2026-94448

  • CVE-2026-97030

  • CVE-2026-97031

  • CVE-2026-111943

W-24624014
## [](#1-12-11)1.12.11 **October 21, 2026** MuleSoft announces the release of Omni Gateway 1.12.11. ### What’s New - The Credential Injection API Key policy now supports DataWeave expressions to resolve the API key from request attributes or payloads at runtime. ### Fixed Issues
Issue Resolution ID

Path normalization is now disabled by default. To enable it, set FLEX_PATH_NORMALIZATION_ENABLED to true.

W-24443266

Omni Gateway now uses /var/tmp for temporary files, avoiding failures in containers with a read-only root filesystem.

W-24279051

Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener.

W-24511699

Omni Gateway no longer crashes during startup in disconnected Runtime Fabric deployments when platform logging, monitoring, or metering endpoints are unavailable.

W-24525793

The Header Injection policy no longer crashes Omni Gateway when a DataWeave string literal contains Unicode characters outside the Latin-1 range on AMD64 and ARM64 platforms.

W-24090265

Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error.

W-24580345

Omni Gateway now preserves component output during shutdown and no longer waits indefinitely when a descendant process keeps output streams open.

W-24129984, W-24141774
## [](#1-12-10)1.12.10 **September 25, 2026** MuleSoft announces the release of Omni Gateway 1.12.10. ### Fixed Issues
Issue Resolution ID

Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization.

W-22456427

The FLEX_FLUENTBIT_OUTPUT_STORAGE_TOTAL_LIMIT_SIZE environment variable now limits filesystem buffering for all Fluent Bit outputs.

W-24062935

Omni Gateway no longer splits log entries longer than 8 KB into continuation lines that can be misclassified. Lines up to 32 KB are preserved, and longer lines are truncated and marked.

W-24055090

Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied by both Gateway Manager and Runtime Fabric.

W-24195540

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-14456

  • CVE-2026-14457

  • CVE-2026-18798

  • CVE-2026-33818

  • CVE-2026-39821

  • CVE-2026-46600

  • CVE-2026-5450

  • CVE-2026-54874

  • CVE-2026-56853

  • CVE-2026-56854

  • CVE-2026-56855

  • CVE-2026-56858

  • CVE-2026-56859

  • CVE-2026-56860

  • CVE-2026-56862

  • CVE-2026-5928

  • CVE-2026-63072

  • CVE-2026-63073

  • CVE-2026-63074

  • CVE-2026-63075

  • CVE-2026-63076

  • CVE-2026-75803

  • CVE-2026-78662

  • CVE-2026-81870

  • CVE-2026-81871

  • CVE-2026-84303

  • CVE-2026-84304

  • CVE-2026-84445

  • GHSA-w67g-5rqw-f597

W-24126253, W-24267883
## [](#1-12-9)1.12.9 **August 27, 2026** MuleSoft announces the release of Omni Gateway 1.12.9. ### What’s New - The OpenTelemetry Collector is now upgraded to version 0.158.0. ### Fixed Issues
Issue Resolution ID

Omni Gateway running in Connected Mode no longer disconnects unexpectedly from Anypoint Platform under high-traffic conditions or when the remote server sends data without replying with protocol-level pong frames.

W-23560278

Custom policies no longer crash Omni Gateway with a segmentation fault when a response payload is larger than the buffer limit (1 MB by default). Use the FLEX_DOWNSTREAM_CONNECTION_BUFFER_LIMIT_BYTES environment variable to increase the buffer limit.

W-23692178

The Basic Authentication: LDAP policy no longer lets specially crafted usernames to manipulate the underlying LDAP search filter.

W-23573199

Resetting Redis shared storage no longer fails with a cross-slot error in cluster-mode deployments (such as AWS ElastiCache).

W-23687400

Control node no longer discards synchronization state after 14 days to prevent inconsistencies when a gateway reconnects following an extended outage.

W-23692384

Control node Redis shared storage no longer grows without bound over time from historical configuration-change data.

W-23748466

The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed.

W-21764662

Omni Gateway running in Connected Mode no longer disrupts running pods when its registration credentials are renewed.

W-23820257

Control node no longer delays propagating a configuration update or logs a false inconsistency warning after a transient failure while committing that update.

W-23754016

Control node no longer fails to apply deployment updates when multiple replicas write to the same resource at nearly the same time.

W-23748463, W-23748465

Custom policies no longer cause a memory leak that can increase memory usage over time.

W-23941703

Omni Gateway no longer produces a malformed path predicate (such as a duplicate or missing slash) when a negative-lookahead path pattern is combined with an API base path.

W-23912976

The Credential Injection OAuth 2.0 policy no longer ignores the configured caching duration when the OAuth 2.0 provider’s token response omits the token expiration value.

W-23705875

The Rate Limiting SLA policy with distributed rate limiting enabled no longer crashes the gateway (WASM trap, returning a 503 error instead of 429) under Redis latency and high concurrency on the same SLA tier.

W-23652660

The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer forward the raw error response from the introspection server to the client.

W-23665332

The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a 503 error on all requests when the exposeHeaders option is enabled and a token claim’s name contains characters that aren’t valid in an HTTP header name.

W-23940967

The contract collector now honors the Retry-After header and properly waits between polls when downloading API configurations.

W-23460693

The OAuth 2.0 Token Introspection policy no longer fails when the introspection URL includes an explicit default port.

W-23471294

These vulnerabilities detected by scanners are now fixed:

  • CVE-2022-27943

  • CVE-2025-27587

  • CVE-2026-41178

  • CVE-2026-42767

  • CVE-2026-56852

  • CVE-2026-73500

  • GHSA-259r-337f-4rfw

  • GHSA-hrxh-6v49-42gf

W-23490974, W-23559915, W-23862957
## [](#1-12-8)1.12.8 **July 21, 2026** MuleSoft announces the release of Omni Gateway 1.12.8. ### Fixed Issues
Issue Resolution ID

Omni Replicas no longer fail to receive configuration updates in Connected Mode when the hostname changed.

W-23123632

Omni Gateway now supports deployments in environments using non-standard IP address ranges (240.0.0.0/4).

W-22771253

The handling of rate-limited responses when downloading API configurations is now improved to reduce failures during high-traffic periods.

W-23202349

The readiness probe accuracy is now improved to ensure Omni Gateway only reports as ready when all API configurations are successfully loaded and available for processing traffic. Set --allow-api-errors to false to enable this behavior.

W-23297348

The XML Threat Protection policy now correctly validates and processes XML payloads.

W-18172654

The Injection Protection policy pattern matching is now improved for better threat detection accuracy.

W-22693332

HTTP retry logic now drains response bodies between retry attempts to prevent connection pool exhaustion.

W-23252601

Configuration caching (control node) now works with AWS ElastiCache Serverless. Redis shared storage now uses the non-blocking SCAN command instead of KEYS. If your Redis access policy allows the KEYS command, update it to allow SCAN.

W-23399906

Policy initialization during Envoy configuration generation is now faster. Wasm module inspection and compilation are now cached across policies that share the same module.

W-23480384

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-34182

  • CVE-2026-34180

  • CVE-2026-45445

  • CVE-2026-45447

  • CVE-2026-7383

  • CVE-2026-9076

  • CVE-2026-39822

  • CVE-2026-42504

  • CVE-2026-27145

  • CVE-2026-42766

  • CVE-2026-45446

  • CVE-2026-42505

  • CVE-2026-42507

  • CVE-2026-42770

W-22698091
## [](#1-12-7)1.12.7 **June 6, 2026** MuleSoft announces the release of Anypoint Omni Gateway 1.12.7. ### Fixed Issues
Issue Resolution ID

The principal is no longer always null in the authentication object for OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies.

W-22696442

These vulnerabilities detected by scanners are now fixed:

  • VE-2025-15281

  • CVE-2026-0861

  • CVE-2026-0915

  • CVE-2026-25680

  • CVE-2026-25681

  • CVE-2026-27136

  • CVE-2026-32952

  • CVE-2026-33814

  • CVE-2026-39821

  • CVE-2026-39824

  • CVE-2026-39827

  • CVE-2026-39828

  • CVE-2026-39829

  • CVE-2026-39830

  • CVE-2026-39831

  • CVE-2026-39832

  • CVE-2026-39833

  • CVE-2026-39834

  • CVE-2026-39835

  • CVE-2026-4046

  • CVE-2026-42502

  • CVE-2026-42506

  • CVE-2026-42508

  • CVE-2026-4437

  • CVE-2026-4438

  • CVE-2026-46595

  • CVE-2026-46597

  • CVE-2026-46598

  • CVE-2026-4878

W-22698091
## [](#1-12-6)1.12.6 **May 20, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.12.6. ### Fixed Issues
Issue Resolution ID

The OpenTelemetry Collector now correctly starts in environments (such as Google Cloud Run) that were previously failing.

W-22419420

The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed.

W-21484884

The flexctl dump error message is now improved when redis is unavailable.

W-22365034

The Injection Protection Policy now allows you to apply a policy that only uses custom protections.

W-22491337

Contract resiliency for PDK now improves resource usage.

W-22048194

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-33811

  • CVE-2026-33814

  • CVE-2026-39820

  • CVE-2026-39836

  • CVE-2026-42499

  • CVE-2026-42501

  • CVE-2026-39817

  • CVE-2026-39819

  • CVE-2026-39823

  • CVE-2026-39825

  • CVE-2026-39826

  • GHSA-8rm2-7qqf-34qm

  • GHSA-wg65-39gg-5wfj

  • GHSA-fw8g-cg8f-9j28

  • GHSA-vffh-x6r8-xx99

  • GHSA-wg65-39gg-5wfj

W-22478633, W-22478649, W-22478660, W-22478666, W-22478702, W-22509993, W-22509992, W-22477420, W-22477544, W-22509994, W-22509995
## [](#1-12-5)1.12.5 **May 7, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.12.5. ### Fixed Issues
Issue Resolution ID

MCP and A2A metrics are now reported correctly.

W-22346105

The OAuth 2.0 Token Introspection and OpenID Connect OAuth 2.0 Token Enforcement policies now correctly use the consumer URL for protected resource metadata.

W-22215222
## [](#1-12-4)1.12.4 **April 29, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.12.4. ### What’s New - Envoy is now updated to version 1.35.10. ### Fixed Issues
Issue Resolution ID

Vulnerabilities detected by scanners are now fixed.

W-22139443
## [](#1-12-3)1.12.3 **April 22, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.12.3. ### Fixed Issues
Issue Resolution ID

Vulnerabilities detected by scanners are now fixed.

W-22028896

The DataWeave -- operator now correctly removes entries from an object.

W-21643871

The OpenID Policy now correctly sends identity provider credentials in the header instead of the body.

W-22061343

Rate Limiting policies now correctly distribute the quota between replicas when distributed rate-limiting is enabled.

W-22108203
## [](#1-12-2)1.12.2 **March 31, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.12.2. ### What’s New - The [OAuth 2.0 Token Introspection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-oauth-token-introspection) and [OpenID Connect OAuth 2.0 Token Enforcement Policy](https://docs.mulesoft.com/gateway/latest/policies-included-openid-token-enforcement) now support the OAuth 2.0 discovery flow and parameters required for MCP clients. ### Fixed Issues
Issue Resolution ID

Vulnerabilities detected by scanners are now fixed.

W-21668427

When making outbound requests from policies, the port is no longer included in the request authority unless the port is explicitly specified in the target URL.

W-21471214
## [](#1-12-1)1.12.1 **March 2, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.12.1. ### Fixed Issues
Issue Resolution ID

Managed Flex Gateway deployed on CloudHub 2.0 no longer produces UDP log errors.

W-21361063
## [](#1-12-0)1.12.0 **February 25, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.12.0. ### What’s New - Managed Flex Gateway now supports Runtime Fabric deployments. See [Deploying Managed Flex Gateway on Runtime Fabric](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up#rtf). - Extra Large Managed Flex Gateway is now available for production purposes with higher throughput and more process demanding policies. To learn more about the performance metrics for Extra Large Managed Flex Gateway, see [Managed Flex Gateway Limits and Performance Metrics](https://docs.mulesoft.com/gateway/latest/review-prerequisites#managed-flex-gateway-limits). - Flex Gateway now supports creating an MCP Bridge to expose API instances as an MCP server. See [api-manager::create-instance-task-mcp-bridge.adoc](#api-manager::create-instance-task-mcp-bridge.adoc). - These DataWeave policies are added to modify and filter requests: - [DataWeave Body Transformation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-dataweave-body-transformation): Transforms request or response body content with a DataWeave script - [DataWeave Headers Transformation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-dataweave-headers-transformation): Transforms request or response headers with a DataWeave script - [DataWeave Request Filter Policy](https://docs.mulesoft.com/gateway/latest/policies-included-dataweave-request-filter): Filters requests by using a DataWeave script - A Credential Injection JWT Generation policy is added to generate and inject JWT tokens into outgoing requests. See [Credential Injection JWT Generation Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-jwt-generation). - A Injection Protection policy is added to scan incoming request headers, path, query string, and body for SQL injection, XSS (Cross-Site Scripting), and custom injection attacks. See [Injection Protection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-injection-protection). - Functionality is added to configure TLS for outgoing HTTP requests from Self-Managed Flex Gateway policies. See [Configuring TLS for Outgoing Policy Requests](https://docs.mulesoft.com/gateway/latest/policies-tls-configuration). - Managed Flex Gateway and Self-Managed Flex Gateway running in Connected Mode now provides the **Runtime Configuration** tab in Runtime Manager to configure and edit logging, tracing, timeouts, circuit breakers, probes, and other runtime properties. - SOAP APIs now support Payloads over 1MB. - Managed Flex Gateway replicas now communicate directly with each other for real-time sharing of HTTP caching and rate limiting data instead of using Object Storage V2. See [Managed Omni Gateway High Availability and Disaster Recovery Deployments](https://docs.mulesoft.com/gateway/latest/gateway-architecture-managed-dr-ha). - Flex Gateway now supports `dw::Core::--` DataWeave functions. See [\-- Functions](https://docs.mulesoft.com/gateway/latest/policies-dataweave-support#available-minus-operators). ### Fixed Issues
Issue Resolution ID

The SOAP Schema Validation Policy no longer intermittently bypasses validation

W-20173820

Flex Gateway no longer has a usage mismatch when using an HTTP probe.

W-20278837

Flex Gateway now retries to download contracts from Anypoint Platform after failure.

W-20435629

Flex Gateway no longer has temporary request failures during API specification (OAS) updates.

W-20646216

JSON Threat Protection Policy no longer rejects numeric exponential notation.

W-21186984

Vulnerabilities detected by scanners are now fixed.

W-21188054

Flex Gateway no longer loses metric data when A2A and MCP policies are applied.

W-21016899
## [](#1-9-19)1.9.19 **October 23, 2026** MuleSoft announces the release of Omni Gateway 1.9.19. ### Fixed Issues
Issue Resolution ID

Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates.

W-24628768

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-42767

  • CVE-2026-54874

  • CVE-2026-63072

  • CVE-2026-63074

  • CVE-2026-63076

  • CVE-2026-75803

  • CVE-2026-78659

  • CVE-2026-78660

  • CVE-2026-78663

  • CVE-2026-78669

  • CVE-2026-97032

  • CVE-2026-111943

W-24624014
## [](#1-9-18)1.9.18 **October 21, 2026** MuleSoft announces the release of Omni Gateway 1.9.18. ### Fixed Issues
Issue Resolution ID

Path normalization is now disabled by default. To enable it, set FLEX_PATH_NORMALIZATION_ENABLED to true.

W-24443266

Omni Gateway now uses /var/tmp for temporary files, avoiding failures in containers with a read-only root filesystem.

W-24279051

Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener.

W-24511699

The Header Injection policy no longer crashes Omni Gateway when a DataWeave string literal contains Unicode characters outside the Latin-1 range on AMD64 and ARM64 platforms.

W-24090265

Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error.

W-24580345

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-56857

  • CVE-2026-56866

  • CVE-2026-78667

  • CVE-2026-94439

  • CVE-2026-94440

  • CVE-2026-94448

  • CVE-2026-97030

  • CVE-2026-97031

W-24578725
## [](#1-9-17)1.9.17 **September 24, 2026** MuleSoft announces the release of Omni Gateway 1.9.17. ### Fixed Issues
Issue Resolution ID

Updating gateway.configuration through the Omni Gateway Helm chart no longer causes a full pod rollout or removes the active configuration.

W-23969934

Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization.

W-22456427

The FLEX_FLUENTBIT_OUTPUT_STORAGE_TOTAL_LIMIT_SIZE environment variable now limits filesystem buffering for all Fluent Bit outputs.

W-24062935

Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied by both Gateway Manager and Runtime Fabric.

W-24195540
## [](#1-9-16)1.9.16 **August 27, 2026** MuleSoft announces the release of Omni Gateway 1.9.16. ### Fixed Issues
Issue Resolution ID

The Basic Authentication: LDAP policy no longer lets specially crafted usernames to manipulate the underlying LDAP search filter.

W-23573199

Resetting Redis shared storage no longer fails with a cross-slot error in cluster-mode deployments (such as AWS ElastiCache).

W-23687400

Control node no longer discards synchronization state after 14 days to prevent inconsistencies when a gateway reconnects following an extended outage.

W-23692384

The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed.

W-21764662

Configuration caching (control node) now works with AWS ElastiCache Serverless. Redis shared storage now uses the non-blocking SCAN command instead of KEYS. If your Redis access policy allows the KEYS command, update it to allow SCAN.

W-23399906

Control node Redis shared storage no longer grows without bound over time from historical configuration-change data.

W-23748466

Control node no longer fails to apply deployment updates when multiple replicas write to the same resource at nearly the same time.

W-23748463, W-23748465

Control node no longer delays propagating a configuration update or logs a false inconsistency warning after a transient failure while committing that update.

W-23754016

Omni Gateway running in Connected Mode no longer disrupts running pods when its registration credentials are renewed.

W-23820257

The contract collector now honors the Retry-After header and properly waits between polls when downloading API configurations.

W-23460693

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-33818

  • CVE-2026-39821

  • CVE-2026-41178

  • CVE-2026-46600

  • CVE-2026-56852

  • CVE-2026-56853

  • CVE-2026-56858

  • CVE-2026-56859

  • CVE-2026-56860

  • CVE-2026-56862

  • CVE-2026-56864

  • CVE-2026-56865

  • CVE-2026-73500

  • GHSA-hrxh-6v49-42gf

W-23559915, W-23735964, W-23862957
## [](#1-9-15)1.9.15 **July 21, 2026** MuleSoft announces the release of Omni Gateway 1.9.15. ### Fixed Issues
Issue Resolution ID

Omni Replicas no longer fail to receive configuration updates in Connected Mode when the hostname changed.

W-23123632

HTTP retry logic now drains response bodies between retry attempts to prevent connection pool exhaustion.

W-23252601

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-34182

  • CVE-2026-34180

  • CVE-2026-45445

  • CVE-2026-45447

  • CVE-2026-7383

  • CVE-2026-9076

  • CVE-2026-39822

  • CVE-2026-42504

  • CVE-2026-27145

  • CVE-2026-42766

  • CVE-2026-45446

  • CVE-2026-42505

  • CVE-2026-42507

  • CVE-2026-42770

W-22698091
## [](#1-9-14)1.9.14 **June 6, 2026** MuleSoft announces the release of Anypoint Omni Gateway 1.9.14. ### Fixed Issues
Issue Resolution ID

These vulnerabilities detected by scanners are now fixed:

  • VE-2025-15281

  • CVE-2026-0861

  • CVE-2026-0915

  • CVE-2026-25680

  • CVE-2026-25681

  • CVE-2026-27136

  • CVE-2026-32952

  • CVE-2026-33814

  • CVE-2026-39821

  • CVE-2026-39824

  • CVE-2026-39827

  • CVE-2026-39828

  • CVE-2026-39829

  • CVE-2026-39830

  • CVE-2026-39831

  • CVE-2026-39832

  • CVE-2026-39833

  • CVE-2026-39834

  • CVE-2026-39835

  • CVE-2026-4046

  • CVE-2026-42502

  • CVE-2026-42506

  • CVE-2026-42508

  • CVE-2026-4437

  • CVE-2026-4438

  • CVE-2026-46595

  • CVE-2026-46597

  • CVE-2026-46598

  • CVE-2026-4878

W-22698091
## [](#1-9-13)1.9.13 **May 20, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.9.13. ### Fixed Issues
Issue Resolution ID

The flexctl dump error message is now improved when redis is unavailable.

W-22365034

These vulnerabilities detected by scanners are now fixed:

  • CVE-2026-33811

  • CVE-2026-33814

  • CVE-2026-39820

  • CVE-2026-39836

  • CVE-2026-42499

  • CVE-2026-42501

  • CVE-2026-39817

  • CVE-2026-39819

  • CVE-2026-39823

  • CVE-2026-39825

  • CVE-2026-39826

W-22478633, W-22478649, W-22478660, W-22478666, W-22478702, W-22509993, W-22509992
## [](#1-9-12)1.9.12 **April 24, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.9.12. ### Fixed Issues
Issue Resolution ID

Vulnerabilities detected by scanners are now fixed.

W-22028896
## [](#1-9-11)1.9.11 **March 31, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.9.11. ### Fixed Issues
Issue Resolution ID

Vulnerabilities detected by scanners are now fixed.

W-21668427
## [](#1-9-10)1.9.10 **March 5, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.9.10. ### Fixed Issues
Issue Resolution ID

Vulnerabilities detected by scanners are now fixed.

W-21259850

Trace configuration now supports setting up a trusted CA.

W-21018187

The JSON Threat Protection policy no longer rejects numeric exponential notation.

W-21186984

The Schema Validation policy now validates the raw URL-encoded raw value instead of the URL-decoded value.

W-20531156

Flex Gateway no longer loses metric data when A2A and MCP policies are applied.

W-21016899
## [](#1-9-9)1.9.9 **January 7, 2026** MuleSoft announces the release of Anypoint Flex Gateway 1.9.9. ### Fixed Issues
Issue Resolution ID

Vulnerabilities detected by scanners are now fixed.

W-20365927

If an error occurs when the JWT Validation policy calls the JWKS server, the time between retry requests now doubles with each request.

W-19647107

Flex Gateway now correctly sends logging information to Anypoint Platform.

W-20365743
## [](#1-9-8)1.9.8 **November 13, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.8. ### Fixed Issues
Issue Resolution ID

Flex Gateway running in Connected Mode now retries when requests to Anypoint Platform fail.

W-20037629

Vulnerabilities detected by scanners are now fixed.

W-20125828
## [](#1-9-7)1.9.7 **October 17, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.7. ### What’s New - For the Rate Limiting and SLA-Based Rate Limiting policies, if distributed rate limiting is enabled, the policy resizes time windows under 10 seconds linearly. For example, if you configure a max of 10 requests per 5 seconds, the policy resizes that window to a max of 20 requests per 10 seconds. See [Rate Limiting: SLA-Based Policy](https://docs.mulesoft.com/gateway/latest/policies-included-rate-limiting-sla) and [Rate Limiting Policy](https://docs.mulesoft.com/gateway/latest/policies-included-rate-limiting). ### Fixed Issues
Issue Resolution ID

Flex Gateway registration calls from Docker no longer fail for Hyperforce deployments.

W-19444135

Vulnerabilities detected by scanners are now fixed.

W-19787132, W-19971092

The Connected Mode deployment process is now improved.

W-19861373
## [](#1-9-6)1.9.6 **August 26, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.6. ### Fixed Issues
Issue Resolution ID

OAS Schemas are now correctly present in the local configuration cache.

W-18833198

The Envoy agent now properly restarts child processes that end with a core dump or kill signal.

W-19327530

The readiness probe no longer fails when the OAuth Token Introspection policy has skip_client_id_validation enabled.

W-19118057

The readiness probe no longer fails when the OpenID Connect OAuth 2.0 Token Enforcement policy has skip_client_id_validation enabled.

W-19304854

Vulnerabilities detected by scanners are now fixed.

W-19095531, W-19308177

Flex Gateway now validates that there are no collisions when an API base path uses regex expressions.

W-19149269
## [](#1-9-5)1.9.5 **July 2, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.5. ### What’s New - Fluent Bit is now updated to version 3.2.10. ### Fixed Issues
Issue Resolution ID

Flex Gateway no longer ignores the json_date_format Fluent-Bit option.

W-18465012

Vulnerabilities detected by scanners are now fixed.

W-18820570

The Credential Injection OAuth 2.0 policy no longer fails if the expires_in attribute is a string.

W-18779819

The Schema Validation policy now recognizes encoded query params correctly.

W-18883397
## [](#1-9-4)1.9.4 **June 4, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.4. ### Fixed Issues
Issue Resolution ID

Deploying Flex Gateway with IPv6 disabled no longer causes an error.

W-18671361
## [](#1-9-3)1.9.3 **May 28, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.3. ### What’s New Flex Gateway now supports the Model Context Protocol (MCP) and the Agent2Agent (A2A) Protocol, enabling you to secure, manage, and govern agent interactions: - You can Publish Flex Gateway MCP and A2A Server instances. See [Publishing Omni Gateway Agent and Tool instances](https://docs.mulesoft.com/gateway/latest/agent-publish-apis). - Flex Gateway now includes MCP and A2A policies. Using these new policies, you can: - Protect agent interactions: Require that agents are invoked with appropriate authentication and authorization. - Enhance agent requests: Modify incoming prompts with additional context to improve server agent execution. - Provide centralized oversight: Enable frictionless agent visibility, logging, and insights for debugging and optimization. - Secure connections: Restrict MCP endpoint access to authorized agents only. - Simplify governance: Provide centralized visibility and control over all interactions. - Flex Gateway now includes these policies: A2A Policies: - **A2A Schema Validation**: Verify requests conform to the A2A schema. See [A2A Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-schema-validation). - **A2A Agent Card**: Proxy the agent through Flex Gateway by rewriting the agent card. See [A2A Agent Card Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-agent-card) - **A2A PII Detector**: Detect sensitive information in messages sent to and from agents. See [A2A Personally Identifiable Information (PII) Detector Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-pii-detector). - **A2A Prompt Decorator**: Modify prompt behavior by injecting custom prompts into requests. See [A2A Prompt Decorator Policy](https://docs.mulesoft.com/gateway/latest/policies-included-a2a-prompt-decorator). - **Server-Sent Events (SSE) Content Logging**: Log content sent by agents for audit and compliance needs. See [SSE Logging Policy](https://docs.mulesoft.com/gateway/latest/policies-included-sse-logging). MCP Policies: - **MCP Schema Validation**: Verify requests conform to the MCP schema. See [MCP Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-schema-validation). - **MCP Support**: Enable MCP support and enable Server-Sent Events (SSE). See [MCP Support Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-support). - **MCP Attribute-Based Access Control**: Allows you to control access to tools, resources, and prompts, based on Cedar expressions. See [MCP Attribute-Based Access Control Policy](https://docs.mulesoft.com/gateway/latest/policies-included-mcp-attribute-access-control). To learn more, see: - [Securing Agent Interactions with Omni Gateway](https://docs.mulesoft.com/gateway/latest/agent-secure). - [API Manager 2.x Release Notes](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes). ## [](#1-9-2)1.9.2 **May 12, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.2. ### Fixed Issues
Issue Resolution ID

The Flex Gateway 1.9.1 TLS context configuration deployment regression is now fixed.

W-18483362
## [](#1-9-1)1.9.1 **May 8, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.1. ### Fixed Issues
Issue Resolution ID

The onDelete event no longer causes a panic.

W-18368903

The Flex Gateway 1.9.0 ForwardProxy regression is now fixed.

W-18202000

The expires_in attribute in the OAuth credential injection policy is now correctly spelled.

W-18201673

Redis keys no longer collide if multiple Flex Gateways use the same Redis server.

W-18004157

Redeploying one API instance after updating a TLS Context now updates the context for APIs that share the TLS context.

W-17737710
## [](#1-9-0)1.9.0 **March 18, 2025** MuleSoft announces the release of Anypoint Flex Gateway 1.9.0. ### What’s New - Managed Flex Gateway on CloudHub 2.0 Flex Gateway now includes Managed Flex Gateway, a fully hosted version of Flex Gateway on CloudHub 2.0. Managed Flex Gateway provides high availability, autoscaling, less operational overhead, and regular automatic patches and upgrades. **Note:** To use Managed Flex Gateway, ensure the business group you want to deploy your gateway to has Managed Flex Gateway Resources. See [Deploy a Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up). - Flex Gateway Version Lifecycle MuleSoft introduces two new release channels, Edge and Long-term Support (LTS). Both release channels are available in all deployment models: Managed Flex Gateway, Self-Managed Flex Gateway Connected Mode, and Self-Managed Flex Gateway Local Mode. Edge releases will be available three times per year, and LTS releases will be available once a year. See [Omni Gateway Version Lifecycle](https://docs.mulesoft.com/gateway/latest/gateway-version-lifecycle). - Outbound Policy Support Outbound policies are policies applied to specific upstreams. To find the new outbound policies, see [Outbound Policies Directory](https://docs.mulesoft.com/gateway/latest/policies-outbound-directory). To apply outbound policies with UI, see [Applying Policies for Managed Omni Gateways and Connected Mode](https://docs.mulesoft.com/gateway/latest/gateway-secure-conn). To apply a policy to a service in Local Mode, see [Secure an API with an Automated Resource-Level Policy](https://docs.mulesoft.com/gateway/latest/local-secure-api-with-auto-policy). - Flex Local Configuration Cache Flex Gateway running in Connected mode can now cache its gateway configuration in shared storage for faster replica initiation, reduced startup times, and accelerated autoscaling. See [Configuring Omni Gateway Configuration Caching in Connected Mode](https://docs.mulesoft.com/gateway/latest/conn-replica-caching). - Flex Scalability Flex Gateway now supports up to 1,000 APIs per gateway. - API Timeouts Flex Gateway now provides the Stream Idle timeout, Response timeout, and Upstream Idle timeout. You can apply the timeouts to the gateway or individual APIs and upstreams as policies. To learn more, see: - [Deploy a Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up) - [Configuring Timeouts in Connected Mode](https://docs.mulesoft.com/gateway/latest/conn-timeout) - [Configuring Timeouts in Local Mode](https://docs.mulesoft.com/gateway/latest/local-timeout) ### Fixed Issues
Issue Resolution ID

When deployed to a Virtual Machine (VM), a Self-Managed Flex Gateway no longer fails to restart after an abrupt stop of the VM.

W-17640917
### Known Issues The [Flex Gateway is unable to send logs when a forward proxy is enabled known issue](https://help.salesforce.com/s/issue?language=en_US&id=a02Ka00000eNiqlIAC) was introduced in Flex Gateway 1.9.0. For more information, see [Salesforce Known Issues](https://help.salesforce.com/s/issues?language=en_US) and set the category to **Mulesoft Flex Gateway**. ## [](#see-also)See Also - [Troubleshooting Omni Gateway](https://docs.mulesoft.com/gateway/latest/troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) # Omni Gateway Release Notes Mulesoft Omni Gateway is an Envoy-based, ultrafast lightweight API gateway designed to manage and secure APIs running anywhere. Built to seamlessly integrate with DevOps and CI/CD workflows, Omni Gateway delivers the performance required for the most demanding applications and microservices while providing enterprise security and manageability across any environment. The following release notes are provided for Omni Gateway: - [Omni Gateway Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes) - [Model Proxy Release Notes](https://docs.mulesoft.com/jp/release-notes/gateway/model-proxy-release-notes) ## [](#policy-release-notes)Policy Release Notes The following release notes are provided for Omni Gateway Policies:
Category Policy

A2A

A2A Agent Card

A2A In-Task Authorization Code

A2A OAuth2 OBO Credential Injection

A2A PII Detector

A2A Prompt Decorator

A2A Quality Evaluation

A2A Schema Validation

A2A Token Based Rate Limit

A2A v1 Agent Card

A2A v1 Azure Content Guardrails

A2A v1 Bedrock Guardrails

A2A v1 PII Detector

A2A v1 Prompt Decorator

A2A v1 Schema Validation

A2A v1 to v0.3 Transcoder

A2A v1 Token Based Rate Limit

A2A and MCP

Agent Connection Telemetry

Compliance

Client ID Enforcement

Cross-Origin Resource Sharing (CORS)

GraphQL

GraphQL Access Control

GraphQL Introspection Control

GraphQL Operation Limits

GraphQL Schema Validation

GraphQL Static Query Complexity

LLM

Amazon Bedrock Guardrails

Azure Content Safety

CrowdStrike AIDR Guardrails

F5 Guardrails

Google Model Armor Guardrails

LLM PII Detection

LLM Token Based Rate Limit

Model Proxy Request Compression

Regex Prompt Guard

MCP

MCP Attribute-Based Access Control

MCP Global Access

MCP PII Detector

MCP Payload Optimization

MCP Tools Progressive Disclosure

MCP Schema Validation

MCP Support

MCP Tool Mapping

Quality of Service

Circuit Breaker

Health Check

HTTP Caching

Rate Limiting

Rate Limiting: SLA-based

Response Idle Timeout

Spike Control

Stream Idle Timeout

Traffic Management for Multiple Upstream Services

Traffic Management for Multiple Upstream Services (Weighted)

Upstream Idle Timeout

WebSocket Connection Limit

SSE

SSE Logging

Security

API Security-Identification Header

AWS Request Signature

Basic Authentication: LDAP

Basic Authentication: Simple

Credential Injection API Key

Credential Injection Basic Authentication

Credential Injection JWT Generation

Credential Injection OAuth 2.0

External Authorization

Injection Protection

IP Allowlist

IP Blocklist

JSON Threat Protection

JWT Validation

OAuth 2.0 OBO Credential Injection

OAuth 2.0 Protected Resource Metadata

OAuth 2.0 Token Introspection

OpenID Connect OAuth 2.0 Access Token Enforcement

Schema Validation

SOAP Schema Validation

Transport Layer Security (TLS) - Inbound

Transport Layer Security (TLS) - Outbound

WS-Security

XML Threat Protection

Transformation

AWS Lambda

DataWeave Body Transformation

DataWeave Headers Transformation

DataWeave Request Filter

External Processing

Header Injection

Header Removal

JavaScript Scripting

Troubleshooting

Message Logging

Outbound Message Logging

Tracing
## [](#see-also)See Also - [Omni Gateway Version Lifecycle](https://docs.mulesoft.com/gateway/latest/gateway-version-lifecycle) - [Omni Gateway Version Support](https://docs.mulesoft.com/gateway/latest/gateway-version-lifecycle#edge-lts) - [Omni Gateway Overview](https://docs.mulesoft.com/gateway/latest/) - [Known Issues](https://help.salesforce.com/s/issues) # OpenAI Connector Release Notes Anypoint Connector for OpenAI (OpenAI Connector) enables Mule applications to access the OpenAI API. Guide: [OpenAI Connector User Guide](https://docs.mulesoft.com/openai-connector/latest/) ## [](#1-1-2)1.1.2 **October 7, 2026** ### What’s New - OpenAI Connector now supports the OpenAI Responses API with the [**Create Response**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#CreateResponse), [**Retrieve Response**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#RetrieveResponse), [**Delete Response**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#DeleteResponse), and [**List Response Input Items**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#ListResponseInputItems) operations. - OpenAI Connector now supports the OpenAI Conversations API with the [**Create Conversation**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#CreateConversation), [**Retrieve Conversation**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#RetrieveConversation), [**Update Conversation**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#UpdateConversation), [**Delete Conversation**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#DeleteConversation), [**Create Conversation Items**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#CreateConversationItems), [**List Conversation Items**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#ListConversationItems), [**Retrieve Conversation Item**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#RetrieveConversationItem), and [**Delete Conversation Item**](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference#DeleteConversationItem) operations. - The deprecated OpenAI Assistants API operations, including its thread, message, and run operations, are removed: **Create Assistant**, **Get Assistant**, **List Assistants**, **Modify Assistant**, **Create Thread**, **Retrieve Thread**, **Modify Thread**, **Delete Thread**, **Create Thread And Run**, **Create Message**, **Retrieve Message**, **Modify Message**, and **List Message**. Before you upgrade, update any flows that use these operations, for example by migrating them to the Responses and Conversations operations. - The connection test now validates the connection by calling the OpenAI **List Models** endpoint instead of the Assistants endpoint. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
### Fixed Issues
Issue Resolution ID

The Create Chat Completion operation now processes responses from GPT-5 search models. These responses can omit logprobs, have null values for refusal or message content, and include annotations with URL citations. Previously, these responses didn’t match the expected response schema.

W-23981494
## [](#1-0-19)1.0.19 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-1)0.1.1 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **December 18, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/openai-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [OpenAI Connector User Guide](https://docs.mulesoft.com/openai-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [OpenAI Connector User Guide](https://docs.mulesoft.com/openai-connector/latest/) - [OpenAI Connector Reference](https://docs.mulesoft.com/openai-connector/latest/openai-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # OpenAM Access Token Enforcement ## [](#1-6-1)1.6.1 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-6-0)1.6.0 **February 07, 2024** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-5-1)1.5.1 **March 15, 2022** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed Issues - Error handling responses revised for JSON compliance. ## [](#1-5-0)1.5.0 **June 24, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Introduced the capability to configure timeouts when validating OAuth2 tokens for incoming requests. ## [](#1-4-0)1.4.0 **December 22, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Added support for policies to validate one or all of the scopes defined in API Manager. - Added OAS3 code snippet in the policy YAML. ## [](#1-3-3)1.3.3 **September 28, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-2)Fixed Issues - Because the `Content-Type` header of the JSON response from the validate endpoint had additional information, such as charset, the response returned was interpreted as String instead of JSON. The additional modifier is now disregarded. - Responses from the validation endpoint in which the value of the `expires_in` field was equal to 0 were not being parsed as an expired token. ## [](#1-3-2)1.3.2 **Apr 30, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in error handling. ### [](#fixed-issues-3)Fixed Issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-3-1)1.3.1 **December 18, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.0** ### [](#fixed-issues-4)Fixed Issues - Authorization entity attributes that contain non-primitive values were not correctly parsed. These values are now ignored. - An error occured when an object within a JSON object was treated as String type instead of JSON type. This issue is now resolved. - The `Fault` element in the WSDL APIs now includes the `Detail` element, with additional error details. ## [](#1-3-0)1.3.0 **Sep 4, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Introduced configuration flag to enable TLS validation on the Authorization Servers' certificates. - Added token rejection when the active field of the introspection endpoint response is 'false'. - Performance improvements. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ### [](#fixed-issues-5)Fixed Issues - Fixed expiration time field being mandatory. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Introduces support to encrypt sensitive information related to the policy. The runtime version needs to support encryption and needs to be properly configured. Encryption is supported since Mule Runtime v4.2.0. - The default configuration has been modified to avoid propagating or returning policy headers unless explicitly configured by checking the "Expose headers" option. - Performance improvements. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-4)1.1.4 **Feb 22, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **4.1.0** ### [](#fixed-issues-6)Fixed Issues - Fixed performance issue concerning scheduling. ## [](#1-1-3)1.1.3 **Jan 11, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Improved the RAML and OAS snippets. ## [](#1-1-2)1.1.2 **Oct 9, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **4.0.0** ### [](#fixed-issues-7)Fixed Issues - Fixed `ExpressionRuntimeException` error when a WSDL proxy receives an empty payload, or an invalid XML. ## [](#1-1-1)1.1.1 **Jun 27, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version **4.0.0** ### [](#fixed-issues-8)Fixed Issues - Fixed error preventing federated and client ID based policies to apply when a Security Manager is defined in the same app with a tracked endpoint. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-13)Minimum Mule Version **4.0.0** ### [](#fixed-issues-9)Fixed Issues - Fixed issue causing federated policies to lose query and URI parameters of the requester. ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-14)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [OpenAM OAuth 2.0 Token Enforcement Policy for Mule 4](#api-manager::openam-oauth-token-enforcement-policy.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # OpenAPI Specification Support Release Notes You can implement, deploy, and operate REST APIs using native OpenAPI Specification (OAS) formats in Anypoint Platform. ## [](#october-22-2026)October 22, 2026 Support for OAS 3.1 is now available across the API lifecycle in Anypoint Platform, including Anypoint Code Builder, Anypoint Exchange, APIkit for REST, API Manager, and API Experience Hub. OAS 3.1 is fully aligned with JSON Schema 2020-12, so you can describe your APIs with precise schemas that AI agents can consume without translation. ### [](#whats-new-in-oas-3-1)What’s New in OAS 3.1 OAS 3.1 introduces these capabilities: - Alignment with JSON Schema 2020-12, including `oneOf`, `anyOf`, `allOf`, `if`/`then`/`else`, `prefixItems`, and `const` - Nullable types declared natively with `type: ["string", "null"]` instead of `nullable: true` - Sibling properties alongside `$ref` - Numeric `exclusiveMinimum` and `exclusiveMaximum` values - SPDX license identifiers in `info.license.identifier` ### [](#oas-3-1-support-in-anypoint-platform)OAS 3.1 Support in Anypoint Platform
API Lifecycle Stage Product Additional Information

Design

Anypoint Code Builder

You can create, edit, and validate OAS 3.1 API specifications in YAML or JSON format, with inline validation and autocompletion for JSON Schema 2020-12 keywords. You can create OAS 3.1 API fragments and reference them with $ref. You can publish the specifications to Exchange directly from Anypoint Code Builder. OAS 3.1 support requires Anypoint Code Builder extension pack version 1.28.0 or later. To scaffold OAS 3.1 specifications, use Mule runtime 4.13 or later. For more information, see:

Catalog

Anypoint Exchange

You can upload and publish OAS 3.1 API specifications in YAML or JSON format and view the specification documentation. You can download OAS 3.1 assets in their original OAS version or as RAML. REST Connect generates Mule 4 connectors from OAS 3.1 API specifications. API Console renders OAS 3.1 schemas, and the mocking service validates requests against JSON Schema 2020-12. For more information, see:

Implement

APIkit for REST

You can scaffold Mule flows from OAS 3.1 API specifications. OAS 3.1 support requires APIkit for REST version 1.13.2 or later and Mule runtime 4.13 or later. The minimum Mule runtime version for other specifications doesn’t change. For more information, see APIkit Compatibility and APIkit for REST Scaffolding Reference.

Manage

API Manager

You can create API instances from OAS 3.1 API specifications for Mule Gateway and apply policies to them. For more information, see Adding a Mule Gateway API Instance.

Share

API Experience Hub

You can publish OAS 3.1 API specifications and view the specification documentation.
### [](#upgrade-oas-3-0-api-specifications-to-oas-3-1)Upgrade OAS 3.0 API Specifications to OAS 3.1 OAS 3.1 isn’t backward compatible with OAS 3.0. To upgrade an OAS 3.0 API specification to OAS 3.1, update constructs such as `nullable: true` to the JSON Schema 2020-12 equivalents. Your existing OAS 3.0 API specifications continue to work without changes. ### [](#limitations)Limitations - OAS 3.2 isn’t supported in this release. - Exchange doesn’t resolve dynamic references (`$dynamicRef` and `$dynamicAnchor`) in OAS 3.1 API specifications and doesn’t apply custom `$schema` dialects. For more information, see [Creating an Asset](https://docs.mulesoft.com/jp/exchange/to-create-an-asset). - Exchange doesn’t support importing and managing OAS 3.x components as Exchange dependencies inside a specification. - API Manager doesn’t support the OAS 3.1 callback feature. To work around this limitation, handle the callback outside of the Mule runtime engine domain or use an OAS 3.1 specification that doesn’t use callbacks. For more information, see [Adding a Mule Gateway API Instance](https://docs.mulesoft.com/jp/api-manager/latest/create-instance-task-mule#notes). - Omni Gateway doesn’t support OAS 3.1 API specifications in this release. - API Designer, Anypoint Studio, and API Community Manager don’t support OAS 3.1. To design OAS 3.1 API specifications, use Anypoint Code Builder. - REST Connect doesn’t support webhooks and or the `mutualTLS` security scheme in OAS 3.1 API specifications. ## [](#february-2-2021)February 2, 2021 Support for OAS 3.0 is included in API Designer, Anypoint Studio, Anypoint Exchange, API Manager, and Anypoint API Community Manager. You can catalog existing REST OAS 3.0 API specifications to share with partners, customers, and developers in the platform or in internal and external API communities. You can also manage and secure your OAS 3.0 APIs by applying appropriate policies. Additionally, if required, Anypoint Platform enables you to [convert](#convert_specs) an OAS 3.0 specification to RAML or OAS 2.0. ### [](#oas-3-0-support-in-anypoint-platform)OAS 3.0 Support in Anypoint Platform OAS 3.0 is supported by all the products in Anypoint Platform for the API lifecycle stages of design, publish, and manage.
API Lifecycle Stage Product OAS 3.0 Supported? Additional Information

Design

API Designer

Yes

You can create an OAS 3.0 API specification or import one from Anypoint Exchange.

Design

Anypoint Studio

Yes

You can import an OAS 3.0 API specification from Design Center as an editable API specification project in Studio. You can also create an API specification project from scratch in Studio and then synchronize it with Design Center.

Publish

Anypoint Exchange

Yes

You can download, and publish an OAS 3.0 specification and view the specification documentation in Exchange.

Publish

Anypoint API Community Manager

Yes

You can publish an OAS 3.0 specification and view the specification documentation.

Publish

REST Connect

Yes

API specifications are typically published from API Designer to Anypoint Exchange, except when a connector cannot be generated from the API specification. For such cases, an email is sent to the user, explaining the cause of the error.

Implement

Anypoint Studio

Yes

You can import your OAS 3.0 API specification from Exchange or Maven and write your flows.

Deploy

Mule runtime engine

Yes

OAS 3.0 is supported in Mule runtime engine.

Operate

API Manager

Yes

OAS 3.0 is supported in API Manager.
### [](#convert_specs)Convert Specifications The RAML and OAS specification standards have some differences. RAML has constructs such as resource types, traits, and overlays, which do not exist in OAS. Similarly, OAS 3.0 has constructs such as server-templating, links, and callbacks, which do not exist in RAML. The conversion between these standards is a best effort only. #### [](#convert-to-raml)Convert to RAML When you upload an OAS 3.0 specification to Anypoint Exchange, it automatically generates a RAML version. To convert an OAS 3.0 API specification to RAML in API Designer: 1. Import the OAS 3.0 API specification to API Designer. 2. Click the three dots next to the filename in the **Files** pane and select **Duplicate as…​**. 3. In the **Duplicate As** dialog, select **RAML**. 4. Set the root file of the project to the RAML version of the API specification. You can use the converted RAML specification in Anypoint Studio and API Manager. #### [](#convert-to-oas-2-0)Convert to OAS 2.0 Currently, Anypoint Platform does not support converting OAS 3.0 APIs to OAS 2.0. To convert an API from OAS 3.0 to OAS 2.0, download the OAS 3.0 specification and convert it using a third-party or open-source tool, such as APImatic Transformer. You can upload the converted OAS 2.0 specification to Exchange. Converting an asset in API Designer creates a new version of the asset in Exchange and does not create a second duplicate asset in Exchange. Downloading an asset from Exchange, converting it by using a third-party tool such as APIMatic Transformer, and uploading the converted asset back to Exchange does create a second duplicate asset in Exchange. It is best to have no duplicate assets. However, only third-party tools can convert OAS 3.0 to OAS 2.0. ### [](#api_designer)Work with OAS 3.0 APIs in API Designer API Designer supports these actions with OAS 3.0 APIs: - Create API specifications in OAS 3.0. When creating a new API-specification project, select **OAS 3.0** in the **Language** field. - Import OAS 3.0 specifications from Anypoint Exchange or from your filesystem: ![Options for importing](/mulesoft/current/ja-jp/release-notes/_images/platform/apid-import.png) Figure 1. How to import files into an API-specification project in API Designer 1. Click the gear icon in the top-right corner of the text editor. 2. Select either of these options: - Select **Import from Exchange** to see both of these lists: - A list of the API specifications that are available from the business organization that your user ID belongs to in Anypoint Platform - A list of the API specifications that are published by MuleSoft - Select **Import** to import an API specification from your local filesystem. - Develop and edit OAS 3.0 specifications. - View documentation that is included in OAS 3.0 API specifications. - Simulate calls to methods that are in OAS 3.0 API specifications by activating the mocking service. - Publish OAS 3.0 API specifications to Anypoint Exchange. ### [](#exchange)Work with OAS 3.0 APIs in Anypoint Exchange Exchange supports these actions with OAS 3.0 APIs: - Publish an existing OAS 3.0 API specification. On the **Publish a new asset** page, select **REST API - OAS** in the **Asset type** field. The API is now visible to Exchange users, and the users can explore the documentation and specification as with any other API, including the original OAS 3.0 specification and the generated RAML specification. - Download OAS 3.0 API specifications as RAML API specifications for scaffolding and implementation with third-party IDEs. ### [](#apim)Work with OAS 3.0 APIs in API Manager You can create OAS 3.0 APIs as the following types in API Manager: - Basic Endpoint for Mule applications (callbacks not supported) - Basic Endpoint for non-Mule applications - Endpoint with proxy (callbacks not supported) You can manage your OAS 3.0 APIs by creating versions and instances, and applying policies from API Manager. ### [](#community_manager)Work with OAS 3.0 APIs in API Community Manager Publish APIs written in OAS 3.0 and cataloged in the platform into your API communities. OAS 3.0 APIs are presented to your target audiences the same way as RAML and OAS 2.0 APIs, so that your audiences can discover, learn, and consume the APIs seamlessly, regardless of the specification language. ## [](#see-also)See Also - [Anypoint Exchange release notes](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes) - [Anypoint API Community Manager release notes](https://docs.mulesoft.com/jp/release-notes/api-community-manager/api-community-manager-release-notes) - [Anypoint API Designer release notes](https://docs.mulesoft.com/jp/release-notes/design-center/design-center-release-notes-api_specs) - [OpenAPI Initiative](https://www.openapis.org/) - [Known Issues](https://help.salesforce.com/s/issues) # OpenID Connect Access Token Enforcement ## [](#1-6-1)1.6.1 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-6-0)1.6.0 **February 07, 2024** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#0-9-0)0.9.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - Flex support for the Policy. ## [](#1-5-1)1.5.1 **March 15, 2022** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed Issues - Error handling responses revised for JSON compliance. ## [](#1-5-0)1.5.0 **June 24, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Introduced the capability to configure timeouts when validating OAuth2 tokens for incoming requests. ## [](#1-4-0)1.4.0 **December 22, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Added support for policies to validate one or all of the scopes defined in API Manager. - Added OAS3 code snippet in the policy YAML. ## [](#1-3-3)1.3.3 **September 28, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-2)Fixed Issues - Because the `Content-Type` header of the JSON response from the validate endpoint had additional information, such as charset, the response returned was interpreted as String instead of JSON. The additional modifier is now disregarded. - Responses from the validation endpoint in which the value of the `expires_in` field was equal to 0 were not being parsed as an expired token. ## [](#1-3-2)1.3.2 **Apr 30, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in error handling. ### [](#fixed-issues-3)Fixed Issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-3-1)1.3.1 **December 18, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.0** ### [](#fixed-issues-4)Fixed Issues - Authorization entity attributes that contain non-primitive values were not correctly parsed. These values are now ignored. - An error occured when an object within a JSON object was treated as String type instead of JSON type. This issue is now resolved. - The `Fault` element in the WSDL APIs now includes the `Detail` element, with additional error details. ## [](#1-3-0)1.3.0 **Sep 4, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Introduced configuration flag to enable TLS validation on the Authorization Servers' certificates. - Performance improvements. ### [](#fixed-issues-5)Fixed Issues - Fixed expiration time field being mandatory. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Introduces support to encrypt sensitive information related to the policy. The runtime version needs to support encryption and needs to be properly configured. Encryption is supported since Mule Runtime v4.2.0. - The default configuration has been modified to avoid propagating or returning policy headers unless explicitly configured by checking the "Expose headers" option. - Performance improvements. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-4)1.1.4 **Feb 22, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **4.1.0** ### [](#fixed-issues-6)Fixed Issues - Fixed performance issue concerning scheduling. ## [](#1-1-3)1.1.3 **Jan 11, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Improved the RAML and OAS snippets. ## [](#1-1-2)1.1.2 **Oct 9, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **4.0.0** ### [](#fixed-issues-7)Fixed Issues - Fixed `ExpressionRuntimeException` error when a WSDL proxy receives an empty payload, or an invalid XML. ## [](#1-1-1)1.1.1 **Jun 27, 2018** ### [](#fixed-issues-8)Fixed Issues - Fixed error preventing federated and client ID based policies to apply when a Security Manager is defined in the same app with a tracked endpoint. ### [](#minimum-mule-version-12)Minimum Mule Version **4.0.0** ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-13)Minimum Mule Version **4.0.0** ### [](#fixed-issues-9)Fixed Issues - Fixed issue causing federated policies to lose query and URI parameters of the requester. ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-14)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [OpenID Connect OAuth 2.0 Token Enforcement Policy for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-openid-token-enforcement) - [Known Issues](https://help.salesforce.com/s/issues) # OpenID Connect OAuth 2.0 Token Enforcement The OpenID Connect OAuth 2.0 Token Enforcement policy allows access only to authorized client applications. For configuration details, see [OpenID Connect OAuth 2.0 Token Enforcement Policy](https://docs.mulesoft.com/gateway/latest/policies-included-openid-token-enforcement). ## [](#september-2-2026)September 2, 2026 ### What’s New - The **Validated Token TTL** (`maxFederationExpirationTime`) and **Maximum Cache Entries** (`maxCacheSize`) settings are now exposed in Connected Mode, so you can control how long validated tokens are cached and how many are stored from the policy configuration. See [OpenID Connect OAuth 2.0 Token Enforcement Policy](https://docs.mulesoft.com/gateway/latest/policies-included-openid-token-enforcement). - OpenID Connect OAuth 2.0 Token Enforcement policy implementation version 1.5.0 is now supported by Omni Gateway. - OpenID Connect OAuth 2.0 Token Enforcement policy definition version 0.11.0 is now supported by Omni Gateway. ## [](#february-27-2025)February 27, 2025 ### What’s New - OpenID Connect OAuth 2.0 Token Enforcement policy implementation version 0.9.0 is now supported by Omni Gateway. - OpenID Connect OAuth 2.0 Token Enforcement policy definition version 0.9.0 is now supported by Omni Gateway. # OpenWeatherMap Connector Release Notes Anypoint Connector for OpenWeatherMap (OpenWeatherMap Connector) enables Mule applications to access the OpenWeatherMap API. Guide: [OpenWeatherMap Connector User Guide](https://docs.mulesoft.com/openweathermap-connector/latest/) ## [](#1-0-15)1.0.15 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-0-14)1.0.14 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#1-0-0)1.0.0 **December 11, 2025** ### What’s New This is a new connector. For more information, see the [OpenWeatherMap Connector User Guide](https://docs.mulesoft.com/openweathermap-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
## [](#see-also)See Also - [OpenWeatherMap Connector User Guide](https://docs.mulesoft.com/openweathermap-connector/latest/) - [OpenWeatherMap Connector Reference](https://docs.mulesoft.com/openweathermap-connector/latest/openweathermap-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Oracle E-Business Suite 12.2 Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Oracle E-Business Suite (EBS) 12.2 provides real-time connectivity to query and update Oracle EBS using REST web services. The connector has been developed for the Oracle EBS v12.2.x. Guide: [Oracle EBS 12.2 Connector User Guide](https://docs.mulesoft.com/jp/oracle-ebs-122-connector/latest/) ## [](#2-3-5)2.3.5 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8, 11, and 17
## [](#2-3-4)2.3.4 **August 12, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory errors no longer occur when downloading or installing the connector in Anypoint Studio.

W-23528247

The connector icon no longer fails to load in Anypoint Studio due to an unsupported style definition in the icon file.

W-23528247

Unexpected end of file from server errors no longer occur when the connector retrieves WADL and XSD metadata from Oracle EBS, including when the metadata references internal hostnames that the connector can’t reach.

W-22291338
## [](#2-3-3)2.3.3 **March 19, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.21.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The json library is upgraded to version 20251224.

  • The xercesImpl library is upgraded to version 2.12.2.

W-21506502
## [](#2-3-2)2.3.2 **February 4, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-beanutils library is upgraded to version 1.11.0.

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The commons-collections library is upgraded to version 20030418.083655.

W-20503824
## [](#2-3-1)2.3.1 **September 24, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer adds blank lines in the XML request when using Java 17.

W-16730584
## [](#2-3-0)2.3.0 **April 12, 2024** ### What’s New - This connector is now compatible with Java 17. - A new external library called **Javax Transaction Library (JTA)** is now required for the **Jms** and **Jms Url** connection types for Java 17. For Java 8 and 11, the external library is not required. ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8, 11, and 17
## [](#2-2-0)2.2.0 **July 6, 2023** ### What’s New - **Business events source** now includes the new **Filter message criteria** field, which filters business events based on SQL like criteria. ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8 and 11
## [](#2-1-6)2.1.6 **April 29, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The connector no longer incorrectly returns an ISG_SOAP_INVALID_HEADER error when testing the connection.

W-10795844
## [](#2-1-5)2.1.5 **March 29, 2021** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8 and 11
### [](#fixed-issues-6)Fixed Issues The client connection timeout value was overwritten by the default value (30 seconds) during runtime. The connector now uses the configured value, if available. (SE-16772) ## [](#2-1-4)2.1.4 **November 10, 2020** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8 and 11
### [](#fixed-issues-7)Fixed Issues The default value for the connection timeout is `0`, which some versions of Mule interpret as zero wait time before the connection times out. The connection timeout value of `0` now means that the wait for the connection timeout is indefinite. ## [](#2-1-3)2.1.3 **May 15, 2020** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later

Oracle EBS

12.2.x

OpenJDK

8 and 11
### [](#fixed-issues-8)Fixed Issues Fixed all reported security issues. (CONN-5977) ## [](#2-1-2)2.1.2 **August 7, 2019** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.0 and later

Oracle EBS

12.2.x

Java

8
### [](#fixed-issues-9)Fixed Issues - Business events now publish the correct media type response. - Business events that map messages using the **Transform Message** component are now fixed. ## [](#2-1-1)2.1.1 **March 20, 2019** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.0 and later

Oracle EBS

12.2.x

Java

8
### [](#fixed-issues-10)Fixed Issues - **Metadata** - Various fixes for the metadata resolving strategy were applied. It should now work as expected in all 12.2.x instances. ## [](#2-1-0)2.1.0 **December 14, 2018** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.0 and later

Oracle EBS

12.2.x

Java

8
### [](#features)Features - **Business Events** - Support for subscribing to Business Events was added. ### [](#fixed-issues-11)Fixed Issues - **WADL Alias** - Users needed to define the alias of deployed WADLs as their internal names, in lowercase. This new version fixes that and this is no longer required. ## [](#2-0-0)2.0.0 **January 12, 2018** Oracle E-Business Suite 12.2 connector is available on Mule 4.0.
Software Version

Mule

4.0 and later

Oracle EBS

12.2.x

Java

8
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Oracle EBS 12.1 Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Oracle E-Business Suite (Oracle EBS Connector) provides real-time connectivity to query and update Oracle EBS using web services. Oracle EBS Connector requires an Enterprise license. Guide: [Oracle EBS 12.1 Connector](https://docs.mulesoft.com/jp/oracle-ebs-connector/latest/) Reference: [Oracle EBS 12.1 Connector Reference](https://docs.mulesoft.com/jp/oracle-ebs-connector/latest/oracle-ebs-connector-reference) ## [](#5-3-5)5.3.5 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8, 11, and 17
## [](#5-3-4)5.3.4 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Oracle JDBC (ojdbc8) library is upgraded to version 19.32.0.0 to address reported security vulnerabilities.

W-23441618
## [](#5-3-3)5.3.3 **July 9, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.22.0.

  • The gson library is upgraded to version 2.14.0.

  • The stax2-api library is upgraded to version 4.3.0.

  • The ojdbc8 library is upgraded to version 19.31.0.0.

  • The jaxb-api library is upgraded to version 2.3.1.

  • The jaxb-core library is upgraded to version 2.3.0.1.

  • The jaxb-impl library is upgraded to version 2.3.9.

  • The rt library is upgraded to version 2.3.7.

W-23135027
## [](#5-3-2)5.3.2 **March 22, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.21.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The cryptacular library is upgraded to version 1.2.7.

  • The gson library is upgraded to version 2.13.2.

  • The stax2-api library is upgraded to version 4.2.2.

W-21506502
## [](#5-3-1)5.3.1 **February 28, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The cfx-core library is upgraded to version 3.5.11.

  • The commons-io library is upgraded to version 2.15.0.

  • The commons-lang library is upgraded to version 20030203.000129.

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The gson library is upgraded to version 2.12.0.

  • The spring-context library is upgraded to version 6.1.20.

  • The spring-core library is upgraded to version 5.3.39-spring-framework-5.3.45.

W-20633605
## [](#5-3-0)5.3.0 **October 22, 2024** ### What’s New - This connector is now compatible with Java 17. - A new external library called **Javax Transaction Library (JTA)** is now required for the **Jms Parameter Config** and **Jms Url Config** connection types for Java 17. For Java 8 and 11, the external library is not required. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8, 11, and 17
## [](#5-2-5)5.2.5 **June 6, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Business events source no longer fails to reconnect when there are connection issues.

W-10909180
## [](#5-2-4)5.2.4 **May 27, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the spring-beans package from org.springframework:spring-beans:5.3.18 to org.springframework:spring-beans:5.3.20.

W-11195294
## [](#5-2-3)5.2.3 **April 26, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Spring Context library from componentorg.springframework:spring-context:5.3.18.RELEASE to componentorg.springframework:spring-context:5.3.18.PROVIDED.

W-11001895
## [](#5-2-2)5.2.2 **April 7, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by updating the following libraries:

  • Spring Beans componentorg.springframework:spring-beans:5.2.6.RELEASE to componentorg.springframework:spring-beans:5.3.18

  • Spring Expression componentorg.springframework:spring-expression:5.2.6.RELEASE to componentorg.springframework:spring-expression:5.3.18

  • Spring Core componentorg.springframework:spring-core:5.2.6.RELEASE to componentorg.springframework:spring-core:5.3.18

W-10927726, W-10920504, W-10920480
## [](#5-2-1)5.2.1 **December 2, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The connector added an extra / to the FND_WEB_SEC service URL.

SE-23337

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9295
## [](#5-2-0)5.2.0 **April 14, 2021** ### [](#compatibility-12)Compatibility Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### [](#fixed-issues-10)Fixed Issues - Added a new flag (Fix url end point) that overrides the URL to use the URL of the WSDL file. (SE-19296) ## [](#5-1-5)5.1.5 **January 14, 2021** ### [](#compatibility-13)Compatibility Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### [](#fixed-issues-11)Fixed Issues - The connector did not send headers with some PLSQL operations, which resulted in an SAAJ0131 HeaderElements must be namespace qualified exception. (SE-19049) ## [](#5-1-4)5.1.4 **December 29, 2020** ### [](#compatibility-14)Compatibility Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### [](#fixed-issues-12)Fixed Issues - Fixed security vulnerabilities. (CONN-7300) ## [](#5-1-3)5.1.3 **November 18, 2020** ### [](#compatibility-15)Compatibility Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### [](#fixed-issues-13)Fixed Issues The JMS 'test connection' has been fixed. ## [](#5-1-2)5.1.2 **October 9, 2020** ### [](#compatibility-16)Compatibility Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### [](#new-features)New Features The PL/SQL connection idle timeout is now configurable. ### [](#fixed-issues-14)Fixed Issues The default value for the connection timeout is 0, which some versions of Mule interpret as zero wait time before the connection times out. This behavior has changed, so that a value of 0 now means the wait time for the connection timeout is indefinite. ## [](#5-1-1)5.1.1 **August 20, 2020** ### [](#compatibility-17)Compatibility The Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

OpenJDK

8 and 11
### [](#new-features-2)New Features The connector is now compatible with Java 11. ### [](#fixed-issues-15)Fixed Issues None. ## [](#5-1-0)5.1.0 **December 2, 2019** ### [](#compatibility-18)Compatibility The Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Oracle EBS

12.1.x

Java

8
### [](#new-features-3)New Features PL/SQL connection read timeout is now configurable. (CICD-37) ### [](#fixed-issues-16)Fixed Issues - Fixed error when the response of an operation contains a null field. (CONN-3284) - Removed connection exception when the connector is redeployed. (SE-13958) ## [](#5-0-0)5.0.0 **November 18, 2017** ### [](#compatibility-19)Compatibility The Oracle EBS Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

Oracle EBS

12.1.x

Java

8
### [](#new-features-4)New Features - Support for SuiteTalk API version 2017.1. - Added support for Mule 4. ### [](#fixed-issues-17)Fixed Issues - Business Events now return JSON. - XML Gateway Outbound metadata was fixed. It now declares its output as XML. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Oracle PeopleSoft Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Oracle PeopleSoft (PeopleSoft Connector) provides real-time connectivity to query and update any Oracle PeopleSoft module using a common integration interface known as the Component Interface. Guide: [Oracle PeopleSoft Connector](https://docs.mulesoft.com/jp/peoplesoft-connector/latest/) Reference: [Oracle PeopleSoft Connector Reference](https://docs.mulesoft.com/jp/peoplesoft-connector/latest/peoplesoft-connector-reference) ## [](#3-1-13)3.1.13 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04

OpenJDK

8, 11, and 17
## [](#3-1-12)3.1.12 **August 30, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The guava library is upgraded to version 33.6.0-jre.

  • The google-gson library is upgraded to version 2.14.0.

  • The byte-buddy library is upgraded to version 1.18.11-jdk5.

W-23657993
## [](#3-1-11)3.1.11 **February 1, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.19.0.

  • The commons-io library is upgraded to version 2.20.0.

  • The byte-buddy library is upgraded to version 1.17.7.

  • The google-gson library is upgraded to version 2.13.2.

W-20970559
## [](#3-1-10)3.1.10 **November 20, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The apache-common library is upgraded to version 3.18.0.

  • The google-guava library is upgraded to version 33.4.8-android.

  • The google-gson library is upgraded to version 2.12.0.

  • The commons-io library is upgraded to version 2.15.0.

W-19467714
## [](#3-1-9)3.1.9 **October 25, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04

OpenJDK

8, 11, and 17
## [](#3-1-8)3.1.8 **February 27, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04
### Fixed Issues
Issue Resolution ID

The connector no longer fails with an issue when used with Anypoint Studio 7.15.0.

W-14437636
## [](#3-1-7)3.1.7 **December 14, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04
### Fixed Issues
Issue ID

Made the product language more inclusive.

CONN-9477
## [](#3-1-6)3.1.6 **November 23, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04
### Fixed Issues
Issue ID

Fixed security vulnerabilities.

CONN-9294
## [](#3-1-5)3.1.5 **December 28, 2020** ### [](#compatibility-9)Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04
### [](#fixed-issues-7)Fixed Issues - Fixed security vulnerabilities. (CONN-7302) ## [](#3-1-4)3.1.4 **April 28, 2020** ### [](#compatibility-10)Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02 to 8.58.04
### [](#fixed-issues-8)Fixed Issues - Updated connector with new Munit dependencies. (CONN-4646) - Fixed security vulnerabilities. (CONN-5595) ### [](#features)Features The connector now supports PeopleTools 8.58. ## [](#3-1-3)3.1.3 **December 3, 2019** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02
### [](#features-2)Features The Update User Profile ID Type operation was added to update the `IdType` attribute of an existing user profile. (CONN-3809) ### [](#fixed-issues-9)Fixed Issues - Fixed `RouteControlProfile is required` error when a USER\_PROFILE is created. (CONN-3807) - Fixed `IDType is required` error when a USER\_PROFILE is created. (CONN-3808) ## [](#3-1-2)3.1.2 **November 7, 2019** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02
### [](#features-3)Features None ### [](#fixed-issues-10)Fixed Issues The `peoplesoft.psjoa` dependency scope was declared as provided, and was added as a shared library for the execution of MUnit. ## [](#3-1-1)3.1.1 **November 6, 2019** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02
### [](#features-4)Features You can now log the request and response with Oracle PeopleSoft. To implement, add a logger of the class `org.mule.modules.peoplesoft.extension.internal.service.PeopleSoftServiceImpl` at DEBUG level to the log4j2.xml file of the Mule app: ```xml ``` ### [](#fixed-issues-11)Fixed Issues None ## [](#3-1-0)3.1.0 **October 21, 2019** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later

PeopleSoft

9.2

PeopleTools

8.53.02
### [](#features-5)Features You can now customize the `dateTime` format for the connector. The default value is `MM/dd/yyyy K:mm:ssa`. ### [](#fixed-issues-12)Fixed Issues You can now use a different `dateTime` format than the default. This allows the connector to work when the format has been changed in the server. (SE-13355) ## [](#3-0-0)3.0.0 **November 18, 2017** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.0.0 and later

PeopleSoft

9.2

PeopleTools

8.53.02
### [](#features-6)Features This version is compatible with Mule 4.0.0. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Outbound Message Logging The Outbound Message Logging policy logs custom messages from outbound requests sent to upstream services, responses from upstream services, or information from other outbound policies applied to the same upstream service. For configuration details, see [Outbound Message Logging Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-message-logging). ## [](#september-2-2026)September 2, 2026 ### What’s New - The policy now supports data masking to detect and mask personally identifiable information (PII), such as email addresses, in log messages before they are written. You can select built-in PII types (Email, US SSN, Credit Card, and Phone Number) or add custom regex patterns. Request and response bodies are forwarded to the upstream service unchanged. - Outbound Message Logging policy implementation version x.x.x is now supported by Omni Gateway. - Outbound Message Logging policy definition version x.x.x is now supported by Omni Gateway. ## [](#february-24-2025)February 24, 2025 ### What’s New - Outbound Message Logging policy implementation version 1.2.1 is now supported by Omni Gateway. - Outbound Message Logging policy definition version 2.0.2 is now supported by Omni Gateway. # PagerDuty Connector Release Notes Anypoint Connector for PagerDuty (PagerDuty Connector) enables Mule applications to access the PagerDuty API. Guide: [PagerDuty Connector User Guide](https://docs.mulesoft.com/pagerduty-connector/latest/) ## [](#1-0-29)1.0.29 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17, 21
## [](#1-0-28)1.0.28 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.11.0 and later

OpenJDK

17, 21
## [](#1-0-0)1.0.0 **December 8, 2025** ### What’s New This is a new connector. For more information, see the [PagerDuty Connector User Guide](https://docs.mulesoft.com/pagerduty-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
## [](#see-also)See Also - [PagerDuty Connector User Guide](https://docs.mulesoft.com/pagerduty-connector/latest/) - [PagerDuty Connector Reference](https://docs.mulesoft.com/pagerduty-connector/latest/pagerduty-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # PingFederate Access Token Enforcement ## [](#1-6-1)1.6.1 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-6-0)1.6.0 **February 07, 2024** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-5-1)1.5.1 **March 15, 2022** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed Issues - Error handling responses revised for JSON compliance. ## [](#1-5-0)1.5.0 **June 24, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Introduced the capability to configure timeouts when validating OAuth2 tokens for incoming requests. ## [](#1-4-0)1.4.0 **December 22, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Added support for policies to validate one or all of the scopes defined in API Manager. - Added OAS3 code snippet in the policy YAML. ## [](#1-3-3)1.3.3 **September 28, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-2)Fixed Issues - Because the `Content-Type` header of the JSON response from the validate endpoint had additional information, such as charset, the response returned was interpreted as String instead of JSON. The additional modifier is now disregarded. - Responses from the validation endpoint in which the value of the `expires_in` field was equal to 0 were not being parsed as an expired token. ## [](#1-3-2)1.3.2 **Apr 30, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in error handling. ### [](#fixed-issues-3)Fixed Issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-3-1)1.3.1 **December 18, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.0** ### [](#fixed-issues-4)Fixed Issues - Authorization entity attributes that contain non-primitive values were not correctly parsed. These values are now ignored. - An error occured when an object within a JSON object was treated as String type instead of JSON type. This issue is now resolved. - The `Fault` element in the WSDL APIs now includes the `Detail` element, with additional error details. ## [](#1-3-0)1.3.0 **Sep 4, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Introduced configuration flag to enable TLS validation on the Authorization Servers' certificates. - Added token rejection when the active field of the introspection endpoint response is 'false'. - Performance improvements. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ### [](#fixed-issues-5)Fixed Issues - Fixed expiration time field being mandatory. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Introduces support to encrypt sensitive information related to the policy. The runtime version needs to support encryption and needs to be properly configured. - The default configuration has been modified to avoid propagating or returning policy headers unless explicitly configured by checking the "Expose headers" option. - Performance improvements. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-4)1.1.4 **Feb 22, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **4.1.0** ### [](#fixed-issues-6)Fixed Issues - Fixed performance issue concerning scheduling. ## [](#1-1-3)1.1.3 **Jan 11, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **4.0.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Improved the RAML and OAS snippets. ## [](#1-1-2)1.1.2 **Oct 9, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **4.0.0** ### [](#fixed-issues-7)Fixed Issues - Fixed `ExpressionRuntimeException` error when a WSDL proxy receives an empty payload, or an invalid XML. ## [](#1-1-1)1.1.1 **Jun 27, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version **4.0.0** ### [](#fixed-issues-8)Fixed Issues - Fixed error preventing federated and client ID based policies to apply when a Security Manager is defined in the same app with a tracked endpoint. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#fixed-issues-9)Fixed Issues - Fixed issue causing federated policies to lose query and URI parameters of the requester. ### [](#minimum-mule-version-13)Minimum Mule Version **4.0.0** ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-14)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [PingFederate OAuth 2.0 Token Enforcement Policy for Mule 4](#api-manager::policy-ping-federate.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # QuickBooks Online Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for QuickBooks Online (QuickBooks Online Connector) gives you access to the QuickBooks platform. This connector exposes operations provided by the QuickBooks Online API. See the [Intuit Developer page](https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/account) to learn more. Guide: [QuickBooks Online Connector User Guide](https://docs.mulesoft.com/jp/quickbooks-online-connector/latest/) ## [](#2-0-22)2.0.22 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

QuickBooks API

75
## [](#2-0-21)2.0.21 **August 27, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

QuickBooks API

75
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind library is upgraded to version 2.22.2.

  • The guava library is upgraded to version 33.7.1-jre.

  • The commons-io library is upgraded to version 2.22.0.

  • The org.json library is upgraded to version 20260814.

W-23441663
## [](#2-0-20)2.0.20 **July 7, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

QuickBooks API

75
### Fixed Issues
Issue Resolution ID

The connector now installs and loads correctly from Anypoint Exchange in Anypoint Studio. Previously, QuickBooks Online Connector 2.0.19 failed to load its extension model because a packaging regression omitted the required REST SDK common classes from the connector plugin.

W-23345186
## [](#v2-0-19)2.0.19 (Deprecated) **July 5, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

QuickBooks API

75
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind library is upgraded to version 2.22.0.

  • The guava library is upgraded to version 33.6.0-jre.

W-23286234
## [](#2-0-18)2.0.18 **May 15, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

QuickBooks API

75
### Fixed Issues
Issue Resolution ID

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21761959

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind library is upgraded to version 2.21.1.

  • The json library is upgraded to version 20251224.

  • The selenium-java library is upgraded to version 4.43.0.

  • The commons-io library is added at version 2.21.0.

  • The commons-lang3 library is added at version 3.20.0.

W-22024294
## [](#2-0-17)2.0.17 **August 24, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

QuickBooks API

75
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-18116231
## [](#2-0-16)2.0.16 **July 27, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

QuickBooks API

75
### Fixed Issues
Issue Resolution ID

QuickBooks Connector now uses QuickBooks API minor version 75.

W-18200610

The Content-Length header is now implicitly added to the Create upload operation. The Content-Length header is not required to be passed explicitly for larger payloads. The connector calculates the content length and passes it to the QuickBooks server.

W-19052353
## [](#2-0-15)2.0.15 **August 21, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#2-0-14)2.0.14 **November 16, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector no longer fails on startup due to an incorrect definition of expression annotation.

W-14494160
## [](#2-0-13)2.0.13 **May 30, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now includes an enhanced implementation for input parameters, such as better mapping when input parameters are not specified or are null.

W-13280661
## [](#2-0-12)2.0.12 **April 12, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12724854
## [](#2-0-11)2.0.11 **March 27, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

An exception with an unknown description no longer occurs when custom fields are not specified.

W-12724854
## [](#2-0-10)2.0.10 **February 21, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

A null pointer exception no longer occurs when custom fields are not specified.

W-12572592
## [](#2-0-9)2.0.9 **January 31, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12353522, W-12448131
## [](#2-0-8)2.0.8 **October 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853436
## [](#2-0-7)2.0.7 **September 6, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11388800
## [](#2-0-6)2.0.6 **May 5, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The State parameter is no longer incorrectly added twice in the OAuth dance URL in multi-tenancy environments. Refer to Quickbooks Connector Reference for more information about the State parameter.

W-10979996
## [](#2-0-5)2.0.5 **April 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920461
## [](#2-0-4)2.0.4 **February 3, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CONN-9891
## [](#2-0-3)2.0.3 **January 6, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9891
## [](#2-0-2)2.0.2 **January 3, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9664
## [](#2-0-1)2.0.1 **December 17, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9664
## [](#2-0-0)2.0.0 **October 6, 2021** ### Upgrade - Made the following changes to some operations: - Changed operation names - The **Get query** operation now makes an HTTP GET request instead of an HTTP POST request to the `/query` endpoint - The **Get invoice by invoice id** operation now makes an HTTP GET request instead of an HTTP POST request to the `/invoice/{invoiceId}` endpoint - The **Upload** operation now has the **File\_content\_0-Body** parameter, the **File\_content\_0-Filename** parameter, and the **File\_metadata\_0-Body** parameter - Removed the **Content type** parameter from all operations - Removed the **Accept** parameter from all operations - Added the **Body** parameter to some operations - Added sources For more information, refer to [Quickbooks Upgrade and Migrate](https://docs.mulesoft.com/jp/quickbooks-online-connector/latest/quickbooks-connector-upgrade-migrate). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#1-0-0)1.0.0 **February 11, 2021** New connector ### [](#compatibility-24)Compatibility QuickBooks Online Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features For a list of supported configurations and operations, see the QuickBooks Online Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Rate Limiting The Rate Limiting policy monitors access to an API by defining the maximum number of requests processed within a period of time For configuration details, see [Rate Limiting Policy](https://docs.mulesoft.com/gateway/latest/policies-included-rate-limiting). ## [](#april-09-2025)April 09, 2025 ### What’s New - Rate Limiting policy implementation version 1.2.3 is now supported by Omni Gateway. - Rate Limiting policy definition version 1.5.0 is now supported by Omni Gateway. # Rate Limiting ## [](#1-4-2)1.4.2 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-4-0)1.4.0 **September 28, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-3-7)1.3.7 **September 29, 2022** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed issues - Nodes no longer become unresponsive on a cluster scenario when persistence is enabled. ## [](#0-9-1)0.9.1 **June 27, 2022** ### [](#fixed-issues-2)Fixed Issues - Rate limit window is no longer limited to 24 days. ## [](#0-9-0)0.9.0 **May 17, 2022** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Flex support for the Policy. ## [](#1-3-6)1.3.6 **April 1, 2022** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-3)Fixed issues - Quota is now reset when editing tier configuration. ## [](#1-3-5)1.3.5 **June 16, 2021** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Improved error handling for connectivity issues in clusters. - Improved logging for errors. ## [](#1-3-4)1.3.4 **Apr 30, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. ### [](#fixed-issues-4)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). - Improved resiliency on cluster scenarios. - Improved logging information in locking, object store, and distributed mechanisms for better troubleshooting. - Several performance improvements are introduced in the algorithm of the Rate Limiting policy. ## [](#1-3-3)1.3.3 **November 26, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-5)Fixed Issues - Improved the algorithm to allow executing with small `throttling.distribution_percentage` values - Removed the warning message (WARN) in the application log when multiple asynchronous quota requests are executed in a distributed scenario - Fixed the `NullPointerException` error on the persistence scheduler when a distributed quota is temporarily unavailable ## [](#1-3-2)1.3.2 **November 13, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-6)Fixed Issues - Improved resiliency when the throttling algorithm is created under heavy load in clustering scenarios - Optimized the threading usage of the algorithm - Fixed the `NullPointerException` error on the persistence scheduler when counters are persisted due to a sudden surge in requests ## [](#1-3-1)1.3.1 **July 12, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Several performance improvements were introduced in this release. ## [](#1-3-0)1.3.0 **April 26, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Unless explicitly configured, by checking the "Expose headers" option, the policy header will not be propagated or returned. The default configuration is modified to support this behaviour. - Several performance improvements were introduced in this release. ### [](#fixed-issues-7)Fixed Issues - The persistence scheduler was losing quota in a Mule Cluster when the node’s clocks were out-of-sync. This error is now resolved. ## [](#1-2-3)1.2.3 **February 14, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-8)Fixed Issues - Fixed `NullPointerException` thrown when disposing policy in a Mule Cluster. ## [](#1-2-2)1.2.2 **October 17, 2018** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-9)Fixed Issues - Resolved the WSDL error response issue. - An object store error occurred when hitting the API concurrently. This error is now resolved. - Optimized throttling connector performance. - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. ## [](#1-2-1)1.2.1 **June 25, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Added 'violationCategory' in the YAML configuration file for Feedback Loop. ### [](#fixed-issues-10)Fixed Issues - If an extension set authentication using an Authentication object containing null properties, a `NullPointerException` error occurred. This error is now resolved. ## [](#1-2-0)1.2.0 **March 22, 2018** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-8)New Features and Enhancements - Parameterized throttling algorithm introduced for Mule 4. - Migrated pluggable Hazelcast to 4.x. ### [](#fixed-issues-11)Fixed Issues - The Rate Limiting policy was rejected from scheduler during high network traffic. This error is now resolved. ## [](#1-1-0)1.1.0 **January 25, 2018** ### [](#minimum-mule-version-13)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-9)New Features and Enhancements - Updated `WWW-Authenticate` header value from `mule-real` to `Client-ID-Enforcement`. - Reduced error-handling verbosity in templates. ### [](#fixed-issues-12)Fixed Issues - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. ## [](#1-0-0)1.0.0 **November 14, 2017** ### [](#minimum-mule-version-14)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [Rate Limit for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-rate-limiting) - [Known Issues](https://help.salesforce.com/s/issues) # Rate Limiting - SLA-based ## [](#1-3-2)1.3.2 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-3-0)1.3.0 **September 28, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-2-9)1.2.9 **September 29, 2022** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues)Fixed issues - Nodes no longer become unresponsive on a cluster scenario when persistence is enabled. ## [](#0-9-0)0.9.0 **May 17, 2022** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Flex support for the Policy. ## [](#1-2-8)1.2.8 **June 16, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Improved error handling for connectivity issues in clusters. - Improved logging for errors. - Corrected spelling issues and typos in policy’s code snippets. ## [](#1-2-7)1.2.7 **January 06, 2021** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Added OAS 3.0 code snippet in the policy YAML file. ## [](#1-2-6)1.2.6 **Apr 30, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compilant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. ### [](#fixed-issues-2)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-2-5)1.2.5 **March 13, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-3)Fixed issues - Improved logging information in locking, object store, and distributed mechanisms for better troubleshooting. - Added client name in the authentication attributes for the request to an API that has the Rate Limiting policy applied. - When request quota exceeds, authentication objects are now made accessible to the protected resource in the authentication store. - Several performance improvements were introduced in the algorithm of the Rate Limiting policy. ## [](#1-2-4)1.2.4 **November 26, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-4)Fixed issues - Improved algorithm to allow executing with small `throttling.distribution_percentage` values. - Removed the warning (WARN) message in application log when multiple async quota requests are executed in a distributed scenario. - Fixed the `NullPointerException` error on persistence scheduler when distributed quota is temporarily unavailable. ## [](#1-2-3)1.2.3 **November 13, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-5)Fixed issues - Improved resiliency when throttling algorithm is created under heavy load in clustering scenarios. - Optimized the threading usage of the algorithm. - Fixed the `NullPointerException` error on persistence scheduler when counters are persisted due to a sudden surge in requests. ## [](#1-2-2)1.2.2 **July 12, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Several performance improvements were introduced in this release. ### [](#fixed-issues-6)Fixed Issues - The persistence scheduler was losing quota in a Mule Cluster when the node’s clocks were out-of-sync. This error is not resolved. ## [](#1-2-1)1.2.1 **April 30, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-7)Fixed Issues - An error occurred when multiple client applications using one rate limiting algorithm were configured with the same SLA in Anypoint Platform. This error is now resolved. ## [](#1-2-0)1.2.0 **April 26, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Unless explicitly configured, by checking the "Expose headers" option, the policy header will not be propagated or returned. The default configuration is modified to support this behaviour. - Several performance improvements were introduced in this release. ## [](#1-1-3)1.1.3 **February 14, 2019** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-8)Fixed Issues - Fixed `NullPointerException` thrown when disposing policy in a Mule Cluster. ## [](#1-1-2)1.1.2 **January 10, 2019** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-8)New Features and Enhancements - Improved the RAML and OAS snippets. ## [](#1-1-1)1.1.1 **June 25, 2018** ### [](#minimum-mule-version-13)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-9)New Features and Enhancements - Migrated pluggable Hazelcast to 4.x. ### [](#fixed-issues-9)Fixed Issues - The Rate Limiting policy was rejected from scheduler during high network traffic. This error is now resolved. - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. - If an extension set authentication using an Authentication object containing null properties, a `NullPointerException` error occurred. This error is now resolved. ## [](#1-1-0)1.1.0 **January 25, 2018** ### [](#minimum-mule-version-14)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-10)New Features and Enhancements - Changed `WWW-Authenticate` header value from `mule-real` to `Client-ID-Enforcement`. - Reduced error-handling verbosity in templates. ### [](#fixed-issues-10)Fixed Issues - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. ## [](#1-0-0)1.0.0 **November 14, 2017** ### [](#minimum-mule-version-15)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [Rate Limit for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-rate-limiting) - [Known Issues](https://help.salesforce.com/s/issues) # Rate-limiting SLA The Rate-limiting SLA policy monitors access to an API by defining the maximum number of requests processed within a timespan, based on SLAs. For configuration details, see [Rate Limiting: SLA-Based Policy](https://docs.mulesoft.com/gateway/latest/policies-included-rate-limiting-sla). ## [](#april-09-2025)April 09, 2025 ### What’s New - Rate-limiting SLA policy implementation version 1.3.4 is now supported by Omni Gateway. - Rate-limiting SLA policy definition version 1.4.0 is now supported by Omni Gateway. # Redis Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Redis (Redis Connector) provides access to an open-source advanced key-value store that is often referred to as a data structure server because the keys can contain strings, hashes, lists, sets, and sorted sets. The Redis Connector offers complete support for its CRUD API. Guide: [Redis Connector](https://docs.mulesoft.com/redis-connector/latest/) Reference: [Redis Connector Reference](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference) ## [](#5-8-1)5.8.1 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

Redis

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x

OpenJDK

8, 11, and 17
## [](#5-8-0)5.8.0 **August 21, 2026** ### What’s New - The connector now includes the optional **Socket Timeout** and **Socket Time Unit** fields on the **Clustered**, **NonClustered**, and **Sentinel** connection types. Use these fields on the connection **Advanced** tab to set an independent read timeout for Redis command responses. Leave **Socket Timeout** empty to reuse **Connection Timeout** as the read timeout, which preserves the previous single-timeout behavior. For more information, see [Clustered](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#redis_clustered), [NonClustered](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#redis_nonclustered), and [Sentinel](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#redis_sentinel). - The Jedis client is upgraded to 7.5.3. ## Compatibility
Software Version

Mule

4.1.1 and later

Redis

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Clustered connection now applies pooling settings such as Max Total and Max Wait Millis to the cluster client, instead of ignoring those values.

W-23857760

REDIS:UNKNOWN errors no longer occur when the Set operation runs with If Not Exists set to true on a key that already exists. The operation now returns null and leaves the existing value and TTL unchanged.

W-23546930
## [](#5-7-0)5.7.0 **June 25, 2026** ### What’s New - The Jedis client is upgraded to 7.5.2. - The connector now includes the new **Username** field for all connection types to enable ACL authentication. For the **Sentinel** connection type, you can also configure the **Sentinel Username** field to set independent credentials for the sentinel nodes. Use these fields alongside the existing password fields to authenticate to Redis servers that require ACL credentials. ACL authentication requires Redis server 6.0 or later. Connections that omit a username continue to use password-only authentication. For more information, see [Redis Connector Reference](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference). ## Compatibility
Software Version

Mule

4.1.1 and later

Redis

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x

OpenJDK

8, 11, and 17
## [](#5-6-0)5.6.0 **May 4, 2026** ### What’s New - The connector now includes the new **TLS Configuration** and **Endpoint identification algorithm** fields for the **Sentinel** connection type. Use these fields to configure the communication protocol and select the algorithm used by clients to validate the server host name via TLS/SSL. ## Compatibility
Software Version

Mule

4.1.1 and later

Redis

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x

OpenJDK

8, 11, and 17
## [](#5-5-0)5.5.0 **February 19, 2026** ### What’s New - The connector is now compatible with Redis 8.x (Jedis 7.2.1). ## Compatibility
Software Version

Mule

4.1.1 and later

Redis

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly handles the Connection Time Unit value for the Clustered connection type so that the timeout is properly converted based on the specified time unit. Previously, the Connection Time Unit value was treated as milliseconds regardless of the configured unit, causing immediate connection failures.

W-21246508
## [](#5-4-7)5.4.7 **May 2, 2025** ## Compatibility
Software Version

Mule

4.1.1 and later

Redis Java Client

4.4.8

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, and 7.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Thread leaks no longer occur if invoked with the Set, Get, or Del operations using dynamic configuration.

W-17880825
## [](#5-4-6)5.4.6 **August 22, 2024** ### What’s New - This connector is now compatible with Redis server 7. ## Compatibility
Software Version

Mule

4.1.1 and later

Redis Java Client

4.4.8

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, and 7.x

OpenJDK

8, 11, and 17
## [](#5-4-5)5.4.5 **June 6, 2024** ## Compatibility
Software Version

Mule

4.1.1 and later

Redis Java Client

3.10.0

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Entry TTL field for RedisObjectStore is now transformed correctly from Long to Integer and from milliseconds to seconds. Additionally, Mule apps that use an Object Store entry TTL exceeding 24 days now observe that the TTL for new keys is set to the correct values.

W-14745160
## [](#5-4-4)5.4.4 **March 8, 2024** ## Compatibility
Software Version

Mule

4.1.1 and later

Redis Java Client

3.10.0

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The RedisObjectStore remove operation now correctly returns the stored value associated with the removed key, aligning with the Object Store interface specification. Previously, the connector erroneously returned a Long value representing the outcome of the underlying Del operation. This change can affect backward compatibility for custom Mule apps that rely on the previous behavior. However, it does not impact the Redis Connector or RedisObjectStore in Mule apps, as these usages are implemented correctly. The change affects direct usage of RedisObjectStore within custom applications.

W-14809749
## [](#5-4-3)5.4.3 **February 2, 2024** ### What’s New - This connector is now compatible with Java 17. ## Compatibility
Software Version

Mule

4.1.1 and later

Redis Java Client

3.10.0

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x

OpenJDK

8, 11, and 17
## [](#5-4-2)5.4.2 **June 14, 2023** ## Compatibility
Software Version

Mule

4.1.1 and later

Redis Java Client

3.10.0

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x

OpenJDK

8 and 11
### What’s New - Upgraded the Jedis client to version 3.10.0. ## [](#5-4-1)5.4.1 **February 18, 2021** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.1.1 and later

Redis Java Client

3.5.1

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x

OpenJDK

8 and 11
### [](#features)Features Upgraded the Jedis client to version 3.5.1. ## [](#5-4-0)5.4.0 **January 20, 2021** ### [](#compatibility-13)Compatibility
Software Version

Mule

4.1.1 and later

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x and 6.0.x

OpenJDK

8 and 11
### [](#features-2)Features - Added the Trim From List and Range From List operations. ## [](#5-3-0)5.3.0 **September 14, 2020** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x and 6.0.x

OpenJDK

8 and 11
### [](#features-3)Features - Added a sentinel connection provider that enables you to connect to a Redis instance that is configured to run in sentinel mode. ## [](#5-2-0)5.2.0 **August 3, 2020** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.1 and later

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x and 6.0.x
### [](#features-4)Features - Added support for TLS. - Upgraded the jedis client version to 3.3.0. ## [](#5-1-3)5.1.3 **June 29, 2020** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.1.1 and later

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, and 5.0.x
### [](#fixed-issues-6)Fixed Issues - When using the Set operation with TTL, the operation correctly set the specified value, but did not set the expire time. The connector now uses the Redis SET operation to set the expire time. (SE-16101) ## [](#5-1-2)5.1.2 **November 25, 2019** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.1.1 and later

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, and 5.0.x
### [](#fixed-issues-7)Fixed Issues - Fixed order issue for both ascending and descending orders in the [Get Range By Score](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#getRangeByScore) and [Get Range By Index](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#getRangeByIndex) operations. (SE-13883) ## [](#5-1-1)5.1.1 **June 6, 2019** ### [](#compatibility-18)Compatibility
Software Version

Mule

4.0 and later

Redis server

2.8.x, 3.0.x, 3.2.x, 4.x, and 5.0.x
### [](#fixed-issues-8)Fixed Issues - Redis connector 5.1.0 test connection always return successful. This issue was fixed by making sure the Redis instance being used is actually up and running by sending an ECHO command to it. (SE-11775) ## [](#5-1-0)5.1.0 **April 22, 2019** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.0 and later

Redis server

2.8.x, 3.0.x, and 3.2.x
### [](#features-5)Features Added support so that the Redis connector can be used as a custom object store in a Mule application. ## [](#5-0-0)5.0.0 **November 18, 2017** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.0 and later

Redis server

2.8.x, 3.0.x, and 3.2.x
### [](#features-6)Features Migrated to Mule 4.0.0 and later runtime. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Regex Prompt Guard Policy The Regex Prompt Guard Policy policy blocks LLM requests that match deny-list regex patterns. For configuration details, see [Regex Prompt Guard Policy](https://docs.mulesoft.com/gateway/latest/policies-included-regex-prompt-guard). ## [](#april-30-2026)April 30, 2026 ### What’s New - Regex Prompt Guard Policy policy implementation version 1.0.1 is now supported by Omni Gateway. ## [](#february-20-2026)February 20, 2026 ### What’s New - Regex Prompt Guard Policy policy definition version 1.0.0 is now supported by Omni Gateway. # Release Note Summary by Month [RSS Feed](https://docs.mulesoft.com/releases.rss "Add this URL to your RSS feed reader to stay up to date with MuleSoft releases.") ## [](#october-2026)October 2026 October 23 - [Apache Kafka Connector 4.15.4](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-15-4) - [Confluent Schema Registry Connector 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-2-4) - [Database Connector 1.16.6](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-16-6) - [Microsoft Dynamics NAV Connector 4.0.0](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4#4-0-0) - [Omni Gateway 1.14.4](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-14-4) - [Omni Gateway 1.13.8](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-13-8) - [Omni Gateway 1.12.12](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-12) - [Omni Gateway 1.9.19](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-19) - [ServiceNow Connector 6.18.8](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-8) - [X12 EDI Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/x12-edi-connector-release-notes-mule-4#3-0-0) October 22 - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#october-22-2026) - [OAuth2 Provider Module 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/oauth2-provider-release-notes#1-2-4) - [Object Store Connector 1.3.4](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4#1-3-4) - [OpenAPI Specification 3.1 Support](https://docs.mulesoft.com/jp/release-notes/platform/oas3#october-22-2026) - [ServiceNow Connector 6.18.7](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-7) - [Spring Module 2.2.0](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#2-2-0) October 21 - [Microsoft Dynamics GP Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-gp-connector-release-notes-mule-4#3-0-0) - [Neo4j Connector 3.0.9](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4#3-0-9) - [Neo4j Connector 4.0.4](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4#4-0-4) - [Omni Gateway 1.13.7](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-13-7) - [Omni Gateway 1.12.11](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-11) - [Omni Gateway 1.9.18](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-18) October 20 - [Omni Gateway 1.14.3](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-14-3) October 19 - [Mule Maven Plugin 4.10.3](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.3-release-notes) - [OAuth Module 1.1.30](https://docs.mulesoft.com/jp/release-notes/connector/oauth-module-release-notes#1-1-30) October 16 - [Amazon Lambda Connector 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-lambda-connector-release-notes-mule-4#1-2-4) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#october-16) - [MuleSoft WebCrawler Connector 1.0.2](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-webcrawler-connector-release-notes-mule-4#1-0-2) - [Zendesk Connector 1.1.14](https://docs.mulesoft.com/jp/release-notes/connector/zendesk-connector-release-notes-mule-4#1-1-14) - [Zuora AQuA Connector 1.0.19](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4#1-0-19) October 15 - [Amazon Kinesis Data Streams Connector 2.0.7](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-7) - [MongoDB Connector 6.4.3](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4#6-4-3) - [Mule runtime engine 4.13.1](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes) - [Mule runtime engine patch update 4.12.5](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes#october-2026) - [Mule runtime engine patch update 4.9.23](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#october-2026) - [Mule runtime engine patch update 4.6.36](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#october-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#october-15-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#october-15-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#october-15-2026) - [NetSuite Connector 12.0.3](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4#12-0-3) - [Salesforce Marketing Cloud Connector 5.0.5](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4#5-0-5) October 14 - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes#october-14-2026) - [Amazon DynamoDB Connector 1.6.8](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-8) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#october-14-2026) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#october-14-2026) - [Java Module 2.0.8](https://docs.mulesoft.com/jp/release-notes/connector/java-module#2-0-8) - [JMS Connector 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms#2-0-2) - [Twilio Connector 4.2.10](https://docs.mulesoft.com/jp/release-notes/connector/twilio-connector-release-notes-mule-4#4-2-10) - [Validation Module 2.0.12](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-validation#2-0-12) - [Web Service Consumer Connector 2.2.6](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-2-6) October 13 - [AMQP Connector 1.9.5](https://docs.mulesoft.com/jp/release-notes/connector/connector-amqp#1-9-5) - [Azure Event Hubs Connector 1.2.6](https://docs.mulesoft.com/jp/release-notes/connector/azure-event-hubs-connector-release-notes#1-2-6) - [Confluent Schema Registry Connector 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-2-3) - [IBM MQ Connector 2.0.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#2-0-1) - [Salesforce Connector 12.0.5](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#12-0-5) - [XML Module 1.4.8](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-xml#1-4-8) - [Zuora Connector 6.0.19](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4#6-0-19) October 9 - [APIkit for Mule 4 1.12.10](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.10-release-notes) - [APIkit for Mule 4 1.13.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.13.0-release-notes) - [Google BigQuery Connector 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector/google-bigquery-connector-release-notes-mule-4#1-3-0) - [SAP S/4HANA SOAP Connector 2.6.2](https://docs.mulesoft.com/jp/release-notes/connector/sap-s4-hana-soap-cloud-connector-release-notes-mule-4#2-6-2) October 8 - [Apache Hadoop Distributed File System Connector 6.0.33](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4#6-0-33) - [Apache Kafka Connector 4.15.3](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-15-3) - [FTPS Connector 2.1.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftps#2-1-3) - [Runtime Fabric 3.0.35601](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-3.x.x#3-0-35601) October 7 - [Azure Service Bus Connector 3.8.1](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-8-1) - [Mule Maven Plugin 4.10.2](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.2-release-notes) - [MUnit 3.7.5](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.5-release-notes) - [OpenAI Connector 1.1.2](https://docs.mulesoft.com/jp/release-notes/connector/openai-connector-release-notes-mule-4#1-1-2) - [Runtime Fabric 3.0.34501](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-3.x.x#3-0-34501) October 6 - [Adobe Marketo Connector 3.0.11](https://docs.mulesoft.com/jp/release-notes/connector/marketo-connector-release-notes-mule-4#3-0-11) - [API Experience Hub](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes#october-2026) - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#october-6-2026) - [DataWeave 2.13.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.13.0-release-notes) - [Mule runtime engine 4.13.0](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes) - [Mule runtime engine patch update 4.12.4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes#october-2026) - [Mule runtime engine patch update 4.9.22](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#october-2026) - [Mule runtime engine patch update 4.6.35](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#october-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#october-6-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#october-6-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#october-6-2026) - [MuleSoft Inference Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-inference-connector-release-notes-mule-4#1-2-1) - [MuleSoft Vectors Connector 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-vectors-connector-release-notes-mule-4#1-1-1) - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes#week-of-october-5-2026) - [ServiceNow Connector 6.18.6](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-6) - [Tracing Module 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector/tracing-module-release-notes#1-3-0) - [WS-Security Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/web-services-security-release-notes) October 5 - [Gmail Connector 1.1.3](https://docs.mulesoft.com/jp/release-notes/connector/gmail-connector-release-notes-mule-4#1-1-3) - [HL7 EDI Connector 5.0.0](https://docs.mulesoft.com/jp/release-notes/connector/hl7-connector-release-notes-mule-4#5-0-0) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#october-5) - [Microsoft Dynamics 365 Connector 2.6.9](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-365-connector-release-notes-mule-4#2-6-9) - [Microsoft OneDrive Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-onedrive-connector-release-notes-mule-4#1-2-1) - [Microsoft Teams Connector 1.1.6](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-teams-connector-release-notes-mule-4#1-1-6) - [SAP S/4HANA SOAP Connector 2.6.1](https://docs.mulesoft.com/jp/release-notes/connector/sap-s4-hana-soap-cloud-connector-release-notes-mule-4#2-6-1) - [Web Service Consumer Connector 2.2.5](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-2-5) October 4 - [Google Pub/Sub Connector 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector/google-pubsub-connector-release-notes-mule-4#1-3-0) October 2 - [Database Connector 1.16.5](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-16-5) - [MCP Connector 1.7.2](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-7-2) October 1 - [Amazon Kinesis Data Streams Connector 2.0.6](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-6) - [API Security-Identification Header Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/api-security-identification-header-release-notes) - [API Security-Identification Header Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/api-security-identification-header-policy-release-notes) - [APIkit for Mule 4 1.12.8](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.8-release-notes) - [APIkit for Mule 4 1.12.9](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.9-release-notes) - [APIkit for SOAP 2.1.6](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.6) - [Azure Cosmos DB Connector 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/azure-cosmos-db-connector-release-notes-mule-4#1-1-1) - [Basic Authentication: LDAP Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/basic-auth-ldap-release-notes) - [Basic Authentication - LDAP Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/ldap-policy-release-notes) - [Basic Authentication: Simple Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/basic-auth-simple-release-notes) - [Basic Authentication - Simple Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/http-basic-auth-release-notes) - [Client ID Enforcement Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/client-id-enforcement-release-notes) - [Client ID Enforcement Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/client-id-enforcement-release-notes) - [Cross-Origin Resource Sharing (CORS) Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/cors-release-notes) - [Cross-Origin Resource Sharing Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/cors-policy-release-notes) - [Header Injection Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/header-injection-release-notes) - [Header Injection Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/header-injection-release-notes) - [Header Removal Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/header-removal-release-notes) - [Header Removal Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/header-removal-release-notes) - [HTTP Caching Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/http-caching-release-notes) - [HTTP Caching Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/http-caching-release-notes) - [IP Allowlist Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/ip-allowlist-release-notes) - [IP Allowlist Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/ip-allowlist-policy-release-notes) - [IP Blocklist Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/ip-blocklist-release-notes) - [IP Blocklist Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/ip-blocklist-policy-release-notes) - [JSON Threat Protection Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/json-threat-protection-release-notes) - [JSON Threat Protection Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/json-threat-protection-release-notes) - [JWT Validation Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/jwt-validation-release-notes) - [JWT Validation Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/jwt-validation-release-notes) - [Message Logging Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/message-logging-release-notes) - [Message Logging Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/message-logging-release-notes) - [OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/mule-oauth-token-enforcement-policy-release-notes) - [Omni Gateway 1.14.2](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-14-2) - [OpenAM Access Token Enforcement Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/openam-oauth-token-enforcement-policy-release-notes) - [OpenID Connect OAuth 2.0 Access Token Enforcement Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/openid-token-enforcement-release-notes) - [OpenID Connect Access Token Enforcement Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/openid-connect-oauth-token-enforcement-policy-release-notes) - [PingFederate Access Token Enforcement Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/pingfederate-oauth-token-enforcement-policy-release-notes) - [Rate Limiting Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/rate-limiting-release-notes) - [Rate Limiting Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/rate-limit-policy-release-notes) - [Rate Limiting: SLA-based Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/rate-limiting-sla-release-notes) - [Rate Limiting - SLA-based Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/rate-limit-sla-release-notes) - [Spike Control Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/spike-control-release-notes) - [Spike Control Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/spike-control-release-notes) - [XML Threat Protection Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/xml-threat-protection-release-notes) - [XML Threat Protection Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/xml-threat-protection-release-notes) ## [](#september-2026)September 2026 September 30 - [Amazon EC2 Connector 3.0.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-ec2-connector-release-notes-mule-4#3-0-4) - [Amazon SQS Connector 5.12.12](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-12) - [EDIFACT EDI Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/edifact-edi-connector-release-notes#3-0-0) - [SAP Concur Connector 4.2.4](https://docs.mulesoft.com/jp/release-notes/connector/sap-concur-connector-release-notes-mule-4#4-2-4) - [TRADACOMS EDI Connector 3.0.1](https://docs.mulesoft.com/jp/release-notes/connector/tradacoms-edi-connector-release-notes-mule-4#3-0-1) September 29 - [Amazon DynamoDB Connector 1.6.7](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-7) - [Amazon S3 Connector 8.0.10](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-10) - [Apache Hadoop Distributed File System Connector 6.0.32](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4#6-0-32) - [Apache Kafka Connector 4.15.2](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-15-2) - [Confluent Schema Registry Connector 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-2-2) - [Neo4j Connector 3.0.8](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4#3-0-8) - [Snowflake Connector 1.4.2](https://docs.mulesoft.com/jp/release-notes/connector/snowflake-connector-release-notes-mule-4#1-4-2) September 28 - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#september-28-2026) - [Salesforce Einstein Analytics Connector 4.0.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-analytics-connector-release-notes-mule-4#4-0-0) September 26 - [Salesforce Marketing Cloud Connector 5.0.4](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4#5-0-4) September 25 - [Amazon S3 Connector 8.0.9](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-9) - [Amazon SNS Connector 4.8.5](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4#4-8-5) - [Amazon SQS Connector 5.12.11](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-11) - [JSON Module 2.5.11](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-11) - [Omni Gateway 1.14.1](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-14-1) - [Omni Gateway 1.12.10](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-10) - [RosettaNet Connector 3.1.0](https://docs.mulesoft.com/jp/release-notes/connector/rosettanet-connector-release-notes-mule-4#3-1-0) - [RPA Builder 6.7.26](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.26-release-notes) - [Salesforce Composite Connector 3.1.4](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#3-1-4) - [Salesforce Marketing Cloud REST Connector 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-marketing-cloud-rest-connector-release-notes-mule-4#1-2-3) - [SAP Connector 5.9.14](https://docs.mulesoft.com/jp/release-notes/connector/sap-connector-release-notes-mule-4#5-9-14) - [Scripting Module 2.1.4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-scripting#2-1-4) September 24 - [APIkit for Mule 4 1.12.7](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.7-release-notes) - [Einstein AI Connector 2.0.0](https://docs.mulesoft.com/jp/release-notes/connector/einstein-ai-connector-release-notes-mule-4#2-0-0) - [JMS Connector 2.0.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms#2-0-1) - [MuleSoft AI Chain Connector 2.0.0](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-ai-chain-connector-release-notes-mule-4#2-0-0) - [OAuth Module 1.1.29](https://docs.mulesoft.com/jp/release-notes/connector/oauth-module-release-notes#1-1-29) - [Omni Gateway 1.13.6](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-13-6) - [Omni Gateway 1.9.17](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-17) - [Runtime Manager Agent 2.7.20](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20) - [Runtime Manager Agent 2.8.5](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) - [Salesforce Data Cloud Connector 1.5.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-data-cloud-connector-release-notes-mule-4#1-5-1) September 23 - [Microsoft SharePoint Connector 3.10.0](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-10-0) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#september-23-2026) - [Mule Upgrade Tool 1.1.9](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.9-release-notes) - [Salesforce Connector 12.0.4](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#12-0-4) September 22 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#september-22-2026) - [APIkit for OData 4 1.6.2](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.6.2) - [Microsoft Power BI Connector 1.0.7](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-power-bi-connector-release-notes-mule-4#1-0-7) - [NetSuite REST Connector 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-rest-connector-release-notes-mule-4#1-0-1) September 21 - [Aggregators Module 1.1.6](https://docs.mulesoft.com/jp/release-notes/connector/aggregators-module-release-notes#1-1-6) - [Amazon SQS Connector 5.12.10](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-10) - [APIkit for SOAP 2.1.5](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.5) - [Azure Event Hubs Connector 1.2.5](https://docs.mulesoft.com/jp/release-notes/connector/azure-event-hubs-connector-release-notes#1-2-5) - [Azure Key Vault Connector 1.2.7](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4#1-2-7) - [Cassandra Connector 5.0.0](https://docs.mulesoft.com/jp/release-notes/connector/cassandra-connector-release-notes-mule-4#5-0-0) - [Connector Builder 1.5.2](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes#1-5-2) - [IBM CICS Transaction Gateway Connector 3.0.2](https://docs.mulesoft.com/jp/release-notes/connector/ibm-ctg-connector-release-notes-mule-4#3-0-2) - [JSON Module 2.5.10](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-10) - [LDAP Connector 3.7.3](https://docs.mulesoft.com/jp/release-notes/connector/ldap-connector-release-notes-mule-4#3-7-3) - [Microsoft Dynamics 365 Business Central Connector 1.0.7](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-365-business-central-connector-release-notes-mule-4#1-0-7) - [Microsoft Dynamics CRM Connector 3.2.17](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-crm-connector-release-notes-mule-4#3-2-17) - [Microsoft Dynamics GP Connector 2.1.9](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-gp-connector-release-notes-mule-4#2-1-9) - [Microsoft Dynamics NAV Connector 3.0.2](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4#3-0-2) - [NetSuite Connector 12.0.2](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4#12-0-2) - [NetSuite OpenAir Connector 2.0.14](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-openair-connector-release-notes-mule-4#2-0-14) - [NetSuite Restlet Connector 1.0.11](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-restlet-connector-release-notes-mule-4#1-0-11) - [Redis Connector 5.8.1](https://docs.mulesoft.com/jp/release-notes/connector/redis-connector-release-notes-mule-4#5-8-1) - [Salesforce Connector 12.0.3](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#12-0-3) - [Salesforce Pub/Sub Connector 1.4.2](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4#1-4-2) - [SFTP Connector 2.7.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-7-4) - [WebSockets Connector 1.0.5](https://docs.mulesoft.com/jp/release-notes/connector/websockets-connector-release-notes-mule-4#1-0-5) September 20 - [MuleSoft WebCrawler Connector 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-webcrawler-connector-release-notes-mule-4#1-0-1) - [Siebel Connector 4.0.12](https://docs.mulesoft.com/jp/release-notes/connector/siebel-connector-release-notes-mule-4#4-0-12) September 18 - [AMQP Connector 1.9.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-amqp#1-9-4) - [Azure Key Vault Properties Provider 2.2.3](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-2-3) - [Azure Service Bus Management Connector 1.0.5](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-mgmt-connector-release-notes-mule-4#1-0-5) - [MCP Connector 1.7.1](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-7-1) - [Microsoft .NET Connector 3.1.14](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dotnet-connector-release-notes-mule-4#3-1-14) - [Microsoft Dynamics AX 2012 Connector 2.0.7](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-ax-connector-release-notes-mule-4#2-0-7) - [Microsoft MSMQ Connector 2.1.3](https://docs.mulesoft.com/jp/release-notes/connector/msmq-connector-release-notes-mule-4#2-1-3) - [Microsoft Service Bus Connector 2.2.10](https://docs.mulesoft.com/jp/release-notes/connector/ms-service-bus-connector-release-notes-mule-4#2-2-10) - [Microsoft Windows PowerShell Connector 2.1.5](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-powershell-connector-release-notes-mule-4#2-1-5) - [Neo4j Connector 4.0.3](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4#4-0-3) - [Sockets Connector 1.2.10](https://docs.mulesoft.com/jp/release-notes/connector/connector-sockets#1-2-10) September 7 - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#september-7-2026) - [gRPC Connector 1.0.4](https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4#1-0-4) September 4 - [Amazon Bedrock Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-bedrock-connector-release-notes-mule-4#1-1-0) - [Amazon DynamoDB Connector 1.6.6](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-6) - [Amazon EC2 Connector 3.0.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-ec2-connector-release-notes-mule-4#3-0-3) - [Amazon Kinesis Data Streams Connector 2.0.5](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-5) - [Amazon Lambda Connector 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-lambda-connector-release-notes-mule-4#1-2-3) - [Amazon Redshift Connector 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-redshift-connector-release-notes-mule-4#1-2-4) - [Amazon S3 Connector 8.0.8](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-8) - [Amazon Secrets Manager Properties Provider 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-secrets-manager-properties-provider-release-notes-mule-4#1-2-1) - [Amazon SNS Connector 4.8.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4#4-8-4) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#september-4-2026) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#september-2026) - [Apache Hadoop Distributed File System Connector 6.0.31](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4#6-0-31) - [Apache Kafka Connector 4.15.1](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-15-1) - [Asana Connector 1.0.10](https://docs.mulesoft.com/jp/release-notes/connector/asana-connector-release-notes-mule-4#1-0-10) - [Azure Data Lake Storage Connector 1.0.11](https://docs.mulesoft.com/jp/release-notes/connector/azure-data-lake-connector-release-notes-mule-4#1-0-11) - [Box Connector 5.3.4](https://docs.mulesoft.com/jp/release-notes/connector/box-connector-release-notes-mule-4#5-3-4) - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#september-4-2026) - [DocuSign Connector 1.1.5](https://docs.mulesoft.com/jp/release-notes/connector/docusign-connector-release-notes-mule-4#1-1-5) - [Dropbox Connector 1.0.13](https://docs.mulesoft.com/jp/release-notes/connector/dropbox-connector-release-notes-mule-4#1-0-13) - [File Connector 1.5.7](https://docs.mulesoft.com/jp/release-notes/connector/connector-file#1-5-7) - [Intercom Connector 1.0.7](https://docs.mulesoft.com/jp/release-notes/connector/intercom-connector-release-notes-mule-4#1-0-7) - [Java Module 1.2.19](https://docs.mulesoft.com/jp/release-notes/connector/java-module#1-2-19) - [Java Module 2.0.7](https://docs.mulesoft.com/jp/release-notes/connector/java-module#2-0-7) - [JSON Module 2.5.9](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-9) - [Mailchimp Marketing Connector 1.0.9](https://docs.mulesoft.com/jp/release-notes/connector/mailchimp-marketing-connector-release-notes-mule-4#1-0-9) - [Mule runtime engine patch update 4.12.3](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes#september-2026) - [Mule runtime engine patch update 4.9.21](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#september-2026) - [Mule runtime engine patch update 4.6.34](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#september-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#september-4-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#september-4-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#september-4-2026) - [Oracle EBS 12.1 Connector 5.3.5](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-connector-release-notes-mule-4#5-3-5) - [Oracle EBS 12.2 Connector 2.3.5](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-122-connector-release-notes-mule-4#2-3-5) - [Oracle PeopleSoft Connector 3.1.13](https://docs.mulesoft.com/jp/release-notes/connector/peoplesoft-connector-release-notes-mule-4#3-1-13) - [QuickBooks Online Connector 2.0.22](https://docs.mulesoft.com/jp/release-notes/connector/quickbooks-online-connector-release-notes-mule-4#2-0-22) - [Salesforce Composite Connector 3.1.3](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#3-1-3) - [SAP S/4HANA OData Connector 2.9.6](https://docs.mulesoft.com/jp/release-notes/connector/sap-s4-hana-connector-release-notes-mule-4#2-9-6) - [SAP SuccessFactors Connector 5.0.4](https://docs.mulesoft.com/jp/release-notes/connector/sap-successfactors-connector-release-notes-mule-4#5-0-4) - [Scripting Module 2.1.3](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-scripting#2-1-3) - [Shopify Connector 1.1.14](https://docs.mulesoft.com/jp/release-notes/connector/shopify-connector-release-notes-mule-4#1-1-14) - [Slack Connector 2.0.3](https://docs.mulesoft.com/jp/release-notes/connector/slack-connector-release-notes-mule-4#2-0-3) - [Smartsheet Connector 1.2.9](https://docs.mulesoft.com/jp/release-notes/connector/smartsheet-connector-release-notes-mule-4#1-2-9) - [Stripe Connector 1.0.19](https://docs.mulesoft.com/jp/release-notes/connector/stripe-connector-release-notes-mule-4#1-0-19) - [Tableau Connector 1.1.6](https://docs.mulesoft.com/jp/release-notes/connector/tableau-specialist-connector-release-notes-mule-4#1-1-6) - [Trello Connector 1.2.6](https://docs.mulesoft.com/jp/release-notes/connector/trello-connector-release-notes-mule-4#1-2-6) - [Veeva Vault Connector 1.5.7](https://docs.mulesoft.com/jp/release-notes/connector/veeva-vault-release-notes-mule-4#1-5-7) - [VM Connector 2.0.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-vm#2-0-3) - [Zendesk Connector 1.1.13](https://docs.mulesoft.com/jp/release-notes/connector/zendesk-connector-release-notes-mule-4#1-1-13) - [Zoom Connector 1.0.8](https://docs.mulesoft.com/jp/release-notes/connector/zoom-connector-release-notes-mule-4#1-0-8) - [Zuora AQuA Connector 1.0.18](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4#1-0-18) - [Zuora Connector 6.0.18](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4#6-0-18) September 3 - [AMQP Connector 1.9.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-amqp#1-9-3) - [Compression Module 2.2.9](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-compression#2-2-9) - [Confluent Schema Registry Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-2-1) - [Cryptography Module 2.2.2](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes#2-2-2) - [Database Connector 1.16.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-16-4) - [JMS Connector 1.10.6](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms#1-10-6) - [MongoDB Connector 6.4.2](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4#6-4-2) - [MQTT Connector 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/mqtt3-connector-release-notes#1-1-1) - [Neo4j Connector 4.0.2](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4#4-0-2) - [Object Store Connector 1.3.3](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4#1-3-3) - [Secure Configuration Properties Extension 1.3.2](https://docs.mulesoft.com/jp/release-notes/mule-runtime/secure-properties#1-3-2) - [Spring Module 1.5.3](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#1-5-3) - [Spring Module 2.1.4](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#2-1-4) - [Validation Module 2.0.11](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-validation#2-0-11) - [XML Module 1.4.7](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-xml#1-4-7) September 2 - [Amazon Secrets Manager Properties Provider 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-secrets-manager-properties-provider-release-notes-mule-4#1-2-0) - [Blackboard Connector 0.2.0](https://docs.mulesoft.com/jp/release-notes/connector/blackboard-connector-release-notes-mule-4#0-2-0) - [Canvas Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/canvas-connector-release-notes-mule-4#1-1-0) - [D2L Brightspace Connector 0.1.1](https://docs.mulesoft.com/jp/release-notes/connector/d2l-brightspace-connector-release-notes-mule-4#0-1-1) - [D2L Brightspace Connector 0.1.2](https://docs.mulesoft.com/jp/release-notes/connector/d2l-brightspace-connector-release-notes-mule-4#0-1-2) - [MCP Schema Validation Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/mcp-schema-validation-release-notes#september-2-2026) September 1 - [Bird Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/bird-connector-release-notes-mule-4#1-1-0) - [MUnit 3.7.4](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.4-release-notes) ## [](#august-2026)August 2026 August 31 - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes#august-31-2026) - [APIkit for Mule 4 1.12.6](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.6-release-notes) - [Azure Cosmos DB Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/azure-cosmos-db-connector-release-notes-mule-4#1-1-0) - [Azure Key Vault Properties Provider 2.2.2](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-2-2) - [Coda Connector 0.1.23](https://docs.mulesoft.com/jp/release-notes/connector/coda-connector-release-notes-mule-4#0-1-23) - [DHL Tracking Connector 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/dhl-tracking-connector-release-notes-mule-4#1-1-1) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#august-31-2026) - [Google Gemini Connector 1.0.21](https://docs.mulesoft.com/jp/release-notes/connector/google-gemini-connector-release-notes-mule-4#1-0-21) - [gRPC Connector 1.0.3](https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4#1-0-3) - [Microsoft Power BI Connector 1.0.6](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-power-bi-connector-release-notes-mule-4#1-0-6) - [Model Proxy](https://docs.mulesoft.com/jp/release-notes/gateway/model-proxy-release-notes#august-31-2026) - [Moodle Connector 0.1.3](https://docs.mulesoft.com/jp/release-notes/connector/moodle-connector-release-notes-mule-4#0-1-3) - [MuleSoft MCP Server](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-aug31-26) - [NetSuite Connector 12.0.1](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4#12-0-1) - [Notion Connector 1.0.22](https://docs.mulesoft.com/jp/release-notes/connector/notion-connector-release-notes-mule-4#1-0-22) - [OpenAI Connector 1.0.19](https://docs.mulesoft.com/jp/release-notes/connector/openai-connector-release-notes-mule-4#1-0-19) - [OpenWeatherMap Connector 1.0.15](https://docs.mulesoft.com/jp/release-notes/connector/openweathermap-connector-release-notes-mule-4#1-0-15) - [PagerDuty Connector 1.0.29](https://docs.mulesoft.com/jp/release-notes/connector/pagerduty-connector-release-notes-mule-4#1-0-29) - [SAP S/4HANA OData Connector 2.9.5](https://docs.mulesoft.com/jp/release-notes/connector/sap-s4-hana-connector-release-notes-mule-4#2-9-5) - [Shippo Connector 0.1.24](https://docs.mulesoft.com/jp/release-notes/connector/shippo-connector-release-notes-mule-4#0-1-24) - [ShipStation Connector 1.0.7](https://docs.mulesoft.com/jp/release-notes/connector/shipstation-connector-release-notes-mule-4#1-0-7) - [Smartsheet Connector 1.2.8](https://docs.mulesoft.com/jp/release-notes/connector/smartsheet-connector-release-notes-mule-4#1-2-8) - [Teamwork Connector 0.1.28](https://docs.mulesoft.com/jp/release-notes/connector/teamwork-connector-release-notes-mule-4#0-1-28) - [TRADACOMS EDI Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/tradacoms-edi-connector-release-notes-mule-4#3-0-0) - [Workable Connector 0.1.15](https://docs.mulesoft.com/jp/release-notes/connector/workable-connector-release-notes-mule-4#0-1-15) August 30 - [LDAP Connector 3.7.2](https://docs.mulesoft.com/jp/release-notes/connector/ldap-connector-release-notes-mule-4#3-7-2) - [NetSuite REST Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-rest-connector-release-notes-mule-4#1-0-0) - [Oracle PeopleSoft Connector 3.1.12](https://docs.mulesoft.com/jp/release-notes/connector/peoplesoft-connector-release-notes-mule-4#3-1-12) - [Siebel Connector 4.0.11](https://docs.mulesoft.com/jp/release-notes/connector/siebel-connector-release-notes-mule-4#4-0-11) August 28 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#august-28-2026) - [Azure Service Bus Management Connector 1.0.4](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-mgmt-connector-release-notes-mule-4#1-0-4) - [Box Connector 5.3.3](https://docs.mulesoft.com/jp/release-notes/connector/box-connector-release-notes-mule-4#5-3-3) - [Confluent Schema Registry Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-2-0) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#august-28-2026) - [IBM CTG Connector 3.0.1](https://docs.mulesoft.com/jp/release-notes/connector/ibm-ctg-connector-release-notes-mule-4#3-0-1) - [Microsoft Dynamics 365 Business Central Connector 1.0.6](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-365-business-central-connector-release-notes-mule-4#1-0-6) - [Microsoft SharePoint Connector 3.9.1](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-9-1) - [Microsoft Windows PowerShell Connector 2.1.4](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-powershell-connector-release-notes-mule-4#2-1-4) - [Salesforce Marketing Cloud REST Connector 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-marketing-cloud-rest-connector-release-notes-mule-4#1-2-2) August 27 - [APIkit for SOAP 2.1.4](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.4) - [Dropbox Connector 1.0.12](https://docs.mulesoft.com/jp/release-notes/connector/dropbox-connector-release-notes-mule-4#1-0-12) - [Model Proxy Request Compression Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/llm-proxy-request-compression-release-notes) - [Omni Gateway 1.13.5](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-13-5) - [QuickBooks Online Connector 2.0.21](https://docs.mulesoft.com/jp/release-notes/connector/quickbooks-online-connector-release-notes-mule-4#2-0-21) - [SAP SuccessFactors Connector 5.0.3](https://docs.mulesoft.com/jp/release-notes/connector/sap-successfactors-connector-release-notes-mule-4#5-0-3) - [Stripe Connector 1.0.18](https://docs.mulesoft.com/jp/release-notes/connector/stripe-connector-release-notes-mule-4#1-0-18) August 26 - [Anypoint MQ Connector 4.0.23](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4#4-0-23) - [DocuSign Connector 1.1.4](https://docs.mulesoft.com/jp/release-notes/connector/docusign-connector-release-notes-mule-4#1-1-4) - [Dropbox Connector 1.0.11](https://docs.mulesoft.com/jp/release-notes/connector/dropbox-connector-release-notes-mule-4#1-0-11) - [Google Pub/Sub Connector 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/google-pubsub-connector-release-notes-mule-4#1-2-2) - [Object Store Connector 1.3.2](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4#1-3-2) - [Salesforce Marketing Cloud Connector 5.0.3](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4#5-0-3) - [Zoom Connector 1.0.7](https://docs.mulesoft.com/jp/release-notes/connector/zoom-connector-release-notes-mule-4#1-0-7) August 25 - [Database Connector 1.16.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-16-3) - [MCP Connector 1.7.0](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-7-0) - [Spring Module 1.5.2](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#1-5-2) - [Web Service Consumer Connector 2.2.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-2-4) August 24 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#august-24-2026) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#august-24-2026) - [Microsoft MSMQ Connector 2.1.2](https://docs.mulesoft.com/jp/release-notes/connector/msmq-connector-release-notes-mule-4#2-1-2) - [Moodle Connector 0.1.2](https://docs.mulesoft.com/jp/release-notes/connector/moodle-connector-release-notes-mule-4#0-1-2) - [Salesforce Composite Connector 3.1.2](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#3-1-2) - [Spring Module 1.5.1](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#1-5-1) - [Zendesk Connector 1.1.12](https://docs.mulesoft.com/jp/release-notes/connector/zendesk-connector-release-notes-mule-4#1-1-12) August 21 - [Azure Data Lake Storage Connector 1.0.10](https://docs.mulesoft.com/jp/release-notes/connector/azure-data-lake-connector-release-notes-mule-4#1-0-10) - [Azure Event Hubs Connector 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/azure-event-hubs-connector-release-notes#1-2-4) - [Intercom Connector 1.0.6](https://docs.mulesoft.com/jp/release-notes/connector/intercom-connector-release-notes-mule-4#1-0-6) - [Java Module 1.2.18](https://docs.mulesoft.com/jp/release-notes/connector/java-module#1-2-18) - [Microsoft Dynamics NAV Connector 3.0.1](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4#3-0-1) - [OAuth Module 1.1.28](https://docs.mulesoft.com/jp/release-notes/connector/oauth-module-release-notes#1-1-28) - [Oracle EBS 12.1 Connector 5.3.4](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-connector-release-notes-mule-4#5-3-4) - [Redis Connector 5.8.0](https://docs.mulesoft.com/jp/release-notes/connector/redis-connector-release-notes-mule-4#5-8-0) - [Runtime Manager Agent 2.7.19](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-19) - [Runtime Manager Agent 2.8.4](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4) - [Slack Connector 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/slack-connector-release-notes-mule-4#2-0-2) - [Tableau Connector 1.1.5](https://docs.mulesoft.com/jp/release-notes/connector/tableau-specialist-connector-release-notes-mule-4#1-1-5) - [Trello Connector 1.2.5](https://docs.mulesoft.com/jp/release-notes/connector/trello-connector-release-notes-mule-4#1-2-5) - [XML Module 1.4.6](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-xml#1-4-6) August 20 - [Amazon S3 Connector 8.0.7](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-7) - [Apache Kafka Connector 4.15.0](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-15-0) - [Asana Connector 1.0.9](https://docs.mulesoft.com/jp/release-notes/connector/asana-connector-release-notes-mule-4#1-0-9) - [Mailchimp Marketing Connector 1.0.8](https://docs.mulesoft.com/jp/release-notes/connector/mailchimp-marketing-connector-release-notes-mule-4#1-0-8) - [Microsoft Service Bus Connector 2.2.9](https://docs.mulesoft.com/jp/release-notes/connector/ms-service-bus-connector-release-notes-mule-4#2-2-9) - [Omni Gateway Policy Development Kit (PDK) 1.10.0](https://docs.mulesoft.com/jp/release-notes/pdk/pdk-release-notes#1-10-0) - [Salesforce Connector 12.0.2](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#12-0-2) - [Salesforce Data Cloud Connector 1.5.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-data-cloud-connector-release-notes-mule-4#1-5-0) - [Salesforce Marketing Cloud Connector 5.0.2](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4#5-0-2) - [X12 EDI Connector 2.19.0](https://docs.mulesoft.com/jp/release-notes/connector/x12-edi-connector-release-notes-mule-4#2-19-0) August 19 - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#august-19-2026) - [Azure Key Vault Properties Provider 2.2.1](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-2-1) - [Azure Service Bus Connector 3.8.0](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-8-0) - [Coda Connector 0.1.22](https://docs.mulesoft.com/jp/release-notes/connector/coda-connector-release-notes-mule-4#0-1-22) - [Hyperforce](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes) - [MQTT Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/mqtt3-connector-release-notes#1-1-0) - [Shippo Connector 0.1.23](https://docs.mulesoft.com/jp/release-notes/connector/shippo-connector-release-notes-mule-4#0-1-23) August 18 - [HL7 MLLP Connector 2.2.4](https://docs.mulesoft.com/jp/release-notes/connector/hl7-mllp-connector-release-notes-mule-4#2-2-4) - [HTTP Connector 1.12.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-http#1-12-1) - [SFTP Connector 2.7.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-7-3) - [Stripe Connector 1.0.17](https://docs.mulesoft.com/jp/release-notes/connector/stripe-connector-release-notes-mule-4#1-0-17) - [Teamwork Connector 0.1.27](https://docs.mulesoft.com/jp/release-notes/connector/teamwork-connector-release-notes-mule-4#0-1-27) August 17 - [Anypoint MQ Connector 4.0.22](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4#4-0-22) - [Azure Key Vault Connector 1.2.6](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4#1-2-6) - [Microsoft .NET Connector 3.1.13](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dotnet-connector-release-notes-mule-4#3-1-13) - [Microsoft Dynamics AX 2012 Connector 2.0.6](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-ax-connector-release-notes-mule-4#2-0-6) - [Microsoft Dynamics CRM Connector 3.2.16](https://docs.mulesoft.com/jp/release-notes/connector/ms-dynamics-crm-connector-release-notes-mule-4#3-2-16) - [Microsoft Dynamics GP Connector 2.1.8](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-gp-connector-release-notes-mule-4#2-1-8) - [MuleSoft AI Chain Connector 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-ai-chain-connector-release-notes-mule-4#1-0-1) - [Scripting Module 2.1.2](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-scripting#2-1-2) - [WebSockets Connector 1.0.4](https://docs.mulesoft.com/jp/release-notes/connector/websockets-connector-release-notes-mule-4#1-0-4) August 14 - [APIkit for Mule 4 1.12.5](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.5-release-notes) - [Google BigQuery Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/google-bigquery-connector-release-notes-mule-4#1-2-1) - [RPA Builder 6.7.24](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.24-release-notes) - [Shopify Connector 1.1.13](https://docs.mulesoft.com/jp/release-notes/connector/shopify-connector-release-notes-mule-4#1-1-13) - [Veeva Vault Connector 1.5.6](https://docs.mulesoft.com/jp/release-notes/connector/veeva-vault-release-notes-mule-4#1-5-6) - [Zuora AQuA Connector 1.0.17](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4#1-0-17) - [Zuora Connector 6.0.17](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4#6-0-17) August 13 - [Cryptography Module 2.2.1](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes#2-2-1) - [Spring Module 2.1.3](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#2-1-3) August 12 - [Amazon Secrets Manager Properties Provider 1.1.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-secrets-manager-properties-provider-release-notes-mule-4#1-1-3) - [Anypoint Partner Manager 2.27.1](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-27-1) - [Apache Hadoop Distributed File System Connector 6.0.30](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4#6-0-30) - [JMS Connector 1.10.5](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms#1-10-5) - [MCP Support Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/mcp-support-release-notes) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#august-12-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#august-12-2026) - [Oracle EBS 12.2 Connector 2.3.4](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-122-connector-release-notes-mule-4#2-3-4) August 11 - [Amazon Kinesis Data Streams Connector 2.0.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-4) - [gRPC Connector 1.0.2](https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4#1-0-2) August 10 - [Amazon Lambda Connector 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-lambda-connector-release-notes-mule-4#1-2-2) - [AMQP Connector 1.9.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-amqp#1-9-2) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#august-10-2026) - [MCP Schema Validation Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/mcp-schema-validation-release-notes) - [ServiceNow Connector 6.18.5](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-5) August 7 - [Amazon S3 Connector 8.0.6](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-6) - [Amazon SNS Connector 4.8.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4#4-8-3) - [APIkit for SOAP 2.1.3](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.3) - [MuleSoft Developer Hub](https://docs.mulesoft.com/jp/release-notes/developer-hub/mulesoft-developer-hub-release-notes#august-7-2026) August 6 - [A2A v1 Azure Content Guardrails Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/a2a-v1-azure-guardrails-release-notes) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#august-6-2026) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#august-6-2026) - [API Governance](https://docs.mulesoft.com/jp/release-notes/api-governance/api-governance-release-notes#august-2026) - [API Security-Identification Header Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/api-security-identification-header-release-notes) - [API Security-Identification Header Policy for Mule Gateway](https://docs.mulesoft.com/jp/release-notes/policies/api-security-identification-header-policy-release-notes) - [APIkit for Mule 4 1.12.4](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.4-release-notes) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#august-6-2026) - [NetSuite OpenAir Connector 2.0.13](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-openair-connector-release-notes-mule-4#2-0-13) - [NetSuite Restlet Connector 1.0.10](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-restlet-connector-release-notes-mule-4#1-0-10) - [Salesforce Connector 12.0.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#12-0-1) - [Salesforce Einstein Analytics Connector 3.21.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-analytics-connector-release-notes-mule-4#3-21-1) - [Salesforce Pub/Sub Connector 1.4.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4#1-4-1) August 5 - [Amazon DynamoDB Connector 1.6.5](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-5) - [Amazon EC2 Connector 3.0.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-ec2-connector-release-notes-mule-4#3-0-2) - [Amazon Redshift Connector 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-redshift-connector-release-notes-mule-4#1-2-3) - [Amazon SQS Connector 5.12.9](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-9) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#august-5-2026) - [Snowflake Connector 1.4.1](https://docs.mulesoft.com/jp/release-notes/connector/snowflake-connector-release-notes-mule-4#1-4-1) August 4 - [A2A v1 Bedrock Guardrails Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/a2a-v1-bedrock-guardrails-release-notes) - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#august-4-2026) - [HTTP Connector 1.12.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-http#1-12-0) - [Java Module 1.2.17](https://docs.mulesoft.com/jp/release-notes/connector/java-module#1-2-17) - [JMS Connector 2.0.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms#2-0-0) - [Kerberos Module 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/kerberos-module#1-0-1) - [Mule runtime engine patch update 4.12.2](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes#august-2026) - [Mule runtime engine patch update 4.9.20](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#august-2026) - [Mule runtime engine patch update 4.6.33](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#august-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#august-4-2026) - [Salesforce Composite Connector 3.1.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#3-1-1) - [Web Service Consumer Connector 1.12.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#1-12-0) - [Web Service Consumer Connector 2.2.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-2-3) August 3 - [A2A Connector 2.0.0](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4#2-0-0) - [A2A Quality Evaluation Policy](https://docs.mulesoft.com/jp/release-notes/gateway/policies/a2a-quality-evaluation-release-notes) - [Aggregators Module 1.1.5](https://docs.mulesoft.com/jp/release-notes/connector/aggregators-module-release-notes#1-1-5) - [APIkit for Mule 4 1.12.3](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.3-release-notes) - [IBM MQ Connector 2.0.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#2-0-0) - [Java Module 2.0.6](https://docs.mulesoft.com/jp/release-notes/connector/java-module#2-0-6) - [JSON Module 2.5.8](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-8) - [Workday Connector 16.7.1](https://docs.mulesoft.com/jp/release-notes/connector/workday-connector-release-notes-mule-4#16-7-1) ## [](#july-2026)July 2026 July 31 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#july-2026) - [APIkit for OData 4 1.6.1](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.6.1) - [APIkit for SOAP 1.7.2](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.7.2) - [APIkit for SOAP 2.1.2](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.2) - [gRPC Connector 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4#1-0-1) - [Veeva Vault Connector 1.5.5](https://docs.mulesoft.com/jp/release-notes/connector/veeva-vault-release-notes-mule-4#1-5-5) July 30 - [MongoDB Connector 6.4.1](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4#6-4-1) - [Runtime Fabric 3.0.277](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-3.x.x#3-0-277) - [Runtime Fabric Command Line Tool 1.0.150](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes#1-0-150) July 29 - [MuleSoft WebCrawler Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-webcrawler-connector-release-notes-mule-4#1-0-0) - [Validation Module 2.0.10](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-validation#2-0-10) July 28 - [Usage Reports](https://docs.mulesoft.com/jp/release-notes/usage-reports/usage-reports-release-notes#july-28-2026) - [VM Connector 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-vm#2-0-2) July 27 - [Azure Key Vault Properties Provider 2.2.0](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-2-0) - [Neo4j Connector 4.0.1](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4#4-0-1) - [Usage Reports](https://docs.mulesoft.com/jp/release-notes/usage-reports/usage-reports-release-notes#july-27-2026) - [Xero Accounting Connector 1.1.9](https://docs.mulesoft.com/jp/release-notes/connector/xero-accounting-connector-release-notes-mule-4#1-1-9) July 26 - [HL7 MLLP Connector 2.2.3](https://docs.mulesoft.com/jp/release-notes/connector/hl7-mllp-connector-release-notes-mule-4#2-2-3) July 24 - [Amazon Secrets Manager Properties Provider 1.1.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-secrets-manager-properties-provider-release-notes-mule-4#1-1-2) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#july-24-2026) - [Compression Module 2.2.8](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-compression#2-2-8) - [Cryptography Module 2.1.3](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes#2-1-3) - [Cryptography Module 2.2.0](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes#2-2-0) - [File Connector 1.5.6](https://docs.mulesoft.com/jp/release-notes/connector/connector-file#1-5-6) - [Microsoft Outlook 365 Connector 1.3.2](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-outlook-365-connector-release-notes-mule-4#1-3-2) - [X12 EDI Connector 2.18.1](https://docs.mulesoft.com/jp/release-notes/connector/x12-edi-connector-release-notes-mule-4#2-18-1) - [XML Module 1.4.5](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-xml#1-4-5) July 23 - [Database Connector 1.16.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-16-2) - [JMS Connector 1.10.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms#1-10-4) - [Object Store Connector 1.3.1](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4#1-3-1) - [Omni Gateway 1.13.4](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-13-4) - [SFTP Connector 2.7.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-7-2) - [Sockets Connector 1.2.9](https://docs.mulesoft.com/jp/release-notes/connector/connector-sockets#1-2-9) July 22 - [Connector Builder 1.5.0](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes#1-5-0) - [MUnit 3.7.3](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.3-release-notes) - [Salesforce Marketing Cloud Connector 5.0.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4#5-0-1) - [Secure Configuration Properties Extension 1.3.1](https://docs.mulesoft.com/jp/release-notes/mule-runtime/secure-properties#1-3-1) - [Zuora AQuA Connector 1.0.16](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4#1-0-16) July 21 - [Amazon S3 Connector 8.0.5](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-5) - [AMQP Connector 1.9.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-amqp#1-9-1) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#july-21-2026) - [Anypoint MQ Connector 4.0.21](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4#4-0-21) - [Box Connector 5.3.2](https://docs.mulesoft.com/jp/release-notes/connector/box-connector-release-notes-mule-4#5-3-2) - [Microsoft .NET Connector 3.1.12](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dotnet-connector-release-notes-mule-4#3-1-12) - [Microsoft Service Bus Connector 2.2.8](https://docs.mulesoft.com/jp/release-notes/connector/ms-service-bus-connector-release-notes-mule-4#2-2-8) - [OAuth2 Provider Module 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/oauth2-provider-release-notes#1-2-3) - [Omni Gateway 1.12.8](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-8) - [Omni Gateway 1.9.15](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-15) - [Omni Gateway Policy Development Kit (PDK) 1.9.2](https://docs.mulesoft.com/jp/release-notes/pdk/pdk-release-notes#1-9-2) - [Salesforce Connector 12.0.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#12-0-0) July 20 - [Anypoint Platform Private Cloud Edition 4.2.1](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.2.1-release-notes) - [LDAP Connector 3.7.1](https://docs.mulesoft.com/jp/release-notes/connector/ldap-connector-release-notes-mule-4#3-7-1) - [Salesforce Composite Connector 3.1.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#3-1-0) July 19 - [Zendesk Connector 1.1.11](https://docs.mulesoft.com/jp/release-notes/connector/zendesk-connector-release-notes-mule-4#1-1-11) July 17 - [MCP Connector 1.6.1](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-6-1) - [MongoDB Connector 6.4.0](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4#6-4-0) - [WSS Module 2.2.2](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4#wss-2.2.2) July 15 - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#july-15-2026) - [Google Pub/Sub Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/google-pubsub-connector-release-notes-mule-4#1-2-1) - [MUnit 3.7.2](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.2-release-notes) July 14 - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes#july-14-2026) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#july-14-2026) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#july-2026) - [Azure Event Hubs Connector 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/azure-event-hubs-connector-release-notes#1-2-3) - [Mule Maven Plugin 4.10.1](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.1-release-notes) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#july-14-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#july-14-2026) - [Web Service Consumer Connector 2.2.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-2-2) July 10 - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#july-10) - [Microsoft Dynamics 365 Business Central Connector 1.0.5](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-365-business-central-connector-release-notes-mule-4#1-0-5) July 9 - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#july-10-2026) - [Oracle EBS 12.1 Connector 5.3.3](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-connector-release-notes-mule-4#5-3-3) July 8 - [Anypoint CLI 4.x 1.6.25](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Anypoint MQ Connector 4.0.20](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4#4-0-20) - [APIkit for Mule 4 1.12.2](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.2-release-notes) - [Azure Key Vault Connector 1.2.5](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4#1-2-5) - [Azure Service Bus Connector 3.7.0](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-7-0) - [Jira Connector 1.2.17](https://docs.mulesoft.com/jp/release-notes/connector/jira-connector-release-notes-mule-4#1-2-17) - [JSON Module 2.5.7](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-7) - [Salesforce Einstein Analytics Connector 3.21.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-analytics-connector-release-notes-mule-4#3-21-0) July 7 - [Amazon RDS Connector 1.4.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-rds-connector-release-notes-mule-4#1-4-3) - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#june-2-2026) - [Mule runtime engine patch update 4.12.1](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes#july-2026) - [Mule runtime engine patch update 4.11.6](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes#july-2026) - [Mule runtime engine patch update 4.9.19](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#july-2026) - [Mule runtime engine patch update 4.6.32](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#july-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#july-7-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#july-7-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#july-7-2026) - [QuickBooks Online Connector 2.0.20](https://docs.mulesoft.com/jp/release-notes/connector/quickbooks-online-connector-release-notes-mule-4#2-0-20) July 5 - [QuickBooks Online Connector 2.0.19](https://docs.mulesoft.com/jp/release-notes/connector/quickbooks-online-connector-release-notes-mule-4#v2-0-19) July 2 - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#july-2-2026) - [Salesforce Pub/Sub Connector 1.4.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4#1-4-0) - [Shopify Connector 1.1.12](https://docs.mulesoft.com/jp/release-notes/connector/shopify-connector-release-notes-mule-4#1-1-12) - [Sockets Connector 1.2.8](https://docs.mulesoft.com/jp/release-notes/connector/connector-sockets#1-2-8) - [Stripe Connector 1.0.16](https://docs.mulesoft.com/jp/release-notes/connector/stripe-connector-release-notes-mule-4#1-0-16) July 1 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#july-2026) - [DHL Tracking Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/dhl-tracking-connector-release-notes-mule-4#1-1-0) - [Google Gemini Connector 1.0.18](https://docs.mulesoft.com/jp/release-notes/connector/google-gemini-connector-release-notes-mule-4#1-0-18) - [Google Gemini Connector 1.0.19](https://docs.mulesoft.com/jp/release-notes/connector/google-gemini-connector-release-notes-mule-4#1-0-19) - [Google Gemini Connector 1.0.20](https://docs.mulesoft.com/jp/release-notes/connector/google-gemini-connector-release-notes-mule-4#1-0-20) - [Notion Connector 0.1.1](https://docs.mulesoft.com/jp/release-notes/connector/notion-connector-release-notes-mule-4#0-1-1) - [OpenAI Connector 0.1.1](https://docs.mulesoft.com/jp/release-notes/connector/openai-connector-release-notes-mule-4#0-1-1) - [OpenWeatherMap Connector 1.0.14](https://docs.mulesoft.com/jp/release-notes/connector/openweathermap-connector-release-notes-mule-4#1-0-14) - [PagerDuty Connector 1.0.28](https://docs.mulesoft.com/jp/release-notes/connector/pagerduty-connector-release-notes-mule-4#1-0-28) - [SAP S/4HANA OData Connector 2.9.4](https://docs.mulesoft.com/jp/release-notes/connector/sap-s4-hana-connector-release-notes-mule-4#2-9-4) - [ShipStation Connector 0.1.1](https://docs.mulesoft.com/jp/release-notes/connector/shipstation-connector-release-notes-mule-4#0-1-1) - [Zuora Connector 6.0.16](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4#6-0-16) ## [](#june-2026)June 2026 June 30 - [Amazon S3 Connector 8.0.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-4) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#june-30-2026) - [APIkit for Mule 4 1.12.1](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.1-release-notes) - [Coda Connector 0.1.21](https://docs.mulesoft.com/jp/release-notes/connector/coda-connector-release-notes-mule-4#0-1-21) - [Java Module 2.0.5](https://docs.mulesoft.com/jp/release-notes/connector/java-module#2-0-5) - [Shippo Connector 0.1.22](https://docs.mulesoft.com/jp/release-notes/connector/shippo-connector-release-notes-mule-4#0-1-22) - [Teamwork Connector 0.1.26](https://docs.mulesoft.com/jp/release-notes/connector/teamwork-connector-release-notes-mule-4#0-1-26) - [Workable Connector 0.1.14](https://docs.mulesoft.com/jp/release-notes/connector/workable-connector-release-notes-mule-4#0-1-14) June 29 - [Amazon Kinesis Data Streams Connector 2.0.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-3) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#june-29-2026) - [APIkit for Mule 4 1.12.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.12.0-release-notes) - [Web Service Consumer Connector 2.2.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-2-1) June 28 - [Amazon Redshift Connector 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-redshift-connector-release-notes-mule-4#1-2-2) June 27 - [WebSockets Connector 1.0.3](https://docs.mulesoft.com/jp/release-notes/connector/websockets-connector-release-notes-mule-4#1-0-3) June 26 - [Amazon RDS Connector 1.4.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-rds-connector-release-notes-mule-4#1-4-2) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#june26-2026) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#june-26-2026) - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#june-26-2026) - [Anypoint Partner Manager 2.27.0](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-27-0) - [APIkit for Mule 4 1.11.18](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.18-release-notes) - [MuleSoft Developer Hub](https://docs.mulesoft.com/jp/release-notes/developer-hub/mulesoft-developer-hub-release-notes#june-26-2026) - [Zuora AQuA Connector 1.0.15](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4#1-0-15) June 25 - [Microsoft .NET Connector 3.1.11](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dotnet-connector-release-notes-mule-4#3-1-11) - [Redis Connector 5.7.0](https://docs.mulesoft.com/jp/release-notes/connector/redis-connector-release-notes-mule-4#5-7-0) - [Salesforce Connector 11.5.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-5-0) June 24 - [Anypoint CLI 4.x 1.6.23](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Database Connector 1.16.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-16-1) - [Informatica Business 360 Connector 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/informatica-b360-connector-release-notes-mule-4#1-0-1) June 23 - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#june-23-2026) - [APIkit for SOAP 1.7.1](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.7.1) - [APIkit for SOAP 2.1.1](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.1) - [RPA Builder 6.7.22](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.22-release-notes) - [XML Module 1.4.4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-xml#1-4-4) June 22 - [Amazon DynamoDB Connector 1.6.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-4) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#june-22-2026) - [Microsoft SharePoint Connector 3.9.0](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-9-0) - [MuleSoft Terraform Provider 1.0.14](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-14) June 19 - [Amazon SQS Connector 5.12.8](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-8) - [MuleSoft Government Cloud](https://docs.mulesoft.com/jp/release-notes/gov-cloud/gov-cloud-release-notes#june-19-2026) June 18 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#june18-2026) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#june-18-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#june-18-2026) June 17 - [Azure Data Lake Storage Connector 1.0.9](https://docs.mulesoft.com/jp/release-notes/connector/azure-data-lake-connector-release-notes-mule-4#1-0-9) June 16 - [MuleSoft Terraform Provider 1.0.13](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-13) - [Zuora AQuA Connector 1.0.14](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4#1-0-14) June 15 - [Amazon SQS Connector 5.12.7](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-7) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#june-15-2026) - [FTPS Connector 2.1.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftps#2-1-2) - [Hyperforce](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes) - [IBM MQ Connector 1.9.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#1-9-0) - [Veeva Vault Connector 1.5.4](https://docs.mulesoft.com/jp/release-notes/connector/veeva-vault-release-notes-mule-4#1-5-4) June 13 - [Stripe Connector 1.0.15](https://docs.mulesoft.com/jp/release-notes/connector/stripe-connector-release-notes-mule-4#v1-0-15) June 12 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#June11-2026) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#june-2026) - [Apache Kafka Connector 4.14.0](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-14-0) - [Azure Key Vault Properties Provider 2.1.6](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-1-6) - [ServiceNow Connector 6.18.4](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-4) June 11 - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#june-11-2026) - [MongoDB Connector 6.3.13](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4#6-3-13) June 10 - [MuleSoft Terraform Provider 1.0.12](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-12) - [Zuora Connector 6.0.15](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4#6-0-15) June 8 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#june-2026) - [MCP Connector 1.6.0](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-6-0) - [MuleSoft Terraform Provider 1.0.10](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-10) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#june-8-2026) June 5 - [Azure Event Hubs Connector 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/azure-event-hubs-connector-release-notes#1-2-2) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#june-5) - [LDAP Connector 3.7.0](https://docs.mulesoft.com/jp/release-notes/connector/ldap-connector-release-notes-mule-4#3-7-0) - [MuleSoft Terraform Provider 1.0.9](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-9) June 4 - [Anypoint API Community Manager](https://docs.mulesoft.com/jp/release-notes/api-community-manager/api-community-manager-release-notes#june-2026) - [Anypoint CLI 4.x 1.6.22](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Azure Key Vault Properties Provider 2.1.5](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-1-5) June 3 - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#june-3-2026) - [JSON Module 2.5.6](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-6) - [Web Service Consumer Connector 2.2.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-2-0) June 2 - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#june-2-2026) - [Connector Builder 1.4.0](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes#1-4-0) - [DataWeave 2.12.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.12.0-release-notes) - [Mule Maven Plugin 4.10.0](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.10.0-release-notes) - [Mule runtime engine 4.12.0](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes) - [Mule runtime engine patch update 4.11.5](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes#june-2026) - [Mule runtime engine patch update 4.9.18](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#june-2026) - [Mule runtime engine patch update 4.6.31](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#june-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#june-2-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#june-2-2026) - [MuleSoft DX MCP Server](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-june2-26) June 1 - [Amazon Kinesis Data Streams Connector 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-2) - [MuleSoft Terraform Provider 1.0.7](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-7) - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes#week-of-june-1-2026) - [ServiceNow Connector 6.18.3](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-3) ## [](#may-2026)May 2026 May 31 - [Salesforce Pub/Sub Connector 1.3.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4#1-3-1) May 30 - [Salesforce Marketing Cloud Connector 5.0.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4#5-0-0) May 29 - [APIkit for AsyncAPI 1.2.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-asyncapi-1.2.0) - [MuleSoft Terraform Provider 1.0.5](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-5) May 28 - [Amazon S3 Connector 8.0.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-3) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes#may-28-2026) - [MuleSoft Developer Hub](https://docs.mulesoft.com/jp/release-notes/developer-hub/mulesoft-developer-hub-release-notes#may-28-2026) - [MuleSoft Platform MCP Server](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-may28-26) - [Runtime Fabric 3.0.102](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-3.x.x#3-0-102) May 27 - [Amazon SNS Connector 4.8.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4#4-8-2) - [MuleSoft Terraform Provider 1.0.3](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-3) May 26 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#May26-2026) - [API Experience Hub](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes#may-2026) - [Box Connector 5.3.1](https://docs.mulesoft.com/jp/release-notes/connector/box-connector-release-notes-mule-4#5-3-1) - [Microsoft .NET Connector 3.1.10](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dotnet-connector-release-notes-mule-4#3-1-10) May 25 - [Amazon Lambda Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-lambda-connector-release-notes-mule-4#1-2-1) - [Amazon SQS Connector 5.12.6](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-6) - [MuleSoft Terraform Provider 1.0.2](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-2) May 22 - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#may-22-2026) - [MuleSoft Terraform Provider 1.0.1](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#v1-0-1) May 21 - [WSS Module 2.2.1](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4#wss-2.2.1) May 20 - [Apache Hadoop Distributed File System Connector 6.0.29](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4#6-0-29) - [Database Connector 1.16.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-16-0) - [Omni Gateway 1.13.1](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-13-1) - [Omni Gateway 1.12.6](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-6) - [Omni Gateway 1.11.10](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-11-10) - [Omni Gateway 1.9.13](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-13) - [Web Service Consumer Connector 2.1.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-1-4) May 19 - [Anypoint CLI 4.x 1.6.21](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#May19-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#may-19-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#may-19-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#may-19-2026) - [Tableau Connector 1.1.4](https://docs.mulesoft.com/jp/release-notes/connector/tableau-specialist-connector-release-notes-mule-4#1-1-4) - [Usage Reports](https://docs.mulesoft.com/jp/release-notes/usage-reports/usage-reports-release-notes#may-19-2026) - [Web Service Consumer Connector 2.1.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-1-3) May 18 - [FTP Connector 2.0.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftp#2-0-4) - [OAuth Module 1.1.27](https://docs.mulesoft.com/jp/release-notes/connector/oauth-module-release-notes#1-1-27) May 16 - [Spring Module 2.1.2](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#2-1-2) May 15 - [Confluent Schema Registry Connector 1.1.5](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-1-5) - [Cryptography Module 2.1.2](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes#2-1-2) - [QuickBooks Online Connector 2.0.18](https://docs.mulesoft.com/jp/release-notes/connector/quickbooks-online-connector-release-notes-mule-4#2-0-18) - [Trello Connector 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/trello-connector-release-notes-mule-4#1-2-4) May 14 - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#may-14-2026) - [HTTP Connector 1.11.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-http#1-11-3) May 13 - [Anypoint CLI 4.x 1.6.20](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) May 12 - [HTTP Connector 1.11.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-http#1-11-2) - [Microsoft OneDrive Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-onedrive-connector-release-notes-mule-4#1-2-0) - [NetSuite Connector 12.0.0](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4#12-0-0) - [RPA Builder 6.7.20](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.20-release-notes) May 11 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#may-2026) - [API Experience Hub](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes#may-2026) - [API Manager 2.5.30](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes#2-5-30) - [Mule Maven Plugin 4.9.1](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.9.1-release-notes) - [MuleSoft Terraform Provider 1.0.0](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-release-notes#1-0-0) - [MUnit 3.7.1](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.1-release-notes) - [Omni Gateway 1.13.0](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-13-0) - [Salesforce Composite Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#3-0-0) May 9 - [Model Proxy](https://docs.mulesoft.com/jp/release-notes/gateway/model-proxy-release-notes#may-9-2026) May 8 - [Compression Module 2.2.7](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-compression#2-2-7) - [IBM MQ Connector 1.8.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#1-8-3) - [Microsoft Teams Connector 1.1.5](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-teams-connector-release-notes-mule-4#1-1-5) - [MuleSoft Developer Hub](https://docs.mulesoft.com/jp/release-notes/developer-hub/mulesoft-developer-hub-release-notes#may-8-2026) - [RosettaNet Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/rosettanet-connector-release-notes-mule-4#3-0-0) May 7 - [Anypoint Flex Gateway 1.12.5](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-5) - [Anypoint Flex Gateway 1.11.9](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-11-9) - [Tracing Module 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/tracing-module-release-notes#1-2-1) May 6 - [Anypoint CLI 4.x 1.6.19](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [SFTP Connector 2.7.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-7-1) May 5 - [Amazon Bedrock Connector 1.0.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-bedrock-connector-release-notes-mule-4#1-0-2) - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#may-5-2026) - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#may-5-2026) - [DocuSign Connector 1.1.3](https://docs.mulesoft.com/jp/release-notes/connector/docusign-connector-release-notes-mule-4#1-1-3) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#may-5) - [Mule runtime engine patch update 4.11.4](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes#may-2026) - [Mule runtime engine patch update 4.9.17](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#may-2026) - [Mule runtime engine patch update 4.6.30](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#may-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#may-5-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#may-5-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#may-5-2026) May 4 - [Redis Connector 5.6.0](https://docs.mulesoft.com/jp/release-notes/connector/redis-connector-release-notes-mule-4#5-6-0) - [WSS Module 2.2.0](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4#wss-2.2.0) May 1 - [MCP Connector 1.5.0](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-5-0) - [Microsoft SharePoint Connector 3.8.2](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-8-2) ## [](#april-2026)April 2026 April 30 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#april-2026) - [Anypoint Platform Private Cloud Edition 4.2.0](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.2.0-release-notes) - [APIkit for Mule 4 1.11.17](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.17-release-notes) - [APIkit for OData v2 2.4.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.4.0) - [APIkit for SOAP 2.1.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.1.0) April 29 - [Anypoint Flex Gateway 1.12.4](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-4) - [Anypoint Flex Gateway 1.11.8](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-11-8) - [Azure Key Vault Properties Provider 2.1.4](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-1-4) - [Confluent Schema Registry Connector 1.1.4](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-1-4) - [Salesforce Einstein Analytics Connector 3.20.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-analytics-connector-release-notes-mule-4#3-20-0) April 28 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#April27-2026) April 27 - [RPA Builder 6.7.18](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.18-release-notes) April 26 - [Salesforce Pub/Sub Connector 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4#1-3-0) April 25 - [Apache Kafka Connector 4.13.1](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-13-1) April 24 - [Anypoint Flex Gateway 1.11.7](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-11-7) - [Anypoint Flex Gateway 1.9.12](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-12) - [APIkit for GraphQL 1.2.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-graphql-1.2.0) - [MuleSoft Vectors Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-vectors-connector-release-notes-mule-4#1-1-0) April 23 - [Workday Connector 16.7.0](https://docs.mulesoft.com/jp/release-notes/connector/workday-connector-release-notes-mule-4#16-7-0) April 22 - [Anypoint Flex Gateway 1.12.3](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-3) - [Apache Hadoop Distributed File System Connector 6.0.28](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4#6-0-28) - [Mule Upgrade Tool 1.1.8](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.8-release-notes) - [Salesforce Composite Connector 2.21.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#2-21-0) - [Xero Accounting Connector 1.1.8](https://docs.mulesoft.com/jp/release-notes/connector/xero-accounting-connector-release-notes-mule-4#1-1-8) April 21 - [Access Management](https://docs.mulesoft.com/jp/release-notes/access-management/access-management-release-notes#april-21-2026) - [Amazon RDS Connector 1.4.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-rds-connector-release-notes-mule-4#1-4-1) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#april-2026) - [Anypoint Flex Gateway Policy Development Kit (PDK) 1.8.0](https://docs.mulesoft.com/jp/release-notes/pdk/pdk-release-notes#1-8-0) - [Anypoint MQ 2.18.0](https://docs.mulesoft.com/jp/release-notes/mq/mq-release-notes#2-18-0) - [SFTP Connector 2.7.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-7-0) April 20 - [Anypoint API Manager 2.5.29](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#April20-2026) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#april-2026) April 19 - [Amazon Redshift Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-redshift-connector-release-notes-mule-4#1-2-1) - [Azure Cosmos DB Connector 1.0.6](https://docs.mulesoft.com/jp/release-notes/connector/azure-cosmos-db-connector-release-notes-mule-4#1-0-6) - [Azure Key Vault Connector 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4#1-2-4) - [DocuSign Connector 1.1.2](https://docs.mulesoft.com/jp/release-notes/connector/docusign-connector-release-notes-mule-4#1-1-2) - [Dropbox Connector 1.0.10](https://docs.mulesoft.com/jp/release-notes/connector/dropbox-connector-release-notes-mule-4#1-0-10) - [Informatica Business 360 Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/informatica-b360-connector-release-notes-mule-4#1-0-0) - [MongoDB Connector 6.3.12](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4#6-3-12) April 16 - [APIkit for Mule 4 1.11.16](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.16-release-notes) - [Mule Maven Plugin 4.9.0](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.9.0-release-notes) April 15 - [Anypoint CLI 4.x 1.6.18](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Database Connector 1.15.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-15-1) April 14 - [APIkit for OData 4 1.6.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.6.0) - [Blackboard Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/blackboard-connector-release-notes-mule-4#0-1-0) - [Canvas Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/canvas-connector-release-notes-mule-4#1-0-0) - [Cryptography Module 2.1.1](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes#2-1-1) - [D2L Brightspace Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/d2l-brightspace-connector-release-notes-mule-4#0-1-0) - [Moodle Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/moodle-connector-release-notes-mule-4#0-1-0) April 13 - [IBM MQ Connector 1.8.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#1-8-2) April 12 - [Amazon DynamoDB Connector 1.6.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-3) - [ServiceNow Connector 6.18.2](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-2) - [Zuora Connector 6.0.14](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4#6-0-14) April 10 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#april-2026) - [Web Service Consumer Connector 2.1.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-1-2) April 7 - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#april-7-2026) - [Mule runtime engine patch update 4.11.3](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes#april-2026) - [Mule runtime engine patch update 4.9.16](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#april-2026) - [Mule runtime engine patch update 4.6.29](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#april-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#april-7-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#april-7-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#april-7-2026) April 6 - [APIkit for SOAP 1.7.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.7.0) - [APIkit for SOAP 2.0.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-2.0.0) April 5 - [Amazon SQS Connector 5.12.5](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-5) - [Salesforce Connector 11.4.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-4-0) April 4 - [API Designer (Crowd) 2.79.0](https://docs.mulesoft.com/jp/release-notes/design-center/design-center-release-notes-api_specs#2-79-0) April 3 - [Workday Connector 16.6.0](https://docs.mulesoft.com/jp/release-notes/connector/workday-connector-release-notes-mule-4#16-6-0) - [Zendesk Connector 1.1.10](https://docs.mulesoft.com/jp/release-notes/connector/zendesk-connector-release-notes-mule-4#1-1-10) April 2 - [Agentforce Connector 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector/agentforce-connector-release-notes-mule-4#1-3-0) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#april-2) - [Salesforce Data Cloud Connector 1.4.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-data-cloud-connector-release-notes-mule-4#1-4-0) ## [](#march-2026)March 2026 March 31 - [Anypoint Flex Gateway 1.12.2](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-2) - [Anypoint Flex Gateway 1.11.6](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-11-6) - [Anypoint Flex Gateway 1.9.11](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-11) - [FTPS Connector 2.1.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftps#2-1-1) - [Integration Intelligence (Anypoint Monitoring)](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#march-31-2026) March 30 - [Anypoint API Manager 2.5.28](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes#2-5-28) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#march-30-2026) - [Hyperforce](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes) - [Model Proxy](https://docs.mulesoft.com/jp/release-notes/gateway/model-proxy-release-notes#march-30-2026) - [Usage Reports](https://docs.mulesoft.com/jp/release-notes/usage-reports/usage-reports-release-notes#march-17-2026) March 29 - [Azure Key Vault Connector 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4#1-2-3) March 27 - [Object Store Connector 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4#1-3-0) March 26 - [RPA Bot 1.7.24](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.24-release-notes) - [Salesforce Marketing Cloud REST Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-marketing-cloud-rest-connector-release-notes-mule-4#1-2-1) - [Validation Module 2.0.9](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-validation#2-0-9) March 25 - [APIkit for Mule 4 1.11.15](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.15-release-notes) - [SFTP Connector 2.6.5](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-6-5) March 23 - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#march-2026) - [Integration Intelligence (Anypoint Monitoring)](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#march-23-2026) March 22 - [MCP Connector 1.4.0](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-4-0) - [Microsoft .NET Connector 3.1.9](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dotnet-connector-release-notes-mule-4#3-1-9) - [Microsoft Dynamics 365 Business Central Connector 1.0.4](https://docs.mulesoft.com/jp/release-notes/connector/microsoft-dynamics-365-business-central-connector-release-notes-mule-4#1-0-4) - [Oracle EBS 12.1 Connector 5.3.2](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-connector-release-notes-mule-4#5-3-2) March 21 - [Apache Kafka Connector 4.13.0](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-13-0) March 20 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#March20-2026) - [APIkit for OData 4 1.5.5](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.5) - [FTPS Connector 2.1.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftps#2-1-0) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#march-20) - [Salesforce Connector 11.3.4](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-3-4) - [Slack Connector 2.0.1](https://docs.mulesoft.com/jp/release-notes/connector/slack-connector-release-notes-mule-4#2-0-1) - [WSS Module 2.1.0](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4#wss-2.1.0) March 19 - [A2A Connector 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4#1-1-1) - [Confluent Schema Registry Connector 1.1.3](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-1-3) - [Mailchimp Marketing Connector 1.0.7](https://docs.mulesoft.com/jp/release-notes/connector/mailchimp-marketing-connector-release-notes-mule-4#1-0-7) - [NetSuite Connector 11.11.2](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4#11-11-2) - [Oracle EBS 12.2 Connector 2.3.3](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-122-connector-release-notes-mule-4#2-3-3) March 18 - [Azure Service Bus Connector 3.6.1](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-6-1) - [gRPC Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/grpc-connector-release-notes-mule-4#1-0-0) - [Microsoft SharePoint Connector 3.8.1](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-8-1) March 17 - [Anypoint Partner Manager 2.26.0](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-26-0) - [Runtime Manager Agent 2.7.11](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11) - [Usage Reports](https://docs.mulesoft.com/jp/release-notes/usage-reports/usage-reports-release-notes#march-17-2026) March 16 - [Anypoint API Manager 2.5.27](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes#2-5-27) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#March16-2026) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#march-2026) - [API Governance](https://docs.mulesoft.com/jp/release-notes/api-governance/api-governance-release-notes#march-2026) - [APIkit for gRPC 1.0.0](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-grpc-1.0.0) March 12 - [Amazon Bedrock Connector 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-bedrock-connector-release-notes-mule-4#1-0-1) - [Mule Maven Plugin 4.8.0](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.8.0-release-notes) - [Workday Connector 16.5.0](https://docs.mulesoft.com/jp/release-notes/connector/workday-connector-release-notes-mule-4#16-5-0) March 10 - [Amazon Kinesis Data Streams Connector 2.0.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-1) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#march-10) March 8 - [Amazon EC2 Connector 3.0.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-ec2-connector-release-notes-mule-4#3-0-1) - [Amazon S3 Connector 8.0.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-2) - [Workday Connector 16.4.2](https://docs.mulesoft.com/jp/release-notes/connector/workday-connector-release-notes-mule-4#16-4-2) March 7 - [RPA Bot 1.7.22](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.22-release-notes) March 6 - [Anypoint API Manager 2.5.26](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes#2-5-26) - [APIkit for Mule 4 1.11.14](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.14-release-notes) - [Connector Builder 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes#1-3-0) - [MuleSoft MCP Server](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-mar6-26) - [RPA Builder 6.7.16](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.16-release-notes) March 5 - [Anypoint Flex Gateway 1.11.5](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-11-5) - [Anypoint Flex Gateway 1.10.6](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-10-6) - [Anypoint Flex Gateway 1.9.10](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-9-10) - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#march-5-2026) March 4 - [AS2 Connector 7.0.0](https://docs.mulesoft.com/jp/release-notes/connector/as2-connector-release-notes-mule-4#7-0-0) March 3 - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#march-3-2026) - [Mule runtime engine patch update 4.11.2](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes#march-2026) - [Mule runtime engine patch update 4.9.15](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#march-2026) - [Mule runtime engine patch update 4.6.28](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#march-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#march-3-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#march-3-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#march-3-2026) March 2 - [A2A Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4#1-1-0) March 1 - [Amazon Lambda Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-lambda-connector-release-notes-mule-4#1-2-0) ## [](#february-2026)February 2026 February 28 - [Jira Connector 1.2.16](https://docs.mulesoft.com/jp/release-notes/connector/jira-connector-release-notes-mule-4#1-2-16) - [Oracle EBS 12.1 Connector 5.3.1](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-connector-release-notes-mule-4#5-3-1) February 26 - [Adobe Marketo Connector 3.0.10](https://docs.mulesoft.com/jp/release-notes/connector/marketo-connector-release-notes-mule-4#3-0-10) - [HL7 MLLP Connector 2.2.2](https://docs.mulesoft.com/jp/release-notes/connector/hl7-mllp-connector-release-notes-mule-4#2-2-2) - [Shopify Connector 1.1.11](https://docs.mulesoft.com/jp/release-notes/connector/shopify-connector-release-notes-mule-4#1-1-11) February 25 - [Anypoint Flex Gateway 1.12.0](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-12-0) - [Confluent Schema Registry Connector 1.1.2](https://docs.mulesoft.com/jp/release-notes/connector/confluent-schema-registry-connector-release-notes-mule-4#1-1-2) February 24 - [A2A Connector 1.0.2](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4#1-0-2) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Feb24-2026) February 20 - [APIkit for Mule 4 1.11.13](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.13-release-notes) February 19 - [Redis Connector 5.5.0](https://docs.mulesoft.com/jp/release-notes/connector/redis-connector-release-notes-mule-4#5-5-0) February 18 - [Cassandra Connector 4.1.4](https://docs.mulesoft.com/jp/release-notes/connector/cassandra-connector-release-notes-mule-4#4-1-4) - [Mule Upgrade Tool 1.1.6](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.6-release-notes) February 17 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Feb17-2026) - [Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#february-2026) February 14 - [Mule runtime engine patch update 4.11.1](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes#february-2026) - [Mule runtime engine patch update 4.9.14](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#february-2026) - [Mule runtime engine patch update 4.6.27](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#february-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#february-14-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#february-14-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#february-14-2026) February 13 - [Anypoint API Manager 2.5.25](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes#2-5-25) February 12 - [Anypoint Flex Gateway Policy Development Kit (PDK) 1.7.0](https://docs.mulesoft.com/jp/release-notes/pdk/pdk-release-notes#1-7-0) - [OAuth Module 1.1.26](https://docs.mulesoft.com/jp/release-notes/connector/oauth-module-release-notes#1-1-26) February 10 - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#february-10-2026) - [Google BigQuery Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/google-bigquery-connector-release-notes-mule-4#1-2-0) February 9 - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes#february-9-2026) - [Agent Visualizer](https://docs.mulesoft.com/jp/release-notes/agent-visualizer/agent-visualizer-release-notes#february-9-2026) - [JSON Module 2.5.5](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-5) February 6 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Feb06-2026) - [APIkit for SOAP 1.6.10](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.10) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#february-6-2026) - [Salesforce Pub/Sub Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4#1-2-0) February 5 - [Amazon Bedrock Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-bedrock-connector-release-notes-mule-4#1-0-0) - [APIkit for Mule 4 1.11.12](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.12-release-notes) - [CloudHub 1.130.0](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes#1-130-0) February 4 - [DataWeave 2.11.0](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-2.11.0-release-notes) - [Mule runtime engine 4.11.0](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#february-4-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#february-4-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#february-4-2026) - [Oracle EBS 12.2 Connector 2.3.2](https://docs.mulesoft.com/jp/release-notes/connector/oracle-ebs-122-connector-release-notes-mule-4#2-3-2) February 3 - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#february-3-2026) - [Mule Maven Plugin 4.7.0](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.7.0-release-notes) - [Mule runtime engine patch update 4.9.13](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#february-2026) - [Mule runtime engine patch update 4.6.26](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#february-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#february-3-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#february-3-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#february-3-2026) - [MUnit 3.7.0](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.7.0-release-notes) - [XML Module 1.4.3](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-xml#1-4-3) February 2 - [Anypoint CLI 4.x 1.6.16](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes#week-of-february-2-2026) February 1 - [Amazon Secrets Manager Properties Provider 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-secrets-manager-properties-provider-release-notes-mule-4#1-1-1) - [Oracle PeopleSoft Connector 3.1.11](https://docs.mulesoft.com/jp/release-notes/connector/peoplesoft-connector-release-notes-mule-4#3-1-11) - [Xero Accounting Connector 1.1.7](https://docs.mulesoft.com/jp/release-notes/connector/xero-accounting-connector-release-notes-mule-4#1-1-7) ## [](#january-2026)January 2026 January 31 - [API Experience Hub](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes#january-2026) - [Salesforce Marketing Cloud Connector 4.1.7](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-mktg-connector-release-notes-mule-4#4-1-7) - [Shopify Connector 1.1.10](https://docs.mulesoft.com/jp/release-notes/connector/shopify-connector-release-notes-mule-4#1-1-10) - [Trello Connector 1.2.3](https://docs.mulesoft.com/jp/release-notes/connector/trello-connector-release-notes-mule-4#1-2-3) - [Zoom Connector 1.0.6](https://docs.mulesoft.com/jp/release-notes/connector/zoom-connector-release-notes-mule-4#1-0-6) - [Zuora AQuA Connector 1.0.13](https://docs.mulesoft.com/jp/release-notes/connector/zuora-aqua-release-notes-mule-4#1-0-13) - [Zuora Connector 6.0.13](https://docs.mulesoft.com/jp/release-notes/connector/zuora-connector-release-notes-mule-4#6-0-13) January 30 - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#january-30-2026) - [APIkit for SOAP 1.6.9](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.9) - [Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#january-2026) - [JMS Connector 1.10.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-jms#1-10-3) - [Microsoft SharePoint Connector 3.8.0](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-8-0) January 29 - [Anypoint Partner Manager 2.25.0](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-25-0) January 28 - [CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes#january-28-2026) - [SFTP Connector 2.6.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-6-4) January 26 - [OAuth2 Provider Module 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/oauth2-provider-release-notes#1-2-2) January 24 - [DocuSign Connector 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/docusign-connector-release-notes-mule-4#1-1-1) - [IBM MQ Connector 1.8.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#1-8-1) January 23 - [Amazon S3 Connector 8.0.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-1) - [Anypoint API Manager 2.5.24](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes#2-5-24) - [Apache Kafka Connector 4.12.2](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-12-2) - [APIkit for OData v2 2.3.5](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.5) - [Cryptography Module 2.1.0](https://docs.mulesoft.com/jp/release-notes/connector/cryptography-module-release-notes#2-1-0) - [Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#january-2026) January 22 - [Azure Key Vault Connector 1.2.2](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4#1-2-2) January 21 - [Jira Connector 1.2.15](https://docs.mulesoft.com/jp/release-notes/connector/jira-connector-release-notes-mule-4#1-2-15) - [Salesforce Connector 11.3.3](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-3-3) January 16 - [Anypoint CLI 4.x 1.6.15](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [MCP Connector 1.3.1](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-3-1) January 15 - [Amazon Redshift Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-redshift-connector-release-notes-mule-4#1-2-0) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Jan15-2026) - [Anypoint Partner Manager 2.24.5](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-24-5) - [CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes#january-15-2026) - [HTTP Connector 1.11.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-http#1-11-1) - [MuleSoft MCP Server](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#new-features-mcp-server-jan15-26) January 14 - [APIkit for Mule 4 1.11.11](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.11-release-notes) January 13 - [CloudHub 1.129.0](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes#1-129-0) - [WSS Module 2.0.3](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4#wss-2.0.3) January 10 - [Apache Hadoop Distributed File System Connector 6.0.27](https://docs.mulesoft.com/jp/release-notes/connector/hdfs-connector-release-notes-mule-4#6-0-27) - [API Community Manager](https://docs.mulesoft.com/jp/release-notes/api-community-manager/api-community-manager-release-notes#january-2026) January 9 - [API Experience Hub](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes#january-2026) - [APIkit for SOAP 1.6.7](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.7) - [Azure Service Bus Connector 3.6.0](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-6-0) January 8 - [A2A Connector 1.0.1](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4#1-0-1) January 7 - [Amazon DynamoDB Connector 1.6.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-2) - [Amazon SNS Connector 4.8.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4#4-8-1) - [Microsoft SharePoint Connector 3.7.3](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-7-3) January 6 - [Amazon Redshift Connector 1.1.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-redshift-connector-release-notes-mule-4#1-1-2) - [Amazon SQS Connector 5.12.4](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-4) - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#january-6-2026) - [Mule runtime engine patch update 4.9.12](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#january-2026) - [Mule runtime engine patch update 4.6.25](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#january-2026) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#january-6-2026) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#january-6-2026) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#january-6-2026) - [MUnit 3.6.3](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.3-release-notes) - [Notion Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/notion-connector-release-notes-mule-4#0-1-0) - [SFTP Connector 2.6.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-6-3) - [ShipStation Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/shipstation-connector-release-notes-mule-4#0-1-0) ## [](#december-2025)December 2025 December 21 - [Amazon RDS Connector 1.4.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-rds-connector-release-notes-mule-4#1-4-0) - [Apache Kafka Connector 4.12.1](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-12-1) - [Azure Data Lake Storage Connector 1.0.8](https://docs.mulesoft.com/jp/release-notes/connector/azure-data-lake-connector-release-notes-mule-4#1-0-8) December 20 - [NetSuite Connector 11.11.1](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4#11-11-1) - [ServiceNow Connector 6.18.1](https://docs.mulesoft.com/jp/release-notes/connector/servicenow-connector-release-notes-mule-4#6-18-1) - [Snowflake Connector 1.4.0](https://docs.mulesoft.com/jp/release-notes/connector/snowflake-connector-release-notes-mule-4#1-4-0) December 19 - [Aggregators Module 1.1.4](https://docs.mulesoft.com/jp/release-notes/connector/aggregators-module-release-notes#1-1-4) - [Object Store Connector 1.2.5](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4#1-2-5) - [SFTP Connector 2.6.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-6-2) December 18 - [Amazon EC2 Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-ec2-connector-release-notes-mule-4#3-0-0) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Dec18-2025) - [Anypoint Partner Manager 2.24.4](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-24-4) - [Connector Builder 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes#1-2-0) - [DHL Tracking Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/dhl-tracking-connector-release-notes-mule-4#0-1-0) - [Hyperforce](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes) - [Java Module 2.0.4](https://docs.mulesoft.com/jp/release-notes/connector/java-module#2-0-4) - [OpenAI Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/openai-connector-release-notes-mule-4#0-1-0) - [Web Service Consumer Connector 2.1.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-1-1) December 17 - [A2A Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4#1-0-0) - [Azure Key Vault Properties Provider 2.1.3](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-properties-provider-release-notes-mule-4#2-1-3) - [FTPS Connector 2.0.5](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftps#2-0-5) - [Teamwork Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/teamwork-connector-release-notes-mule-4#0-1-0) December 16 - [Coda Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/coda-connector-release-notes-mule-4#0-1-0) - [Shippo Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/shippo-connector-release-notes-mule-4#0-1-0) - [Workable Connector 0.1.0](https://docs.mulesoft.com/jp/release-notes/connector/workable-connector-release-notes-mule-4#0-1-0) December 15 - [APIkit for OData 4 1.5.4](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.4) December 12 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Dec12-2025) - [Email Connector 1.8.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-email#1-8-0) - [Web Service Consumer Connector 2.1.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-1-0) December 11 - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Dec11-2025) - [Google Gemini Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/google-gemini-connector-release-notes-mule-4#1-0-0) - [OpenWeatherMap Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/openweathermap-connector-release-notes-mule-4#1-0-0) December 10 - [FTP Connector 2.0.3](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftp#2-0-3) December 9 - [Database Connector 1.15.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-db#1-15-0) - [Microsoft SharePoint Connector 3.7.2](https://docs.mulesoft.com/jp/release-notes/connector/sharepoint-connector-release-notes-mule-4#3-7-2) December 8 - [PagerDuty Connector 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/pagerduty-connector-release-notes-mule-4#1-0-0) - [Runtime Fabric 3.0.1](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-3.x.x#3-0-1) - [Runtime Fabric Command Line Tool 1.0.113](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes#1-0-113) December 7 - [Salesforce Connector 11.3.2](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-3-2) December 5 - [Amazon DynamoDB Connector 1.6.1](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-1) - [Azure Event Hubs Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/azure-event-hubs-connector-release-notes#1-2-1) December 4 - [Amazon SQS Connector 5.12.3](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-3) - [HL7 EDI Connector 4.3.0](https://docs.mulesoft.com/jp/release-notes/connector/hl7-connector-release-notes-mule-4#4-3-0) - [MongoDB Connector 6.3.11](https://docs.mulesoft.com/jp/release-notes/connector/mongodb-connector-release-notes-mule-4#6-3-11) December 3 - [IBM MQ Connector 1.8.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#1-8-0) December 2 - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#december-2-2025) - [Mule Maven Plugin 4.6.1](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.6.1-release-notes) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#december-2-2025) - [MUnit 3.6.2](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.2-release-notes) ## [](#november-2025)November 2025 November 28 - [Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/anypoint-exchange-release-notes#november-2025) November 26 - [API Governance](https://docs.mulesoft.com/jp/release-notes/api-governance/api-governance-release-notes#november-2025) November 24 - [Access Management](https://docs.mulesoft.com/jp/release-notes/access-management/access-management-release-notes#november-24-2025) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes#november-24-2025) - [Anypoint Platform Private Cloud Edition 4.1.3](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.1.3-release-notes) November 23 - [Amazon DynamoDB Connector 1.6.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-6-0) November 22 - [Amazon Kinesis Data Streams Connector 2.0.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-kinesis-connector-release-notes-mule-4#2-0-0) - [API Experience Hub](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes#november-2025) November 21 - [Amazon Secrets Manager Properties Provider 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-secrets-manager-properties-provider-release-notes-mule-4#1-1-0) - [Azure Service Bus Connector 3.5.2](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-5-2) November 20 - [Access Management](https://docs.mulesoft.com/jp/release-notes/access-management/access-management-release-notes#november-20-2025) - [Connector Builder 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes#1-1-0) - [MuleSoft MCP Server](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes#november-20-2025) - [NetSuite Connector 11.11.0](https://docs.mulesoft.com/jp/release-notes/connector/netsuite-connector-release-notes-mule-4#11-11-0) - [Oracle PeopleSoft Connector 3.1.10](https://docs.mulesoft.com/jp/release-notes/connector/peoplesoft-connector-release-notes-mule-4#3-1-10) November 19 - [Jira Connector 1.2.14](https://docs.mulesoft.com/jp/release-notes/connector/jira-connector-release-notes-mule-4#1-2-14) - [Salesforce Connector 11.3.1](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-3-1) November 18 - [CloudHub 1.128.0](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes#1-128-0) November 17 - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes#week-of-november-17-2025) November 16 - [Google Pub/Sub Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/google-pubsub-connector-release-notes-mule-4#1-2-0) November 15 - [Amazon S3 Connector 8.0.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#8-0-0) November 14 - [AMQP Connector 1.9.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-amqp#1-9-0) - [RPA Bot 1.7.18](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.18-release-notes) November 13 - [MCP Connector 1.3.0](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-3-0) - [RosettaNet Connector 2.2.0](https://docs.mulesoft.com/jp/release-notes/connector/rosettanet-connector-release-notes-mule-4#2-2-0) November 12 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Nov12-2025) November 11 - [Anypoint Partner Manager 2.24.3](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-24-3) - [Anypoint Partner Manager 2.24.2](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-24-2) - [SFTP Connector 2.6.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-6-1) November 10 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Nov10-2025) November 8 - [Amazon SQS Connector 5.12.2](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sqs-connector-release-notes-mule-4#5-12-2) - [Xero Accounting Connector 1.1.6](https://docs.mulesoft.com/jp/release-notes/connector/xero-accounting-connector-release-notes-mule-4#1-1-6) November 7 - [APIkit for OData 4 1.5.3](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-4-1.5.3) - [APIkit for OData v2 2.3.4](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.4) - [LDAP Connector 3.6.1](https://docs.mulesoft.com/jp/release-notes/connector/ldap-connector-release-notes-mule-4#3-6-1) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#november-7-2025) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#november-7-2025) - [WSS Module 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4#wss-2.0.2) November 6 - [Anypoint Monitoring Agent Installer](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-installer-release-notes#november-6-2025) November 5 - [Apache Kafka Connector 4.12.0](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-12-0) - [Email Connector 1.7.7](https://docs.mulesoft.com/jp/release-notes/connector/connector-email#1-7-7) November 4 - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes#november-4-2025) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#Nov4-2025) - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#november-4-2025) - [Google Pub/Sub Connector 1.1.1](https://docs.mulesoft.com/jp/release-notes/connector/google-pubsub-connector-release-notes-mule-4#1-1-1) - [Mule runtime engine patch update 4.9.11](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#november-2025) - [Mule runtime engine patch update 4.6.24](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#november-2025) - [Mule runtime engine patch update 4.4.0-20250919](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes#november-2025) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#november-4-2025) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#november-4-2025) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#november-4-2025) November 3 - [FTPS Connector 2.0.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftps#2-0-4) ## [](#october-2025)October 2025 October 31 - [APIkit for Mule4 1.11.10](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.10-release-notes) October 30 - [Anypoint Platform Private Cloud Edition 4.1.2](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-4.1.2-release-notes) - [Azure Key Vault Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/azure-key-vault-connector-release-notes-mule-4#1-2-1) - [EDIFACT EDI Connector 2.10.2](https://docs.mulesoft.com/jp/release-notes/connector/edifact-edi-connector-release-notes#2-10-2) - [File Connector 1.5.5](https://docs.mulesoft.com/jp/release-notes/connector/connector-file#1-5-5) - [X12 EDI Connector 2.18.0](https://docs.mulesoft.com/jp/release-notes/connector/x12-edi-connector-release-notes-mule-4#2-18-0) October 29 - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes#october-29) - [Java Module 1.2.16](https://docs.mulesoft.com/jp/release-notes/connector/java-module#1-2-16) - [Java Module 2.0.3](https://docs.mulesoft.com/jp/release-notes/connector/java-module#2-0-3) - [Salesforce Einstein Analytics Connector 3.19.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-analytics-connector-release-notes-mule-4#3-19-0) October 28 - [Anypoint Partner Manager 2.24.1](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-24-1) - [APIkit for Mule 4 1.11.9](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.9-release-notes) - [APIkit for SOAP 1.6.5](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.5) - [APIkit for SOAP 1.6.6](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-soap-1.6.6) - [FTP Connector 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftp#2-0-2) October 27 - [CloudHub 1.127.0](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes#1-127-0) - [CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes#october-27-2025) - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes#week-of-october-27-2025) October 26 - [IBM CTG Connector 3.0.0](https://docs.mulesoft.com/jp/release-notes/connector/ibm-ctg-connector-release-notes-mule-4#3-0-0) - [Salesforce Composite Connector 2.20.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-composite-connector-release-notes-mule-4#2-20-0) October 24 - [Amazon DynamoDB Connector 1.5.6](https://docs.mulesoft.com/jp/release-notes/connector/amazon-dynamodb-connector-release-notes-mule-4#1-5-6) - [Amazon SNS Connector 4.8.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4#4-8-0) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#oct24-2025) - [SFTP Connector 2.6.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-6-0) October 22 - [Connector Builder 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes#1-0-0) - [Kerberos Module 1.0.0](https://docs.mulesoft.com/jp/release-notes/connector/kerberos-module#1-0-0) October 21 - [RPA Builder 6.7.14](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.14-release-notes) - [Web Service Consumer Connector 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-0-2) October 20 - [Anypoint MQ Connector 4.0.14](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-mq-connector-release-notes-mule-4#4-0-14) - [Mule Upgrade Tool 1.1.5](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool-1.1.5-release-notes) October 17 - [APIkit for GraphQL 1.1.1](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-graphql-1.1.1) - [APIkit for Mule 4 1.11.8](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.11.8-release-notes) - [APIkit for OData v2 2.3.3](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-for-odata-2.3.3) October 14 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#oct14-2025) October 10 - [SFTP Connector 2.5.2](https://docs.mulesoft.com/jp/release-notes/connector/connector-sftp#2-5-2) October 8 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#oct8-2025) - [Salesforce Pub/Sub Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-pubsub-connector-release-notes-mule-4#1-1-0) October 3 - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes) - [Agent Visualizer](https://docs.mulesoft.com/jp/release-notes/agent-visualizer/agent-visualizer-release-notes) - [Amazon SNS Connector 4.7.12](https://docs.mulesoft.com/jp/release-notes/connector/amazon-sns-connector-release-notes-mule-4#4-7-12) - [Anypoint API Manager 2.5.20](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager-release-notes#2-5-20) - [Anypoint CLI 4.x 1.6.8](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-4) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#oct-2025) - [Anypoint Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/exchange-release-notes) - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes) - [HTTP Connector 1.11.0](https://docs.mulesoft.com/jp/release-notes/connector/connector-http#1-11-0) - [Mule Maven Plugin 4.6.0](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.6.0-release-notes) - [MUnit 3.6.1](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.1-release-notes) - [MUnit 3.6.0](https://docs.mulesoft.com/jp/release-notes/munit/munit-3.6.0-release-notes) - [Salesforce Connector 11.3.0](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-3-0) October 2 - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#october-2-2025) - [Jira Connector 1.2.13](https://docs.mulesoft.com/jp/release-notes/connector/jira-connector-release-notes-mule-4#1-2-13) - [Mule runtime engine 4.9.10](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#october-2025) - [Mule runtime engine patch update 4.6.23](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#october-2025) - [Mule runtime engine patch update 4.4.0-20250919](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes#october-2025) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#october-2-2025) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#october-2-2025) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#october-2-2025) - [Secrets Manager](https://docs.mulesoft.com/jp/release-notes/anypoint-security/secrets-manager-release-notes#october-2-2025) October 1 - [Anypoint Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring-release-notes) - [Anypoint Partner Manager 2.24.0](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-partner-manager-2.0-release-notes#2-24-0) ## [](#september-2025)September 2025 September 30 - [A2A Connector 0.4.0-BETA](https://docs.mulesoft.com/jp/release-notes/connector/a2a-connector-release-notes-mule-4#0-4-0-BETA) - [Compression Module 2.2.6](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-compression#2-2-6) - [HTTP Connector 1.10.6](https://docs.mulesoft.com/jp/release-notes/connector/connector-http#1-10-6) - [Secure Configuration Properties Extension 1.3.0](https://docs.mulesoft.com/jp/release-notes/mule-runtime/secure-properties#1-3-0) September 29 - [Anypoint Flex Gateway 1.10.2](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-release-notes#1-10-2) - [MuleSoft Inference Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-inference-connector-release-notes-mule-4#1-2-0) - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes#week-of-september-29-2025) September 28 - [FTP Connector 2.0.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-ftp#2-0-1) September 26 - [Agentforce Connector 1.2.0](https://docs.mulesoft.com/jp/release-notes/connector/agentforce-connector-release-notes-mule-4#1-2-0) - [Sockets Connector 1.2.7](https://docs.mulesoft.com/jp/release-notes/connector/connector-sockets#1-2-7) September 25 - [CloudHub 1.126.0](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-release-notes#1-126-0) September 24 - [Apache Kafka Connector 4.11.1](https://docs.mulesoft.com/jp/release-notes/connector/kafka-connector-release-notes-mule-4#4-11-1) - [Azure Service Bus Connector 3.5.1](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-5-1) September 22 - [Mule Maven Plugin 4.5.3](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.5.3-release-notes) September 19 - [Amazon RDS Connector 1.3.12](https://docs.mulesoft.com/jp/release-notes/connector/amazon-rds-connector-release-notes-mule-4#1-3-12) - [Compression Module 2.2.5](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-compression#2-2-5) - [Validation Module 2.0.8](https://docs.mulesoft.com/jp/release-notes/mule-runtime/module-validation#2-0-8) September 17 - [IBM MQ Connector 1.7.8](https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq#1-7-8) - [Spring Module 2.1.1](https://docs.mulesoft.com/jp/release-notes/connector/spring-module-release-notes#2-1-1) September 16 - [File Connector 1.5.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-file#1-5-4) - [Object Store Connector 1.2.4](https://docs.mulesoft.com/jp/release-notes/connector/object-store-connector-release-notes-mule-4#1-2-4) - [Web Service Consumer Connector 1.11.4](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#1-11-4) - [Web Service Consumer Connector 2.0.1](https://docs.mulesoft.com/jp/release-notes/connector/connector-wsc#2-0-1) September 15 - [CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes#september-15-2025) - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes#week-of-september-15-2025) - [WSS Module 2.0.1](https://docs.mulesoft.com/jp/release-notes/connector/wss-module-release-notes-mule-4#wss-2.0.1) September 14 - [Jira Connector 1.2.12](https://docs.mulesoft.com/jp/release-notes/connector/jira-connector-release-notes-mule-4#1-2-12) - [Neo4j Connector 4.0.0](https://docs.mulesoft.com/jp/release-notes/connector/neo4j-connector-release-notes-mule-4#4-0-0) September 12 - [Salesforce Connector 11.2.3](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-2-3) September 11 - [MCP Connector 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/mcp-connector-release-notes-mule-4#1-2-1) - [OAuth2 Provider Module 1.2.1](https://docs.mulesoft.com/jp/release-notes/connector/oauth2-provider-release-notes#1-2-1) September 9 - [Java Module 2.0.2](https://docs.mulesoft.com/jp/release-notes/connector/java-module#2-0-2) September 8 - [MuleSoft Inference Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/mulesoft-inference-connector-release-notes-mule-4#1-1-0) - [OAuth Module 1.1.25](https://docs.mulesoft.com/jp/release-notes/connector/oauth-module-release-notes#1-1-25) September 7 - [Azure Service Bus Connector 3.5.0](https://docs.mulesoft.com/jp/release-notes/connector/azure-service-bus-connector-release-notes-mule-4#3-5-0) September 6 - [SAP SuccessFactors Connector 5.0.2](https://docs.mulesoft.com/jp/release-notes/connector/sap-successfactors-connector-release-notes-mule-4#5-0-2) September 5 - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#september-5-2025) September 4 - [Amazon S3 Connector 7.2.0](https://docs.mulesoft.com/jp/release-notes/connector/amazon-s3-connector-release-notes-mule-4#7-2-0) - [Salesforce Connector 11.2.2](https://docs.mulesoft.com/jp/release-notes/connector/salesforce-connector-release-notes-mule-4#11-2-2) September 3 - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes#sep-2025) - [Google Pub/Sub Connector 1.1.0](https://docs.mulesoft.com/jp/release-notes/connector/google-pubsub-connector-release-notes-mule-4#1-1-0) - [Runtime Fabric Command Line Tool 1.0.107](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes#1-0-107) September 2 - [CloudHub Dedicated Load Balancer](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-dedicated-load-balancer-release-notes#september-2-2025) - [JSON Module 2.5.4](https://docs.mulesoft.com/jp/release-notes/connector/json-module-release-notes#2-5-4) - [Mule Maven Plugin 4.5.2](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-4.5.2-release-notes) - [Mule runtime engine 4.9.9](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes#september-2025) - [Mule runtime engine patch update 4.6.22](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes#september-2025) - [Mule runtime engine patch update 4.4.0-20250829](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.4.0-release-notes#september-2025) - [Mule runtime engine patch update for CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes#september-2-2025) - [Mule runtime engine patch update for CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-runtimes-release-notes#september-2-2025) - [Mule runtime engine patch update for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes#september-2-2025) # Release Notes - [Accelerators](https://docs.mulesoft.com/jp/release-notes/accelerators/accelerators-release-notes) - [Access Management](https://docs.mulesoft.com/jp/release-notes/access-management/access-management-release-notes) - [Agent Fabric](https://docs.mulesoft.com/jp/release-notes/agent-fabric/agent-fabric-release-notes) - [Agent Visualizer](https://docs.mulesoft.com/jp/release-notes/agent-visualizer/agent-visualizer-release-notes) - [Anypoint Code Builder](https://docs.mulesoft.com/jp/release-notes/code-builder/acb-release-notes) - [Anypoint Platform CLI](https://docs.mulesoft.com/jp/release-notes/cli/anypoint-platform-cli-release-notes) - [API Catalog CLI](https://docs.mulesoft.com/jp/release-notes/api-catalog/api-catalog-release-notes) - [API Community Manager](https://docs.mulesoft.com/jp/release-notes/api-community-manager/api-community-manager-release-notes) - [API Console](https://docs.mulesoft.com/jp/release-notes/api-console/api-console-release-notes) - [API Experience Hub](https://docs.mulesoft.com/jp/release-notes/api-experience-hub/api-experience-hub-release-notes) - [API Functional Monitoring](https://docs.mulesoft.com/jp/release-notes/api-functional-monitoring/api-functional-monitoring-rn-landing-page) - [API Governance](https://docs.mulesoft.com/jp/release-notes/api-governance/api-governance-rn-landing-page) - [API Manager](https://docs.mulesoft.com/jp/release-notes/api-manager/api-manager) - [API Mocking Service](https://docs.mulesoft.com/jp/release-notes/api-mocking-service/api-mocking-service-release-notes) - [API Visualizer](https://docs.mulesoft.com/jp/release-notes/visualizer/anypoint-visualizer-1.0-release-notes) - [APIkit](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-release-notes) - [AsyncAPI Support](https://docs.mulesoft.com/jp/release-notes/platform/event-driven-api) - [CloudHub](https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub) - [CloudHub 2.0](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2) - [Composer](https://docs.mulesoft.com/jp/composer/ms_composer_ms_release_notes) (MuleSoft Composer) - [Composer for Salesforce](https://docs.mulesoft.com/jp/composer-salesforce/ms_composer_release_notes) - [Connector Builder](https://docs.mulesoft.com/jp/release-notes/connector-builder/connector-builder-release-notes) - [Connectors](https://docs.mulesoft.com/jp/release-notes/connector/anypoint-connector-release-notes) - [DataGraph](https://docs.mulesoft.com/jp/release-notes/datagraph/datagraph-release-notes) - [DataWeave](https://docs.mulesoft.com/jp/release-notes/dataweave/dataweave-release-notes) - [Design Center](https://docs.mulesoft.com/jp/release-notes/design-center/design-center-release-notes) - [Enhanced MuleSoft Experience](https://docs.mulesoft.com/jp/release-notes/enhanced-mulesoft-experience/enhanced-mulesoft-exp-release-notes) - [Exchange](https://docs.mulesoft.com/jp/release-notes/exchange/exchange-release-notes) - [Government Cloud](https://docs.mulesoft.com/jp/release-notes/gov-cloud/gov-cloud-release-notes) - [gRPC Support](https://docs.mulesoft.com/jp/release-notes/platform/grpc-support) - [Hyperforce](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes) - [IDP](https://docs.mulesoft.com/jp/release-notes/idp/idp-release-notes) - [Monitoring](https://docs.mulesoft.com/jp/release-notes/monitoring/anypoint-monitoring) - [MQ](https://docs.mulesoft.com/jp/release-notes/mq/anypoint-mq-release-notes) - [Mule Maven Plugin](https://docs.mulesoft.com/jp/release-notes/mule-maven-plugin/mule-maven-plugin-release-notes) - [Mule Runtime](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb) - [Mule Upgrade Tool](https://docs.mulesoft.com/jp/release-notes/mule-upgrade-tool/mule-upgrade-tool) - [MuleSoft Developer Hub](https://docs.mulesoft.com/jp/release-notes/developer-hub/mulesoft-developer-hub-release-notes) - [MuleSoft MCP Servers](https://docs.mulesoft.com/jp/release-notes/mulesoft-mcp-server/mulesoft-mcp-server-release-notes) - [MuleSoft Terraform Provider](https://docs.mulesoft.com/jp/release-notes/terraform/terraform-rn-landing-page) - [MUnit](https://docs.mulesoft.com/jp/release-notes/munit/munit-release-notes) - [MUnit Studio Plugin](https://docs.mulesoft.com/jp/release-notes/munit-studio-plugin/munit-studio-plugin-release-notes) - [Object Store v2](https://docs.mulesoft.com/jp/release-notes/object-store/objectstore-release-notes) - [Omni Gateway](https://docs.mulesoft.com/jp/release-notes/gateway/gateway-rn-landing-page) - [Omni Gateway Policy Development Kit (PDK)](https://docs.mulesoft.com/jp/release-notes/pdk/pdk-rn-landing-page) - [OpenAPI Specification Support](https://docs.mulesoft.com/jp/release-notes/platform/oas3) - [Partner Manager](https://docs.mulesoft.com/jp/release-notes/partner-manager/anypoint-b2b-release-notes) - [Private Cloud Edition](https://docs.mulesoft.com/jp/release-notes/pce/anypoint-private-cloud-release-notes) - [RPA](https://docs.mulesoft.com/jp/release-notes/rpa/rpa-release-notes) - [Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric) - [Runtime Manager](https://docs.mulesoft.com/jp/release-notes/runtime-manager/rtm-and-rtma-rns-landing-page) - [Security](https://docs.mulesoft.com/jp/release-notes/anypoint-security/anypoint-security-release-notes) - [Studio](https://docs.mulesoft.com/jp/release-notes/studio/anypoint-studio) - [Usage Reports](https://docs.mulesoft.com/jp/release-notes/usage-reports/usage-reports-release-notes) # Release Notes for APIkit for OData v4 1.5.3 ## [](#november-7-2025)November 7, 2025 ### Compatibility
Application/Service Version

Mule

4.3.0 or later

Studio

7.9.0 or later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Correlation IDs are now correctly propagated to internal child requests generated during OData $expand operations.

W-17379510

Custom errors from a Raise Error component in secondary OData flows are now correctly propagated.

W-17803691

NullPointerException errors no longer occur during OData XML serialization because the rel property is now correctly set for single and multi-level $expand operations.

W-18592694

The mule-sdk-api project POM file now includes the missing license information, resolving issues identified by security scanning tools like Sonatype NexusIQ.

W-18253269
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Release Notes for APIkit for OData v4 1.5.4 ## [](#december-15-2025)December 15, 2025 ## What’s New - This release upgrades the **commons-io** dependency to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

Studio

7.9.0 or later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-io dependency is upgraded to version 2.20.0 to address reported security vulnerabilities.

W-20318132
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Release Notes for APIkit for OData v4 1.5.5 ## [](#march-20-2026)March 20, 2026 ## What’s New - This release upgrades the **jackson-core** and **commons-lang3** dependencies to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.3.0 or later

Studio

7.9.0 or later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-core direct dependency is upgraded to 2.18.6 to address a known security vulnerability.

W-20318132

The commons-lang3 transitively consumed dependency is upgraded to 3.18.0 to address a known security vulnerability.

W-21574966
## [](#see-also)See Also - [APIkit for OData V4](https://docs.mulesoft.com/jp/apikit/latest/apikit-4-for-odatav4) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Response Timeout The Response Timeout policy sets the maximum duration that Omni Gateway waits for a response from an upstream service. For configuration details, see [Response Timeout Policy](https://docs.mulesoft.com/gateway/latest/policies-included-response-timeout). ## [](#february-24-2025)February 24, 2025 ### What’s New - Response Timeout policy implementation version 1.0.0 is now supported by Omni Gateway. - Response Timeout policy definition version 1.0.0 is now supported by Omni Gateway. # REST Connect Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) **Guide:** [Convert an API specification to a Connector Using REST Connect](https://docs.mulesoft.com/jp/exchange/to-deploy-using-rest-connect) The REST Connect connector generator converts an API specification (RAML 1.0, OAS2, or OAS3) to a connector that you can use in a Mule application. For more information, see [Convert an API specification to a Connector Using REST Connect](https://docs.mulesoft.com/jp/exchange/to-deploy-using-rest-connect). ## [](#1-15-83)1.15.83 **June 25, 2025** ### What’s New - The ability to generate Mule 3 (DevKit) connectors is deprecated. ## [](#1-15-80)1.15.80 **June 6, 2025** ### What’s New - The mule-oauth-module dependency is upgraded to the latest version (1.1.24) when generating Mule 4 connectors. ### Fixed Issues
Issue Resolution ID

Mule 4-generated connectors are now correctly using a proxy (if set) to perform OAuth token requests.

W-17936687
## [](#1-15-64)1.15.64 **January 23, 2025** ### Fixed Issues
Issue Resolution ID

The rest-connect library is upgraded to the latest version, which uses HTTP Connector 1.10.0 when generating Mule 4 connectors.

W-17432465, W-17071678

The AMF parser is updated to version 5.0.8.

W-17432465
## [](#1-15-61)1.15.61 **Nov 13, 2024** ### What’s New - The mule-oauth-module dependency is upgraded to the latest version (1.1.21) when generating Mule 4 connectors. ### Fixed Issues
Issue Resolution ID

Mule 4 generated connectors are now correctly tagged as Java 17 compatible when adding OAuth security to an API spec.

W-17235949
## [](#1-15-5)1.15.5 **February 6, 2024** ### What’s New - The REST Connect connector generator can generate Java 17-compatible connectors. See [Upgrading a REST Connect Generated Connector](https://docs.mulesoft.com/jp/exchange/to-deploy-using-rest-connect#upgrade-rest-connector). - Mule 4 connectors generated with REST Connect now support Transport Layer Security (TLS). See [Generating Connectors With TLS Support](https://docs.mulesoft.com/jp/exchange/to-deploy-using-rest-connect#tls-support). ## [](#1-12-5)1.12.5 **Nov 6, 2020** Moved to the latest version (3.9.12) of Devkit for generating Mule 3 connectors. ### [](#fixed-issues-4)Fixed issues - Fixed an issue in which defining the body of a request as an enum type provoked a failure to generate the Mule 3 version of the connector. (SE-17053) - Fixed an annotated parameter name bug. (SE-15190) ## [](#1-12-4)1.12.4 **Oct 22, 2020** Moved to the latest version (4.3.1) of AMF (AML Modeling Framework). ### [](#fixed-issues-5)Fixed issues Operations now expose the attributes metadata. ## [](#1-12-3)1.12.3 **Aug 19, 2020** Changed the metadata resolution mechanism. ## [](#1-12-2)1.12.2 **Aug 13, 2020** ### [](#fixed-issues-6)Fixed Issues Fixed the XXE vulnerability. (RESTC-935) ## [](#1-12-1)1.12.1 **Jul 23, 2020** The HTTP dependency for smart connectors is updated to the latest version. ## [](#1-12-0)1.12.0 **June 28, 2020** ### [](#new-features)New Features Added support for OAS3 specifications. ## [](#1-11-3)1.11.3 **May 4, 2020** ### [](#new-features-2)New Features Moved to the latest AMF version (4.1.0-0) ### [](#fixed-issues-7)Fixed Issues - Fixed annotated parameter name bug. - Fixed pluralization/singularization issues. ## [](#1-11-2)1.11.2 **Apr 16, 2020** ### [](#fixed-issues-8)Fixed Issues Upgraded outdated dependencies and solved vulnerabilities. ## [](#1-11-1)1.11.1 **Apr 7, 2020** ### [](#fixed-issues-9)Fixed Issues Upgraded outdated dependencies and solved vulnerabilities. ## [](#1-11-0)1.11.0 **Apr 1, 2020** ### [](#new-features-3)New Features Allow users of the generated connector to define a custom response timeout. ## [](#1-10-18)1.10.18 **Mar 19, 2020** Moved to the latest AMF version and adapted to its API changes that supports OAS3 API specs. ### [](#fixed-issues-10)Fixed Issues Support cases where an OAS specification does not define media type for a payload.(SE-14691) ## [](#1-10-17)1.10.17 **Feb 28, 2020** Moved to the latest AMF version. ### [](#fixed-issues-11)Fixed Issues Now using AMF’s compact JSON Schema generation to avoid generating huge schema in some cases. ## [](#1-10-16)1.10.16 **Feb 17, 2020** ### [](#fixed-issues-12)Fixed Issues Fixed 'Billion Laughs' vulnerability. ## [](#1-10-15)1.10.15 **Feb 12, 2020** ### [](#fixed-issues-13)Fixed Issues Fixed a vulnerability in resource loaders. ## [](#1-10-14)1.10.14 **Jan 31, 2020** ### [](#fixed-issues-14)Fixed Issues Fixed XXE vulnerability (RESTC-857). ## [](#1-10-13)1.10.13 **Dec 30, 2019** ### [](#fixed-issues-15)Fixed Issues - Added a parameter that allows customizing the DW expression used to renew the OAuth tokens (SE-14290) - Moved request streaming mode parameter to advanced tab (RESTC-833) - Fixed security scheme flow naming issue. ## [](#1-10-12)1.10.12 **Dec 12, 2019** Moved to AMF latest version (4.0.3). ### [](#fixed-issues-16)Fixed Issues - Optimized primitive type source generation. - Reduced JSONSchema generation. - Added support for base64 strings as primitive types. - Added support for all primitive types. ## [](#1-10-11)1.10.11 **Oct 17, 2019** ### [](#fixed-issues-17)Fixed Issues - Removed legacy Java SDK code. - Log connector GAV when metadata fails to load. ## [](#1-10-10)1.10.10 **Oct 17, 2019** - Update AMF to its latest version. - Update RAML Parser to its latest version. ### [](#fixed-issues-18)Fixed Issues - Changed all wire logging log level to debug (SE-13197). - Updated refresh token only for certain status codes (SE-13224). - Avoid generating huge JSON schemas that can break the extension model generation or make it take too long. ## [](#1-10-9)1.10.9 **Sep 17, 2019** ### [](#fixed-issues-19)Fixed Issues - Allow user to decide which logs to show in the Mule app when using a DevKit connector (SE-13197). - Sanitize user input when generating DevKit connectors to avoid security risks (RESTC-770 & RESTC-771). - Fixed several errors that would not allow the user to generate a connector from a valid API spec (SE-12563, SE-13114, SE-12870 & SE-12852). ## [](#1-10-8)1.10.8 **Aug 26, 2019** - Update RAML Parser to its latest version. - Update AMF to its latest version. - Update generated smart connectors HTTP and OAUTH dependencies to its latest versions. ## [](#1-10-7)1.10.7 **Aug 8, 2019** ### [](#fixed-issues-20)Fixed Issues Sanitized DevKit connectors display names (SE-12525). OAuth tokens are not being refreshed in generated Smart Connectors (RESTC-714). ## [](#1-10-6)1.10.6 **Jul 31, 2019** ### [](#fixed-issues-21)Fixed Issues - Skip parsing of RAML 0.8 specs when using RAMLParser because the format is not supported. - Default values should not get quotation marks (RESTC-682). - Fixed error with RAML specs that use singularize (RESTC-679). - Fixed XXE vulnerability (RESTC-734). ## [](#1-10-5)1.10.5 **Jul 4, 2019** ### [](#fixed-issues-22)Fixed Issues - Trim Project Description in POM file to 250 characters (SE-12309). - Generate all declared UriParms for OAS specs (RESTC-707). ## [](#1-10-4)1.10.4 **Jun 19, 2019** ### [](#fixed-issues-23)Fixed Issues - Use API displayName in operations for smart connectors (SE-11996). - Sanitize reserved parameter names for smart connectors (SE-11578). ## [](#1-10-3)1.10.3 **Jun 7, 2019** ### [](#fixed-issues-24)Fixed Issues This release fixes a bug. ## [](#1-10-2)1.10.2 **Jun 6, 2019** ### [](#fixed-issues-25)Fixed Issues This release fixes several bugs. ## [](#1-10-1)1.10.1 **Feb 12, 2019** ### [](#fixed-issues-26)Fixed Issues This release fixes a bug where the connector artifact was not being generated. ## [](#1-10-0)1.10.0 **Feb 12, 2019** ### [](#new-features-4)New Features Using the latest AMF release (3.1.6) ### [](#fixed-issues-27)Fixed Issues - Fixed maven-install-plugin compiling (RESTC-521). - Reduced generated elements as they are no longer needed (RESTC-521). - Fixed error messages for invalid specs/parsers. ## [](#1-9-4)1.9.4 **Jan 28, 2019** ### [](#fixed-issues-28)Fixed Issues This release solves performance issues of the generated Mule 4 connectors. ## [](#1-9-3)1.9.3 **Jan 28, 2019** ### [](#fixed-issues-29)Fixed Issues This release fixes several bugs. ## [](#1-9-2)1.9.2 **Jan 17, 2019** ### [](#fixed-issues-30)Fixed Issues - Added support for sending arrays as query params (SE-10282). - Pass through security schemes are now generated properly for Smart Connectors (SE-10324). ## [](#1-9-1)1.9.1 **Jan 17, 2019** ### [](#fixed-issues-31)Fixed Issues This release fixes several bugs. ## [](#1-9-0)1.9.0 **Nov 20, 2018** ### [](#new-features-5)New Features - Added request streaming mode config for Mule 4 Connectors (RESTC-501). - Enhanced multipart support for Mule 3 and Mule 4 Connectors by annotations (RESTC-502). - Added default value support for enums (RESTC-504). - Enhanced sanitization for Java Strings (RESTC-376). - Added a better way of generating temporal JSON schema names. - Added supportability docs. - Added parallel testing for the CI environment in order to speed up builds. ### [](#fixed-issues-32)Fixed Issues - Added a test case for this issue (SE-9268) - Fixed errors in multipart requests for Mule 3 (RESTC-502). - RAML 0.8 exception format is now the same for RAMLParser and AMF. ## [](#1-8-0)1.8.0 **Oct 17, 2018** ### [](#new-features-6)New Features - Specify a default mediaType annotation (RESTC-20). - Handle RAMLs that have parameters with similar names on the generation of Mule 3 connectors (RESTC-280). - Generate pojos correctly when using RAML Parser (RESTC-455 & RESTC-459). - Added support for ApiKey security schemes for OAS (RESTC-479). - Generate nicer and shorter operation names for OData specs (RESTC-480). - Sanitize GAV and string that could break the generated POM. - Added a POM check in order for Rest connect to fail when an invalid POM is generated. ### [](#fixed-issues-33)Fixed Issues - Error generating connector: Multiple entries with same key (RESTC-298). - StackOverflowError with Square API in Mule 3 (RESTC-314). - Error generating Mule 3 Connector for New Relic API (RESTC-345). - Error validating examples for OData OAS spec (RESTC-421). - Default value for Enums causes Dev Kit Connector generation to fail (RESTC-458). - Avoid failing when generating schemas for operations that have long names (RESTC-480). - Rest Connect does not support assets with names with non-latin characters (RESTC-495). - OAuth grants not working when proxy is null (RESTC-507). - Escape paths (SE-9084). ## [](#1-7-0)1.7.0 **August 24, 2018** This release incorporates the following improvements: - Uses the latest version of AMF (1.8.0) - Adds an annotation that lets users select which security scheme to use for an operation when creating a flow for Smart Connectors - Fixes DevKit connectors signature to work properly - Improves error messages when Rest Connect fails generating Mule 4 connectors - Exchange improvements: Moves error email management to the Rest Connect Service ### [](#fixed-issues-34)Fixed Issues - Parameters defined for pass through or custom authentication schemes are now sent correctly - Fixed error that caused some generated smart connectors to not be able to be included in a project - Fixed some string sanitization issues ## [](#1-6-2)1.6.2 **August 6, 2018** ### [](#fixed-issues-35)Fixed Issues - Types defined using XML Schemas work properly for Mule 4 Connectors ## [](#1-6-1)1.6.1 **July 27, 2018** ### [](#fixed-issues-36)Fixed Issues - Types defined using XML Schemas work properly for Mule 4 Connectors ## [](#1-6-0)1.6.0 **July 26, 2018** This release incorporates the following improvements: - Implemented conversion for OAS 2.0. - Updated to AMF Parser v1.7.1. - Supporting external files references for JSON and XSD schemas. - Supporting inner references for JSON and XSD schemas. ### [](#fixed-issues-37)Fixed Issues - Set default base path when the RAML does not provide one. - Failing to generate a connector when the API defines a JSON schema using AMF. - Failing to resolve a type defined using a trait when using. - Failing with duplicated parameters. - Failing with elements with the same name within XSD Schemas. - Failing when using two security schemes of the same type. ## [](#1-5-0)1.5.0 **June 28, 2018** This release adds support for OData Specs, Proxies, and Enums. ### [](#fixed-issues-38)Fixed Issues - Fixed string sanitization issues. ## [](#1-4-1)1.4.1 **May 29, 2018** This is a HotFix release. ### [](#fixed-issues-39)Fixed Issues - Pass-through security scheme header did not work under certain conditions. (RESTC-410) ## [](#1-4-0)1.4.0 **May 24, 2018** This release includes support for complex multipart requests containing parts with different types. Additionally, it now supports multilevel objects for sending form URL encoded requests. ### [](#fixed-issues-40)Fixed Issues - Added new Resource Loader for AMF parser to support Exchange Modules. - Added support for array of arrays in DevKit connectors. (RESTC-405) - Added support for invalid base URIs. (RESTC-356) - Created JAR files correctly on Windows. (RESTC-330) - Encapsulated POJO generation errors. - Fixed error generating POJOs on Windows. (RESTC-392) - Fixed illegal argument exception. (RESTC-365) - Fixed StringOutOfRange exception. - Moved to AMF parser 1.3.3. - Moved to latest version of Java RAML parser. (RESTC-381) - Removed unused Manifest from Smart Connectors JAR. - Updated Extensions Maven Plugin version to fix packaging in Windows. (RESTC-393) ## [](#1-3-3)1.3.3 **April 27, 2018** This is a HotFix release. ### [](#fixed-issues-41)Fixed Issues - Fixed "scopes" parameter in Smart Connectors for OAuth2 Schemes without defined scopes. ## [](#1-3-2)1.3.2 **April 17, 2018** This is a HotFix release. ### [](#fixed-issues-42)Fixed Issues - Fixed Mule 3 Connectors with several security schemas not being generated. ## [](#1-3-1)1.3.1 **April 17, 2018** This is a HotFix release. ### [](#fixed-issues-43)Fixed Issues - Fix bug occurring when an OAuth2 scheme had scopes defined. - Performance improvement: Building Smart Connector merged security schema only once. ## [](#1-3-0)1.3.0 **April 13, 2018** This release includes support for custom security schemes. Connectors will be generated based on security schemes defined in an API specification. ### [](#fixed-issues-44)Fixed Issues - Fixed support for securedBy nodes. - Fixed several issues of Mule 3 connector generation with a proper string sanitization. ## [](#1-2-11)1.2.11 **March 1, 2018** This release fixes a bug. ### [](#fixed-issues-45)Fixed Issues - Fixed Pass-through authentication for Mule 3 connectors. ## [](#1-2-10)1.2.10 **February 29, 2018** This release fixes a bug. ### [](#fixed-issues-46)Fixed Issues - Fixed an issue to use the correct parameter name to make requests. ## [](#1-2-9)1.2.9 February 23, 2018 This release fixes a bug. ### [](#fixed-issues-47)Fixed Issues - Avoid NPE when display name is not present in RAML. ## [](#1-2-8)1.2.8 February 23, 2018 This release fixes a bug. ### [](#fixed-issues-48)Fixed Issues - Added support for Mule 4 Connectors to have a default output type. ## [](#1-2-7)1.2.7 February 6, 2018 This release fixes a bug. ### [](#fixed-issues-49)Fixed Issues - REST Connect v1.2.7 now supports use with the Windows file system. ## [](#1-2-6)1.2.6 February 1, 2018 This release fixes a bug. ### [](#fixed-issues-50)Fixed Issues - Using URL-encoded only inside Smart Connectors. ## [](#1-2-5)1.2.5 February 1, 2018 This release provides a bug fix. ### [](#fixed-issues-51)Fixed Issues - Fixed the media type for a form URL-encoded use case. ## [](#1-2-4)1.2.4 January 30, 2018 This release provides a bug fix. ### [](#fixed-issues-52)Fixed Issues - Removed unsupported modes for Basic Auth and Passthrough. ## [](#1-2-3)1.2.3 January 25, 2018 REST Connect v1.2.3 provides the following features: - Added Friendly Name support for operations and parameters by using the operationName and parameterName annotations on the rest-connect library. - Added support for OPTIONS and HEAD HTTP verbs. ### [](#fixed-issues-53)Fixed Issues - Support for placeholders in the baseUri. - Improved error messages for duplicated operations or parameters. - Fixed outOfMemoryError when generating certain Mule 3 connectors. - Fixed error generating Mule3 connector when the RAML included a dot in its title. - Sanitized some property names that could break the build of Mule 3 connectors. ## [](#1-2-2)1.2.2 December 16, 2017 This release provides a bug fix. ### [](#fixed-issues-54)Fixed Issues REST Connect v1.2.2 now supports the PATCH method and properly sends the payload as a JSON rather than as a String. ## [](#1-2-1)1.2.1 December 16, 2017 Version 1.2.1 supports Java RAML Parser 1.0.16. ## [](#1-2-0)1.2.0 November 18, 2017 Version 1.2.0 supports the following security schemes defined in RAML v1.0: - OAuth2 - Authorization code - Digest authentication - Pass through ## [](#1-1-0)1.1.0 October 2, 2017 Version 1.1.0 supports creating Mule 3 connectors. When an API specification publishes to Exchange, REST Connect generates two connectors: one for Mule 4 and the other for Mule 3. ### [](#version-1-1-0-fixes)Version 1.1.0 - Fixes REST Connect v1.1.0 now generates a connector properly whether a description is present or not. In REST Connect v1.0.0, if a description was not provided, REST Connector was unable to generate a connector properly. ## [](#1-0-0)1.0.0 July 28, 2017 Version 1.0.0 provides the following features: - Transforms a RAML 1.0 specification into a connector in Design Center. - Support for unauthorized requests, basic authentication, and OAuth2 (Client Credentials). - Support for query parameters, URI parameters, and headers as input attributes. - Support for metadata defined as RAML datatypes, XML schemas, or JSON schemas. - Inference of operation names given their parameters. ### [](#known-issues)Known Issues - A RAML with the following type definition is not supported: ```text types: RecursiveType: type: object properties: aString: type: RecursiveType description: This modifies the reference and causes a stack overflow error. ``` - No support for connectivity testing in the configuration for Design Center. - REST Connect doesn’t generate friendly names for input attributes. - Connector for Mule 3.x is not supported. - Custom SSL certificates are not supported. ## [](#see-also)See Also - [Anypoint Exchange](https://docs.mulesoft.com/jp/exchange/) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # REST Proxies ## [](#3-2-2)3.2.2 **October 24, 2024** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### What’s New - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.10.1. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#3-2-1)3.2.1 **August 5, 2024** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements)New Features and Enhancements - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.3. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). - APIkit for Mule 4 has been upgraded to version 1.10.4. For more information about the APIkit release, see [APIkit Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-release-notes). ## [](#2-2-1)2.2.1 **August 5, 2024** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.3. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). - APIkit for Mule 4 has been upgraded to version 1.10.4. For more information about the APIkit release, see [APIkit Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-release-notes). ## [](#3-2-0)3.2.0 **February 7, 2024** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-3)New Features and Enhancements - This proxy version is now compatible with Java 17. - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.0. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). - APIkit for Mule 4 has been upgraded to version 1.10.2. For more information about the APIkit release, see [APIkit Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-release-notes). ## [](#2-2-0)2.2.0 **February 7, 2024** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-4)New Features and Enhancements - This proxy version is now compatible with Java 17. - HTTP Connector upgraded to version 1.9.0. - APIkit for Mule 4 has been upgraded to version 1.10.2. For more information about the APIkit release, see [APIkit Release Notes](https://docs.mulesoft.com/jp/release-notes/apikit/apikit-release-notes). ## [](#3-1-6)3.1.6 **June 9, 2023** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - APIkit upgraded from version 1.7.0 to version 1.9.0. ## [](#3-1-5)3.1.5 **November 17, 2022** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-6)New Features and Enhancements - HTTP Connector upgraded from version 1.6.0 to version 1.7.2. ## [](#3-1-4)3.1.4 **October 11, 2022** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-7)New Features and Enhancements - APIkit upgraded from version 1.5.3 to version 1.7.0. ### [](#fixed-issues)Fixed Issues - Parsing of unindented JSON files for OAS API Proxies failed in deployment. ## [](#3-1-3)3.1.3 **Aug 10, 2022** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.1** ### Fixed Issues

Issue

ID

The published 3.1.2 artifact displayed the wrong version format in API Manager. Version 3.1.3 displays the correct version format.

W-11580215
## [](#3-1-2)3.1.2 **June 1, 2022** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-3)Fixed Issues - Performing a POST request when the implementation times out no longer causes the original payload to be returned in the response. ## [](#3-1-1)3.1.1 **December 7, 2021** ### [](#new-features-and-enhancements-8)New Features and Enhancements - HTTP Connector upgraded from version 1.5.25 to version 1.6.0. ## [](#3-1-0)3.1.0 **February 02, 2021** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-9)New Features and Enhancements - APIkit upgraded from version 1.3.17 to version 1.4.2. - Added support for OAS 3.0. ### [](#fixed-issues-4)Fixed Issues - The APIkit attributes validator was causing Heap memory leak issues. ## [](#3-0-2)3.0.2 **November 02, 2020** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-10)New Features and Enhancements - APIKit upgraded from version 1.3.11 to version 1.3.17. ### [](#fixed-issues-5)Fixed Issues - The REST Proxy was incorrectly parsing an OpenAPI JSON definition containing an URL query parameter with datatype int64 as string and not int. - The `Content-Length` header in the incoming request was not reaching the backend. ## [](#3-0-1)3.0.1 **August 12, 2020** ### [](#minimum-mule-version-13)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-6)Fixed Issues - When no cipher suite is selected for the TLS configuration in Secret Manager, the proxy is generated with `enabledCipherSuites=""`. This issue caused all requests to fail. (SE-15303) ## [](#3-0-0)3.0.0 **Apr 30, 2020** ### [](#minimum-mule-version-14)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-11)New Features and Enhancements - HTTP Connector upgraded from version 1.5.7 to version 1.5.17. - Several performance improvements introduced. - Added annotation to [ignore base path](#api-manager::configure-uri-template-regex.adoc#when-to-use-ignoringbasepath) when applying Resource-Level policies. ### [](#fixed-issues-7)Fixed Issues - When an HTTP request with an encoded path was processed, a `path not found` error occurred. The encoded path was first decoded and then encoded again, thereby modifying the original path in some cases. ## [](#2-1-2)2.1.2 **December 14, 2021** ### [](#minimum-mule-version-15)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-12)New Features and Enhancements - APIKit upgraded from version 1.3.11 to version 1.3.17. ### [](#fixed-issues-8)Fixed Issues - The REST Proxy was incorrectly parsing an OpenAPI JSON definition containing an URL query parameter with datatype int64 as string and not int. - The `Content-Length` header in the incoming request was not reaching the backend. ## [](#2-1-1)2.1.1 **Apr 30, 2020** ### [](#minimum-mule-version-16)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-13)New Features and Enhancements - HTTP Connector upgraded from version 1.5.7 to version 1.5.17. - Several performance improvements introduced. ### [](#fixed-issues-9)Fixed Issues - When an HTTP request with an encoded path was processed, a `path not found` error occurred. The encoded path was first decoded and then encoded again, thereby modifying the original path in some cases. ## [](#2-1-0)2.1.0 **September 3, 2019** ### [](#minimum-mule-version-17)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-14)New Features and Enhancements - HTTP Connector upgraded from version 1.4.0 to version 1.5.7. - Performing validations for current request is now configurable. ### [](#fixed-issues-10)Fixed Issues - Cookies for proxies are now disabled by default. To re-enable proxies: 1. Import the proxy application to Anypoint Studio, and then modify the HTTP Request configuration. 2. From **HTTP Request Configuration** > **Settings**, select the **Enable cookies** check box. - RestValidator does not correctly handle the 404 error. ## [](#2-0-0)2.0.0 **January 8, 2019** This version uses REST Validator v2.0.0 with APIKit v1.2.0. ### [](#minimum-mule-version-18)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-15)New Features and Enhancements - Introduced OAS support. - Introduced AMF parser support. - Parsers can now be configured by specifying the `implementation.api.parser` property. Permitted values inlcude: “AUTO”, “AMF”, or “RAML”. The default value is "AUTO". - When setting the `keepApiBaseUri` property to true, you can now retrieve the `baseUri` provided in the specification using the console. Otherwise, the console displays the `baseUri` of your local or CloudHub instance. The default value is "false". - Implemented the following checks: - `disableValidations` flag to enable or disable the parameters and payload validations. The default value is "false". - `queryParamsStrictValidation` flag to limit the allowed query parameters to those defined in the specifications. The default value is "false". - `headersStrictValidation` flag to limit the allowed HTTP headers to those defined in the specification. The default value is "false". ## [](#1-2-0)1.2.0 - September 3, 2019\* ### [](#minimum-mule-version-19)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-16)New Features and Enhancements - HTTP Connector upgraded from version 1.4.0 to version 1.5.7. - Performing validations for current request is now configurable. ### [](#fixed-issues-11)Fixed Issues - Cookies for proxies are now disabled by default. To re-enable proxies: 1. Import the proxy application to Anypoint Studio, and then modify the HTTP Request configuration. 2. From **HTTP Request Configuration** > **Settings**, select the **Enable cookies** check box. - RestValidator does not correctly handle the 404 error. ## [](#1-1-3)1.1.3 **Nov 1, 2018** This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.1 with APIKit v1.1.1. ### [](#new-features-and-enhancements-17)New Features and Enhancements - Implemented the following checks: - `disableValidations` flag to enable or disable the parameters and payload validations. The default value is "false". - `queryParamsStrictValidation` flag to limit the allowed query parameters to those defined in the specifications. The default value is "false". - `headersStrictValidation` flag to limit the allowed HTTP headers to those defined in the specification. The default value is "false". ### [](#known-issues)Known Issues - Because of the way the proxy URL is parsed, if duplicated paths are specified, the not duplicated portion of URL is taken into account. This occurs only for the last specified URL. ### [](#minimum-mule-version-20)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-18)New Features and Enhancements - Improved TLS configuration to simplify using custom specifications. ## [](#1-1-2)1.1.2 **May 14, 2018** This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.1 with APIKit v1.1.1. ### [](#known-issues-2)Known Issues - Because of the way the proxy URL is parsed, if duplicated paths are specified, only the last, not duplicated portion of it is taken into account. ### [](#minimum-mule-version-21)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-19)New Features and Enhancements - Mule Maven Plugin is upgraded from version 3.1.0 to version 3.1.2. ## [](#1-1-1)1.1.1 **Apr 16, 2018** This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.1 with APIKit 1.1.1. ### [](#minimum-mule-version-22)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-20)New Features and Enhancements - HTTPs request updated to include Keystore when making requests. - When a multi-part request is performed, default values are now added. ### [](#fixed-issues-12)Fixed Issues - when a multi-part request was performed, a `StreamClosedException` error is generated . - when a resource is parameterized, a "Resource not found" error is generated. ### [](#known-issues-3)Known Issues - Because of the way the proxy URL is parsed, if duplicated paths are specified, only the last, not duplicated portion of it is taken into account. ## [](#1-1-0)1.1.0 **Jan 25, 2018** This version is deprecated. Use a non-deprecated version, with OAS support. This version uses RAML Validator v1.1.0 with APIKit v1.1.0. ### [](#minimum-mule-version-23)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-21)New Features and Enhancements - Proxy refactored to enable editing using MuleSoft Anypoint Studio. - Properties are now parameterized and property names are now normalized. ### [](#fixed-issues-13)Fixed Issues - Fixed error messages after adding error handler. ### [](#known-issues-4)Known Issues - Because of the way the proxy URL is parsed, if duplicated paths are specified, the not duplicated portion of URL is taken into account. This occurs only for the last specified URL. ## [](#see-also)See Also - [HTTP Connector release notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http) - [Known Issues](https://help.salesforce.com/s/issues) # Roostify Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Roostify allows interaction with Roostify using: - Webhooks, which are callbacks that let you react to activity in Roostify. - A RESTful web API that lets operations work with data stored in Roostify. MuleSoft recommends that you install the latest version of Anypoint Studio. Guide: [Roostify Connector User Guide](https://docs.mulesoft.com/jp/roostify-connector/latest/) ## [](#1-0-0)1.0.0 **June 12, 2019** ### [](#compatibility)Compatibility
Application/Service Version

Mule

4.0.0 and later

Java

8

Roostify

v1
### [](#features)Features This connector provides access to Roostify APIs for these workflows: - Access Control - Accounts - Desktop Underwriter Report - Documents - Leads (Draft) - Loan Applications - Messages - Offerings (Draft) - Reference IDs - Service - Settings - State Changes - Status Update - Tasks - User Management - User Settings - Webhook events - Webhooks ### [](#fixed-issues)Fixed Issues First version. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # RosettaNet Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for RosettaNet (RosettaNet Connector) sends and receives RosettaNet messages using RNIF 2.00.01. The connector automatically handles send timeouts and retries, and responds to received messages with the appropriate HTTP response or signal. Users work directly with the RosettaNet message service content as an XML document. CloudHub is only supported using Object Store v2 on Mule 4.2.x and with 2.0.12 and later. Guide: [RosettaNet Connector](https://docs.mulesoft.com/rosettanet-connector/latest/) ## [](#3-1-0)3.1.0 **September 25, 2026** ### What’s New - Added support for additional PIP versions: - 3A4MG1 V11.10 - 3A6MG1 V11.00 - 3B2MG1 V11.00 - 3C3MG1 V11.00 - Added support for PIPs that provide only XSD definitions. - Added `Content transfer encoding` configuration options for S/MIME messages: - `BASE64` - `BINARY` - `QUOTED_PRINTABLE` - Added `Service-Content Compression` configuration options: - `GZIP` - `ZLIB` - `NONE` - Added migration guidance for external libraries across non-FIPS, FIPS 140-2, and FIPS 140-3 security modes. These external libraries are supported for each security mode:
Security Mode Global Configuration Default Name Required Library Maven Coordinates

non-FIPS

RosettaNet External Libs - Non FIPS

RosettaNetExternal_Libs_Non_FIPS

org.bouncycastle:bcpkix-jdk18on:1.86, org.bouncycastle:bcprov-jdk18on:1.86, org.bouncycastle:bcjmail-jdk18on:1.86, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2

FIPS 140-2

RosettaNet External Libs - FIPS 140-2

RosettaNetExternal_Libs_FIPS_140_2

org.bouncycastle:bcjmail-fips:1.0.4, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2

FIPS 140-3

RosettaNet External Libs - FIPS 140-3

RosettaNetExternal_Libs_FIPS_140_3

org.bouncycastle:bcjmail-fips:2.1.7, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2
### Compatibility
Software Version

Mule

4.6.0 and later

OpenJDK

8, 11, and 17
## [](#3-0-0)3.0.0 **May 8, 2026** ### What’s New - RosettaNet Connector now supports multiple security modes via a new global connector configuration. This configuration also supports selecting the appropriate external library based on your security mode. For more information about the supported security modes, see [Upgrading and Migrating RosettaNet Connector to Version 3.x](https://docs.mulesoft.com/rosettanet-connector/latest/rosettanet-connector-upgrade-migrate). - RosettaNet Connector now uses **jakarta.mail** dependencies instead of **javax.mail** to support updated library requirements. These external libraries are supported for each security mode:
Security Mode Global Configuration Default Name Required Library Maven Coordinates

non-FIPS

RosettaNet External Libs - Non FIPS

RosettaNetExternal_Libs_Non_FIPS

org.bouncycastle:bcpkix-jdk18on:1.84, org.bouncycastle:bcprov-jdk18on:1.84, org.bouncycastle:bcjmail-jdk18on:1.84, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2

FIPS 140-2

RosettaNet External Libs - FIPS 140-2

RosettaNetExternal_Libs_FIPS_140_2

org.bouncycastle:bcjmail-fips:1.0.4, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2

FIPS 140-3

RosettaNet External Libs - FIPS 140-3

RosettaNetExternal_Libs_FIPS_140_3

org.bouncycastle:bcjmail-fips:2.1.6, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2
Standard BouncyCastle (BC) security provider support continues for non-FIPS security modes.
- RosettaNet Connector is now FIPS 140-3 compliant, which includes: - Automatic FIPS mode detection via the `mule.security.model` system property - BouncyCastle FIPS (BCFIPS) security provider registration with safety controls - Prevention of unauthorized JVM security configuration modifications in FIPS mode - Restricted use of encryption and signature algorithms based on compliance needs
RosettaNet Connector still supports FIPS 140-2 compliance.
To upgrade from version 2.x to 3.x, see [Upgrading and Migrating RosettaNet Connector to Version 3.x](https://docs.mulesoft.com/rosettanet-connector/latest/rosettanet-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-2-0)2.2.0 **November 13, 2025** ### What’s New - RosettaNet Connector now supports the SHA256 algorithm for S/MIME message signing, managed by a new `Signing algorithm` configuration parameter that defaults to **SHA1**. - A new `Require secure transport (HTTPS)` configuration parameter is added. When enabled, all traffic uses HTTPS, and an error is generated for any delivery over an insecure channel. When HTTPS is active, the `DeliveryHeader` sets the **isSecureTransportRequired** field to **Yes**. For more information about these new features, see [RosettaNet Connector 3.1 Reference](https://docs.mulesoft.com/rosettanet-connector/latest/rosettanet-connector-reference). ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### Fixed Issues
Issue Resolution ID

The DeliveryHeader of a message no longer incorrectly returns a value of No for the isSecureTransportRequired field when HTTPS is used.

W-19771349
## [](#2-1-0)2.1.0 **October 21, 2024** ### What’s New - The keystore usage now has more validations to address reported security vulnerabilities. For more information, see [RosettaNet Connector](https://docs.mulesoft.com/rosettanet-connector/latest/). ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
## [](#2-0-22)2.0.22 **January 24, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### Fixed Issues
Issue Resolution ID

The cryptographic operations now comply with FIPS 140-2 requirements.

W-14235726
## [](#2-0-21)2.0.21 **June 8, 2023** ### What’s New - The com.fasterxml.woodstox library is upgraded to version 5.4.0 to address reported security vulnerabilities. - The org.bouncycastle library is upgraded to version 1.73. ### Compatibility
Software Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### Fixed Issues
Issue Resolution ID

The connector now has more DEBUG level logging details.

W-13552458
## [](#2-0-20)2.0.20 **September 26, 2022** ### What’s New The following libraries are upgraded to address reported security vulnerabilities: - The bcmail-jdk15on library is upgraded to version 1.70. - The jaxb-jxc library is upgraded to version 2.3.6. ### Compatibility
Software Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### Fixed Issues
Issue ID

Thread management when using the connector with multiple dynamic configurations is now improved.

W-10890706

The Action source source now preserves the HTTP headers.

W-11578185

The generation of XML documents now supports namespaces and references.

W-11638456
## [](#2-0-19)2.0.19 **January 4, 2022** ### Compatibility
Software Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9590
## [](#2-0-18)2.0.18 **December 20, 2021** RosettaNet Connector v2.0.18 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-6)Fixed Issues - Upgraded library dependencies. (CONN-9590) ## [](#2-0-17)2.0.17 **August 25, 2021** RosettaNet Connector v2.0.17 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-7)Fixed Issues - Improved the Object Store implementation to fix the issue in which an application failed to start correctly on CloudHub when it was re-deployed. (SE-22160) ## [](#2-0-16)2.0.16 **July 29, 2021** RosettaNet Connector v2.0.16 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-8)Fixed Issues - Improved the ObjectStore implementation when working on CloudHub. (SE-20832) ## [](#2-0-15)2.0.15 **July 27, 2020**
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#libraries-version-update)Libraries version update
Library Previous Version Current Version

bouncycastle

1.55

64

woodstox

5.0.3

5.3.0
## [](#2-0-14)2.0.14 **February 5, 2020** RosettaNet Connector v2.0.14 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-9)Fixed Issues - The Connectivity Parent dependency is upgraded to version 3.2.2. (CONN-4676) - The File Connector dependency used by the Rosettanet Connector is upgraded to version 1.3.2. (CONN-2522) ## [](#2-0-13)2.0.13 **January 8, 2020** RosettaNet Connector v2.0.13 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-10)Fixed Issues The locationID values on ACK Messages are now allowed as optional. (SE-13421) ## [](#2-0-12)2.0.12 **September 20, 2019** ### [](#compatibility-9)Compatibility RosettaNet Connector v2.0.12 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-11)Fixed Issues - Removed "stale" (outdated) locks from ObjectStore when running on CloudHub, in order to clear situation where the shutdown leaves the locks active. The "Stale" timeout defaults to 180 seconds, but it can be changed by using com.mulesoft.connectors.rosettanet.extension.internal.delivery.DeliveryManager.chLockStaleSeconds property. (SE-13141). - Added logic to skip retry handling during shutdown to mimimize the chance of a CloudHub ObjectStore lock being left set (SE-13141). - Reduced contention for CloudHub ObjectStore lock between runners by only obtaining a lock for retransmit check if not recently run (SE-13141). ### [](#known-issues)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-11)2.0.11 **September 11, 2019** ### [](#compatibility-10)Compatibility RosettaNet Connector v2.0.11 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-12)Fixed Issues Messages in the Action and Completion source were being accepted, but not triggering the remainder of flow. The connector was running mandatory checks on empty optional elements. Now, empty optional elements in RosettaNet headers are treated the same as missing optional elements. (SE-13123) ### [](#known-issues-2)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-10)2.0.10 **September 11, 2019** ### [](#compatibility-11)Compatibility RosettaNet Connector v2.0.10 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-13)Fixed Issues Messages in the Action and Completion source were being accepted, but not triggering the remainder of flow. The connector was running mandatory checks on empty optional elements. Now, empty optional elements in RosettaNet headers are treated the same as missing optional elements. (SE-13123) ### [](#known-issues-3)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-9)2.0.9 **September 9, 2019** ### [](#compatibility-12)Compatibility RosettaNet Connector v2.0.9 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-14)Fixed Issues Added com.mulesoft.connectors.rosettanet.extension.internal.delivery.DeliveryManager.muleLockSeconds property to control timeout (SE-12555). ### [](#known-issues-4)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-8)2.0.8 **September 6, 2019** ### [](#compatibility-13)Compatibility RosettaNet Connector v2.0.8 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-15)Fixed Issues Add com.mulesoft.connectors.rosettanet.extension.internal.delivery.DeliveryManager.muleLockSeconds property to control Mule lock timeout (SE-12555). ### [](#known-issues-5)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-8-2)2.0.8 **September 6, 2019** ### [](#compatibility-14)Compatibility RosettaNet Connector v2.0.8 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-16)Fixed Issues - Add xml:version and xml:encoding attributes to all documents written (cosmetic change) (SE-12891) - Removed unnecessary preable text with MIME headers from sent messages (cosmetic change) (SE-12509). ### [](#known-issues-6)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-7)2.0.7 **September 4, 2019** ### [](#compatibility-15)Compatibility RosettaNet Connector v2.0.7 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-17)Fixed Issues - Corrected removal of acknowledged/exceptioned actions from retry store (SE-12555) - Fixed unsigned message structures to match RosettaNet specification, with wrapping multipart/related (SE-12509) - Corrected "Missing required RN-Preamble header" error on received unsigned messages matching the specification (SE-12508). ### [](#known-issues-7)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-6)2.0.6 **September 3, 2019** ### [](#compatibility-16)Compatibility RosettaNet Connector v2.0.6 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-18)Fixed Issues - Fixed issue in failure handling after retries for CloudHub operations (SE-12555) ### [](#known-issues-8)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-5)2.0.5 **September 2, 2019** ### [](#compatibility-17)Compatibility RosettaNet Connector v2.0.5 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-19)Fixed Issues - Corrected handling of explicit Object Store configuration (SE-12552) - Implemented locking workaround for CloudHub operation with multiple workers (SE-12555) ### [](#known-issues-9)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-4)2.0.4 **August 23, 2019** ### [](#compatibility-18)Compatibility RosettaNet Connector v2.0.4 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-20)Fixed Issues Correction to generated headers to match specification requirements, for both signed and unsigned messages (SE-12509). ### [](#known-issues-10)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-3)2.0.3 **July 5, 2019** ### [](#compatibility-19)Compatibility RosettaNet Connector v2.0.3 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-21)Fixed Issues Correction to handling of PIP settings for signing only in one direction, or only for actions vs. signals (SE-12131). ### [](#known-issues-11)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - A limited selection of Cluster 3 PIPs - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a Keystore - The maximum message size of 5 MB The Mule 4 RosettaNet connector does not support: - Attachments - Flow Designer ## [](#2-0-2)2.0.2 **July 4, 2019** ### [](#compatibility-20)Compatibility RosettaNet Connector v2.0.2 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-22)Fixed Issues - Corrected handling of PIP settings for signing only in one direction, or only for actions vs. signals (SE-12131). - Fixed NullPointerException occurring on startup checking of queued messages when timed out (SE-12010). - Added acknowledgeData attribute to values supplied by Action Source, giving the MIME message sent as the acknowledgment to the received action message (SE-12307). ### [](#known-issues-12)Known Issues The Mule 4 RosettaNet connector supports only: - Asynchronous response messages - RNIF 2.00.01 - Cluster 3 PIPs (limited selection) - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a keystore - The maximum supported message size is 5 MB - No support for attachments - No support for multiple workers on CloudHub It is not supported with Flow Designer. ## [](#2-0-1)2.0.1 **May 8, 2019** ### [](#compatibility-21)Compatibility RosettaNet Connector v2.0.0 is compatible with:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#fixed-issues-23)Fixed Issues Now works with Mule 4.2.0 and Java 11. Added the following missing dependencies: org.glassfish.jaxb:jaxb-jxc:2.3.0, javax.activation:javax.activation-api:1.2.0, javax.xml.bind:jaxb-api:2.3.1, org.glassfish.jaxb:jaxb-runtime:2.3.1, com.sun.xml.bind:jaxb-xjc:2.3.0, javax.xml.bind:jaxb-api:2.3.1, com.sun.xml.bind:jaxb-impl:2.3.1, com.sun.xml.bind:jaxb-core:2.3.0 ### [](#known-issues-13)Known Issues The Mule 4 RosettaNet connector only supports: - Asynchronous response messages - RNIF 2.00.01 - Cluster 3 PIPs (limited selection) - Message signing (optional), not encryption - Certificate revocation managed directly by the user in a keystore - The maximum supported message size is 5 MB It is not supported with Flow Designer. ## [](#2-0-0)2.0.0 **June 29, 2018** This release adapts RosettaNet for use with Mule 4 and Studio 7. ### [](#compatibility-22)Compatibility RosettaNet Connector v2.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

PIP 0A1 Notification of Failure

v02.00

3A4 Request Purchase Order

v02.02

3A6 Distribute Order Status

v02.00, v02.02, v02.03

3B2 Notify of Advance Shipment

v01.00

3C3 Notify of Invoice

v01.00, v01.11
### [](#known-issues-14)Known Issues The Mule 4 RosettaNet connector supports only: - Asynchronous response messages - RNIF 2.00.01 - Cluster 3 PIPs (limited selection) - Message signing (optional), not encryption - Certificate revocation managed directly by a user in the keystore - The maximum supported message size is 5 MB It is not supported on Flow Designer. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # RPA Release Notes RPA Manager instances automatically update to the latest version available; you don’t need to perform any tasks to move to the new version. The latest versions of RPA Builder, RPA Recorder, and RPA Bot become available for download in RPA Manager as soon as they are released and you must manually update them on your local environment. ## [](#rpa-manager)RPA Manager - [RPA Manager Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-manager/rpa-manager-release-notes) ## [](#rpa-builder)RPA Builder - [RPA Builder 6.7.26 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.26-release-notes) - [RPA Builder 6.7.25 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.25-release-notes) - [RPA Builder 6.7.24 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.24-release-notes) - [RPA Builder 6.7.23 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.23-release-notes) - [RPA Builder 6.7.22 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.22-release-notes) - [RPA Builder 6.7.21 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.21-release-notes) - [RPA Builder 6.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.20-release-notes) - [RPA Builder 6.7.19 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.19-release-notes) - [RPA Builder 6.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.18-release-notes) - [RPA Builder 6.7.17 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.17-release-notes) - [RPA Builder 6.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.16-release-notes) - RPA Builder 6.7.15 Release Notes (Internal) - [RPA Builder 6.7.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.14-release-notes) - [RPA Builder 6.7.13 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.13-release-notes) - [RPA Builder 6.7.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.12-release-notes) - [RPA Builder 6.7.11 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.11-release-notes) - [RPA Builder 6.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.10-release-notes) - [RPA Builder 6.7.9 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.9-release-notes) - [RPA Builder 6.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.8-release-notes) - [RPA Builder 6.7.7 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.7-release-notes) - [RPA Builder 6.7.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.6-release-notes) - [RPA Builder 6.7.5 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.5-release-notes) - [RPA Builder 6.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.4-release-notes) - [RPA Builder 6.7.3 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.3-release-notes) - [RPA Builder 6.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.2-release-notes) - [RPA Builder 6.7.1 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.1-release-notes) - [RPA Builder 6.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.7.0-release-notes) - [RPA Builder 6.6.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.8-release-notes) - [RPA Builder 6.6.7 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.7-release-notes) - [RPA Builder 6.6.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.6-release-notes) - [RPA Builder 6.6.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.5-release-notes) - [RPA Builder 6.6.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.4-release-notes) - [RPA Builder 6.6.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.3-release-notes) - [RPA Builder 6.6.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.2-release-notes) - [RPA Builder 6.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.1-release-notes) - [RPA Builder 6.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-builder/rpa-builder-6.6.0-release-notes) ## [](#rpa-recorder)RPA Recorder - [RPA Recorder 6.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-recorder/rpa-recorder-6.6.0-release-notes) - [RPA Recorder 6.5.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-recorder/rpa-recorder-6.5.2-release-notes) - [RPA Recorder 6.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-recorder/rpa-recorder-6.5.0-release-notes) ## [](#rpa-bot)RPA Bot - [RPA Bot 1.7.24 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.24-release-notes) - [RPA Bot 1.7.23 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.23-release-notes) - [RPA Bot 1.7.22 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.22-release-notes) - [RPA Bot 1.7.21 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.21-release-notes) - [RPA Bot 1.7.20 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.20-release-notes) - [RPA Bot 1.7.19 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.19-release-notes) - [RPA Bot 1.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.18-release-notes) - [RPA Bot 1.7.17 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.17-release-notes) - [RPA Bot 1.7.16 Release Notes (Deprecated)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.16-release-notes) - [RPA Bot 1.7.15 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.15-release-notes) - [RPA Bot 1.7.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.14-release-notes) - [RPA Bot 1.7.13 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.13-release-notes) - [RPA Bot 1.7.12 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.12-release-notes) - [RPA Bot 1.7.11 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.11-release-notes) - [RPA Bot 1.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.10-release-notes) - [RPA Bot 1.7.9 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.9-release-notes) - [RPA Bot 1.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.8-release-notes) - [RPA Bot 1.7.7 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.7-release-notes) - [RPA Bot 1.7.6 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.6-release-notes) - [RPA Bot 1.7.5 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.5-release-notes) - [RPA Bot 1.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.4-release-notes) - [RPA Bot 1.7.3 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.3-release-notes) - [RPA Bot 1.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.2-release-notes) - [RPA Bot 1.7.1 Release Notes (Internal)](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.1-release-notes) - [RPA Bot 1.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.7.0-release-notes) - [RPA Bot 1.6.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.6.2-release-notes) - [RPA Bot 1.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/rpa-bot/rpa-bot-1.6.0-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Fabric Mule Action Image Synchronization To maintain compatibility and system integrity, customers using a private registry must synchronize the `rtf-mule-actions` images by the effective dates listed below. ## [](#october-3-2025)October 3, 2025 This section lists the minimum required `rtf-mule-actions` images effective from this date. - `mulesoft/rtf-mule-actions:2.0.7` - `mulesoft/rtf-mule-actions-ubi:2.0.7` ## [](#see-also)See Also - [Anypoint Runtime Fabric Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric) - [Troubleshooting Runtime Fabric with RTFCTL](https://docs.mulesoft.com/runtime-fabric/latest/troubleshoot-rtf-rtfctl) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Fabric Release Notes - Runtime Fabric - [Runtime Fabric 3.x.x Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-3.x.x) - [Runtime Fabric 2.x.x Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-2.x.x) - [Runtime Fabric 1.x.x Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes) - [Runtime Fabric Command Line Tool (rtfctl) Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes) - Runtime Fabric Appliance - [Runtime Fabric Installer Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-installer-release-notes) - [Runtime Fabric Install Scripts Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-install-scripts-release-notes) - [Runtime Fabric Command Line Tool (rtfctl) Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-command-line-tool-release-notes-appliance) - Mule Runtime Engine Patch Updates - [Mule Runtime Patch Updates Release Notes for Runtime Fabric](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-runtimes-release-notes) - Runtime Fabric Mule Action Image - [Runtime Fabric Mule Action Image](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-rtf-mule-action) For versions of Runtime Fabric that have reached [end of life](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf), see the [Anypoint Runtime Fabric Release Notes Archive](https://archive.docs.mulesoft.com/release-notes/runtime-fabric/runtime-fabric-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 1.2.x Release Notes ## [](#1-2-0)1.2.0 The Anypoint Runtime Manager Private Cloud Edition September 2015 release enables users to enhance their unified monitoring experience by easily integrating their on-premises Mule servers and API Gateways with third parties’ monitoring tools, such as Splunk & ELK, for monitoring, analytics and governance. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility Agent plugins integrations is compatible with the following runtime versions: - Runtime Manager Agent 1.2.0 and above - Availability: Cloud & On-Prem - Mule 3.6.x and above - API GW 2.1.x for API Analytics ### [](#features-and-functionality)Features and Functionality #### [](#agent-plugins-integration-splunk-log)Agent Plugins Integration (Splunk & Log) Users will now have the ability to monitor their applications with an out-of-the box integration experience for monitoring tools such as Splunk & ELK. This enables the user to have a unified view of all applications, servers, etc. #### [](#api-gateway-integration)API Gateway Integration Users now have the ability to integrate their API Gateway with Agent/ARM and pass API Metrics for analytics and governance. ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ### [](#resolved-issues)Resolved Issues - Bug fixes for error while deleting servers - Reconnection strategy for Agent - Usability improvements while creating server groups ### [](#migration-guidance)Migration Guidance See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ### [](#known-issues)Known Issues - No way to configure buffering support for Splunk from the UI. **Workaround**: Use YAML file for configuration. ### [](#support)Support No change. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 1.3.x Release Notes ## [](#1-3-1)1.3.1 Anypoint Runtime Manager version 1.3.1 is a minor release that includes performance enhancements, bug fixes, and native support for Splunk’s http event collector in our handler. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above

Availability

Cloud only

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.1.0 and above. However it is recommended that you use the latest version of Agent. Click here for the latest version of Agent.
The Runtime Manager version that is bundled as part of the Anypoint Platform Private Cloud Edition is Version 1.2.
### [](#features-and-functionality)Features and Functionality - **Splunk handler enhancement**: Added support for Splunk’s TCP and HTTP Event Collector, so Splunk users can easily and securely send events from MuleSoft’s platform into Splunk. - **JMX handler enhancements**. ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ### [](#resolved-issues)Resolved Issues Includes usability, performance enhancements, and bug fixes. - CHHYBRID-591: Applications in “Failed” state can now be started - CHHYBRID-963: User can no longer create Server Groups or Clusters if servers have different agent versions - CHHYBRID-1107: Behavioral improvements while redeploying of domains in the Runtime Manager Agent - CHHYBRID-1135: Server deletion enhancements. - CHHYBRID-1176: Users with no permission to see the “Servers” page will now be re-directed. - CHHYBRID-1180: Ability to upload large applications without affecting performance. - CHHYBRID-1198: Memory optimization while deploying an app - CHHYBRID-1209: Fixed ability to configure Plugins when Event Tracking Level is None. - CHHYBRID-1218: Fixed error when a user wants to perform an action in the deployment - CHHYBRID-1223: Fixed enabling the agent plugin for Runtime Manager Agent versions that are greater than 1.2.0 - CHHYBRID-1226: Clusters created in 1.2.0 cannot be deleted in 1.3.0 - CHHYBRID-1233: Correct positioning of Failed message when an application fails ### [](#migration-guidance)Migration Guidance No migration required. ## [](#1-3-0)1.3.0 The Anypoint Runtime Manager, V1.3, release features usability enhancements on clustering support, backend improvements to enhance performance and functionality for the upcoming releases, and bug fixes. Including, but not limited to the mule connection manager.
This release is only available for the cloud version of the Runtime Manager, accesible online through the Anypoint Platform. It’s not yet available for the On Premises version of the Runtime Manager.
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#compatibility-2)Compatibility Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above

Availability

Cloud only

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.1.0 and above. However it is recommended that you use the latest version of Agent. Click here for the latest version of Agent.
The Runtime Manager version that is bundled as part of the Anypoint Platform Private Cloud Edition is Version 1.2.0.
### [](#features-and-functionality-2)Features and Functionality #### [](#usability-enhancements-for-clustering-this-release-includes-improvements-in-clustering-support-in-arm)Usability Enhancements for Clustering: this release includes improvements in clustering support in ARM - Visibility among nodes: Users now have the ability to view any communication issues between nodes in a cluster. - Main node: Identifies the main node in a cluster. - The IP of the nodes are now visible. - Cluster deployment changes: When a node is removed from a cluster the applications will be undeployed, avoiding unexpected behaviors. #### [](#rdbms-support-beta)RDBMS support (Beta) Agent modules for Mule Runtime event tracking and API Gateway analytics, available on request. Support for MySQL, MSSQL and Oracle. ### [](#deprecated-features-or-functionality-2)Deprecated Features or Functionality None. ### [](#resolved-issues-2)Resolved Issues - SE-2861: Cannot delete disconnected servers with applications - CHHYBRID-962: User should not be able to create cluster and server groups if servers have different agent versions - CHHYBRID-1104: Cluster nodes are restarted multiple times during creation - CHHYBRID-1106: Configuration not synchronizing on server startup for groups and clusters - CHHYBRID-1113: Duplicated server name in Application panel ### [](#migration-guidance-2)Migration Guidance No migration required from older versions ### [](#support)Support No change. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 1.4.x Release Notes ## [](#1-4-1)1.4.1 Anypoint Runtime Manager version 1.4.1 is a minor release that officially GAs Unified Alerts for Cloud & Hybrid deployments. Runtime Managers (hybrid) users now have the alerts functionality and existing cloud users now have a global view of all their alerts. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above.

Availability

Cloud only.

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.2.0 and above. However it is recommended that you use the latest version of Agent. Click here for the latest version of Agent.
### [](#features-and-functionality)Features and Functionality - **Unified Alerts for Cloudhub + Anypoint Runtime Manager**: Unified event based alerts for CloudHub and Runtime Manager. It enables IT Operations users to have the ability to proactively monitor several incidents. Support for business groups enables admins to manage read & write access to alerts. See [Alerts](https://docs.mulesoft.com/jp/runtime-manager/alerts-on-runtime-manager). - **Support for static IP addresses**: Agent can now support specific static addresses. See [static IP addresses](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-allowlists#static-ip-addresses). ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ### [](#resolved-issues)Resolved Issues None. ### [](#migration-guidance)Migration Guidance No migration required. ### [](#known-issues)Known Issues - An application running on a cluster or group may not be able to send an alert when one or more of its nodes restarts. If an alert is triggered while a node is restarting, the alert will not be sent even if the node successfully comes back online. - Application with the same names deployed on different servers do not have a clear distinction while setting up alerts. - When a server group or cluster is deleted, any alerts associated with it **_need to be removed at the same time_**. If the Alerts aren’t deleted, they will NOT be triggered. ## [](#1-4-0)1.4.0 The Anypoint Runtime Manager, V1.4, release includes new functionality such as audit logging, performance enhancements, and bug fixes. It also includes an Early Access version of Alerts for Runtime Manager that is available for select beta users and available as a GA on April 23rd 2016. Additionally, once logged in to the Anypoint Platform, CloudHub and Runtime Manager users will now be able to access the console via a link that says **Runtime Manager** instead of "CloudHub", on the nav bar. ### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#compatibility-2)Compatibility Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above.

Availability

Cloud only.

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.2.0 and above. However it is recommended that you use the latest version of Agent. Click here for the latest version of Agent.
### [](#features-and-functionality-2)Features and Functionality - **Audit Logging for Runtime Manager Events:** User actions within the Anypoint Platform are now recorded and available for auditing. See [Audit Logging](https://docs.mulesoft.com/jp/access-management/audit-logging). - **Name change on homepage:** Cloudhub and Runtime Manager customers will now access the console via a link that says “Runtime Manager” instead of "CloudHub" on the nav bar. - **(Beta Users only) Unified Alerts for Cloudhub + Anypoint Runtime Manager:** Unified event based [alerts](https://docs.mulesoft.com/jp/runtime-manager/alerts-on-runtime-manager) for Cloudhub and Runtime Manager. It enables IT Operations users to have the ability to proactively monitor several incidents. Support for business groups enables admins to manage read & write access to alerts. The GA date for this feature is April 23rd 2016. ### [](#deprecated-features-or-functionality-2)Deprecated Features or Functionality None. ### [](#resolved-issues-2)Resolved Issues Includes usability, performance enhancements, and bug fixes. The main ones are listed below: - SE-3401: ARM marks applications as undeployed (Communication Issue). - CHHYBRID-1271: Deleting a cluster with a deployment throws an internal server error. - CHHYBRID-1107: Redeployment of domains results in undeployment of applications associated with the domain. - CHHYBRID-1293: Fixed behavior while deploying an application to a cluster with a failed Deployment ### [](#migration-guidance-2)Migration Guidance No migration required. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 1.5.x Release Notes ## [](#1-5-1)1.5.1 Anypoint Runtime Manager version 1.5.1 includes enhancements and bug fixes. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above.

Availability

Cloud only.

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.5.1 and above for Insight and Dashboards
### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ### [](#resolved-issues)Resolved Issues - Several Application/Server dashboards enhancements - CHHYBRID-1954: New timepicker in the applications tab of SG/Cluster Dashboard - CHHYBRID-1957: Increase applications and targets timeouts - CHHYBRID-1956: Fix "Last updated" label style in latest Chrome version - CHHYBRID-1968: Alerts now have links to the pertinent dashboards - CHHYBRID-1961: Ability to filter per resource type in alert conditions - CHHYBRID-1980: Warning in server group/Cluster page if the plugins are incompatible ### [](#migration-guidance)Migration Guidance No migration required. ### [](#known-issues)Known Issues Apps/servers report a false state of “Not Connected” state even though they are online. This is a rare event that occurs in extremely short bursts and does not affect the performance or activity of the system. It fixes itself without any intervention. ## [](#1-5-0)1.5.0 The Anypoint Runtime Manager, V1.5, release that includes new functionality such as monitoring dashboards with alerts, troubleshooting tools (insight), enhancements and bug fixes. ### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#compatibility-2)Compatibility Agent plugins integrations is compatible with the following runtime versions:

Mule

3.6.x and above.

Availability

Cloud only.

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.5.0 and above for Insight and Dashboards
### [](#features-and-functionality)Features and Functionality - **Monitoring Dashboards & Alerts**: Users who deploy their apps on servers now have the ability to monitor the performance and health of the integration applications, API proxies, servers, server groups, and clusters via [dashboards](https://docs.mulesoft.com/jp/runtime-manager/monitoring-dashboards) or [alerts](https://docs.mulesoft.com/jp/runtime-manager/alerts-on-runtime-manager), within the Anypoint Platform ([1.5.0 Runtime Manager Agent](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.5.x-release-notes#1-5-0) and above is required). - **Insight for Hybrid**: [Insight](https://docs.mulesoft.com/jp/runtime-manager/insight) gives users the ability to troubleshoot their applications for performance and health related issues at a granular level, thus enabling users to determine the root cause of an issue quickly and efficiently. Users who need this feature will need to request access, please contact your customer success representative ([1.5.0 Runtime Manager Agent](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.5.x-release-notes#1-5-0) and above is required). - **MMC to ARM Migration Scripts**: MMC users can now migrate to Runtime Manager. The documentation & scripts to facilitate this process are available in the Download section of the Support Center. ### [](#deprecated-features-or-functionality-2)Deprecated Features or Functionality None. ### [](#resolved-issues-2)Resolved Issues - SE-3766: ARM alert emails do not render HTML code correctly. - SE-3676: Start/Stop Application buttons via ARM without permissions returned an unspecific error message. - SE-3786: Can’t remove servers or applications from ARM because of some inconsistencies. - SE-3687: Servers informed DISCONNECTED status while RUNNING because of timeout issues. - CHHYBRID-1428: When a server group or cluster is deleted, any alerts associated with it need to be removed at the same time. If the Alerts aren’t deleted, they will NOT be triggered. - CHHYBRID-1737: Application with the same names deployed on different servers do not have a clear distinction while setting up alerts. ### [](#migration-guidance-2)Migration Guidance No migration required. ### [](#known-issues-2)Known Issues None ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.0.x Release Notes ## [](#2-0-0)2.0.0 Anypoint Runtime Manager version 2.0.0 includes new and granular troubleshooting functionality such as **Insight** for hybrid users, **flow management** and more granular monitoring graphs so users detect the source of their issues more quickly. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility Agent plugins integration is compatible with the following runtime versions:

Mule

3.6.x and above.

Availability

Cloud only.

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.5.0 and above for Insight and 1.6.0 and above for Flow Management and all metrics charts
### [](#features-and-functionality)Features and Functionality - **Insight for Hybrid Users**: [Insight](https://docs.mulesoft.com/jp/runtime-manager/insight) gives users the ability to troubleshoot their applications for performance and health related issues at a granular level, thus enabling users to determine the root cause of an issue quickly and efficiently. This is now available for all users. - **Flow Management**: Users will have the ability to manage their problematic flows in runtime. They can now just disable a flow without disrupting the entire application. - **Monitoring V2.0**: This release contains granular monitoring charts for metrics that are pertinent to On-Premises servers and are hence used by Hybrid users. The new charts include: - Garbage Collection - Heap/Non-Heap - Load average - Thread count. Additionally alerts have been set for Load Average and Thread count.

Flow management and monitoring V2.0 functionality is only available for integration applications deployed On-Premises, but management occurs through a cloud console.
### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.1.x Release Notes ## [](#2-1-0)2.1.0 Anypoint Runtime Manager version 2.1.0 includes shortcuts to promote hybrid applications to production, and additional configuration capabilities for these. This is yet another step to bridge the feature gap between applications deployed to CloudHub and applications deployed to servers in a hybrid modality. This release also includes significant backend improvements to boost performance and reduce response times. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility Agent plugins integration is compatible with the following runtime versions:

Mule

3.6.x and above.

Availability

Cloud only.

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.5.0 and above for Insight and 1.6.0 and above for Flow Management and all metrics charts
### [](#features-and-functionality)Features and Functionality This release introduces the following capabilities: - Improved support for promotion of hybrid applications between environment from the UI - Capability to enable and disable insights at deployment time for hybrid applications - Capability to configure the log levels at deployment time for hybrid applications - CHHYBRID-2542 Deployment partially persisted - CHHYBRID-2386 Enhance performance of the Audit Logging Aspect - CHHYBRID-2517 Add request tracing logging to the Hybrid-Console ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.10.x Release Notes ## [](#2-10-1)2.10.1 _Feb 16, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.10.1. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains no new features. ### [](#changes-in-this-release)Changes in This Release This release contains no feature changes. ### [](#fixed-issues)Fixed Issues - SE-9163: ARM REST Services returns "No application with the provided GAV could be retrieved from Exchange" when deploying app from Exchange to on-prem server ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes There are no compatibility notes in this release. ## [](#2-10-0)2.10.0 _Jan 26, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.10.0. ### [](#new-features-and-enhancements-2)New Features and Enhancements - New publicly signed certificates with two year expirations and an SHA256 signature algorithm for Root CA, Mule Manager, and Auth Proxy public endpoints. ### [](#changes-in-this-release-2)Changes in This Release - Server Down and Up Alerts now trigger after a five second grace period to avoid Alert fatigue upon quick disconnections. - Runtime Manager API v1 maximum limit increased from 50 items to 250 items. - Faster, new react-based Runtime Manager servers UI with more consistency across the entire platform. ### [](#fixed-issues-2)Fixed Issues - SE-10157: The issue where the Runtime Manager Alerts template included incorrect applications deep-link is fixed. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds Use of new publicly signed certificates requires Agents version 2.2.0+ for Mule 4.x and 1.12.0+ for Mule 3.x. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes There are no compatibility notes in this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.11.x Release Notes ## [](#2-11-4)2.11.4 July 27, 2019 This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.4. ### [](#new-features-and-enhancements)New Features and Enhancements There are no new features or enhancements in this release. ### [](#changes-in-this-release)Changes in This Release There are no changes in this release. ### [](#fixed-issues)Fixed Issues - SE-12164: Unable to deploy Mule apps type as "Examples" to Runtime Fabric with "message": "The file MUST be a jar to deploy to a 4.X target." ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes There are no compatibility notes in this release. ## [](#2-11-3)2.11.3 June 15, 2019 This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.3. ### [](#new-features-and-enhancements-2)New Features and Enhancements There are no new features or enhancements in this release. ### [](#changes-in-this-release-2)Changes in This Release Previous to this release, multiple Mule runtime engines (Mules) sharing the same identity were able to connect to the Anypoint control plane when a connection request happened concurrently. Starting with this release, **only one Mule** is allowed to connect to the control plane per server. Concurrent Mule connections will no longer be allowed to connect and provide status, which means all but one of the concurrent Mules will become unmanaged. The Mule that connects first is able to send information over and sync (in some cases this can mean re-deploying applications that are not actually running on the connected Mule). If the initial Mule then becomes disconnected, there is the potential that the other Mules may connect before the initial Mule can re-connect. This means that the sync process occurs from the current state of the newly connected Mule. This change is beneficial to prevent the possibility of: - Multiple instances of an application running across two or more Mule runtime engines unintentionally - Inaccurate statuses for the Mule runtime engine and/or applications ### [](#fixed-issues-2)Fixed Issues - The issue where multiple connections of different Mule runtime engines were accepted with the same certificate in certain scenarios. - Hybrid scheduler is removed after the flow name changes. \[SE-11484\] - Unable to add email address starts with # in alert configuration. \[SE-11733\]. - Unable to create a cluster from the UI when runtimes don’t report IP addresses. \[SE-12000\] ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes There are no compatibility notes in this release. ## [](#2-11-2)2.11.2 May 18, 2019 This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.2. ### [](#new-features-and-enhancements-3)New Features and Enhancements There are no new features or enhancements in this release. ### [](#changes-in-this-release-3)Changes in This Release This release contains no feature changes. ### [](#fixed-issues-3)Fixed Issues - The issue where orphan deployments were left in the database when concurrent deployment requests were executed is fixed. ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-3)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-3)Compatibility Notes There are no compatibility notes in this release. ## [](#2-11-1)2.11.1 May 4, 2019 This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.1. ### [](#new-features-and-enhancements-4)New Features and Enhancements There are no new features or enhancements in this release. ### [](#changes-in-this-release-4)Changes in This Release This release contains no feature changes. ### [](#fixed-issues-4)Fixed Issues - Expired Cert incorrect error message when trying to renew certificates for a cluster with an invalid Runtime Manager agent version ### [](#known-limitations-and-workarounds-4)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-4)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-4)Compatibility Notes There are no compatibility notes in this release. ## [](#2-11-0)2.11.0 _Mar 23, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.0. ### [](#new-features-and-enhancements-5)New Features and Enhancements - Environment information is now being sent to Audit Log for Hybrid Deployments. ### [](#changes-in-this-release-5)Changes in This Release This release contains no feature changes. ### [](#fixed-issues-5)Fixed Issues - SE-10644: Re-deployment fails in hybrid with "Duplicate key polling://snippet-pollerFlow/" error ### [](#known-limitations-and-workarounds-5)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-5)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-5)Compatibility Notes There are no compatibility notes in this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.12.x Release Notes ## [](#2-12-0)2.12.0 August 24, 2019 This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.12.0. ### [](#new-features-and-enhancements)New Features and Enhancements There are no new features or enhancements in this release. ### [](#changes-in-this-release)Changes in This Release - Atomic schedulers modifications: For Runtime Manager agent versions later than 1.14.0 and 2.4.0, the Control Plane modifies schedulers' settings atomically so that other schedulers deployed to the same Mule runtime engine are not triggered. - Alerts Pages rewritten for faster performance and consistent experience across Runtime Manager. - Show unexpected deployment error in application details page for Runtime Fabric deployments. ### [](#fixed-issues)Fixed Issues - SE-11959: Fixed incorrect Audit Logs **Environment** column for Runtime Fabric deployments - SE-12150: Added descriptive tooltip on restriction for **Deploy Application** button that is disabled in DESIGN environments ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes There are no compatibility notes in this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.2.x Release Notes ## [](#2-2-0)2.2.0 Anypoint Runtime Manager version 2.2.0 includes new functionality for monitoring flows. ### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#compatibility)Compatibility Agent plugins integration is compatible with the following runtime versions:

Mule

3.6.x and above.

Availability

Cloud only.

API GateWay

2.x and above for API Analytics

Runtime Manager Agent

1.5.0 and above for Insight and 1.6.0 and above for Flow Management and all metrics charts
### [](#features-and-functionality)Features and Functionality This release introduces the following capabilities: - Flow Monitoring: Users now have the ability to monitor key metrics in each Mule flow over time with the help of monitoring charts for flow metrics. This release includes metrics for: - Mule messages - Errors - Response time
Flow Monitoring is only available for integration applications deployed On-Premises, but management occurs through a cloud console.
### [](#deprecated-features-or-functionality)Deprecated Features or Functionality None. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.3.x Release Notes ## [](#2-3-1)2.3.1 **May 31, 2017** This release contains the following enhancement:

Feature

Description

Restart and shutdown hybrid servers

Runtime Manager enables you to start, shutdown, and restart servers running in a hybrid deployment scenario.
### [](#hardware-and-software-requirements)Hardware and Software Requirements To use Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

1.7.0 is required when specifying clustering ports, retrieving application uptime and Mule runtime shutdown and restart.

Mule

3.6.x and above

API Gateway

2.x and above for API Analytics
### [](#deprecated-features-or-functionality)Deprecated Features or Functionality No change. ### [](#resolved-issues)Resolved Issues No change. ### [](#migration)Migration No change. ### [](#known-issues)Known Issues None. ### [](#support)Support No change. ## [](#2-3-0)2.3.0 This release contains the following new features and enhancements:

Feature

Description

Application uptime information

Runtime Manager displays the amount of time an application has been running. This information is displayed on the Settings page and information panel for each application.

View and edit server properties on hybrid servers

Runtime Manager enables you to define, view, and edit properties for servers running in a hybrid deployment scenario. Properties are defined as key/value pairs on the Manage Servers page.

Specify the IP address and port for a cluster node

Runtime Manager enables you to specify the IP address and port of a cluster running in a hybrid deployment scenario. To use this feature, your server must be running Mule runtime, version 3.8.5 or greater.
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements To user Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility-2)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

1.7.0 is required when specifying clustering ports, retrieving application uptime and Mule runtime shutdown and restart.

Mule

3.6.x and above

API Gateway

2.x and above for API Analytics
### [](#deprecated-features-or-functionality-2)Deprecated Features or Functionality No change. ### [](#resolved-issues-2)Resolved Issues No change. ### [](#migration-2)Migration No change. ### [](#known-issues-2)Known Issues None. ### [](#support-2)Support No change. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.4.x Release Notes ## [](#2-4-3)2.4.3 **August 26, 2017** This release contains the following enhancements:

Enhancement

Description

Internal enhancements

Contains internal changes that improve system performance and stability.

Flow Management

Adds Flow Management capabilities to Anypoint Platform Private Cloud Edition
### [](#hardware-and-software-requirements)Hardware and Software Requirements To use Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

1.7.0 is required when specifying clustering ports, retrieving application uptime and Mule runtime shutdown and restart.

Mule

3.6.x and above

API Gateway

2.x and above for API Analytics
### [](#deprecated-features-or-functionality)Deprecated Features or Functionality No change. ### [](#resolved-issues)Resolved Issues No change. ### [](#migration)Migration No change. ### [](#known-issues)Known Issues None. ### [](#support)Support No change. ## [](#2-4-0)2.4.0 **June 24, 2017** This release contains the following enhancement:

Feature

Description

Server Properties

Runtime Manager enables you to view additional information about a remote server, including: the server operating system, VM vendor, and license expiration date. See View Server Information (Hybrid).
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements To use Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility-2)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

1.7.0 is required when specifying clustering ports, retrieving application uptime and Mule runtime shutdown and restart.

Mule

3.6.x and above

API Gateway

2.x and above for API Analytics
### [](#deprecated-features-or-functionality-2)Deprecated Features or Functionality No change. ### [](#resolved-issues-2)Resolved Issues No change. ### [](#migration-2)Migration No change. ### [](#known-issues-2)Known Issues None. ### [](#support-2)Support No change. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.5.x Release Notes ## [](#2-5-0)2.5.0 **September 9, 2017** This release contains the following enhancements:

Enhancement

Description

Increase application file size

The maximum application file size increased from 100MB to 200MB.
### [](#hardware-and-software-requirements)Hardware and Software Requirements To use Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

1.7.0 is required when specifying clustering ports, retrieving application uptime and Mule runtime shutdown and restart.

Mule

3.6.x and above

API Gateway

2.x and above for API Analytics
### [](#fixed-issues)Fixed Issues - Resolved issue where servers could not be deleted using Runtime Manager ### [](#known-issues)Known Issues None. ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality No change. ### [](#migration)Migration No change. ### [](#support)Support No change. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.6.x Release Notes ## [](#2-6-1)2.6.1 **November 18, 2017** This release contains the following enhancements:

Enhancement

Description

Deploy an application or example from Exchange

Runtime Manager enables you to deploy a Mule application or example directly from Anypoint Exchange to a server, server group, or cluster.

Mule 4 support

This release provides support for the Mule 4 Early Access release.
### [](#hardware-and-software-requirements)Hardware and Software Requirements To use Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

Version 1.9.0 or later is required for all new features.

Mule

3.9.0 and later is required for the application properties feature.

API Gateway

2.x and above for API Analytics
### [](#fixed-issues)Fixed Issues The following issues were fixed in this release: - Fixed issue where Runtime Manager was unable to stop Mule4 applications. - Fixed issue where Runtime Manager was unable to delete Mule 4 applications from serverGroups or Clusters - Fixed issue where clusterization was working with the Mule 4 Runtime Manager Agent. ### [](#known-issues)Known Issues - Schedule Management is not supported on Mule 4 EA. - Autodiscovery of server properties is not supported on Mule 4 EA. - Application Properties are not supported on Mule 4 EA. ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality No change. ### [](#migration)Migration No change. ### [](#support)Support No change. ## [](#2-6-0)2.6.0 **October 21, 2017** This release contains the following enhancements:

Enhancement

Description

Autodiscovery of remote server properties

Enables Runtime Manager to display environment and system properties of remote servers and Mule runtimes. This feature is applicable to hybrid deployment scenarios only.

Application properties

Enables you to set application properties from Runtime Manager during application deployment. This feature is applicable to hybrid deployment scenarios only.

Schedule management

Adds support for polls to applications deployed in a hybrid deployment scenario. The feature is only supported on single-server environments. It is not supported on servers within server groups or clusters.

Disable Insights

Adds ability to control access to the Insights component for an organization or sub-organization. To prohibit this component, contact your customer success representative.

Increased application size

Adds support for asynchronous uploads of files and increased the supported application file size from 100MB to 200MB
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements To use Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility-2)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

Version 1.9.0 or later is required for all new features.

Mule

3.9.0 and later is required for the application properties feature.

API Gateway

2.x and above for API Analytics
### [](#fixed-issues-2)Fixed Issues None. ### [](#known-issues-2)Known Issues None. ### [](#deprecated-features-or-functionality-2)Deprecated Features or Functionality No change. ### [](#migration-2)Migration No change. ### [](#support-2)Support No change. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.7.x Release Notes ## [](#2-7-0)2.7.0 **January 13, 2018** This release contains the following enhancements:

Enhancement

Description

Schedule Management for Server Groups and Clusters

Runtime Manager enables you to view and control polling elements on applications deployed to a Server Group or Cluster. See Manage Schedules for more information.

Mule 4 GA support

This release provides support for the Mule 4 GA release.
### [](#hardware-and-software-requirements)Hardware and Software Requirements To use Runtime Manager to specify a cluster IP and port in hybrid deployment scenarios, you must be running Mule runtime, version 3.8.5 or greater. ### [](#compatibility)Compatibility Mule Agent plugin integration is compatible with the following component versions:

Availability

Cloud only

Mule Agent Plugin

Version 1.9.0 or later is required for all new features.

Mule

3.9.0 and later.

API Gateway

2.x and above for API Analytics
### [](#fixed-issues)Fixed Issues The following issues were fixed in this release: **TBD** ### [](#known-issues)Known Issues **TBD** ### [](#deprecated-features-or-functionality)Deprecated Features or Functionality No change. ### [](#migration)Migration No change. ### [](#support)Support No change. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.8.x Release Notes ## [](#2-8-4)2.8.4 _May 19, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.8.4. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains the following new features: - **Server certificate renewal**: enables you to renew server certificates directly from Runtime Manager. These certificates are required for secure communication betwee Runtime Manager and the Runtime Manager Agent. This feature requires Runtime Manager Agent, version 1.10.0 and later. See [Renew Server Certificates](https://docs.mulesoft.com/jp/runtime-manager/servers-cert-renewal) for more information. ### [](#changes-in-this-release)Changes in This Release This release contains no feature changes. ### [](#fixed-issues)Fixed Issues There are no fixed issues in this release. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes - To use the new server certificate renewal feature added in this release, you must be using Runtime Manager Agent, version 1.10.0 or later. ## [](#2-8-2)2.8.2 _March 24, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.8.2. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains the following new features: - There are no new features or enhancements in this release. ### [](#changes-in-this-release-2)Changes in This Release This release contains the following change in product functionality: - Flow monitoring is disabled by default on newly deployed applications. You can enable or disable this feature as required per application. - Support for TLS v1.0 has been deprecated. Runtimes using this protocol to secure communications can no longer connect to the platform. You must upgrade to TLS v1.1 or later. ### [](#fixed-issues-2)Fixed Issues This section lists the bugs and known limitations that are fixed in this release. - Fixed issue where some specific new deployments failed to start caused by the runtime receiving empty zip files. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes There are no compatibility notes for this release. ## [](#2-8-1)2.8.1 _February 22, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.8.1. ### [](#new-features-and-enhancements-3)New Features and Enhancements There are no new features or enhancements in this release. ### [](#changes-in-this-release-3)Changes in This Release This release contains the following change in product functionality: - The maximum number of application alerts was increased from 10 to 100. ### [](#fixed-issues-3)Fixed Issues This section lists the bugs and known limitations that are fixed in the release. - Increased the maximum number of application alerts. - Fixed issue where deployments to a server group were failing. - Fixed issue related to redeployment of applications. - Incorporated multiple internal bug fixes and improvements. ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-3)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-3)Compatibility Notes There are no compatibility notes for this release. ### [](#2-8-0)2.8.0 _January 25, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.8.0. ### [](#new-features-and-enhancements-4)New Features and Enhancements This section lists the new features and enhancements in the release: - Improved errors description on alert creation. ### [](#fixed-issues-4)Fixed issues This section lists the bugs and known limitations that are fixed in the release. - Fixed multiple issues that prevented users from deleting servers from the Runtime Manager UI. - Fixed issue that prevented some users deleting applications that failed to be deployed. - Fixed issue that prevented users from deleting servers when one of its applications had configurations applied for some components. - Fixed issue where configured ip and port were not shown when users entered their cluster configuration page. - Fixed issue where maximum version was not being selected by default when users went to deploy an application via Exchange. - Fixed issue where some naming validations were not applied on cluster and server group creation. - Fixed issue where an application created with an invalid name couldn’t be deleted. - Fixed issue that prevented users from downloading their application artifact. ### [](#known-limitations-and-workarounds-4)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-4)Upgrade Requirements There are no upgrade requirements in this release. ### [](#compatibility-notes-4)Compatibility Notes There are no compatibility notes in this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager 2.9.x Release Notes ## [](#2-9-2)2.9.2 _Jan 12, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.9.2. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains no new features. ### [](#changes-in-this-release)Changes in This Release This release contains no feature changes. ### [](#fixed-issues)Fixed Issues - Redeployment of application artifacts from the UI did not pass properties to the application correctly when only changing an artifact. - Hybrid runtimes did not display the Splunk or ELK plugins tab in some scenarios. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes There are no compatibility notes in this release. ## [](#2-9-0)2.9.0 _Dec 8, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.9.0. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains the following new feature: - **Application Versioning**: This feature enables Runtime Fabric users to view the application deployment history, as well as a history of all changes made to deployed configurations. It also gives users an in-depth view of the cluster replica statuses. This feature is available only in the Runtime Manager UI and API for this release. ### [](#changes-in-this-release-2)Changes in This Release This release contains no feature changes. ### [](#fixed-issues-2)Fixed Issues - The issue where properties supplied through the UI were not propagated during restart of the application is fixed. - Unable to pull application properties from Sandbox: `Target does not exist in your organization` is fixed. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes - Application versioning is compatible with all Runtime Fabric versions. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.1.x Release Notes ## [](#1-1-1)1.1.1 _August 15, 2015_ Runtime Manager Agent 1.1.1 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL: [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.n and 3.7.n

API Gateway

2.n
### [](#fixed-in-this-version)Fixed in this Version
Issue Description

AGENT-183

ArrayIndexOutOfBoundsException when user tries to register a Mule in Runtime Manager without a name

AGENT-185

Runtime Manager Agent Administration Service API doesn’t allow inheritable fields

AGENT-195

Agent installer sets the property coreservice_base_uri in the wrapper.conf to null

AGENT-196

The postConfigure() method is invoked at the startup when the Internal Handler is not enabled

AGENT-198

Improve the configuration of the Internal Handlers

AGENT-199

Fix tracking Internal Handlers for the performance tests
### [](#known-issues)Known Issues None. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.10.x Release Notes ## [](#1-10-0)1.10.0 _May 22, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.10.0. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains the following new features or enhancements: - Adds support for renewing server certificate. This feature supports new functionality in Runtime Manager and the Runtime Manager API. - Adds logging for buffer handler instance classes. ### [](#changes-in-this-release)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues)Fixed Issues This release contains no issues fixes. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes There are no compatibility notes for this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.11.x Release Notes ## [](#1-11-3)1.11.3 _December 7, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.11.3. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains the following new features or enhancements: - Added support for flushing disk-buffered Mule events in batches of a configurable size. ### [](#changes-in-this-release)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues)Fixed Issues This release contains the following issue fixes: - Issue that caused buffered events to be discarded when using disk buffer in the scenario that buffered events exceeded in-memory limit size. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

Runtime Manager

V2.0
## [](#1-11-2)1.11.2 _November 12, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.11.2. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-2)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-2)Fixed Issues This release contains the following issue fixes: - Fixed issue where updating scheduler configurations redirected logs to mule\_ee.log instead of app logs. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

Runtime Manager

V2.0
## [](#1-11-1)1.11.1 _October 10, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.11.1 ### [](#new-features-and-enhancements-3)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-3)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-3)Fixed Issues This release contains the following issue fixes: - Disabling Insights removes remove the YAML configuration section. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-3)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-3)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

Runtime Manager

V2.0
## [](#1-11-0)1.11.0 _September 10, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.11.0. ### [](#new-features-and-enhancements-4)New Features and Enhancements This release contains no new features or enhancements: ### [](#changes-in-this-release-4)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-4)Fixed Issues This release contains the following issue fixes: - Displays the correct VM Vendor installed in the Mule Runtime in Runtime Manager - Returns the correct status response and message when trying to deploy an application with errors. - Upgrade version of several dependency libraries. - Changed default Agent truststore name from truststore.jks to anypoint-truststore.jks to avoid conflicts with application defined trust stores. ### [](#known-limitations-and-workarounds-4)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-4)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-4)Compatibility Notes There are no compatibility notes for this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.12.x Release Notes ## [](#1-12-2)1.12.2 _May 3, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 1.12.2. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues)Fixed Issues This release contains the following fixed issues: - HTTP 400 response when uploading metrics using Mule agent for flow names with non-ASCII characters. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.10.0+
## [](#1-12-1)1.12.1 _February 19, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.12.1. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-2)Changes in This Release - The API now returns the root cause when an application fails to deploy. - Application properties are now stored in the application’s `yml` descriptor instead of in the `mule-agent.yml`. - For APCE environments, trusted certificates are always used from the JKS file instead of the JVM. ### [](#fixed-issues-2)Fixed Issues This release contains the following fixed issues: - Support for the `host` property in CloudHub properties caused applications to fail to deploy. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.10.0+
## [](#1-12-0)1.12.0 _January 28, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.12.0. ### [](#new-features-and-enhancements-3)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-3)Changes in This Release - This version of Runtime Manager Agent uses a new Publicly Certified certificate and connects to two new endpoints in Anypoint Runtime Manager. - Now, when enabling a service that has a null log configuration, the Mule Agent API returns a bad request (400) instead of an internal server error (500). ### [](#fixed-issues-3)Fixed Issues This release contains no fixed issues. ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-3)Upgrade Requirements When you upgrade the agent two new endpoints for communicating with Anypoint Runtime Manager are created. Before performing the upgrade, ensure there are no networking constraints for accessing the FQDNs on port 443. For more information, see [Ports, IP Addresses, and Hostnames to Allowlist](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-allowlists).
United States EU

wss://runtime-manager.anypoint.mulesoft.com

https://data-authenticator.anypoint.mulesoft.com

wss://runtime-manager.eu1.anypoint.mulesoft.com

https://data-authenticator.eu1.anypoint.mulesoft.com
### [](#compatibility-notes-3)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.10.0+
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.13.x Release Notes ## [](#1-13-0)1.13.0 _May 31, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 1.13.0. ### [](#new-features-and-enhancements)New Features and Enhancements - Starting with Mule 3.9.3, API Manager Secrets (`clientId`, `clientSecret`, and `Proxy password`) can be stored, encrypted, in the `wrapper.conf` file when an encryption key is provided at setup time. For more information, see [API Gateway Encryption on Mule 3](https://docs.mulesoft.com/jp/mule-gateway/mule-gateway-encryption-mule3). ### [](#changes-in-this-release)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues)Fixed Issues This release contains no fixed issues. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.10.0+
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.14.x Release Notes ## [](#1-14-6)1.14.6 _October 22, 2020_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.14.6. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release)Changes in This Release This release includes no changed features. ### [](#fixed-issues)Fixed Issues This release contains the following fixed issues: - Enabled the ability to stop an application that is stuck in `Starting` status using Runtime Manager agent API. - Fixed an issue that sometimes cleared the agent configuration file. - Fixed a null pointer exception that occurred when deploying an application with logging configuration. - Fixed an issue in which starting an application resulted in a `Stopping` status in the flows. - Fixed an issue in which internal agent log messages appeared in the application logs. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-14-5)1.14.5 _July 31, 2020_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.14.5. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-2)Changes in This Release This release includes no changed features. ### [](#fixed-issues-2)Fixed Issues This release contains the following fixed issue: - Upgraded several dependency components. - Fixed an issue in which restarting a logging service caused an error message. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-14-4)1.14.4 _June 17, 2020_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.14.4. ### [](#new-features-and-enhancements-3)New Features and Enhancements The agent now supports the file protocol for application properties. If an application property is a URI with a file protocol, the agent reads the file content as the property value. This feature is disabled by default. To enable it, set the following property in `mule-agent.yaml`: services.mule.agent.application.properties.service.fileProtocolConfiguration.enabled: true For more information, see [ARM Mule Agent Plugin API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/mule-agent-plugin-api/). ### [](#changes-in-this-release-3)Changes in This Release Reordered the index of the additional Java properties in the `wrapper.conf` file with the following suffixes: - `stripquotes` - `java_version.min` - `java_version.max` ### [](#fixed-issues-3)Fixed Issues This release contains the following fixes: - Fixed an issue in which starting a Mule application after flows become unmanaged caused an error message. - Agent show descriptive message when server registration fails ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-3)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-3)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-14-3)1.14.3 _January 24, 2020_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.14.3. ### [](#new-features-and-enhancements-4)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-4)Changes in This Release - Added new modules provided by MuleSoft to the default Runtime Manager agent version 1.x ZIP distribution: - Zabbix, Graphite, and CloudWatch metrics publishers - DB and HTTP API Analytics trackers ### [](#fixed-issues-4)Fixed Issues This release contains the following fixes: - Starting and stopping applications or flows now sends logs to the correct files. ### [](#known-limitations-and-workarounds-4)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-4)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-4)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-14-2)1.14.2 _November 28, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 1.14.2. ### [](#new-features-and-enhancements-5)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-5)Changes in This Release - HTTP callbacks now include a new authentication header emitted via the WebSockets channel. - Two extra fields were added to the Mule agent REST transport endpoint. ### [](#fixed-issues-5)Fixed Issues This release contains the following fixes: - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds-5)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-5)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-5)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-14-1)1.14.1 _September 26, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 1.14.1. ### [](#new-features-and-enhancements-6)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-6)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-6)Fixed Issues This release contains the following fixes: - Fixed connection issues when using an encrypted proxy password stored in mule-agent.yml. ### [](#known-limitations-and-workarounds-6)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-6)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-6)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-14-0)1.14.0 _July 15, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 1.14.0. ### [](#new-features-and-enhancements-7)New Features and Enhancements This release contains the following new features or enhancements: - Atomic schedulers modifications: A new HTTP endpoint in the Mule Runtime Manager agent API will modify schedulers' settings atomically so that other schedulers deployed to the same Mule runtime engine are not triggered. Prior to this update, modifications to schedulers forced the synchronous trigger of the schedulers of all applications running in the same Mule runtime engine. ### [](#changes-in-this-release-7)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-7)Fixed Issues This release contains no fixed issues. ### [](#known-limitations-and-workarounds-7)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-7)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-7)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Java

JRE 1.7.0, 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.15.x Release Notes ## [](#1-15-13)1.15.13 **Sep 19, 2022** ### Fixed Issues

Issue

ID

Upgraded dependencies.

W-11747837
### Compatibility

Software

Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i v3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

v2.12.0 and later
## [](#1-15-12)1.15.12 **Jun 10, 2022** ### Fixed Issues

Issue

ID

Upgrading the Mule Agent (amc_setup -U) on Windows OS no longer throws the error message The process cannot access the file because it is being used by another process.

W-10757157
### Compatibility

Software

Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i v3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

v2.12.0 and later
## [](#1-15-11)1.15.11 **Feb 14, 2022** ### Fixed Issues

Issue

ID

Security improvements.

W-10672072
### Compatibility

Software

Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i v3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

v2.12.0 and later
## [](#1-15-10)1.15.10 **Jan 19, 2022** ### Fixed Issues

Issue

ID

Security improvements.

CHHYBRID-6687
### Compatibility

Software

Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i v3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

v2.12.0 and later
## [](#1-15-9)1.15.9 **Dec 27, 2021** ### Compatibility

Software

Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-8)1.15.8 **Dec 17, 2021** ### Compatibility

Software

Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-7)1.15.7 **Oct 29, 2021** ### Fixed Issues

Issue

ID

Forced the classloader to take the correct Bouncy Castle version to avoid a null pointer error.

SE-22243
### Compatibility

Software

Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-6)1.15.6 _Jul 16, 2021_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.15.6. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains the following enhancements: - Minor internal improvements ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-5)1.15.5 _Jun 23, 2021_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.15.5. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains the following enhancements: - Minor internal improvements ### [](#compatibility-notes-2)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-4)1.15.4 _Jun 10, 2021_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.15.4. ### [](#fixed-issues-6)Fixed Issues This release contains the following fixed issues: - Fixed an issue that made application deployments unmanaged when restarting domains. ### [](#compatibility-notes-3)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-3)1.15.3 _Jan 14, 2021_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.15.3. ### [](#fixed-issues-7)Fixed Issues This release contains the following fixed issues: - Fixed a null pointer exception that occurred when sending analytics data to an external database. - Upgraded the versions of several dependency libraries. ### [](#compatibility-notes-4)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-2)1.15.2 _Dec 11, 2020_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.15.2. ### [](#new-features-and-enhancements-3)New Features and Enhancements This release contains the following enhancements: - Minor internal improvements ### [](#compatibility-notes-5)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-1)1.15.1 _Nov 12, 2020_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.15.1. ### [](#new-features-and-enhancements-4)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release)Changes in This Release This release includes no changed features. ### [](#fixed-issues-8)Fixed Issues This release contains the following fixed issues: - Fixed an issue in which sometimes the agent configuration file was corrupted by invalid characters. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-6)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#1-15-0)1.15.0 _Oct 30, 2020_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 1.15.0. ### [](#new-features-and-enhancements-5)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-2)Changes in This Release This release includes the following changes: - End support for JRE 1.7 ### [](#fixed-issues-9)Fixed Issues This release contains the following fixed issues: - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-7)Compatibility Notes
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.16.x Release Notes ## [](#1-16-0)1.16.0 **Aug 4, 2023**
Mule Agent releases starting with 1.16.0 are only compatible with the Mule Runtime Engine versions 3.9.5-202308 and later (and viceversa). This version won’t be able to load Mule Runtime versions older than 3.9.5-202308. This is a joint release with Mule Runtime 3.9.5-202308 monthly release
### Fixed Issues

Issue

ID

Security upgrades: snakeyaml 2.0, jersey-media 2.39.1 and jackson-core 2.15.0

W-13193206, W-13078073, W-12770203

Shutdown keepalive service upon mule deletion

W-12235306
### Compatibility

Software

Version

Mule Runtime

3.9.5-202308 and later

API Gateway

2.x and later

Java

JRE 1.8.0 [Oracle, IBM, OpenJDK]

OS

MacOS 10.11.x, HP-UX 11i v3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

v2.12.0 and later
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.2.x Release Notes ## [](#1-2-0)1.2.0 _September 17, 2015_ Runtime Manager Agent 1.2.0 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL: [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.n and 3.7.n

API Gateway

2.n
### [](#features-in-this-release)Features in this Release - Support Splunk and Logs Mule Events integration - Support Splunk and Logs API Gateway Analytics Integration ### [](#fixed-in-this-version)Fixed in this Version
Issue Description

AGENT-188

Internal Message Handler for Tracking should be disabled by default

AGENT-194

Add password encryption for configurable fields

AGENT-197

Integrate Gateway Analytics collection within Runtime Manager Agent

AGENT-211

Problems changing Splunk configuration using Administration Service

AGENT-226

YML dateFormatPattern incorrect

AGENT-231

Splunk isn’t splitting the events when buffering is enabled
### [](#known-issues)Known Issues None. ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.3.x Release Notes ## [](#1-3-3)1.3.3 _July 4, 2017_ Runtime Manager Agent 1.3.3 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.n and 3.7.n

API Gateway

2.n
### [](#improvements)Improvements - CHHYBRID-2984: Backport ELK buffering capability to agent version 1.3.3 - CHHYBRID-2985: Add payloadExcluded and globalPayloadExclusion configurations to the agent 1.3.3 ### [](#known-issues)Known Issues - CHHYBRID-2995: TrackingLevel per app fails if is not set ## [](#1-3-1)1.3.1 _January 26, 2016_ Runtime Manager Agent 1.3.0 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-2)Compatibility
Software Version

Mule Runtime

3.6.n and 3.7.n

API Gateway

2.n
### [](#features-in-this-release)Features in this Release - AGENT-243 - Add TCP and HTTP Event Collector sending mechanism to Splunk Internal Handler. ### [](#improvements-2)Improvements
Issue Description

AGENT-271

Keep the API Analytics events when no Internal Handler is active.

AGENT-269

Improve the SSL Connections of the Runtime Manager Agent to use TLSv1.2.

AGENT-247

Added the Nagios JMX Internal Handler to the Runtime Manager Agent Plugin distribution.

AGENT-228

Remove fields annotated as password from administration api response instead of returning empty values.
### [](#fixed-issues)Fixed Issues
Issue Description

AGENT-239

The DomainDeploymentService is setting in null on runtime shutdown.
### [](#known-issues-2)Known Issues None. ## [](#1-3-0)1.3.0 _December 12, 2015_ Runtime Manager Agent 1.3.0 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-3)Compatibility
Software Version

Mule Runtime

3.6.n and 3.7.n

API Gateway

2.n
### [](#features-in-this-release-2)Features in this Release - Support Splunk and Logs Mule Events integration - Support Splunk and Logs API Gateway Analytics Integration ### [](#improvements-3)Improvements
Issue Description

AGENT-188

Internal Message Handler for Tracking should be disabled by default.

AGENT-190

Enhanced log messages when redeploying or stopping an application.

AGENT-236

Upgrade Bouncy Castle Crypto library to 1.5.0 which solves the TLS vulnerability related to CVE-2013-0169.

AGENT-237

Remove the mule-agent-modules parent project and make it standalone.

AGENT-238

Replace the pattern serialization to a simpler JSON one.

AGENT-254

Add the Buffer Exhausted Action to the Splunk buffer.

AGENT-268

Add the OS to the Agent handshake.
### [](#fixed-issues-2)Fixed Issues
Issue Description

AGENT-242

Fix the jackson-core and jackson-databind dependencies on the mule-agent-plugin project.

AGENT-251

Runtime Manager Agent Installer - copy and paste issue in instructions on agent update.

AGENT-255

Nested configurations for modules are persisted as JSON strings instead of native YAML.

AGENT-260

The Runtime Manager Agent Plugin isn’t loading the .jar libraries placed on the mule-agent-plugin/lib/modules/ folder.

AGENT-262

Remove the mule-agent-modules-common jar from the RDBMS .zip distribution.

AGENT-263

Fix the Runtime Manager Agent Gateway Service to poll more than one event at a time.

AGENT-265

Redeploying Domains doesn’t properly clean resources before the new version is deployed.

AGENT-267

Use TLS 1.2v when calling Access Management on the Runtime Manager Agent Installer.
### [](#known-issues-3)Known Issues None. ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.4.x Release Notes ## [](#1-4-2)1.4.2 _June 13, 2016_ Runtime Manager Agent 1.4.2 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n
### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#deprecated-features-and-functionality)Deprecated Features and Functionality None. ### [](#fixed-issues)Fixed Issues - CHHYBRID-1673: Log (ELK) integration doesn’t work with Mule 3.8 ### [](#known-issues)Known Issues None. ## [](#1-4-1)1.4.1 _May 14, 2016_ Runtime Manager Agent 1.4.1 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-2)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#deprecated-features-and-functionality-2)Deprecated Features and Functionality None. ### [](#fixed-issues-2)Fixed Issues - AGENT-305: Support the new version of Hazelcast implemented on Mule 3.8.0 - AGENT-306: Upgrade the registration connection of the Runtime Manager Agent to Hybrid to use TLS 1.2 - CHHYBRID-1544: GA - Alerts - server / servergroup / cluster - \*-down condition being triggered twice in linux and windows - SE-3571: Unable to pair the sever with ARM - SE-3683: Intermittence on servers status: `Disconnected`,`Connected` and `Running` - AGENT-304: Runtime Manager Agent - bind to IP address ### [](#known-issues-2)Known Issues None. ## [](#1-4-0)1.4.0 _April 04, 2016_ Runtime Manager Agent 1.4.0 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-3)Compatibility
Software Version

Mule Runtime

3.6.n and 3.7.n

API Gateway

2.n
### [](#hardware-and-software-requirements-3)Hardware and Software Requirements No change. ### [](#features-in-this-release)Features in this Release - Support for static IP addresses: Agent can now support specific static addresses. - Addition of an external handler to manage monitoring service tracked beans ### [](#deprecated-features-and-functionality-3)Deprecated Features and Functionality None. ### [](#fixed-issues-3)Fixed Issues - AGENT-275: Remove the /mule/agent/ping endpoint since it’s not used and causes the mule to exit - AGENT-277: Retrieve the correct Mule and GW version for the unified Mule Runtime 3.8.0 - AGENT-278: The tracking tests are failing with a org/apache/http/ssl/TrustStrategy class not found error - AGENT-284: Runtime Manager Agent isn’t detecting that the 3.8.0-M1 Mule Runtime is a unified runtime - AGENT-297: Configuring REST transport with custom key store isn’t using the given file - AGENT-286: Report the runtime as Mule on server registration for Unified Runtimes ### [](#known-issues-3)Known Issues None. ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.5.x Release Notes ## [](#1-5-3)1.5.3 _November 7, 2016_ Runtime Manager Agent 1.5.3 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V1.5.0 + For Insight and Dashboards

This version (as a minimum) is required to access features released as part of Runtime Manager Cloud V1.5+. It’s also required to access Runtime Manager in the Anypoint Platform Private Cloud Edition V 1.0 & V1.5

Onprem V1.5 only currently does not include monitoring functionality or insight, but will be available in a future release.
### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues)Improvements and resolved issues - Host name verification enabled in the Web socket transport. - Flag added to enable SSL verification for Splunk. - Support for Mule Agent registration with TLSv1.2 and JVM 1.7. Core Services certificate trust enhancement. - Fixed the mule-agent.yml generation when using a proxy during registration. ### [](#known-issues)Known Issues - SE-4508 - Add a MuleSoft NTP server to retrieve the server date ### [](#migration-guide)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#1-5-2)1.5.2 _October 17, 2016_ Runtime Manager Agent 1.5.2 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-2)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V1.5.0 + For Insight and Dashboards

This version (as a minimum) is required to access features released as part of Runtime Manager Cloud V1.5+. It’s also required to access Runtime Manager in the Anypoint Platform Private Cloud Edition V 1.0 & V1.5

Onprem V1.5 only currently does not include monitoring functionality or insight, but will be available in a future release.
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#features-and-functionality)Features and Functionality - SE-4321: Added a configurable property to exclude the payload from the tracking notifications. - SE-4507: Added a rolling file appender to the `mule_agent.log` by default, and the possibility to configure a `mule-agent-appender` which will be used by the Mule Agent Plugin in the case is provided on the `$MULE_HOME/conf/log4j2.xml` file. See Logging in Mule. - URI creation for the `conf/log4j2.xml` file is now fixed - Added timezone to the log4j PatternLayout. - Ability to configure proxy settings when executed with the -P option. - DiskBuffer no longer throws an error with CustomEventProperties ### [](#known-issues-2)Known Issues - SE-4508: Add a MuleSoft NTP server to retrieve the server date ### [](#migration-guide-2)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#1-5-1)1.5.1 _August 15, 2016_ Runtime Manager Agent 1.5.1 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-3)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V1.5.0 + For Insight and Dashboards
### [](#hardware-and-software-requirements-3)Hardware and Software Requirements No change. ### [](#features-and-functionality-2)Features and Functionality ### [](#deprecated-features-and-functionality)Deprecated Features and Functionality None. ### [](#improvements)Improvements - \[AGENT-336: - Add support for proxies on the communication to the Auth Proxy ### [](#fixed-issues)Fixed Issues - AGENT-333: ELK Internal Handler Is throwing errors - AGENT-334: NPE when security is not configured at all - SE-4208: Runtime Manager Agent API, not returning the list of application ### [](#known-issues-3)Known Issues None. ## [](#1-5-0)1.5.0 _July 21, 2016_ Runtime Manager Agent 1.5.0 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-4)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V1.5.0 + For Insight and Dashboards
### [](#hardware-and-software-requirements-4)Hardware and Software Requirements No change. ### [](#features-and-functionality-3)Features and Functionality ### [](#deprecated-features-and-functionality-2)Deprecated Features and Functionality None. ### [](#fixed-issues-2)Fixed Issues - CHHYBRID-1673: Log (ELK) integration doesn’t work with Mule 3.8 ### [](#known-issues-4)Known Issues None. ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.6.x Release Notes ## [](#1-6-4)1.6.4 _March 27, 2017_ Runtime Manager Agent 1.6.4 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V2.0

Version 1.6.0 (as a minimum) is required to access features released as part of Runtime Manager Cloud V2.0+. It’s also required to access Runtime Manager in the Anypoint Platform Private Cloud Edition V 1.0 & V1.5
### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues)Improvements and resolved issues - CHHYBRID-2663: Logging a warn when auth proxy response with a successful status code - CHHYBRID-2666: Fixed log line condition check ### [](#known-issues)Known Issues None ### [](#migration-guide)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#1-6-3)1.6.3 _March 21, 2017_ Runtime Manager Agent 1.6.3 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-2)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V2.0

Version 1.6.0 (as a minimum) is required to access features released as part of Runtime Manager Cloud V2.0+. It’s also required to access Runtime Manager in the Anypoint Platform Private Cloud Edition V 1.0 & V1.5
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues-2)Improvements and resolved issues - CHHYBRID-2388: Fixed Mime Type issues when retrieving the Payload. Refer to the mime type list of payloads that are serialized and sent to Splunk/ELK. Non-serializable classes are set as the payload the class name of the payload object. See [Payload Formats and Logging](https://docs.mulesoft.com/jp/runtime-manager/about-logging-of-payload-formats). - CHHYBRID-2579: Fixed NPE while retrieving metrics for JVM GC time on Windows. - AGENT-397: Include CUSTOM\_TRANSACTION\_ID in the tracking notifications. - SE-5496: When adding the buffer configuration to the agent, it removes customEventProperties from event ### [](#known-issues-2)Known Issues None ### [](#migration-guide-2)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#1-6-2)1.6.2 _February 24, 2017_ Runtime Manager Agent 1.6.2 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-3)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V2.0

Version 1.6.0 (as a minimum) is required to access features released as part of Runtime Manager Cloud V2.0+. It’s also required to access Runtime Manager in the Anypoint Platform On-Premises Edition V 1.0 & V1.5

Onprem V1.5 currently does not include monitoring functionality, Flow Management or Insight.
### [](#hardware-and-software-requirements-3)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues-3)Improvements and resolved issues - CHHYBRID-2531: Payload is corrupted when event tracking is enabled and message type is modified ### [](#known-issues-3)Known Issues None ### [](#migration-guide-3)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#1-6-1)1.6.1 _January 4, 2017_ Runtime Manager Agent 1.6.1 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-4)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V2.0 + For complete server Dashboards and Flow Management

Version 1.6.0 (as a minimum) is required to access features released as part of Runtime Manager Cloud V2.0+. It’s also required to access Runtime Manager in the Anypoint Platform Private Cloud Edition V 1.0 & V1.5

Onprem V1.5 currently does not include monitoring functionality, Flow Management or Insight, but will be available in a future release.
### [](#hardware-and-software-requirements-4)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues-4)Improvements and Resolved Issues - CHHYBRID-2388: Enhanced Payload cloning to avoid corrupting streams while Event Tracking is enabled. - CHHYBRID-2376: Fixed date parsing when the user locale is not english. - CHHYBRID-2368: Fixed disk buffer file corruption under high load. - CHHYBRID-2342: REST API call to '/mule/agent' reports mule started flag correctly. - CHHYBRID-2298: Fixed Flows retrieval when an application fails to deploy. - AGENT-374: Enhanced Mule Agent Plugin upgrader message when is not installed. - AGENT-372: Removed SLF4J warning message from upgrader. - AGENT-371: Fixed the encryption feature of the Mule Agent Plugin. ### [](#known-issues-4)Known Issues None ### [](#migration-guide-4)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#1-6-0)1.6.0 _November 19, 2016_ Runtime Manager Agent 1.6.0 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**:[Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-5)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V2.0 + For complete server Dashboards and Flow Management

This version (as a minimum) is required to access features released as part of Runtime Manager Cloud V2.0+. It’s also required to access Runtime Manager in the Anypoint Platform Private Cloud Edition V 1.0 & V1.5

Onprem V1.5 currently does not include monitoring functionality, Flow Management or Insight, but will be available in a future release.
### [](#hardware-and-software-requirements-5)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues-5)Improvements and resolved issues - Support for [Flow Management](https://docs.mulesoft.com/jp/runtime-manager/flow-management) - Support for new server metrics in dashboards ### [](#known-issues-5)Known Issues None ### [](#migration-guide-5)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.7.x Release Notes ## [](#1-7-1)1.7.1 _June 26, 2017_ Runtime Manager Agent 1.7.1 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V2.0
### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues)Improvements and resolved issues - SE-5702: Flows of apps created with ApiKit are shown as Failed. - SE-6207: When writing business events to the ELK file, the process generates contention with a large number of events. - SE-5779: There seems to be some network contention when the disk buffering is enabled, causing network timeouts. ### [](#known-issues)Known Issues None ### [](#migration-guide)Migration Guide The 1.7.1 release of the runtime manager agent changes the disk buffering implementation. In case you were using disk buffering on a previous version, you will be asked to manually remove remaining buffer files when running the runtime manager agent update. See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#1-7-0)1.7.0 _May 23, 2017_ Runtime Manager Agent 1.7.0 provides a new downloadable zip file to easily update Runtime Manager Agent. Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. **Runtime Manager Agent Install Guide**: [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) ### [](#compatibility-2)Compatibility
Software Version

Mule Runtime

3.6.n, 3.7.n, 3.8.n

API Gateway

2.n and above

Runtime Manager

V2.0

Version 1.6.0 (as a minimum) is required to access features released as part of Runtime Manager Cloud V2.0+.
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues-2)Improvements and resolved issues - CHHYBRID-2770: Send the last date an application was started - CHHYBRID-2610: Send ClusteringTicket to Mule with the new clusteringPort property. - CHHYBRID-2711: Implement Stop Runtime on the Mule Agent - CHHYBRID-2710: Implement Restart on the Mule Agent - CHHYBRID-2692: Agent should send server metadata to the hybrid console - CHHYBRID-2749: Disable the Jackson feature to fail on unknown properties ### [](#known-issues-2)Known Issues None ### [](#migration-guide-2)Migration Guide See [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Salesforce Help](https://help.salesforce.com) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.8.x Release Notes ## [](#1-8-0)1.8.0 _October 19, 2017_ This version of the Runtime Manager Agent is deprecated. Please use version 1.9.0. See [Runtime Manager Agent 1.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.9.x-release-notes#1-9-0) for more information. ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 1.9.x Release Notes ## [](#1-9-5)1.9.5 _May 5, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.9.5. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues)Fixed Issues This release contains the following issue fixes: - Upgrades the Jackson library to version 2.9.5 to fix vulnerability. - Upgrades Jetty to version 9.4.8.v20171121 to fix vulnerability. - Fixes error when tracking notification were consumed and sent to a database. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes There are no compatibility notes for this release. ## [](#1-9-4)1.9.4 _March 2, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 1.9.4. ### [](#new-features-and-enhancements-2)New Features and Enhancements - Added log entries for web socket disconnections to help understand the root cause of server disconnections. - Reduced logging verbosity of the Runtime Manager Agent to avoid unnecessary log noise ### [](#changes-in-this-release-2)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-2)Fixed Issues There are no fixed issues in this release. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes There are no compatibility notes for this release. ## [](#1-9-3)1.9.3 _January 15, 2018_ Download Runtime Manager Agent, version 1.9.3 at the following URL: [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) ### [](#compatibility)Compatibility
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Runtime Manager

V2.0
### [](#hardware-and-software-requirements)Hardware and Software Requirements No change. ### [](#improvements)Improvements - Add runtime version and agent version to response of the endpoint to retrieve information about the agent and the runtime. - Upgrade amc\_debug script to exclude HEAP by default and include network check. - Support for Schedule Management on Clusters and Server Groups ### [](#fixed-issues-3)Fixed Issues - Upgrade BouncyCastle library to 1.59 to fix vulnerability (CVE-2017-13098) - Fix bug in scheduling management where not all schedulers where being reported when the agent had schedulers configured. ### [](#known-issues)Known Issues There are no known issues in this release. ## [](#1-9-2)1.9.2 _December 15, 2017_ Download Runtime Manager Agent, version 1.9.2 at the following URL: [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) ### [](#compatibility-2)Compatibility
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Runtime Manager

V2.0
### [](#hardware-and-software-requirements-2)Hardware and Software Requirements No change. ### [](#improvements-2)Improvements - Added support for the EU control plane. - Added correlationSequence and correlationGroupSize to the event tracking notification. - Added the ability to collapse comments. ### [](#fixed-issues-4)Fixed Issues - Added a check for application properties feature availability. - Made the command line agent installer URLs take precedence over the service registry ones. - Upgraded the `log4j` library from 2.5 to version 2.8.2 due to end of support and vulnerability(CVE-2017-5645). - Upgraded the Grizzly library version due to security vulnerability(CVE-2017-1000028). - Ensured that null application properties are not applied at deployment/redeployment time. ### [](#known-issues-2)Known Issues There are no known issues in this release. ## [](#1-9-1)1.9.1 _November 10, 2017_ Download Runtime Manager Agent, version 1.9.1 at the following URL: [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) ### [](#compatibility-3)Compatibility
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Runtime Manager

V2.0
### [](#hardware-and-software-requirements-3)Hardware and Software Requirements No change. ### [](#improvements-and-fixed-issues)Improvements and Fixed Issues - Updated runtime status displayed in Runtime Manager to CONNECTED when the runtime is boot instead of when the application starts. This resolve an issue with servers experiencing disconnection issues when an application took longer than 50 seconds to start. - Fixed issue where application properties managed in Runtime Manager did not default to the correct values. - Changed the log level in situations when JMX is not found. - Fixed issue where Memory Server Metrics were not being collected correctly when configuring a different garbage collector in the `wrapper.conf` file. - Fixed issue with `FileNotFoundException` after installing the RUagent with -I flag. - \[SE-6934\] Fixed issue where global flags were not being considered when they were not set for `trackedApplication`. - \[SE-6307\] Fixed issue where the Runtime Manager Agent failed to work on the IBM JDK. - Added support for deploying applications to regions within the European Union. **Update:** Due a change in the SSL certificates, 1.9.1 has NO longer support for the European Union region. Please use the 1.9.2 and above version of the Mule Agent for that region’s support. ### [](#known-issues-3)Known Issues None ## [](#1-9-0)1.9.0 _October 06, 2017_ Download the Runtime Manager agent from the following URL. [MuleSoft Downloads](https://help.salesforce.com/s/mulesoft-product-downloads) You must supply your Anypoint login and password to access this page. ### [](#compatibility-4)Compatibility
Software Version

Mule Runtime

3.6.x, 3.7.x, 3.8.x, 3.9.x

API Gateway

2.x and above

Runtime Manager

V2.0
### [](#hardware-and-software-requirements-4)Hardware and Software Requirements No change. ### [](#improvements-and-resolved-issues)Improvements and resolved issues - Fixed issue where a user could not delete an application that failed to deploy. - Fixed issue where a custom business event name was not displayed in Insights. - Fixed issue where Mule agent fails on the IBM JDK. - Added support for Autodiscovery of local Server Properties. - Added support for Configuration Management when deploying or redeploying. - Mule Runtime Agent support for schedulers management - Support for multiple environments on Anypoint Platform - Support for Mule Runtime Agent configuration fragments - Support for large application sizes (200MB) - `MuleAgentProperties` are now stored in wrapper.conf - Corrected response when listing apps from Rest API - Updated dependency versions ### [](#known-issues-4)Known Issues None ## [](#see-also)See Also - [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) - [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent) - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.1.x Release Notes ## [](#2-1-9)2.1.9 _December 7, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.1.9. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains the following new features or enhancements: - Added support for flushing disk-buffered Mule events in batches of a configurable size. ### [](#changes-in-this-release)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues)Fixed Issues This release contains the following issue fixes: - Issue that caused buffered events to be discarded when using disk buffer in the scenario that buffered events exceeded in-memory limit size. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes
Software Version

JDK

JDK 1.8.0 (Recommended JDK 1.8.0_151/52)

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Mule 4.1.x

This agent version is compatible only with Mule 4.1.x versions.
## [](#2-1-8)2.1.8 _November 12, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.1.8. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains the following features or enhancements: - Faster startup time with less memory footprint than earlier versions. ### [](#changes-in-this-release-2)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-2)Fixed Issues This release contains the following issue fixes: - Fixed connectivity issue with Anypoint Platform Control Plane when running the Agent behind a proxy. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-2)Compatibility Notes
Software Version

JDK

JDK 1.8.0 (Recommended JDK 1.8.0_151/52)

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Mule 4.1.x

This agent version is compatible only with Mule 4.1.x versions.
## [](#2-1-7)2.1.7 _October 08, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.1.7. ### [](#new-features-and-enhancements-3)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-3)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-3)Fixed Issues This release contains the following issue fixes: - For Studio : DataWeaver preview now always set payload, vars and attribute variables . ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-3)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-3)Compatibility Notes
Software Version

JDK

JDK 1.8.0 (Recommended JDK 1.8.0_151/52)

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Mule 4.1.x

This agent version is compatible only with Mule 4.1.x versions.
## [](#2-1-6)2.1.6 _September 13, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.1.6. ### [](#new-features-and-enhancements-4)New Features and Enhancements This release contains no new features or enhancements: ### [](#changes-in-this-release-4)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-4)Fixed Issues This release contains the following issue fixes: - Upgrade version of several dependency libraries. - Fix in Insights feature. ### [](#known-limitations-and-workarounds-4)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-4)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-4)Compatibility Notes There are no compatibility notes for this release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.2.x Release Notes ## [](#2-2-1)2.2.1 _February 19, 2019_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.2.1. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release)Changes in this Release - The API now returns the root cause when an application fails to deploy. - Application properties are now stored in the application `yml` descriptor instead of in the `mule-agent.yml`. - For APCE environments, trusted certificates are always used from the JKS file instead of the JVM. ### [](#fixed-issues)Fixed Issues This release contains the following fixed issues: - Application fails at restart from side panel due to property not found. - When tracking was enabled in Mule 4.1.x, `TransactionNotification` related errors were written to the application’s log instead of the `mule_ee.log`. - Support for the `host` property in CloudHub properties caused applications to fail to deploy. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule Runtime

This agent version is compatible only with Mule 4.1.x versions.

JDK

JRE 1.8.0 (Recommended JRE 1.8.0_151/52)

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.10.0+
## [](#2-2-0)2.2.0 _January 28, 2018_ This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.2.0. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release contains the following new features or enhancements: - Added Java 11 OpenJDK Support ### [](#changes-in-this-release-2)Changes in This Release - This version of Runtime Manager Agent enables connection to the new Runtime Manager Publicly Certified endpoints for Mule Manager and Auth Proxy. - Now, when enabling a service that has a null log configuration, the Mule Agent API returns a bad request (400) instead of an internal server error (500). ### [](#fixed-issues-2)Fixed Issues This release contains the following fixed issue: - The issue that caused an NPE when processing `ExceptionNotification` from the implicit error handler is fixed. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements When you upgrade the agent, two new endpoints for communicating with Anypoint Runtime Manager are created. Before performing the upgrade, ensure there are no networking constraints for accessing the FQDNs on port 443. For more information, see [Ports, IP Addresses, and Hostnames to Allowlist](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-allowlists).
United States EU

wss://runtime-manager.anypoint.mulesoft.com

https://data-authenticator.anypoint.mulesoft.com

wss://runtime-manager.eu1.anypoint.mulesoft.com

https://data-authenticator.eu1.anypoint.mulesoft.com
### [](#compatibility-notes-2)Compatibility Notes
Software Version

Mule Runtime

This agent version is compatible only with Mule 4.1.x versions.

JDK

JRE 1.8.0 (Recommended JRE 1.8.0_151/52)

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.10.0+
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.3.x Release Notes ## [](#2-3-0)2.3.0 _May 2, 2019_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.3.0. ### [](#new-features-and-enhancements)New Features and Enhancements This release contains the following new features or enhancements: - Starting with Mule 4.2.0, API Manager Secrets (`clientId`, `clientSecret`, and `Proxy password`) can be stored, encrypted, in the `wrapper.conf` file when an encryption key is provided at setup time. For more information, see [API Gateway Encryption on Mule 4](https://docs.mulesoft.com/jp/mule-gateway/mule-gateway-encryption-mule4). ### [](#changes-in-this-release)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues)Fixed Issues This release contains the following fixed issue: - HTTP 400 response when uploading metrics via mule agent for flow names with non-ASCII characters. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements
This is only applicable to users with HTTP events enabled and stored in an on premises database:
- `policy_violation_policy_id` data type must be updated in the Database Schema. Please refer to the following documentation: [Send API Analytics from Runtime Manager to an External Database](https://docs.mulesoft.com/jp/runtime-manager/sending-api-analytics-from-arm-to-db) ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule Runtime

This agent version is compatible only with Mule 4.1.x and Mule 4.2.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.10.0+
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.4.x Release Notes ## [](#2-4-37)2.4.37 **Jan 12 2023** ### Fixed Issues
Issue Resolution ID

Runtime Manager Agent Notifications (via REST) now works as expected

W-11722041

Addressed multiple high-severity vulnerabilities in Runtime Manager Agent 2.4.36 associated with Woodstox 3pp

W-12176621

Addressed multiple high-severity vulnerabilities in Runtime Manager Agent 2.4.36 associated with snakeyaml

W-12355765
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-36)2.4.36 **Nov 15, 2022** ### What’s New - You can now trace WebSocket messages by configuring the `mule.agent.configuration.trace_ws` property in your `wrapper.conf` file, or adding this property in the UI for your Mule. You need to restart your server for it to take this property. ### Fixed Issues
Issue Resolution ID

There is now an option to trace WebSocket messages in Mule Agent

W-10632188
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-35)2.4.35 **Nov 4, 2022** ### What’s New - Added a default implementation for the application jar signer validator with support for keystores with multiple aliases and expired certificate checks on the application validator service. ### Fixed Issues
Issue ID

Runtime manager no longer overrides the anypoint.platform.analytics_base_uri property in your wrapper.conf file when your Mule agent is updated.

W-11989119
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-34)2.4.34 **Sep 16, 2022** ### Fixed Issues
Issue ID

Upgraded the versions of several dependency libraries.

W-11732881
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-33)2.4.33 **Jul 29, 2022** ### Fixed Issues
Issue ID

Requesting to renew the certificate in Windows now works correctly.

W-11130919

The agent now supports Java 11 with FIPS.

W-11268395
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-32)2.4.32 **Jul 21, 2022** ### Fixed Issues
Issue ID

Upgraded the versions of several dependency libraries.

W-11471229
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-31)2.4.31 **Jun 27, 2022** ### Fixed Issues
Issue ID

Upgraded the versions of several dependency libraries.

W-11267482
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-30)2.4.30 **Jun 9, 2022** ### Fixed Issues
Issue ID

Upgraded the versions of several dependency libraries.

W-11267437
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-29)2.4.29 **Jun 1, 2022** ### Fixed Issues
Issue ID

Schedulers no longer start automatically after an application restart, and they retain the same configuration they had before the application stopped.

W-11032600

Changing scheduler configurations no longer causes Fixed Frequency schedulers to restart.

W-11032600
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-28)2.4.28 **Apr 29, 2022** ### What’s New - Added a new optional validation step to the deployment process. This enables you to write your own application validators to stop a deployment if the given conditions are not satisfied. See [feature documentation](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-app-validator) for details.
Issue ID

Upgraded third-party libraries.

SE-24290
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-27)2.4.27 **Feb 03, 2022** ### What’s New - Enabled the Bouncy Castle security provider by adding the property `mule.security.provider` with the value **BC** to the runtime `wrapper.conf`, for example, `wrapper.java.additional.=-Dmule.security.provider=BC`. If you encountered cryptography issues since Mule Agent 2.4.18, you can now use this flag to update the agent version and activate Bouncy Castle as a default security provider. ### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-4-26)2.4.26 **Dec 21, 2021**
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-25)2.4.25 **Dec 15, 2021**
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-24)2.4.24 **Dec 14, 2021** ### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-23)2.4.23 **Nov 10, 2021**
Issue ID

Fixed an issue that occurred when deploying an application with scheduler configurations.

SE-22911
Application/Service Version

Mule runtime engine

Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-22)2.4.22 **Sep 17, 2021**
Issue ID

Upgraded third-party libraries.

SE-21687
Application/Service Version

Mule runtime engine

Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-21)2.4.21 _Aug 09, 2021_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.21. ### [](#fixed-issues-10)Fixed Issues This release includes the following fixes: - This version contains no updates due to an issue in the release process. ### [](#compatibility-notes)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-20)2.4.20 _June 29, 2021_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.20. ### [](#fixed-issues-11)Fixed Issues This release includes the following fixes: - Custom logging configurations are no longer lost when redeploying an application with a new JAR file. - Renew Certificate action via API REST not functioning due to Bouncy Castle dependency conflict. - Add validation on configurations while deploying applications on Mule Server. For example, for `mule.agent.application.properties.service`, you can only configure `applicationName` and `properties`. ### [](#compatibility-notes-2)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-19)2.4.19 _June 8, 2021_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.19. ### [](#fixed-issues-12)Fixed Issues This release includes the following fixes: - The `mule-agent.yml has an invalid format` error no longer occurs when concurrent agent configuration requests are made. ### [](#compatibility-notes-3)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-18)2.4.18 _April 9, 2021_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.18. ### [](#new-features-and-enhancements)New Features and Enhancements This release includes the following features: - Implemented FIPS compliance for CloudHub. - Upgraded the versions of several dependency libraries. ### [](#fixed-issues-13)Fixed Issues This release includes the following fixes: - Fixed an `InvalidAlgorithmParameterException` that occurred because a PGP algorithm parameter was not supported. - Fixed an issue in which restarting a stopped application resulted in a `Starting` status in the application UI. ### [](#compatibility-notes-4)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-17)2.4.17 _March 12, 2021_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.17. ### [](#new-features-and-enhancements-2)New Features and Enhancements This release includes the following features: - Enabled the keystore password encryption in the `mule-agent.yml` file. ### [](#fixed-issues-14)Fixed Issues This release includes the following fixes: - Upgraded the versions of several dependency libraries. ### [](#compatibility-notes-5)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-16)2.4.16 _February 18, 2021_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.16. ### [](#new-features-and-enhancements-3)New Features and Enhancements This release includes the following features: - Added reliability and resiliency enhancements. ### [](#compatibility-notes-6)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-15)2.4.15 _February 12, 2021_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.15. ### [](#new-features-and-enhancements-4)New Features and Enhancements This release includes the following features: - Support for FIPS 140-2 on Anypoint Platform PCE. ### [](#fixed-issues-15)Fixed Issues This release includes the following fixes: - Fixed a null pointer exception that occurred when sending analytics data to an external database. - Fixed an issue that made application deployments unmanaged when restarting domains. - Fixed a class cast exception that occurred when redeploying an application after changing the scheduler type. - Fixed a file system exception error that occurred while processing the Mule agent configuration file for update. ### [](#compatibility-notes-7)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-14)2.4.14 _December 17, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.14. ### [](#fixed-issues-16)Fixed Issues This release includes the following fixes: - Fixed an issue in which the application properties failed to load when an application was started. ### [](#compatibility-notes-8)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-13)2.4.13 _December 11, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.13. ### [](#fixed-issues-17)Fixed Issues This release includes the following fixes: - Fixed an issue in which the column `policy_violation_policy_name` was not populated when analytic data was sent to an external database. ### [](#compatibility-notes-9)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-12)2.4.12 _December 1, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.12. ### [](#new-features-and-enhancements-5)New Features and Enhancements This release includes no new features or enhancements. ### [](#changes-in-this-release)Changes in This Release This release includes no changed features. ### [](#fixed-issues-18)Fixed Issues This release includes the following fixes: - Fixed an issue in which analytic data was not sent to external database due an SQL syntax error. ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-10)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-11)2.4.11 _November 18, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.11. ### [](#new-features-and-enhancements-6)New Features and Enhancements This release includes no new features or enhancements. ### [](#changes-in-this-release-2)Changes in This Release This release includes no changed features. ### [](#fixed-issues-19)Fixed Issues This release includes the following fixes: - Fixed an issue in which, after restarting the runtime, the properties of the application did not load correctly. - Fixed an issue in which deploying an application with secure properties failed on Oracle JDK distributions. - Fixed an issue in which the web socket reserved a large amount of memory to buffer connections. - Fixed an issue in which analytic data was not sent to external database. - Fixed an issue in which sometimes the agent configuration file was corrupted by invalid characters. ### [](#known-limitations-and-workarounds-2)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-2)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-11)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-10)2.4.10 _October 7, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.10. ### [](#new-features-and-enhancements-7)New Features and Enhancements This release includes no new features or enhancements. ### [](#changes-in-this-release-3)Changes in This Release This release includes no changed features. ### [](#fixed-issues-20)Fixed Issues This release includes the following fixes: - Fixed an issue in which starting a flow did not start its scheduler. - Fixed a null pointer exception that occurred when deploying an application with logging configuration. - Fixed a null pointer exception that occurred when deploying an application with missing application properties. - Fixed an issue in which starting an application resulted in a `Stopping` status in the flows. - Fixed an issue in which internal agent log messages appeared in the application logs. - Fixed an issue in which sometimes the agent configuration file was cleared. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds-3)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-3)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-12)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-9)2.4.9 _August 27, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.9. ### [](#new-features-and-enhancements-8)New Features and Enhancements - Support for FIPS 140-2 - Support for the Mulesoft Government Cloud environment ### [](#changes-in-this-release-4)Changes in This Release This release includes no changed features. ### [](#fixed-issues-21)Fixed Issues This release includes no fixed issues. ### [](#known-limitations-and-workarounds-4)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-4)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-13)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-8)2.4.8 _July 31, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.8. ### [](#new-features-and-enhancements-9)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-5)Changes in This Release This release includes no changed features. ### [](#fixed-issues-22)Fixed Issues This release contains the following fixed issue: - Upgraded several dependency components. ### [](#known-limitations-and-workarounds-5)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-5)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-14)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-7)2.4.7 _July 20, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.7. ### [](#new-features-and-enhancements-10)New Features and Enhancements The agent now supports the file protocol for application properties. If an application property is a URI with a file protocol, the agent reads the file content as the property value. This feature is disabled by default. To enable it, set the following property in `mule-agent.yaml`: services.mule.agent.application.properties.service.fileProtocolConfiguration.enabled: true For more information, see [ARM Mule Agent Plugin API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/mule-agent-plugin-api/). ### [](#changes-in-this-release-6)Changes in This Release This release includes no changed features. ### [](#fixed-issues-23)Fixed Issues This release contains the following fixed issues: - Fixed an issue in which starting a Mule application after flows become unmanaged caused an error message. - Fixed an issue in which restarting a logging service caused an error message. - Fixed an issue in which stopping a flow and redeploying the Mule application showed the flow as `stopping` instead of `stopped`. - The DataWeave preview feature now supports binary content for payload content. ### [](#known-limitations-and-workarounds-6)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-6)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-15)Compatibility Notes
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-6)2.4.6 _April 7, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.6. ### [](#new-features-and-enhancements-11)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-7)Changes in This Release Reordered the index of the additional Java properties in the `wrapper.conf` file with the following suffixes: - `stripquotes` - `java_version.min` - `java_version.max` ### [](#fixed-issues-24)Fixed Issues This release contains the following fixes: - Fixed an issue in which starting a Mule application after flows become unmanaged caused an error message. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds-7)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-7)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-16)Compatibility Notes
Software Version

Mule Runtime Engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-5)2.4.5 _January 24, 2020_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.5. ### [](#new-features-and-enhancements-12)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-8)Changes in This Release - Added new modules provided by MuleSoft to the default Runtime Manager agent version 2.x ZIP distribution: - Zabbix, Graphite, and CloudWatch metrics publishers - DB and HTTP API Analytics trackers ### [](#fixed-issues-25)Fixed Issues This release contains the following fixes: - JMX Publisher no longer stops publishing metrics after an undeploying an app. - Starting and stopping applications or flows now sends logs to the correct files. ### [](#known-limitations-and-workarounds-8)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-8)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-17)Compatibility Notes
Software Version

Mule Runtime Engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-4)2.4.4 _December 19, 2019_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.4. ### [](#new-features-and-enhancements-13)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-9)Changes in This Release - HTTP callbacks now include a new authentication header emitted via the WebSockets channel. - Two extra fields were added to the Mule agent REST transport endpoint. ### [](#fixed-issues-26)Fixed Issues This release contains the following fixes: - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds-9)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-9)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-18)Compatibility Notes
Software Version

Mule Runtime Engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-3)2.4.3 _September 26, 2019_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.3. ### [](#new-features-and-enhancements-14)New Features and Enhancements This release contains no new features or enhancements. ### [](#fixed-issues-27)Fixed Issues This release contains the following fixed issues: - Fixed connection issues when using an encrypted proxy password stored in mule-agent.yml. For information, see [Include an Encrypted Password in the mule-agent.yml File](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-proxy-config#encrypt_password). - Fixed an issue in which a persistent Object Store that was created with its connector was deleted when redeploying and restarting an app through Runtime Manager. (MULE-17300, MULE-17417)
To take advantage of this fix, you must also upgrade your Mule runtime engine to version 4.3.0. See Mule Runtime 4.3.0 Release Notes.
### [](#known-limitations-and-workarounds-10)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-10)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-19)Compatibility Notes
Software Version

Mule Runtime Engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-2)2.4.2 _September 3, 2019_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.2. ### [](#new-features-and-enhancements-15)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-10)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-28)Fixed Issues This release contains the following fixed issues: - Agent logs display null version for Agent 2.x during startup. - Deployment failure root cause message is truncated when sent to Runtime Manager. ### [](#known-limitations-and-workarounds-11)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-11)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-20)Compatibility Notes
Software Version

Mule Runtime Engine

This agent version is compatible only with Mule 4.1.x and Mule 4.2.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-1)2.4.1 _July 26, 2019_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.1. ### [](#new-features-and-enhancements-16)New Features and Enhancements This release contains no new features or enhancements. ### [](#changes-in-this-release-11)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-29)Fixed Issues This release contains the following fixed issue: - NoClassDefFoundError exception when trying to upgrade the agent version 2.3.0 through a proxy. ### [](#known-limitations-and-workarounds-12)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-12)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-21)Compatibility Notes
Software Version

Mule Runtime Engine

This agent version is compatible only with Mule 4.1.x and Mule 4.2.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#2-4-0)2.4.0 _July 22, 2019_ These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.0. ### [](#new-features-and-enhancements-17)New Features and Enhancements This release contains the following new features or enhancements: - Atomic schedulers modifications: A new HTTP endpoint in the Mule Runtime Manager agent API will modify schedulers' settings atomically so that other schedulers deployed to the same Mule runtime engine are not triggered. Prior to this update, modifications to schedulers forced the synchronous trigger of the schedulers of all applications running in the same Mule runtime engine. ### [](#changes-in-this-release-12)Changes in This Release This release contains no changes to existing functionality. ### [](#fixed-issues-30)Fixed Issues This release contains the following fixed issue: - Deploying an application that takes longer than one minute to start causes the runtime to disconnect from Anypoint Runtime Manager. - Upgraded the versions of several dependency libraries. ### [](#known-limitations-and-workarounds-13)Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### [](#upgrade-requirements-13)Upgrade Requirements There are no upgrade requirements for this release. ### [](#compatibility-notes-22)Compatibility Notes
Software Version

Mule Runtime

This agent version is compatible only with Mule 4.1.x and Mule 4.2.x.

Java

JRE/JDK 1.8.0

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04

Runtime Manager

V2.12.0+
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.5.x Release Notes ## [](#2-5-10)2.5.10 **Jan 03 2024** ### Fixed Issues
Issue Resolution ID

Added custom JSON dependency for Runtime Manager Agent.

W-14499045

Removed unused dependencies and modules.

W-14499048, W-14634649, W-14560677

Added compatibility to renew certificates in Hyperforce.

W-14571860
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, and Mule 4.5.x.

Java

JRE/JDK 1.8.0, JDK 11.

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-5-9)2.5.9 **Nov 29 2023** ### Fixed Issues
Issue Resolution ID

Adjusted dependency libraries to reduce file size.

W-14471415

Added Hyperforce compatibility for Runtime Manager agent.

W-13739907
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, and Mule 4.5.x.

Java

JRE/JDK 1.8.0, JDK 11.

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-5-8)2.5.8 **Nov 10 2023** ### What’s New This version of the Runtime Manager agent contains a noticeable file size change due to the upgrade of a dependency library. ### Fixed Issues
Issue Resolution ID

Updated versions of several dependency libraries.

W-14040448 W-14088453 W-14366993

Fix Certificate renewal for agent 2.5.x.

W-13462295
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, and Mule 4.5.x.

Java

JRE/JDK 1.8.0, JDK 11.

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-5-7)2.5.7 **Nov 3 2023** ### Fixed Issues
Issue Resolution ID

Updated versions of several dependency libraries.

W-13866827 W-14307449

Logging improvements.

W-14130091
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, and Mule 4.5.x.

Java

JRE/JDK 1.8.0, JDK 11.

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-5-6)2.5.6 **Oct 09 2023** ### Fixed Issues
Issue Resolution ID

Removed benign null-pointer exception stack trace from error logs produced due to the absence of environment variables for application properties.

W-12588190
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x and Mule 4.5.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04

Runtime Manager

v2.12.0+ and later
## [](#2-5-5)2.5.5 **Sep 01 2023** ### Fixed Issues
Issue Resolution ID

Upgraded the versions of several dependency libraries.

W-13847387 W-13848351 W-13897908
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-5-4)2.5.4 **Aug 04 2023** ### Fixed Issues
Issue Resolution ID

Addressed vulnerability in Mule Agent

W-13748457

Addressed thread leak issue in Mule Agent

W-12574154

Upgraded the versions of several dependency libraries.

W-13632764 W-13206634 W-13206645 W-13206645 W-13206633 W-13831509

Logging improvements

W-13797513
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-5-3)2.5.3 **July 07 2023** ### Fixed Issues
Issue Resolution ID

Addressed high-severity vulnerability in Runtime Manager Agent 2.5.2 associated with bouncy castle

W-13274789

Addressed high-severity vulnerability in Runtime Manager Agent 2.5.2 associated with kryo

W-13335140

Addressed high-severity vulnerability in Runtime Manager Agent 2.5.2 associated with jetty

W-13504626
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-5-2)2.5.2 **May 19 2023** ### Fixed Issues
Issue Resolution ID

You can now correctly encrypt passwords in mule-agent.yml on Windows.

W-12153152

Upgraded the versions of several dependency libraries.

W-12770203
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-5-1)2.5.1 **Mar 09 2023** ### Fixed Issues
Issue Resolution ID

Upgraded the versions of several dependency libraries.

W-12506185
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#2-5-0)2.5.0 **Jan 26 2023** ### Fixed Issues
Issue Resolution ID

Added support for Proxy authentication with Kerberos protocol (only supported in CommCloud with JRE/JDK 8 and without FIPS enabled)

W-11657643
### Compatibility
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x.

Java

JRE/JDK 1.8.0, JDK 11

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04

Runtime Manager

v2.12.0+ and later
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.6.x Release Notes ## [](#2-6-7)2.6.7 **October 23 2024** ### Fixed Issues
Issue Resolution ID

Runtime Manager agent is now compatible with PCE4.

W-16471473

The TCP connections open to the control plane for PCE environments have now been optimized.

W-16978355

The org.bouncycastle:bcprov-jdk15to18 is upgraded to 1.78

W-16734469
### Compatibility
Java 17 is compatible only with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (from 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, RHEL 9, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-6-6)2.6.6 **October 3 2024** ### Fixed Issues
Issue Resolution ID

Reverted changes made to the logic for calculation of Metrics messageCount and averageResponseTime made in the 2.6.5 Agent Release.

W-16883996
### Compatibility
Java 17 is compatible only with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (from 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-6-5)2.6.5 **Jul 24 2024** ### Fixed Issues
Issue Resolution ID

Updated logic for calculation of Metrics - messageCount and averageResponseTime. Both Metrics are reported to Anypoint and ARM Monitoring.

W-15493004

Memory leaks no longer when metric publishing fails.

W-16244698
### Compatibility
Java 17 is compatible only with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (from 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-6-4)2.6.4 **Jul 9 2024** ### Fixed Issues
Issue Resolution ID

The versions of several dependency libraries are now updated.

W-15488385
### Compatibility
Java 17 is compatible only with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (from 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-6-3)2.6.3 **May 23 2024** ### Fixed Issues
Issue Resolution ID

The renovation of certificates no longer fails when using an intermediary proxy.

W-14981489

Runtime Manager agent is now compatible with Hyperforce.

W-15492714

Added Logging improvements.

W-15734481
### Compatibility
Java 17 is compatible only with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (from 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-6-2)2.6.2 **Apr 16 2024** ### Fixed Issues
Issue Resolution ID

The versions of several dependency libraries are now updated.

W-15301315, W-14998190
### Compatibility
Java 17 is compatible with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (Mule 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-6-1)2.6.1 **Mar 13 2024** ### Fixed Issues
Issue Resolution ID

The versions of several dependency libraries are now updated.

W-15052605

Partial scheduler configuration updates are now allowed in Runtime Manager agent.

W-15130072
### Compatibility
Java 17 is compatible with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (Mule 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#2-6-0)2.6.0 **Feb 06 2024** ### Fixed Issues
Issue Resolution ID

Runtime Manager Agent now supports Java17.

W-13462591, W-14894215
### Compatibility
Java 17 is compatible with Mule 4.6.x and later.
Software Version

Mule runtime engine

This agent version is compatible with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, Mule 4.4.x, Mule 4.5.x, Mule 4.6.x, Mule 4.7.x.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (Mule 4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 8, and Ubuntu Server 20.04.

Runtime Manager

v2.12.0+ and later.
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.7.x Release Notes ## [](#2-7-20)2.7.20 **Sep 24 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

Changing an application’s log level no longer removes existing Log4j appender references or changes logger additivity. Clearing the change restores the original log level.

W-18145972

Undeploying an application no longer resequences unrelated additional Java properties in the wrapper.conf file.

W-23716595

Timed-out WebSocket connection attempts are now canceled before the agent starts another connection attempt.

W-24093711

The deployment operation status tracking API introduced in Runtime Manager agent 2.7.18 is removed.

W-23438297

The Java 8-compatible UBB plugin is upgraded from 1.1.4 to 1.1.6.

W-23137965, W-24048672, W-24276290
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-19)2.7.19 **Aug 21 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The io.netty dependency is upgraded to 4.2.17.Final to address CVE vulnerabilities.

W-23716580, W-3300013

The bouncycastle dependency is upgraded to 1.85 to address CVE vulnerabilities.

W-23716580, W-3300013

The jackson-databind dependency is upgraded to 2.22.2 to address CVE vulnerabilities.

W-3300013

The wire-runtime dependency is upgraded to 6.4.1 to address CVE vulnerabilities.

W-23716580
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-18)2.7.18 **Jul 29 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

A new REST endpoint now provides deployment status reporting used by CloudHub 1.0 runtimes.

W-23438297
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-17)2.7.17 **Jul 14 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The jackson-core dependency is upgraded to 2.22.0 to address CVE vulnerabilities.

W-22806004, W-23037571

The log4j-core dependency is upgraded to 2.26.1 to address CVE vulnerabilities.

W-22939392

The wire-runtime-jvm dependency is upgraded to 6.3.0 to address CVE vulnerabilities.

W-21688020

The commons-configuration2 and commons-io dependencies are upgraded to 2.15.1 and 2.22.0 respectively to address CVE vulnerabilities.

W-22806009
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-16)2.7.16 **Jun 17 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The ConfigurationWatcher no longer generates unnecessary error logs during a Mule upgrade.

W-22734121

The amc_setup --encrypt command now uses a strong cryptographic algorithm to encrypt mule-agent.yaml.

W-22678184

The plexus-utils dependency is upgraded to 4.0.3

W-22389904

The io.netty dependency is upgraded to 4.2.15.Final

W-22389904

The async-http-client dependency is upgraded to 2.15.0

W-22389904, W-22052914
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-15)2.7.15 **May 15 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The transitive org.apache.avro dependency is updated to address the CVE-2025-33042 vulnerability.

W-21305070

Startup failures due to version incompatibilities no longer occur.

W-22389904
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-14)2.7.14 **May 1 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The log4j dependency is updated to address the CVE-2025-68161 vulnerability.

W-22310570
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-13)2.7.13 **April 23 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

BouncyCastle bcprov-jdk15to18.jar is updated to resolve CVE-2026-5598 security vulnerability.

W-22110728

The UBB plugin is updated from version 1.0.9 to 1.1.0.

W-22030519

The non-FIPS Bouncy Castle library location is now adjusted for Mule Runtime Distribution.

W-22143421
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-12)2.7.12 **April 06 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

Runtime Manager agent supports FIPS-140-3 security model.

W-21191356

Runtime Manager agent supports TLS 1.3.

W-19654603

Runtime Manager agent now works with Bouncy Castle FIPS 2.x library.

W-21716139

The transitive commons-beanutils dependency is updated to address the CVE-2025-48734 vulnerability.

W-21688021
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-11)2.7.11 **March 17 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The transitive netty-codec-http dependency is updated to address the CVE-2025-67735 vulnerability.

W-21289678

The transitive bcpkix-jdk15to18 dependency is updated to address the CVE-2025-8916 vulnerability.

W-21289678

Mule Agent UBP plugin is updated to address the CVE-2025-48924 vulnerability.

W-21289717
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-10)2.7.10 **January 10 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The transitive jetty-server dependency is updated to address the CVE-2024-8184 vulnerability.

W-20525474
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-9)2.7.9 **December 4 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The transitive netty-codec dependency is updated to address the CVE-2025-58057 vulnerability.

W-20142478

The transitive netty-codec-http dependency is updated to address the CVE-2025-58056 vulnerability.

W-201424798

The transitive org.glassfish.jersey.core:jersey-client dependency is updated to address the CVE-2025-12383 vulnerability.

W-20266857

The Runtime Manager agent FIPS installation now works correctly on Windows machines with Java 11 or later.

W-19842756

The keepalive service now shuts down correctly when a Mule instance is deleted.

W-13847247

Keepalive messages from Runtime Manager Agent to Runtime Manager now include logging to help diagnose network issues.

W-19721110
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-8)2.7.8 **October 24 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

Runtime Manager agent logging is now enhanced to improve network diagnostics.

W-19721110

The Trace method now returns the correct HTTP status code.

W-18751510

The mule-agent-ubb-module dependency is updated to the latest version.

W-19057569
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-7)2.7.7 **August 29 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

Application JAR signature validation now works with Java 17.

W-19247658

Runtime Manager agent now reports JVM initial and maximum heap size metrics.

W-19092305
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-6)2.7.6 **July 31 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

CloudHub 2.0 can now capture application events for pricing calculation.

W-19013687
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-5)2.7.5 **June 20 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The transitive commons-beanutils dependency is updated to address the CVE-2025-48734 vulnerability.

W-18679781

The transitive jetty-server dependency is updated to address the CVE-2024-6763, CVE-2024-13009, and CVE-2024-8184 vulnerabilities.

W-18665780

Runtime Manager agent now works correctly in FIPS-configured PCE environments.

W-18719047
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-4)2.7.4 **May 30 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The transitive logback-core dependency is updated to address the CVE-2024-12798 vulnerability.

W-18220563

Agents running only Windows OS are enhanced to avoid disk buffering issues.

W-18623872
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-3)2.7.3 **April 4 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

All Spring Framework Dependencies in Runtime Manager agent have been removed.

W-17818536

Resolve Incorrect Transient Application Status Bug.

W-17990784

commons.io has been updated to resolve the CVE-2024-47554 security vulnerability.

W-17776646

com.google.code.gson has been updated to resolve the sonatype-2025-000535 security vulnerability.

W-17896352
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-2)2.7.2 **March 25 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
This Runtime Manager agent version 2.7.2 supports keystore.type=FIPS and bouncycastle.fips.approved_only mode for strong secure compliance.
### Fixed Issues
Issue Resolution ID

FIPS upgrade script amc_setup now detects the fips model automatically.

W-14933954

Runtime Manager agent now supports FIPS keystore.

W-16597799

Runtime Manager agent now honors all the ciphers in the cipher list in tls-fips140-2.conf file, some were getting ignored before.

W-16359169

The io.netty:netty-handler package is updated to fix the CVE-2025-24970 security vulnerability.

W-17896363

The async-http-client library is updated to fix the CVE-2024-53990 security vulnerability.

W-17912724

The configuration watcher now works as expected in Runtime Fabric on OpenShift.

W-17507230
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-1)2.7.1 **March 14 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
Before upgrading to Runtime Manager agent 2.7.1, review the upgrade requirement below.
### Fixed Issues
Issue Resolution ID

Runtime manager agent upgrade now works correctly in FIPS configured environments.

W-17866706

Runtime manager agent startup now works correctly in FIPS configured environments.

W-17937015
### Upgrade If FIPS has been enabled, ensure the upgrade is run using the command: `amc_setup -U --fips`. ### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-7-0)2.7.0 **February 17 2025**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### What’s New Runtime Manager agent 2.7.0 introduces these enhancements: - Ability to capture flow and message metrics is now available. - Certificates are now renewed during Runtime Manager agent upgrades. ### Fixed Issues
Issue Resolution ID

The DiskBuffer integration no longer prevents Runtime Manager agent from starting up.

W-17292380

io.netty dependency has been upgraded to 4.1.115.Final.

W-16918281

Insights are now displayed for customers' Mule runtime.

W-16462759

Ingress Gateway is now supported in Hyperforce.

W-16899987
### Compatibility
This Runtime Manager agent version is compatible with all HSA flavors, including GovCloud and PCE. However, FIPS is not certified in this version. If you need to enable FIPS, we recommend skipping this version.
### [](#upgrade-requirements)Upgrade Requirements Before installing or upgrading to Runtime Manager agent 2.7.0, review the updated network configuration requirements on [Ports](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-allowlists#ports) and [Dynamics IP Addresses](https://docs.mulesoft.com/jp/runtime-manager/rtm-agent-allowlists#dynamic-ip-addresses).
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.4.0-20221111 and later.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent 2.8.x Release Notes ## [](#2-8-5)2.8.5 **Sep 24 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The agent logging endpoint now deserializes artifact and scope logging configurations correctly on Java 25, preventing unknown runtime status and log-level failures.

W-24110885

The agent now injects the Tooling Service correctly in Mule 4.12.

W-22692660

Changing an application’s log level no longer removes existing Log4j appender references or changes logger additivity. Clearing the change restores the original log level.

W-18145972

Undeploying an application no longer resequences unrelated additional Java properties in the wrapper.conf file.

W-23716595

Timed-out WebSocket connection attempts are now canceled before the agent starts another connection attempt.

W-24093711

The deployment operation status tracking API introduced in Runtime Manager agent 2.8.3 is removed.

W-23438297

The UBB plugin is upgraded from 1.1.4 to 1.1.6.

W-24048672, W-24276290

The avro dependency is upgraded to 1.12.1 to address reported security vulnerabilities.

W-3300013

The plexus-utils dependency is upgraded to 4.1.0 to address reported security vulnerabilities.

W-3300013

The snakeyaml dependency is upgraded to 2.4 to address reported security vulnerabilities.

W-3300013

The io.netty dependency is upgraded to 4.2.18.Final to address reported security vulnerabilities.

W-3300013

The jackson-databind dependency is upgraded to 2.22.3 to address reported security vulnerabilities.

W-3300013
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-8-4)2.8.4 **Aug 21 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The jetty dependency is upgraded to 12.1.12 to address CVE vulnerabilities.

W-23716580

The io.netty dependency is upgraded to 4.2.17.Final to address CVE vulnerabilities.

W-23716580, W-3300013

The bouncycastle dependency is upgraded to 1.85 to address CVE vulnerabilities.

W-23716580, W-3300013

The jackson-databind dependency is upgraded to 2.22.2 to address CVE vulnerabilities.

W-3300013

The wire-runtime dependency is upgraded to 6.4.1 to address CVE vulnerabilities.

W-23716580

The commons-lang (v2) dependency is replaced by commons-lang3 to address CVE vulnerabilities.

W-23564887

The jsendnsca dependency is upgraded to 2.2.0 to remove the transitive end-of-life commons-lang(v2) dependency.

W-23564887
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-8-3)2.8.3 **Jul 29 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

Fix Jetty 12 connection issue.

W-23427722

A new REST endpoint now provides deployment status reporting used by CloudHub 1.0 runtimes.

W-23438297
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-8-2)2.8.2 **Jul 14 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The jackson-core dependency is upgraded to 2.22.0 to address CVE vulnerabilities.

W-22806004, W-23037571

The log4j-core dependency is upgraded to 2.26.1 to address CVE vulnerabilities.

W-22939392

The wire-runtime-jvm dependency is upgraded to 6.3.0 to address CVE vulnerabilities.

W-21688020

The commons-configuration2 and commons-io dependencies are upgraded to 2.15.1 and 2.22.0 respectively to address CVE vulnerabilities.

W-22806009
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-8-1)2.8.1 **Jun 17 2026**
For the best performance and stability on Windows deployments, use Runtime Manager agent 2.7.4 and later.
### Fixed Issues
Issue Resolution ID

The ConfigurationWatcher no longer generates unnecessary error logs during a Mule upgrade.

W-22734121

The amc_setup --encrypt command now uses a strong cryptographic algorithm to encrypt mule-agent.yaml.

W-22678184

The plexus-utils dependency is upgraded to 4.0.3

W-22389904

The io.netty dependency is upgraded to 4.2.15.Final

W-22389904

The async-http-client dependency is upgraded to 2.15.0

W-22389904, W-22052914
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16+ for FIPS-140-3 and 4.11.3+ for TLS 1.3 support.

Java

JRE/JDK 1.8.0, JDK 11, and JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#2-8-0)2.8.0 **June 9 2026**
Runtime Manager agent 2.8.0 and later is compatible only with JDK 17 and requires Runtime Manager 4.9.0 and later.
### Fixed Issues
Issue Resolution ID

The Jetty HTTP library is updated to address CVE-2026-2332.

W-22391892

The Jetty library is upgraded to version 12.

W-22203900

Runtime Manager agent now compiles and packages with Java 17.

W-22163115
### Compatibility
Software Version

Mule runtime engine

This Runtime Manager agent version is compatible with Mule 4.9.16 and later for FIPS 140-3 and Mule 4.11.3 and later for TLS 1.3 support.

Java

JDK 17 (4.6.x and later).

OS

MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 9, and Ubuntu Server 20.04.
## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Agent Release Notes _Enterprise Edition_ The [Runtime Manager agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) is a plugin extension for a Mule runtime engine that exposes the Mule API. Using Runtime Manager agent, you can monitor and control your Mule servers by calling APIs from external systems, or have Mule publish its own data to external systems. The Anypoint Runtime Manager agent does not automatically update to the latest version available. After initial installation, you need to manually update the agent version. See [Runtime Manager エージェントのインストールまたは更新](https://docs.mulesoft.com/jp/runtime-manager/installing-and-configuring-runtime-manager-agent). The version of Runtime Manager agent must support the version of Mule and Runtime Manager you are using. Check the following release notes to determine compatibility: - [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5) - [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4) - [Runtime Manager Agent 2.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-3) - [Runtime Manager Agent 2.8.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-2) - [Runtime Manager Agent 2.8.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-1) - [Runtime Manager Agent 2.8.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-0) - [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20) - [Runtime Manager Agent 2.7.19 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-19) - [Runtime Manager Agent 2.7.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-18) - [Runtime Manager Agent 2.7.17 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-17) - [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16) - [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15) - [Runtime Manager Agent 2.7.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-14) - [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13) - [Runtime Manager Agent 2.7.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-12) - [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11) - [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10) - [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9) - [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8) - [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7) - [Runtime Manager Agent 2.7.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-6) - [Runtime Manager Agent 2.7.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-5) - [Runtime Manager Agent 2.7.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-4) - [Runtime Manager Agent 2.7.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-3) - [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2) - [Runtime Manager Agent 2.7.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-1) - [Runtime Manager Agent 2.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-0) - [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7) - [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6) - [Runtime Manager Agent 2.6.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-5) - [Runtime Manager Agent 2.6.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-4) - [Runtime Manager Agent 2.6.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-3) - [Runtime Manager Agent 2.6.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-2) - [Runtime Manager Agent 2.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-1) - [Runtime Manager Agent 2.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-0) - [Runtime Manager Agent 2.5.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-10) - [Runtime Manager Agent 2.5.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-9) - [Runtime Manager Agent 2.5.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-8) - [Runtime Manager Agent 2.5.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-7) - [Runtime Manager Agent 2.5.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-6) - [Runtime Manager Agent 2.5.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-5) - [Runtime Manager Agent 2.5.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-4) - [Runtime Manager Agent 2.5.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-3) - [Runtime Manager Agent 2.5.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-2) - [Runtime Manager Agent 2.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-1) - [Runtime Manager Agent 2.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.5.x-release-notes#2-5-0) - [Runtime Manager Agent 2.4.37 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-37) - [Runtime Manager Agent 2.4.36 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-36) - [Runtime Manager Agent 2.4.35 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-35) - [Runtime Manager Agent 2.4.34 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-34) - [Runtime Manager Agent 2.4.33 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-33) - [Runtime Manager Agent 2.4.32 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-32) - [Runtime Manager Agent 2.4.31 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-31) - [Runtime Manager Agent 2.4.30 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-30) - [Runtime Manager Agent 2.4.29 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-29) - [Runtime Manager Agent 2.4.28 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-28) - [Runtime Manager Agent 2.4.27 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-27) - [Runtime Manager Agent 2.4.26 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-26) - [Runtime Manager Agent 2.4.25 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-25) - [Runtime Manager Agent 2.4.24 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-24) - [Runtime Manager Agent 2.4.23 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-23) - [Runtime Manager Agent 2.4.22 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-22) - [Runtime Manager Agent 2.4.21 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-21) - [Runtime Manager Agent 2.4.20 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-20) - [Runtime Manager Agent 2.4.19 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-19) - [Runtime Manager Agent 2.4.18 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-18) - [Runtime Manager Agent 2.4.17 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-17) - [Runtime Manager Agent 2.4.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-16) - [Runtime Manager Agent 2.4.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-15) - [Runtime Manager Agent 2.4.14 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-14) - [Runtime Manager Agent 2.4.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-13) - [Runtime Manager Agent 2.4.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-12) - [Runtime Manager Agent 2.4.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-11) - [Runtime Manager Agent 2.4.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-10) - [Runtime Manager Agent 2.4.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-9) - [Runtime Manager Agent 2.4.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-8) - [Runtime Manager Agent 2.4.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-7) - [Runtime Manager Agent 2.4.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-6) - [Runtime Manager Agent 2.4.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-5) - [Runtime Manager Agent 2.4.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-4) - [Runtime Manager Agent 2.4.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-3) - [Runtime Manager Agent 2.4.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-2) - [Runtime Manager Agent 2.4.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-1) - [Runtime Manager Agent 2.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.4.x-release-notes#2-4-0) - [Runtime Manager Agent 2.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.3.x-release-notes#2-3-0) - [Runtime Manager Agent 2.2.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.2.x-release-notes#2-2-1) - [Runtime Manager Agent 2.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.2.x-release-notes#2-2-0) - [Runtime Manager Agent 2.1.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.1.x-release-notes#2-1-9) - [Runtime Manager Agent 2.1.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.1.x-release-notes#2-1-8) - [Runtime Manager Agent 2.1.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.1.x-release-notes#2-1-7) - [Runtime Manager Agent 2.1.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.1.x-release-notes#2-1-6) **Mule Agent Plugin 1.x:** - [Runtime Manager Agent 1.16.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.16.x-release-notes#1-16-0) - [Runtime Manager Agent 1.15.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-13) - [Runtime Manager Agent 1.15.12 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-12) - [Runtime Manager Agent 1.15.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-11) - [Runtime Manager Agent 1.15.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-10) - [Runtime Manager Agent 1.15.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-9) - [Runtime Manager Agent 1.15.8 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-8) - [Runtime Manager Agent 1.15.7 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-7) - [Runtime Manager Agent 1.15.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-6) - [Runtime Manager Agent 1.15.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-5) - [Runtime Manager Agent 1.15.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-4) - [Runtime Manager Agent 1.15.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-3) - [Runtime Manager Agent 1.15.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-2) - [Runtime Manager Agent 1.15.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-1) - [Runtime Manager Agent 1.15.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.15.x-release-notes#1-15-0) - [Runtime Manager Agent 1.14.6 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.14.x-release-notes#1-14-6) - [Runtime Manager Agent 1.14.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.14.x-release-notes#1-14-5) - [Runtime Manager Agent 1.14.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.14.x-release-notes#1-14-4) - [Runtime Manager Agent 1.14.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.14.x-release-notes#1-14-3) - [Runtime Manager Agent 1.14.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.14.x-release-notes#1-14-2) - [Runtime Manager Agent 1.14.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.14.x-release-notes#1-14-1) - [Runtime Manager Agent 1.14.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.14.x-release-notes#1-14-0) - [Runtime Manager Agent 1.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.13.x-release-notes#1-13-0) - [Runtime Manager Agent 1.12.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.12.x-release-notes#1-12-2) - [Runtime Manager Agent 1.12.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.12.x-release-notes#1-12-1) - [Runtime Manager Agent 1.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.12.x-release-notes#1-12-0) - [Runtime Manager Agent 1.11.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.11.x-release-notes#1-11-3) - [Runtime Manager Agent 1.11.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.11.x-release-notes#1-11-2) - [Runtime Manager Agent 1.11.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.11.x-release-notes#1-11-1) - [Runtime Manager Agent 1.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.11.x-release-notes#1-11-0) - [Runtime Manager Agent 1.10.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.10.x-release-notes#1-10-0) - [Runtime Manager Agent 1.9.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.9.x-release-notes#1-9-5) - [Runtime Manager Agent 1.9.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.9.x-release-notes#1-9-4) - [Runtime Manager Agent 1.9.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.9.x-release-notes#1-9-3) - [Runtime Manager Agent 1.9.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.9.x-release-notes#1-9-2) - [Runtime Manager Agent 1.9.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.9.x-release-notes#1-9-1) - [Runtime Manager Agent 1.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.9.x-release-notes#1-9-0) - [Runtime Manager Agent 1.8.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.8.x-release-notes#1-8-0) - [Runtime Manager Agent 1.7.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.7.x-release-notes#1-7-1) - [Runtime Manager Agent 1.7.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.7.x-release-notes#1-7-0) - [Runtime Manager Agent 1.6.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.6.x-release-notes#1-6-4) - [Runtime Manager Agent 1.6.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.6.x-release-notes#1-6-3) - [Runtime Manager Agent 1.6.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.6.x-release-notes#1-6-2) - [Runtime Manager Agent 1.6.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.6.x-release-notes#1-6-1) - [Runtime Manager Agent 1.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.6.x-release-notes#1-6-0) - [Runtime Manager Agent 1.5.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.5.x-release-notes#1-5-3) - [Runtime Manager Agent 1.5.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.5.x-release-notes#1-5-2) - [Runtime Manager Agent 1.5.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.5.x-release-notes#1-5-1) - [Runtime Manager Agent 1.5.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.5.x-release-notes#1-5-0) - [Runtime Manager Agent 1.4.2 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.4.x-release-notes#1-4-2) - [Runtime Manager Agent 1.4.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.4.x-release-notes#1-4-1) - [Runtime Manager Agent 1.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.4.x-release-notes#1-4-0) - [Runtime Manager Agent 1.3.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.3.x-release-notes#1-3-3) - [Runtime Manager Agent 1.3.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.3.x-release-notes#1-3-1) - [Runtime Manager Agent 1.3.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.3.x-release-notes#1-3-0) - [Runtime Manager Agent 1.2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.2.x-release-notes#1-2-0) - [Runtime Manager Agent 1.1.1 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-1.1.x-release-notes#1-1-1) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Release Notes - [Runtime Manager Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes) - [Runtime Manager Agent Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-release-notes) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Runtime Manager Release Notes Runtime Manager is the interface to [Anypoint Platform](https://anypoint.mulesoft.com/login/) that provides a unified view of your applications, servers, and APIs. As of August 11, 2023, these release notes describe all weekly updates impacting the Runtime Manager platform. Please, refer to the release notes for each product to check the specific release dates. For previous Runtime Manager release notes, see [Runtime Manager Release Notes Archive](https://docs.mulesoft.com/jp/release-notes/runtime-manager/runtime-manager-release-notes-archive). ## [](#week-of-october-5-2026)Week of October 5, 2026 ### What’s New - Mule runtime engine 4.13.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.13.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.13.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#week-of-june-1-2026)Week of June 1, 2026 ### What’s New - Mule runtime engine 4.12.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.12.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.12.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#week-of-february-2-2026)Week of February 2, 2026 ### What’s New - Mule runtime engine 4.11.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.11.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#week-of-november-17-2025)Week of November 17, 2025 ### What’s New **CloudHub** - CloudHub now includes reliability and resiliency enhancements to the UI. ## [](#week-of-october-27-2025)Week of October 27, 2025 ### What’s New **Runtime Manager UI** - You can now use the MuleSoft diagnostics agent to collect diagnostics data from your CloudHub and CloudHub 2.0 applications and analyze them with Einstein. See [Troubleshooting Applications](https://docs.mulesoft.com/jp/runtime-manager/troubleshooting#troubleshooting-applications). **CloudHub 2.0** - You can now use the MuleSoft diagnostics agent to collect diagnostics data from your CloudHub 2.0 applications and analyze them with Einstein. See [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/cloudhub-2/ch2-view-diag). **CloudHub** - You can now use the MuleSoft diagnostics agent to collect diagnostics data from your CloudHub applications and analyze them with Einstein. See [Generate Apps Diagnostics and Analyze with Einstein](https://docs.mulesoft.com/cloudhub/ch-diagnostics-agent). ## [](#week-of-september-29-2025)Week of September 29, 2025 ### What’s New - Mule runtime engine 4.10.0 is now available. For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#week-of-september-15-2025)Week of September 15, 2025 ### What’s New **Runtime Manager UI** - You can now use the in-product app migration tool in Runtime Manager to migrate your CloudHub applications to CloudHub 2.0. For more information, see [CloudHub to CloudHub 2.0 Application Migration](https://docs.mulesoft.com/cloudhub/app-migration). - You can now configure path rewriting per endpoint in your application’s **Ingress** configuration. When used in conjunction with the app migration tool, you can carry over differing mapping rules for different endpoints within the application. - You can now configure custom domains for internal endpoints that are only accessible from within your private network. Use the new **Access** field to specify internal or external access for your custom endpoints. **CloudHub 2.0** - You can now configure path rewriting per endpoint in your application’s **Ingress** configuration. When used in conjunction with the app migration tool, you can carry over differing mapping rules for different endpoints within the application. - You can now configure custom domains for internal endpoints that are only accessible from within your private network. Use the new **Access** field to specify internal or external access for your custom endpoints. ## [](#week-of-june-9-2025)Week of June 9, 2025 **Runtime Manager UI** ### Fixed Issues
Issue Resolution ID

SFTP connectors no longer display as manageable schedulers in Runtime Manager. This is only applicable to applications repackaged with Java 17 with the Mule Maven Plugin (MMP) version set to 4.5.1 in the application. Use either Anypoint Studio or Anypoint Code Builder to ensure that the mule-artifact.json file contains the field javaSpecificationVersions: ["17"].

W-14782361
## [](#week-of-april-21-2025)Week of April 21, 2025 **CloudHub 2.0** ### Fixed Issues
Issue Resolution ID

You can now revert applications from Mule runtime 4.9 to 4.4. For more information, see Known Issues.

W-17934919

You can now revert applications from Mule runtime 4.6 and above to 4.4. For more information, see Known Issues.

W-17934919
## [](#week-of-february-3-2025)Week of February 3, 2025 ### What’s New - Mule runtime engine 4.9.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.9.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). **Runtime Manager UI** ### What’s New - You can now use the in-product VPC upgrade tool in Runtime Manager to migrate your CloudHub dedicated Virtual Private Clouds (VPCs) to CloudHub 2.0 private spaces. For more information, see [CloudHub VPC to CloudHub 2.0 Private Space Upgrade](https://docs.mulesoft.com/cloudhub/vpc-upgrade). ## [](#week-of-october-14-2024)Week of October 14, 2024 ### Fixed Issues **CloudHub 2.0**
Issue Resolution ID

Schedulers configured with variable properties now work as expected after editing any of their settings.

W-13974038
## [](#week-of-october-7-2024)Week of October 7, 2024 ### What’s New - Mule runtime engine 4.8.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.8.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.8.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#week-of-september-30-2024)Week of September 30, 2024 ### Fixed Issues **CloudHub 2.0**
Issue Resolution ID

Schedulers configured with variable properties now function as expected after enabling or disabling them.

W-15058904
**Runtime Fabric**
Issue Resolution ID

Schedulers configured with variable properties now function as expected after enabling or disabling them.

W-15058904
See [CloudHub 2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes#august-18-2023). ## [](#week-of-september-9-2024)Week of September 9, 2024 ### Fixed Issues **CloudHub 2.0**
Issue Resolution ID

CloudHub 2.0 scheduler settings are now retained when redeploying an app using the Mule Maven plugin.

W-14325188
See [CloudHub 2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes#september-13-2024). ## [](#week-of-august-19-2024)Week of August 19, 2024 ### What’s New **CloudHub 2.0** - The maximum number of replicas per application deployed to CloudHub 2.0 is now 16 for organizations having the Anypoint Integration Advanced package or a Platinum or Titanium subscription to Anypoint Platform. **Runtime Fabric** - The maximum number of replicas per application deployed to Runtime Fabric is now 16. ## [](#week-of-july-8-2024)Week of July 8, 2024 ### What’s New **Runtime Manager UI** - The Runtime Manager UI now shows two different route tables in the Transit Gateways configuration section, one for specific routes added for the TGW attachment and another for all the VPC routes. For more information, see [Configure Transit Gateway Routing](https://docs.mulesoft.com/cloudhub/tgw-attach-arm#enable_outbound_traffic_from_vpc). ## [](#week-of-june-10-2024)Week of June 10, 2024 ### What’s New **CloudHub 2.0** - You can now deploy [`SNAPSHOT` version assets](https://docs.mulesoft.com/jp/exchange/to-publish-assets-maven#asset-lifecycle-state) to CloudHub 2.0 using the Mule Maven plugin without the need to increment your application’s version number manually. For more information, see [Exchange Snapshot Assets](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-maven#exchange-snapshot-assets). **Runtime Fabric** - You can now deploy [`SNAPSHOT` version assets](https://docs.mulesoft.com/jp/exchange/to-publish-assets-maven#asset-lifecycle-state) to Runtime Fabric using the Mule Maven plugin without the need to increment your application’s version number manually. For more information, see [Exchange Snapshot Assets](https://docs.mulesoft.com/runtime-fabric/latest/deploy-maven-4.x#exchange-snapshot-assets). ## [](#week-of-june-3-2024)Week of June 3, 2024 ### What’s New - Mule runtime engine 4.7.0 is now available. For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#week-of-march-4-2024)Week of March 4, 2024 ### What’s New **Runtime Manager UI** - Customers using the new pricing and packaging model can now enable CPU-based horizontal autoscaling when deploying applications to CloudHub 2.0. For more information, see [Horizontal Autoscaling](https://docs.mulesoft.com/jp/runtime-manager/deployment-strategies#horizontal-autoscaling). **CloudHub 2.0** - Customers using the new pricing and packaging model can now leverage CPU-based horizontal autoscaling on CloudHub 2.0. For more information, see [Configuring Horizontal Autoscaling (HPA) for CloudHub 2.0 Deployments](https://docs.mulesoft.com/cloudhub-2/ch2-configure-horizontal-autoscaling). ## [](#week-of-february-5-2024)Week of February 5, 2024 ### What’s New - Mule runtime engine 4.6.0 is now available. For information about the release notes, see [Mule Runtime Engine 4.6.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes). For information about the new release cadence, see [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). - You can now select between Java 8 and Java 17 when deploying a Mule application. ## [](#week-of-october-2-2023)Week of October 2, 2023 ### What’s New **Runtime Manager UI** - You can now use Mule 4.5 Edge release channel when deploying applications to CloudHub, CloudHub 2.0, and Runtime Fabric. - You can now see the Mule runtime version on the application list for CloudHub 2.0 and Runtime Fabric. ## [](#week-of-august-18-2023)Week of August 18, 2023 ### Fixed Issues **Runtime Manager UI**
Issue Resolution ID

You can now use protected properties to configure a custom log appender in CloudHub 2.0 targets. It requires update to the latest runtime 4.4 or 4.3 patch.

W-12756066
**CloudHub 2.0**
Issue Resolution ID

You can now use protected properties to configure a custom log appender. It requires update to the latest runtime 4.4 or 4.3 patch.

W-12756066
See [CloudHub 2.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/cloudhub-2/cloudhub-2-release-notes#august-18-2023). ## [](#week-of-august-11-2023)Week of August 11, 2023 ### What’s New **Runtime Manager UI** - You can now deploy apps with sizes up to 350 MB to Runtime Fabric targets. **Runtime Fabric** - You can now deploy apps with sizes up to 350 MB to Runtime Fabric targets. See [Anypoint Runtime Fabric 2.4.0 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-fabric/runtime-fabric-release-notes-2.x.x#2-4-0).
The application size limit of 350 MB for uploading and deploying apps to CloudHub 2.0 was released on April 24, 2023. See CloudHub 2.0 Release Notes.
## [](#see-also)See Also - [トラブルシューティング](https://docs.mulesoft.com/jp/runtime-manager/troubleshooting) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Commerce Cloud B2C Data Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce Commerce Cloud B2C Data APIs (B2C Data Connector) provides Mule users with a quick and easy way to integrate with Salesforce Commerce Cloud B2C Data API endpoints. Guide: [Commerce Cloud B2C Data Connector User Guide](https://docs.mulesoft.com/jp/commerce-cloud-b2c-data-connector/latest/) Unresolved include directive in modules/ROOT/pages/connector/commerce-cloud-b2c-data-connector-release-notes-mule-4.adoc - include::connectors::partial$b2c-connectors-deprecated.adoc\[\] ## [](#1-0-1)1.0.1 **April 25, 2025** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.6.14 and later

OpenJDK

8, 11, and 17
## [](#1-0-0)1.0.0 **October 8, 2020** New connector. ### [](#compatibility-2)Compatibility Salesforce Commerce Cloud B2C Data Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8 and 11
### [](#features)Features Salesforce Commerce Cloud B2C Data Connector provides access to Salesforce Commerce Cloud B2C Data APIs for the below workflows: - Assignments - Campaigns - Catalogs - Coupons - Customers - Gift Certificates - Orders - Products - Promotions - Source Code Groups ### [](#fixed-in-this-release)Fixed in This Release Not applicable. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Composite Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce Composite (Salesforce Composite Connector) provides a way to integrate with the Salesforce Composite API. The connector exposes convenient methods for preparing subrequests, executing them in a batch, and parsing the results. The connector provides DataSense for the preparation of subrequests and for parsing a response of an execution. Guide: [Salesforce Composite Connector](https://docs.mulesoft.com/salesforce-composite-connector/latest/) Reference: [Salesforce Composite Connector Reference](https://docs.mulesoft.com/salesforce-composite-connector/latest/salesforce-composite-connector-reference) ## [](#3-1-4)3.1.4 **September 25, 2026** ### Compatibility
Application or Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce Composite REST API

v67.0
### Fixed Issues
Issue Resolution ID

OAuth JWT connections that configure both a key store and a trust store now send REST API calls to port 8443, instead of port 443. A network rule that allows only port 443 blocks these calls until port 8443 is allowed. The previous behavior caused Salesforce to return HTTP 403 MUTUAL_AUTHENTICATION_FAILED.

W-24117375

These libraries are upgraded to address reported security vulnerabilities:

  • The org.bouncycastle:bcprov-jdk18on, org.bouncycastle:bcpkix-jdk18on, and org.bouncycastle:bcutil-jdk18on libraries are upgraded to version 1.86.

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.3.

  • The guava library is upgraded to version 33.7.1-jre.

W-24262985
## [](#3-1-3)3.1.3 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application or Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce Composite REST API

v67.0
## [](#3-1-2)3.1.2 **August 24, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application or Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce Composite REST API

v67.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-codec library is upgraded to version 1.22.1.

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.2.

W-23441730
## [](#3-1-1)3.1.1 **August 4, 2026** ### Compatibility
Application or Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce Composite REST API

v67.0
### Fixed Issues
Issue Resolution ID

Failed signing payload errors no longer occur when an OAuth JWT connection uses a keystore certificate that is CA-signed with an RSA algorithm other than SHA256withRSA, such as SHA384withRSA.

W-23543204

The commons-codec:commons-codec library is upgraded to version 1.22.1.

W-3300013
## [](#3-1-0)3.1.0 **July 20, 2026** ### What’s New - Salesforce Composite Connector now supports Salesforce API v67.0. - You can now tune the outbound HTTP connection pool for high-throughput workloads by using the new **Max Connections**, **Use Persistent Connections**, **Connection Idle Timeout**, and **Connection Idle Timeout Unit** parameters on the **Advanced** tab of the connection configuration. The default values match the Mule runtime defaults, so existing applications behave the same after you upgrade. ### Compatibility
Application or Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce Composite REST API

v67.0
### Fixed Issues
Issue Resolution ID

Testing the connection now succeeds for any authenticated user, including Government Cloud and restricted-profile users who don’t have access to the Account object. Previously, testing the connection failed with a 404 NOT_FOUND error for these users even when their credentials were valid.

W-23342593

These libraries are upgraded to address reported security vulnerabilities:

  • The org.bouncycastle:bcprov-jdk18on, org.bouncycastle:bcpkix-jdk18on, and org.bouncycastle:bcutil-jdk18on libraries are upgraded to version 1.85 to address CVE-2025-14813.

  • The org.apache.santuario:xmlsec library is upgraded to version 2.3.5.

  • The org.opensaml:opensaml-core, org.opensaml:opensaml-saml-api, and org.opensaml:opensaml-saml-impl libraries are upgraded to version 3.4.6.

  • The org.apache.httpcomponents:httpclient library is upgraded to version 4.5.14.

  • The org.cryptacular:cryptacular library is upgraded to version 1.3.0.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.1 to address CVE-2026-54512 and CVE-2026-54513.

W-23227978, W-23192339
## [](#3-0-0)3.0.0 **May 11, 2026** ### What’s New - This connector is now compatible with Java 17 only. - The connector now supports the new **OAuth Client Credentials** connection type. For more information, refer to [OAuth Client Credentials](https://docs.mulesoft.com/salesforce-composite-connector/latest/salesforce-composite-connector-reference#composite-config_oauth-client-credentials). ### Compatibility
Application or Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce Composite REST API

v66.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The commons-io library is upgraded to version 2.21.0.

  • The jackson-core library is upgraded to version 2.21.2.

W-22162659
## [](#2-21-0)2.21.0 **April 22, 2026** ### What’s New - Salesforce Composite Connector now supports Salesforce API v66.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v66.0
### Fixed Issues
Issue Resolution ID

The jackson-core library is upgraded to version 2.18.6 to address reported security vulnerabilities.

W-21980469
## [](#2-20-0)2.20.0 **October 26, 2025** ### What’s New - Salesforce Composite Connector now supports Salesforce API v65.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v65.0
## [](#2-19-0)2.19.0 **July 16, 2025** ### What’s New - Salesforce Composite Connector now supports Salesforce API v62.0, v63.0, and v64.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v64.0
## [](#2-18-1)2.18.1 **November 10, 2024** ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v61.0
### Fixed Issues
Issue Resolution ID

The connection now works when the password contains special characters.

W-16862726
## [](#2-18-0)2.18.0 **June 27, 2024** ### What’s New - Salesforce Composite Connector now supports Salesforce API v61.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v61.0
## [](#2-17-3)2.17.3 **May 13, 2024** ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v60.0
### Fixed Issues
Issue Resolution ID

The org.apache.santuario:xmlsec library is upgraded to version 2.2.6 to address reported security vulnerabilities.

W-15631266
## [](#2-17-2)2.17.2 **March 22, 2024** ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v60.0
### Fixed Issues
Issue Resolution ID

The connector now properly supports SSL/TLS when setting up the truststore configuration in the connection configuration.

W-15302732
## [](#2-17-1)2.17.1 **March 18, 2024** ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v60.0
### Fixed Issues
Issue Resolution ID

The Bouncy Castle library (bcprov-jdk15on) is removed to address reported security vulnerabilities.

W-15243934
## [](#2-17-0)2.17.0 **February 28, 2024** ### What’s New - Salesforce Composite Connector now supports Salesforce API v60.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v60.0
## [](#2-16-1)2.16.1 **January 15, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Salesforce Composite REST API

v59.0
## [](#2-16-0)2.16.0 **November 10, 2023** ### What’s New - Salesforce Composite Connector now supports Salesforce API v59.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v59.0
## [](#2-15-0)2.15.0 **June 20, 2023** ### What’s New - Salesforce Composite Connector now supports Salesforce API v58.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v58.0
## [](#2-14-0)2.14.0 **April 10, 2023** ### What’s New - Salesforce Composite Connector now supports Salesforce API v57.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v57.0
## [](#2-13-0)2.13.0 **October 17, 2022** ### What’s New - Salesforce Composite Connector now supports Salesforce API v56.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v56.0
## [](#2-12-1)2.12.1 **October 10, 2022** ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v55.0
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853400
## [](#2-12-0)2.12.0 **June 16, 2022** ### What’s New - Salesforce Composite Connector now supports Salesforce API v55.0. - Salesforce Composite Connector now supports authentication with **Token Connection**. For more information, refer to [Token Connection](https://docs.mulesoft.com/salesforce-composite-connector/latest/salesforce-composite-connector-reference#composite-config_token-connection). ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v55.0
## [](#2-11-1)2.11.1 **March 31, 2022** ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v54.0
### Fixed Issues
Issue ID

Upgraded com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.13.2.1.

W-10920495
## [](#2-11-0)2.11.0 **February 24, 2022** ### What’s New - Added support for Salesforce API v54.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v54.0
## [](#2-10-1)2.10.1 **January 7, 2022** ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v53.0
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the XMLSec library from com.fasterxml.jackson.core:jackson-databind:2.11.3 to com.fasterxml.jackson.core:jackson-databind:2.12.6.

CONN-9829
## [](#2-10-0)2.10.0 **October 20, 2021** ### What’s New - Added support for Salesforce API v53.0. ### Compatibility
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v53.0
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the XMLSec library from org.apache.santuario:xmlsec:2.1.4 to org.apache.santuario:xmlsec:2.2.3.

CONN-8996
## [](#2-9-1)2.9.1 **September 7, 2021** ### Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v52.0
### Fixed Issues
Issue ID

The connector used an expired access token for OAuth connection.

SE-22465
## [](#2-9-0)2.9.0 **June 14, 2021** ### [](#compatibility-28)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

Salesforce Composite REST API

v52.0
### [](#new-features)New Features - Added support for Salesforce API v52.0. ### [](#fixed-issues-16)Fixed Issues - Upgraded the BouncyCastle dependency `org.bouncycastle:bcprov-jdk15on:1.65` to `org.bouncycastle:bcprov-jdk15on:1.67` to fix a vulnerability issue. (CONN-8332) ## [](#2-8-1)2.8.1 **May 4, 2021** ### [](#compatibility-29)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v51
### [](#fixed-issues-17)Fixed Issues - Removed the Velocity dependency `org.apache.velocity:velocity:1.7` to fix security vulnerability issues. (CONN-7951) ## [](#2-8-0)2.8.0 **February 18, 2021** ### [](#compatibility-30)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v51
### [](#features)Features - Added support for Salesforce Composite API version 51.0. ## [](#2-7-0)2.7.0 **November 11, 2020** ### [](#compatibility-31)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v50
### [](#features-2)Features Added support for the OAuth 2.0, OAuth JWT, and OAuth SAML connection types. ## [](#2-6-0)2.6.0 **October 28, 2020** ### [](#compatibility-32)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v50
### [](#features-3)Features - Added support for Salesforce Composite API version 50.0. - Added the **Execute Composite Graph** operation to support Salesforce API v50.0 functionality. ### [](#fixed-issues-18)Fixed Issues - Upgraded the Jackson Databind dependency `com.fasterxml.jackson.core:jackson-databind:2.10.0` to `com.fasterxml.jackson.core:jackson-databind:2.11.3` to fix vulnerability issues. (CONN-7127) ## [](#2-5-0)2.5.0 **July 31, 2020** ### [](#compatibility-33)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v49
### [](#features-4)Features Support for Salesforce Composite API version 49.0 is added in this release. ## [](#2-4-0)2.4.0 **May 22, 2020** ### [](#compatibility-34)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v48
### [](#features-5)Features - Added support for Salesforce Composite API version 48.0 - Added `TLS configuration` parameter. If HTTPS is configured as the protocol, you must also have a keystore configured. - Response headers and status codes mapped in 'attributes' returned for all operations - Added optional `Connection timeout` parameter to configure the socket connection timeout value ## [](#2-3-1)2.3.1 **April 14, 2020** ### [](#compatibility-35)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v46
### [](#fixed-issues-19)Fixed Issues Upgraded Jackson Databind 2.8.11.1 to 2.10.0 to fix vulnerability issues. (CONN-5799) ## [](#2-3-0)2.3.0 **November 25, 2019** ### [](#compatibility-36)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v46
### [](#fixed-issues-20)Fixed Issues A timeout exception occurred when the response from Salesforce was delayed. You can now use the **Response timeout** parameter under the **Advanced** tab in **Global Element Properties** to specify how long to wait until a response is received. (SE-13369) ## [](#2-2-2)2.2.2 **October 25, 2019** ### [](#compatibility-37)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v46
### [](#fixed-issues-21)Fixed Issues - Fixed thread leaks issue. Threads were created and never disposed of properly when the connector was under a heavy work load. (SE-13644) ## [](#2-2-1)2.2.1 **October 24, 2019** ### [](#compatibility-38)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v46
### [](#fixed-issues-22)Fixed Issues - Fixed thread leaks issue. Threads were created and never disposed of properly when the connector was under a heavy work load. (SE-13644) ## [](#2-2-0)2.2.0 **September 2, 2019** ### [](#compatibility-39)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v46
### [](#features-6)Features - Added support for API version 46.0. - Implemented the `Upsert SObject Collections` operation, which was added with v46.0 of the API. ### [](#fixed-issues-23)Fixed Issues - Fixed an issue in the connection provider where reconnect forever did not work properly. (SE-12727) ## [](#2-1-0)2.1.0 **October 10, 2018** ### [](#compatibility-40)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.1 and later

SalesForce Composite REST API

v43
### [](#features-7)Features - Support for SalesForce Composite REST API v43. - Added CRUD Collections operations. - Added Execute Composite Request operation. ## [](#2-0-1)2.0.1 **October 22, 2018** ### [](#compatibility-41)Compatibility Salesforce Composite Connector is compatible with:
Application or Service Version

Mule

4.1.0 and later
### [](#fixed-issues-24)Fixed Issues Fixed an issue in the connection provider where the field for security token was not allowing blank values even if that field is not required by Salesforce. ## [](#2-0-0)2.0.0 **March 13, 2018** ### [](#compatibility-42)Compatibility Salesforce Composite Connector is compatible with:
Application/Service Version

Mule

4.1.0 and later
## [](#see-also)See Also - [Salesforce Composite API](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite.htm) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce (Salesforce Connector) provides access to the Salesforce APIs. Guide: [Salesforce Connector](https://docs.mulesoft.com/salesforce-connector/latest/) Reference: [Salesforce Connector Reference](https://docs.mulesoft.com/salesforce-connector/latest/salesforce-connector-reference) ## [](#12-0-5)12.0.5 **October 13, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

When using the OAuth Client Credentials connection type, the Invoke Apex Soap Method operation now renews the session after an INVALID_SESSION_ID or session-timeout fault, instead of continuing to use the expired session.

W-24083612

When using the OAuth Client Credentials connection type, metadata operations and Partner API operations now renew the session after an INVALID_SESSION_ID or session-timeout fault, instead of failing with a connectivity error.

W-23517165

The AllOrNoneHeader and CallOptions values in the Headers field are now applied on the Create Metadata, Update Metadata, Upsert Metadata, Delete Metadata, Read Metadata, List Metadata, Describe Metadata, Retrieve Metadata, Rename Metadata, and Deploy Metadata operations. Previously, these values were ignored.

W-24209547

The connector no longer includes the archived mule-connector-logging library, version 1.0.2, which has no published license metadata. Connector logging behavior is unchanged.

W-24327308

These libraries are upgraded to address reported security vulnerabilities:

  • The xmlschema-core library is upgraded to version 2.3.3.

  • The jackson-databind library is upgraded to version 2.22.3.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-collections4 library is upgraded to version 4.6.0.

  • The commons-text library is upgraded to version 1.15.0.

  • The cxf-rt-wsdl library is upgraded to version 4.2.3.

W-24369627, W-24137088, W-3300013

Apache Commons Collections 3.x is removed to address the sonatype-2024-3350 security vulnerability.

W-24209547
## [](#12-0-4)12.0.4 **September 23, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

Streaming sources now reconnect and resume receiving events when a connection failure occurs during an in-progress restart. Previously, these sources stopped receiving events until the application was restarted.

W-24228300

The jackson-core library is upgraded to version 2.22.3 to address reported security vulnerabilities.

W-3300013
## [](#12-0-3)12.0.3 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

The test-only allure-junit4 dependency is no longer included in the shipped connector artifact.

W-24098525

The Invoke Apex REST operation now serializes request bodies using UTF-8 instead of the JVM default character encoding.

W-23682552

When uploading a batch fails, the Create Job Bulk API v2 operation now aborts the job instead of leaving it in the Open state.

W-23422580

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.2.

  • The jackson-annotations library is upgraded to version 2.22.

  • The jetty library is upgraded to version 12.1.13.

  • The commons-codec library is upgraded to version 1.22.1.

  • The cxf-rt-wsdl library is upgraded to version 4.1.8.

W-3300013
## [](#12-0-2)12.0.2 **August 20, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

Streaming sources no longer leak background worker threads, which previously accumulated over time and could degrade application performance.

W-23841225

The jakarta.mail library is upgraded to version 1.6.8 to address a reported security vulnerability.

W-23795603
## [](#12-0-1)12.0.1 **August 6, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

The Merge operation no longer returns an error resolving metadata for the Master Record input parameter.

W-17715398

When Cache Events In Memory is set to false (the default), streaming sources now correctly update the replay ID after processing events, preventing duplicate event reprocessing.

W-22893114

These libraries are upgraded to address reported security vulnerabilities:

  • The jetty library is upgraded to version 12.1.12.

  • The cometd library is upgraded to version 8.0.12.

W-3300013
## [](#12-0-0)12.0.0 **July 21, 2026** ### What’s New - This connector is now compatible with Java 17 only. - The **OAuth Username Password** connection type is removed because Salesforce is retiring the OAuth 2.0 Username-Password flow. Applications that use this connection type fail to deploy on 12.0.0. Migrate to another supported connection type, such as [OAuth 2.0](https://docs.mulesoft.com/salesforce-connector/latest/salesforce-connector-reference#sfdc-config_config-with-oauth), [OAuth Client Credentials](https://docs.mulesoft.com/salesforce-connector/latest/salesforce-connector-reference#sfdc-config_oauth-client-credentials), [OAuth JWT](https://docs.mulesoft.com/salesforce-connector/latest/salesforce-connector-reference#sfdc-config_jwt), or [OAuth SAML](https://docs.mulesoft.com/salesforce-connector/latest/salesforce-connector-reference#sfdc-config_saml). - The new **Query Time Buffer (Seconds)** field enables you to configure a polling time buffer (from `0` to `120` seconds) for source listeners to prevent missing records committed between polls for the **On New Object**, **On Modified Object**, and **On Deleted Object** sources. The query buffer time for the **On Modified Object** source now defaults to `0` seconds, instead of the former hardcoded default of `2` seconds. Applications that rely on the previous 2-second buffer must explicitly configure this value in the **Query Time Buffer (Seconds)** field. For more information, see [Salesforce Connector Reference](https://docs.mulesoft.com/salesforce-connector/latest/salesforce-connector-reference). For more information about how to upgrade, see [Upgrading and Migrating Salesforce Connector to 12.x](https://docs.mulesoft.com/salesforce-connector/latest/salesforce-connector-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

The On Modified Object source now honors the read timeout configured in the connector configuration for internal DescribeSObjects calls. Previously, these calls defaulted to an infinite timeout (readTimeout=0), which caused connections to hang under certain network conditions.

W-20080289

These libraries are upgraded to address reported security vulnerabilities:

  • The Apache CXF library is upgraded to version 4.1.7.

  • The jackson-core and jackson-databind libraries are upgraded to version 2.21.5.

  • The woodstox-core library is upgraded to version 6.7.0.

  • The httpclient library is upgraded to version 4.5.14.

  • The commons-codec library is upgraded to version 1.22.0.

  • The opencsv library is upgraded to version 5.12.0.

  • The jackson-annotations library is upgraded to version 2.21.

  • The gson library is upgraded to version 2.12.0.

  • The jaxws-rt library is upgraded to version 2.3.7.

  • The jetty library is upgraded to version 12.1.10.

  • The cometd-java library is upgraded to version 8.0.7.

W-23198392, W-21363914, W-22929772, W-23192337, W-22894638
## [](#11-5-0)11.5.0 **June 25, 2026** ### What’s New - Salesforce Connector now supports Salesforce API v67.0. ### Compatibility
Application/Service Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
## [](#11-4-0)11.4.0 **April 5, 2026** ### What’s New - Salesforce Connector now supports Salesforce API v66.0. ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0
### Fixed Issues
Issue Resolution ID

The variable name for Time unit is changed from objectTTLUnit to objectTTLTimeUnit. The display name (Time unit) remains unchanged.

W-21082898

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core library is upgraded to version 2.18.6.

  • The commons-text library is upgraded to version 1.14.0.

  • The guava library is upgraded to version 32.1.3-jre.

  • The mule-connector-logging library is upgraded to version 1.0.2.

W-21713141
## [](#11-3-4)11.3.4 **March 20, 2026** ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0
### Fixed Issues
Issue Resolution ID

The variable names for Object TTL and Time unit are changed from objectTTLTimeout and objectTTLTimeoutUnit to objectTTL and objectTTLUnit to resolve a backward compatibility break introduced in version 11.3.0. Previously, this change caused existing applications to fail during build with an error stating that the objectTTL attribute was not allowed. The display names (Object TTL and Time unit) remain unchanged.

W-21082898

The jetty.version library is upgraded to version 9.4.58.v20250814 to address reported security vulnerabilities.

W-21577093
## [](#11-3-3)11.3.3 **January 21, 2026** ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0
### Fixed Issues
Issue Resolution ID

The Token field is renamed to Security Token for the Basic Authentication connection type.

W-19987844

The connector now handles Apex class failure responses correctly and no longer throws the java.lang.ClassCastException error when propagating errors from Salesforce. Previously, when an Apex class returned a failure response code, the connector failed to cast SalesforceException to ModuleException, preventing proper error propagation.

W-20089710

The connector now correctly closes the streaming connection for the Replay Channel Listener source before attempting a source restart during 403 or 401 error scenarios. By stopping the streaming client before raising a connection exception, the connector prevents a leak where multiple client IDs remain active and receive the same platform events.

W-20604291
## [](#11-3-2)11.3.2 **December 7, 2025** ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0
### Fixed Issues
Issue Resolution ID

The connector with the OAuth Client Credentials connection type now renews the token when an INVALID_SESSION_ID error occurs in the Create Job and Create Job Bulk Api V2 operations.

W-19714693
## [](#11-3-1)11.3.1 **November 19, 2025** ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0
### Fixed Issues
Issue Resolution ID

The Spring Framework dependency now excludes the spring-context and spring-aop libraries to address the CVE-2024-38820 security vulnerability.

W-19805552
## [](#11-3-0)11.3.0 **October 3, 2025** ### What’s New - Salesforce Connector now supports Salesforce API v65.0. - The connector no longer supports the **Basic Authentication** connection type for the Salesforce API v65.0. - The variable names for **Object TTL** and **Time unit** are changed from `objectTTL` and `objectTTLTimeUnit` to `objectTTLTimeout` and `objectTTLTimeoutUnit`. The display names (**Object TTL** and **Time unit**) remain unchanged. ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0
## [](#11-2-3)11.2.3 **September 12, 2025** ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0
### Fixed Issues
Issue Resolution ID

For the OAuth JWT connection type, the connector now uses the SHA256WithRSA algorithm to sign certificates by default.

W-19075988
## [](#11-2-2)11.2.2 **September 4, 2025** ### Compatibility
Application/Service Version

Mule

4.6.6 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v37.0, v38.0, v39.0, v40.0, v41.0, v42.0, v43.0, v44.0, v45.0, v46.0, v47.0, v48.0, v49.0, v50.0, v51.0, v52.0, v53.0, v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0
### Fixed Issues
Issue Resolution ID

The Query xml stream operation now correctly throws the SALESFORCE:INVALID_INPUT error instead of the MULE:UNKNOWN error when invalid input is provided.

W-18779869

The connector with the OAuth Client Credentials connection type now renews the token when an INVALID_SESSION_ID error occurs in the Invoke apex rest method operation.

W-19003555
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Data Cloud Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce Data Cloud (Salesforce Data Cloud Connector) provides MuleSoft developers with a quick and easy way to integrate with Salesforce Data 360 (formerly Salesforce Data Cloud) API endpoints. Users can automate data ingestion from third parties, query the Data 360 Data Lake, search and query customer profile information and calculated insights, and consume data action events to enrich the 360-degree view of their customers in their Data 360 instance. Guide: [Salesforce Data Cloud Connector User Guide](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/) ## [](#1-5-1)1.5.1 **September 24, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-5-0)1.5.0 **August 20, 2026** ### What’s New - The connector now includes these Query v3 operations: - **Query v3** - **Query v3 - Get Status** - **Query v3 - Get Rows** - **Query v3 - Get Chunk** - **Query v3 - Get Metadata** - **Query v3 - Cancel** For more information, see [Salesforce Data Cloud Connector Reference](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-reference) and [Salesforce Data Cloud Connector Examples](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-examples). For more information about migration, see [Migrate to Query API V3](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-migration.html). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-4-0)1.4.0 **April 2, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

For the OAuth JWT flow connection type, the connector now automatically sets the keystore type to BCFKS when operating in a FIPS-compliant environment.

W-21802214
## [](#1-3-1)1.3.1 **April 11, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This connector version supports Maven 3.6.x and earlier.

W-18256219
## [](#1-3-0)1.3.0 **April 11, 2025**
Salesforce Data Cloud 1.3.0 doesn’t support Maven 3.6.x and earlier. All other Salesforce Data Cloud connector versions support Maven 3.6.x and earlier.
### What’s New - This connector now supports the OAuth Client Credentials connection type. For more information, refer to [OAuth Client Credentials](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-reference#SdcConfig_OauthClientCredentials). - This connector now includes the new **Bulk - List Jobs** operation. For more information, refer to [Bulk - List Jobs](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-reference#GetBulkJobs). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-collections dependency is excluded to address reported security vulnerabilities. Now, the connector includes a direct dependency to version 4.4 of commons-collections4.

W-16842162
## [](#1-2-1)1.2.1 **July 12, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The OAuth JWT and OAuth Username Password connection types now include the new Data Space field.

W-14227473
## [](#1-2-0)1.2.0 **June 13, 2024** ### What’s New - This connector is now compatible with Java 17. - You can now use the following new operations: - **Query V2** Supports SQL queries in ANSI standard and returns results as an array of records. The input objects include data stream, profile and engagement data model objects, and unified data model objects. For more information, see [Query v2](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-reference#QueryAnsiSqlV2). - **Query v2 - Get Next Batch** Returns the next batch of data from the initial POST request. For more information, see [Query v2 - Get Next Batch](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-reference#GetNextBatchAnsiSqlV2). - The connector is rebranded from Anypoint Connector for Salesforce CDP to Anypoint Connector for Salesforce Data Cloud (Salesforce Data Cloud Connector). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-0)1.1.0 **January 4, 2022** ### What’s New - Added operations to look up and search customer profile information using the [Salesforce CDP Profile API Library](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/c360a-api-profile-call-overview.html). - Added operations to query calculated insights using the [Salesforce CDP Calculated Insights API Library](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/c360a-api-ci-call-overview.html). - Added a **Data Action Webhook** source and configuration to consume [Salesforce CDP Data Action](https://help.salesforce.com/s/articleView?id=data.c360_a_data_actions.htm&type=5) events. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#1-0-1)1.0.1 **October 29, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The OAuth JWT configuration didn’t support a relative path for keystore file.

W-10099284
## [](#1-0-0)1.0.0 **October 14, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the [Salesforce Data Cloud Connector Reference Guide](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-reference). ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Data Cloud Connector Reference](https://docs.mulesoft.com/salesforce-data-cloud-connector/latest/salesforce-data-cloud-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Einstein Analytics Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce Einstein Analytics (Salesforce Einstein Analytics Connector) enables you to connect to the Salesforce Analytics Cloud application using Salesforce External Data API. The connector exposes convenient methods for creating and populating data sets into the Salesforce Analytics Cloud system. Guide: [Salesforce Analytics Cloud Connector](https://docs.mulesoft.com/salesforce-analytics-cloud-connector/latest/) Reference: [Salesforce Analytics Cloud Connector Reference](https://docs.mulesoft.com/salesforce-analytics-cloud-connector/latest/salesforce-analytics-connector-reference) ## [](#4-0-0)4.0.0 **September 28, 2026** ### What’s New - This release includes general security fixes. - Salesforce Einstein Analytics Connector now supports the [OAuth Client Credentials](https://docs.mulesoft.com/salesforce-analytics-cloud-connector/latest/salesforce-analytics-connector-reference#salesforce-analytics_oauth-client-credentials) connection type, which enables automated, server-to-server integrations that don’t require user interaction. For more information about how to upgrade, see [Upgrading and Migrating Salesforce Einstein Analytics Connector to Version 4.x](https://docs.mulesoft.com/salesforce-analytics-cloud-connector/latest/salesforce-analytics-connector-upgrade). ### Compatibility
Application/Service Version

Mule

4.6.0 and later

External Data API

v67.0

OpenJDK

8, 11, and 17
## [](#3-21-1)3.21.1 **August 6, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v67.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.bouncycastle:bcpkix-jdk18on library is upgraded to version 1.85 to address reported security vulnerabilities.

W-3300013
## [](#3-21-0)3.21.0 **July 8, 2026** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v67.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v67.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The org.apache.santuario:xmlsec library is upgraded to version 2.3.5.

  • The com.fasterxml.jackson.core:jackson-databind library is upgraded to version 2.22.1.

  • The commons-codec:commons-codec library is upgraded to version 1.22.0.

  • The com.fasterxml.woodstox:woodstox-core library is upgraded to version 6.7.0.

W-23227976
## [](#3-20-0)3.20.0 **April 29, 2026** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v66.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v66.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The bcpkix-jdk18on library is upgraded to version 1.84 to address reported security vulnerabilities.

W-22212117
## [](#3-19-0)3.19.0 **October 29, 2025** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v65.0. - The connector no longer supports the `Username Password` connection type for Salesforce API v65.0. Support is limited to Salesforce API v64.0 and below. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v65.0

OpenJDK

8, 11, and 17
## [](#3-18-0)3.18.0 **July 16, 2025** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v62.0, v63.0, and v64.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v64.0

OpenJDK

8, 11, and 17
## [](#3-17-1)3.17.1 **June 25, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v61.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Custom timezone support now works as expected when enabled from the Salesforce instance.

W-16063160
## [](#3-17-0)3.17.0 **June 24, 2024** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v61.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v61.0

OpenJDK

8, 11, and 17
## [](#3-16-0)3.16.0 **April 18, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v60.0

OpenJDK

8, 11, and 17
## [](#3-15-0)3.15.0 **February 29, 2024** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v60.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v60.0

OpenJDK

8, 11, and 17
## [](#3-14-2)3.14.2 **February 7, 2024** ### What’s New - The com.fasterxml.woodstox library is upgraded to version 6.6.0 to address reported security vulnerabilities. - The com.google.guava library is upgraded to version 33.0.0 to address reported security vulnerabilities. - The com.fasterxml.jackson.core library is upgraded to version 2.16.1 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v59.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The following libraries are updated to address reported security vulnerabilities:

  • The com.fasterxml.woodstox library is upgraded to version 6.6.0.

  • The com.google.guava library is upgraded to version 33.0.0.

  • The com.fasterxml.jackson.core library is upgraded to version 2.16.1.

W-14911031
## [](#3-14-1)3.14.1 **January 16, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v59.0

OpenJDK

8, 11, and 17
## [](#3-14-0)3.14.0 **November 8, 2023** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v59.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v59.0

OpenJDK

8 and 11
## [](#3-13-1)3.13.1 **September 22, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v58.0
### Fixed Issues
Issue ID

The connector now supports DateOnly field types in the metadata files.

W-14128054
## [](#3-13-0)3.13.0 **June 20, 2023** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v58.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v58.0
## [](#3-12-0)3.12.0 **April 10, 2023** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v57.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v57.0
## [](#3-11-1)3.11.1 **November 4, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v56.0
### Fixed Issues
Issue ID

The connector now retains quotations that are at the end of a data field when uploading data to Salesforce.

W-12009468
## [](#3-11-0)3.11.0 **October 17, 2022** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v56.0. - The new **Mode** field is added to the **Create Data Set** and **Upload External Data Into New Dataset And Start Processing** operations. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v56.0
## [](#3-10-2)3.10.2 **October 10, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v55.0
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11845802
## [](#3-10-1)3.10.1 **September 28, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v55.0
### Fixed Issues
Issue ID

The Upload External Data operation now works for Date fields when the payload is a type other than Java.

W-11796693
## [](#3-10-0)3.10.0 **June 16, 2022** ### What’s New - Salesforce Einstein Analytics Connector now supports Salesforce API v55.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v55.0
## [](#3-9-2)3.9.2 **April 18, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v54.0
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Bouncy Castle library from org.bouncycastle:bcprov-jdk15on:1.67 to org.bouncycastle:bcprov-jdk15on:1.70.

W-11001896
## [](#3-9-1)3.9.1 **April 1, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v54.0
### Fixed Issues
Issue ID

Upgraded com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.13.2.1.

W-10920477
## [](#3-9-0)3.9.0 **February 24, 2022** ### What’s New - Added support for Salesforce API v54.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v54.0
## [](#3-8-3)3.8.3 **January 7, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v53.0
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the XMLSec library from com.fasterxml.jackson.core:jackson-databind:2.11.3 to com.fasterxml.jackson.core:jackson-databind:2.12.6.

CONN-9849
## [](#3-8-2)3.8.2 **December 10, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v53.0
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the GSON library from com.google.code.gson:gson:2.8.5 to com.google.code.gson:gson:2.8.9.

CONN-9293
## [](#3-8-1)3.8.1 **October 28, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v53.0
### Fixed Issues
Issue ID

When using Mule 4.3.0, the connector did not throw an error when there was a connection issue.

SE-21503
## [](#3-8-0)3.8.0 **October 20, 2021** ### What’s New - Added support for Salesforce API v53.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

External Data API

v53.0
### Fixed Issues
Issue ID

The Create Data Set operation incorrectly mapped exceptions.

SE-22843

Fixed reported security vulnerabilities by upgrading the XMLSec library from org.apache.santuario:xmlsec:2.1.4 to org.apache.santuario:xmlsec:2.2.3.

CONN-8996
## [](#3-7-1)3.7.1 **June 28, 2021** ### [](#compatibility-29)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v52.0
### [](#fixed-issues-16)Fixed Issues - The connector restarted uploading data from an already processed part number after throwing an error. (SE-21466) ## [](#3-7-0)3.7.0 **June 14, 2021** ### [](#compatibility-30)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v52.0
### [](#new-features)New Features - Added support for Salesforce API v52.0. ## [](#3-6-1)3.6.1 **April 19, 2021** ### [](#compatibility-31)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v51.0
### [](#fixed-issues-17)Fixed Issues - While retrying the **Upload External Data** operation, the connector generated a new part number instead of preserving the original one. (SE-20534) - Removed the Velocity dependency `org.apache.velocity:velocity:1.7` to fix a security vulnerability issues. (CONN-7951) ## [](#3-6-0)3.6.0 **February 18, 2021** ### [](#compatibility-32)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v51.0
### [](#new-features-2)New Features Added support for Salesforce API version 51.0. ## [](#3-5-1)3.5.1 **January 7, 2021** ### [](#compatibility-33)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v50.0
### [](#fixed-issues-18)Fixed Issues Upgraded the Bouncy Castle dependency `org.bouncycastle:bcprov-jdk15on:1.65` to `org.bouncycastle:bcprov-jdk15on:1.67` to fix security vulnerability issues. (CONN-7440) ## [](#3-5-0)3.5.0 **November 19, 2020** ### [](#compatibility-34)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v50.0
### [](#new-features-3)New Features A new, optional **Audience URL** field was added to support custom domains for the OAuth JWT connection. ## [](#3-4-0)3.4.0 **October 26, 2020** ### [](#compatibility-35)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v50.0
### [](#new-features-4)New Features This releases adds support for Salesforce API version 50.0. ### [](#fixed-issues-19)Fixed Issues - Upgraded the Jackson Databind dependency `com.fasterxml.jackson.core:jackson-databind:2.10.3` to `com.fasterxml.jackson.core:jackson-databind:2.11.3` to fix vulnerability issues. (CONN-7127) - Upgraded the Apache HttpClient dependency `org.apache.httpcomponents:httpclient:4.5.3` to `org.apache.httpcomponents:httpclient:4.5.13` to fix vulnerability issues. (CONN-7124) ## [](#3-3-0)3.3.0 **July 29, 2020** ### [](#compatibility-36)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v49.0
### [](#new-features-5)New Features This releases adds support for Salesforce API version 49.0. ### [](#fixed-issues-20)Fixed Issues - Upgraded the Commons Codec dependency `commons-codec:commons-codec:1.13` to `commons-codec:commons-codec:1.14` to fix vulnerability issues. (CONN-6437) ## [](#3-2-0)3.2.0 **May 29, 2020** ### [](#compatibility-37)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v48.0
### [](#new-features-6)New Features - Added support for Salesforce API version 48.0 - Added support for Mutual authentication ### [](#fixed-issues-21)Fixed Issues - The display parameter for the OAuth 2.0 connection type is now optional. (CONN-4731) ## [](#3-1-8)3.1.8 **April 15, 2020** ### [](#compatibility-38)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v46.0
### [](#fixed-issues-22)Fixed Issues - Upgraded the following dependencies to fix vulnerability issues (CONN-5800): - Woodstox Core `com.fasterxml.woodstox:woodstox-core:5.0.3` upgraded to `com.fasterxml.woodstox:woodstox-core:6.1.1` - Cryptacular `org.cryptacular:cryptacular:1.1.3` upgraded to `org.cryptacular:cryptacular:1.2.4` - Mule file connector `org.mule.connectors:mule-file-connector:1.2.0` scope changed to test ## [](#3-1-7)3.1.7 **March 2, 2020** ### [](#compatibility-39)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v46.0
### [](#fixed-issues-23)Fixed Issues The issue that caused the Create DataSet operation to throw a `NullPointerException` when the `LinesTerminatedBy` property was not specified in the file format of the JSON describing the dataset is fixed.(SE-14981) ## [](#3-1-6)3.1.6 **January 28, 2020** ### [](#compatibility-40)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v46.0
### [](#fixed-issues-24)Fixed Issues Fixed security vulnerabilities for the following dependencies: - org.codehaus.jackson:jackson-mapper-asl:1.9.13 - com.fasterxml.jackson.core:jackson-databind:2.9.3 - org.bouncycastle:bcprov-jdk15on:1.56 - apache-httpclient:commons-httpclient:3.1 - apache-beanutils:commons-beanutils:1.7.0 - commons-codec:commons-codec:1.10 - ca.juliusdavies:not-yet-commons-ssl:0.3.9 - org.owasp.esapi:esapi:2.0.1 - org.opensaml:xmltooling:1.4.4 - org.opensaml:opensaml:2.6.4 ## [](#3-1-5)3.1.5 **November 27, 2019** ### [](#compatibility-41)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v46.0
### [](#fixed-issues-25)Fixed Issues Added support for the zoned date time when processing CSV files for the Upload External Data operation.(SE-14002) ## [](#3-1-4)3.1.4 **November 6, 2019** ### [](#compatibility-42)Compatibility The Salesforce Analytics Cloud Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v46.0
### [](#features)Features Added support for the local date time when processing CSV files for the Upload External Data operation. ## [](#3-1-3)3.1.3 **August 26, 2019** ### [](#compatibility-43)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

External Data API

v46.0
### [](#features-2)Features Added support for Salesforce Analytics Cloud V46. ## [](#3-1-2)3.1.2 **July 29, 2019** ### [](#compatibility-44)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

Mule Enterprise Edition 4.0.0 and later

External Data API

v43.0
### [](#fixed-issues-26)Fixed Issues Updated Object Store Connector dependency to version 1.1.3. (CONN-2521) ## [](#3-1-1)3.1.1 **June 12, 2019** ### [](#compatibility-45)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

External Data API

v43.0
### [](#fixed-issues-27)Fixed Issues Unable to upload external data - An error occurred when uploading data to Salesforce Analytics if a dataset’s ID was invalid. The fix improves error handling and provides an exception if a dataset ID is invalid. (SE-12115) ## [](#3-1-0)3.1.0 **September 18, 2018** ### [](#compatibility-46)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

External Data API

v43.0
### [](#features-3)Features Added support for Salesforce Analytics Cloud V43. ## [](#3-0-1)3.0.1 **March 15, 2018** ### [](#compatibility-47)Compatibility Salesforce Einstein Analytics Cloud Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

External Data API

v36.0
### [](#fixed-issues-28)Fixed Issues Changed connector icon. ## [](#3-0-0)3.0.0 **January 15, 2018** ### [](#compatibility-48)Compatibility Salesforce Einstein Analytics Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

External Data API

v36.0
### [](#features-4)Features - Added the Delete Data Set operation to delete datasets that are not needed anymore. - Changed the DataSense mechanism of the connector to provide dynamic metadata for the Upload External Data, Start Data Processing, and Delete Data Set operations. Now you can select the dataset ID for which one of the mentioned operations executes. For the Upload External Data operation, the connector also provides dynamic input metadata that describes the format of the data to be uploaded to the selected dataset. - Create Data Set, Upload External Data Into New Data Set, and Start Processing operations now allow the user to select a file that serves as a schema description of the dataset to be created. These operations do not have DataSense support, as the file describing the dataset schema can’t be read at design time. ## [](#see-also)See Also - [Salesforce External Data API](https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_ext_data.meta/bi_dev_guide_ext_data/) - [Add the Data](https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_ext_data.meta/bi_dev_guide_ext_data/bi_ext_data_add_data.htm) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Marketing Cloud Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce Marketing Cloud (Salesforce Marketing Cloud Connector) enables you to connect to the Salesforce Marketing Cloud web services using the Salesforce Exact Target API. This connector exposes convenient methods for managing objects and calling services provided by the Salesforce Exact Target API, also known as Salesforce Marketing Cloud. Guide: [Salesforce Marketing Cloud Connector User Guide](https://docs.mulesoft.com/salesforce-marketing-cloud-connector/latest/) ## [](#5-0-5)5.0.5 **October 15, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The gson library is upgraded to version 2.14.0.

  • The Apache CXF libraries (cxf-core, cxf-rt-wsdl, cxf-rt-ws-rm, cxf-rt-ws-security, cxf-rt-frontend-simple, cxf-rt-frontend-jaxws, and cxf-rt-transports-http) are upgraded to version 4.1.9.

  • The kotlin-stdlib library is upgraded to version 2.4.21.

W-24406484
## [](#5-0-4)5.0.4 **September 26, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These library are upgraded to address reported security vulnerabilities:

  • The Apache CXF libraries (cxf-core, cxf-rt-frontend-jaxws, cxf-rt-transports-http, cxf-rt-management, cxf-rt-ws-security, cxf-rt-ws-rm, cxf-rt-security-saml, and cxf-rt-security) are upgraded to version 4.1.8.

  • The neethi library is upgraded to version 3.2.4.

  • The jackson-databind, jackson-core, jackson-dataformat-xml, jackson-datatype-jsr310, and jackson-module-jakarta-xmlbind-annotations libraries are upgraded to version 2.22.3.

  • The woodstox-core library is upgraded to version 7.2.2.

  • The commons-codec library is upgraded to version 1.22.1.

  • The guava library is upgraded to version 33.7.1-jre.

  • The bcprov-jdk18on, bcpkix-jdk18on, and bcutil-jdk18on libraries are upgraded to version 1.86.

  • The jetty-http, jetty-security, jetty-server, and jetty-util libraries are upgraded to version 12.0.39.

  • The spring-core, spring-beans, spring-context, and spring-expression libraries are upgraded to version 6.2.19.

  • The httpclient5 library is upgraded to version 5.6.4.

  • The httpcore5 and httpcore5-h2 libraries are upgraded to version 5.4.3.

  • The commons-collections 3.2.2 transitive dependency is removed from commons-beanutils.

W-24262985, W-24137088, W-3300013
## [](#5-0-3)5.0.3 **August 26, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The cxf-core, cxf-rt-frontend-jaxws, cxf-rt-transports-http, and cxf-rt-management libraries are upgraded to version 4.2.3 to address reported security vulnerabilities.

W-23441630
## [](#5-0-2)5.0.2 **August 20, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

SSL handshake errors no longer occur when you deploy the connector in an air-gapped or network-restricted environment.

W-23409290
## [](#5-0-1)5.0.1 **July 22, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The cxf library is upgraded to version 4.2.2.

  • The jackson library is upgraded to version 2.22.1.

  • The woodstox-core library is upgraded to version 7.2.1.

  • The kotlin-stdlib library is upgraded to version 2.4.0.

  • The jakarta.xml.bind-api library is upgraded to version 4.0.5.

  • The jaxb-runtime library is upgraded to version 4.0.9.

  • The jakarta.xml.ws-api library is upgraded to version 4.0.3.

  • The jakarta.activation-api library is upgraded to version 2.1.4.

W-23452701
## [](#5-0-0)5.0.0 **May 30, 2026** ### What’s New - This connector is now compatible with Java 17 only. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The springframework library is upgraded to version 6.2.18.

  • The jackson-databind and jackson-dataformat-xml libraries are upgraded to version 2.21.3.

  • The cxf-core library is upgraded to 4.2.0.

  • The woodstox-core library is upgraded to version 7.2.0.

  • The stax2-api library is upgraded to version 4.3.0.

  • The cryptacular library is upgraded to version 1.3.0.

  • The dom4j library is upgraded to version 2.2.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons.lang3 library is upgraded to version 3.20.0.

  • The commons-codec library is upgraded to version 1.22.0.

  • The commons-beanutils library is upgraded to version 1.11.0.

  • The commons-text library is upgraded to version 1.14.0.

  • The kotlin-stdlib library is upgraded to version 2.1.21.

  • The xmlsec library is upgraded to version 4.0.4.

  • The guava library is upgraded to version 33.6.0-jre.

  • The jakarta.xml.bind-api library is upgraded to version 4.0.2.

  • The jaxb-runtime library is upgraded to version 4.0.5.

  • The jakarta.xml.ws-api library is upgraded to version 4.0.2.

  • The jakarta.jws-api library is upgraded to version 3.0.0.

  • The jakarta.xml.soap-api library is upgraded to version 3.0.2.

  • The jakarta.activation-api library is upgraded to version 2.1.3.

  • The jackson-module-jaxb-annotations library is replaced by the jackson-module-jakarta-xmlbind-annotations library.

W-21709983, W-20579615

The FuelSDK dependency is removed. Core connector operations are now migrated to localized, compile-time generated classes to eliminate external classpath and transitive library conflicts in your Mule applications.

W-20826329
## [](#4-1-7)4.1.7 **January 31, 2026** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly throws the SFDC-MARKETING-CLOUD:INVALID_INPUT error instead of MULE:UNKNOWN by resolving a reflection issue when running on Java 17.

W-20729302

The connector now correctly deploys the Mule application even if the configured authentication URL is invalid or unreachable during application startup.

W-19601304
## [](#4-1-6)4.1.6 **June 29, 2025** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The spring-context and spring-beans libraries are upgraded to version 5.3.39 to address reported security vulnerabilities.

W-18881961
## [](#4-1-5)4.1.5 **June 26, 2025** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The cxf-core library is upgraded to version 3.5.10 to address reported security vulnerabilities.

W-18142881
## [](#4-1-4)4.1.4 **February 24, 2025** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.springframework dependencies are upgraded to version 5.3.5 to address reported security vulnerabilities.

W-17517223

The payload remains case-sensitive after upgrading the fasterxml library versions.

W-17506325
## [](#4-1-3)4.1.3 **October 28, 2024** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer incorrectly throws an error if you define a local WSDL file.

W-16862135
## [](#4-1-2)4.1.2 **September 19, 2024** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.apache.cxf libraries are upgraded to version 3.5.9 to address reported security vulnerabilities.

W-16783690
## [](#4-1-1)4.1.1 **July 24, 2024** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The proxy configuration is now also used when downloading the WSDL file.

W-16063541
## [](#4-1-0)4.1.0 **April 24, 2024** ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Bouncy Castle library (bcprov-jdk15on) is removed to address security vulnerabilities.

W-15310626
## [](#4-0-0)4.0.0 **February 20, 2024** ### What’s New - The connector now supports multiple child organizations by specifying the **Account Id** field. - The `SFDC-MARKETING-CLOUD:THROTTLED` error is removed. ### Compatibility
Application/Service Version

Mule

4.5.0 and later

OpenJDK

8, 11, and 17
## [](#3-2-13)3.2.13 **January 12, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#3-2-12)3.2.12 **February 15, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector no longer makes an extra API request for the Retrieve entities operation.

W-12487851
## [](#3-2-11)3.2.11 **January 23, 2023** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue Resolution ID

The connector no longer throws an error when filtering null values.

W-12404291

The Apache CXF Core dependency is upgraded to version 3.5.5 to fix reported security vulnerabilities.

W-12390525

The Commons-IO dependency is upgraded to version 2.11.0 to fix reported security vulnerabilities.

W-12390525
## [](#3-2-10)3.2.10 **December 14, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

The overall stability and performance of the connector are improved.

W-11991934
## [](#3-2-9)3.2.9 **November 9, 2022** ### What’s New - The com.fasterxml.jackson.core library is upgraded to version 2.14.0. - The com.fasterxml.woodstox:woodstox-core library is upgraded to version 6.4.0. ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0 to address reported security vulnerabilities.

W-12029613

The com.fasterxml.woodstox:woodstox-core library is upgraded to version 6.4.0 to address reported security vulnerabilities.

W-12029613
## [](#3-2-8)3.2.8 **September 28, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

The connector now properly handles null properties.

W-11807779
## [](#3-2-7)3.2.7 **June 20, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

The connector no longer contains a policy violation in the sizeof-agent transitive dependency.

W-11282445
## [](#3-2-6)3.2.6 **June 9, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Spring Beans library from org.springframework:spring-beans:5.3.18 to org.springframework:spring-beans:5.3.20.

W-11226200

Fixed reported security vulnerabilities by upgrading the CXF RT Transports HTTP library from cxf-rt-transports-http:jar:3.3.5 to cxf-rt-transports-http:jar:3.5.2.

W-11220137
## [](#3-2-5)3.2.5 **April 20, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Mule SOAP Engine library from org.mule.connectors:mule-soap-engine:1.3.2 to org.mule.connectors:mule-soap-engine:1.6.9.

W-10920502, W-10927724

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920505

Fixed reported security vulnerabilities by upgrading the Spring Framework library from org.springframework:spring-context:5.1.6.RELEASE to org.springframework:spring-context:5.3.19.

W-11001897

Fixed reported security vulnerabilities by upgrading the Bouncy Castle library from org.bouncycastle:bcprov-jdk15on:1.67 to org.bouncycastle:bcprov-jdk15on:1.70.

W-11001900
## [](#3-2-4)3.2.4 **January 7, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the XMLSec library from com.fasterxml.jackson.core:jackson-databind:2.11.3 to com.fasterxml.jackson.core:jackson-databind:2.12.6.

CONN-9832
## [](#3-2-3)3.2.3 **December 7, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by removing the transitive dependency for the com.google.code.gson:gson:2.8.5 library.

CONN-9296
## [](#3-2-2)3.2.2 **October 21, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the XMLSec library from org.apache.santuario:xmlsec:2.1.4 to org.apache.santuario:xmlsec:2.2.3.

CONN-8996
## [](#3-2-1)3.2.1 **June 10, 2021** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-26)Fixed Issues - Expired token did not refresh properly for the **On new object** and **On modified object** sources. (SE-20989) - Fixed a vulnerability issue by upgrading the Bouncycastle dependency `org.bouncycastle:bcprov-jdk15on:1.65` to `org.bouncycastle:bcprov-jdk15on:1.67`. (CONN-8332) ## [](#3-2-0)3.2.0 **June 2, 2021** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#new-features)New Features - The **Since** parameter for sources supports date values included in a time zone. - The sources return values for all of the object fields. ### [](#fixed-issues-27)Fixed Issues - The **On Modified Objects** source did not support all of the objects listed in the dropdown. The source uses the **Modified Date** field, which is not retrievable for all objects. The dropdown is now filtered to display only objects that retrieve the **Modified Date** field. (SE-20516) - There was a connection error while deploying the connector in a closed environment without internet access. To fix this, the connector resources now include an ``etframework.wsdl`and `ETFrameworkFault.xsd``. (SE-19993) ## [](#3-1-6)3.1.6 **March 24, 2021** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-28)Fixed Issues - The connector threw `INVALID_INPUT` errors after the app restarted in Anypoint Runtime Manager. (SE-19926) - The connector did not reconnect after it encountered a network disruption. (SE-20010) ## [](#3-1-5)3.1.5 **November 17, 2020** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-29)Fixed Issues - The **Retrieve** operation did not throw an exception when the query didn’t execute succcessfully. (SE-18218) - Fixed a vulnerability issue by upgrading the Jackson Databind dependency `com.fasterxml.jackson.core:jackson-databind:2.10.3` to `com.fasterxml.jackson.core:jackson-databind:2.11.3`. ## [](#3-1-4)3.1.4 **October 6, 2020** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-30)Fixed Issues - Misleading errors appeared in DEBUG mode. (SE-17810) ## [](#3-1-3)3.1.3 **September 9, 2020** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-31)Fixed Issues - Fixed a vulnerability issue by upgrading the Commons-IO dependency `commons-io:commons-io:2.4` to `commons-io:commons-io:2.7` ## [](#3-1-2)3.1.2 **August 10, 2020** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-32)Fixed Issues - Encountered an ArrayIndexOutOfBoundsException when executing the Update operation. (SE-16999) - Fixed a vulnerability issue by upgrading the Apache CXF dependency `org.apache.cxf:cxf-rt-transports-http:3.3.0` to `org.apache.cxf:cxf-rt-transports-http:3.3.5` ## [](#3-1-1)3.1.1 **July 23, 2020** Salesforce Marketing Cloud Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-33)Fixed Issues - Fixed the NewObject and ModifyObject input sources to correctly parse date values that have the format `yyyy-MM-dd’T’HH:mm:ss`. (CONN-1620) - Fixed the following vulnerability issues: - Updated the Commons Codec dependency `commons-codec:commons-codec:1.13` to `commons-codec:commons-codec:1.14` - Excluded the Bouncy Castle dependency `org.bouncycastle:bcprov-jdk15on` from `org.mule.connectors:mule-soap-engine:1.3.2` and `org.cryptacular:cryptacular:1.2.4` - Excluded the Bouncy Castle dependency `org.bouncycastle:bcprov-jdk15on` from `org.cryptacular:cryptacular:1.2.4` ## [](#3-1-0)3.1.0 **June 16, 2020** ### [](#compatibility-28)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-34)Fixed Issues The connector did not support parameter expressions for the Service URL parameter. (SE-16129) ## [](#3-0-4)3.0.4 **May 29, 2020** ### [](#compatibility-29)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-35)Fixed Issues The Upsert operation sent an API request with the wrong SOAP action. The operation now uses the SOAP Update action. (SE-16073) ## [](#3-0-3)3.0.3 **May 7, 2020** ### [](#compatibility-30)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-36)Fixed Issues - The OAuth access token was not refreshed correctly when it expired. (SE-15630) - Upgraded the following dependency versions to fix vulnerability issues: - Jackson Databind `com.fasterxml.jackson.core:jackson-databind:2.9.3` upgraded to `com.fasterxml.jackson.core:jackson-databind:2.10.0` - Cryptacular `org.cryptacular:cryptacular:1.1.1` upgraded to `org.cryptacular:cryptacular:1.2.4` - Apache CXF Core `org.apache.cxf:cxf-core:3.3.0` upgraded to `org.apache.cxf:cxf-core:3.3.6` - Apache CXF RT Management `org.apache.cxf:cxf-rt-management:3.3.1` upgraded to `org.apache.cxf:cxf-rt-management:3.3.6` - Woodstox Core `com.fasterxml.woodstox:woodstox-core:5.0.3` upgraded to `com.fasterxml.woodstox:woodstox-core:6.1.1` - Commons Bean Utils `commons-beanutils:commons-beanutils:1.9.2` upgraded to `commons-beanutils:commons-beanutils:1.9.4` - Dom4j `org.dom4j:dom4j:2.1.1` upgraded to `org.dom4j:dom4j:2.1.3` - Commons Codec `commons-codec:commons-codec:1.11` upgraded to `commons-codec:commons-codec:1.13` - XMLSec `org.apache.santuario:xmlsec:2.1.2` upgraded to `org.apache.santuario:xmlsec:2.1.5` ## [](#3-0-2)3.0.2 **April 2, 2020** ### [](#compatibility-31)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-37)Fixed Issues - The OAuth Connection Provider did not refresh the access token when it expired. (SE-13371) - The connector could not retrieve the DataExtensionObject if the column name contained spaces in the Where clause or in the selected fields. (CONN-4183) ## [](#3-0-1)3.0.1 **December 18, 2019** ### [](#compatibility-32)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#fixed-issues-38)Fixed Issues - When using the `upsert` operation, the connector sent an incorrect request to the API. It changed the request from UpdateRequest to CreateRequest. (SE-14064) ## [](#3-0-0)3.0.0 **October 31, 2019** ### [](#compatibility-33)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.2.1 and later
### [](#features)Features - Added the OAuth client credentials connection provider to enable the use of the OAuth mechanism for authentication. - Removed FuelSDK and used Mule HTTP client to perform the SOAP requests to the API. ## [](#2-2-0)2.2.0 **October 1, 2019** ### [](#compatibility-34)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Fuel SDK

v1.2.2
### [](#fixed-issues-39)Fixed Issues - Fixed a bug where sensitive information was displayed in logs by making logging optional. You can enable logging by using the new `Enable Soap Logging` parameter in the connector configuration. (SE-13059) ## [](#2-1-5)2.1.5 **August 8, 2019** ### [](#compatibility-35)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Fuel SDK

v1.2.2
### [](#features-2)Features - Upgraded the File Connector dependency to version 1.3.0. (CONN-2523) ### [](#fixed-issues-40)Fixed Issues - The Salesforce Marketing Cloud Connector was throwing the UNKNOWN error on an invalid query. The error handling has been improved and now, when a query is invalid, the correct exception is thrown. (SE-12523) ## [](#2-1-4)2.1.4 **May 29, 2019** ### [](#compatibility-36)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Fuel SDK

v1.2.2
### [](#fixed-issues-41)Fixed Issues - Salesforce Marketing Cloud Connector did not parse queries correctly. The connector now translates an SOQL query correctly when including a clause in parentheses. (SE-11721) ## [](#2-1-3)2.1.3 **May 6, 2019** ### [](#compatibility-37)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Fuel SDK

v1.2.2
### [](#fixed-issues-42)Fixed Issues - SFMC (Salesforce Marketing Connector) no longer erroneously appends a timestamp to the value in a SQL statement(SE-11603). - Now works with Mule 4.2.0 and Java 11. Added the following missing dependencies: com.sun.xml.messaging.saaj:saaj-impl:1.5.1, javax.ws.rs:javax.ws.rs-api:2.1.1 and javax.xml.ws:jaxws-api:2.3.1 ## [](#2-1-2)2.1.2 **March 11, 2019** ### [](#compatibility-38)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Fuel SDK

v1.2.2
### [](#fixed-issues-43)Fixed Issues - Cannot connect to Salesforce Marketing: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog. This issue was fixed by wrapping the thrown exception with a more readable one, SFDC-MARKETING-CLOUD:UNKNOWN. ## [](#2-1-1)2.1.1 **February 7, 2019** ### [](#compatibility-39)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Fuel SDK

1.2.2
### [](#fixed-issues-44)Fixed Issues - Fixed error in parser date. ## [](#2-1-0)2.1.0 **November 20, 2018** The Salesforce Marketing Cloud connector is compatible with: ### [](#compatibility-40)Compatibility
Application/Service Version

Mule

4.1 and later

Fuel SDK

1.2.2
### [](#features-3)Features - Support for Salesforce Marketing Cloud API v43 based on Fuel SDK v1.2.2. ## [](#2-0-0)2.0.0 **January 19, 2018** Release notes for the Salesforce Marketing Cloud connector. ### [](#compatibility-41)Compatibility The Salesforce Marketing Cloud connector is compatible with:
Application/Service Version

Mule

4.0 and later

Exact Target API

v145.3
### [](#features-4)Features - Configure Create - Calls the "Configure" command with "Create" as the action attribute when connected to the Marketing Cloud SOAP web service. - Configure Delete - Calls the "Configure" command with "Delete" as the action attribute when connected to the Marketing Cloud API SOAP web service. - Configure Update - Calls the "Configure" command with "Update" as the action attribute when connected to the Marketing Cloud API SOAP web service. - Create - Creates a new object on the Marketing Cloud API web server. - Delete - Deletes an existing object on the Marketing Cloud API web server. - Perform get max count - Calls the "Perform" command with "GetMaxCount" as the action attribute when connected to the Marketing Cloud API SOAP web service. - Perform start - Sends a "Perform" command having "Start" as an action attribute when connected to the Marketing Cloud API SOAP web service. - Perform stop - Sends a "Perform" command having "Stop" as an action attribute when connected to the Marketing Cloud API SOAP Web service. - Retrieve - Retrieves objects from the Marketing Cloud API web server in a SQL query-like fashion. - Schedule start - Calls the "Schedule" command with "Start" as the action attribute when connected to the Marketing Cloud API SOAP web service. - Update - Updates an existing object on the Marketing Cloud API web server. - Upsert - Creates an object if the object does not already exist, or delete an existing object on the Marketing Cloud API web server. This operation is achieved by using "Create" method of the Marketing Cloud API SOAP API. ### [](#fixed-issues-45)Fixed Issues This is the first version of the connector, thus no fixes were required; there are only new features. ### [](#known-issues)Known Issues #### [](#providing-a-subclass-as-type-to-a-complex-field)Providing a Subclass as Type To a Complex Field Some objects have complex fields that represent a base class from Salesforce Marketing. So, if instead of the base class, you want to pass a subclass of it as value to that field, that is not possible because the connector is not recognize the fields that do not belong to the base class. You must manually map those fields in Transform Message and add a field named "concreteClassType" with the name of the subclass as value. For more information and an example, read the connector guide. #### [](#retrieving-fields-from-a-hierarchy-not-possible)Retrieving Fields From a Hierarchy Not Possible Querying fields that are lower than level 1 in the hierarchy is not supported by the API. For example,queries like `Select Attributes.Name from Subscriber` because Name is at level 2 in the hierarchy. #### [](#server-results-that-contain-an-automation-object-structure-cause-exception-to-be-thrown)Server Results that Contain an Automation Object Structure Cause Exception to Be Thrown When performing operations on an Automation object, the result of the operation causes an exception to be thrown because the response has a field that cannot be parsed by the API. To bypass this, make those types of operations asynchronous. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Marketing Cloud REST Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce Marketing Cloud REST (Salesforce Marketing Cloud REST Connector) enables you to integrate with the Salesforce Marketing Cloud marketing platform. This connector exposes operations provided by the Salesforce Marketing Cloud REST API. Guide: [Salesforce Marketing Cloud REST Connector User Guide](https://docs.mulesoft.com/jp/salesforce-marketing-cloud-rest-connector/latest/) ## [](#1-2-3)1.2.3 **September 25, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-2-2)1.2.2 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The gson library is upgraded to version 2.14.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The log4j-api, log4j-core, log4j-slf4j-impl, and log4j-1.2-api libraries are upgraded to version 2.25.5.

W-23441732
## [](#1-2-1)1.2.1 **March 26, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.21.0.

  • The gson library is upgraded to version 2.13.2.

W-21334596
## [](#1-2-0)1.2.0 **April 18, 2024** ### What’s New - This connector is now compatible with Java 17. - This connector is now FIPS 140-2 compliant. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-1)1.1.1 **February 13, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12128867
## [](#1-1-0)1.1.0 **October 18, 2022** ### What’s New - Added the following new operations to work with event definitions: - **Create Event Definition** - **Delete Event Definition** - **Get Event Definition** - **Trigger Event** - **Update Event Definition** - Added these other new operations: - **Send Email Message to Multiple Recipients** - **Send SMS Message to Multiple Recipients** - **Send Email Using Triggered Send Definition** For information about these new operations, see the [Salesforce Marketing Cloud REST Connector Reference](https://docs.mulesoft.com/jp/salesforce-marketing-cloud-rest-connector/latest/salesforce-marketing-cloud-rest-connector-reference). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#1-0-3)1.0.3 **October 3, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The OAuth connection token now properly refreshes when it expires.

W-11835048
## [](#1-0-2)1.0.2 **July 26, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11354813
## [](#1-0-1)1.0.1 **July 14, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The connector now contains improved error message descriptions for some operations.

W-11291817
## [](#1-0-0)1.0.0 **February 15, 2022** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Salesforce Marketing Cloud REST Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Salesforce Pub/Sub Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Salesforce Pub/Sub (Salesforce Pub/Sub Connector) enables you to connect to the Pub/Sub API, which provides a single interface for publishing and subscribing to platform events, including real-time event monitoring events and change data capture events. Guide: [Salesforce Pub/Sub Connector User Guide](https://docs.mulesoft.com/salesforce-pubsub-connector/latest/) ## [](#1-4-2)1.4.2 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

The Subscribe Channel Listener source no longer enters an infinite reconnection loop after a transient gRPC internal error. The previous behavior required you to restart the application to resume event processing.

W-23423143

These libraries are upgraded to address reported security vulnerabilities:

  • The grpc-java library is upgraded to version 1.84.0.

  • The guava library is upgraded to version 33.7.1-jre.

  • The protobuf-java library is upgraded to version 4.36.0.

  • The jackson library is upgraded to version 2.22.2.

W-3300013
## [](#1-4-1)1.4.1 **August 6, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The okio library is upgraded to version 3.18.1 to address CVE-2026-53914.

  • The commons-compress library is upgraded to version 1.28.0.

  • The jackson-core library is upgraded to version 2.18.8.

  • The bcpkix-jdk18on library is upgraded to version 1.85.

  • The xmlsec library is upgraded to version 2.3.5.

  • The cryptacular library is upgraded to version 1.3.0.

W-23614326, W-3300013
## [](#1-4-0)1.4.0 **July 2, 2026** ### What’s New - Salesforce Pub/Sub Connector now supports Salesforce API v67.0. - Salesforce Pub/Sub Connector now supports the **OAuth Client Credentials** connection type. For more information, see [OAuth Client Credentials Connection Type](https://docs.mulesoft.com/salesforce-pubsub-connector/latest/salesforce-pubsub-connector-reference#PubsubConfig_OauthClientCredentials). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0, v67.0
## [](#1-3-1)1.3.1 **May 31, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0
### Fixed Issues
Issue Resolution ID

The connector applications no longer hang indefinitely without throwing an error when the Salesforce streaming server stalls. The Connection Timeout default value is changed from 0 to 30 seconds, and the Login Request Timeout default value is changed from 0 to 60 seconds. To preserve the legacy behavior, you can explicitly configure either parameter to 0.

W-18723883
## [](#1-3-0)1.3.0 **April 26, 2026** ### What’s New - Salesforce Pub/Sub Connector now supports Salesforce API v66.0. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0, v66.0
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The avro library is upgraded to version 1.11.5.

  • The jackson-core library is upgraded to version 2.18.6.

  • The jackson-databind library is upgraded to version 2.18.6.

  • The protobuf-java library is upgraded to version 4.33.6.

  • The mule-connector-commons library is upgraded to version 2.1.2.

W-21927631, W-20579633
## [](#1-2-0)1.2.0 **February 6, 2026** ### What’s New - Salesforce Pub/Sub Connector now supports Salesforce API v65.0. - The connector no longer supports the `Basic Authentication` connection type for Salesforce API v65.0. Support is limited to Salesforce API v64.0 and below. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0, v62.0, v63.0, v64.0, v65.0
### Fixed Issues
Issue Resolution ID

The grpc library is upgraded to version 1.76.0 to address reported security vulnerabilities.

W-20139044

The connector now supports graceful shutdown of gRPC connections, allowing active requests to complete before the service terminates to prevent data loss or connection errors during restarts.

W-20139044

The connector now correctly throws the ConnectionException error to Mule runtime if JWT token generation fails. Previously, the connector logged the error but incorrectly reported a successful reconnection, which prevented the reconnection strategy from triggering and stopped event processing.

W-20727817

The connector now includes the Inactivity Watchdog Scheduler to address issues where the subscriber intermittently stops receiving platform events without logging errors. Use the new Inactivity Watchdog Scheduler Frequency and Inactivity Watchdog Scheduler Time Unit fields to enable this scheduler.

W-20347755
## [](#1-1-0)1.1.0 **October 8, 2025** ### What’s New - You can now configure how long the connector waits for a publish request to complete before timing out. Use the new **Publish Request Timeout** and **Publish Request Time Unit** parameters to control this behavior. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0
### Fixed Issues
Issue Resolution ID

The connector now auto-generates x-client-trace-id during the publish API call, and you can view this ID in the logs.

W-19643054

The connector now correctly obtains a new session when receiving the Invalid Session ID found in SessionHeader: Illegal Session. Session not found exception.

W-18048086
## [](#1-0-18)1.0.18 **August 14, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0
### Fixed Issues
Issue Resolution ID

Session IDs are now logged at the DEBUG or TRACE level instead of the INFO level by default.

W-19251792
## [](#1-0-17)1.0.17 **May 27, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core:jackson-core dependency is upgraded to version 2.18.3 to address reported security vulnerabilities.

W-18355862

The io.grpc dependency is upgraded to version 1.66.0 to address reported security vulnerabilities.

W-18355862

The org.apache.santuario:xmlsec dependency is upgraded to version 2.2.6 to address reported security vulnerabilities.

W-18355862

The com.fasterxml.jackson.core:jackson-databind dependency is upgraded to version 2.18.3 to address reported security vulnerabilities.

W-18355862

The org.apache.commons:commons-compress dependency is upgraded to version 1.27.1 to address reported security vulnerabilities.

W-18355862

The com.google.guava:guava dependency is upgraded to version 33.4.8-jre to address reported security vulnerabilities.

W-18355862
## [](#1-0-16)1.0.16 **March 7, 2025** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0
### Fixed Issues
Issue Resolution ID

The Avro dependency is upgraded to version 1.11.4 to address a reported security vulnerability.

W-17819091
## [](#1-0-15)1.0.15 **August 19, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0
### Fixed Issues
Issue Resolution ID

The EventDTO class, which is the response for the Subscribe channel listener source, is moved from the internal package to the api package for easier access.

W-16393438
## [](#1-0-14)1.0.14 **July 23, 2024** ### What’s New - Salesforce Pub/Sub Connector now supports Salesforce API v61.0. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0, v55.0, v56.0, v57.0, v58.0, v59.0, v60.0, v61.0
## [](#1-0-13)1.0.13 **May 13, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Salesforce, Salesforce Government Cloud

v54.0
## [](#1-0-12)1.0.12 **April 18, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now properly supports SSL/TLS when setting up the truststore configuration in the connection configuration.

W-15395279
## [](#1-0-11)1.0.11 **March 21, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Bouncy Castle library (bcprov-jdk15on) is removed to address reported security vulnerabilities.

W-15301880
## [](#1-0-10)1.0.10 **February 20, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now contains a fixed read timeout period if the connection is validated after the static IP feature is applied in CloudHub 1.0.

W-15028700
## [](#1-0-9)1.0.9 **December 7, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The output metadata for the Subscribe Channel Listener source now uses lowercase fields that match the payload.

W-14608371
## [](#1-0-8)1.0.8 **September 18, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

When the saved replay ID is encoded as a byte array in Object Store, the connector now correctly decodes the replay ID.

W-14108089
## [](#1-0-7)1.0.7 **July 26, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

When there are connectivity issues with the connector, the replay ID is now correctly treated as valid, rather than the connector defaulting to the EARLIEST replay option.

W-13704839

When the connector is subscribed to multiple channels using the same configuration for all listeners, the listeners no longer fail to reconnect when the daily limit is reached.

W-13716068
## [](#1-0-6)1.0.6 **July 10, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now properly reads the replay ID from the Object Store when using the Replay id from object store replay option in Subscribe Channel Listener.

W-13732644
## [](#1-0-5)1.0.5 **March 22, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The proxy configuration now works properly when connecting to the gRPC API.

W-12650923

The connector now handles numeric values properly when publishing events.

W-12704176
## [](#1-0-4)1.0.4 **October 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The connector now returns the EventId and CorrelationKey fields for all the events.

W-11743090

The connector no longer has metadata issues for CDC events.

W-11797082
## [](#1-0-3)1.0.3 **August 31, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The connector got stuck when specifying a value over 100 for the Batch events size field. Now, when specifying a value over 100, the connector prints a log message that the Batch events size field accepts a maximum value of 100, as per the Salesforce Pub/Sub API.

W-11637670
## [](#1-0-2)1.0.2 **August 10, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Consuming events no longer fails with an InvalidArgument error when using Replay id from object store as the Replay Option.

W-11554123
## [](#1-0-1)1.0.1 **July 28, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Consuming events no longer fails with a NumberFormat Exception when using Earliest as the Replay Option.

W-11450684

Consuming events no longer fails with an InvalidArgument error when using Custom replay id as the Replay Option and providing a number in the replay ID or when using Replay id from object store as the Replay Option.

W-11450737
## [](#1-0-0)1.0.0 **June 30, 2022** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Salesforce Pub/Sub Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SAP Concur Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for SAP Concur is a SaaS provider of integrated travel and expense management solutions. SAP Concur Connector operates as a bidirectional gateway between instances of SAP Concur and Mule. The connector is available for deployment on-premises and in the cloud. Guide: [SAP Concur Connector User Guide](https://docs.mulesoft.com/jp/sap-concur-connector/latest/) ## [](#4-2-4)4.2.4 **September 30, 2026** ### What’s New - Some operations are marked as deprecated. For more information, see [SAP Concur Connector 4.2 リファレンス](https://docs.mulesoft.com/jp/sap-concur-connector/latest/sap-concur-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-text library is upgraded to version 1.14.0.

W-24134477
## [](#4-2-3)4.2.3 **January 18, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#4-2-2)4.2.2 **December 4, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The invoice/vendors endpoint now uses SAP Concur Vendor API 3.1 instead of 3.0.

W-14588588
## [](#4-2-1)4.2.1 **November 7, 2022** ### What’s New - The org.apache.commons library is upgraded to version 1.10.0. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The org.apache.commons library is upgraded to version 1.10.0 to address reported security vulnerabilities.

W-11913982
## [](#4-2-0)4.2.0 **November 11, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Delete List Item operation failed with a Content-Type header is missing error message. Now, the Delete List Item operation supports the Content Type parameter.

SE-23125
## [](#4-1-0)4.1.0 **August 6, 2021** ### [](#compatibility-6)Compatibility
Application/Service Version

Mule

4.0.0 and later

OpenJDK

8 and 11
### [](#new-features)New Features - Added proxy support for the connector. ## [](#4-0-3)4.0.3 **June 11, 2021** ### [](#compatibility-7)Compatibility
Application/Service Version

Mule

4.0.0 and later

OpenJDK

8 and 11
### [](#fixed-issues-5)Fixed Issues - Fixed the name of the connector in Anypoint Studio. (CONN-8245) ## [](#4-0-2)4.0.2 **September 7, 2020** ### [](#compatibility-8)Compatibility
Application/Service Version

Mule

4.0.0 and later

OpenJDK

8 and 11
### [](#fixed-issues-6)Fixed Issues Fixed a security vulnerability. (CONN-6897) ## [](#4-0-1)4.0.1 **October 8, 2019** ### [](#compatibility-9)Compatibility
Application/Service Version

Mule

4.0.0 and later
### [](#features)Features - Updated connector icons. ## [](#4-0-0)4.0.0 **February 28, 2018** Concur connector is available on Mule 4.0.
Application/Service Version

Mule

4.0.0 and later

Anypoint

7 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SAP Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for SAP (SAP Connector) enables Mule runtime engine (Mule) support for SAP integration and leverages the SAP Java Connector (JCo) libraries. Guide: [SAP Connector User Guide](https://docs.mulesoft.com/jp/sap-connector/latest/) ## [](#5-9-14)5.9.14 **September 25, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

  • The sapjco3 JAR and its native libraries must be compatible with the operating system and JVM architecture (for example, 64-bit) where the Mule app is deployed.

  • In SAP JCo 3.1.12 and later, you can’t rename sapjco3.jar. You might need to configure the Maven Shade Plugin.

Supported SAP IDoc libraries

3.0.10 and later, 3.1.x

  • If you use SAP JCo 3.1.x, sapidoc3.jar must be a 3.1.x build from 2019 or later to avoid missing classes.

  • In SAP IDoc 3.1.12 and later, you can’t rename sapidoc3.jar. You might need to configure the Maven Shade Plugin.

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

JCO_ERROR_CONFIGURATION: Invalid X.509 certificate encountered errors no longer occur when you use a Certificate connection with a valid X.509 certificate file.

W-19312900
## [](#5-9-13)5.9.13 **August 13, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.10 and later, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

Previously, the connector checked the RETURN tag only in the export parameter part of the SAP BAPI response. Now, the connector checks the RETURN tag in the export parameter, changing parameter, import parameter, and table parameter of the SAP BAPI response.

W-19013864
## [](#5-9-12)5.9.12 **December 12, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.10 and later, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The com.nimbusds:nimbus-jose-jwt library is upgraded to version 9.40 to address reported security vulnerabilities.

W-16202238
## [](#5-9-11)5.9.11 **October 8, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The connector now logs extended properties only in debug mode.

W-16896861
## [](#5-9-10)5.9.10 **August 12, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The com.nimbusds:nimbus-jose-jwt library is upgraded to version 9.40 to address reported security vulnerabilities.

W-16202238
## [](#5-9-9)5.9.9 **July 30, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

This release includes only non-user-impacting changes.

W-16150318
## [](#5-9-8)5.9.8 **July 2, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

SAP Connector no longer generates excessive debug logs, which resolves potential log file size issues in CloudHub environments.

W-16089322
## [](#5-9-7)5.9.7 **June 7, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

This release includes only non-user-impacting changes.

W-15938277
## [](#5-9-6)5.9.6 **June 5, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The connector now logs extended properties only in debug mode.

W-15938277
## [](#5-9-5)5.9.5 **February 28, 2024** ### What’s New - You can now run the connector in a CloudHub 2.0 environment when using the Certificate connection type with SAP CommonCryptoLib. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
## [](#5-9-4)5.9.4 **February 1, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The connector now correctly parses a nested structure in the metadata.

W-14710871

The ROW fields inside a table row in a BAPI function are now correctly parsed.

W-14808509
## [](#5-9-3)5.9.3 **January 9, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
## [](#5-9-2)5.9.2 **December 11, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The Function Listener source no longer encounters a deadlock when the flow completes and processes the event.

W-14556339
## [](#5-9-1)5.9.1 **September 19, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The new Asynchronous RFC and Synchronous RFC operations introduced in SAP 5.9.0 are now renamed to Asynchronous Remote Function Call and Synchronous Remote Function Call. The operations deprecated in SAP 5.9.0 are now renamed to Asynchronous Remote Function Call (Deprecated) and Synchronous Remote Function Call (Deprecated). The new operations can be used only with the latest JCo library (3.1.x) and the deprecated operations in SAP 5.9.0 can be used only with the earlier JCo library (3.0.x).

W-14070158
## [](#5-9-0)5.9.0 **September 1, 2023** ### What’s New - You can now use the new **Asynchronous RFC** and **Synchronous RFC** operations to enforce payload validation and ensure that the provided payload contains only the supported fields when calling a BAPI function. The existing **Asynchronous Remote Function Call** and **Synchronous Remote Function Call** operations are now deprecated, so you must use the new **Asynchronous RFC** and **Synchronous RFC** operations. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

Some logs are now at the DEBUG level as intended instead of the INFO level.

W-14050231
## [](#5-8-0)5.8.0 **April 20, 2023** ### What’s New - You can now filter IDocs by the type extension by using the new **Idoc Type Extension Filter Regex** field in the **Document listener** source. - The **Encoding** field is now exposed as an optional field in sources and in some operations. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue Resolution ID

The connector now correctly maps a value for a table that contains another table.

W-12970067
## [](#5-7-0)5.7.0 **January 13, 2023** ### What’s New - You can now achieve SAP SNC with Kerberos using the new Kerberos connection type. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
## [](#5-6-3)5.6.3 **October 5, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

The connector now sends the response back to SAP.

W-11686868
## [](#5-6-2)5.6.2 **September 8, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

The connector now establishes two RFC source connections at the same time.

W-11686906
## [](#5-6-1)5.6.1 **August 29, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

Sending IDocs with empty segments no longer fails.

W-11610118
## [](#5-6-0)5.6.0 **July 8, 2022** ### What’s New - You can now update a specific row in a table by adding the new `INDEX_ROW_UPDATE` parameter to the payload when using **Function Listener**. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
## [](#5-5-1)5.5.1 **February 1, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

SAP Connector did not work with multiple function listeners that used the same program ID.

SE-24176
## [](#5-5-0)5.5.0 **January 18, 2022** ### What’s New - Added a new parameter, **Use SAP Format On Function Listener**, to control the SAP date format on the function listener. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

The SAP connector date format for the function listener was always SAP format.

SE-23450

SAP remote function calls returned an incomplete byte array.

SE-23534

SAP objects' metadata inside a table rendered incorrectly.

SE-23232
## [](#5-4-1)5.4.1 **November 10, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP IDoc libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

The application was unresponsive after restarting SAP Connector.

SE-23348
## [](#5-4-0)5.4.0 **November 2, 2021** ### What’s New - The **Document Listener** and **Function Listener** sources can now connect to SAP via Message Server. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
## [](#5-3-5)5.3.5 **September 29, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

SAP request-response pattern did not work for the latest Mule version.

CONN-8906
## [](#5-3-4)5.3.4 **September 7, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### Fixed Issues
Issue ID

SAP connections did not close after stopping the application.

SE-21151
## [](#5-3-3)5.3.3 **July 16, 2021** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-23)Fixed Issues - SAP **Document Listener** received messages based on the SAP debug log but did not trigger a flow. (SE-21727) - SAP **Function Listener** stopped receiving messages after multiple exceptions. (SE-21728) ## [](#5-3-2)5.3.2 **June 2, 2021** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-24)Fixed Issues SAP Connector parsed DateTime objects using the `hhmmss` format instead of the `HHmmss` format. (SE-20522) ## [](#5-3-1)5.3.1 **May 12, 2021** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-25)Fixed issues The Runtime Manager restart of connections to the SAP environment hung and blocked the application. (SE-19866) ## [](#5-3-0)5.3.0 **January 29, 2021** ### [](#compatibility-31)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#features)Features Multiple DocumentSources and FunctionSources can now connect to the same SAP instance and listen to the same Program ID, Host, and Gateway. ## [](#5-2-1)5.2.1 **January 26, 2021** ### [](#compatibility-32)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-26)Fixed Issues Mule runtime engine did not release the connections to the gateway after the application restarted. (SE-18647) ## [](#5-2-0)5.2.0 **December 17, 2020** ### [](#compatibility-33)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-27)Fixed Issues - An error was not thrown for an IDoc parsing exception. (SE-18502) - Some exceptions logged at the ERROR level should have been logged at the DEBUG level. (SE-18631) ### [](#features-2)Features - Added IDocXMLProcessor parse and render options. ## [](#5-1-11)5.1.11 **November 25, 2020** ### [](#compatibility-34)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-28)Fixed Issues - SAP Connector could not process certain Japanese characters on Windows.(SE-18494) ## [](#5-1-10)5.1.10 **October 26, 2020** ### [](#compatibility-35)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-29)Fixed Issues - When there was an odd number of Chinese characters in a request, SAP Connector could not process them. (SE-17904) - SAP Connector did not listen for IDOC/BAPI from two different SAP instances when they had the same program ID configured. (SE-17173) ## [](#5-1-9)5.1.9 **September 18, 2020** ### [](#compatibility-36)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-30)Fixed Issues Added support for dylib on the connector’s certificate connection. ## [](#5-1-8)5.1.8 **August 31, 2020** ### [](#compatibility-37)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x, 3.1.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-31)Fixed Issues Support version 3.1.x of the Sap Java Connector Library. (SE-16428) ## [](#5-1-7)5.1.7 **June 29, 2020** ### [](#compatibility-38)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-32)Fixed Issues Fixed SAP outbound queue exception management. (SE-16428) ## [](#5-1-6)5.1.6 **June 3, 2020** ### [](#compatibility-39)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-33)Fixed Issues Fixed a security vulnerability. (CONN-6222) ## [](#5-1-5)5.1.5 **May 26, 2020** ### [](#compatibility-40)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-34)Fixed Issues - Restarting an application failed to register the program ID and other apps stopped processing. (SE-14920) - SAP Connector failed to serialize incoming data into a valid XML object when the data contained `0x0`. (SE-15986) ## [](#5-1-4)5.1.4 **April 29, 2020** ### [](#compatibility-41)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP JCo libraries

3.0.x

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-35)Fixed Issues - SAP Connector failed to receive IDOC\_INBOUND\_ASYNCHRONOUS on the function source because of parsing issues. (SE-15632) - Metadata did not mark nodes as repeatable. (SE-14232) ## [](#5-1-3)5.1.3 **April 16, 2020** ### [](#compatibility-42)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-36)Fixed Issues - Fixed existing vulnerabilities. (CONN-5801) - Fixed Munit cannot delete data folder while disposing an application in Windows. (SE-15095) ## [](#5-1-2)5.1.2 **March 13, 2020** ### [](#compatibility-43)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-37)Fixed Issues - SAP Connector failed to parse fields that started with a digit. (SE-15150) - SAP Connector did not send field values with special characters in the name to SAP. ## [](#5-1-1)5.1.1 **February 4, 2020** ### [](#compatibility-44)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-38)Fixed Issues - Fix for IDoc `BENEFIT3` basic type missing from metadata list (SE-13986) - Fix for `Found exception stopping source` warning for Inbound SAP Function Source Connector (SE-14337) ## [](#5-1-0)5.1.0 **December 30, 2019** ### [](#compatibility-45)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-39)Fixed Issues - SAP Connector table rows were missing in a response back to the SAP server. (SE-14063) - SAP Connector did not recognize all BAPI metadata. (SE-14018) - The `JCO_ERROR_DESTINATION_DATA_INVALID` error was incorrectly thrown in the SAP Connector. (SE-14098) ### [](#features-3)Features - Implemented metadata support for the function source. - Refactored error types to provide better error handling. ## [](#5-0-1)5.0.1 **December 18, 2019** ### [](#compatibility-46)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-40)Fixed Issues The issue where SAP Connector was not closing connections when the application was redeployed is fixed.
You must set the jco.destination.pool_capacity to 0 in the extended properties of the connector so the connection count is honored.
## [](#5-0-0)5.0.0 **November 8, 2019** ### [](#compatibility-47)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, and SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#features-4)Features This release contains the following new features and enhancements: - IDoc source filtering is added to enable users to filter the document type based on a regular expression. Any type of regular expression is supported. - The SAP X.509 certificate field is now required when the connection is `Certificate`. - The reconnection strategy on SAP (applies to operations only) is improved. With this enhancement, when a connection fails on the `FunctionSource` or `DocumentSource`, the JCo server automatically tries to reestablish a connection in the following way: - If a connection issue occurs, the JCo server retries immediately. - If the connection is not restored immediately, the JCo server waits for one second and retries. - If the connection is not restored after the second retry, the JCo server waits for two seconds and retries. - If the connection is still not restored, the JCo server retries at four seconds, and then again at eight seconds. - Message logging is added for when the connector is in `debug` mode. - The timeout parameter is removed because the JCo library does not support timeout functionality. ### [](#fixed-issues-41)Fixed Issues - Fixed some memory leak issues - Fixed class loader leak issues - Adapted demos for the new operation - Updated documentation - Fixed the issue of the function source request-response pattern not working (SE-13280) - Made other general changes that increase the stability and improve the performance of the connector ### [](#migration-information-for-sap-connector-5-0)Migration Information for SAP Connector 5.0 SAP Connector 5.0.0 provides some new features that provide a more efficient way to achieve the same results as in earlier versions. The new configuration also gives a better understanding of what configuration to use in the connector. These new features and enhancements may cause backward compatibility issues. - The `Create` operation is renamed `Retrieve IDoc`. - The execute BAPI functions over qRFC, tRFC, and sRFC operations are merged into Synchronous Remote Function Call (sRFC) and Asynchronous Remote Function Call (aRFC) operations. - **Disable function template cache flag** is renamed to **Disable JCo internal cache**, and applies to both functions and sources. The default value is `false`. - The sources now have `-listener` in their aliases instead of source. For example, the XML is changed from `sap:document-source` to `sap:document-listener`. - The SAP configuration has the following changes: - The SAP Inbound and SAP Outbound configurations are merged into the new SAP configuration. - The **Message Server** field is now in the **General** tab. ## [](#4-5-3)4.5.3 **April 29, 2020** ### [](#compatibility-48)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-42)Fixed Issues - SAP Connector failed to receive IDOC\_INBOUND\_ASYNCHRONOUS on the function source because of parsing issues. (SE-15632) - Metadata did not mark nodes as repeatable. (SE-14232) - Fixed Munit cannot delete data folder while disposing an application in Windows. (SE-15794) ## [](#4-5-2)4.5.2 **March 6, 2020** ### [](#compatibility-49)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-43)Fixed Issues - The issue that caused SAP Connector fail to parse fields starting with a digit is fixed. (SE-15150) - The issue that caused SAP Connector to not send values of fields with special characters in the name to SAP is fixed. ## [](#4-5-1)4.5.1 **February 4, 2020** ### [](#compatibility-50)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-44)Fixed Issues - Fix for IDoc `BENEFIT3` basic type missing from metadata list (SE-13986) - Fix for `Found exception stopping source` warning for Inbound SAP Function Source Connector (SE-14337) ## [](#4-5-0)4.5.0 **December 3, 2019** ### [](#compatibility-51)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#features-5)Features Added support for request-response pattern on all BAPIFunction parameters. ## [](#4-4-1)4.4.1 **November 29, 2019** ### [](#compatibility-52)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-45)Fixed Issues - Fixed SAP Connector metadata not being built for inner tables. (SE-14018) - Fixed SAP Connector not recognizing specific JCo error types as connection issues. (SE-14098) ## [](#4-4-0)4.4.0 **November 25, 2019** ### [](#compatibility-53)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#features-6)Features This release contains the following new feature: Implemented keys and output DataSense support for `FunctionSource`. ## [](#4-3-6)4.3.6 **October 4, 2019** ### [](#compatibility-54)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issue)Fixed Issue SAP Connector’s `FunctionSource` request-response pattern didn’t support data of type `Structure` within an RFC response. (SE-13280) ## [](#4-3-5)4.3.5 **September 20, 2019** ### [](#compatibility-55)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on the NetWeaver Platform

Supported SAP Industrial Solutions

SAP Retail, SAP Banking
### [](#fixed-issues-46)Fixed Issues - General connector improvements. - Refactoring to improve compliance with the Mule development best practices. - Deprecated the UNKNOWN error type that will be removed in the next major upcoming release. ## [](#4-3-4)4.3.4 **August 23, 2019** ### [](#compatibility-56)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

Supported SAP ERP Central Component

SAP ECC 6.0.

Supported SAP Business Suites Products

SAP Solution Manager, SAP CRM, SAP ERP, SAP PLM, SAP SCM, SAP SRM based on Netweaver Platform.

Supported SAP Industrial Solutions

SAP Retail, SAP Banking.
### [](#fixed-issues-47)Fixed Issues - Fixed missing configuration parameters in the source configuration. (SE-12658, SE-12484). - Fixed sRFC call that reported a successful response, but which had data missing on the SAP side. The timeout must be set to 0 (default value) to execute a function as a transaction. In this case, using a try scope. (SE-12681) ## [](#4-3-3)4.3.3 **August 8, 2019** ### [](#compatibility-57)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

SAP Solution

SAP ECC 6.0 and its subsequent enhancement packages.

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#features-7)Features Updated connector icons. ## [](#4-3-2)4.3.2 **July 26, 2019** ### [](#compatibility-58)Compatibility
Software Version

Mule

4.1.1 and later

Java

8

SAP Solution

SAP ECC 6.0 and its subsequent enhancement packages.

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#features-8)Features Updated the dependency on the File connector to its latest version (1.2.4). ## [](#4-3-1)4.3.1 **June 27, 2019** ### [](#compatibility-59)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

SAP ECC 6.0 and its subsequent enhancement packages.

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issue-2)Fixed Issue Fixed UNICODE null character at the end of response XML (CONN-2455) ## [](#4-3-0)4.3.0 **June 12, 2019** ### [](#compatibility-60)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issues-48)Fixed Issues - Retrieving 50K records using the SAP connector results in an OOME inconsistency at 1.5 GB heap memory. (CONN-1838) - Unable to define the RFC timeout setting in the SAP connector in Mule 4.(SE-12045) ## [](#4-2-1)4.2.1 **May 31, 2019** ### [](#compatibility-61)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issues-49)Fixed Issues - SAP Connector - Wrong number format returned. Fixed by adding the new `useSAPFormat` parameter, which if set to true, returns the default values received from SAP. (SE-12022) - SAP Connector - Parsing error when the SAP response contains nested tables. (SE-11910) - Fixed SAP Connector vulnerability to an XML External Entity (XXE). - Fixed SAP Connector Encoding field with a hint description. ## [](#4-2-0)4.2.0 **May 23, 2019** ### [](#compatibility-62)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#features-9)Features - New SAP format for the date and time when working with BAPI functions over sRFC: A new parameter in the SAP outbound configuration has been added to the Global Element Properties > **Advanced** tab. The **Use SAP date time format** defaults to the `false` value. If `true`, the DATE and TIME fields are formatted as strings in the `yyyy-MM-dd / HH:mm:ss` format. If false, the DATE and TIME fields values are returned. ### [](#fixed-issues-50)Fixed Issues - Added SAP date and time format (see Features for more information). (SE-11815) - The SAP connector did not accept special characters in an incoming BAPI function sRFC response. (SE-11651) - Configuring SNC in SAP connector was not working. Added message server configuration parameters: ```code String JCO_MSHOST = "jco.client.mshost"; String JCO_MSSERV = "jco.client.msserv"; String JCO_R3NAME = "jco.client.r3name"; String JCO_GROUP = "jco.client.group"; String JCO_SAPROUTER = "jco.client.saprouter"; ``` These are reflections of JCo properties. (SE-10985) ## [](#4-1-6)4.1.6 **May 10, 2019** ### [](#compatibility-63)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issues-51)Fixed Issues - SAP connector is not honoring the encoding set in the configuration. (SE-11690) - I\_DOCNUM is not being returned. (SE-11630) ## [](#4-1-5)4.1.5 **April 10, 2019** ### [](#compatibility-64)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issues-52)Fixed Issues - SAP Connector throws parsing XML error for a BAPI call (SE-11457) - Sap Connector caching JCOFunction templates. (SE-11417) - Solved the issue where empty tables would crash the metadata generation. (SE-10776) ## [](#4-1-4)4.1.4 **April 4, 2019** ### [](#compatibility-65)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issue-3)Fixed Issue SAP connector did not accept slash `/` in a BAPI function call. (SE-10952) ## [](#4-1-3)4.1.3 **March 28, 2019** ### [](#compatibility-66)Compatibility
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issues-53)Fixed Issues - Customer facing SAP connector was not able to update SAP correctly when IDOCs were sent as a collection. (SE-11221) - SAP connector did not accept slash "/" on a BAPI function call. (SE-10952) ## [](#4-1-2)4.1.2 **March 8, 2019**
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issues-54)Fixed Issues - Out of memory when retrieving data from SAP due to XML serialization. Solved by changing XML serialization implementation. - Fixed empty metadata name issue that caused the metadata generation to fail. The empty entries were removed so only the valid ones end up in the XML. - Fixed source not sending the response back to SAP in case of export parameters. Solved by implementing handling for this scenario. ## [](#4-1-1-deprecated)4.1.1 - Deprecated **October 23, 2018**
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#fixed-issue-4)Fixed Issue - Duplicate IDoc elements were filtered. Now they are properly processed. ## [](#4-1-0-deprecated)4.1.0 - Deprecated **July 25, 2018**
Software Version

Mule

4.1.1 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#features-10)Features Minimum Mule version set to 4.1.1. ### [](#fixed-issues-55)Fixed Issues - Trying to access row values in a table which does not have any rows yet was throwing an error. It doesn’t do that anymore now. - Connector can now be downloaded without having to add the releases repository in the settings.xml. ### [](#known-issues)Known Issues None ## [](#4-0-1-deprecated)4.0.1 - Deprecated **July 17, 2018**
Software Version

Mule

4.0.0 and later

Java

8

SAP Solution

ECC 6.0 and later

Supported Modules

SAP CRM, SAP ERP, SAP SRM, SAP SCM, and any other modules compatible with the NetWeaver platform.
### [](#features-11)Features No new features added ### [](#fixed-issue-5)Fixed Issue Information was missing when Idocs are received in connector. The information is now properly transmitted. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SAP S/4HANA OData Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for SAP S/4HANA OData Connector provides full support to query, create, update, and delete entities, and execute remote functions using the SAP S/4HANA API. Guide: [SAP S/4HANA OData Connector](https://docs.mulesoft.com/jp/sap-s4hana-cloud-connector/latest/) Reference: [SAP S/4HANA OData Connector Reference](https://docs.mulesoft.com/jp/sap-s4hana-cloud-connector/latest/sap-s4hana-cloud-connector-reference) ## [](#2-9-6)2.9.6 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.2.0 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
## [](#2-9-5)2.9.5 **August 31, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.2.0 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The gson library is upgraded to version 2.14.0.

  • The jackson library is upgraded to version 2.22.2.

  • The commons-codec library is upgraded to version 1.22.1.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The woodstox library is upgraded to version 7.2.2.

  • The guava library is upgraded to version 33.7.1-jre.

W-23840766
## [](#2-9-4)2.9.4 **July 1, 2026** ### Compatibility
Software Version

Mule

4.2.0 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.google.guava:guava library is upgraded to version 33.6.0-jre to address a reported security vulnerability (CVE-2023-2976).

W-22996181

The org.apache.commons:commons-text library is upgraded to version 1.15.0 to address a reported security vulnerability (CVE-2025-46295).

W-22996180
## [](#2-9-3)2.9.3 **August 27, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

FileAlreadyExistsException errors no longer occur when multiple users trigger the same Mule flow with dynamic configurations, due to improved concurrency handling.

W-18459988
## [](#2-9-2)2.9.2 **August 9, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.google.code.gson:gson library is upgraded to version 2.13.1.

  • The commons-io::commons-io library is upgraded to version 2.20.0.

  • The org.apache.commons::commons-lang3 library is upgraded to version 3.18.0.

W-18986663
## [](#2-9-1)2.9.1 **July 20, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now configure setters in HTTP headers when using the connector in Java 17 and Mule 4.9.x.

W-18625117
## [](#2-9-0)2.9.0 **May 1, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Batch update entity operation now uses the correct syntax for the OData v4 URI for fields that have the EDM type as GUID.

W-18213819

The connector now proactively re-triggers service discovery before each operation if the service list is empty.

W-18344579

The connector now throws the correct error types:

  • When there is an invalid filter provided in the operation, the connector now throws S4HANA:INVALID_FILTER instead of S4HANA:INVALID_ENTITY.

  • When there are authentication issues (such as an incorrect username, password, or URL), the connector now throws S4HANA:UNAUTHORIZED instead of S4HANA:NO_SUCH_SERVICE.

    This means a 403 Forbidden error received during the service discovery calls now explicitly causes the connector to throw S4HANA:UNAUTHORIZED. This indicates that the user’s SAP permissions for the service discovery URL are insufficient.

    To fix this, you can either:

    • Check permissions in the SAP server for the service discovery URL that is throwing the 403 Forbidden error.

    • Disable service discovery if you are not using it.

W-18169170, W-18516707, W-18723610
## [](#2-8-0)2.8.0 **April 8, 2025** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now supports pagination logic of version 2.6.2 and earlier in the Query operation with the new Legacy Pagination checkbox.

W-18183205
## [](#2-7-1)2.7.1 **March 11, 2025** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector check no longer throws exceptions during app initialization.

W-17427764

The logic to identify Custom Business Objects is changed. All entities starting with YY1 and ZZ1 are now considered as Custom Business Object entities.

W-17522361

The OData v4 service catalog now displays all service types except the UI service type.

W-17522361
## [](#2-7-0)2.7.0 **November 10, 2024** ### What’s New - SAP S/4HANA OData Connector now provides support for OData API v4. - To support OData API v4, the connector now includes the new **OData v4 service discovery relative path** field in the connection types. For information about the **OData v4 service discovery relative path** field, see [SAP S/4HANA OData Connector Reference](https://docs.mulesoft.com/jp/sap-s4hana-cloud-connector/latest/sap-s4hana-cloud-connector-reference). - The **Execute Function** operation now includes the new `S4HANA:INVALID_ENTITY` error type. - The connector now includes additional classifications for specific exceptions in certain scenarios. ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2 and v4

OpenJDK

8, 11, and 17
## [](#2-6-4)2.6.4 **October 8, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now has additional checks during app disposal to prevent exceptions.

W-16876722
## [](#2-6-3)2.6.3 **June 18, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Pagination in the Query operation now prevents redundant next calls when the maximum number of returned elements is reached.

W-16032742
## [](#2-6-2)2.6.2 **June 12, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly processes custom services with different URLs.

W-15457838
## [](#2-6-1)2.6.1 **January 16, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly filters conditional headers when fetching metadata.

W-14773734
## [](#2-6-0)2.6.0 **September 18, 2023** ### What’s New - The connector now supports custom namespaces. To support custom namespaces, the connector now includes the new **Scoped service discovery relative path** and **Services attributes** fields in the connection types and the new **Service Attribute** type. Use custom namespaces to define and organize custom objects and developments, such as programs, function modules, or tables. The naming convention for a custom namespace is `Z` or `Y` followed by an identifier. For example, if there are custom programs that manage customer data, you can create a custom namespace called `ZCUST` to organize all custom programs related to customer data. Custom namespaces enable you to maintain better control over your custom objects and developments and avoid naming conflicts with SAP standard objects or custom objects by other organizations, as well as improve the maintainability and upgradability of the system. ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
## [](#2-5-4)2.5.4 **March 6, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now correctly processes items of the Datetimeoffset and Guid data types.

W-12534658
## [](#2-5-3)2.5.3 **January 26, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

In case of error, the connector now responds to the original error response received from SAP.

W-12064688
## [](#2-5-2)2.5.2 **January 13, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Pagination now returns the correct number of items in the payload.

W-12284444
## [](#2-5-1)2.5.1 **October 24, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.12.6.1 to com.fasterxml.jackson.core:jackson-databind:2.14.0-rc1 to fix reported security vulnerabilities.

W-11853424
## [](#2-5-0)2.5.0 **October 6, 2022** ### What’s New - You can now use the new **Batch Upsert Custom Business Object** operation and the modified **Batch update entity** operation to support custom business objects. ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
## [](#2-4-5)2.4.5 **September 13, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The connector now correctly parses input parameters of type Number.

W-11719254
## [](#2-4-4)2.4.4 **September 9, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The OAuth 2.0 access token now refreshes after expiry.

W-11686820
## [](#2-4-3)2.4.3 **July 11, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The cache now works for multiple entities from the same service used in one application.

W-11362347
## [](#2-4-2)2.4.2 **April 18, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Batch Create Entity operation now returns the Bulk Item ID.

W-10885701
## [](#2-4-1)2.4.1 **April 4, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920476
## [](#2-4-0)2.4.0 **January 18, 2022** ### What’s New - Added support for a configurable cache of metadata for S/4HANA services to improve performance by not executing a metadata request in every operation call. ### Compatibility
App/Service Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
## [](#2-3-8)2.3.8 **January 3, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9290

Upgraded the com.fasterxml.jackson.core:jackson-databind dependency.

CONN-9838
## [](#2-3-7)2.3.7 **October 26, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The $count endpoint sometimes did not accept the application/json content-type. Now, the connector accepts the text/plain content-type when requesting the $count endpoint.

SE-23027
## [](#2-3-6)2.3.6 **July 16, 2021** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-24)Fixed Issues - The service used for requests is now used also for fetching the CSRF token. (SE-21821) - Improved the speed of retrieving metadata by using partial fetching. (SE-21443) ## [](#2-3-5)2.3.5 **June 29, 2021** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-25)Fixed Issues A precondition failed error was thrown using conditional headers. (SE-21532) ## [](#2-3-4)2.3.4 **May 11, 2021** ### [](#compatibility-31)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-26)Fixed Issues The connector was making multiple requests to fetch metadata in each invocation of the **Query** operation. (CONN-7964) ## [](#2-3-3)2.3.3 **May 3, 2021** ### [](#compatibility-32)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-27)Fixed Issues - Logging a request body using SAP S/4Hana logger with the `TRACE` level enabled threw an error. Use HttpMessageLogger instead of SAP S/4Hana logger for logging the payload. (SE-20520) ## [](#2-3-2)2.3.2 **March 8, 2021** ### [](#compatibility-33)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-28)Fixed Issues - Improved metadata loading performance (CONN-7658) ## [](#2-3-1)2.3.1 **February 11, 2021** ### [](#compatibility-34)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-29)Fixed Issues - Default HTTP headers were not included in a batch request. (SE-18812) - The connector was not returning a complete response. (SE-18902) ## [](#2-3-0)2.3.0 **January 29, 2021** ### [](#compatibility-35)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#features)Features Added support to enable or disable the automatic retrieval of a CSFR token before a resource-modifying request, such as a POST request. ## [](#2-2-3)2.2.3 **December 11, 2020** ### [](#compatibility-36)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-30)Fixed Issues Custom headers were not included in calls to retrieve the EDM model. (SE-18812) ## [](#2-2-2)2.2.2 **November 27, 2020** ### [](#compatibility-37)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#features-2)Features - Multiple libraries have been updated to the latest versions. ## [](#2-2-1)2.2.1 **July 27, 2020** ### [](#compatibility-38)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2

OpenJDK

8 and 11
### [](#fixed-issues-31)Fixed Issues - Invalid conversion of the date field in the URI (SE-16674) - Connector was adding two days to the `ValidityStartDate` field value (SE-16675) - Issues with creating a directory on Anypoint Runtime Fabric runtimes (SE-16669) ## [](#2-2-0)2.2.0 **July 22, 2020** ### [](#compatibility-39)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#features-3)Features The ability to configure the response timeout as well as the client and connection timeout for the request has been added. (SE-16430, CONN-5490) ## [](#2-1-0)2.1.0 **May 20, 2020** ### [](#compatibility-40)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#features-4)Features Added support for batch processing. (CONN-5488) ## [](#2-0-0)2.0.0 **March 19, 2020** ### [](#compatibility-41)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#features-5)Features Added support for OAuth 2.0 client credentials. This new feature breaks backward compatibility. (CONN-2944) See [Upgrade SAP S/4HANA OData Connector to 2.0](https://docs.mulesoft.com/jp/sap-s4hana-cloud-connector/latest/sap-s4hana-cloud-connector-upgrade-migrate) for information about how to upgrade to the latest version. ## [](#1-2-2)1.2.2 **June 1, 2020** ### [](#compatibility-42)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#fixed-issues-32)Fixed Issues The issue where PurchaseOrder entities could not be created after the SAP S/4HANA Cloud 2005 release is fixed. (CONN-6225) ## [](#1-2-1)1.2.1 **January 23, 2020** ### [](#compatibility-43)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#fixed-issues-33)Fixed Issues Unable to perform deep inserts. (SE-14296) ## [](#1-2-0)1.2.0 **December 18, 2019** ### [](#compatibility-44)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#features-6)Features - Returns HTTP response code and response headers as attributes. (CONN-3789) - Added parameter to enable or disable the discovery service. (CONN-3783) ### [](#fixed-issues-34)Fixed Issues - Create Entity operation failed when non-mandatory key fields weren’t set. (CONN-3911) - NexusIQ security vulnerability for the connector. (CONN-3733) - Removed the default asterisk (`*`) value for the Select parameter in the Get Entity and Query operations. (CONN-3796) ## [](#1-1-1)1.1.1 **October 25, 2019** ### [](#compatibility-45)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#fixed-issues-35)Fixed Issues Peformance regression and incorrect behavior of the **Query** operation in SAP S/4HANA OData Connector v1.1.0. (CONN-3794) ## [](#1-1-0)1.1.0 **September 27, 2019** ### [](#compatibility-46)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#features-7)Features - Added new **Expanded properties** parameter to support entity expansion in the **Get Entity by key** and **Query** operations. This parameter enables you to specify a comma-separated list of navigation properties. Each navigation property can be followed by a forward slash and another navigation property to identify a multi-level relationship. Properties of an expanded navigation property are not a part of the payload unless selected. - New `S4HANA:SERVER_ERROR` and `S4HANA:NO_SUCH_NAVIGATION_PROPERTY` errors are provided. ### [](#fixed-issues-36)Fixed Issues - Fixed bugs related to creating and updating sales orders and purchase orders when line items were specified. (CONN-2530) - Date and time formats were not formatted correctly. (CONN-3075) - Connector did not stop the HTTP client when resolving metadata. (CONN-3498) - There was no way to specify an entity key when performing an update operation. (SE-13101) - The **Returned Fields** parameter description is revised to be: a comma-separated list of selection clauses. Each selection clause may be a property name, navigation property name, or the asterisk `*` character. The `*` syntax causes all properties for an entry to be included without traversing associations. Use forward slash `/` to select fields of expanded navigation properties. If no field is selected, then all fields are returned. ## [](#1-0-2)1.0.2 **August 8, 2019** ### [](#compatibility-47)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#features-8)Features Updated connector icons. ## [](#1-0-1)1.0.1 **July 3, 2019** ### [](#compatibility-48)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
### [](#fixed-issues-37)Fixed Issues Fixed the **Test Connection** issue. ## [](#1-0-0)1.0.0 **June 28, 2019** Mule 4 version of the SAP S/4HANA OData Connector. ### [](#compatibility-49)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA API

v1

OData API

v2
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SAP S/4HANA SOAP Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for SAP S/4HANA SOAP Connector provides full support to execute operations on SAP S/4HANA’s SOAP APIs. Guide: [SAP S/4HANA SOAP Connector User Guide](https://docs.mulesoft.com/jp/sap-s4hana-soap-connector/latest/) ## [](#2-6-2)2.6.2 **October 9, 2026** ### Compatibility
Software Version

Mule

4.2.2 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The wss4j libraries are upgraded to version 2.4.4.

  • The xmlschema-core library is upgraded to version 2.3.3.

W-24317616, W-24330655
## [](#2-6-1)2.6.1 **October 5, 2026** ### Compatibility
Software Version

Mule

4.2.2 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The com.fasterxml.jackson.core:jackson-databind and com.fasterxml.jackson.core:jackson-core libraries are upgraded to version 2.22.3.

  • The org.springframework:spring-core, org.springframework:spring-context, org.springframework:spring-expression, org.springframework:spring-beans, org.springframework:spring-aop, and org.springframework:spring-jcl libraries are upgraded to version 5.3.39-spring-framework-5.3.49.

  • The org.apache.neethi:neethi library is upgraded to version 3.2.4.

  • The org.apache.httpcomponents.core5:httpcore5 and org.apache.httpcomponents.core5:httpcore5-h2 libraries are upgraded to version 5.4.3.

  • The org.apache.httpcomponents.client5:httpclient5 library is upgraded to version 5.6.4.

  • The org.apache.cxf:cxf-core and org.apache.cxf:cxf-rt-wsdl libraries are upgraded to version 3.6.12.

  • The org.apache.commons:commons-lang3 library is upgraded to version 3.20.0.

  • The org.apache.santuario:xmlsec library is upgraded to version 2.3.5.

  • The org.mule.wsdl:mule-wsdl-parser library is upgraded to version 1.4.13.

W-23801100, W-24134445, W-24317616
## [](#2-6-0)2.6.0 **May 22, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Software Version

Mule

4.2.2 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8, 11, and 17
## [](#2-5-1)2.5.1 **March 20, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.2 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The following libraries are upgraded to address reported security vulnerabilities:

  • The mule-soap-engine library is upgraded to version 1.8.6.

  • The org.mule.wsdl parser library is upgraded to version 1.4.8.

  • The com.fasterxml.jackson.core library is upgraded to version 2.16.1.

  • The soa-model-core library is upgraded to version 2.0.1.

  • The commons-lang3 library is upgraded to version 3.14.0.

  • The org.apache.wss4j library is upgraded to version 2.4.3.

W-15058671
## [](#2-5-0)2.5.0 **May 26, 2023** ### What’s New - The **Listener Config** now contains the new **Security** field which enables you to configure message-level web service security for the **Outbound Message Listener** source. The new **Security** field enables you to configure or revoke client access, and enable message signature verification using X.509 certificates. ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
## [](#2-4-5)2.4.5 **October 28, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.12.6.1 to com.fasterxml.jackson.core:jackson-databind:2.14.0-rc1 to fix reported security vulnerabilities.

W-11853434
## [](#2-4-4)2.4.4 **June 29, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading org.apache.httpcomponents:httpclient:4.5.4 to org.apache.httpcomponents:httpclient:4.5.13.

W-11226199
## [](#2-4-3)2.4.3 **May 31, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the spring-beans package from org.springframework:spring-beans:5.3.18 to org.springframework:spring-beans:5.3.20.

W-11195295
## [](#2-4-2)2.4.2 **April 19, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerability by upgrading the spring-context package from org.springframework:spring-context:5.3.3 to org.springframework:spring-context:5.3.19.

W-11006018
## [](#2-4-1)2.4.1 **April 4, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the spring-beans package from org.springframework:spring-beans:5.3.3 to org.springframework:spring-beans:5.3.18.

W-10920498 and W-10933794
## [](#2-4-0)2.4.0 **March 29, 2022** ### What’s New - Added two optional parameters which secure the Outbound Message Listener: **Sender Business System ID** and **Recipient Business System ID**. ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
## [](#2-3-0)2.3.0 **February 28, 2022** ### What’s New - Added support for X509 SSL client certificates. - Added support for custom SOAP headers. ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
## [](#2-2-3)2.2.3 **January 13, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Updated the componentcom.fasterxml.jackson.core library to 2.12.6 to address security vulnerabilities.

CONN-8945
## [](#2-2-2)2.2.2 **October 26, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The connector threw a NullPointerException when resolving the metadata of some services.

SE-22652

Fixed a software vulnerability by upgrading the XMLSec library to org.apache.santuario:xmlsec:2.2.3.

CONN-8945
## [](#2-2-1)2.2.1 **April 29, 2021** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### [](#features)Features Added additional error logging for SOAP requests to make error tracking easier for asynchronous operations. To enable logging, set the logger named `com.mulesoft.connector.sap.s4hana.soap.internal.connection` to level `ERROR` or higher. ### [](#fixed-issues-11)Fixed Issues N/A ## [](#2-2-0)2.2.0 **March 8, 2021** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### [](#features-2)Features Added WS-Addressing capability. ### [](#fixed-issues-12)Fixed Issues N/A ## [](#2-1-4)2.1.4 **Janaury 7, 2021** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### [](#features-3)Features Upgraded the Groovy library to version 2.4.8. ### [](#fixed-issues-13)Fixed Issues N/A ## [](#2-1-3)2.1.3 **September 4, 2020** ### [](#compatibility-18)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1

OpenJDK

8 and 11
### [](#features-4)Features Multiple libraries are updated to the latest versions. ### [](#fixed-issues-14)Fixed Issues N/A ## [](#2-1-2)2.1.2 August 7, 2020 ### [](#compatibility-19)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1
### [](#features-5)Features N/A ### [](#fixed-issues-15)Fixed Issues A NullPointerException was thrown when the payload of incoming messages contained additional whitespaces or was pretty-printed. (SE-16979) ## [](#2-1-1)2.1.1 **July 14, 2020** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1
### [](#features-6)Features Upgraded Jackson libraries to the latest version 2.11.1 ### [](#fixed-issues-16)Fixed Issues N/A ### [](#known-issues)Known Issues Resolution of metadata keys in the Outbound Message Listener doesn’t work in Anypoint Studio versions below 7.6.0 (STUDIO-14846) Outbound Message Listener lacks the access to the BasePath parameter from the HTTP configuration. ## [](#2-1-0)2.1.0 **June 30** ### [](#compatibility-21)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1
### [](#features-7)Features Added the Outbound Message Listener input source, which listens for SAP S/4HANA outbound messages. (CONN-5914) ### [](#fixed-issues-17)Fixed Issues N/A ### [](#known-issues-2)Known Issues Resolution of metadata keys in the Outbound Message Listener doesn’t work in Anypoint Studio versions below 7.6.0 (STUDIO-14846) Outbound Message Listener lacks the access to the BasePath parameter from the HTTP configuration. ## [](#2-0-1)2.0.1 **May 15, 2020** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1
### [](#features-8)Features Updated multiple libraries to the latest version. ### [](#fixed-issues-18)Fixed Issues N/A ## [](#2-0-0)2.0.0 **April 2, 2020** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.2.1 and later

SAP S/4HANA SOAP API

v1
### [](#features-9)Features Added support for OAuth 2.0 client credentials. This new feature breaks backward compatibility. (CONN-5257) See [Upgrade SAP S/4HANA SOAP Connector to 2.0](https://docs.mulesoft.com/jp/sap-s4hana-soap-connector/latest/sap-s4hana-soap-connector-upgrade-migrate) for information about how to upgrade to the latest version. ### [](#fixed-issues-19)Fixed Issues N/A ## [](#1-0-0)1.0.0 **November 22, 2019** New release of Mule 4 version of the SAP S/4HANA SOAP Connector. ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.1 and later

SAP S/4HANA SOAP API

v1
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SAP SuccessFactors Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for SAP SuccessFactors (SAP SuccessFactors Connector) provides full support to query, create, update, and delete entities using the OData API v2 exposed by SuccessFactors. Guide: [SAP SuccessFactors Connector User Guide](https://docs.mulesoft.com/jp/sap-successfactors-connector/latest/) ## [](#5-0-4)5.0.4 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.6.6 and later

SuccessFactors API

OData API v2

OpenJDK

8, 11, and 17
## [](#5-0-3)5.0.3 **August 27, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.6.6 and later

SuccessFactors API

OData API v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Jackson Databind and Jackson Core libraries are upgraded to version 2.22.2.

  • The Gson library is upgraded to version 2.14.0.

  • The Apache Commons Codec library is upgraded to version 1.22.1.

W-23967456
## [](#5-0-2)5.0.2 **September 6, 2025** ### Compatibility
Software Version

Mule

4.6.6 and later

SuccessFactors API

OData API v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Default query parameters field now works correctly when using either the Edit inline or the Expression options.

W-19313743
## [](#5-0-1)5.0.1 **May 5, 2025** ### Compatibility
Software Version

Mule

4.6.6 and later

SuccessFactors API

OData API v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now successfully download the connector in Anypoint Studio because the org.mule.commons::mule-oauth-client dependency is upgraded to version 2.3.3.

W-18400354
## [](#5-0-0)5.0.0 **April 16, 2025** ### What’s New - Basic Authentication is now deprecated. - In OAuth SAML Bearer Assertion Authentication: - **The private key from the X.509 certificate.** and **The authorisation url.** fields are removed. - **Key store**, **Store password**, **Type**, and **Certificate alias** fields are added. - **Scopes** is moved from the **Advanced** tab to the **General** tab. For more information about how to upgrade the connector to version 5.0, refer to [Upgrading and Migrating SAP SuccessFactors Connector to Version 5.0](https://docs.mulesoft.com/jp/sap-successfactors-connector/latest/sap-successfactors-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.6.6 and later

SuccessFactors API

OData API v2

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer ignores proxy settings during the OAuth token call when using OAuth SAML Bearer Assertion Authentication.

W-18234690
## [](#4-1-9)4.1.9 **January 16, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8, 11, and 17
## [](#4-1-8)4.1.8 **February 27, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now includes TLS context initialization when creating a connection.

W-12511414
## [](#4-1-7)4.1.7 **January 11, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Query pagination now fetches all items.

W-12283628
## [](#4-1-6)4.1.6 **December 16, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Query pagination for a specific setup is now terminated when all required items are fetched from the server.

W-12211375
## [](#4-1-5)4.1.5 **October 27, 2022** ### What’s New - The Jackson Databind library is upgraded to `com.fasterxml.jackson.core:jackson-databind:2.14.0-rc1`. ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.12.6.1 to com.fasterxml.jackson.core:jackson-databind:2.14.0-rc1 to fix reported security vulnerabilities.

W-10920467
## [](#4-1-4)4.1.4 **April 5, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920467
## [](#4-1-3)4.1.3 **January 4, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9834
## [](#4-1-2)4.1.2 **December 23, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The Upsert operation threw an error for a user entity.

SE-23633
## [](#4-1-1)4.1.1 **November 19, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9258
## [](#4-1-0)4.1.0 **November 2, 2021** ### What’s New - Added support for server-side pagination: - Cursor-based pagination - Snapshot-based pagination ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
## [](#4-0-6)4.0.6 **October 18, 2021** ### Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The connector threw an exception that did not have error type mapping, which resulted in a null error type definition.

SE-22715
## [](#4-0-5)4.0.5 **June 29, 2021** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### [](#fixed-issues-14)Fixed Issues - The connector did not refresh the authentication token. (SE-20062) ## [](#4-0-4)4.0.4 **April 29, 2021** ### [](#compatibility-18)Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### [](#fixed-issues-15)Fixed Issues The **Query** operation did not refresh the authentication token. (SE-20062) ## [](#4-0-3)4.0.3 **April 22, 2021** ### [](#compatibility-19)Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### [](#fixed-issues-16)Fixed Issues The Query operation did not use the specified page size value. (SE-20440) ## [](#4-0-2)4.0.2 **March 19, 2021** ### [](#compatibility-20)Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### [](#fixed-issues-17)Fixed Issues The Query operation returned duplicate results. (SE-20027) ## [](#4-0-1)4.0.1 **December 11, 2020** ### [](#compatibility-21)Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### [](#fixed-issues-18)Fixed Issues Fixed an incompatibility with Scripting Module 2.0. ## [](#4-0-0)4.0.0 **November 04, 2020** ### [](#compatibility-22)Compatibility
Software Version

Mule

4.2.0 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### [](#features)Features Added support for OAuth 2.0 SAML Bearer Assertion authentication, which enables users to securely consume SAP SuccessFactors Employee Central OData API using a registered OAuth client ID and valid OAuth token. ## [](#3-2-1)3.2.1 **September 7, 2020** ## [](#3-2-2)3.2.2 **September 23, 2020** ### [](#compatibility-23)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2

OpenJDK

8 and 11
### [](#fixed-issues-19)Fixed Issues SAP SuccessFactors Connector 3.2 caused a java.lang.NoClassDefFoundError. (SE-17391) ## [](#3-2-1-2)3.2.1 **September 7, 2020** ### [](#compatibility-24)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2
### [](#fixed-issues-20)Fixed Issues Fixed a security vulnerability. (CONN-6896) ## [](#3-2-0)3.2.0 **July 15, 2020** ### [](#compatibility-25)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2
### [](#features-2)Features Added the following parameters for the Query and Get Entity by ID operations using the ODATA API exposed by the SuccessFactors system: - `$select` - `$expand` ## [](#3-1-4)3.1.4 **May 29, 2020** ### [](#compatibility-26)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2
### [](#fixed-issues-21)Fixed Issues Fixed a security vulnerability. (CONN-6223) ## [](#3-1-3)3.1.3 **April 29, 2020** ### [](#compatibility-27)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2
### [](#fixed-issues-22)Fixed Issues - The connector threw a connection exception on startup when deploying a test connection. (SE-15505) - Fixed all major and medium reported dependency-related vulnerabilities. (CONN-5820) ## [](#3-1-2)3.1.2 **August 8, 2019** ### [](#compatibility-28)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2
### [](#features-3)Features - Updated connector icons. ## [](#3-1-1)3.1.1 **June 10, 2019** ### [](#compatibility-29)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2
### [](#fixed-issues-23)Fixed Issues SuccessFactors Connector did not send the mandatory `hr` and `manager` fields. (SE-12039) ## [](#3-1-0)3.1.0 **March 25, 2019** ### [](#compatibility-30)Compatibility
Software Version

Mule

4.1.1 and later

SuccessFactors API

OData API v2
### [](#features-4)Features Added support for the SuccessFactors Update operation. ## [](#3-0-0)3.0.0 **June 27, 2018** Mule 4 version of SAP SuccessFactors Connector. **Note:** Version 3.0.0 and later discards the SFAPI API and introduces the ODATA API v2 exposed by SuccessFactors. ### [](#compatibility-31)Compatibility
Software Version

Mule

4.0.0 and later

SuccessFactors API

ODATA API (Olingo 2.0.0)
## [](#see-also)See Also - [SuccessFactors HCM Suite](https://help.sap.com/docs/r/product/SAP_SUCCESSFACTORS_HXM_SUITE) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Scheduler Service Release Notes - Mule 4 ## [](#1-3-2)1.3.2 **Jun 12, 2020** ### [](#new-features)New Features - None. ### [](#fixed-issues)Fixed Issues - Race condition between scheduler stop and scheduleWithFixedDelay leads to a memory leak. (MULE-18471) ## [](#1-2-6)1.2.6 **Jun 12, 2020** ### [](#new-features-2)New Features - None. ### [](#fixed-issues-2)Fixed Issues - Race condition between scheduler stop and scheduleWithFixedDelay leads to a memory leak. (MULE-18471) ## [](#1-3-1)1.3.1 **Jun 10, 2020** ### [](#new-features-3)New Features - None. ### [](#fixed-issues-3)Fixed Issues - CustomScheduler#destroyThreadGroup is taking more than configured shutdownTimeout. (MULE-18224) ## [](#1-2-5)1.2.5 **Jun 10, 2020** ### [](#new-features-4)New Features - None. ### [](#fixed-issues-4)Fixed Issues - CustomScheduler#destroyThreadGroup is taking more than configured shutdownTimeout. (MULE-18224) ## [](#1-2-2)1.2.2 **May 22, 2019** ### [](#new-features-5)New Features - None. ### [](#fixed-issues-5)Fixed Issues - Race condition in prestartCoreThreads for a Scheduler. (MULE-16858) ## [](#1-1-10)1.1.10 **May 22, 2019** ### [](#new-features-6)New Features - None. ### [](#fixed-issues-6)Fixed Issues - Race condition in prestartCoreThreads for a Scheduler. (MULE-16858) ## [](#1-2-1)1.2.1 **May 20, 2019** ### [](#new-features-and-enhancements)New Features and Enhancements - Allow the properties in scheduler-pools.conf to be configured as system property. (MULE-16788) ### [](#fixed-issues-7)Fixed Issues - Setting low heap memory in multicore machine causes Mule to fail to start. (MULE-16829) - NPE when a customScheduler is shutting down itself. (MULE-16760) - WARN logged when fixed rate task overlap in a single thread. (MULE-16759) ## [](#1-1-9)1.1.9 **May 20, 2019** ### [](#new-features-7)New Features - None. ### [](#fixed-issues-8)Fixed Issues - Setting low heap memory in multicore machine causes Mule to fail to start. (MULE-16829) ## [](#1-2-0)1.2.0 **April 25, 2019** ### [](#new-features-8)New Features - Allow overriding the location of the Scheduler config file via a system property. (MULE-14552) ### [](#fixed-issues-9)Fixed Issues - NPE when a customScheduler is shutting down itself. (MULE-16760) - WARN logged when fixed rate task overlap in a single thread Scheduler. (MULE-16759) - Race condition in ThreadGroup destroying for customScheduler threadGroup. (MULE-16516) - Rejected from scheduler warning has too high frequency in logs. (MULE-15588) - Avoid keeping references to muleContext from a CustomScheduler. (MULE-14907) - Custom Scheduler shutdown from a thread from the same scheduler fails. (MULE-14736) - Cannot destroy thread groups that have commons-pool evictor threads. (MULE-14675) - ThrottlingScheduler active tasks count breaks when tasks are cancelled.. (MULE-14590) - Delayed task is triggered when target Scheduler is busy is lost. (MULE-14577) \*| Scheduler#scheduleAtFixedRate cancels task if triggered while previous is still running. (MULE-14572) - Unclear error with missing parameter in Scheduler configuration. (MULE-14558) - Schedulers don’t indicate which one is exhausted. (MULE-14524) - Add data about dangling threads when a ThreadGroup can’t be destroyed. (MULE-15666) - Add an option to always log the creation location of a Schedule. (MULE-15531) ## [](#1-1-8)1.1.8 **April 25, 2019** ### [](#new-features-9)New Features - None. ### [](#fixed-issues-10)Fixed Issues - NPE when a customScheduler is shutting down itself. (MULE-16760) - WARN logged when fixed rate task overlap in a single thread Scheduler. (MULE-16759) - Race condition in ThreadGroup destroying for customScheduler threadGrou. (MULE-16516) ## [](#1-1-7)1.1.7 **October 9, 2018** ### [](#new-features-10)New Features - None. ### [](#fixed-issues-11)Fixed Issues - Rejected from scheduler warning has too high a frequency in logs. (MULE-15588) - Leaks through hard references to types, classloaders, and Schedulers. (MULE-15716) - Add data about dangling threads when a ThreadGroup can’t be destroyed. (MULE-15666) - Add an option to always log the creation location of a Scheduler. (MULE-15531) ## [](#1-1-6)1.1.6 **July 24, 2018** ### [](#new-features-11)New Features - None. ### [](#fixed-issues-12)Fixed Issues - Scheduler Service: provide a method to determine if current thread is CPU. (MULE-15415) ## [](#1-1-5)1.1.5 **May 9, 2018** ### [](#new-features-12)New Features - None. ### [](#fixed-issues-13)Fixed Issues - Avoid keeping references to muleContext from a CustomScheduler. (MULE-14907) ## [](#1-1-4)1.1.4 **March 16, 2018** ### [](#new-features-13)New Features - None. ### [](#fixed-issues-14)Fixed Issues - Custom scheduler shutdown from a thread from the same Scheduler fails. (MULE-14736) - Minor performance improvements. (MULE-14693) ## [](#1-1-3)1.1.3 **March 7, 2018** ### [](#new-features-14)New Features - None. ### [](#fixed-issues-15)Fixed Issues - Cannot destroy thread groups that have commons-pool evictor threads. (MULE-14675) - Race condition in reactor causes premature thread. (MULE-14665) ## [](#1-1-2)1.1.2 **March 5, 2018** ### [](#new-features-15)New Features - None. ### [](#fixed-issues-16)Fixed Issues - ThrottlingScheduler active tasks count breaks when tasks are cancelled. (MULE-14590) - Delayed task is triggered when target scheduler is busy is lost. (MULE-14577) - Too many ThreadGroup instances leaked after redeploy. (MULE-14658) ## [](#1-1-1)1.1.1 **January 31, 2018** ### [](#new-features-16)New Features - Allow to override the location of the scheduler config file via system property. (MULE-14552) ### [](#fixed-issues-17)Fixed Issues - Scheduler#scheduleAtFixedRate cancels task if triggered while previous is still running. (MULE-14572) - Unclear error with missing parameter in scheduler configuration. (MULE-14558) - Schedulers don’t indicate which one is exhausted. (MULE-14524) - Prevent classloader leak through accesscontext in thread. (MULE-14179) ## [](#1-1-0)1.1.0 **January 30, 2018** Initial Release. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Schema Validation Policy The Schema Validation Policy policy validates incoming traffic against a supplied API schema For configuration details, see [Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-schema-validation). ## [](#september-2-2026)September 2, 2026 ### What’s New - The policy now validates `multipart/form-data` requests against their OAS schema definitions, in addition to `application/json` request bodies. - Schema Validation Policy policy implementation version x.x.x is now supported by Omni Gateway. - Schema Validation Policy policy definition version x.x.x is now supported by Omni Gateway. ## [](#february-27-2025)February 27, 2025 ### What’s New - Schema Validation Policy policy implementation version 1.1.1 is now supported by Omni Gateway. - Schema Validation Policy policy definition version 1.0.0 is now supported by Omni Gateway. # Scripting Module Release Notes for Mule 4 Support Category: Select Scripting module executes custom logic written in a scripting language. Guide: [Scripting Module User Guide](https://docs.mulesoft.com/jp/scripting-module/latest/) ## [](#2-1-4)2.1.4 **September 25, 2026** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

NullPointerException errors no longer occur when a flow that contains a <script:execute> operation is invoked concurrently for the first time.

W-24088176

The io.projectreactor:reactor-core library is upgraded to version 3.8.7 to address the CVE-2026-47857 security vulnerability.

W-24277557
## [](#2-1-3)2.1.3 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#2-1-2)2.1.2 **August 17, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jruby library is upgraded to version 9.4.15.0.

  • The commons-lang3 library is upgraded to version 3.20.0.

W-23657171
## [](#2-1-1)2.1.1 **June 5, 2024** ### What’s New - The GraalVM JS libraries are removed from the scripting module to reduce its size. You must now provide those libraries yourself. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#2-1-0)2.1.0 **December 14, 2023** ### What’s New - This connector is now compatible with Java 17. - GraalVM JS libraries added 20MB+ size. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#2-0-4)2.0.4 **October 31, 2023** ### Compatibility
Software Version

Mule

4.2.0 and later
### Fixed Issues
Issue Resolution ID

Memory leak no longer occurs when using Groovy after multiple re-deployments.

W-12691090
## [](#2-0-3)2.0.3 **September 28, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later
### Fixed Issues
Issue Resolution ID

Scripting engine ECMAScript not found error no longer occurs.

W-11619477
## [](#2-0-2)2.0.2 **August 3, 2022** ### Compatibility
Software Version

Mule

4.2.0 and later
### Fixed Issues
Issue Resolution ID

Fixed multiple vulnerabilities and removed unnecessary dependencies. Scripting module now uses external libraries instead.

W-11472915
## [](#2-0-1-deprecated)2.0.1 (Deprecated) **March 17, 2022** This version is deprecated. All of the features and fixed issues for this version are in version 2.0.2. ## [](#2-0-0)2.0.0 **June 29, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.2.0** ### [](#new-features-and-enhancements)New Features and Enhancements Scripting Module does not bundles anymore scripting engines which drastically reduces the size of Mule applications. Streams are now correctly injected into the script avoiding the injection of internal MuleSoft classes. ### [](#fixed-issues-6)Fixed Issues - The usage of Scripting Module increase drastically the size of Mule applications. ## [](#1-1-7)1.1.7 **April 17, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-2)New Features and Enhancements None. ### [](#fixed-issues-7)Fixed Issues - Upgraded JRuby dependency to 9.2.11.1. - Upgraded Jython dependency to 2.7.2. - Upgraded Reactor dependency to 3.2.3. - Updated connectors-parent version to 1.1.7 (MULE-18198) - Updated MUnit version to the latest release (MULE-17301) ## [](#1-1-6)1.1.6 **April 11, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-3)New Features and Enhancements None. ### [](#fixed-issues-8)Fixed Issues - Upgraded JRuby dependency to 9.2.7.0. (MULE-16706) - Upgraded Reactor dependency to 3.2.8. (MULE-16706) - Upgraded Groovy dependency to 2.4.16. (MULE-16706) ## [](#1-1-5)1.1.5 **April 8, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-4)New Features and Enhancements None. ### [](#fixed-issues-9)Fixed Issues - Upgraded JRuby dependency to 9.2.6.0. (MULE-16673) - Upgraded Reactor dependency to 3.2.6. (MULE-16189) ## [](#1-1-4)1.1.4 **January 31, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-5)New Features and Enhancements N/A ### [](#fixed-issues-10)Fixed Issues - Scripting Module propagates the input payload MimeType as the output payload MimeType. (MULE-15640) - Improve Static Metadata. (MULE-14951) - Upgrade Groovy to 2.4.15. (MULE-14926) ## [](#1-1-3)1.1.3 **July 12, 2018** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements N/A ### [](#fixed-issues-11)Fixed Issues - Scripting checks registry on each execution. (MULE-15294) - Race condition in Scripting module initialization. (MULE-15339) ## [](#1-1-2)1.1.2 **May 7, 2018** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.0.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements This release includes the following enhancements, changes, and fixes: - Improves processing by changing execution type from CPU\_LITE to CPU\_INTENSIVE. - Improves context variables binding by only exposing compatibility related ones when such plugin is present. ### [](#fixed-issues-12)Fixed Issues - Thread type to be used by scripting component must be CPU\_INTENSIVE. (MULE-14720) - Limit DW message binding context attribute exposure. (MULE-13297) ## [](#1-1-1)1.1.1 **March 15, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.0.0** ### [](#new-features-and-enhancements-8)New Features and Enhancements This release includes the following library upgrade: - JRuby to version 9.1.16.0. ### [](#fixed-issues-13)Fixed Issues - Upgrade jruby-stdlib to 9.1.16.0. (MULE-14639) ## [](#1-1-0)1.1.0 **Jan 23, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.0.0** ### [](#new-features-and-enhancements-9)New Features and Enhancements Initial release. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Secrets Manager Release Notes ## [](#october-2-2025)October 2, 2025 Secrets Manager now supports TLS 1.3 for TLS Contexts. When creating or modifying a TLS Context for Mule, TLS 1.3 from the list of supported protocols. This enhancement enables your Mule applications to leverage the latest security standards, ensuring more secure and performant connections with external services. ## [](#february-20-2021)February 20, 2021 Starting with this release, Secrets Manager no longer uses the lock feature when creating or modifying a secrets group. In previous versions of Secrets Manager, changes made to a secrets group were not applied until you clicked **Finish** to commit the changes. After this update, changes to a secret group, such as creating a key store or TLS context, are applied as soon as they are created or saved. The **Finish** and **Cancel Edit** buttons are no longer applicable. ## [](#march-30-2020)March 30, 2020 When creating a TLS context using Secrets Manager, the expiration date incorrectly defaults to one year for keystore expirations that are shorter than one year. (SE-15141) Workaround: Manually enter the correct expiration date in the **Expiration Date** field when creating or editing a TLS context. ## [](#november-9-2019)November 9, 2019 This release has the following known issue: In the Secret Groups left navigation, **CRL Distributor Config** appears, but it is not yet supported, and you can’t add a Certificate List Distributor (CRL) configuration to your Secret Group. ## [](#january-12-2019)January 12, 2019 This Secrets Manager release has the following fixed issue: ### [](#users-unable-to-perform-actions-in-secrets-manager)Users Unable to Perform Actions in Secrets Manager When users of business groups accessed the Secrets Manager user interface, the `do not have permission` error occurred when trying to perform actions in Secrets Manager. This happened even though the root organization (or a parent of a business group) had the **API Manager Environments** entitlement. FIX: If the root organization has the **API Manager Environments** entitlement, users of the child business groups are now able to access Secrets Manager functionality. For more information about Secrets Manager, see [Secret Groups](https://docs.mulesoft.com/jp/anypoint-security/asm-secret-group-concept) ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Secure Configuration Properties Extension Release Notes for Mule 4 Support Category: Select ## [](#1-3-2)1.3.2 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#1-3-1)1.3.1 **July 22, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Commons IO library is upgraded to version 2.22.0 to address reported security vulnerabilities.

W-23441575
## [](#1-3-0)1.3.0 **September 30, 2025** ### Compatibility
Software Version

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-19679723
## [](#1-2-7)1.2.7 **January 30, 2024** ### Compatibility
Software Version

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated mule-encryption dependency.

W-14922250
## [](#1-2-6)1.2.6 **December 13, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

OpenJDK

8, 11, and 17
## [](#1-2-5)1.2.5 - Sep 14, 2022 \* ### Fixed Issues
Description ID

The Secure Properties Tool supports additional scenarios to remove escape characters before encrypting strings in the file value and console.

W-10698898
## [](#1-2-4)1.2.4 - Aug 18, 2022 \* ### Fixed Issues
Description ID

The Secure Properties Tool now supports removing escape characters before encrypting strings in the file value and console.

W-10698898
## [](#1-2-3)1.2.3 - June 25, 2020 \* ### [](#fixed-issues-6)Fixed Issues - Show warning message in Secure Properties when properties are not encrypted (EE-7370) ## [](#1-2-2)1.2.2 - April 13, 2020 \* ### [](#fixed-issues-7)Fixed Issues - Support random initialization vector (IV) usage (MULE-18292) ## [](#1-2-1)1.2.1 - February 20, 2020 \* ### [](#fixed-issues-8)Fixed Issues - Secure Configuration Properties - Encoding dropdown values (MULE-18066) ## [](#1-2-0)1.2.0 **July 12, 2019** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.2.0** ### [](#new-features)New Features - Support file-level encryption for configuration property files. (EE-5893) ## [](#1-1-0)1.1.0 **April 23, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#known-limitations-and-workarounds)Known Limitations and Workarounds The key size for the Blowfish algorithm cannot exceed 448 bits. This limit is by design because larger keys don’t add additional security. ### [](#fixed-issues-9)Fixed Issues - Reduce the size of the mule-secure-configuration-property-module by removing dependency to BC. (EE-6623) - Review: Encryption is adding 4MB to each policy. (AGW-2709) - Extract secure properties encryption code into runtime module. (AGW-2405) - Secure Configuration Properties should have correct display model for File Attribute. (EE-6260) ## [](#1-0-2)1.0.2 **July 25, 2018** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-10)Fixed Issues - NPE when using secure-properties and mode is not set. (MULE-15392) ## [](#1-0-1)1.0.1 **May 2, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-11)Fixed Issues - Secure Properties cannot be defined depending on another secure property. (EE-6050) ## [](#1-0-0)1.0.0 **March 21, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-2)New Features - Initial Release ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Server-Sent Events (SSE) Logging The Server-Sent Events (SSE) Logging policy logs every SSE event while streaming. For configuration details, see [SSE Logging Policy](https://docs.mulesoft.com/gateway/latest/policies-included-sse-logging). ## [](#april-30-2026)April 30, 2026 ### What’s New - Server-Sent Events (SSE) Logging policy implementation version 1.0.4 is now supported by Omni Gateway. ## [](#april-20-2026)April 20, 2026 ### What’s New - Server-Sent Events (SSE) Logging policy definition version 1.0.2 is now supported by Omni Gateway. # ServiceNow Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [ServiceNow Connector User Guide](https://docs.mulesoft.com/servicenow-connector/latest/) ## [](#6-18-8)6.18.8 **October 23, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, Yokohama, Zurich, and Australia

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-24541378
## [](#6-18-7)6.18.7 **October 22, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, Yokohama, Zurich, and Australia

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

ServiceNow Connector now returns an INVALID_WSDL error instead of parsing WSDL documents that contain any of the following:

  • A DOCTYPE declaration

  • An XInclude element

  • An absolute import, include, or redefine reference in a WSDL or XML schema

Relative WSDL and schema imports continue to work.

W-24541378
## [](#6-18-6)6.18.6 **October 6, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, Yokohama, Zurich, and Australia

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jsoup library is upgraded to version 1.23.2.

  • The gson library is upgraded to version 2.14.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The guava library is upgraded to version 33.6.0-jre.

  • The neethi library is upgraded to version 3.2.4.

  • The Apache CXF libraries are upgraded to version 3.6.12.

  • The jaxb-runtime and jaxb-api libraries are upgraded to version 2.3.1.

W-24123989, W-24326375, W-3300013
## [](#6-18-5)6.18.5 **August 10, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, Yokohama, Zurich, and Australia

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The spring-beans, spring-context, and spring-expression libraries are upgraded to version 6.2.19.

  • The jsoup library is upgraded to version 1.23.1.

W-23623404
## [](#6-18-4)6.18.4 **June 12, 2026** ### What’s New - ServiceNow Connector now supports the Australia API release. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, Yokohama, Zurich, and Australia

OpenJDK

8, 11, and 17
## [](#6-18-3)6.18.3 **June 1, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, Yokohama, and Zurich

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-22237178
## [](#6-18-2)6.18.2 **April 12, 2026** ### What’s New - ServiceNow Connector now supports the Zurich API release. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, Yokohama, and Zurich

OpenJDK

8, 11, and 17
## [](#6-18-1)6.18.1 **December 20, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, and Yokohama

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.springframework:spring-beans library is upgraded to 6.2.11.

W-20593332

The org.springframework:spring-context library is upgraded to 6.2.11.

W-20622326

The commons-io:commons-io library is upgraded to 2.19.0.

W-20593114

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20622326
## [](#6-18-0)6.18.0 **August 15, 2025** ### What’s New - ServiceNow Connector now supports the Xanadu and Yokohama API releases. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington, Xanadu, and Yokohama

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The org.mule.connectors:mule-soap-engine library is upgraded to version 1.10.2.

  • The org.mule.connectors:mule-http-connector library is upgraded to version 1.10.3.

  • The org.springframework.spring-expression library is upgraded to version 5.3.39.

  • The com.google.code.gson:gson library is upgraded to version 2.13.1.

  • The commons-beanutils:commons-beanutils library is upgraded to version 1.11.0.

  • The commons-io:commons-io library library is upgraded to version 2.19.0.

  • The org.yaml:snakeyaml library is upgraded to version 2.4.

  • The org.apache.commons:commons-lang3 library is upgraded to version 3.18.0.

W-18981319
## [](#6-17-1)6.17.1 **March 19, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, and Washington (default)

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-collections:commons-collections library version 3.2.2 is excluded to address reported security vulnerabilities.

W-16863227
## [](#6-17-0)6.17.0 **February 26, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, and Washington (default)

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17345882
## [](#6-16-1)6.16.1 **October 1, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, and Washington (default)

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.mule.connectors:mule-soap-engine library is upgraded to version 1.9.3 to address reported security vulnerabilities.

W-16841974
## [](#6-16-0)6.16.0 **April 24, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, and Washington (default)

OpenJDK

8, 11, and 17
## [](#6-15-0)6.15.0 **March 7, 2024** ### What’s New - ServiceNow Connector now supports the Utah, Vancouver, and Washington API releases. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, and Washington (default)

OpenJDK

8, 11, and 17
## [](#6-14-1)6.14.1 **January 23, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, and Tokyo (default)

OpenJDK

8, 11, and 17
## [](#6-14-0)6.14.0 **April 19, 2023** ### What’s New - The **Invoke** operation now contains the **Allow Empty Value** field, which enables you to clear a specific field with a null or empty value for the `update` operation. - The OAuth 2.0 Authorization Code connection now contains an optional **State** field. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, and Tokyo (default)

OpenJDK

8 or 11
## [](#6-13-0)6.13.0 **January 10, 2023** ### What’s New - ServiceNow Connector now supports the Tokyo release. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, and Tokyo (default)

OpenJDK

8 or 11
## [](#6-12-1)6.12.1 **December 12, 2022** ### What’s New - The org.apache.commons library is upgraded to version 1.10.0. - The org.springframework library is upgraded to version 5.3.20. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, and San Diego (default)

OpenJDK

8 or 11
### Fixed Issues
Issue Resolution ID

The New/Updated Record source now picks up messages for all appropriate timestamps.

W-12176039

Sudden disconnections in high workload scenarios no longer occur.

W-12035222

The org.apache.commons library is upgraded to version 1.10.0 to address reported security vulnerabilities.

W-11913979

The org.springframework library is upgraded to version 5.3.20 to address reported security vulnerabilities.

W-12150392
## [](#6-12-0)6.12.0 **September 27, 2022** ### What’s New - ServiceNow Connector now supports the San Diego release. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, Rome, and San Diego (default)

OpenJDK

8 or 11
## [](#6-11-7)6.11.7 **August 31, 2022** ### What’s New - The jsoup component is upgraded to version 1.15.3 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
### Fixed Issues
Issue ID

The jsoup component is upgraded to version 1.15.3 to address reported security vulnerabilities.

W-11662365
## [](#6-11-6)6.11.6 **August 25, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
### Fixed Issues
Issue ID

The connector no longer creates SoapClients for subsequent requests to ServiceNow when there are multiple credential variables in the MEL expression.

W-11384532
## [](#6-11-5)6.11.5 **August 19, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
### Fixed Issues
Issue ID

The Read Timeout field is updated from 5 seconds to 15 seconds to avoid timeouts on large tables.

W-11601586
## [](#6-11-4)6.11.4 **August 2, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
### Fixed Issues
Issue ID

Some display names now use title case instead of sentence case.

W-10575461
## [](#6-11-3)6.11.3 **June 15, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
### Fixed Issues This release includes only non-user-impacting changes. ## [](#6-11-2)6.11.2 **May 10, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
### Fixed Issues
Issue ID

The connector now loads all available tables automatically, however, you can still use the user table override to access tables that do not load.

W-10919969

Fixed reported security vulnerabilities by upgrading the Spring Beans dependency from org.springframework:spring-beans:5.3.17 to org.springframework:spring-beans:5.3.19.

W-10981860

Fixed reported security vulnerabilities by upgrading the Spring Context dependency from org.springframework:spring-context:5.2.7.RELEASE to org.springframework:spring-context:5.3.19.

W-11001899
## [](#6-11-1)6.11.1 **April 11, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Spring Beans library from org.springframework.spring-beans:5.2.7 to org.springframework.spring-beans:5.3.17.

W-10933795

Fixed reported security vulnerabilities by upgrading the Spring Expression library from org.springframework.spring-expression:5.2.7 to org.springframework.spring-expression:5.3.17.

W-10920482
## [](#6-11-0)6.11.0 **October 28, 2021** ### What’s New - Added support for the ServiceNow `Rome` release. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris, Quebec, and Rome (default)

OpenJDK

8 or 11
## [](#6-10-2)6.10.2 **October 4, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris and Quebec (default)

OpenJDK

8 or 11
### Fixed Issues
Issue ID

Removed the vulnerabilities caused by the XMLSec library.

CONN-8936
## [](#6-10-1)6.10.1 **August 3, 2021** ### [](#compatibility-29)Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris and Quebec (default)

OpenJDK

8 or 11
### [](#fixed-issues-20)Fixed Issues - WSDL files are now stored in a temporary directory to prevent storage leakage. (SE-19180, SE-21870) ## [](#6-10-0)6.10.0 **July 19, 2021** ### [](#compatibility-30)Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris and Quebec (default)

OpenJDK

8 or 11
### [](#new-features)New Features - Added the **On New/Updated Record** source. ## [](#6-9-1)6.9.1 **June 3, 2021** ### [](#compatibility-31)Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris and Quebec (default)

OpenJDK

8 or 11
### [](#features)Features - None. ### [](#fixed-issues-21)Fixed Issues If you did not enter credentials on the **Transport** tab when configuring the connector, the connector returned a `NullPointerException` when testing the connection. This error occurred even if you entered credentials on the **General** tab. You can now enter credentials on the **General** tab only. (CONN-2986 and CONN-8307) ### [](#known-issues)Known Issues - None. ## [](#6-9-0)6.9.0 **March 18, 2021** ### [](#compatibility-32)Compatibility
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando, Paris and Quebec (default)

OpenJDK

8 or 11
### [](#features-2)Features Added support for the ServiceNow `Quebec` release. ### [](#fixed-issues-22)Fixed Issues - None. ### [](#known-issues-2)Known Issues - None. ## [](#6-8-0)6.8.0 **December 11, 2020**
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando and Paris (default)

OpenJDK

8 or 11
### [](#features-3)Features Added support for using the `Encoding` field. ### [](#fixed-issues-23)Fixed Issues - None. ### [](#known-issues-3)Known Issues - None. ## [](#6-7-0)6.7.0 **October 13, 2020**
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, Orlando and Paris (default)

OpenJDK

8 or 11
### [](#features-4)Features Added support for the ServiceNow `Paris` release. ### [](#fixed-issues-24)Fixed Issues - None. ### [](#known-issues-4)Known Issues - None. ## [](#6-6-1)6.6.1 **September 4, 2020**
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, and Orlando (default)

OpenJDK

8 and 11
### [](#features-5)Features Multiple libraries are updated to the latest versions. ### [](#fixed-issues-25)Fixed Issues - None. ### [](#known-issues-5)Known Issues - None. ## [](#6-6-0)6.6.0 **May 13, 2020**
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, New York, and Orlando (default)

JDK

8
### [](#features-6)Features This release contains the following new features and enhancements: - Support for the ServiceNow `Orlando` release - Support for using display value as a parameter - Multiple libraries were updated to the latest versions ### [](#fixed-issues-26)Fixed Issues - None. ### [](#known-issues-6)Known Issues - None. ## [](#6-5-0)6.5.0 **February 28, 2020**
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, and New York (default)

JDK

8
### [](#features-7)Features - Support for WS-Security 1.1 was added. - Support for OAuth 2.0 authentication was added. ### [](#fixed-issues-27)Fixed Issues - None ### [](#known-issues-7)Known Issues - Metadata does not work with the OAuth 2.0 connection. - The OAuth dance does not work with Mule 4.1.6. You must use Mule versions 4.1.5 or 4.2.1 and later. ## [](#6-4-1)6.4.1 **November 29, 2019**
Application/Service Version

Mule

4.1.1 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, and New York (default)

JDK

8
### [](#features-8)Features - None ### [](#fixed-issues-28)Fixed Issues - The issue with getting illegal XML characters in the payload when using a Windows operating system is fixed. - The issue with the connector not fetching metadata for the Service and Operation parameters is fixed. ## [](#6-4-0)6.4.0 **October 3, 2019**
Application/Service Version

Mule

4.1.0 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston, Madrid, and New York (default)

JDK

8
### [](#features-9)Features - Added support for the ServiceNow `New York` release. ## [](#6-3-0)6.3.0 July 2019
Application/Service Version

Mule

4.1.0 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, Kingston and Madrid — Default is Madrid

JDK

8
### [](#features-10)Features - Now supports the ServiceNow Madrid release. ## [](#6-2-2)6.2.2 **January 15, 2019**
Application/Service Version

Mule

4.1.0 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, and Kingston — Default is Kingston

JDK

8
### [](#fixed-issues-29)Fixed Issues - Fixed error in mapping on response of the connection. ## [](#6-2-1)6.2.1 **November 9, 2018**
Application/Service Version

Mule

4.1.0 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, and Kingston — Default is Kingston

JDK

8
### [](#fixed-issues-30)Fixed Issues - Fixed thread leakage. ## [](#6-2-0)6.2.0 **March 14, 2018**
Application/Service Version

Mule

4.0.0 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta, and Kingston — Default is Kingston

JDK

8
### [](#features-11)Features - The ServiceNow connector now supports the ServiceNow Kingston release. ### [](#fixed-issues-31)Fixed Issues - Fixed the test connectivity. ## [](#6-1-0)6.1.0 **December 22, 2017** ### [](#compatibility-33)Compatibility The ServiceNow connector 6.0.0 is compatible with:
Application/Service Version

Mule

4.0.0 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, Istanbul, Jakarta — Default is Jakarta

JDK

8
### [](#features-12)Features - Updated to support the ServiceNow Jakarta release. ## [](#6-0-0)6.0.0 **November 18, 2017** ServiceNow Connector is available on Mule 4.0. No new updates. ### [](#compatibility-34)Compatibility The ServiceNow connector 6.0.0 is compatible with:
Application/Service Version

Mule

4.0.0 and later

ServiceNow

Eureka, Fuji, Geneva, Helsinki, and Istanbul — Default is Istanbul

JDK

8
### [](#features-13)Features This version is compatible with Mule 4.0.0. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SFTP Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for SFTP (SFTP Connector) provides access to files and folders on an SFTP server. SFTP connector’s operations manage file transfers over the SFTP (Secure File Transfer Protocol) protocol. Guide: [SFTP Connector User Guide](https://docs.mulesoft.com/sftp-connector/latest/) ## [](#2-7-4)2.7.4 **September 21, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.19.0
### Fixed Issues
Issue Resolution ID

ClassCastException errors no longer occur when the On New or Updated File source polls after you upgrade the connector from version 1.x to version 2.x with watermarking enabled.

W-23034519

The connector now uses updated Apache Tika MIME-type mappings for content-type detection in SFTP file operations.

W-23965714
## [](#2-7-3)2.7.3 **August 18, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.19.0
### Fixed Issues
Issue Resolution ID

The Apache Mina SSHD version is upgraded to version 2.19.0 to address reported security vulnerabilities.

W-23725102, W-23860561
## [](#2-7-2)2.7.2 **July 23, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.17.1
### Fixed Issues
Issue Resolution ID

The connector now closes the previous SFTP connection when reconnecting to a server that has closed the SFTP channel while keeping the underlying SSH connection open. Previously, these orphaned connections accumulated on Mule runtime and were released only when the application restarted.

W-23339292
## [](#2-7-1)2.7.1 **May 6, 2026**
CloudHub 2.0 applications that use SFTP Connector versions earlier than 2.7.1 might not show their schedulers on the Runtime Manager Schedules tab because scheduler metadata can’t be generated for the application. This issue is more likely to occur when you build the application with a recent Mule Maven Plugin version. Upgrade to SFTP Connector 2.7.1 or later and redeploy the application.
### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.17.1
### Fixed Issues
Issue Resolution ID

The Read operation no longer incorrectly throws the SFTP:ACCESS_DENIED error when accessing files on servers that don’t report standard Unix permission bits. The connector now defers to server-side permission validation instead of pre-emptively denying access, allowing authorized users to access files on servers that rely on alternative permission models.

W-22335397

The connector now maintains a stable connection to SFTP servers during application redeployments when using Bouncy Castle as a security provider by correctly deregistering the provider during the disposal phase. Previously, redeploying an application in Anypoint Studio or a standalone runtime caused SFTP connection failures during public key authentication with a NoClassDefFoundError.

W-20879667
## [](#2-7-0)2.7.0 **April 21, 2026** ### What’s New - The connector now includes the new **Idle Timeout** and **Idle Timeout Unit** fields for the **SFTP Connection** type. Use these fields to specify the maximum duration an established connection can remain inactive without data exchange before it is automatically closed. For more information, refer to [SFTP Connection](https://docs.mulesoft.com/sftp-connector/latest/sftp-documentation#config_connection). ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.16.0
## [](#2-6-5)2.6.5 **March 25, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.16.0
### Fixed Issues
Issue Resolution ID

The connector now correctly processes subsequent files when the listener handles multiple files in a single cycle and no longer throws the org.apache.sshd.common.SshException: Channel is being closed error. Previously, after successfully processing the first file, the connector prematurely closed the connection, causing the stream for subsequent files to close.

W-21319993
## [](#2-6-4)2.6.4 **January 28, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.16.0
### Fixed Issues
Issue Resolution ID

SFTP Connector now has extra loggers.

W-20840374
## [](#2-6-3)2.6.3 **January 6, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.16.0
### Fixed Issues
Issue Resolution ID

The connector now uses the custom implementation for the file’s MIME-type detection instead of the Apache Tika dependency to address the CVE-2025-54988 and CVE-2025-66516 security vulnerabilities.

W-20499199
## [](#2-6-2)2.6.2 **December 19, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

The org.mule.runtime.api.exception.MuleRuntimeException: Exception found while consuming stream error no longer occurs when multiple SFTP listeners poll the same directory. Mule flows now run reliably and concurrently without interfering with each other’s underlying SFTP connections.

W-20203952, W-20232072

SFTP Connector no longer throws the SftpConnectionException error during application redeployment when using EdDSA identity files. The connector now correctly manages the registration and removal of the EdDSA security provider to prevent classloader conflicts and memory leaks between application deployments.

W-19111963
## [](#2-6-1)2.6.1 **November 11, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

The connector no longer throws an error that the client is closed when processing files from an SFTP server directory. For more information, see Intermittent “client is closed” Error with SFTP Connector.

W-19863871

The connector no longer has a connection leak when it polls a non-existent directory. For more information, see SFTP Connection Leak with "On New or Updated File" Source and Reconnect Strategy.

W-20134874
## [](#2-6-0)2.6.0 **October 24, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.14.0
### Fixed Issues
Issue Resolution ID

General security fixes and non-user impacting changes.

W-19867063
## [](#2-5-2)2.5.2 **October 10, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

The connector no longer throws the SSH_FX_NO_SUCH_FILE error and correctly handles SftpException during reconnection strategy for the Write operation.

W-19597549

The connector now supports the KEYBOARD_INTERACTIVE preferred authentication method again.

W-17956924
## [](#2-5-1)2.5.1 **August 19, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

The connector no longer uses high memory due to SFTP client thread leaks.

W-19282755

The connector no longer throws an SSH_FX_FAILURE error when you write a new file.

W-18988489

The connector no longer causes the pwd command to fail for certain servers.

W-16071743

The connector no longer throws an SSH_FX_NO_SUCH_PATH error when you write a new file.

W-17951986
## [](#2-5-0)2.5.0 **July 4, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

You can now adjust the value of the Response Timeout field to set the operation timeout value to accommodate slower or higher latency SFTP servers.

W-18284646
## [](#2-4-6)2.4.6 **June 30, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

The mule-sdk-api library is upgraded to version 0.7.5 because earlier versions do not include a <license> tag in the POM file.

W-18222885
## [](#2-4-5)2.4.5 **June 20, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

The connector no longer throws an error that the client is closed if there is no activity from the client side for more than 5 minutes.

W-18338461
## [](#2-4-4)2.4.4 **April 22, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.15.0
### Fixed Issues
Issue Resolution ID

The connector verifies user read access before reading the file.

W-17672899

The commons-collections:commons-collections:3.2.2 library is excluded and updated to org.apache.commons:commons-collections4:4.3 to address security vulnerabilities.

W-17637753
## [](#2-4-3)2.4.3 **March 7, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.13.2
### Fixed Issues This release includes only non-user-impacting changes. ## [](#2-4-2)2.4.2 **February 7, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.13.2
### Fixed Issues
Issue Resolution ID

The Write operation with CUSTOM_APPEND mode now works consistently for the CUSTOM_WRITE strategy.

W-17555345
## [](#2-4-1)2.4.1 **December 24, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.13.2
### Fixed Issues
Issue Resolution ID

The commons-io:commons-io library is upgraded to version 2.14.0 to address reported security vulnerabilities.

W-17368719

The org.json:json library is upgraded to version 20231013 to address reported security vulnerabilities.

W-14499233
## [](#2-4-0)2.4.0 **November 13, 2024** ### What’s New - The connector no longer supports the `KEYBOARD_INTERACTIVE` preferred authentication method. Use the `PUBLIC_KEY`, `PASSWORD`, or `GSSAPI_WITH_MIC` preferred authentication methods instead. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.13.2
### Fixed Issues
Issue Resolution ID

The Preferred Authentication Methods field no longer includes KEYBOARD_INTERACTIVE.

W-16765499
## [](#2-3-0)2.3.0 **September 23, 2024** ### What’s New - The connector has a new custom [Write strategy](https://docs.mulesoft.com/sftp-connector/latest/sftp-write#write-strategy) field that enables you to configure the strategy to write a file. Use this strategy only in `APPEND` mode particularly for old SFTP servers that do not follow the standard SFTP guidelines. Additionally, you can configure the buffer size to write the file in the **Buffer size for write strategy** field. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.13.2
### Fixed Issues
Issue Resolution ID

The connector no longer hangs while performing operations on Rebex TinySFTP servers.

W-14051911

The connector now has a new custom Write strategy field that supports the append issues in the Globalscape and Titan SFTP Servers.

W-15124410

The connector no longer evicts an active connection when processing a huge file.

W-16342066

The connector no longer logs the Unknown channel request: keepalive@openssh.com warning when debug mode is disabled.

W-16750435

The connector no longer throws a null pointer exception during resource release when an exception occurs in the flow.

W-16645502
## [](#2-2-2)2.2.2 **August 26, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

The connector no longer has thread leaks when connections fail.

W-15259057
## [](#2-2-1)2.2.1 **August 13, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

The connector no longer incorrectly throws a connection timeout error.

W-15437508
## [](#2-2-0)2.2.0 **July 12, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

The SFTP filename attribute is now consistent between the payload and its transformation to JSON.

W-15717354
## [](#2-1-4)2.1.4 **July 2, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

Removed unnecessary dependency reducing the overall size of the Mule app that includes the SFTP Connector.

W-16134781
## [](#2-1-3)2.1.3 **June 18, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

SFTP Connector now throws the SftpConnectionException message to cover missing cases of errors, such as connection refused and connection reset by peer.

W-14987667, W-15890258

Resolved memory leak issues related to classloader usage, which also addresses application deletion failures on Windows systems for Java versions 11 and 17.

W-15988716
## [](#2-1-2)2.1.2 **May 30, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

SFTP Connector now creates a new file in append mode if the file does not exist.

W-15291302

SFTP Connector now appends content at the end of the file in append mode.

W-15294043
## [](#2-1-1)2.1.1 **May 29, 2024** ### What’s New - SFTP Connector now supports external security configurations through a configuration file. You can configure this file in the **Advanced** tab of the connector configuration, which supports the following settings: - `KexAlgorithms` Specifies comma separated list of Key Exchange algorithms - `Ciphers` Specifies comma separated list of the symmetric Ciphers - `HostKeyAlgorithms` Specifies comma separated list of Host Key Signature algorithms - `MACs` Specifies comma separated list of Message Authentication Codes Because you control this configuration file, it may introduce an additional security risk. Therefore, configuring security settings using this file means you accept the [shared responsibilities](https://docs.mulesoft.com/connectors/introduction/connectors-shared-responsibilities) documentation. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

The Key Negotiation feature is working as expected now with legacy SFTP servers.

W-14557165
## [](#2-1-0)2.1.0 **May 14, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. - To make the connector FIPS 140-2 compliant, the `net.i2p.crypto:eddsa:0.3.0` EdDSA library is removed from the connector artifact and the related algorithms are no longer available by default. If needed, add the EdDSA library as an external library to the connector configuration to use the EdDSA library if FIPS 140-2 compliance is not required. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
## [](#2-0-7)2.0.7 **March 05, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.12.1
### Fixed Issues
Issue Resolution ID

Upgraded Apache Mina version.

W-15081128

Added support to strict key feature to mitigate Terrapin Attack.

W-14875716

Improved logging on "On New or Updated File" operation.

W-15003430
## [](#2-0-6)2.0.6 **February 27, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.10.0
### Fixed Issues
Issue Resolution ID

SFTP Connector now closes the SSH client when the login fails. Additionally, there are new null pointer exception checks at connection time and new logging actions to see errors.

W-14571055
## [](#2-0-5)2.0.5 **February 20, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.10.0
### Fixed Issues
Issue Resolution ID

SFTP Connector now connects to the SFTP client through a proxy with HTTP and SOCK5 protocols.

W-14165289, W-14317632, W-14317577

SFTP File attributes now have null values validation.

W-14571847

SFTP Connector now redeploys successfully when using EdDSA identity files.

W-14492587
## [](#2-0-4)2.0.4 **January 26, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.10.0
### Fixed Issues
Issue Resolution ID

The SFTP Connector Write operation with the parameter Overwrite enabled now works correctly with SFTP servers.

W-14412871
## [](#2-0-3)2.0.3 **January 9, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.3.0 and later

OpenJDK

8, 11, and 17

Apache Mina SSHD

2.10.0
## [](#2-0-2)2.0.2 **December 28, 2023** ### Compatibility
Software Version

Mule

4.1.5 and later

OpenJDK

8 and 11

Apache Mina SSHD

2.10.0
### Fixed Issues
Issue Resolution ID

The On New or Updated File source now supports multiple files concurrently.

W-14203139
## [](#2-0-1)2.0.1 **October 6, 2023** ### Compatibility
Software Version

Mule

4.3.0 and later

JDK

8

Apache Mina SSHD

2.10.0
### Fixed Issues
Issue Resolution ID

The SFTP Connector Write operation now responds correctly.

W-14051911
## [](#2-0-0)2.0.0 **Aug 17, 2023** ### What’s New - SFTP Connector 2.0.0 no longer supports the `jcraft JSCH` library. The connector now uses the `Apache Mina SSHD` library. - The **List** operation no longer fetches the content of each file. Now, the payload of each list item contains the complete path to the found file or directory. - The connector no longer uses the `mule.sftp.useHomeDirectory` system property. SFTP Connector now uses the default home directory. - The SFTP **Regular Size** file attribute is renamed to **Regular File**, because its behavior is not related to size. The file attribute value is a file (`true`) or a directory (`false`). - SFTP Connector 2.0.0 does not support ciphers `3des-ctr` and `arcfour`. For more information, refer to [Supported Ciphers](https://docs.mulesoft.com/sftp-connector/latest/sftp-connector-upgrade-guide#supported-ciphers). - The SFTP proxy protocol works only with HTTP and SOCKS5. SOCKS4 support is not supported. - SFTP Connector no longer uses `javax.activation` to resolve the media types of the files. The connector now uses `Apache Tika`, which can result in different media file interpretations. - The connector changed the classes to manage the date from `LocalDateTime` to `ZonedDateTime`. - The deprecated **Encoding** parameter in the configuration and **Write** operation is removed. The connector uses Mule’s default encoding. ### Compatibility
Software Version

Mule

4.3.0 and later

JDK

8

Apache Mina SSHD

2.9.2
## [](#1-6-3)1.6.3 **December 8, 2023** ### Compatibility
Software Version

Mule

4.1.2 and later

JDK

8

JSCH libraries

0.1.55
### Fixed Issues
Issue Resolution ID

The org.mule.modules:mule-module-file-extension-common library is upgraded to version 1.4.3.

W-14535257
## [](#1-6-2)1.6.2 **Sep 18, 2023** ### Compatibility
Software Version

Mule

4.1.2 and later

JDK

8

JSCH libraries

0.1.55
### Fixed Issues
Issue Resolution ID

The SFTP Connector connection no longer breaks when a timeout exception is thrown.

W-13769562
## [](#1-6-1)1.6.1 **Dec 15, 2022** ### Compatibility
Software Version

Mule

4.1.2 and later

JDK

8

JSCH libraries

0.1.55
### Fixed Issues
Issue ID

SFTP Connector no longer has a memory leak when the session is not closed due to an error opening a channel.

W-12098169
## [](#1-6-0)1.6.0 **Aug 30, 2022** ### Compatibility
Software Version

Mule

4.1.2 and later

JDK

8
### Fixed Issues
Issue ID

The On New or Updated File operation now provides the Overwrite field, which enables you to overwrite the target file when the destination file has the same name.

W-11645847
## [](#1-5-1)1.5.1 **August 17, 2022** ### Compatibility
Software Version

Mule

4.1.2 and later
### Fixed Issues
Issue ID

SFTP Connector now supports the mule.sftp.useHomeDirectory system property, which you can set to true to use the default home directory. Previously, SFTP Connector did not use the default home directory when the working directory was not configured.

W-10673625
## [](#1-5-0)1.5.0 **June 29, 2022** ### What’s New - SFTP Connector now supports an independent file system matcher that lists files following SFTP RTF standards. Use the **Case sensitive** field to configure an external file system matcher as case sensitive or insensitive. ### Compatibility
Software Version

Mule

4.1.2 and later
### Fixed Issues
Issue ID

SFTP Connector no longer fails when a file name contains :.

W-10678323
## [](#1-4-1)1.4.1 **October 15, 2021** ### What’s New - Added more error and debug level logging information. ### Compatibility
Software Version

Mule

4.1.2 and later
### Fixed Issues
Issue ID

SFTP Connector On New or Updated File operation did not reconnect.

SE-22668
## [](#1-4-0)1.4.0 **April 6, 2021** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.2** ### [](#fix-issues)Fix issues - Fixed an issue where the SFTP Connector threw a `MULE:CONNECTIVITY` exception instead of an `SFTP:CONNECTIVITY` exception for all the operations (SE-19522). ## [](#1-3-10)1.3.10 **September 30, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.2** ### [](#fix-issues-2)Fix issues - SFTP Connector now throws an `SFTP:ACCESS_DENIED` Mule error code instead of a `MULE:UNKNOWN` code if the connector does not have the required permissions to read from or write to a file (SE-16476). - Improved error handling for the **Write** operation. SFTP Connector now throws an `SFTP:FILE_DOESNT_EXIST` Mule error code instead of a `MULE:UNKNOWN` code (SE-15186). ## [](#1-3-9)1.3.9 **September 2, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issue)Fixed Issue - Fixed an issue in which the reconnection strategy did not re-establish the connection to the SFTP server when performing the Directory Listing Operation (SFTPC-51). ## [](#1-3-8)1.3.8 **July 15, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issue-2)Fixed Issue Lock not released after write operation is successful (SFTPC-47). ## [](#1-3-7)1.3.7 **March 10, 2020** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issue-3)Fixed Issue - MULE-18163: Verifying root folder resulted in exception when using default working directory. (MULE-18163) ## [](#1-3-6)1.3.6 **February 26, 2020** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issue-4)Fixed Issue - Avoid CD operation when working directory is not set (MULE-18058) ## [](#1-3-5)1.3.5 **February 13, 2020** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issue-5)Fixed Issue - Fixed issue that caused connector fails to authenticate when using ECDSA algorithm with key size of 384 and 521 bits. (MULE-18061) ## [](#1-3-4)1.3.4 **December 17, 2019** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issues-42)Fixed Issues - The issue that made SFTP Connector fail to recognize connection issues as such on certain cases is fixed. (MULE-17854) - The issue that made it impossible to rename a file without moving it using the listener POST action is fixed. (MULE-17836) ## [](#1-3-3)1.3.3 **December 2, 2019** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issues-43)Fixed Issues The issue that made some operations throw a `MULE:UNKNOWN` error when the configured working directory did not exist is fixed. (MULE-17731) ## [](#1-3-2)1.3.2 **September 25, 2019** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issues-44)Fixed Issues - Fixed an issue where the **Write** operation was throwing a `MULE:UNKNOWN` error instead of an `SFTP:ILLEGAL_PATH` error. (MULE-17482) - Fixed an issue where the SFTP **Listener** operation was trying to release connections that were never obtained. (MULE-17491) - Fixed a bug where the SFTP Connector was unable to dispose of an invalid connection. (MULE-17494) ## [](#1-3-1)1.3.1 **September 11, 2019** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.2** ### [](#fixed-issues-45)Fixed Issues - Fixed a bug that made the write operation fail to write big files on certain servers. (MULE-17395) ## [](#1-3-0)1.3.0 **September 6, 2019** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.2** ### [](#features)Features The parameters **Updated in the last**, **Not updated in the last**, and **Time unit** are added to the **File Matching Rules**. These parameters enable you to have a List or Listener operation to filter files based on when they were last updated. ### [](#fixed-issues-46)Fixed Issues - The issue where the read operation took more than one connection to read the file content is fixed. (MULE-17316) - The issue where if you were using the latest version of the SFTP connector with older versions of the File, FTP and FTPS connectors, those connectors failed to work correctly is fixed. (MULE-17404) ## [](#1-2-6)1.2.6 **August 14, 2019** ### [](#minimum-mule-version-13)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-47)Fixed Issues Windows apps failed if the path contained a colon character (:) in the FTP server. (MULE-17064) ## [](#1-2-5)1.2.5 **July 1, 2019** ### [](#minimum-mule-version-14)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-48)Fixed Issues - Libraries that may contain vulnerabilities were updated. (MULE-16747) - Fixed a bug that made the time between a size check not behave as expected when the time unit was not milliseconds. (MULE-17004) ## [](#1-2-4)1.2.4 **November 20, 2018** ### [](#minimum-mule-version-15)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-49)Fixed Issues Mule 4 SFTP connection pooling is not working correctly. (MULE-16018) ## [](#1-2-3)1.2.3 **October 23, 2018** ### [](#minimum-mule-version-16)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-50)Fixed Issues - SFTP Connector listener may skip a file given a special configuration. (MULE-15852) ## [](#1-2-2)1.2.2 **July 19, 2018** ### [](#minimum-mule-version-17)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-51)Fixed Issues SFTP Connector must not close the connection in a Paging Provider. (MULE-15354) ## [](#1-2-1)1.2.1 **June 26, 2018** ### [](#minimum-mule-version-18)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-52)Fixed Issues - Change in behavior of the SFTP connector for Mule 4 with regard to directory paths. (MULE-15173) - SFTP authentication methods displayed incorrectly / missing (MULE-15185) - SFTP is not reconnecting after experiencing a disconnect (MULE-15196) ## [](#1-2-0)1.2.0 **May 7, 2018** ### [](#minimum-mule-version-19)Minimum Mule Version **Mule 4.1.0** ### [](#features-2)Features - You can make use of timeBetweenSizeCheck to prevent the connector from processing files while they are being written. - Fixed an issue that happened when using a filter by filenamePattern, failing to search files recursively in folders. ### [](#fixed-issues-53)Fixed Issues - Add CustomSftpLogger for JSCh. (MULE-14738) - SFTP getting partial file. (MULE-14824) - SFTP Connector does not check for files recursively if a filenamePattern is given. (MULE-14863) ## [](#1-1-2)1.1.2 **March 14, 2018** ### [](#minimum-mule-version-20)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-54)Fixed Issues Connectors do not communicate correctly if their POJOs properties are nullable or not. (MULE-14701) ## [](#1-1-1)1.1.1 **February 02, 2018** ### [](#fixed-issues-55)Fixed Issues sftp:listener has an undescriptive display name. (MULE-14589) ## [](#1-1-0)1.1.0 **January 19, 2018** ### [](#features-3)Features This release includes the following enhancements, changes, and fixes: Added a message source that automatically polls for new files, while handling clustering, idempotency, post actions, and watermark automatically. ### [](#upgrade-requirements)Upgrade Requirements Mule 4.1 ### [](#fixed-issues-56)Fixed Issues SFTP connectors exports internal classes. (MULE-14496) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SharePoint Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for SharePoint (SharePoint Connector) enables you to connect to the Microsoft SharePoint application. The connector exposes convenient methods to work with the Microsoft SharePoint API. Guide: [SharePoint Connector User Guide](https://docs.mulesoft.com/sharepoint-connector/latest/) ## [](#3-10-0)3.10.0 **September 23, 2026** ### What’s New - The [**OAuth Client Credentials**](https://docs.mulesoft.com/sharepoint-connector/latest/sharepoint-connector-reference#sharepoint-online_oauth-client-credentials) connection type now includes a [**TLS Context**](https://docs.mulesoft.com/sharepoint-connector/latest/sharepoint-connector-reference#Tls) field. Use **TLS Context** when you request an OAuth token through a TLS-inspecting proxy or when the token endpoint presents a certificate that the JVM default truststore doesn’t trust. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The OAuth Client Credentials connection type now sends OAuth token requests through the configured proxy.

W-24199249
## [](#3-9-1)3.9.1 **August 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

IllegalArgumentException errors no longer occur when the connector re-initializes a dynamic configuration that uses the OAuth Client Credentials connection type.

W-23683159

These libraries are upgraded to address reported security vulnerabilities:

  • The jersey-common library is upgraded to version 2.48.

  • The java-jwt library is upgraded to version 4.6.0.

  • The javassist library is upgraded to version 3.32.0-GA.

W-23441723

The commons-lang 2.4 library is removed to address the CVE-2025-48924 security vulnerability.

W-23559068
## [](#3-9-0)3.9.0 **June 22, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-22472089
## [](#3-8-2)3.8.2 **May 1, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now correctly classifies HTTP 400 (Bad Request) errors and throws the SHAREPOINT:INVALID_PARAMETERS error when malformed request parameters or invalid URLs are detected. Previously, the connector misclassified these data validation failures as SHAREPOINT:CONNECTIVITY.

W-22096311
## [](#3-8-1)3.8.1 **March 18, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector with OAuth Client Credentials connection type no longer throws an intermittent NullPointerException during connection re-establishment under concurrent request conditions.

W-21572883

The jackson-core library is upgraded to version 2.18.6 to address reported security vulnerabilities.

W-21579558
## [](#3-8-0)3.8.0 **January 30, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-20966408
## [](#3-7-3)3.7.3 **January 7, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The OAuth Client dependency version is changed to 0.8.0.

W-20642427

The connector no longer throws an intermittent NullPointerException when a pagination response has an empty result.

W-20241067

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to 2.16.0.

  • The modelmapper library is upgraded to 2.4.5.

  • The jcifs library is upgraded to 1.3.19.

  • The commons-io library is upgraded to 2.15.0.

  • The commons-lang3 library is upgraded to 3.18.0.

W-20241067
## [](#3-7-2-deprecated)3.7.2 (Deprecated) **December 9, 2025** ### Fixed Issues The features and fixed issues for this version are in version 3.7.3. ## [](#3-7-1)3.7.1 **June 11, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The List Item Query operation now correctly applies the $top parameter when specified in the query string, limiting results to the requested number of items instead of returning all items.

W-18142298

The connector no longer throws an intermittent NullPointerException during connection re-establishment.

W-18625193
## [](#3-7-0)3.7.0 **April 1, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17441445

In the OAuth Client Credentials connection type, the Keystore type field now includes BCFKS.

W-17441445

All operations can now throw the SHAREPOINT:SECURITY error.

W-17441445

The List Item Query operation now handles null values in the list.

W-17757864
## [](#3-6-2)3.6.2 **June 12, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector connection is now improved and remains stable even during extended runs.

W-15274457
## [](#3-6-1)3.6.1 **February 20, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The On New Objects source no longer fails if the SharePoint table does not have a Unique Id field.

W-14395943
## [](#3-6-0)3.6.0 **January 18, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The OAuth Client Credentials connection type now includes the new Key password field.

W-13744963

The socket, connection, and request timeouts are now set to 120 seconds.

W-14632137
## [](#3-5-2)3.5.2 **September 22, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

PDF file content now downloads correctly.

W-13966224

XLSX file content now downloads correctly.

W-14145039
## [](#3-5-1)3.5.1 **June 15, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The OAuth Client Credentials connection now correctly refreshes the access token.

W-13543543

The On Deleted Objects source now detects all deleted items.

W-13585587
## [](#3-5-0)3.5.0 **May 3, 2023** ### What’s New - The connector now supports OAuth Client Credentials with Certificate authentication. ### Compatibility
Application/Service Version

Mule

4.1.1 and later
## [](#3-4-7)3.4.7 **October 11, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853435
## [](#3-4-6)3.4.6 **September 8, 2022** ### What’s New - The `org.jsoup` library is upgraded to version 1.15.3 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The org.jsoup library is upgraded to version 1.15.3 to address reported security vulnerabilities.

W-11662366
## [](#3-4-5)3.4.5 **June 29, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The connector now uses the refresh token to retry the operation when there is an invalid token in the OAuth v2.0 Authorization Code connection.

W-11298719

The connector no longer contains a memory leak.

W-11335726
## [](#3-4-4)3.4.4 **June 14, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The Test connection button no longer returns a Test connection successful message when providing invalid values for the NTLM connection type in the SharePoint On-premises configuration.

W-11237136
## [](#3-4-3)3.4.3 **May 27, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The File Move operation now processes more than five files.

W-11153962
## [](#3-4-2)3.4.2 **April 5, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The sources now pick up all objects.

W-10839353
## [](#3-4-1)3.4.1 **January 18, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.12.6 to address security vulnerabilities.

CONN-9850

Changed the logger level of the connector from ERROR to WARN.

SE-23901

Updated annotations with semantic terms.

CONN-9958
## [](#3-4-0)3.4.0 **January 12, 2022** ### What’s New - Added the `SHAREPOINT:NOT_FOUND` error type. ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Removed Atlantic Commons and improved the exception handling layer.

CONN-8871
## [](#3-3-2)3.3.2 **November 18, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The connector threw a NullPointerException when using the TaxCatchAll hidden field for a metadata item.

SE-23268

When using special characters, the List Item Query operation returned a different output than expected.

SE-23435
## [](#3-3-1)3.3.1 **September 28, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Fixed all reported vulnerabilities.

CONN-8746

Deployment failed with Code Grant Authorization.

SE-22645

List Item Query threw an error when using a file with a special character.

SE-22490
## [](#3-3-0)3.3.0 **August 17, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The connector returned a SHAREPOINT:UNKNOWN error when a SocketException was thrown instead of a SHAREPOINT:CONNECTIVITY error.

SE-21002
## [](#3-2-3)3.2.3 **June 29, 2021** ### [](#compatibility-27)Compatibility
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-27)Fixed Issues - Fixed a query language ClassCastException error. ## [](#3-2-2)3.2.2 **May 13, 2021** ### [](#compatibility-28)Compatibility
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-28)Fixed Issues - Fixed the reported vulnerabilities for the connector. ## [](#3-2-1)3.2.1 **April 27, 2021** ### [](#compatibility-29)Compatibility
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-29)Fixed Issues - The security token connection was deprecated starting with version 3.1.4, but it was missing an explicit reference in Studio. This release improves the description of the Security Token connection by adding the `DEPRECATED` label. ## [](#3-2-0)3.2.0 **March 30, 2021** ### [](#compatibility-30)Compatibility
Application/Service Version

Mule

4.1.1 and later
### [](#features)Features - Added the OAuth Authorization Code grant connection provider, which can be used as an option for SharePoint online configuration. - Added the **Move File** operation, which is used to move and rename files within Microsoft SharePoint. ## [](#3-1-13)3.1.13 **January 12, 2021** ### [](#compatibility-31)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-30)Fixed Issues Fixed all reported vulnerabilities. ## [](#3-1-12)3.1.12 **October 27, 2020** ### [](#compatibility-32)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-31)Fixed Issues Fixed the problem that occured when using the $top paramater in a query (SE-17853). ## [](#3-1-11)3.1.11 **September 9, 2020** ### [](#compatibility-33)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-32)Fixed Issues Fixed an Apache Commons IO vulnerability. ## [](#3-1-10)3.1.10 **August 27, 2020** ### [](#compatibility-34)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-33)Fixed Issues Incorrect content appeared when using the File get content operation. (SE-16897 and SE-17362) ## [](#3-1-9)3.1.9 **August 21, 2020** ### [](#compatibility-35)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-34)Fixed Issues The issue that caused a `String index out of range` error when a connection configuration was incorrect is fixed. (SE-16607) ## [](#3-1-8)3.1.8 **July 7, 2020** ### [](#compatibility-36)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-35)Fixed Issues Fixed security vulnerabilities for the connector. ## [](#3-1-7)3.1.7 **Jun 25, 2020** ### [](#compatibility-37)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-36)Fixed Issues Fixed reported vulnerabilities for the connector. ## [](#3-1-6)3.1.6 **June 11, 2020** ### [](#compatibility-38)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-37)Fixed Issues The `Modified objects` input source with recursive mode enabled did not work on folders that had a large volume of files. (SE-15656) The connector now performs one request only to get the needed information when you do the following: - Use the `New objects` or `Modified objects` input source - Set `Object type` to `FILE` - Enable recursive mode - Provide a value for `list id` This new functionality improves the execution time, especially when the operations create or modify complex document libraries or hierarchies. ## [](#3-1-5)3.1.5 **May 26, 2020** ### [](#compatibility-39)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-38)Fixed Issues - Upgraded the following dependencies to fix vulnerability issues (CONN-6024): - `commons-codec:commons-codec:1.10` to `commons-codec:commons-codec:1.13` - `com.google.guava:guava:18.0` to `com.google.guava:guava:28.1-jre` - `org.springframework:spring-expression:4.1.9.RELEASE` to `org.springframework:spring-expression:5.2.3.RELEASE` - `com.fasterxml.jackson.core:jackson-databind:2.9.3` to `com.fasterxml.jackson.core:jackson-databind:2.10.2` - `com.sun.xml.bind:jaxb-impl:2.3.0` to `com.sun.xml.bind:jaxb-impl:2.3.2` - To fix vulnerability issues, `Log4j:log4j:1.2.17` was replaced with `commons-logging:commons-logging:1.2` ## [](#3-1-4)3.1.4 **December 19, 2019** ### [](#compatibility-40)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-39)Fixed Issues - The File Add operation did not work properly. (SE-14053) - Deprecated the Security Token Provider because it is no longer needed. The Basic Authentication mechanism obtains the security token and is easier to use. For SAML access, you can obtain a [security token from SharePoint](https://docs.mulesoft.com/sharepoint-connector/latest/#security-token-authentication). ## [](#3-1-3)3.1.3 **July 17, 2019** ### [](#compatibility-41)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#features-2)Features - An optional parameter named **Path** is now available for the **Created objects** and **Modified objects** triggers. Use this parameter to specify the root path to start querying for when the object type is `FILE` or `FOLDER`. The **Path** parameter is ignored for other object types. - The default value for the **Since** field of the **Created objects**, **Modified objects** and **Deleted objects** triggers now formats the current time in UTC format rather than defaulting to the time on the machine running the Mule application. ### [](#fixed-issues-40)Fixed Issues Not possible to use $top parameter for retrieve-collection. (SE-12212) ## [](#3-1-2)3.1.2 **July 2, 2019** ### [](#compatibility-42)Compatibility The SharePoint connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-41)Fixed Issues Error produced when using a payload with é (e with accent) in the connector. (SE-11852) ## [](#3-1-1)3.1.1 **October 5, 2018** ### [](#compatibility-43)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#fixed-issues-42)Fixed Issues When doing a Select Item Query the connector threw NullPointerException. The problem was solved by parsing the query provided by the client. ## [](#3-1-0)3.1.0 **May 10, 2018** Sharepoint Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later
### [](#features-3)Features: Implemented triggers for created, deleted and updated objects. The triggers are New Objects Trigger, Deleted Objects Trigger, Modified Objects Trigger. ## [](#3-0-0)3.0.0 **January 19, 2018** ### [](#compatibility-44)Compatibility SharePoint Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Shippo Connector Release Notes Anypoint Connector for Shippo (Shippo Connector) enables Mule applications to access the Shippo API. Guide: [Shippo Connector User Guide](https://docs.mulesoft.com/shippo-connector/latest/) ## [](#0-1-24)0.1.24 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-23)0.1.23 **August 19, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-22)0.1.22 **June 30, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **December 16, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/shippo-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [Shippo Connector User Guide](https://docs.mulesoft.com/shippo-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
## [](#see-also)See Also - [Shippo Connector User Guide](https://docs.mulesoft.com/shippo-connector/latest/) - [Shippo Connector Reference](https://docs.mulesoft.com/shippo-connector/latest/shippo-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # ShipStation Connector Release Notes Anypoint Connector for ShipStation (ShipStation Connector) enables Mule applications to access the ShipStation API. Guide: [ShipStation Connector User Guide](https://docs.mulesoft.com/shipstation-connector/latest/) ## [](#1-0-7)1.0.7 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-1)0.1.1 **July 1, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **January 6, 2026** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/shipstation-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [ShipStation Connector User Guide](https://docs.mulesoft.com/shipstation-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#see-also)See Also - [ShipStation Connector User Guide](https://docs.mulesoft.com/shipstation-connector/latest/) - [ShipStation Connector Reference](https://docs.mulesoft.com/shipstation-connector/latest/shipstation-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Shopify Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Shopify (Shopify Connector) gives you access to the Shopify platform. This connector exposes operations provided by the Shopify REST Admin API. Guide: [Shopify Connector User Guide](https://docs.mulesoft.com/jp/shopify-connector/latest/) ## [](#1-1-14)1.1.14 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Shopify REST Admin API

v.2026-01
## [](#1-1-13)1.1.13 **August 14, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Shopify REST Admin API

v.2026-01
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core, jackson-databind, and jackson-datatype-jsr310 libraries are upgraded to version 2.22.1.

  • The json library is upgraded to version 20260719.

  • The commons-collections4 library is upgraded to version 4.6.0.

W-23795889
## [](#1-1-12)1.1.12 **July 2, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Shopify REST Admin API

v.2026-01
### Fixed Issues
Issue Resolution ID

The jackson and jackson-databind libraries are upgraded to version 2.22.0 to address reported security vulnerabilities.

W-23136407
## [](#1-1-11)1.1.11 **February 26, 2026** ### What’s New - The connector is now compatible with Shopify REST Admin API v2026-01. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Shopify REST Admin API

v.2026-01
## [](#1-1-10)1.1.10 **January 31, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The json library is upgraded to version 20250517.

  • The jackson-core library is upgraded to version 2.20.0.

  • The jackson-databind library is upgraded to version 2.20.0.

  • The commons-collections version 3.2.2 library is upgraded to commons-collections4 version 4.5.0.

W-20970382
## [](#1-1-9)1.1.9 **March 26, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Shopify REST Admin API

v.2021-10
## [](#1-1-8)1.1.8 **June 26, 2023** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue Resolution ID

Package conflicts no longer occur when using this connector with other specific connectors in a project.

W-13311688
## [](#1-1-7)1.1.7 **October 20, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.13.4.2 to address reported security vulnerabilities.

W-10920464
## [](#1-1-6)1.1.6 **September 27, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

The watermarking in the sources now works as intended.

W-11731709
## [](#1-1-5)1.1.5 **August 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

The limit field in the Product List operation now works as intended.

W-11221402
## [](#1-1-4)1.1.4 **April 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920464
## [](#1-1-3)1.1.3 **March 3, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

Upgraded library dependencies.

W-10733880
## [](#1-1-2)1.1.2 **January 18, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.13.1 to address security vulnerabilities.

CONN-9830

Fixed the customer-test-suite MUnit test.

N/A
## [](#1-1-1)1.1.1 **December 22, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9686
## [](#1-1-0)1.1.0 **December 16, 2021** ### What’s New - Added the following new sources: - **On updated customer trigger** - **On updated order trigger** - **On updated product trigger** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9561
## [](#1-0-0)1.0.0 **October 18, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Shopify Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11

Shopify REST Admin API

v.2021-10
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Siebel Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) The Anypoint Connector for Siebel allows you to create connections to Oracle’s Siebel customer relationship manager (CRM) from a Mule application. The connector comprises three modules that together form a single connection to these objects: - Oracle Siebel Business Objects: Create, update, upsert, query, and delete Siebel business components. - Oracle Siebel Integration Objects: Create, update, upsert, query, delete, query page, execute, and synchronize Siebel integration objects. - Oracle Siebel Business Services: Execute Siebel business services. Guide: [Siebel Connector User Guide](https://docs.mulesoft.com/jp/siebel-connector/latest/) ## [](#4-0-12)4.0.12 **September 20, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Siebel Java Provider

10.0.0

Siebel

IP18, IP19, IP20, IP21, and IP22

OpenJDK

8, 11, and 17
## [](#4-0-11)4.0.11 **August 30, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Siebel Java Provider

10.0.0

Siebel

IP18, IP19, IP20, IP21, and IP22

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-lang3 library is upgraded to version 3.20.0 to address reported security vulnerabilities.

W-23441724
## [](#4-0-10)4.0.10 **March 11, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Siebel Java Provider

10.0.0

Siebel

IP18, IP19, IP20, IP21, and IP22

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now throws connectivity errors when a connection timeout occurs.

W-17669266
## [](#4-0-9)4.0.9 **August 12, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Siebel Java Provider

10.0.0

Siebel

IP18, IP19, IP20, IP21, and IP22

OpenJDK

8, 11, and 17
## [](#4-0-8)4.0.8 **April 1, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Siebel Java Provider

10.0.0

Siebel

IP18, IP19, IP20, IP21, and IP22

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Removed the atlantic-commons dependency.

W-10889948
### Known Issues
Known Issue Workaround ID

IP21 only: Metadata does not work for the Create Business Component, Query Business Components, and Update Business Component operations.

N/A

N/A
## [](#4-0-7)4.0.7 **February 26, 2021** ### [](#compatibility-6)Compatibility Siebel connector 4.0.7 is compatible with:
Application/Service Version

Mule

4.1.1 and later

Siebel

IP18, IP19, and IP20
### [](#features)Features Configuration of Siebel load balancing is now supported. (SE-18970) ### [](#fixed-issues-4)Fixed Issues The Siebel connectivity tests were fixed. (SE-18970) ## [](#4-0-6)4.0.6 **November 20, 2020** ### [](#compatibility-7)Compatibility Siebel connector 4.0.6 is compatible with:
Application/Service Version

Mule

4.1.1 and later

Siebel

IP18, IP19, and IP20
### [](#features-2)Features The connector now supports Siebel IP20. ## [](#4-0-5)4.0.5 **September 2, 2020** ### [](#compatibility-8)Compatibility Siebel connector 4.0.5 is compatible with:
Application/Service Version

Mule

4.1.1 and later

Siebel

IP18 and IP19
### [](#fixed-issues-5)Fixed Issues - Fixed the connector to work with IP19 instances that were set up with runtime repositories or development repositories. (SE-16821) **November 5, 2019** ### [](#compatibility-9)Compatibility Siebel connector 4.0.4 is compatible with:
Application/Service Version

Mule

4.1.1 and later

Siebel

IP18 and IP19
### [](#fixed-issues-6)Fixed Issues - Fixed the Siebel metadata for the Attachment object and the Business Integration Category. (CONN-3420) ### [](#features-3)Features You can now log all of the input and output from the SiebelDataBean. ## [](#4-0-3)4.0.3 **September 23, 2019** ### [](#compatibility-10)Compatibility Siebel connector 4.0.3 is compatible with:
Application/Service Version

Mule

4.1.1 and later

Siebel

IP18 and IP19
### [](#fixed-issues-7)Fixed Issues - Added a **Synchronized calls** checkbox in the configuration. Enable it if making multiple calls at the same time results in error messages from Siebel. (SE-13188) ## [](#4-0-2)4.0.2 **September 16, 2019** ### [](#compatibility-11)Compatibility Siebel connector 4.0.2 is compatible with:
Application/Service Version

Mule

4.1.1 and later

Siebel

IP18 and IP19
### [](#fixed-issues-8)Fixed Issues - Password was removed from the error popup when Test Connection failed. (CONN-2859) ## [](#4-0-1)4.0.1 **May 29, 2019** ### [](#compatibility-12)Compatibility Siebel connector 4.0.1 is compatible with:
Application/Service Version

Mule

4.1.1 and later

Siebel

IP18 and IP19
### [](#fixed-issues-9)Fixed Issues - Metadata for Business Services was fixed. The connector now generates the correct metadata for lists of objects. ## [](#4-0-0)4.0.0 **November 18, 2017** ### [](#compatibility-13)Compatibility Siebel connector 4.0.0 is compatible with:
Application/Service Version

Mule

4.0.0 and later

Siebel

8.1 and later
### [](#features-4)Features This connector now is a conglomerate of the previous 3 modules (Oracle Siebel Business Objects, Oracle Siebel Integration Objects, Oracle Siebel Business Services). ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Slack Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Slack (Slack Connector) gives you access to the Slack platform. This connector exposes operations provided by the Slack API. Visit the [official Slack site](https://slack.com/help/articles/115004071768-What-is-Slack-) to learn more. Guide: [Slack Connector User Guide](https://docs.mulesoft.com/jp/slack-connector/latest/) ## [](#2-0-3)2.0.3 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#2-0-2)2.0.2 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.2.

  • The Google Guava library is upgraded to version 33.6.0-jre.

W-23848672
## [](#2-0-1)2.0.1 **March 20, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-text library is upgraded to version 1.15.0.

  • The guava library is upgraded to version 33.5.0-jre.

  • The jackson library is upgraded to version 2.21.1.

  • The json library is upgraded to version 20251224.

W-21506502

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21602195
## [](#2-0-0)2.0.0 **March 2, 2025** ### What’s New - This connector no longer has the **Upload File** operation because the Slack `files.upload` API method is deprecated. For more information, refer to the [Slack API documentation](https://docs.slack.dev/reference/methods/files.upload/). - To upload files, this connector now includes the new **Get upload url** and **Complete Upload External** operations. For more information about the operations, refer to [Get Upload URL](https://docs.mulesoft.com/jp/slack-connector/latest/slack-connector-reference#GetFilesUploadUrl) and [Complete Upload External](https://docs.mulesoft.com/jp/slack-connector/latest/slack-connector-reference#CreateFilesCompleteuploadExternal). For examples about how to use these operations, refer to [Upload a File to a Slack Channel (Using File Path)](https://docs.mulesoft.com/jp/slack-connector/latest/slack-connector-examples#upload-file-to-channel) and [Upload File Text Content to a Slack Channel](https://docs.mulesoft.com/jp/slack-connector/latest/slack-connector-examples#upload-file-text-content-to-channel). - In the Slack Connector configuration window, the **TLS** tab is renamed to the **Security** tab. For more information about how to upgrade this connector to version 2.0.0, refer to [Upgrading and Migrating Slack Connector to Version 2.x](https://docs.mulesoft.com/jp/slack-connector/latest/slack-connector-upgrade-migrate). ### Compatibility
Software Version

Mule runtime engine

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-19)1.0.19 **April 8, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now use Conversation list and Users list operations in Anypoint Studio as intended.

W-15448362
## [](#1-0-18)1.0.18 **March 14, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Slack Connector in Anypoint Studio as intended.

W-15251546
## [](#1-0-17)1.0.17 **January 25, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-16)1.0.16 **March 28, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12433949
## [](#1-0-15)1.0.15 **December 12, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12180337
## [](#1-0-14)1.0.14 **October 18, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The org.apache.commons library is upgraded to version 1.10.0 to address reported security vulnerabilities.

W-11913983

The com.fasterxml.jackson.core is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853432
## [](#1-0-13)1.0.13 **July 29, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11415979
## [](#1-0-12)1.0.12 **May 17, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11031313
## [](#1-0-11)1.0.11 **April 5, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920457
## [](#1-0-10)1.0.10 **February 1, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

When sending a message in Slack Connector, a Content cannot be displayed notification appeared instead of the message preview.

COCN-727
## [](#1-0-9)1.0.9 **January 3, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9851, CONN-9857
## [](#1-0-8)1.0.8 **December 21, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9564
## [](#1-0-7)1.0.7 **November 3, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CSCA-1031
## [](#1-0-6)1.0.6 **October 14, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-512
## [](#1-0-5)1.0.5 **September 2, 2021** ### Compatibility Slack Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-539, COCN-512
## [](#1-0-4)1.0.4 **July 9, 2021** ### [](#compatibility-20)Compatibility Slack Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-17)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-0-3)1.0.3 **June 8, 2021** ### [](#compatibility-21)Compatibility Slack Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-18)Fixed Issues - Improved the value provider’s error handling. (CONN-7984) ## [](#1-0-2)1.0.2 **March 19, 2021** ### [](#compatibility-22)Compatibility Slack Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-in-this-release)Fixed in This Release - Improved the content of some operations and their metadata. (CONN-7745) ## [](#1-0-1)1.0.1 **February 19, 2021** ### [](#compatibility-23)Compatibility Slack Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-in-this-release-2)Fixed in This Release - The connector did not appear in Studio. (CONN-7667) - When using the Conversations List or Users List operation, the connector failed with a null pointer exception. (CONN-7548) ## [](#1-0-0)1.0.0 **January 22, 2021** New connector. ### [](#compatibility-24)Compatibility Slack Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features For a list of supported configurations and operations, see the Slack Connector Reference Guide. ### [](#fixed-in-this-release-3)Fixed in This Release Not applicable. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Smartsheet Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Smartsheet (Smartsheet Connector) gives you access to the Smartsheet platform. This connector exposes operations provided by the Smartsheet API. Guide: [Smartsheet Connector User Guide](https://docs.mulesoft.com/jp/smartsheet-connector/latest/) ## [](#1-2-9)1.2.9 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-8)1.2.8 **August 31, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-7)1.2.7 **March 23, 2025** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-18104492, W-17915033
## [](#1-2-6)1.2.6 **February 26, 2025** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17141443
## [](#1-2-5)1.2.5 **June 20, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Smartsheet Connector in Anypoint Studio as intended.

W-16052094
## [](#1-2-4)1.2.4 **April 25, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-3)1.2.3 **December 22, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9679
## [](#1-2-2)1.2.2 **December 15, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9552
## [](#1-2-1)1.2.1 **August 18, 2021** ### [](#compatibility-9)Compatibility Smartsheet Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-6)Fixed Issues - Output metadata for the paginated operation **List Sheets** did not display correctly. (CONN-8701) ## [](#1-2-0)1.2.0 **August 10, 2021** ### [](#compatibility-10)Compatibility Smartsheet Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#new-features)New Features - Added the paginated **List Sheets** operation. ## [](#1-1-0)1.1.0 **May 12, 2021** ### [](#compatibility-11)Compatibility Smartsheet Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#new-features-2)New Features - Added a new **If Version After** field in the **Get Sheet** operation. Do not use the earlier version of this field. ## [](#1-0-0)1.0.0 **March 2, 2021** ### [](#compatibility-12)Compatibility Smartsheet Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features New connector For a list of supported configurations and operations, see the Smartsheet Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Snowflake Connector Release Notes Support Category: Select Anypoint Connector for Snowflake (Snowflake Connector) enables you to connect with your Snowflake instance to load data, run queries in Snowflake tables, and sync data with external business applications. Guide: [Snowflake Connector User Guide](https://docs.mulesoft.com/snowflake-connector/latest/) ## [](#1-4-2)1.4.2 **September 29, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.18.0 (Standard) or FIPS-certified driver (for FIPS environments)

BouncyCastle FIPS

2.1.3 (bc-fips) and 2.1.10 (bcpkix-fips)
### Fixed Issues
Issue Resolution ID

The c3p0 library is upgraded to version 0.14.2 to address reported security vulnerabilities.

W-3300013
## [](#1-4-1)1.4.1 **August 5, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.18.0 (Standard) or FIPS-certified driver (for FIPS environments)

BouncyCastle FIPS

2.1.3 (bc-fips) and 2.1.10 (bcpkix-fips)
### Fixed Issues
Issue Resolution ID

The BouncyCastle FIPS (bc-fips) library is upgraded to version 2.1.3 to address reported security vulnerabilities.

W-23441735
## [](#1-4-0)1.4.0 **December 20, 2025** ### What’s New - FIPS 140-3 Compliance Support: This release introduces comprehensive FIPS 140-3 compliance support, including: - Automatic FIPS mode detection via the `mule.security.model` system property - Smart BouncyCastle FIPS (BCFIPS) security provider registration with safety controls - Support for FIPS-certified Snowflake JDBC driver - Prevention of unauthorized JVM security configuration modifications in FIPS mode - Two configuration options: Configure BCFIPS in `java.security` (recommended) or enable auto-registration with explicit authorization - TLS 1.3 Support: Enhanced security with modern TLS 1.3 protocol support for Snowflake connections - Security Provider Management: Improved security provider registration logic with validation-first approach to prevent conflicts in regulated environments For detailed FIPS configuration instructions, see [Configuring FIPS 140-3 for Snowflake Connector](https://docs.mulesoft.com/snowflake-connector/latest/snowflake-connector-fips-config). ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.18.0 (Standard) or FIPS-certified driver (for FIPS environments)

BouncyCastle FIPS

2.1.2 (bc-fips) and 2.1.10 (bcpkix-fips)
### Fixed Issues
Issue Resolution ID

Security provider registration now validates whether BCFIPS already exists before attempting modifications, preventing conflicts in production environments.

W-20533642

In FIPS-enabled environments, automatic BCFIPS registration is disabled by default and requires explicit authorization via the mule.snowflake.fips.bcfips.autoregister system property.

W-20533642

Enhanced error handling and logging for cryptographic operations during private key authentication.

W-20533642
## [](#1-3-2)1.3.2 **May 17, 2025** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.18.0
### Fixed Issues
Issue Resolution ID

The mule-db-client dependency is upgraded to version 1.6.18.

W-18449673
## [](#1-3-1)1.3.1 **April 21, 2025** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.18.0
### Fixed Issues
Issue Resolution ID

The mule-db-client dependency now uses the latest GA version (1.6.17) instead of a SNAPSHOT version.

W-14218425

The connection tag is now in the Company_Product format.

W-17999498

Basic Snowflake Connection now includes a message stating it will be deprecated soon.

W-18115315
## [](#1-3-0)1.3.0 **February 24, 2025** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.18.0
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17796452

The BCFIPS provider is now added internally and is no longer a provided dependency.

If you added the BCFIPS provider in previous versions of Snowflake Connector, you must now remove bcprov-jdk18on-1.8.0.jar and bcpkix-jdk18on-1.8.0.jar from the JAVA_VM_FOLDER/jre/lib/ext folder. Then, remove the corresponding security provider entry from the java.security configuration file.

W-17796452

Bouncy Castle security provider is now registered while running MUnit test cases in Anypoint Studio.

W-17670180
## [](#1-2-1)1.2.1 **September 11, 2024** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.18.0
### Fixed Issues
Issue Resolution ID

The Copy into table operation now processes the PARSE_HEADER parameter correctly.

W-15961512
## [](#1-2-0)1.2.0 **March 5, 2024** ### What’s New - This connector now supports Key-pair authentication. ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.14.4
## [](#1-1-3)1.1.3 **January 31, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8, 11, and 17

Snowflake JDBC

3.14.2
## [](#1-1-2)1.1.2 **June 30, 2022** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11

Snowflake JDBC

3.14.2
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-11244962
## [](#1-1-1)1.1.1 **June 6, 2022** ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### Fixed Issues
Issue ID

The Max Idle Time field in the Snowflake Db Pooling Profile type now has the default value of 10800 instead of 0 to match the conditions set by Snowflake.

W-11235605
## [](#1-1-0)1.1.0 **January 11, 2022** ### What’s New - Added the **On Table Row** source. For more information, refer to the [Snowflake Connector Reference Guide](https://docs.mulesoft.com/snowflake-connector/latest/snowflake-connector-reference#Listener). ### Compatibility
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
## [](#1-0-1)1.0.1 **June 11, 2021** ### [](#compatibility-13)Compatibility Snowflake Connector is compatible with these software versions:
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### [](#fixed-issues-10)Fixed Issues - Fixed an issue with some exported packages from the `mule-db-client` library to avoid potential conflicts with other connectors. ## [](#1-0-0)1.0.0 **June 8, 2021** ### [](#compatibility-14)Compatibility Snowflake Connector is compatible with these software versions:
Software Version

Mule Runtime

4.3.0 and later

OpenJDK

8 or 11
### [](#features)Features New connector. For a list of supported configurations and operations, see the Snowflake Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # SOAP Schema Validation Policy The SOAP Schema Validation Policy policy validates incoming traffic against a specified WSDL schema. For configuration details, see [SOAP Schema Validation Policy](https://docs.mulesoft.com/gateway/latest/policies-included-soap-schema-validation). ## [](#september-2-2026)September 2, 2026 ### What’s New - SOAP Schema Validation Policy policy implementation version 1.1.0 is now supported by Omni Gateway. - This policy’s implementation is updated to improve policy performance, delivering higher throughput and lower latency. ## [](#april-15-2025)April 15, 2025 ### What’s New - SOAP Schema Validation Policy policy definition version 1.0.0 is now supported by Omni Gateway. # Sockets Connector Release Notes Anypoint Connector for Sockets (Sockets Connector) provides a sockets listener, send capability, and send and receive functionality. Additionally, it provides TCP and UDP requesters. Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Sockets Connector User Guide](https://docs.mulesoft.com/jp/sockets-connector/latest/) ## [](#1-2-10)1.2.10 **September 18, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-9)1.2.9 **July 23, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Commons IO library is upgraded to version 2.22.0 to address reported security vulnerabilities.

W-23441576
## [](#1-2-8)1.2.8 **July 2, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Previously, when using sockets:send-and-receive over a pooled TCP/TLS requester with the XML message protocol, the operation returned a null payload if the remote server half-closed the connection (via TCP FIN or TLS close_notify). The connector now actively detects these remotely closed connections and triggers a connectivity error, allowing your configured reconnection strategy to automatically reestablish the connection.

W-20876152
## [](#1-2-7)1.2.7 **September 26, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Apache commons-lang3 dependency is upgraded to version 3.19.0 to fix the CVE-2025-48924 vulnerability.

W-19174603
## [](#1-2-6)1.2.6 **June 27, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated org.mule.sdk:mule-sdk-api from 0.10.2 to 0.10.5.

W-18223642

Updated commons-io:commons-io from 2.14.0 to 2.19.0.

W-18223642

Updated org.mule.tools.maven:maven-helper-plugin from 3.3.0 to 3.6.1.

W-18223642

Updated org.mule.modules:mule-spring-module from 1.3.11 to 1.5.0.

W-18223642

Updated org.mule.tools.maven:munit-extensions-maven-plugin from 1.5.0 to 1.6.0.

W-18223642
## [](#1-2-5)1.2.5 **October 22, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Security vulnerabilities are now fixed.

W-16958714
## [](#1-2-4)1.2.4 **December 14, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-3)1.2.3 **October 18, 2022**
Software Version

Mule

4.1.1 and later
Issue ID

Updated typo in Max message leght label to Max message length.

W-11878349
## [](#1-2-2)1.2.2 **August 31, 2021**
Software Version

Mule

4.1.1 and later
Issue ID

The Send and Receive operation didn’t throw the ConnectionException message needed to trigger the reconnection strategy. Now, the operation throws the exception correctly.

SOCON-7

The Sockets Connector EoF protocol didn’t properly inform the end of file was reached and hanged until the timeout occurred. Now, the protocol performs correctly.

SOCON-10
## [](#1-2-1)1.2.1 **Jan 20, 2021** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-6)Fixed Issues Sockets Connector hangs during Studio debugging due to a 'NoClassDefFound' exception being thrown. (SOCON-6) ## [](#1-2-0)1.2.0 **June 24, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#features)Features Verbose/Wirelog log for TCP Connections. (MULE-18479) Consider that enabling Verbose/Wirelog can affect the performance related to the quantity of data logged. ## [](#1-1-6)1.1.6 **March 19, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-7)Fixed Issues Fixed issue that caused reconnection strategy to not work. (MULE-18173) ## [](#1-1-5)1.1.5 **March 28, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-8)Fixed Issues Upgraded Commons IO dependency to version 2.6. ## [](#1-1-4)1.1.4 **December 18, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-9)Fixed Issues Removed unnecessary uses of Guava to improve performance. ## [](#1-1-3)1.1.3 **December 14, 2018** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-10)Fixed Issues Updated mule-extensions-parent and mule-extensions-maven-plugin with the fix versions of the maven-install-plugin and maven. (MULE-15766) ## [](#1-1-2)1.1.2 **September, 20 2018** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.0.0** ### [](#fixed-issues-11)Fixed Issues Connector did not implement Equals() and HashCode() for their POJOs, which caused dynamic connections to not work properly. (MULE-15711) ## [](#1-1-1)1.1.1 **Mar 14, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.0.0** ### [](#new-features)New Features - Metadata for the Attributes of this connector is more accurate and now tells which fields are nullable. ### [](#fixed-issues-12)Fixed Issues - Connectors don’t communicate correctly if their POJOs properties are nullable or not. (MULE-14701) ## [](#1-1-0)1.1.0 **Jan 22, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-13)Fixed Issues - Upgrade Guava to 23.5. (MULE-14215) - Make sure all Serializable classes have UUID. (MULE-13670) ## [](#1-0-0)1.0.0 **Nov 13, 2017** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.0.0** ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Spike Control The Spike Control policy regulates API traffic. For configuration details, see [Spike Control Policy](https://docs.mulesoft.com/gateway/latest/policies-included-spike-control). ## [](#october-1-2026)October 1, 2026 ### What’s New - Spike Control policy definition version 1.2.3 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - Spike Control policy implementation version 1.2.2 is now supported by Omni Gateway. - Spike Control policy definition version 1.2.1 is now supported by Omni Gateway. # Spike Control ## [](#1-2-3)1.2.3 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-1-6)1.1.6 **October 27, 2023** ### [](#fixed-issues)Fixed issues - Policy can now be applied alongside Rate Limiting. ## [](#1-2-1)1.2.1 **May 26, 2022** ### [](#fixed-issues-2)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-2-0)1.2.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-1-5)1.1.5 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. ### [](#fixed-issues-3)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2).
Because a critical issue was found in the last validation stage, the Spike Control policy v1.1.4 has been deprecated and removed from production.
## [](#1-1-3)1.1.3 **August, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Several performance improvements are introduced in this release. ### [](#fixed-issues-4)Fixed Issues - When using a SOAP proxy, an incorrect return code is passed. ## [](#1-1-2)1.1.2 **April 26, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Several performance improvements are introduced in this release. ## [](#1-1-1)1.1.1 **March 16, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Added the `violationCategory` parameter in the YAML configuration file for Feedback Loop. ### [](#fixed-issues-5)Fixed Issues - The Rate Limiting policy is rejected from the scheduler during high network traffic. ## [](#1-1-0)1.1.0 **January 25, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.0** ## [](#see-also)See Also - [Spike Control](https://docs.mulesoft.com/gateway/latest/policies-included-spike-control) - [Known Issues](https://help.salesforce.com/s/issues) # Spring Module Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Spring Module User Guide](https://docs.mulesoft.com/spring-module/latest/) ## [](#2-2-0)2.2.0 **October 22, 2026** ### What’s New - Spring Module now supports Spring Framework 7 and Spring Security 7 through the new [`spring:v7-config`](https://docs.mulesoft.com/spring-module/latest/spring-module-reference#v7-config) global element. For the required library setup steps, see [Set Up Spring 7 Libraries in the pom.xml File](https://docs.mulesoft.com/spring-module/latest/spring-xml-maven#spring7-libraries). - `spring:v7-config` requires Spring Framework 7.0.9 and Spring Security 7.1.1. If a different Spring major version is loaded, the configuration fails at startup with a descriptive error. - The `spring-security-access` library is an optional dependency of `spring:v7-config`. Spring Security 7 moved the legacy access API classes into this library, so add it only if your application uses those classes. To determine whether your application is affected, see [Access API moves to spring-security-access](https://spring.io/blog/2025/09/09/access-api-moves-to-spring-security-access). - The [`spring:config`](https://docs.mulesoft.com/spring-module/latest/spring-module-reference#config) global element, which uses Spring Framework 6.2.19 and Spring Security 6.5.11, is deprecated. - A Mule application can’t use configurations of two different Spring Framework major versions at the same time. If an application defines both `spring:config` and `spring:v7-config`, validation fails. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
## [](#2-1-4)2.1.4 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
## [](#2-1-3)2.1.3 **August 13, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - The Spring Framework library is upgraded to version 6.2.19. - The Spring Security library is upgraded to version 6.5.11. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

Spring Module no longer throws a NullPointerException error when a bean lookup occurs before the Spring application context is initialized, such as when multiple spring:config elements are used across a plugin and an application with cross-context dependencies.

W-22204254
## [](#2-1-2)2.1.2 **May 16, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The spring-core library is upgraded to version 6.2.18 to address the CVE-2026-22745 and CVE-2025-41242 vulnerabilities.

W-22457008
## [](#2-1-1)2.1.1 **September 17, 2025** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

Spring Module is now backwards compatible with version 2.0.0 through restored injection fallback mechanism for Mule runtime objects in Spring beans.

W-19606565

Update spring-core to version 6.2.11 and spring-security-core to version 6.5.4.

W-19578337
## [](#2-1-0-deprecated)2.1.0 (Deprecated) **August 29, 2025** This version is deprecated. All of the features and fixed issues for this version are in version 2.1.1. ## [](#2-0-0)2.0.0 **July 30, 2025** ### What’s New - Spring Module (and its dependencies) are now compilable and compatible only with Java 17. - To align with modern development practices and ensure continued compatibility with secure and supported libraries, Spring Module is upgraded from Spring 5.x to Spring 6.x. - The structure of the `spring:security-manager` element is updated to resolve validation issues with the DSL. Previously, `delegate-security-providers` could be defined directly within `spring:security-manager`. Now, all `spring:delegate-security-provider` elements must be wrapped within a new `spring:delegate-security-providers` element. - Old structure (no longer supported): ```xml ``` - New structure (required): ```xml ``` For more information about how to upgrade the connector to version 2.0, refer to [Upgrading and Migrating Spring Module to Version 2.x](https://docs.mulesoft.com/spring-module/latest/spring-module-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.9.4 and later

OpenJDK

17
## [](#1-5-3)1.5.3 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x

OpenJDK

8, 11, and 17
## [](#1-5-2)1.5.2 **August 25, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes internal changes.

W-23985574
## [](#1-5-1)1.5.1 **August 24, 2026** This version is deprecated. The new features and fixed issues for this version are in version 1.5.2. ## [](#1-5-0)1.5.0 **March 19, 2025** ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17849656
## [](#1-4-0)1.4.0 **May 9, 2024** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x

OpenJDK

8, 11, and 17
## [](#1-3-11)1.3.11 **December 13, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x

OpenJDK

8, 11, and 17
## [](#1-3-10)1.3.10 **October 31, 2023** ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x
### Fixed Issues
Issue Resolution ID

Now logging works fine when defined as a bean.

W-12785049
## [](#1-3-9)1.3.9 **August 28, 2023** ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x
### What’s New - Upgraded spring-security-core to version: 5.8.6 and spring-core to version:5.3.29. ## [](#1-3-8)1.3.8 **July 21, 2023** ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x
### What’s New - Upgraded spring-security-core to version: 5.7.8 ## [](#1-3-7)1.3.7 **September 26, 2022** ### Compatibility
Application/Service Version

Mule

4.1.5 and later

Spring

4.3.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x
### What’s New - Upgraded com.google.code.gson to version 2.9.1. - Upgraded org.springframework to version 5.3.22. - Upgraded org.springframework.security to version 5.7.3. ## [](#1-3-6)1.3.6 **March 8, 2021** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.5** ### [](#supported-spring-versions)Supported Spring Versions - 4.3.x - 5.0.x - 5.1.x ### [](#fixed-issue)Fixed Issue - Fix the `Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.springframework.org/schema/security]` error when using the Spring Module within a shared lib. (SPRM-203) ## [](#1-3-5)1.3.5 **December 4, 2020** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### [](#supported-spring-versions-2)Supported Spring Versions - 4.3.x - 5.0.x - 5.1.x ### [](#fixed-issue-2)Fixed Issue - Removed local packages that are exported by Mule runtime engine (SPRM-124) ## [](#1-3-4)1.3.4 **September 15, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### [](#supported-spring-versions-3)Supported Spring Versions - 4.3.x - 5.0.x - 5.1.x ### [](#fixed-issue-3)Fixed Issue - Fixed an issue that occurred when running MUnit tests starting with Mule runtime engine version 4.4.0. (MULE-18457) ## [](#1-3-3)1.3.3 **March 16, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### [](#supported-spring-versions-4)Supported Spring Versions - 4.3.x - 5.0.x - 5.1.x ### [](#fixed-issue-4)Fixed Issue - Fixed issue where it was unable to load resources whenever spring:config is in defined both domain and application. (MULE-18139) ## [](#1-3-2)1.3.2 **November 1, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#supported-spring-versions-5)Supported Spring Versions - 4.3.x - 5.0.x - 5.1.x ### [](#fixed-issues-7)Fixed Issues - Spring Module extension model had the wrong suggested libraries versions. (MULE-17695) ## [](#1-3-1)1.3.1 **July 12, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.1** ### [](#supported-spring-versions-6)Supported Spring Versions - 4.3.x - 5.0.x - 5.1.x ### [](#fixed-issues-8)Fixed Issues - Upgrade Spring to 5.1.6 and Spring Security to 5.1.5. (MULE-16647) - Add mappings of `-current` spring schemas for backward compatability. (MULE-16748) - "DefaultExtensionManager: Registering extension Spring." log entry shows an incorrect version. (MULE-16566) ## [](#1-3-0)1.3.0 **December 12, 2018** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements)New Features and Enhancements - Add support for Spring 5. (MULE-15677) ### [](#fixed-issues-9)Fixed Issues - Get resources using reflection to support Mule 4.1.x. (MULE-16204) ## [](#1-2-1)1.2.1 **December 11, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-10)Fixed Issues - Spring Context behavior is broken. (MULE-15523) ## [](#1-2-0)1.2.0 **July 25, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-11)Fixed Issues - Set `alwaysEnabled` in order to allow a lazy Mule context to initialize the security manager. (MULE-15171) - Include all essential Spring dependencies as required. (MULE-15439) ## [](#1-1-1)1.1.1 **May 11, 2018** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-12)Fixed Issues - Review security configuration options. (MULE-14711) ## [](#1-1-0)1.1.0 **January 30, 2018** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-13)Fixed Issues - Define UUID on all serializable classes. (MULE-13670) ## [](#1-0-0)1.0.0 **November 14, 2017** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.0.0** ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Stream Idle Timeout The Stream Idle Timeout policy sets the maximum idle duration for a stream between the Omni Gateway and an upstream service. For configuration details, see [Upstream Idle Timeout Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-upstream-idle-timeout). ## [](#february-24-2025)February 24, 2025 ### What’s New - Stream Idle Timeout policy implementation version 1.0.0 is now supported by Omni Gateway. # Stream Idle Timeout The Stream Idle Timeout policy sets the maximum duration a stream can remain idle without receiving a request or response. For configuration details, see [Stream Idle Timeout Policy](https://docs.mulesoft.com/gateway/latest/policies-included-stream-idle-timeout). ## [](#february-24-2025)February 24, 2025 ### What’s New - Stream Idle Timeout policy implementation version 1.0.0 is now supported by Omni Gateway. - Stream Idle Timeout policy definition version 1.0.0 is now supported by Omni Gateway. # Stripe Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Stripe (Stripe Connector) gives you access to the Stripe platform. This connector exposes operations provided by the Stripe API. Guide: [Stripe Connector User Guide](https://docs.mulesoft.com/jp/stripe-connector/latest/) ## [](#1-0-19)1.0.19 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-18)1.0.18 **August 27, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core and jackson-databind libraries are upgraded to version 2.22.2.

  • The JSON-Java (org.json) library is upgraded to version 20260719.

  • The Apache Commons IO library is upgraded to version 2.22.0.

W-23441678
## [](#1-0-17)1.0.17 **August 18, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-core and jackson-databind libraries are upgraded to version 2.22.1 to address reported security vulnerabilities.

W-23705584
## [](#1-0-16)1.0.16 **July 2, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now installs and loads correctly from Anypoint Exchange in Anypoint Studio. Previously, Stripe Connector 1.0.15 failed to load its extension model because a packaging regression omitted the required REST SDK common classes from the connector plugin.

W-23152650
## [](#v1-0-15)1.0.15 (Deprecated) **June 13, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The List all events operation no longer returns an HTTP 400 error from the Stripe API when you specify multiple event types.

W-18383316
## [](#1-0-14)1.0.14 **July 2, 2024** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer throws an error when used in conjunction with Amazon Lambda Connector.

W-15283306
## [](#1-0-13)1.0.13 **April 23, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-0-12)1.0.12 **July 14, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-13672146
## [](#1-0-11)1.0.11 **December 16, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The expand field now works for the Retrieve a customer operation.

W-12073606
## [](#1-0-10)1.0.10 **November 8, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-12027076
## [](#1-0-9)1.0.9 **November 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-12008730
## [](#1-0-8)1.0.8 **October 26, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The connector now shows polling logs for all sources.

W-10866183, W-11853409
## [](#1-0-7)1.0.7 **May 24, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The connector now shows polling logs for all sources.

W-11120854
## [](#1-0-6)1.0.6 **April 26, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920463
## [](#1-0-5)1.0.5 **February 1, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CSCA-1325
## [](#1-0-4)1.0.4 **January 14, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Updated the com.fasterxml.jackson.core library to 2.12.6 to address security vulnerabilities.

CONN-9840
## [](#1-0-3)1.0.3 **October 19, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CSCA-913
## [](#1-0-2)1.0.2 **May 25, 2021** ### [](#compatibility-18)Compatibility Stripe Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-16)Fixed Issues Optimized the connector to improve its overall stability and performance. ## [](#1-0-1)1.0.1 **February 16, 2021** ### [](#compatibility-19)Compatibility Stripe Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-in-this-release)Fixed in This Release - Stripe Connector did not appear in Studio Search. (CONN-7661) ## [](#1-0-0)1.0.0 **January 29, 2021** New connector. ### [](#compatibility-20)Compatibility Stripe Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features For a list of supported configurations and operations, see the Stripe Connector Reference Guide. ### [](#fixed-in-this-release-2)Fixed in This Release Not applicable. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Tableau Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Tableau (Tableau Connector) enables you to integrate and transform data from applications to build visualizations. This connector exposes operations provided by the Tableau API. Guide: [Tableau Connector User Guide](https://docs.mulesoft.com/jp/tableau-specialist-connector/latest/) ## [](#1-1-6)1.1.6 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-5)1.1.5 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind library is upgraded to version 2.22.1.

  • The gson library is upgraded to version 2.14.0.

  • The commons-io library is upgraded to version 2.22.0.

  • The commons-collections4 library is upgraded to version 4.6.0.

  • The jna library is upgraded to version 5.19.1.

W-23441625
## [](#1-1-4)1.1.4 **May 19, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind library is upgraded to version 2.21.1.

  • The gson library is upgraded to version 2.13.2.

  • The commons-collections library is upgraded to version 4.4.3.

W-22449434
## [](#1-1-3)1.1.3 **March 25, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-1-2)1.1.2 **February 14, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now automatically reconnects when the session expires and the Tableau API returns a 401002:INVALID_AUTH_CREDENTIALS exception.

W-14556306
## [](#1-1-1)1.1.1 **June 28, 2023** ### What’s New - The com.fasterxml.jackson.core library is upgraded to version 2.15.2. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now throws a TABLEAU-SPECIALIST:UNKNOWN error with the intended message when the error code is not mapped.

W-13508120

The com.fasterxml.jackson.core library is upgraded to version 2.15.2 to address reported security vulnerabilities.

W-13636774
## [](#1-1-0)1.1.0 **December 7, 2021** ### What’s New - Added support for the Server Rest configuration. - Added support for the Tableau Site API which contains the following new operations: - **Create site** - **Delete site** - **Query site** - **Query sites** - **Update site** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#1-0-0)1.0.0 **October 7, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Tableau Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Teamwork Connector Release Notes Anypoint Connector for Teamwork (Teamwork Connector) enables Mule applications to access the Teamwork API. Guide: [Teamwork Connector User Guide](https://docs.mulesoft.com/teamwork-connector/latest/) ## [](#0-1-28)0.1.28 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-27)0.1.27 **August 18, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-26)0.1.26 **June 30, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **December 17, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/teamwork-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [Teamwork Connector User Guide](https://docs.mulesoft.com/teamwork-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
## [](#see-also)See Also - [Teamwork Connector User Guide](https://docs.mulesoft.com/teamwork-connector/latest/) - [Teamwork Connector Reference](https://docs.mulesoft.com/teamwork-connector/latest/teamwork-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Tokenization
This policy uses the legacy unified policy model. Therefore, the policy does not have implementation release notes in API Manager and all release notes are provided here.
## [](#1-2-1)1.2.1 **August 6, 2024** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### What’s New - Updated third party dependencies. ## [](#1-2-0)1.2.0 **February 07, 2024** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### What’s New - This policy is now compatible with Java 17 for Mule runtime versions 4.6.0 or later. ## [](#1-1-2)1.1.2 **January 06, 2021** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Added OAS 3.0 code snippet in the policy YAML file. - Improved error handling for WSDL APIs. ## [](#1-1-1)1.1.1 **Apr 30, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Tokenization support is now provided for the `text/xml` and `application/soap+xml` payloads. ### [](#fixed-issues)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-1-0)1.1.0 **Mar 20, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Improved performance in header manipulation. ### [](#fixed-issues-2)Fixed Issues - Fixed error that caused the policy to apply the configuration in the response incorrectly. ## [](#1-0-0)1.0.0 **Jan 30, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **4.1.1** ## [](#see-also)See Also - [Tokenization Policy for Mule 4](#api-manager::policy-mule4-tokenization.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # Tracing The Tracing policy override global tracing configuration. For configuration details, see [Tracing Policy](https://docs.mulesoft.com/gateway/latest/policies-included-tracing). ## [](#august-06-2025)August 06, 2025 ### What’s New - Tracing policy implementation version 1.1.0 is now supported by Omni Gateway. - Tracing policy definition version 1.1.0 is now supported by Omni Gateway. # Tracing Module Release Notes Tracing module enables you to enhance your logs by adding, removing, and clearing all variables from the logging context for a given Mule event. It also enables you to modify the correlation ID during flow execution and add custom attributes to a transaction’s root span. Guide: [Tracing Module User Guide](https://docs.mulesoft.com/tracing-module/latest/) ## [](#1-3-0)1.3.0 **October 6, 2026** ### What’s New - The new Add Root Span Attributes operation (``) adds custom attributes to the root span of the current transaction. This operation requires Mule runtime 4.13 or later and has no effect on earlier runtime versions. For more information, see [Add Custom Attributes to the Root Span with Tracing Module](https://docs.mulesoft.com/tracing-module/latest/tracing-module-add-root-span-attributes). ### Compatibility
Software Version

Mule

4.4.0 or later

OpenJDK

8, 11, and 17
## [](#1-2-1)1.2.1 **May 7, 2026** ### What’s New
Issue Resolution ID

The plugins used for packaging are updated to fix a connector metadata generation issue related to Java 17 compatibility.

W-21748187
### Compatibility
Software Version

Mule

4.4.0 or later

OpenJDK

8, 11, and 17
## [](#1-2-0)1.2.0 **November 20, 2024** ### What’s New - This release includes performance enhancements. ### Compatibility
Software Version

Mule

4.4.0 or later

OpenJDK

8, 11, and 17
## [](#1-1-0)1.1.0 **January 10, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.4.0 or later

OpenJDK

8, 11, and 17
## [](#1-0-0)1.0.0 **October 5, 2021** ### What’s New New connector. For a list of supported configurations and operations, refer to the Tracing module Reference Guide. ### Compatibility
Application/Service Version

Mule

4.4.0 and later
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # TRADACOMS EDI Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [TRADACOMS EDI Connector User Guide](https://docs.mulesoft.com/tradacoms-edi-connector/latest/) ## [](#3-0-1)3.0.1 **September 30, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.6.24 and later

Java

8, 11, and 17

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
## [](#3-0-0)3.0.0 **August 31, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. - TRADACOMS EDI Connector now requires Mule 4.6.24 or later. ### Compatibility
Software Version

Mule runtime engine

4.6.24 and later

Java

8, 11, and 17

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
## [](#2-0-7)2.0.7 **January 22, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
## [](#2-0-6)2.0.6 **September 21, 2023** ### What’s New - The `org.yaml.snakeyaml` library is upgraded to version 2.0 to address reported security vulnerabilities. - The `org.scala-lang` library is upgraded to version 2.12.15. ### Compatibility
Software Version

Mule

4.1.0 and later

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
## [](#2-0-5)2.0.5 **October 24, 2022** ### What’s New - The `org.yaml.snakeyaml` library is upgraded to version 1.32 to address reported security vulnerabilities. ### Compatibility
Software Version

Mule

4.1.0 and later

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
## [](#2-0-4)2.0.4 **January 4, 2022** ### Compatibility
Software Version

Mule

4.1.0 and later

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9587
## [](#2-0-3)2.0.3 **December 20, 2021** ### [](#compatibility-7)Compatibility TRADACOMS EDI Connector v2.0.3 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
### [](#fixed-issue)Fixed Issue Upgraded library dependencies. (CONN-9587) ## [](#2-0-2)2.0.2 **November 9, 2020** ### [](#compatibility-8)Compatibility TRADACOMS EDI Connector v2.0.2 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
### [](#fixed-issue-2)Fixed Issue Upgraded the `Connectivity parent` 4.0.1 dependency. (CONN-7161) ## [](#2-0-1)2.0.1 **September 09, 2020** ### [](#compatibility-9)Compatibility TRADACOMS EDI Connector v2.0.1 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
### [](#fixed-issues-2)Fixed Issues Removed the following unused dependencies (CONN-6887): - Apache Commons IO library dependency - Apache Log4j dependency ## [](#2-0-0)2.0.0 **April 13, 2018** This release adapts TRADACOMS for use with Mule 4 and Studio 7. ### [](#compatibility-10)Compatibility TRADACOMS EDI Connector v2.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

TRADACOMS (file:version)

ACKMNT:4, AVLDET:4, CORDER:6, CRAINF:3, CREDIT:9, CUSINF:8, DELIVR:9, DLCDET:5, DRAINF:3, EXCINF:3, GENRAL:3, INVOIC:9, LPRDET:2, ORDERS:9, PAYINF:3, PICKER:4, PPRDET:2, PRIINF:8, PROINF:8, SADDET:3, SNPSTS:3, SRMINF:9, UCNDET:3, UPLIFT:4, UTLBIL:3
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Traffic Management for Multiple Upstream Services The Traffic Management for Multiple Upstream Services policy manages API instance traffic to multiple upstream services from a single consumer endpoint For configuration details, see [Traffic Management for Multiple Upstream Services](https://docs.mulesoft.com/gateway/latest/policies-included-traffic-management-route). ## [](#february-27-2025)February 27, 2025 ### What’s New - Traffic Management for Multiple Upstream Services policy support added to Omni Gateway. # Traffic Management for Multiple Upstream Services (Weighted) The Traffic Management for Multiple Upstream Services (Weighted) policy manages weighted API instance traffic to multiple upstream services from a single consumer endpoint. For configuration details, see [Traffic Management for Multiple Upstream Services (Weighted)](https://docs.mulesoft.com/gateway/latest/policies-included-traffic-management). ## [](#february-27-2025)February 27, 2025 ### What’s New - Traffic Management for Multiple Upstream Services (Weighted) policy support added to Omni Gateway. # Transport Layer Security (TLS) - Inbound The Transport Layer Security (TLS) - Inbound policy enables authentication between a client and the API proxy. For configuration details, see [Transport Layer Security Policy - Inbound](https://docs.mulesoft.com/gateway/latest/policies-included-tls). ## [](#february-27-2025)February 27, 2025 ### What’s New - Transport Layer Security (TLS) - Inbound policy support added to Omni Gateway. # Transport Layer Security (TLS) - Outbound The Transport Layer Security (TLS) - Outbound policy enables two-way authentication between the API proxy and an upstream service. For configuration details, see [Transport Layer Security Policy - Outbound](https://docs.mulesoft.com/gateway/latest/policies-included-tls-outbound). ## [](#february-27-2025)February 27, 2025 ### What’s New - Transport Layer Security (TLS) - Outbound policy support added to Omni Gateway. # Trello Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Trello (Trello Connector) gives you access to the Trello platform. This connector exposes the most important operations provided by the Trello API. See the [Trello API Reference](https://developer.atlassian.com/cloud/trello/rest/api-group-actions/) to learn more. Guide: [Trello Connector User Guide](https://docs.mulesoft.com/jp/trello-connector/latest/) ## [](#1-2-6)1.2.6 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-5)1.2.5 **August 21, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The json library is upgraded to version 20260814 to address reported security vulnerabilities.

W-23441679
## [](#1-2-4)1.2.4 **May 15, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21761922
## [](#1-2-3)1.2.3 **January 31, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release upgrades some internal dependencies.

W-20970507
## [](#1-2-2)1.2.2 **May 24, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-2-1)1.2.1 **June 16, 2021** ### [](#compatibility-6)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#new-features)New Features - Added a test connection for the connector. (CONN-8053) ## [](#1-2-0)1.2.0 **March 31, 2021** ### [](#compatibility-7)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features - Added the Board Id field for the two sources (On New Card and On Updated Card). ## [](#1-1-0)1.1.0 **March 18, 2021** ### [](#compatibility-8)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features-2)Features - Added two new sources (On New Card and On Updated Card). - Added one new operation (DeleteBoardsByIdBoard). ## [](#1-0-0)1.0.0 **February 5, 2021** ### [](#compatibility-9)Compatibility Trello Connector is compatible with these software versions:
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features-3)Features New connector For a list of supported configurations and operations, see the Trello Connector Reference. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Twilio Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Twilio is an API cloud provider for voice and SMS communications for customers who want to use phone services as marketing leverage. The Twilio Connector lets you interact with the Twilio SMS API within Mule. Guide: [Twilio Connector User Guide](https://docs.mulesoft.com/jp/twilio-connector/latest/) ## [](#4-2-10)4.2.10 **October 14, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

Twilio REST API

2010-04-01

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.3.

  • The org.json library is upgraded to version 20260814.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The guava library is upgraded to version 33.7.2-jre.

W-24134446
## [](#4-2-9)4.2.9 **June 20, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

Twilio REST API

2010-04-01

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Twilio Connector in Anypoint Studio as intended.

W-16051073
## [](#4-2-8)4.2.8 **April 26, 2024** ### Compatibility
Software Version

Mule

4.2.1 and later

Twilio REST API

2010-04-01

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Twilio Connector in Anypoint Studio as intended.

W-15593389
## [](#4-2-7)4.2.7 **March 21, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.1 and later

Twilio REST API

2010-04-01

OpenJDK

8, 11, and 17
## [](#4-2-6)4.2.6 **January 17, 2023** ### Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The On New Message source now sends only new messages to the flow.

W-11798920
## [](#4-2-5)4.2.5 **June 7, 2022** ### Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The product now uses more inclusive language.

W-11156928
## [](#4-2-4)4.2.4 **January 7, 2022** ### Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9858
## [](#4-2-3)4.2.3 **December 22, 2021** ### Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9683
## [](#4-2-2)4.2.2 **December 17, 2021** ### Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9554
## [](#4-2-1)4.2.1 **August 18, 2021** ### Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### Fixed Issues - Output metadata for paginated operations did not display correctly. ## [](#4-2-0)4.2.0 **August 11, 2021** ### [](#compatibility-11)Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### [](#new-features)New Features - Added the **On New Message** source. - Added new, paginated List operations. ## [](#4-1-0)4.1.0 **June 3, 2021** ### [](#compatibility-12)Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### [](#fixed-issues-10)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#4-0-0)4.0.0 February 9, 2021 ### [](#compatibility-13)Compatibility
Software Version

Mule

4.2.1

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### [](#features)Features - New version of Twilio Connector. For a list of supported operations, see the Twilio Connector Reference Guide. ## [](#3-0-4)3.0.4 **December 7, 2020** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.0

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### [](#features-2)Features - Upgraded the Apache Commons IO library to the latest version, 2.8.0. ## [](#3-0-3)3.0.3 **May 20, 2020** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.0

Twilio REST API

2010-04-01

OpenJDK

8 and 11
### [](#features-3)Features Updated multiple libraries to the latest version ## [](#3-0-2)3.0.2 **April 22, 2019** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.0.0

Twilio REST API

2010-04-01
### [](#fixed-issues-11)Fixed Issues - Several minor fixes ## [](#3-0-1)3.0.1 **August 13, 2018** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.0.0

Twilio REST API

2010-04-01
### [](#fixed-issues-12)Fixed Issues - Operations failing - Some operations, such as Send Message, failed to perform successful calls to the Twilio REST API. This is now fixed. ## [](#3-0-0)3.0.0 **January, 2018** This version provides support for Mule 4. ### [](#compatibility-18)Compatibility
Software Version

Mule

4.0.0

Twilio REST API

2010-04-01
### [](#features-4)Features - This version supports Mule 4. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.6.0-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.6.0-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.6.2-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.6.2-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.0-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.0-release-notes.adoc\[\] ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.1-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.1-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.10-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.10-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.11-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.11-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.12-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.12-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.13-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.13-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.14-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.14-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.15-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.15-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.16-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.16-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.17-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.17-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.18-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.18-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.19-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.19-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.2-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.2-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.20-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.20-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.21-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.21-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.22-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.22-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.23-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.23-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.24-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.24-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.3-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.3-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.4-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.4-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.5-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.5-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.6-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.6-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.7-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.7-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.8-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.8-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-bot/rpa-bot-1.7.9-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-bot-1.7.9-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.0-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.0-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.1-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.1-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.2-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.2-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.3-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.3-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.4-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.4-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.5-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.5-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.6-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.6-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.7-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.7-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.6.8-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.6.8-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/6.6/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.0-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.0-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/latest/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.1-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.1-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.10-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.10-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.11-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.11-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.12-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.12-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.13-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.13-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.14-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.14-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.16-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.16-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.17-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.17-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.18-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.18-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.19-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.19-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.2-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.2-release-notes.adoc\[\] \* [Troubleshooting Microsoft Azure Setup](https://docs.mulesoft.com/rpa-builder/latest/troubleshooting-azure-oauth-setup) \* [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.20-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.20-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.21-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.21-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.22-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.22-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.23-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.23-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.24-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.24-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.25-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.25-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.26-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.26-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.3-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.3-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.4-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.4-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.5-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.5-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.6-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.6-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.7-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.7-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.8-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.8-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-builder/rpa-builder-6.7.9-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-builder-6.7.9-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-manager/rpa-manager-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-manager-release-notes.adoc\[\] ## [](#see-also)See Also - [ボットのトラブルシューティング](https://docs.mulesoft.com/jp/rpa-manager/botmanagement-troubleshoot) - [Known Issues](https://help.salesforce.com/s/issues) Unresolved include directive in modules/ROOT/pages/rpa-recorder/rpa-recorder-6.5.0-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-recorder-6.5.0-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-recorder/rpa-recorder-6.5.2-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-recorder-6.5.2-release-notes.adoc\[\] Unresolved include directive in modules/ROOT/pages/rpa-recorder/rpa-recorder-6.6.0-release-notes.adoc - include::rpa-home::partial$release-notes/rpa-recorder-6.6.0-release-notes.adoc\[\] ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Update Patches to Mule Patch updates are cumulative releases that include the latest bug fixes and security enhancements to a specific patch (x.y.z) version, plus all previously released features and fixes for that patch version. A patch update version appends an update identifier such as `-20210622` to the release version, for example, `4.3.0-20210622` for the Mule 4.3.0 release. You can find release notes for monthly Mule runtime engine patch updates in [MuleSoft Release Note Summary by Month](https://docs.mulesoft.com/jp/release-notes/quick-refs/by-date-index). For Mule 4.5 and later, the version naming convention for CloudHub, CloudHub 2.0, and Runtime Fabric changes following the schema for the new release channels, Edge and Long-term Support (LTS). _Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\] : Build\[numeric\] Channel\[e for edge, nothing for LTS\]_ Here are examples of the version numbers: - Edge: 4.5.0:1e - Edge: 4.6.0:1e - LTS: 4.6.0:1 In the case of Standalone (On-Premises), the Mule runtime versioning changes from date-based, for example, `4.4.0-20230317` to semVer as: _Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\]_ Here are examples of the version numbers: - 4.5.1 - 4.5.2 - 4.5.3 See [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ## [](#schedule)Patch Update Schedule ### [](#for-mule-4-5-and-later-versions)For Mule 4.5 and Later Versions Starting with Mule 4.5, MuleSoft introduces two new release channels, Edge and Long-Term Support (LTS). Both release channels are available in all our deployment models: Anypoint Runtime Fabric, CloudHub, CloudHub 2.0, and Hybrid Standalone. Release cadence refers to new Mule runtime versions. Patch updates for supported versions continue to follow the monthly patch update schedule. Consider these factors to determine the approach that best suits your requirements ahead of the Mule 4.4 End of Standard Support.
Channel Type Release Cadence Differentiators Support Coverage

Edge

Up to three times per year

  • Includes new features on a frequent release cadence with shorter maintenance coverage.

  • Versions aren’t FedRAMP approved.

For versions 4.9 and later:

  • Standard Support until one month after the next Edge version is released

  • 3 months of Extended Support

For version 4.8:

  • 5 months of Standard Support

  • 3 months of Extended Support

For versions 4.5 to 4.7:

  • 4 months of Standard Support

  • 4 months of Extended Support

LTS

Periodic (Scheduled for February)

  • Includes new features introduced in prior Edge releases, along with new features introduced in the February Edge release. This release is maintained for an extended period over being the first to adopt new capabilities.

For version 4.6 and later:

  • A minimum of 18 months of Standard Support

  • A minimum of 6 months of Extended Support
If an LTS version is released in February, both Edge and LTS share the same underlying version, including the same minor Mule runtime version and new features. ### [](#for-mule-4-4-and-previous-versions)For Mule 4.4. and Previous Versions Each month, MuleSoft releases updates to selected Mule patch releases. In some cases, MuleSoft also releases updates outside of this timeframe, typically to expedite the delivery of more critical security updates. Update strategies differ by product.
  On-premises (Standalone) Mule CloudHub Anypoint Runtime Fabric

On the first full week of the month, updates to Mule patches are available. MuleSoft provides updates only for patch versions that received bug fixes or security enhancements for the month.

Yes

Yes

Yes

You can continue to use a previous update to a Mule patch until the third full week of the month after the latest patch update is released.

Yes

Yes

Yes

Your new deployments require use of the latest patch update during the third full week of the month.

No

Yes

Yes

On the third full week of the month, MuleSoft automatically updates existing applications to the latest patch update of Mule.

No

Yes

  • Sandbox environments undergo forced updates Monday through Friday.

  • Production environments undergo forced updates Saturday and Sunday.

See the monthly update schedule in CloudHub Runtime and Operating System Patch Update Release Notes.

No
Managing Mule Runtime Patch Updates for Runtime Fabric
On-premises Mule, CloudHub, and Anypoint Runtime Fabric updates for a given Mule patch version receive the same _Mule runtime engine_ fixes and enhancements. However, CloudHub and Anypoint Runtime Fabric patches can contain additional fixes and improvements that are specific to those products. ## [](#apply_patch_updates)Apply Patch Updates Before updating the patch version on which you are running your Mule applications, review the [patch update schedule](#schedule). The update procedure and schedule differ by deployment environment, whether on-premises, CloudHub, or Anypoint Runtime Fabric. To perform the update, see: - [Mule Runtime Patch Updates for Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/runtime-patch-updates) - [CloudHub Runtime Continuous Updates](https://docs.mulesoft.com/cloudhub/cloudhub-app-runtime-version-updates) - [On-premise Mule Updates](#update_onprem_patch) ### [](#update_onprem_patch)Apply a Patch Update to an On-Premises (Standalone) Mule For standalone Mule instances, which are hosted on-premises, you can use the [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) to automate the patching process or you can apply the patch manually to the instance. MuleSoft typically releases monthly updates to the latest Mule minor versions and sometimes to earlier versions of Mule. Each Mule runtime patch update is posted to [Release Note Summary by Month](https://docs.mulesoft.com/jp/release-notes/quick-refs/by-date-index). It is important to note that for on-premise deployments, a single instance of Mule can run one or more applications. When you patch an instance of Mule, the update applies simultaneously to all the applications deployed to that instance. Standalone Mule installations do not undergo forced updates, but MuleSoft recommends that you apply the latest upgrades each month updates are available to benefit from the latest fixes and security enhancements. For on-premises (standalone) Mule instances: 1. [Download Standalone Mule for On-Premises Deployments](#mule_standalone_download) #### [](#mule_standalone_download)Download Standalone Mule for On-Premises Deployments On the first full week of the month you can download new versions of updated Mule from your customer portal in the [Salesforce Help](https://help.salesforce.com). The portal provides links to full Mule distributions that apply the latest patch: - Installation files that follow the filename convention `mule-ee-distribution-standalone-x.y.z-YYYMMDD.zip` (for example,`mule-ee-distribution-standalone-4.3.0-20210622.zip`) are for new Mule installations, rather than updates to existing installations. These installations contain all fixes and enhancements up to the specified month and year. If you need to install a full instance of Mule instead of applying a patch update to an existing Mule instance, unzip the file, and set the `MULE` environment variable. For general guidance, see [Download, Install, Configure, and Upgrade On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task). # Upgrading Mule Runtime Engine (Versions 3.x to 3.n) **Mule 3.x Upgrades Only** (For guidance with migrations from Mule 3.x to Mule 4, see [Mule 4 for Mule 3 Users](https://docs.mulesoft.com/mule-runtime/latest/).) This document describes considerations and best practices when changing the 3.x versions of Mule runtime engine on your on-premises servers in the following deployments: - Mule standalone instances - Mule instances on-premises through [Runtime Manager](https://docs.mulesoft.com/jp/runtime-manager/)
Keep in mind that if you’re deploying your applications to CloudHub, then this content is not relevant to you, with the exception of the steps outlined in the section Application Runtime Version. Changing the Mule runtime version of a Mule application that’s deployed to on CloudHub is simply managed from the runtime version drop-down box in the application settings deployment configuration page.
## [](#application-runtime-version)Application Runtime Version

Mule runtimes use semantic versioning, therefore please note that Mule applications:

  • Are most likely not compatible between major runtime versions releases (e.g. z.0.0)

  • Are potentially compatible between minor runtime version releases (e.g: 3.y.0), but MuleSoft recommends executing a regression test cycle to validate this.

  • Are assured to be fully compatible for patch releases of the Mule runtime (e.g: 3.8.x)
Before you begin, read the [release notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb) for the Mule Runtime version you wish to upgrade to (which we will call the target version, from here on), to know if you must make any necessary changes to your applications to ensure compatibility. For example, if you migrate from a version that’s older than 3.6 to a version that’s newer, you might want to change all HTTP connectors to the newer version of this connector as the old one is deprecated as of Mule Runtime 3.6. If there are no relevant changes between the Mule Runtime version in which the application is developed and the target Mule Runtime version to which you’re migrating, then you shouldn’t need to modify your application. Mule Runtimes support having applications that are built with older Mule versions deployed to them. If you do decide to change your Mule application’s version, you must: 1. [Install Mule Runtime Engine in Anypoint Studio](https://docs.mulesoft.com/studio/install-mule-runtime-versions) to handle that version in the IDE. 2. For every application that you update: 1. [Import the application](https://docs.mulesoft.com/studio/import-export-packages) to Anypoint Studio as a Mule project. 2. Navigate the package explorer on the left to find its `mule-project.xml` file and open it. Change the Mule version by selecting it from the **Server Runtime** dropdown menu. ![updating mule versions 364d6](/mulesoft/current/ja-jp/release-notes/_images/mule-runtime/updating-mule-versions-364d6.png) 3. Make any other changes to your Mule project that may be necessary depending on the version gap you’re transitioning. 4. Export your project as a Mule Deployable Archive (.zip file). If you use Maven to build your application, edit its **pom.xml** file to change the `muleVersion` property value, so that it matches the target version. Once the Mule Deployable Archives (.zip files) are in versions that you’re sure are compatible with the target runtime version and you’ve also validated that any other necessary changes that ensure compatibility have been applied, you can move on to installing the corresponding Mule Runtime on your servers. ## [](#mule-standalone-runtime-version)Mule Standalone Runtime Version
To ensure that you have faster downtime and an easier backup route, we recommend that you initially install your new Mule Runtime on a separate server from where you have your current Mule Runtime installed.
1. Download the new Mule version from the Customer Portal and install it (preferably on a different server or virtual machine). 2. If any of your applications use shared custom libraries, make sure you copy those .jar files to the `/lib/user` directory of the new version.

If any of your previous applications rely on a full or a partial custom patch in order to work properly (these would be found in the folder <MULE_HOME>/lib/user), please verify that the fix is included in this target release by reviewing the corresponding release notes page.

Otherwise, please contact MuleSoft Support by creating a new support case, to request a new patch compatible with the target version. Patch files are version specific and MUST NOT be used in a different runtime version.
3. Download a new copy of your license from the Customer Portal and install it on the target version, by following the instructions described at Installing an Entrerprise License. 4. If you have set any custom configurations to your runtime instance – for example: if you defined a different maximum heap size in the `wrapper.conf` file – you might want to replicate these settings manually. 5. Run your new Mule Server to verify your installation is working as expected. 6. Depending on the circumstances and your current infrastructure, you might want to consider shutting down your previous Mule Server at this point. Please evaluate the impact of this action before proceeding. 7. If you have previously set any environment variables, such as `MULE_HOME` or `PATH`, make sure that they are now pointing to the new Runtime’s installation path. 8. Deploy your applications to your new Mule Server. ## [](#mulerunvers)Mule Runtime Version on Runtime Manager
To migrate following these steps, you must have the Runtime Management Agent installed. The agent comes bundled with Mule runtime as of version 3.6.0 and later. In case you’re migrating from a Mule runtime version that is older than that, you must do this migration manually.
To ensure that you’ll have less downtime and an easier backup route, we recommend that you initially install your new Mule Runtime on a separate server from where you have your current Mule Runtime installed. That way you can set everything up and only then decouple the old server and initiate the new one.
To migrate your Mule servers on-premises that are being managed through Runtime Manager, you must perform these steps on each: 1. Go through steps 1 through to 5 of the previous section, [Mule Standalone Runtime Version](#mule-standalone-runtime-version) 2. Copy the following three files from the path `/conf` from your old Mule installation into the same on the new installation: - `mule-agent.yml` - `mule-agent.jks` - `truststore.jks` and/or `anypoint-truststore.jks` 3. Copy the mule-agent-plugin folder from the path `/plugins` from your old Mule installation into the same on the new installation. 4. Open a terminal window and navigate to the `/bin` of your new Mule installation. Once there, run the following command: amc\_setup -U Through executing this command, you’re installing the latest version of the Runtime Manager Agent on your Mule runtime, which is assured to be compatible with your target runtime version. The files you copied from your old installation hold all of the configuration information that registers the Mule instance on Runtime Manager, so no further steps should be needed. Even when you’re installing your new Mule runtime version on another server or VM, the copied configuration files should suffice to smoothly transition the Mule instance’s identity on the Runtime Manager. If your origin server had apps that were deployed to it through the Runtime Manager, there’s no need to manually copy these, as they automatically upload to your new server when instructed to deploy them through Runtime Manager.

Applications must be running and showing as Started in Runtime Manager. This process does not migrate stopped Applications.
5. At this point the Mule server is already updated to the target version. Updating the Mule applications that are deployed to it is optional. If wish to do so to take full advantage of the features of the target runtime, then you must also: 1. Follow the steps in [Application Runtime Version](#application-runtime-version) to update your application. 2. Find the application on the **Applications** tab on Runtime Manager and click **Choose File** to [upload](https://docs.mulesoft.com/jp/runtime-manager/managing-deployed-applications#updating-your-application) the new Mule Deployable Archive (.zip file). ## [](#upgrade-the-mule-runtime-version-in-a-runtime-manager-server-group)Upgrade the Mule Runtime Version in a Runtime Manager Server Group Follow these steps to upgrade the Mule version in a Runtime Manager server group: 1. Go to Anypoint Runtime Manager. 2. Switch to the corresponding environment. 3. Select **Servers** in the navigation menu. 4. Select the server group to update. 1. In the server group dashboard, select the **Servers** tab and select the server to upgrade. 2. In the actions dropdown menu, select **Shutdown**. 3. Repeat the previous two steps for each server in your server group. 5. Open a terminal in the local machine that hosts your Mule instance. 6. If your Runtime Manager agent version is earlier than 1.12.0, upgrade to the latest version. Go to the current Mule Home directory and run the following commands: `cd ${MULE-3.8.4_HOME}/bin` `cp ~/Downloads/agent-setup-1.15.3.zip .` `unzip agent-setup-1.15.3.zip` `./amc_setup -U` 7. Go to the target directory for the new Mule runtime version and install it: `cd ${MULE-3.9.5_DIRECTORY}` `cp ~/Downloads/mule-ee-distribution-standalone-3.9.5.zip .` `unzip mule-ee-distribution-standalone-3.9.5.zip` 8. Install the latest agent version: `cd mule-enterprise-standalone-3.9.5/bin` `cp ~/Downloads/agent-setup-1.15.3.zip .` `unzip agent-setup-1.15.3.zip` `./amc_setup -I` `rm ../conf/mule-agent.yml` 9. Copy the following files from the previous Mule runtime `/conf` directory to the new Mule runtime `/conf` directory: - All YAML files (`*.yml`) - All keystore files (`*.jks`) 10. Confirm that the DNS configured in `mule-agent.yml` has the following values: websocket.transport: consoleUri: wss://runtime-manager.anypoint.mulesoft.com:443/mule authenticationProxy: endpoint: https://data-authenticator.anypoint.mulesoft.com 11. If you installed domains in your previous Mule instance, copy those domains to your new Mule instance: `cp -R ${MULE-3.8.4_HOME}/domains${MULE-3.9.5_HOME}/domains` 12. Start Mule: `cd ${MULE-3.9.5_HOME}/bin` `./mule start` 13. Go to Runtime Manager to confirm that your Mule applications are deployed and displayed as **Running**. ## [](#upgrading-a-runtime-manager-cluster)Upgrading a Runtime Manager Cluster
Copy the mule-cluster.properties file located in the $MULE_HOME/.mule/ directory from your old Mule installation in the same folder on the new installation to configure the Mule runtime instance to work as a cluster node.
Zero downtime cannot be guaranteed when migrating clusters to another version. At some point during the migration the cluster is in a mixed state, with coexisting nodes running two different versions. This might lead to incompatible communication protocols between Hazelcast instances. When such errors occur, every node in the cluster must be shut down to proceed with the migration. ## [](#mule-management-console-versions)Mule Management Console Versions
Note that unless instructed otherwise, you need to upgrade your MMC version to handle the corresponding Mule Runtime. See our policies regarding MMC versioning. Keep in mind that Mule versions prior to 3.5 aren’t supported on MMC.
For each of the servers that you manage through MMC, go through steps 1 through to 5 of the section, [Mule Standalone Runtime Version](#mule-standalone-runtime-version) If you use default persistence on MMC, the recommended way to migrate to a newer MMC version is to perform a clean install of MMC and then register your existing Mule Servers to this new version. In that case, before installing the new version you must: 1. Disband any existing cluster (if any). 2. Unregister all your servers from the old MMC version. 3. Undeploy the previous MMC version from your servlet `container/application` server. 4. Delete the `mmc-data` folder (after making a backup of it) On the other hand, if you prefer to perform an upgrade directly, once you have the latest copy of the MMC `.war` file (available for download through our Support Center), you must then follow these steps: 1. Stop your application server (E.g: Tomcat). 2. In case you have enabled LDAP support and/or configured an External Database, you must backup all the custom configuration files ( see the [Backing up MMC Configuration Files](#backing-up-mmc-configuration-files) section below). 3. Uncompress the recently downloaded MMC .war file (you can simply manually change the .war extension to .zip and it can then be handled by any software that supports the .zip extension). 4. Replace the configuration files on this new MMC version with the files that you backed up from the older version in the previous step. 5. Pack/Compress the folder contents back, and make sure its extension is `.war` (simply rename the file’s extension, if necessary). 6. Start you application server and undeploy the previously installed MMC version. 7. Restart your application server and deploy the new version of MMC. ### [](#backing-up-mmc-configuration-files)Backing up MMC Configuration Files
The following information applies to MMC versions 3.4.2 and 3.5.x onwards to the latest.
The following files need to be backed up from your current MMC installation in order to preserve any custom configuration it may have, such as LDAP support and External Database configurations: 1. `/WEB-INF/web.xml` 2. `/WEB-INF/classes/META-INF/mmc-ldap.properties` 3. `/WEB-INF/classes/META-INF/databases/-.properties`
The <MMC_HOME> path could either refer to the copy of your custom/"already configured" MMC .war file you are currenlty deploying, or to the current exploded MMC’s application folder at your application server application directory.

Please note that these are only configuration files, by backing them up you are NOT preserving the current state of your MMC.

Make sure that MMC and the application servers are not running at the moment you back these files up
### [](#mmc-agent-version)MMC Agent Version Also, for earlier MMC versions than 3.4.0, make sure the version of the Mule Agent you use is also compatible with your target Runtime version. For MMC Agent versions, the rule of thumb is the following: For Mule versions 3.4.0 and later: - The MMC Console (or Server) version should be greater or equal to the ESB version. - Since the MMC Agent comes bundled with the Mule Runtime, there is no need to download it separately. If the MMC version is later than the ESB version, the bundled agent works transparently and there is no need to download it separately. For Mule versions earlier than 3.4.0: - The MMC Agent version should be the same as the Mule Runtime version. - The MMC Console (or Server) version should be greater or equal to the Runtime version. ### [](#upgrading-an-mmc-cluster-with-zero-downtime)Upgrading an MMC Cluster With Zero Downtime
These steps are valid only for clusters created with MMC.
To achieve a zero downtime upgrade you need to have an external load balancer and set up two different clusters (it is not possible to have a cluster with mixed Mule Runtime versions). You need to implement the following procedure: 1. Install the new Mule Runtime in all of the servers. 2. Configure these new Mule instances as members of a different cluster. 3. Node by node, do the following: 1. Remove the old Mule instance from the load balancer so it won’t receive new invocations. 2. Shut down the old Mule instance. 3. Start up the new Mule instance. 4. Deploy all the applications to this new Mule instance. 5. Register the new Mule instance to the load balancer. ## [](#see-also)See Also - [Known Issues](https://help.salesforce.com/s/issues) # Upgrading Mule Runtime Engine (Versions 4.x to 4.n) To upgrade your current Mule instance to a later release of Mule runtime engine (version 4.x), you must follow some best practices. The following steps and recommendations help you to: - Upgrade your standalone Mule instances. - Upgrade your on-premises Mule instances managed through Runtime Manager. - Change the Mule version used to build your Mule applications, if necessary. To change the Mule runtime engine version of your CloudHub workers, you need to use the [runtime version drop-down box](https://docs.mulesoft.com/cloudhub/deploying-to-cloudhub#runtime-tab) in the application settings deployment configuration page. ## [](#ensuring-mule-application-compatibility)Ensuring Mule Application Compatibility When you create a Mule application, you select the Mule runtime engine version that your application is intended to run on. This is the target Mule version of an application. Because Mule runtime engine uses semantic versioning (MAJOR.MINOR.PATCH), Mule applications are: - Rarely compatible between _major_ releases (3.9.3 to 4.1.0, for example). - Potentially compatible between _minor_ releases (4.1.0 to 4.2.0, for example). - Fully compatible between _patch_ releases (4.1.4 to 4.1.5 for example). Note that Mule provides a feature flagging mechanism that enables Mule applications to change the behavior of the Mule instance depending on the minimum Mule version (`minMuleVersion`). This feature ensures backward compatibility because it enables Mule applications to continue working on later Mule runtime versions, while new Mule applications can benefit from the latest bug fixes implemented in the Mule instance. For details, see [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging). Read the [release notes](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb) for the Mule runtime engine version that you want to upgrade to and verify if you must make any compatibility changes to your Mule applications. MuleSoft recommends executing a regression test cycle to validate compatibility between minor releases. For Mule 4.5 and later, the version naming convention for CloudHub, CloudHub 2.0, and Runtime Fabric changes following the schema for the new release channels, Edge and Long-term Support (LTS). _Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\] : Build\[numeric\] Channel\[e for edge, nothing for LTS\]_ Here are examples of the version numbers: - Edge: 4.5.0:1e - Edge: 4.6.0:1e - LTS: 4.6.0:1 In the case of Standalone (On-Premises), the Mule runtime versioning changes from date-based, for example, `4.4.0-20230317` to semVer as: _Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\]_ Here are examples of the version numbers: - 4.5.1 - 4.5.2 - 4.5.3 See [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence). ### [](#changing-the-target-mule-version-of-your-mule-application)Changing the Target Mule Version of your Mule Application In case you need to change your Mule application’s target Mule version, follow these steps: 1. [Download the desired Mule runtime engine](https://docs.mulesoft.com/studio/studio-update-sites#mule-runtimes-for-anypoint-studio-update-site) in Anypoint Studio so that you can select that version in the IDE. 2. For every application that you upgrade: 1. [Import the application](https://docs.mulesoft.com/studio/import-export-packages#importing-projects-to-studio) to Anypoint Studio as a Mule project. 2. During the import process remember to change the target Mule version by selecting it from the **Server Runtime** menu. ![updating mule versions 415](/mulesoft/current/ja-jp/release-notes/_images/mule-runtime/updating-mule-versions-415.png) 3. Make any other changes necessary to ensure compatibility with the Mule version you are transitioning to. 4. [Export your project](https://docs.mulesoft.com/studio/import-export-packages#exporting-projects-from-studio) as a Mule Deployable Archive (`.jar` file). 5. Edit the `pom.xml` file to make the `muleVersion` property value match the target Mule version. After you have successfully built the Mule Deployable Archives (`.jar` files) with the new target Mule version, and you have applied any other necessary changes to ensure compatibility, you can move on to upgrading the corresponding Mule runtime engine instances. ## [](#upgrading-a-standalone-mule-instance)Upgrading a Standalone Mule Instance Use the Mule upgrade tool to automate the upgrade process of your local Mule instances. Visit [Mule upgrade tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) for installation and usage instructions. Optionally, you can also perform a completely manual update of your Mule instances. To ensure less downtime and easier backups during manual upgrades, first install the new Mule runtime engine on a separate server from that on which your current Mule runtime engine is installed. That way you can set everything up and only then initiate the new Mule instance and decouple the previous one.

If you are upgrading Mule in the same server or virtual machine, ensure that you remove the Mule service or daemon before you install the new Mule runtime engine as a service.
### [](#steps-to-manually-upgrade-the-mule-instance)Steps to Manually Upgrade the Mule Instance 1. From the Customer Portal, download the Mule runtime engine version you want to upgrade to. 2. If you run Mule as a service, install the new Mule version on a different server or virtual machine: - `$MULE_HOME\bin\mule.bat install` on Windows systems - `$MULE_HOME/bin/mule install` on Linux/Unix systems 3. Download a new copy of your license from the Customer Portal and install it on the new Mule instance (see [Installing an Enterprise License](https://docs.mulesoft.com/on-premises/latest/installing-an-enterprise-license) for instructions). 4. If you have custom configurations in your previous Mule instance (for example, if you defined a different maximum heap size in the `wrapper.conf` file), replicate these settings in the new Mule instance. 5. [Run your new Mule instance](https://docs.mulesoft.com/on-premises/latest/starting-and-stopping-mule-esb#running-mule) to verify that your installation is working as expected. 6. After considering possible negative impact, you can shut down your previous Mule instance at this point. 7. If you set environment variables such as `MULE_HOME` or `PATH`, verify that they point to the new Mule runtime engine’s installation path. 8. Deploy your applications to your new Mule instance. ## [](#mulerunvers)Upgrading an On-Premises Mule Instance Managed Through Runtime Manager Use the Mule upgrade tool to automate the upgrade process of your local Mule instances. Visit [Mule upgrade tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) for installation and usage instructions. Optionally, you can also perform a completely manual update of your on-premises Mule instances. To ensure less downtime and easier backups, first install the new Mule runtime engine on a separate server from that on which your current Mule runtime engine is installed. That way you can set everything up. Shut down the previous Mule instance and only then initiate the new Mule instance. To manually migrate following these steps, you must have the [Runtime Manager Agent](https://docs.mulesoft.com/jp/runtime-manager/runtime-manager-agent) installed. ### [](#steps-to-manually-upgrade-the-mule-instance-2)Steps to Manually Upgrade the Mule Instance 1. Go through steps 1 through to 5 of the previous section, [Upgrading a Standalone Mule Instance](#upgrading-a-standalone-mule-instance). 2. Copy the following three files from `/conf` from your previous Mule instance into the same folder on the new Mule instance: - `mule-agent.yml` - `mule-agent.jks` - `truststore.jks` and/or `anypoint-truststore.jks` 3. Copy the `mule-agent-plugin` folder from `/server-plugins` from your previous Mule instance into the same folder on the new Mule instance. 4. Shut down the previous Mule instance. 5. Open a terminal window and navigate to the `/bin` directory of your new Mule instance. 6. Run the following command: amc\_setup -U This command installs the latest version of the Runtime Manager Agent on your new Mule instance, ensuring compatibility. The files you copied from your previous Mule instance hold all of the configuration information to register the new Mule instance on Runtime Manager. Even when you’re installing your new Mule version on another server or VM, the copied configuration files should suffice to smoothly transition the Mule instance’s identity on Runtime Manager. If your previous Mule instance has apps deployed through Runtime Manager, there’s no need to manually copy them, as they automatically upload to your new Mule instance. This process automatically redeploys the applications to the new instance. If your previous Mule instance has apps that were manually deployed, you need to manually redeploy them.

Applications must be running and showing as Started in Runtime Manager. This process does not migrate stopped Applications.
7. At this point, your Mule instance is upgraded to the desired Mule version. Updating the target Mule version of your deployed applications is optional. If you decide to do so, then you must also: 1. Follow the steps in [Changing the Target Mule Version of your Mule Application](#changing-the-target-mule-version-of-your-mule-application). 2. Find the application on the **Applications** tab on Runtime Manager and click **Choose File** to [upload](https://docs.mulesoft.com/jp/runtime-manager/managing-deployed-applications#updating-your-application) the new Mule Deployable Archive (`.jar` file). ### [](#considerations-about-clusters)Considerations About Clusters After you complete the manual upgrade steps for your on-premises Mule instance, copy the `mule-cluster.properties` file from folder `/.mule` in the previous Mule instance to the same folder in the new Mule instance. If the `.mule` folder does not exist in the new Mule instance, create the folder and then copy the file. Zero downtime cannot be guaranteed when upgrading the Mule runtime engine version of your Runtime Manager clusters. At some point during the upgrade, the cluster is in a mixed state, with coexisting nodes running two different Mule versions. This might lead to incompatible communication protocols between Hazelcast instances. When such errors occur, every node in the cluster must be shut down to proceed with the upgrade. ## [](#upgrade-the-mule-runtime-version-in-a-runtime-manager-server-group)Upgrade the Mule Runtime Version in a Runtime Manager Server Group Follow these steps to upgrade the Mule version in a Runtime Manager server group: 1. Go to Anypoint Runtime Manager. 2. Switch to the corresponding environment. 3. Select **Servers** in the navigation menu. 4. Select the server group to update. 1. In the server group dashboard, select the **Servers** tab and select the server to upgrade. 2. In the actions dropdown menu, select **Shutdown**. 3. Repeat the previous two steps for each server in your server group. 5. Open a terminal in the local machine that hosts your Mule instance. 6. If your Runtime Manager agent version is earlier than 2.2.0, upgrade to the latest version. Go to the current Mule Home directory and run the following commands: `cd ${MULE-4.1.5_HOME}/bin` `cp ~/Downloads/agent-setup-2.4.20.zip .` `unzip agent-setup-2.4.20.zip` `./amc_setup -U` 7. Go to the target directory for the new Mule runtime version and install it: `cd ${MULE-4.3.0_DIRECTORY}` `cp ~/Downloads/mule-ee-distribution-standalone-4.3.0.zip .` `unzip mule-ee-distribution-standalone-4.3.0.zip` 8. Install the latest agent version: `cd mule-enterprise-standalone-4.3.0/bin` `cp ~/Downloads/agent-setup-2.4.20.zip .` `unzip agent-setup-2.4.20.zip` `./amc_setup -I` `rm ../conf/mule-agent.yml` 9. Copy the following files from the previous Mule runtime `/conf` directory to the new Mule runtime `/conf` directory: - All YAML files (`*.yml`) - All keystore files (`*.jks`) 10. Confirm that the DNS configured in `mule-agent.yml` has the following values: websocket.transport: consoleUri: wss://runtime-manager.anypoint.mulesoft.com:443/mule authenticationProxy: endpoint: https://data-authenticator.anypoint.mulesoft.com 11. If you installed domains in your previous Mule instance, copy those domains to your new Mule instance: `cp -R ${MULE-4.1.5_HOME}/domains${MULE-4.3.0_HOME}/domains` 12. Start Mule: `cd ${MULE-4.3.0_HOME}/bin` `./mule start` 13. Go to Runtime Manager to confirm that your Mule applications are deployed and displayed as **Running**. ## [](#upgrading-from-mule-4-2-or-4-1-to-mule-4-3-or-later)Upgrading from Mule 4.2 or 4.1 to Mule 4.3 or Later If you are upgrading from Mule 4.2.x or 4.1.x to Mule 4.3.x or later Mule 4 releases, take the following actions: - If no custom threading settings are applied (either through `scheduler-pools.conf` or directly in the Mule app), then no action is required. - If custom threading configurations are applied, test your Mule applications using the default configuration. Because of the UBER pool strategy and other performance updates implemented in Mule 4.3, you might not need custom threading configurations. - If tests confirm that a custom configuration is still necessary, a problem might exist with resource management in the application, one of the application dependencies, or the Mule instance. ## [](#see-also)See Also - [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) - [Mule Standalone Installation](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task) - [Runtime Manager](https://docs.mulesoft.com/jp/runtime-manager/) - [Known Issues](https://help.salesforce.com/s/issues) # Usage Reports Release Notes These release notes reflect enhancements, changes, and bug fixes for Anypoint Platform usage reports. ## [](#july-28-2026)July 28, 2026 ### What’s New - Mule Credits usage is now available with granular visibility in Usage Reports by usage type, business group, and application. Use Salesforce Digital Wallet as the source of truth for finalized Mule Credits totals, statements, and overage billing outcomes. For more information, see [general::mule-credits-usage-and-rates.adoc](#general::mule-credits-usage-and-rates.adoc) ## [](#july-27-2026)July 27, 2026 ### What’s New - CloudHub vCore usage is now available in Usage Reports. You can view combined vCore consumption across CloudHub and CloudHub 2.0 deployments, including peak usage at the organization level and per-application details such as deployment platform, Horizontal Pod Autoscaling status, and vCore allocation. For more information, see [CloudHub vCore Usage](https://docs.mulesoft.com/jp/general/usage-metrics#cloudhub-vcore-usage). ## [](#may-19-2026)May 19, 2026 ### What’s New - Mule Credits is now available on Salesforce Digital Wallet. With Digital Wallet, you can track daily and monthly consumption against your remaining capacity, identify usage trends for better budgeting and buying decisions, and configure proactive custom notifications to reduce surprises. Mule Credits is available with MuleSoft Integration, MuleSoft Automation, MuleSoft AI & API Management, Agent Fabric, and MuleSoft All-Access License. The usage types available to you depend on your subscription plan. For more information, see: - [general::mule-credits-usage-and-rates.adoc](#general::mule-credits-usage-and-rates.adoc) - [Digital Wallet-Enabled Consumption-Based Products](https://help.salesforce.com/s/articleView?id=xcloud.wallet_enabled_products_rate_cards.htm&type=5) ## [](#march-30-2026)March 30, 2026 ### What’s New - Usage reports now include model proxy usage reports to track the number of tokens your model proxy consumes from an LLM Provider. ## [](#march-17-2026)March 17, 2026 ### What’s New - MuleSoft Automation Credits 3.0 is now available in Salesforce Digital Wallet. With this launch, you can now track daily and monthly consumption against your remaining capacity, identify usage trends for better budgeting and buying decisions, and configure proactive custom notifications to reduce surprises. Automation Credits 3.0 includes MuleSoft for Flow: Integration, Anypoint IDP, and MuleSoft for Flow: IDP. Detailed breakdowns of your product consumption are also available in Digital Wallet.
MuleSoft Composer and Robotic Process Automation (RPA) are not included in Automation Credits 3.0. As of February 18, 2026, Flow Orchestration is included and don’t consume Automation Credits in 3.0.
- Documentation for [general::automation-credits-usage-and-rates.adoc](#general::automation-credits-usage-and-rates.adoc), previously distributed across Composer, IDP, and RPA documentation, is now available in [使用状況レポート](https://docs.mulesoft.com/jp/general/usage-reports). This consolidation provides a single location for all automation credits information. For more information, see: - [general::mulesoft-automation-credits-3-0.adoc](#general::mulesoft-automation-credits-3-0.adoc). - [Digital Wallet-Enabled Consumption-Based Products](https://help.salesforce.com/s/articleView?id=xcloud.wallet_enabled_products_rate_cards.htm&type=5) ## [](#october-13-2025)October 13, 2025 ### What’s New - Starting in October, new billable usage types for Flex Credits are available in connected Salesforce orgs. If your Anypoint Platform organization has a tenant relationship established with a Salesforce org and Agentforce is enabled, calls to the large language model (LLM) gateway will now consume Flex Credits for applicable AI features. If the connected Salesforce org currently has one of the Salesforce Flex Foundation, Agentforce 1 Edition or Agentforce add-on licenses, calls to the large language model (LLM) gateway will now consume Flex Credits. If you’re using Conversations for the Agentforce services, you’ll continue to consume Einstein Requests.
If your Anypoint Platform organization is connected to a Salesforce org that doesn’t have Flex Credits entitlement, Einstein Requests continue to be consumed for applicable AI features.
Currently, Einstein Requests consumption is based on calls made to the LLM gateway. To support this change, new Flex Credits usage types are available for AI usage. - Starter Prompts - Standard Prompts - Basic Prompts - Advanced Prompts ### [](#whats-changing)What’s Changing - Einstein Requests (ERs) are being unmetered for Anypoint Code Builder, Exchange AI documentation generation, and IDP, effective October 2025. This means Einstein Requests are no longer needed to use AI functionality in these products. - For Intelligent Document Processing (IDP), effective October 2025: - The per page price for Automation Credits 2.0 is being raised from 25 Automation Credits per page to 30 Automation Credits per page. - The per page price for Automation Credits 1.0 is being raised from 1 MuleSoft Automation Credit = 6 IDP document pages to 1 MuleSoft Automation Credit = 5 IDP document pages. For more information, see: - [Flex Credits Billable Usage Types](https://help.salesforce.com/s/articleView?id=ai.usage_flex_credits.htm&type=5). - [Einstein Requests Billable Usage Types](https://help.salesforce.com/s/articleView?id=ai.generative_ai_usage_einstein_requests.htm&type=5). - [Large Language Model Support](https://help.salesforce.com/s/articleView?id=ai.generative_ai_large_language_model_support.htm&type=5). ## [](#august-19-2025)August 19, 2025 ### What’s New - The usage report data now refreshes twice a day. Daily and month-to-date usage reports show updated information multiple times throughout the day and are subject to change. This gives you more current insights into your consumption. For more information, see [使用状況レポート](https://docs.mulesoft.com/jp/general/usage-reports). ## [](#july-7-2025)July 7, 2025 ### What’s New - Alerts for usage reaching 80% and 90% of the contractual entitlement are now sent automatically to the primary billing contact email address. The primary billing contact gets alerts monthly once thresholds are reached. For more information, see the [Salesforce Usage Alerts FAQ](https://help.salesforce.com/s/articleView?id=004811177&type=1) knowledge article. ## [](#june-26-2025)June 26, 2025 ### What’s New - Anypoint MQ and Object Store v2 metrics are now available in [使用状況レポート](https://docs.mulesoft.com/jp/general/usage-reports) with historical data. - Anypoint MQ reports message units, message bytes, API requests, and messages received. - Object Store v2 reports effective API requests. For more information about MQ and OS metrics, see: - [Anypoint MQ Usage](https://docs.mulesoft.com/jp/general/usage-metrics#anypoint-mq-usage) - [Object Store Usage](https://docs.mulesoft.com/jp/general/usage-metrics#object-store-usage) ## [](#june-17-2025)June 17, 2025 ### What’s New - The Anypoint Usage API is now available on Anypoint Exchange to access monthly and daily usage metrics. For more information, see [Usage API](https://docs.mulesoft.com/jp/general/usage-reports#usage-api). ## [](#june-3-2025)June 3, 2025 ### What’s New - The user icon dropdown menu option for **Usage** is renamed to **Usage Reports**. For more information, see [Access Usage Reports](https://docs.mulesoft.com/jp/general/usage-reports#access-usage-reports). ## [](#april-1-2025)April 1, 2025 ### What’s New - Usage Reports are now available for hybrid standalone deployments. To view your hybrid standalone deployment flows and messages, see [Supported Mule Runtime Versions](https://docs.mulesoft.com/jp/general/usage-reports#supported-mule-runtime-versions) for information about upgrading your applications. In a hybrid standalone deployment, you host Mule runtime engine and its services in an environment that you manage. The Mule runtime server can run on a physical server, a virtual machine, or within a third-party cloud installation. ## [](#march-18-2025)March 18, 2025 ### What’s New - The usage dashboard includes new metrics for Flex Gateway: - Gateway Type Gateway type of the Flex Gateway registered. - Data Egress (GB) Total amount of outbound data in gigabytes (GB) transmitted by the Flex Gateway egress to upstream services. For more information about Flex Gateway usage metrics, see [Flex Gateway Usage](https://docs.mulesoft.com/jp/general/usage-metrics#flex-gateway-usage). ## [](#december-9-2024)December 9, 2024 ### What’s New - Usage Reports are now available on Hyperforce. For details, refer to [Hyperforce Release Notes](https://docs.mulesoft.com/jp/release-notes/hyperforce/hyperforce-release-notes). For more information, see: - [Usage Reports on Hyperforce](https://docs.mulesoft.com/jp/general/usage-reports#usage-reports-on-hyperforce) - [Products Available in Usage Reports](https://docs.mulesoft.com/jp/general/usage-reports#products-usage-reports) ## [](#november-15-2024)November 15, 2024 ### What’s New - Daily usage reports are now available for API Manager for APIs in preproduction, production, and for unclassified (not associated with an environment) APIs. - Usage reports for all products are in the new usage reports interface and the legacy view is removed. Historical data for API Manager before September 2024 isn’t available. ## [](#november-6-2024)November 6, 2024 ### What’s New - The usage dashboard includes new metrics that provide details to analyze Runtime Fabric instances and application deployments and let you track, monitor, and govern core usage in hybrid environments: - CPU Limit Tracks the maximum amount of CPU, allocated by the user, that the application can burst to within the shared cluster or Runtime Fabric instance. - Cluster Capacity Shows the capacity of a set of workers or nodes that act as a single deployment target for a Runtime Fabric instance. - The exportable CSV file for Runtime Fabric includes a new column (**RTF Worker Count**). The Runtime Fabric worker count comes from the Runtime Manager configuration defined by the user rather than from the runtime plane. For more information, see [Runtime Fabric Usage Metrics](https://docs.mulesoft.com/jp/general/usage-metrics#rtf-usage-metrics). ## [](#september-26-2024)September 26, 2024 ### What’s New - Daily usage reports and CSV download capabilities are now available. ## [](#may-1-2024)May 1, 2024 ### What’s New - Intelligent Document Processing (IDP) metrics are available in Usage Report ## [](#july-12-2023)July 12, 2023 ### What’s New - You can now view Mule runtime (Flows, Messages, and Data Throughput) metrics with the application and environment names that were previously shown as IDs. ## [](#february-1-2023)February 1, 2023 ### What’s New - Mule runtime (Flows, Messages, and Data Throughput) metrics are available usage reports are available for all customers. - The maximum number of replicas per application deployed to CloudHub 2.0 is now 16 for organizations that have the Anypoint Integration Advanced package or a Platinum or Titanium subscription to Anypoint Platform. ## [](#see-also)See Also - [Usage Reports](https://docs.mulesoft.com/jp/general/usage-reports) - [使用状況レポートのトラブルシューティング](https://docs.mulesoft.com/jp/general/troubleshooting-usage-reports) - [Known Issues](https://help.salesforce.com/s/issues) # Validation Module Release Notes for Mule 4 The Validation module verifies that the content of a message in a Mule flow matches specific criteria. Guide: [Validation Module User Guide](https://docs.mulesoft.com/jp/validation-connector/latest/) ## [](#2-0-12)2.0.12 **October 14, 2026** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-validator:commons-validator library is upgraded to version 1.11.0.

  • The com.google.guava:guava library is upgraded to version 33.7.2-jre.

W-24454150
## [](#2-0-11)2.0.11 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17
## [](#2-0-10)2.0.10 **July 29, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Apache Commons Lang library is upgraded to version 3.20.0.

  • The Google Guava library is upgraded to version 33.6.0-jre.

  • The Mule Scheduler Service library is upgraded to version 1.12.0.

W-23441578
## [](#2-0-9)2.0.9 **March 26, 2026** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Validation All and Validation Any operations now handle concurrent processing correctly when used in a nested configuration. Previously, nesting these operations under heavy load could result in a deadlock, causing application threads to hang and become unresponsive.

W-21671624
## [](#2-0-8)2.0.8 **September 19, 2025** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated org.apache.commons:commons-lang3 from 3.17.0 to 3.18.0.

W-19174581

Updated commons-validator:commons-validator from 1.9.0 to 1.10.0.

W-19174581

Updated com.google.guava:guava from 33.4.6-jre to 33.5.0-jre.

W-19174581

Fixed commons-collections:commons-collections library due to security vulnerabilities.

W-19685569
## [](#2-0-7)2.0.7 **March 26, 2025** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Validation Module enhances error handling to prevent memory leaks in validations across the ALL scope.

W-17328050
## [](#2-0-6)2.0.6 **December 14, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17
## [](#2-0-5)2.0.5 **August 28, 2023** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Internal libraries have been updated.

W-13954776
## [](#2-0-4)2.0.4 **March 7, 2023** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Now the Any and All scopes do not throw NullPointerException when many requests are received in parallel.

W-12566283
## [](#2-0-3)2.0.3 **February 24, 2023** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

When nested validation operations inside the Validation Module All scope fail, they no longer throw null pointer exceptions (NPE).

W-12130090
## [](#2-0-2)2.0.2 **August 16, 2022** ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Operations inside the Any and All scopes are now intercepted during MUnit testing.

W-10900821
## [](#2-0-1)2.0.1 **Apr 27, 2022** ### What’s New - The product now uses more inclusive language. For more information, refer to the [Upgrading Validation Module to 2.0](https://docs.mulesoft.com/jp/validation-connector/latest/validation-module-upgrade) documentation. ### Compatibility
Software Version

Mule

4.4.0 and later

OpenJDK

8 and 11
## [](#2-0-0-deprecated)2.0.0 (Deprecated) **Apr 25, 2022** This version is deprecated. All of the features and fixed issues for this version are in version 2.0.1. ## [](#1-4-7)1.4.7 **June 13, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The Any and All scopes no longer throw NullPointerExceptions when receiving multiple requests in parallel.

W-12566283
## [](#1-4-6)1.4.6 **August 11, 2022** ### [](#compatibility-14)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### [](#fixed-issues-11)Fixed Issues
Issue Resolution ID

Operations inside the Any and All scopes are now intercepted during MUnit testing.

W-10900821
## [](#1-4-5)1.4.5 **Jun 4, 2021** ### [](#compatibility-15)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### [](#new-features-and-enhancements)New Features and Enhancements N/A ### [](#fixed-issues-12)Fixed Issues Upgraded internal dependencies. ## [](#1-4-4)1.4.4 **May 26, 2021** ### [](#minimum-mule-version)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-2)New Features and Enhancements N/A ### [](#fixed-issues-13)Fixed Issues
Issue Description

VAL-58

Updated dependency com.google.guava to 30.1.1-jre.
## [](#1-4-3)1.4.3 **January 29, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-3)New Features and Enhancements N/A ### [](#fixed-issues-14)Fixed Issues
Issue Description

MULE-19139

Fixed an issue where mapped errors are throwing a MULE:UNKNOWN error, instead of the correct name for the error
## [](#1-4-2)1.4.2 **December 02, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-4)New Features and Enhancements N/A ### [](#fixed-issues-15)Fixed Issues
Issue Description

VAL-24

Removed local packages that are exported by Mule runtime engine.
## [](#1-4-1)1.4.1 **October 20, 2020** ### [](#minimum-mule-version-4)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-5)New Features and Enhancements N/A ### [](#fixed-issues-16)Fixed Issues
Issue Description

MULE-18900

Execution of aggregate validations inside foreach hangs if an unexpected error occurs in an inner validation in Mule 4.3 and later versions.
## [](#1-4-0)1.4.0 **November 29, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-6)New Features and Enhancements - The Size validator now takes into account more types of collections. ### [](#fixed-issues-17)Fixed Issues
Issue Description

MULE-16072

validation:validate-size fails with mule-file-connector 1.2.0.
## [](#1-3-0)1.3.0 **October 5, 2018** ### [](#minimum-mule-version-6)Minimum Mule Version Mule 4.1.0 ### [](#new-features-and-enhancements-7)New Features and Enhancements - | MULE-15767 | Added an `any` validator. ### [](#fixed-issues-18)Fixed Issues
Issue Description

MULE-15342

Validation module is-time operation accepted invalid dates.

MULE-14971

DataWeave null output with JSON datatype was not validated as null.
## [](#1-2-2)1.2.2 **July 12, 2018** ### [](#minimum-mule-version-7)Minimum Mule Version Mule 4.1.0 ### [](#new-features-and-enhancements-8)New Features and Enhancements N/A ### [](#fixed-issues-19)Fixed Issues
Issue Description

MULE-15342

Validation module is-time operation accepted invalid dates.
## [](#1-2-1)1.2.1 **March 14, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version Mule 4.1.0 ## [](#1-2-0)1.2.0 **January 31, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version Mule 4.1.0 ### [](#new-features-and-enhancements-9)New Features and Enhancements - Custom Validators are no longer supported since this is covered by the creation of Validators using the SDK. ### [](#fixed-issues-20)Fixed Issues - Remove Custom Validators from the validation module. (MULE-14551) ## [](#1-1-0)1.1.0 **January 22, 2018** ### [](#minimum-mule-version-10)Minimum Mule Version Mule 4.1.0 ### [](#new-features-and-enhancements-10)New Features and Enhancements - Fixed Is Null and Is Not Null validations. ### [](#fixed-issues-21)Fixed Issues - TRAINING: Is Null and Is Not Null validation not working. (MULE-14472) - Validation module exports internal classes. (MULE-14506) ## [](#1-0-0)1.0.0 **November 13, 2017** ### [](#minimum-mule-version-11)Minimum Mule Version Mule 4.0.0 ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Veeva Vault Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Veeva Vault (Veeva Vault Connector) enables you to integrate the Veeva Vault platform with third-party vendors using connector operations in a Mule flow. The connector performs CRUD (Create, Retrieve, Update, Delete), Query, and Export operations on the vault using Veeva Vault APIs. Guide: [Veeva Vault Connector User Guide](https://docs.mulesoft.com/jp/veevavault-connector/latest/) ## [](#1-5-7)1.5.7 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1 and later

OpenJDK

8, 11, and 17

Veeva Vault APIs

18.0-24.1

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
## [](#1-5-6)1.5.6 **August 14, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1 and later

OpenJDK

8, 11, and 17

Veeva Vault APIs

18.0-24.1

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

The json library is upgraded to version 20260719 to address reported security vulnerabilities.

W-23441627
## [](#1-5-5)1.5.5 **July 31, 2026** ### Compatibility
Software Version

Mule

4.1 and later

OpenJDK

8, 11, and 17

Veeva Vault APIs

18.0-24.1

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

The jackson library is upgraded to version 2.22.1 to address reported security vulnerabilities.

W-23623355
## [](#1-5-4)1.5.4 **June 15, 2026** ### Compatibility
Software Version

Mule

4.1 and later

OpenJDK

8, 11, and 17

Veeva Vault APIs

18.0-24.1

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind, jackson-dataformat-xml, jackson-annotations, and jackson-core libraries are upgraded to version 2.18.6.

  • The org.json:json library is upgraded to version 20240205.

W-22925920
## [](#1-5-3)1.5.3 **March 12, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1 and later

OpenJDK

8, 11, and 17

Veeva Vault APIs

18.0-24.1

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
## [](#1-5-2)1.5.2 **September 20, 2023** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

The connector now passes response fields with null values, as it did for Veeva Vault Connector 1.3.4 and earlier.

W-14041593
## [](#1-5-1)1.5.1 **August 15, 2023** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

Errors that receive the WARN response type are now handled as intended.

W-13941310
## [](#1-5-0)1.5.0 **August 11, 2023** ### What’s New - The original Veeva Vault API headers that are received from an underlying HTTP request are now present in the response of every operation and some errors. ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
## [](#1-4-6)1.4.6 **July 18, 2023** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

The WARNING response type is now handled properly in version 23.1 of the Veeva API.

W-13739420
## [](#1-4-5)1.4.5 **June 23, 2023** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

The org.json library is upgraded to version 20230618 to address reported security vulnerabilities.

W-13637107

The jackson-databind library is upgraded to version 2.15.2 to address reported security vulnerabilities.

W-13637107
## [](#1-4-4)1.4.4 **June 12, 2023** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

The Batch Size field in the Query operation is now deprecated.

W-13509061
## [](#1-4-3)1.4.3 **May 15, 2023** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue Resolution ID

You can now use the maximum query string length of 50,000 in the Query operation.

W-13195654
## [](#1-4-2)1.4.2 **October 25, 2022** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue ID

The Jackson Databind library is upgraded from com.fasterxml.jackson.core:jackson-databind:2.13.2.1 to com.fasterxml.jackson.core:jackson-databind:2.13.4.2 to fix reported security vulnerabilities.

W-11853404
## [](#1-4-1)1.4.1 **September 30, 2022** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue ID

Paging did not work correctly with Veeva API v20.3 and later because the paging parameters used were deprecated in those API versions. Now, both the old and new sets of paging parameters are used to support all Veeva API versions.

W-11177312

The parsing error during response validation is now fixed.

W-11729891
## [](#1-4-0)1.4.0 **August 1, 2022** ### What’s New - The connector now supports the OAuth 2.0 / Open ID connection. For more information, refer to the [Veeva Vault Connector Reference](https://docs.mulesoft.com/jp/veevavault-connector/latest/veevavault-connector-reference#config_oauth2-oidc-connection). ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
## [](#1-3-5)1.3.5 **July 21, 2022** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20180130 and later
### Fixed Issues
Issue ID

The session renewal mechanism is no longer faulty. Now, the mechanism is replaced with a more robust way of handling the session renewal using the Mule built-in reconnection strategy.

W-11192788

The JSON parsing error A JSONObject text must begin with '{' at 1 [character 2 line 1] no longer occurs.

W-11192788

Some special characters in a query did not escape correctly which resulted in errors from Veeva. Now, all characters escape correctly, with the exception of the backslash \.

W-11244712

The JSON library is updated to fix a security vulnerability.

W-11202570
## [](#1-3-4)1.3.4 **December 20, 2021** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20170516 and later
### Fixed Issues
Issue ID

The AsyncHttpClient closed unexpectedly.

SE-23580
## [](#1-3-3)1.3.3 **November 15, 2021** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20170516 and later
### Fixed Issues
Issue ID

The connector used a GET operation for query operations, which exceeded the maximum URI length. Now, the connector uses a POST operation for query operations, which does not exceed the maximum URI length.

SE-23301
## [](#1-3-2)1.3.2 **September 29, 2021** ### Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20170516 and later
### Fixed Issues
Issue ID

Reconnection did not work properly as the connector threw an INVALID_SESSION_ID error and a CONNECT_TIMEOUT error.

SE-22748

Uploading documents with the Invoke REST API operation did not work.

SE-22493
## [](#1-3-1)1.3.1 **June 11, 2021** ### [](#compatibility-20)Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20170516 and later
### [](#fixed-issues-16)Fixed Issues - The connector threw an execution error when API v21.1 was used. (SE-21252) - Intermittent execution errors occurred when using the **Invoke REST API** operation. (SE-20175) ## [](#1-3-0)1.3.0 **February 8, 2021** ### [](#compatibility-21)Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20170516 and later
### [](#new-features)New Features The connector now supports dynamic configuration for all connection parameter types. ### [](#fixed-issues-17)Fixed Issues This release contains the following fixed issues: - The Invoke REST API operation was not supporting an attachment response. - The Invoke REST API operation was failing to resolve multiple URI parameters. ## [](#1-2-0)1.2.0 **May 22, 2020** ### [](#compatibility-22)Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20170516 and later
### [](#new-features-2)New Features The Invoke Rest API operation is now supported, which enables the Veeva Vault Rest APIs that don’t have defined operations to be called. ### [](#fixed-issues-18)Fixed Issues This release contains the following fixed issues: - The Export Documents operation ran in an infinite loop when an invalid or deleted document ID was passed. - The Spark Validator operation failed to verify the Spark message if the Spark headers received from the Vault were passed in non-alphabetical order. ## [](#1-1-0)1.1.0 **February 5, 2020** ### [](#compatibility-23)Compatibility
App/Service Version

Mule

4.1 and later

JDK

1.8 and later

Veeva Vault APIs

18.0 and later

Apache Common Language

2.6 and later

JSON libraries

20170516 and later
### [](#new-features-3)New Features The Spark Message Validator operation was implemented to validate and verify Spark messages with a public key and signature received from the vault. ### [](#fixed-issues-19)Fixed Issues This release contains the following fixed issues: - Export Documents operation should return Job results instead of Job Status response. - Get Documents and Get Object Records operations threw an error when the Document or Field properties list was configured as empty or None. ## [](#1-0-3)1.0.3 **August 2019** This is a new release. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # VM Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for VM enables communication between apps or within an app through asynchronous queues. The asynchronous queues can be either transient or persistent. This connector is pre-installed in Anypoint Studio 7 and later. Guide: [VM Connector User Guide](https://docs.mulesoft.com/jp/vm-connector/latest/) ## [](#2-0-3)2.0.3 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-0-2)2.0.2 **July 28, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-0-1)2.0.1 **December 15, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#2-0-0)2.0.0 **July 18, 2018** ### [](#compatibility-4)Compatibility
Software Version

Mule

4.1.0 and later

JDK

8
### [](#features)Features The main difference between this version and previous versions is how the `publish-consume` operation manages errors: - In previous versions, if the flow at the receiving end failed, the operation failed with a `VM:QUEUE_TIMEOUT` error. - In this version, a `VM:PUBLISH_CONSUMER_FLOW_ERROR` is thrown instead, signaling the difference between a timeout and an actual failure. It’s still possible for the `publish-consume` operation to fail with a timeout error if the receiving flow doesn’t fail, but also doesn’t respond in time. ### [](#fixed-issues)Fixed Issues - `validateNoListenerOnQueue` failed with a null pointer exception (NPE) when generating the error message. (MULE-15236) - Listener did not send a response when an error occurred in the flow. (MULE-15217) - `publish-consume` with transactions was broken. (MULE-15214) ## [](#1-1-1)1.1.1 **March 14, 2018** ### [](#compatibility-5)Compatibility
Software Version

Mule

4.1 and later

JDK

8
### [](#fixed-issues-2)Fixed Issues - Added summary to parameters in `Queue Descriptors` and fixed metadata issues with attributes. (MULE-14701) ## [](#1-1-0)1.1.0 **January 27, 2018** ### [](#compatibility-6)Compatibility
Software Version

Mule

4.1 and later

JDK

8
### [](#features-2)Features This release includes the following features: - Added support for message correlation. - Added hinting of available queues in Listener. ### [](#fixed-issues-3)Fixed Issues - VM Connector exported internal classes. (MULE-14444) ## [](#1-0-0)1.0.0 **November 18, 2017** ### [](#compatibility-7)Compatibility
Software Version

Mule

4.0 and later

JDK

8
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Web Service Consumer Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Web Service Consumer (Web Service Consumer Connector) consumes a SOAP web service from a Mule app to acquire data from an external source. Guide: [Web Service Consumer Connector User Guide](https://docs.mulesoft.com/web-service-consumer-connector/latest/) ## [](#2-2-6)2.2.6 **October 14, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The Spring Framework libraries are removed to address reported security vulnerabilities.

W-24406570, W-24440859, W-24456506, W-24456507, W-24468387

The Apache CXF library is updated to version 4.1.9 to address the CVE-2026-65432 and CVE-2026-49875 security vulnerabilities. The connector declares the Apache CXF modules directly so that the fixed CXF version is used by your Mule app. Unneeded transitive OpenSAML dependencies are excluded so that the connector’s dependencies can be resolved from public repositories.

W-24406484, W-23508473
## [](#2-2-5)2.2.5 **October 5, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The Jetty library is upgraded to version 12.1.13 to address CVE-2026-19203.

  • The apache-neethi library is upgraded to version 3.2.4.

  • The slf4j library is upgraded to version 2.0.20.

W-24311747
## [](#2-2-4)2.2.4 **August 25, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

StackOverflowError errors no longer occur when the connector uses dynamic WSDL, service, port, address, or operation configuration after processing a large volume of SOAP calls.

W-23609392

The cxf.version library is upgraded to version 4.2.3 to address the CVE-2026-65432 security vulnerability.

W-23907809
## [](#2-2-3)2.2.3 **August 4, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The apache-neethi library is upgraded to version 3.2.2.

  • The Apache CXF library is upgraded to version 4.1.7.

  • The spring-context, spring-beans, and spring-aop libraries are upgraded to version 6.2.19.

  • The Jetty library is upgraded to version 12.0.36.

W-23623769, W-23647918, W-23460362, W-23572402
## [](#2-2-2)2.2.2 **July 14, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The springframework.version library is upgraded to version 6.2.19 to address the CVE-2026-41848 security vulnerability.

W-23286564
## [](#2-2-1)2.2.1 **June 29, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The org.apache.neethi dependency is upgraded to version 3.2.2 to address reported security vulnerabilities.

W-23155657, W-22835667, W-22996812, W-23139004, W-23137185
## [](#2-2-0)2.2.0 **June 3, 2026** ### What’s New - Web Service Consumer Connector operations that fail because of a security-related cause now raise a new `WSC:SECURITY` error type, which can be handled in `` blocks. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The soap-engine dependency is upgraded to version 2.4.0 with security improvements.

W-21335900
## [](#2-1-4)2.1.4 **May 20, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now preserves the complete <detail> content of SOAP 1.2 faults that contain multiple namespaces and nested elements, so structured error information is no longer lost when accessed programmatically.

W-21461701

The soap-engine dependency is upgraded to version 2.3.2 to fix Jetty vulnerabilities.

W-22392943, W-22489960, W-22489920, W-22489946, W-22489958
## [](#2-1-3-deprecated)2.1.3 (Deprecated) **May 19, 2026** This version is deprecated. All of the features and fixed issues for this version are in version 2.1.4. ## [](#2-1-2)2.1.2 **April 10, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The soap-engine dependency is upgraded to version 2.3.1 to fix the Jetty vulnerability.

W-21809059
## [](#2-1-1)2.1.1 **December 18, 2025** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The soap-engine dependency is upgraded to version 2.1.1 to fix the Angus Mail CVE.

W-20593303
## [](#2-1-0)2.1.0 **December 12, 2025** ### What’s New - The WSS Sign Configuration Adapter type now includes the new **Expand XOP Include** field to define how XOP (XML-binary Optimized Packaging) includes are expanded inline within the SOAP message body. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
## [](#2-0-2)2.0.2 **October 21, 2025** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The springframework.version library is upgraded to version 6.2.11 to address reported security vulnerabilities.

W-19725425
## [](#2-0-1)2.0.1 **September 16, 2025** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The Default HTTP Transport Configuration type no longer corrupts deflated binary attachments when debug logs are enabled.

W-19428838

The commons.lang.version library is upgraded to version 3.18.0 to address reported security vulnerabilities.

W-19174555

The springframework.version library is upgraded to version 6.2.10 to address reported security vulnerabilities.

W-19578330

Web Service Consumer Connector with dynamic configuration no longer leaks CXF DelayedCachedOutputStreamCleaner threads.

W-19258285
## [](#2-0-0)2.0.0 **July 16, 2025** ### What’s New - Web Service Consumer Connector (and its dependencies) are now compilable and compatible only with Java 17. - To align with modern development practices and ensure continued compatibility with secure and supported libraries, Web Service Consumer Connector is upgraded from Spring 5.x to Spring 6.x. For more information about how to upgrade the connector to version 2.0, refer to [Upgrading and Migrating Web Service Consumer Connector to Version 2.2](https://docs.mulesoft.com/web-service-consumer-connector/latest/web-service-consumer-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
## [](#1-12-0)1.12.0 **August 4, 2026** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now preserves complete SOAP 1.2 fault <detail> content for faults with complex multi-namespace and nested elements, so SoapFaultException.getDetail() no longer returns an empty value when structured error information is available.

W-21461701
## [](#1-11-4)1.11.4 **September 16, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Default HTTP Transport Configuration type no longer corrupts deflated binary attachments when debug logs are enabled.

W-19428838

The commons.lang.version library is upgraded to version 3.18.0 to address reported security vulnerabilities.

W-19174555
## [](#1-11-3)1.11.3 **June 30, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The mule-sdk-api library is upgraded to version 0.8.7 because earlier versions do not include a <license> tag in the POM file.

W-18223316
## [](#1-11-2)1.11.2 **May 7, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now improves logs and removes unnecessary warnings.

W-13593144

Web Service Consumer Connector now contains patched Apache CXF to fix security vulnerabilities.

W-18412824
## [](#1-11-1)1.11.1 **March 27, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now contains patched Spring 5.x to fix security vulnerabilities.

W-17918465
## [](#1-11-0)1.11.0 **February 26, 2025** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17440028
## [](#1-10-3)1.10.3 **September 23, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector no longer returns a null error message when a dispatcher exception occurs.

W-16446386
## [](#1-10-2)1.10.2 **August 23, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now uses mule-soap-engine version 1.9.3 to fix a security vulnerability in the cxf-core dependency.

W-16518539
## [](#1-10-1)1.10.1 **August 12, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now uses mule-soap-engine version 1.9.2 to avoid throwing the No Content-Type boundled in the message error. For more information, refer to No Content-Type Boundled in the Message.

W-13628673
## [](#1-10-0)1.10.0 **June 12, 2024** ### What’s New - In the connector configuration, use the new **Security headers order** field to select the order (empty, `TimestampAtEnd`, or `TimestampAtStart`) of outgoing WS-Security tags. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-9-0)1.9.0 **May 3, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-8-8)1.8.8 **May 3, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The following dependencies are upgraded for maintenance:

  • The spring-expression dependency is upgraded to version 5.3.34.

  • The mule-sdk-api dependency is upgraded to version 0.8.2.

W-15438142
## [](#1-8-7)1.8.7 **April 10, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now uses mule-soap-engine version 1.9.1 to address a reported security vulnerability.

W-14979268
## [](#1-8-6)1.8.6 **March 13, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-8-5)1.8.5 **January 31, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

Web Service Consumer Connector now uses mule-soap-engine version 1.8.6 to address a reported security vulnerability.

W-14606069
## [](#1-8-4)1.8.4 **November 28, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later

Java

1.8

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The connector now uses org.apache.santuario:xmlsec:jar:2.3.4 library to address reported security vulnerabilities.

W-14414918
## [](#1-8-3)1.8.3 **August 30, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Internal dependencies that fix vulnerability issues are updated.

W-13971847
## [](#1-8-2)1.8.2 **April 24, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The spring expression library is upgraded to version 5.3.27.

W-13064379
## [](#1-8-1)1.8.1 **March 7, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Web Service Consumer connector has a new system property mule.soap.maxAttributeSize.

The XML parser library has a limit that specifies maximum allowed length (in characters) of attribute values. This limit protects against possible Denial-of-Service (DoS) attacks.

The default limit value is 524288 characters and it is a reasonable default value for normal usage. You can change it to a higher value if input documents can legitimately exceed the default limit, or to a lower value if specific attacks are observed or the system has a lower resource allocation. The maximum value allowed is 2147483647 (Integer.MAX_VALUE in Java). If you set 0 or if you don’t set the property, the connector takes the default value.

W-12429671
## [](#1-8-0-deprecated)1.8.0 (Deprecated) **February 2, 2023** This version is deprecated. All of the features and fixed issues for this version are in version 1.8.1. ## [](#1-7-2)1.7.2 **January 10, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Internal dependencies that fix vulnerability issues are updated.

W-12276489
## [](#1-7-1)1.7.1 **November 3, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Internal dependencies that fix vulnerability issues are updated.

W-11983186
## [](#1-7-0)1.7.0 **October 3, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Web Service Consumer Connector now adds additionalTransportData when throwing exceptions in a failure scenario.

W-11210481

Web Service Consumer Connector now throws the WSC:EMPTY_RESPONSE message instead of WSC:BAD_RESPONSE when mandatory fields are missing from the response (Illegal Empty Response).

W-11058572

Updated internal WSDL parser of the connector.

W-11618208
## [](#1-6-14)1.6.14 **August 9, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

SOAP request compression now works correctly with Web Service Consumer Connector.

W-11399540
## [](#1-6-13)1.6.13 **June 28, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Updated internal dependencies.

W-11357865
## [](#1-6-12)1.6.12 **June 16, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Updated internal dependencies.

W-11227883
## [](#1-6-11)1.6.11 **May 12, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Web Service Consumer Connector no longer throws the message No Content-Type boundled in the message in CloudHub when the web service response contains the Content-type header.

W-10818756
## [](#1-6-10)1.6.10 **April 19, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Internal dependencies updated.

W-10940986
## [](#1-6-9)1.6.9 **February 04, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The connector is now able to decode file attachments using base64 encoding.

WSCC-131
## [](#1-6-8)1.6.8 **January 14, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The connector no longer sets the indentation in the XML header by default, which prevents breaking the digital signature when the header contains a signed SAML assertion.

WSCC-125

Added new property mule.soap.enable.namespaces, which prevents resolving two headers with different namespaces as a duplicated header.

WSCC-124
## [](#1-6-7)1.6.7 **December 3, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

Response message did not contain the proper response data error due to an invalid SOAP response with an empty body.

WSCC-122

Error logged when there are spaces after a response tag.

WSCC-121
## [](#1-6-6)1.6.6 **August 23, 2021** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

A parsing error occurred in the WSDL attachment response enrichment when there was more than one root element in the body of the SOAP response message.

WSCC-120
## [](#1-6-5)1.6.5 **July 29, 2021** ### [](#fixed-issues-41)Fixed Issues - Fixed Web Service Consumer Connector dependencies to run properly on JDK 11. (WSCC-119) ## [](#1-6-4)1.6.4 **March 23, 2021** ### [](#fixed-issues-42)Fixed Issues - Now the MTOM flag affects only outgoing messages because some servers do not manage incoming multi-part messages. Web Service Consumer input messages are treated the same regardless of whether those messages are MTOM or not. ## [](#1-6-3)1.6.3 **January 26, 2021** ### [](#fixed-issues-43)Fixed Issues - Fixed an issue in which mtom input attachment remains inaccessible in responses. ## [](#1-6-2)1.6.2 **December 29, 2020** ### [](#fixed-issues-44)Fixed Issues - Fixed an issue in which large incoming attachments were splitting and not rejoining. (WSCC-104) ## [](#1-6-1)1.6.1 **July 27, 2020** ### [](#features)Features - Added new option to append XML Prolog into the envelope’s body XML content (WSCC-72) ### [](#fixed-issues-45)Fixed Issues - Fixed an issue where messages were mistakenly transformed to UTF, regardless of whether they were raw binary content or text, and caused attachments that were not sent encoded in base64 to be corrupt in the process. (WSCC-76) ## [](#1-6-0-deprecated)1.6.0 (Deprecated) This version is deprecated. All of the features and fixed issues for this version are in version 1.6.1. ## [](#1-5-8)1.5.8 **March 30, 2020** ### [](#fixed-issues-46)Fixed Issues - Fixed issue that caused the connector to retry, get, and parse an invalid WSDL. (MULE-18024) - Fixed an issue that may cause the connector initialization to fail randomly. (MULE-18175) ## [](#1-5-7)1.5.7 **March 9, 2020** ### [](#fixed-issues-47)Fixed Issues The issue that caused the connector to fail to parse the WSDL when encountering an operation that didn’t have an input message is fixed. (MULE-18038) ## [](#1-5-6)1.5.6 **March 4, 2020** ### [](#fixed-issues-48)Fixed Issues - Fixed issue that caused the connector to fail when using MTOM with a signed request. (MULE-17957) ## [](#1-5-5)1.5.5 **March 2, 2020** ### [](#features-2)Features - Removes guava dependency and start using java classes instead. (MULE-18126) ## [](#1-5-4)1.5.4 **January 15, 2020** ### [](#fixed-issues-49)Fixed Issues - Fixed issue that caused consumption of unnecesary amounts of memory. (MULE-17937) - Fixed issue that caused the connector to fail to find attachments that were not mandatory. (MULE-17928) ## [](#1-5-3)1.5.3 **December 17, 2019** ### [](#fixed-issues-50)Fixed Issues - Added caching to resources. (MULE-17742) ## [](#1-5-2)1.5.2 **November 19, 2019** ### [](#fixed-issues-51)Fixed Issues Replace `CID:` with the corresponding XML element when creating a SOAP request. (MULE-17675) ## [](#1-5-1)1.5.1 **September 17, 2019** ### [](#fixed-issues-52)Fixed Issues Fixed issue that caused streams to close before the SOAP responses were consumed. (MULE-17222) ## [](#1-5-0)1.5.0 **September 2, 2019** ### [](#features-3)Features Added the ability to configure Web Services Security attributes **Actor** and **Must understand**. (MULE-17319) ## [](#1-4-1)1.4.1 **August 13, 2019** ### [](#fixed-issues-53)Fixed Issues - Error when processing a SOAP response encoded with an encoding different that the one used by Mule. (MULE-17272) - The HTTP content-type header was not included on an HTTP request that is made to consume an operation. (MULE-17283) - WSDL was not parsed when an operation was missing bindings for input or output. (MULE-17302) ## [](#1-4-0)1.4.0 **July 16, 2019** ### [](#features-4)Features Added the ability to configure verification of a web service security timestamp on responses. (MULE-17106) ### [](#fixed-issues-54)Fixed Issues None ## [](#1-3-4)1.3.4 **July 12, 2019** ### [](#fixed-issues-55)Fixed Issues Fixed issue that caused the HTTP transport configuration to not be honored at design time. (MULE-16977) ## [](#1-3-3)1.3.3 **June 18, 2019** ### [](#fixed-issues-56)Fixed Issues Fixed issue that caused performance degradation when using an expression in a configuration. (MULE-16970) ## [](#1-3-2)1.3.2 **May 3, 2019** ### [](#fixed-issues-57)Fixed Issues - Fixed issue that caused metadata not being collected when the location of the WSDL was a relative path. (MULE-16876) - Fixed issue that caused the signature and the timestamp to be incorrectly swapped when signing the timestamp. (MULE-16834) - Fixed issue that caused the operation not being loaded on Studio. (MULE-16931) ## [](#1-3-1)1.3.1 **April 4, 2019** ### [](#fixed-issues-58)Fixed Issues - Fixed issue that caused the WSDL parsing to fail when an import with HTTPS was included in the WSDL. (MULE-16623) - Fixed issue that caused the connector to fail finding attachments when an element has a namespace. (MULE-16592) - Fixed issue that caused the connector to be unable to decrypt responses using the Key Transport Algorithm RSA 1.5. (MULE-16605) - Fixed issue that caused the connector to be unable to generate the signature value, CXF library version upgraded. (MULE-16637) ## [](#1-3-0)1.3.0 **February 11, 2019** ### [](#features-5)Features - Able to configure encryption algorithms. (MULE-16099, MULE-16099) - Able to configure signature algorithm. (MULE-16100, MULE-11299) - Able to configure which parts of the request should be signed or encrypted. (MULE-16094) - New web service consumer connector icon. (MULE-16376) ### [](#fixed-issues-59)Fixed Issues - Expose HTTP status code. (MULE-16333) - Fixed issue that caused NPE when a SOAP attachment didn’t include a MIME type. (MULE-16441) - Fixed issue that cause the execution of MUnit test to hang if a HTTP:CONNECTIVITY error is thrown. (MULE-16221) ## [](#1-2-4)1.2.4 **January 29, 2019** ### [](#fixed-issues-60)Fixed Issues Update net.sf.Saxon to 9.9.1-1. (MULE-16393) ## [](#1-2-3)1.2.3 **January 25, 2019** ### [](#fixed-issues-61)Fixed Issues Fixed issue that caused XML Schema choice Element not being handled. (MULE-16235) ## [](#1-2-2)1.2.2 **December 20, 2018** ### [](#fixed-issues-62)Fixed Issues - Fixed issue when parsing a WSDL that imports another WSDL. (MULE-16231) - Fixed issue that caused NPE when configuring invalid headers to the consume operation. (MULE-16177) ## [](#1-2-1)1.2.1 **Nov 12, 2018** ### [](#fixed-issues-63)Fixed Issues - Fixed issue when resolving metadata of a WSDL that contains multiple operations with the same name for different ports. (MULE-15988) - Fixed issue when parsing embedded Base64 attachments. (MULE-15790) ## [](#1-2-0)1.2.0 **October 29, 2018** ### [](#features-6)Features This release includes major performance improvements to resolving values for configurations and DataSense. ### [](#known-issues)Known Issues RPC WSDLs are not supported. ### [](#fixed-issues-64)Fixed Issues - WSC headers metadata is being badly generated. (MULE-15922) - Improve the WSC value provider performance. (MULE-15885) - WSC should allow timeout configuration for default HTTP config. (MULE-15844) - Make WSC take advantage of the metadata cache. (MULE-15551) - Upgrade `commons-lang3` to 3.7. (MULE-15082) - Upgrade Guava to 25.1. (MULE-15079) - WSC cannot load WSDL files inside JAR files. (MULE-14996) ## [](#1-1-1)1.1.1 **March 26, 2018** ### [](#known-issues-2)Known Issues RPC WSDLs are not supported ### [](#fixed-issues-65)Fixed Issues WSC is affected by CVE-2017-9735. (EE-5773) ## [](#1-1-0)1.1.0 **January 19, 2018** ### [](#features-7)Features This release includes the following enhancements, changes, and fixes: - Support for multipart messages - Added configuration hints through Value Providers - Same experience for MTON and Soap with Attachments - Improved UX ### [](#known-issues-3)Known Issues RPC WSDLs are not supported ### [](#upgrade-requirements)Upgrade Requirements Mule 4.1 ### [](#fixed-issues-66)Fixed Issues - WSC Connector exports internal classes. (MULE-14445) - Upgrade to CXF 3.2.1. (MULE-14060) - Correct event is not used when running with custom HTTP transport config. (MULE-14388) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # WebSocket Connection Limit The WebSocket Connection Limit policy limits the number of simultaneous WebSocket connections that each API instance allows. For configuration details, see [WebSocket Connection Limit Policy](https://docs.mulesoft.com/gateway/latest/policies-included-websocket-connection-limit). ## [](#march-17-2026)March 17, 2026 ### What’s New - WebSocket Connection Limit policy implementation version 1.0.0 is now supported by Omni Gateway. - WebSocket Connection Limit policy definition version 1.0.0 is now supported by Omni Gateway. # WebSockets Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for WebSockets (WebSockets Connector) establishes bidirectional and full-duplex communication between a server and client, implements server push notifications, works with the HTTP infrastructure, and removes the need for clients to regularly poll the server for new data. Guide: [WebSockets Connector](https://docs.mulesoft.com/jp/websockets-connector/latest/) Reference: [WebSockets Connector Reference](https://docs.mulesoft.com/jp/websockets-connector/latest/websockets-connector-reference) ## [](#1-0-5)1.0.5 **September 21, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
App/Service Version

Mule

4.2.2 and later

OpenJDK

8, 11, and 17
## [](#1-0-4)1.0.4 **August 17, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
App/Service Version

Mule

4.2.2 and later

OpenJDK

8, 11, and 17
## [](#1-0-3)1.0.3 **June 27, 2026** ### Compatibility
App/Service Version

Mule

4.2.2 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Open Outbound Socket operation now correctly closes the previous connection and retains the new connection when reconnecting with the same socket ID.

W-19389824

WebSockets Connector now uses the retry support from mule-api instead of mule-core if available.

W-19290853
## [](#1-0-2)1.0.2 **March 26, 2025** ### Compatibility
App/Service Version

Mule

4.2.2 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

WebSockets Connector now closes duplicate connections when trying to use the same socket ID.

W-17502656
## [](#1-0-1)1.0.1 **January 8, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
App/Service Version

Mule

4.2.2 and later

Open JDK

8, 11, and 17
## [](#1-0-0)1.0.0 **November 15, 2019** ### [](#compatibility-6)Compatibility
App/Service Version

Mule

4.2.2 and later
New release. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Workable Connector Release Notes Anypoint Connector for Workable (Workable Connector) enables Mule applications to access the Workable API. Guide: [Workable Connector User Guide](https://docs.mulesoft.com/workable-connector/latest/) ## [](#0-1-15)0.1.15 **August 31, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-14)0.1.14 **June 30, 2026** ### What’s New This release includes only non-user-impacting changes. ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17, 21
## [](#0-1-0)0.1.0 **December 16, 2025** ### What’s New This is a new connector. Unresolved include directive in modules/ROOT/pages/connector/workable-connector-release-notes-mule-4.adoc - include::connectors::partial$beta-connector-disclaimer.adoc\[\] For more information, see the [Workable Connector User Guide](https://docs.mulesoft.com/workable-connector/latest/). ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
## [](#see-also)See Also - [Workable Connector User Guide](https://docs.mulesoft.com/workable-connector/latest/) - [Workable Connector Reference](https://docs.mulesoft.com/workable-connector/latest/workable-connector-reference) - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Workday Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Workday is a software as a service (SaaS) solution developed by Workday comprising of a set of management applications that cover areas such as human resources management, staffing, recruiting, and performance management. Workday Connector requires an Enterprise license. Guide: [Workday Connector](https://docs.mulesoft.com/workday-connector/latest/) Reference: [Workday Connector Reference](https://docs.mulesoft.com/workday-connector/latest/workday-reference) ## [](#16-7-1)16.7.1 **August 3, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v46.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson library is upgraded to version 2.22.1 to address reported security vulnerabilities.

W-23623414
## [](#16-7-0)16.7.0 **April 23, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v46.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now provides improved X.509 certificate authentication reliability in environments with restricted security providers.

W-21346211
## [](#16-6-0)16.6.0 **April 3, 2026** ### What’s New - Workday Connector now supports Workday API v46.0. ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v46.0

OpenJDK

8, 11, and 17
## [](#16-5-0)16.5.0 **March 12, 2026** ### What’s New - In the **x.509 Authentication** connection type, the **Key store path** field now includes `BCFKS`. ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-21346211
## [](#16-4-2)16.4.2 **March 8, 2026** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The soap.engine.version library is upgraded to version 1.10.2.

  • The commons-text library is upgraded to version 1.14.0.

W-21134485
## [](#16-4-1)16.4.1 **August 31, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Workday Connector with the x.509 Authentication connection type now correctly handles relative paths for keystore files and no longer requires an absolute path to the keystore files.

W-18134597
## [](#16-4-0)16.4.0 **May 12, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-18198183
## [](#16-3-0)16.3.0 **March 12, 2025** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-17144244
## [](#16-2-2)16.2.2 **November 7, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-collections:commons-collections version 3.2.2 library is now excluded to address reported security vulnerabilities.

W-16863203
## [](#16-2-1)16.2.1 **October 16, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The org.mule.connectors:mule-soap-engine library is upgraded to version 1.9.3 to address reported security vulnerabilities.

W-16863721
## [](#16-2-0)16.2.0 **October 7, 2024** ### What’s New - The connector now supports the **Workday OAuth Code Authentication Connection** connection type to seamlessly integrate with OAuth2-compliant authorization servers. For more information, refer to [Workday OAuth Code Authentication Connection Type](https://docs.mulesoft.com/workday-connector/latest/workday-reference#Config_WorkdayOauthAuthentication). - The connector now supports the **Unauthorize** operation. For more information, refer to [Unauthorize](https://docs.mulesoft.com/workday-connector/latest/workday-reference#Unauthorize). ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
## [](#16-1-1)16.1.1 **June 14, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

DOCTYPE declarations are disabled to address reported XML External Entity Injection security vulnerabilities.

W-15200141
## [](#16-1-0)16.1.0 **April 11, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

OpenJDK

8, 11, and 17
## [](#16-0-2)16.0.2 **January 23, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

Open JDK

8, 11, and 17
## [](#16-0-1)16.0.1 **November 29, 2023** ### What’s New - The com.google.guava library is upgraded to version 32.0.0-jre. - The org.jetbrains.kotlin library is upgraded to version 1.7.10. - The org.apache.santuario:xmlsec library is upgraded to version 2.2.6. - The org.bouncycastle:bcprov-jdk18on library is now removed. ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The following libraries are upgraded to address reported security vulnerabilities:

  • The com.google.guava library is upgraded to version 32.0.0-jre.

  • The org.jetbrains.kotlin library is upgraded to version 1.7.10.

  • The org.apache.santuario:xmlsec library is upgraded to version 2.2.6.

W-14388392

The org.bouncycastle:bcprov-jdk18on library is now removed.

W-14388392
## [](#16-0-0)16.0.0 **May 4, 2023** ### What’s New - The connector is upgraded to Workday API version 40.0. - The connector now supports the **ACA Partner Integrations** and **Student Transfer Credit** operations. - The connector now throws the new `WORKDAY:BAD_REQUEST` error. - The com.fasterxml.jackson.core library is upgraded to version 2.15.0 to address reported security vulnerabilities. - The mule-soap-engine library is upgraded to version 1.7.2 to address reported security vulnerabilities. - The org-springframework library is upgraded to version 5.3.27 to address reported security vulnerabilities. To learn more about the changes in this major release, see [Upgrade Workday Connector](https://docs.mulesoft.com/workday-connector/latest/workday-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v40.0

Open JDK

8 and 11
## [](#15-0-14)15.0.14 **July 1, 2024** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-15239656
## [](#15-0-13)15.0.13 **October 18, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by removing the jsoup org.jsoup:jsoup:1.14.3.

W-11658649, W-11824232

Fixed reported security vulnerabilities by upgrading the Jackson Databind dependency from com.fasterxml.jackson.core:jackson-databind:2.13.2.1 to com.fasterxml.jackson.core:jackson-databind:2.14.0-rc1.

W-11853426

Fixed reported security vulnerabilities by upgrading the Apache Commons-Text dependency from org.apache.commons:commons-text:1.6 to org.apache.commons:commons-text:1.10.0.

W-11913986
## [](#15-0-12)15.0.12 **July 22, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the HTTP Client dependency from org.apache.httpcomponents:httpclient:4.5.10 to org.apache.httpcomponents:httpclient:4.5.13.

W-11436460
## [](#15-0-11)15.0.11 **June 16, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

The connector no longer contains a policy violation in the sizeof-agent transitive dependency.

W-11074604

The connector now excludes unnecessary artifacts from a transitive dependency.

W-11279931
## [](#15-0-10)15.0.10 **June 6, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

The connection validation now succeeds even if the user does not have access to the Performance_Management service.

W-11193505

Fixed reported security vulnerabilities by upgrading the Spring Framework library from org.springframework:spring-context:5.3.18 to org.springframework:spring-context:5.3.20.

W-11195299
## [](#15-0-9)15.0.9 **May 12, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Spring Framework library from org.springframework:spring-context:5.3.18 to org.springframework:spring-context:5.3.19.

W-11074603
## [](#15-0-8)15.0.8 **April 29, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10574582, W-10574581, W-10574580, W-10574462, W-10574440, W-10574444, W-10574439, W-10574489, W-10574413, W-10574467, W-10574483
## [](#15-0-7)15.0.7 **April 19, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Mule SOAP Engine library from org.mule.connectors:mule-soap-engine:1.6.8 to org.mule.connectors:mule-soap-engine:1.6.9.

W-10933796

Fixed reported security vulnerabilities by upgrading the Spring Framework library from org.springframework:spring-context:5.1.6.RELEASE to org.springframework:spring-context:5.3.19.

W-11001897
## [](#15-0-6)15.0.6 **April 11, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10663753
## [](#15-0-5)15.0.5 **March 31, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.13.2.1.

W-10920503

Upgraded org.mule.connectors:mule-soap-engine:1.5.0 to org.mule.connectors:mule-soap-engine:1.6.8.

W-10920497
## [](#15-0-4)15.0.4 **January 27, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

SE-24297
## [](#15-0-3)15.0.3 **January 7, 2022** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the XMLSec library from com.fasterxml.jackson.core:jackson-databind:2.11.2 to com.fasterxml.jackson.core:jackson-databind:2.12.6.

CONN-9842

Upgraded library dependencies.

CONN-9855
## [](#15-0-2)15.0.2 **December 20, 2021** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9685
## [](#15-0-1)15.0.1 **December 15, 2021** ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9569
## [](#15-0-0)15.0.0 **November 18, 2021** ### What’s New - Upgraded the Workday API to 37.0. - Added the **Drive**, **Metadata Translations**, and **Org Studio** operations. To learn more about the changes in this major release, refer to [Upgrade Workday Connector](https://docs.mulesoft.com/workday-connector/latest/workday-connector-upgrade-migrate). ### Compatibility
Software Version

Mule

4.3.0 and later

Workday API

v37.0

Open JDK

8 and 11
## [](#14-1-1)14.1.1 **January 13, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v36.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9974
## [](#14-1-0)14.1.0 **October 6, 2021** ### What’s New - Added the ability to include headers in requests. ### Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v36.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Removed the vulnerabilities caused by the XMLSec library.

CONN-8981
## [](#14-0-1)14.0.1 **September 8, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v36.0

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

COCN-443
## [](#14-0-0)14.0.0 **March 15, 2021** ### [](#compatibility-35)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v36.0

Open JDK

8 and 11
### [](#features)Features - Upgraded the Workday API to 36.0. (CONN-7708) - Added the **Scheduling** operation, which enables you to invoke the Workday Scheduling web service. To learn more about the changes in this major release, see [Upgrade Workday Connector](https://docs.mulesoft.com/workday-connector/latest/workday-connector-upgrade-migrate). ### [](#fixed-issues-29)Fixed Issues - None. ## [](#13-0-1)13.0.1 **November 24, 2020** ### [](#compatibility-36)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v35.0

Open JDK

8 and 11
### [](#features-2)Features - None. ### [](#fixed-issues-30)Fixed Issues - The **Encoding** field was missing from the **Advanced** tab for the **On Modified Objects** source. (CONN-7215) - The connector logged a warning message for every HTTP call. (CONN-7216) - The **On Modified Objects** source exposed incorrect output metadata for the Worker\_Descriptor field. (CONN-7217) ## [](#13-0-0)13.0.0 **October 15, 2020** ### [](#compatibility-37)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v35.0

Open JDK

8 and 11
### [](#features-3)Features - Upgraded the Workday API to 35.0. (CONN-6946) - Added the **Moments** operation, which enables you to invoke the Workday Moments Web Service. To learn more about the changes in this major release, see [Upgrade Workday Connector](https://docs.mulesoft.com/workday-connector/latest/workday-connector-upgrade-migrate). ### [](#fixed-issues-31)Fixed Issues None ## [](#12-1-0)12.1.0 **August 28, 2020** ### [](#compatibility-38)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v34.0

OpenJDK

8 and 11
### [](#features-4)Features Added support for client certificate (x.509) authentication. ### [](#fixed-issues-32)Fixed Issues None ## [](#12-0-2)12.0.2 **June 23, 2020** ### [](#compatibility-39)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v34.0
### [](#features-5)Features None ### [](#fixed-issues-33)Fixed Issues Fixing issues related to reading the time zone from the configuration of connector source operations. ## [](#12-0-1)12.0.1 **May 15, 2020** ### [](#compatibility-40)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v34.0
### [](#features-6)Features Updated multiple libraries to the latest version. ### [](#fixed-issues-34)Fixed Issues None ## [](#12-0-0)12.0.0 **April 24, 2020** ### [](#compatibility-41)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v34.0
### [](#features-7)Features - Upgraded the Workday API to 34.0. (CONN-5640) - Added the `Student Core` operation, which enables you to invoke the Workday Student Core Web Service - Replaced the `On New Objects` input source with the `On Modified Objects` input source, which polls data more efficiently - Changed all operations so that they return headers as attributes - Added the ability to create response timeouts for the input source (`On Modified Objects`) and all connector operations by using the new `Response Timeout` and `Response Timeout Unit` fields - Split the connection timeout fields into value and time unit fields For more information, see [Upgrade the Connector to Version 12.0](https://docs.mulesoft.com/workday-connector/latest/workday-connector-upgrade-migrate). ### [](#fixed-issues-35)Fixed Issues - Unexpected error while consuming a web service operation. (SE-15544) - Metadata propagation error. (CONN-2127) - Workday trigger not working. (CONN-3822) ## [](#11-1-3)11.1.3 **April 28, 2020** ### [](#compatibility-42)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v32.1
### [](#fixed-issues-36)Fixed Issues Fixed the error caused when an empty response was returned from the Workday API. (SE-15544) ## [](#11-1-2)11.1.2 **February 5, 2020** ### [](#compatibility-43)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v32.1
### [](#fixed-issues-37)Fixed Issues Improved the tooltip for the Tenant Name parameter. (CONN-4741) ## [](#11-1-1)11.1.1 **October 24, 2019** ### [](#compatibility-44)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v32.1
### [](#features-8)Features Memory management improvements ### [](#fixed-issues-38)Fixed Issues None ### [](#known-issues)Known Issues - When using Workday Connector in Anypoint Studio, depending on connectivity conditions, a timeout can occur while obtaining Workday metadata. See [Increase Timeout in Studio](https://docs.mulesoft.com/workday-connector/latest/workday-connector-studio#increase-timeout-in-studio) in the Workday Connector documentation. - The only way to test connections between a Mule app and Workday is to have permissions for the **Get\_Degrees** operation in the Performance\_Management web service. ## [](#11-1-0)11.1.0 **September 27, 2019** ### [](#compatibility-45)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v32.1
### [](#features-9)Features - Improved error handling. The validation `WORKDAY:VALIDATION_ERROR` and the processing `WORKDAY:PROCESSING_ERROR` error types were added. - The Workday 11.0.0 **Max In Memory Size** field name was changed in Workday 11.1.0 to **In Memory Size**. The type and description for this field stays the same. See [Workday Connector Reference](https://docs.mulesoft.com/workday-connector/latest/workday-reference). ### [](#fixed-issues-39)Fixed Issues None ## [](#11-0-0)11.0.0 **July 16, 2019** ### [](#compatibility-46)Compatibility
Software Version

Mule

4.1.1 and later

Workday API

v32.1
### [](#features-10)Features - Added support for Workday API version 32.1. - Added support for TLS. - Improved error descriptions. ### [](#fixed-issues-40)Fixed Issues None ## [](#10-0-1)10.0.1 **June 21, 2019** ### [](#compatibility-47)Compatibility
Software Version

Mule

4.0.0 and later

Workday API

v28.0, v29.0, v30.0
### [](#features-11)Features None ### [](#fixed-issues-41)Fixed Issues Workday passwords that contained special characters (such as `< > & "`) caused connectivity issues. \[SE-12090\] ## [](#10-0-0)10.0.0 **November 9, 2018** ### [](#compatibility-48)Compatibility
Software Version

Mule

4.0.0 and later

Workday API

v28.0, v29.0, v30.0
### [](#features-12)Features - This connector now supports multiple versions of the Workday API. - New Object Trigger - You can now start a flow with the connector every time an object of a specific type is created. ### [](#fixed-issues-42)Fixed Issues None ## [](#9-2-0)9.2.0 **March 15, 2018** ### [](#compatibility-49)Compatibility
Software Version

Mule

4.0.0 and later

Workday API

v29.1
### [](#features-13)Features None ### [](#fixed-issues-43)Fixed Issues Fixed test connectivity ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # WS-Security Policy The WS-Security policy validates Web Services Security (WS-Security) UsernameToken credentials, XML signatures, or both on inbound SOAP requests. For configuration details, see [WS-Security Policy](https://docs.mulesoft.com/gateway/latest/policies-included-web-services-security). ## [](#october-7-2026)October 7, 2026 ### What’s New - WS-Security policy implementation version 1.0.0 is now supported by Omni Gateway. - WS-Security policy definition version 1.0.0 is now supported by Omni Gateway. # WSDL Proxies ## [](#3-1-4)3.1.4 **April 25, 2025** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.1** ### What’s New
Issue Resolution ID

The cxf-core dependency is updated to fix the CVE-2025-231 vulnerability

W-17937891
## [](#2-2-2)2.2.2 **April 25, 2025** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.1** ### What’s New
Issue Resolution ID

The cxf-core dependency is updated to fix the CVE-2025-231 vulnerability

W-17937891
## [](#3-1-3)3.1.3 **October 24, 2024** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.1** ### What’s New - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.10.1. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#3-1-2)3.1.2 **October 15, 2024** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.1** ### Fixed Issues
Issue Resolution ID

Resources no longer fail to load for WSDL proxies with multiple file schemas.

W-16845006
## [](#3-1-1)3.1.1 **August 5, 2024** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements)New Features and Enhancements - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.3. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#2-2-1)2.2.1 **August 5, 2024** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.3. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#3-1-0)3.1.0 **February 7, 2024** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-3)New Features and Enhancements - This proxy version is now compatible with Java 17. - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.0. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#2-2-0)2.2.0 **February 7, 2024** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-4)New Features and Enhancements - This proxy version is now compatible with Java 17. - Anypoint Connector for HTTP (HTTP Connector), a proxy dependency, has been upgraded to version 1.9.0. For more information about the HTTP Connector release, see [HTTP Connector Release Notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http). ## [](#3-0-2)3.0.2 **November 17, 2022** ### [](#minimum-mule-version-9)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-5)New Features and Enhancements - HTTP Connector upgraded from version 1.6.0 to version 1.7.2. ## [](#3-0-1)3.0.1 **August 22, 2022** ### [](#minimum-mule-version-10)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-2)Fixed Issues - Upgrade of DW 2.3.0 deprecated `nameSet` function due to warning log message. - When using a remote WSDL, the download location of the WSDL file is now `%MULE_HOME/.mule`. ## [](#3-0-0)3.0.0 **December 7, 2021** ### [](#fixed-issues-3)Fixed Issues - Disabling Validations was not functioning in certain payload scenarios. ### [](#new-features-and-enhancements-6)New Features and Enhancements - HTTP Connector upgraded from version 1.5.17 to version 1.6.0. ## [](#2-1-1)2.1.1 **October 26, 2020** ### [](#minimum-mule-version-11)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-4)Fixed Issues - The WSDL proxy ignored the response timeout that was configured in the UI and used the default response timeout instead. ## [](#2-1-0)2.1.0 **September 1, 2020** ### [](#minimum-mule-version-12)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Introduced support for retrieving a WSDL that is protected with basic authentication - WSDL can now be retrieved using a TLS context that is configured for a proxy requester. ## [](#2-0-2)2.0.2 **August 12, 2020** ### [](#minimum-mule-version-13)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-5)Fixed Issues - When no cipher suite is selected for the TLS configuration in the secrets manager, the proxy is generated with `enabledCipherSuites=""`. This issue caused all requests to fail. (SE-15303) - With heavy performance load, back pressure errors increase causing the proxy’s DataWeave scripts to fail due to type mismatch of the parameters. (AGW-4286) ## [](#2-0-1)2.0.1 **June 02, 2020** ### [](#minimum-mule-version-14)Minimum Mule Version **Mule 4.1.1** ### [](#fixed-issues-6)Fixed Issues - The proxy listener path resolves to "/\*" instead of ${proxy.path}. This issue caused the proxy path configuration to be ignored. (SE-16184). ## [](#2-0-0)2.0.0 **April 30, 2020** Introduced a new version of WSDL proxies that uses SOAP Request Validator v1.0.0 without CXF. ### [](#minimum-mule-version-15)Minimum Mule Version **Mule 4.1.1** ### [](#new-features-and-enhancements-8)New Features and Enhancements - Introduced several performance improvements. - Upgraded HTTP Connector from version 1.5.7 to version 1.5.17. ### [](#fixed-issues-7)Fixed Issues - Fixed non-compliant status codes for SOAP version 1.2. ## [](#1-2-2)1.2.2 **January 23, 2020** ### [](#minimum-mule-version-16)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-8)Fixed Issues - Removed unused Mule scripting schema that were previously imported. - WSDL files with circular dependencies caused a stack overflow error. This issue is now resolved. ## [](#1-2-1)1.2.1 **September 3, 2019** ### [](#minimum-mule-version-17)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-9)New Features and Enhancements - HTTP Connector upgraded from v1.3.2 to v1.5.7. - Ability to configure whether validations must be performed in the current request. ### [](#fixed-issues-9)Fixed Issues - Proxies no longer handle cookies by default. To re-enable proxies, you must import the proxy application to Anypoint Studio, and then modify the HTTP Request configuration. From **HTTP Request Configuration** > **Settings**, select the **Enable cookies** check box to access this feature. - XML validation issue resolved. ## [](#1-2-0)1.2.0 **November 1, 2018** ### [](#minimum-mule-version-18)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-10)New Features and Enhancements - Keystore can now be specified when making HTTPs requests. ## [](#1-1-2)1.1.2 **July 6, 2018** ### [](#minimum-mule-version-19)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-11)New Features and Enhancements - Removed legacy headers filtering. ### [](#fixed-issues-10)Fixed Issues - Fixed proxy deployment issues when deploying to Mule Runtime 4.1.3. ## [](#1-1-1)1.1.1 **May 14, 2018** ### [](#minimum-mule-version-20)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-12)New Features and Enhancements - Mule Maven Plugin upgraded from version 3.1.0 to version 3.1.2. ### [](#fixed-issues-11)Fixed Issues - Fixed content length HTTP header data. ### [](#known-issues)Known Issues - WSDL proxy is not deploying in 4.1.3 runtimes. ## [](#1-1-0)1.1.0 **January 25, 2018** ### [](#minimum-mule-version-21)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-13)New Features and Enhancements - Proxies can now be easily imported using MuleSoft Anypoint Studio. - New WSDL property resolver is introduced using which, a service name and a service port can now be specified. - Proxy binary size is decreased. ### [](#fixed-issues-12)Fixed Issues - Fix path expression ### [](#known-issues-2)Known Issues - WSDL Proxy is not deploying in Mule Runtime 4.1.3. ## [](#see-also)See Also - [HTTP Connector release notes](https://docs.mulesoft.com/jp/release-notes/connector/connector-http) - [Known Issues](https://help.salesforce.com/s/issues) # WSS Module Release Notes WSS Module enables you to process and validate an inbound SOAP request against a given Web Service Security (WSS) extension configuration to, for example, validate the request signature, perform an LDAP authentication, or decrypt the inbound message. WSS Module also enables you to sign your response by adding a WSS header to it, or to encrypt your outbound message. Guide: [WSS Module Connector User Guide](https://docs.mulesoft.com/wss-module/latest/) ## [](#wss-2.2.5)2.2.5 **October 22, 2026** ### What’s New - The WSS Module updates the **Spring Framework** and **Micrometer** libraries to address reported security vulnerabilities. ### Fixed Issues
Issue Resolution ID

The WSS Module updates the Spring Framework and Micrometer libraries to address reported security vulnerabilities.

W-24440865
## [](#wss-2.2.4)2.2.4 **October 1, 2026** ### What’s New - This release includes only non-user-impacting changes. ## [](#wss-2.2.3)2.2.3 **July 29, 2026** ### What’s New - The WSS Module updates the **Spring LDAP** and **Spring Expression** libraries to address reported security vulnerabilities. ### Fixed Issues
Issue Resolution ID

The WSS Module updates the spring-ldap-core and spring-expression libraries to address reported security vulnerabilities.

W-23569598
## [](#wss-2.2.2)2.2.2 **July 15, 2026** ### What’s New - The WSS Module updates the **Spring Framework** libraries to address reported security vulnerabilities. ### Fixed Issues
Issue Resolution ID

The WSS Module updates the spring-core library to 6.2.19 and the spring-context library to 6.2.19 to address reported security vulnerabilities.

W-23286572
## [](#wss-2.2.1)2.2.1 **May 21, 2026** ### What’s New - The WSS Module updates the `guava` and `spring-security-ldap` libraries to address reported security vulnerabilities. ### Fixed Issues
Issue Resolution ID

The WSS Module updates the guava library to version 32.0.1 to address reported security vulnerabilities.

W-22373455

The WSS Module updates the spring-security-ldap library to version 6.5.10 to address reported security vulnerabilities.

W-22392922
## [](#wss-2.2.0)2.2.0 **May 4, 2026** ### What’s New - Identify API operations more easily with dynamic telemetry traces WSS Module 2.2.0 introduces dynamic telemetry traces for easier API operation identification. This enhancement improves visibility into API behavior and performance, streamlining troubleshooting and optimization. ## [](#wss-2.1.1)2.1.1 **April 3, 2026** ### Fixed Issues
Issue Resolution ID

The org.springframework.security:spring-security library is upgraded to version 6.5.9 to address reported security vulnerabilities.

W-21703721
## [](#wss-2.1.0)2.1.0 **March 20, 2026** ### What’s New - WSS Module upgrades the default hashing algorithm from SHA-1 to SHA-256 to enhance cryptographic security and ensure alignment with FIPS 140-3 approved standards. ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
## [](#wss-2.0.3)2.0.3 **January 13, 2026** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The processSecurity() method no longer creates a thread bottleneck that reduces throughput under high concurrency.

W-20816910
## [](#wss-2.0.2)2.0.2 **November 7, 2025** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The spring library is upgraded to address reported security vulnerabilities.

W-20009365
## [](#wss-2.0.1)2.0.1 **September 15, 2025** ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

The spring-core library is upgraded to version 6.2.10 to address reported security vulnerabilities.

W-19578309
## [](#wss-2.0.0)2.0.0 **June 27, 2025** ### What’s New - WSS Module (and its dependencies) are now compilable and compatible only with Java 17. - To align with modern development practices and ensure continued compatibility with secure and supported libraries, WSS Module is upgraded from Spring 5.x to Spring 6.x. - In the **Encryption Config** type, the `EMBEDDED_KEY_NAME` option has been removed from the **Encryption Key Identifier** field. For more information about how to upgrade the connector to version 2.0, refer to [Upgrading and Migrating WSS Module to Version 2.2](https://docs.mulesoft.com/wss-module/latest/wss-module-upgrade-migrate). ### Compatibility
Application/Service Version

Mule

4.9.0 and later

OpenJDK

17
## [](#wss-1.2.3)1.2.3 **March 21, 2025** ### What’s New - This release upgrades some dependencies to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#wss-1.2.2)1.2.2 **May 30, 2024** ### What’s New - This release fixes issues and updates dependencies. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The WSS module now raises an error when a validation fails after passing a fake certificate in the request.

W-15715423

WSS now has the option to leave the encryption digest algorithm empty.

W-14094903
## [](#wss-1.2.1)1.2.1 **May 2, 2024** ### What’s New - WSS module is now FIPS 140-2 compliant. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#wss-1.2.0)1.2.0 **February 20, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#wss-1.1.4)1.1.4 **February 15, 2024** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The WSS module now checks if the security tag is not empty.

W-15042975
## [](#wss-1.1.3)1.1.3 **June 12, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

The WSS module now correctly removes the certificate from Object Store upon flow completion.

W-12697701
## [](#wss-1.1.2)1.1.2 **March 10, 2023** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

mustUnderstand attribute is applied according to the outbound configuration.

W-12644155
## [](#wss-1.1.1)1.1.1 **June 21, 2022** ### Compatibility
Application/Service Version

Mule

4.1.1 and later
### Fixed Issues
Issue ID

The initialization of the WSS library no longer displays an error on Mule applications without inbound configurations.

W-11261692
## [](#wss-1.1.0)1.1.0 **March 08, 2022** ### [](#minimum-mule-version)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements)New Features and Enhancements - The "Apply WSS" operation now has a parameter that enables you to add a timestamp to the security header (W-10655907) ## [](#wss-1.0.4)1.0.4 **Feb 14, 2022** ### [](#minimum-mule-version-2)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-2)New Features and Enhancements - Internal changes related to automation processes (W-10564213) ## [](#wss-1.0.3)1.0.3 **Dec 1, 2021** ### [](#minimum-mule-version-3)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-3)New Features and Enhancements Add support for Java JDK 11 ## [](#wss-1.0.2)1.0.2 **Apr 21, 2021** ### [](#minimum-mule-version-4)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-4)New Features and Enhancements The encryption configuration (`encryptionConfig`) with `encryptionKeyIdentifier` as `DIRECT_REFERENCE` now generates a binary security token (`BinarySecurityToken`). ## [](#1-0-1)1.0.1 **Feb 25, 2021** ### [](#minimum-mule-version-5)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-5)New Features and Enhancements Internal changes related to automation processes ## [](#1-0-0)1.0.0 **Oct 7, 2020** ### [](#minimum-mule-version-6)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-6)New Features and Enhancements Initial release. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # X12 EDI Connector Release Notes Support Category: [Premium](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [X12 EDI Connector User Guide](https://docs.mulesoft.com/x12-edi-connector/latest/) ## [](#3-0-0)3.0.0 **October 23, 2026** ### What’s New - X12 Connector now requires Mule 4.6.0 and later. - The connector now supports X12 HIPAA versions `006020X314` and `006020X316` in the provided schemas. ### Compatibility
Application/Service Version

Mule

4.6.0 and later

OpenJDK

8, 11, and 17

X12

Standard: 002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

UCS: 003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

VICS: 003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306, 006020X314, 006020X316
## [](#2-19-0)2.19.0 **August 20, 2026** ### What’s New - A new Interchange control version field in the config **Writer** tab lets you set a custom Interchange control version (ISA12). If ISA12 isn’t in the incoming payload, the connector overrides the schema value. For more information, see [X12 EDI Connector 2.19 Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

X12

002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
## [](#2-18-1)2.18.1 **July 24, 2026** ### Compatibility
Application/Service Version

Mule

4.4.0 and later

OpenJDK

8, 11, and 17

X12

002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
### Fixed Issues
Issue Resolution ID

The connector now stops promptly and efficiently during application shutdown.

W-22896562
## [](#2-18-0)2.18.0 **October 30, 2025** ### What’s New - A new property `Require unique transactions in group` is added for the **Read** operation and controls whether duplicate transaction set control numbers (ST02) can be included in the functional group of an interchange. For more information, see [X12 EDI Connector 2.19 Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
## [](#2-17-2)2.17.2 **March 13, 2025** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
### Fixed Issues
Issue Resolution ID

The incoming payload now ignores fields with null values and no longer throws exceptions when using Java 17.

W-17830212
## [](#2-17-1)2.17.1 **October 23, 2024** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
### Fixed Issues
Issue Resolution ID

If the incoming payload fails to validate, the Copy of Data Element (AK4-04 or IK4-04) is now truncated in the acknowledgment if the element exceeds the length limit.

W-17016123
## [](#2-17-0)2.17.0 **September 26, 2024** ### What’s New - The default value for the `Character set` parameter is changed to `UNRESTRICTED`. For more information, see the parameter in the [Parameters section](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference#Parameters) of the Default Configuration section on the X12 EDI Connector Reference page. ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
### Fixed Issues
Issue Resolution ID

Allowed characters in the Character set parameter are now enforced.

W-16531421
## [](#2-16-0)2.16.0 **July 10, 2024** ### What’s New - The connector now supports X12 versions `002001`, `002002`, `002003`, `002040`, and `008050` in the provided schemas. ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

002001, 002002, 002003, 002040, 003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040, 008050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
### Fixed Issues
Issue Resolution ID

The connector now generates the correct Invalid code value error when the code does not match any of the segment variants.

W-15285820

Locking errors no longer occur when the application experiences a heavy load.

W-15945128
## [](#2-15-1)2.15.1 **March 13, 2024** ### What’s New - The connector’s **Read** operation now outputs an ordered map that follows the schema structure. ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
### Fixed Issues
Issue Resolution ID

The connector now generates an accurate segment tag and segment index for certain errors.

W-15093132
## [](#2-15-0)2.15.0 **February 22, 2024** ### What’s New - The connector now supports X12 HIPAA versions `005010X298`, `005010X299`, and `005010X300` in the provided schemas. - A new field named **Include ignored segments** enables you to include data elements from segments with `Ignore` as the usage type in the **Read** operation’s output map and metadata representation. For more information, see the [X12 EDI Connector Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X298, 005010X299, 005010X300, 005010X306
## [](#2-14-0)2.14.0 **January 29, 2024** ### What’s New - This connector is now compatible with Java 17. - A new field named **Lock Mechanism** enables you to determine the mechanism used to manage locks for control number sequencing. For more information, see the [X12 EDI Connector Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

OpenJDK

8, 11, and 17

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
## [](#2-13-0)2.13.0 **November 16, 2023** ### What’s New - A new field named **Include trailer segment details** enables you to include the interchange and group trailer details in the read’s output map. For more information, see the [X12 EDI Connector Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue Resolution ID

The connector no longer replicates the inbound Acknowledgment Requested Code (ISA14) value in the output acknowledgment map.

W-14488084
## [](#2-12-0)2.12.0 **October 26, 2023** ### What’s New - The connector now supports X12 versions `007060`, `008010`, `008020`, `008030`, and `008040` in the provided schemas. - The connector uses the new **strictValidationOfYear** system property to determine whether to validate the year `0000`. By default, the year `0000` is valid. For more information, see the [X12 EDI Connector Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050, 007060, 008010, 008020, 008030, 008040

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
## [](#2-11-2)2.11.2 **August 16, 2023** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue Resolution ID

StringIndexOfBoundException errors no longer occur when invalid date times occur in the input. Also, invalid characters in dates now generate only one error message instead of one error message for each occurrence. The error message is generated for the first occurrence only.

W-10581264

The Read operation now throws an error when the GS04 (Group Date) and GS05 (Group Time) segments contain an invalid date time.

W-13723427

The connector no longer downloads old log4j POM files.

W-13797183
## [](#2-11-1)2.11.1 **June 21, 2023** ### What’s New - The org.scala-lang library is upgraded to version 2.12.15. - The org.yaml.snakeyaml library is upgraded to version 2.0 to address reported security vulnerabilities. ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue Resolution ID

When composites or repetitions are placed incorrectly in the received message, the parser now throws an error for the incorrect element instead of the element after the incorrect element.

W-13214932
## [](#2-11-0)2.11.0 **May 18, 2023** ### What’s New - A new field named **Set acknowledgement schema by inbound message** enables you to set the acknowledgment structure automatically according to the inbound message version. For more information, see the [X12 EDI Connector Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue Resolution ID

The generated Functional Acknowledgment is now more compatible with different X12 versions.

W-12776825

All the fields in the Data Element Note (AK4/IK4) are now generated correctly in the acknowledgment.

W-13025198

The Loop Identifier Code (AK3-03/IK3-03) is now populated in the acknowledgment when the error occurs in a loop.

W-13035983

When the X12 Read operation receives an EDI-Message and the schema is not defined in the configuration, the parser looks for the schema using the version and transaction set ID. This works for HIPAA, VICS, and UCS transactions.

W-13146370
### Known Issues
Known Issue Workaround ID

When composites or repetitions are placed incorrectly in the received message, unexpected errors occur.

W-13214932
## [](#2-10-0)2.10.0 **April 4, 2023** ### What’s New - The connector now supports the HIPAA `005010X216` `278 Notification` and `278 Acknowledgement` schema versions. - Several dependency libraries are updated for the connector. ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X216, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue Resolution ID

Dates are now validated correctly when HIPAA schemas contains the rule D.

W-12374508

The unexpected error None.get no longer occurs when an invalid code is present in the Date Time Period Format Qualifier field.

W-12629964
## [](#2-9-2)2.9.2 **January 19, 2023** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue Resolution ID

Element ST03 (Implementation Convention Reference) from transaction 835 and version 005010X221A1 now has the usage U (Unused) instead of O (Optional).

W-11221387

Element GS04 (Date) is now written with the correct format, YYMMDD, in version 003070 and in earlier versions.

W-12219376

Envelope segments (ISA, IEA, GS, GE, ST, SE) are now obtained from the schema definition, if present. If the envelope segments are not in the schema definition, the connector uses hard-coded segments.

W-12270419
## [](#2-9-1)2.9.1 **October 20, 2022** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### What’s New - The `org.yaml.snakeyaml` library is upgraded to version 1.32 to address reported security vulnerabilities. ### Fixed Issues
Issue ID

An X12 AK304 or IK304 error is generated with the appropriate segment error code when a non-fatal element error occurs.

W-11514473

AK4 or IK4 loops are not carried over to an incorrect AK3 or IK3 data element.

W-11514665
## [](#2-9-0)2.9.0 **June 7, 2022** ### What’s New - A new field named **Report non-fatal errors in acknowledgments** enables you to enable or disable the inclusion of non-fatal errors found during the validation of inbound EDI message payloads. For more information, see the [X12 EDI Connector Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

The functional acknowledgement object generated as a result of an X12 Read operation now sets GS01 in the acknowledgement to the code FA.

W-10909976

The syntax rules containing composite components are now validated correctly.

W-10977782
## [](#2-8-2)2.8.2 **March 23, 2022** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

Thread management when using the connector with multiple dynamic configurations is now improved.

W-10878642
## [](#2-8-1)2.8.1 **March 17, 2022** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

Upgraded library dependencies.

W-10718515, W-10718531

Improved how dependent schema files are packaged within the connector.

W-10822805
## [](#2-8-0)2.8.0 **February 22, 2022** ### What’s New - Added the new **Use segment line ending in last line** field, which enables you to add a segment line ending character at the end of the IEA segment. For more information, see the [X12 EDI Connector Reference](https://docs.mulesoft.com/x12-edi-connector/latest/x12-edi-connector-reference). ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

Unexpected exceptions occurred while parsing date and time formats in HIPAA schemas.

SE-24277

Some segment IDs from HIPAA schemas were generated in an arbitrary order, leading to inconsistencies between versions.

SE-24317

The 2400_Loop for the HIPAA Schema 005010X223A2 837.esl did not contain the 2420A_Loop.

SE-24063

In some cases, LX segment validation raised an error even if there were no issues with the payload.

W-10671469
## [](#2-7-4)2.7.4 **January 24, 2022** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

Hierarchical Level segments (HL) were written twice if present in a HIPAA structure.

SE-23655

The control characters CR, CRLF, or LF were not added at the end of the last segment.

SE-23865

The logger level was always set to ERROR, even if the error was not fatal.

SE-24073

VICS and UCS schemas were not included in the versions.txt file.

CONN-9946
## [](#2-7-3)2.7.3 **December 23, 2021** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9586
## [](#2-7-2)2.7.2 **December 20, 2021** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9586
## [](#2-7-1)2.7.1 **December 13, 2021** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

The generated functional acknowledgement contained incorrect element values on the partial rejection.

CONN-9413
## [](#2-7-0)2.7.0 **December 1, 2021** ### What’s New - The connector now supports message formats that comply with the X12 Voluntary Industry Commerce Standards (VICS) and Uniform Communication Standards (UCS). - The connector now includes standard X12, VICS schema, and UCS schema code set definitions in the EDI Schema Language (ESL) definitions for data elements defined as identifiers. - Added the option to enable code set validations for the **Read**, **Write**, and **Batch** operations. - Added the option to specify the UTC timezone offset for date/time stamps in the Interchange and group segments for the **Write** and **Batch** operations. - The errorDetails section in the output of the X12 **Read** operation now includes additional error information when the parsed payloads fail in the X12 syntax check validations. ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, 007050

003010UCS, 003020UCS, 003030UCS, 003040UCS, 003050UCS, 003060UCS, 003070UCS, 004010UCS, 004020UCS, 004030UCS, 004040UCS, 004050UCS, 004060UCS, 005010UCS, 005020UCS, 005030UCS, 005040UCS

003010VICS, 003020VICS, 003030VICS, 003040VICS, 003050VICS, 003060VICS, 003070VICS, 004010VICS, 004020VICS, 004030VICS, 004040VICS, 004050VICS, 004060VICS, 005010VICS, 005020VICS, 005030VICS, 005040VICS

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, 005010X306
### Fixed Issues
Issue ID

In some cases, non-fatal errors referred to incorrect segments or elements instead of to the segments or elements causing issues.

CONN-7890

The ISA and GS segments in the functional and technical acknowledgements generated by the X12 Read operation contained the timestamp from the input X12 payload instead of the timestamp of the acknowledgement generation.

CONN-8359

When using drag-and-drop style mapping in DataWeave, new field mapping assignments sometimes removed previously-mapped field mappings.

CONN-8476
## [](#2-6-5)2.6.5 **October 18, 2021** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### Fixed Issues
Issue ID

The control number was re-initialized after an application running in a customer-hosted Mule cluster restarted.

SE-22081
## [](#2-6-4)2.6.4 **September 24, 2021** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### Fixed Issues
Issue ID

The Read operation threw an outOfMemory exception when a non-alphabetic character was used as a repetition separator (ISA11).

SE-22230

The Read operation did not validate the count defined in the schema for repeating elements.

SE-22230
## [](#2-6-3)2.6.3 **August 26, 2021** ### Compatibility
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### Fixed Issues
Issue ID

An InvalidState error occurred during concurrent operations in the CloudHub environment.

N/A

The connector did not perform integrity checks on the LX sequence number values against SNIP validation rules.

SE-21156
## [](#2-6-2)2.6.2 **July 28, 2021** ### [](#compatibility-32)Compatibility X12 EDI Connector v2.6.2 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### [](#fixed-issues-26)Fixed Issues - The acknowledgement schema path configuration defined in the Parser setting was not used in the generated Functional Acknowledgement structure for X12 HIPAA transactions. (SE-21623) - The Functional Group version (GS08) and Version Identifier Code (AK103) were set with the GS08 value of the input payload, instead of the version code of the generated implementation acknowledgement (999) for HIPAA transactions. (SE-21623) - The following code values have been added as valid values for the AK103 element definition: `005010X210`, `005010X212`, `005010X214`, `005010X215`, `005010X217`, `005010X218`, `005010X220A1`, `005010X221A1`, `005010X222A1`, `005010X222A2`, `005010X223A2`, `005010X223A3`, `005010X224A2`, `005010X224A3`, `005010X228`, `005010X231`, `005010X231A1`, `005010X279A1`, and `005010X306`. (SE-21623) - The Implementation Convention Reference (ST03) was not populated for X12 HIPAA 999 implementation acknowledgements. (SE-21623) ## [](#2-6-1)2.6.1 **July 6, 2021** ### [](#compatibility-33)Compatibility X12 EDI Connector v2.6.1 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### [](#fixed-issues-27)Fixed Issues - The connector did not validate the date in some transactions. (SE-19901) - The connector did not generate a negative ACK generation for invalid input date formats. (SE-20361) - Mule apps that used the X12 **Write** operation when deploying multiple workers in the CloudHub enviroment failed because the locks didn’t increment the message number. (SE-20943) - The X12 **Read** operation failed when the incoming data contained the `GS07` Agency Code `T`. (SE-20955) ## [](#2-6-0)2.6.0 **June 8, 2021** ### [](#compatibility-34)Compatibility X12 EDI Connector v2.6.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### [](#new-features)New Features - Added a new **Write batch** operation and a corresponding **Configuration** tab. The new operation receives an input containing multiple outbound X12 messages for the same partner and merges them into a single ISA interchange. - Added a new configuration property `Truncate values exceeding the length limits` for **Read**, **Write**, and **Write batch** operations to optionally truncate data element values when ignoring length validations. ### [](#fixed-issues-28)Fixed Issues - Data element values are no longer truncated by default when enabling length validations in **Read** and **Write** operations. (CONN-7723) ## [](#2-5-8)2.5.8 **April 28, 2021** ### [](#compatibility-35)Compatibility X12 EDI Connector v2.5.8 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### [](#fixed-issues-29)Fixed Issues - When a segment contained composite elements, the parser failed to validate the presence of dependent elements. (SE-19994) - Fixed issues with concurrent write of EDI messages while processing through the Async scope. (SE-19637) ## [](#2-5-7)2.5.7 **April 14, 2021** ### [](#compatibility-36)Compatibility X12 EDI Connector v2.5.7 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### [](#fixed-issue)Fixed Issue - In a CloudHub deployment, when multiple workers were used, the thread lock occasionally caused an error. (SE-19046) ### [](#known-issue)Known Issue - When a segment contained composite elements, the parser failed to validate the presence of dependent elements. (SE-19994) ## [](#2-5-6)2.5.6 **March 5, 2021** ### [](#compatibility-37)Compatibility X12 EDI Connector v2.5.6 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X231A1, 005010X279A1, and 005010X306.
### [](#fixed-issues-30)Fixed Issues The extension X222A1 was not defined for AK103, causing the validation to fail. (SE-18005) ## [](#2-5-5)2.5.5 **February 22, 2021** ### [](#compatibility-38)Compatibility X12 EDI Connector v2.5.5 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X279A1, and 005010X306.
### [](#fixed-issues-31)Fixed Issues The sample output header Anypoint Studio generates is fixed to `output application/dw`. (SE-18979) ## [](#2-5-4)2.5.4 **February 3, 2021** ### [](#compatibility-39)Compatibility X12 EDI Connector v2.5.4 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X279A1, and 005010X306.
### [](#fixed-issues-32)Fixed Issues - Generated sample data in the payload preview pane did not display correctly. (SE-18979) ## [](#2-5-3)2.5.3 **November 11, 2020** ### [](#compatibility-40)Compatibility X12 EDI Connector v2.5.3 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X279A1, and 005010X306.
### [](#fixed-issues-33)Fixed Issues - Fixed ANSI X12 message support for message versions earlier than 004020. (SE-18189) - Removed the incorrect validation that resulted in conditional (usage= 'C') components being treated as mandatory (usage= 'M') components, which caused some `null` or `empty` values to throw exceptions. (SE-18151) ## [](#2-5-2)2.5.2 **October 21, 2020** ### [](#compatibility-41)Compatibility X12 EDI Connector v2.5.2 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X279A1, and 005010X306.
### [](#fixed-issues-34)Fixed Issues - Removed unnecessary scala-compiler dependency to fix vulnerability issue related to jQuery’s DOM manipulation methods. (SE-17989) ## [](#2-5-1)2.5.1 **August 27, 2020** ### [](#compatibility-42)Compatibility X12 EDI Connector v2.5.1 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X279A1, and 005010X306.
### [](#fixed-issues-35)Fixed Issues - Fixed Write operation error caused by parsing decimal values set as the `java.lang.Double` type. (SE-16956) - Fixed Ack 999 generation when `generate999Acks` parameter is set to `true`. (CONN-6671) ## [](#2-5-0)2.5.0 **July 23, 2020** ### [](#compatibility-43)Compatibility X12 EDI Connector v2.5.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214, 005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, 005010X228, 005010X231, 005010X279A1, and 005010X306.
### [](#new-features-2)New Features - Added the configuration option `enforceConditionalRulesOnParser` in the X12 Read operation and \`enforceConditionalRulesOnWriter\`in the X12 Write operation to turn on conditional relationship validation of data elements. - Added configuration options for interchange, group, and transaction control number keys in the X12 Write operation to provide flexibility in managing control number sequencing. - Users are now allowed to initialize or reset control numbers when using Anypoint Connector for Object Store (Object Store Connector). - Added the functional group code in the attributes of the post X12 Write operation along with generated control numbers. ### [](#fixed-issues-36)Fixed Issues - The Connector failed to generate a correct sequence number for a Dependent segment (SE-15881). - Users were required to explicitly specify the 997 schema path when parsing inbound 997s (CONN-6596). ### [](#known-limitations)Known Limitations - X12 EDI Connector supports files up to 20MB. If you process files larger than 20MB, consider that the connector has a 40x memory requirement that corresponds to the EDI file size. For example, a 30 MB X12 (or EDIFACT) file needs 1.4 GB of memory, so it’s important to consider this memory requirement in conjunction with your transaction processing system needs for large files. - As of connector version 2.2.0, reading and writing HIPAA 005010X231A1 999 Implementation Acknowledgments is fully supported, but when generating acknowledgments as 005010X231A1 CTX segments, these are not added. To use CTX segments, you must manually add them to the generated acknowledgment. ## [](#2-4-0)2.4.0 **June 30, 2020** ### [](#compatibility-44)Compatibility X12 EDI Connector v2.4.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214,005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3,005010X228, 005010X231, 005010X279A1 and 005010X306
### [](#features)Features - Added the configuration option `writeEnforceLengthLimits` in the X12 Write operation for optionally turning off Length validations of data elements. - Control numbers generated in the X12 Write operation are now passed as attributes post X12 Write operation. ### [](#fixed-issues-37)Fixed Issues - Resolved issues with the connector failing to generate a correct sequence number for a Dependent segment (SE-15881) - Fixed an issue where the 5010 acknowledgment schema was being used as the default for versions less than 5010 when the acknowledgment schema path was not explicitly defined in the Parser configuration. (CONN-6184) - Fixed issues with whitespace getting mapped to mandatory and conditional elements when the mapped input data value is empty (CONN-6462) - Length validations on optional elements that are empty/null were ignored. (CONN-5981) ### [](#known-limitations-2)Known Limitations Parsing inbound 997s in the X12 Read operation requires users to explicitly specify the 997 ESL path. X12 EDI Connector supports files up to 20MB. If you process files larger than 20MB, consider that the connector has a 40x memory requirement that corresponds to the EDI file size. For example, a 30MB X12 (or EDIFACT) file needs 1.4GB of memory, so it’s important to consider this memory requirement in conjunction with your Transaction Processing System needs for large files. As of version 2.2.0, reading and writing HIPAA 005010X231A1 999 Implementation Acknowledgments is fully supported, but when generating acknowledgments as 005010X231A1 CTX segments, these are not added. To use CTX segments, you must manually add them to the generated acknowledgment. ## [](#2-3-0)2.3.0 **May 20, 2020** ### [](#compatibility-45)Compatibility X12 EDI Connector v2.3.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214,005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3,005010X228, 005010X231, 005010X279A1 and 005010X306
### [](#features-2)Features - Added the configuration option `acknowledgmentSchemaPath` which specifies the schema to be used for generating 997 or 999 acknowledgments. ### [](#fixed-issues-38)Fixed Issues - Added alphanumeric support for transaction number increments. (SE-14275) - Improved X12 Write error reporting for errors in the ISA and GS fields. (SE-14152) - Added error details to X12Error objects included in the parsing output. (CONN-4947) - Improved error detection and reporting for overlay schemas. (CONN-5890) - Fixed parsing of repeated values. (CONN-6097) - Corrected the parsing of the HIPAA 005010X231A1 999 transaction set with AK2 loops. (CONN-6098) - Fixed ISA12 and GS08 to use values from configured transaction set schemas. (CONN-5980) - Corrected the HIPAA 005010X231 version to 005010X231A1. (CONN-5005) - Fixed document parsing with multiple interchanges using an ISA11 repetition separator. (CONN-6112) - Corrected the handling of ISA14 and ISA15 settings from configuration. (CONN-5979) - Corrected the handling of `formValidation` HIPAA validation choices and the `ackAllSets` configuration parameter. (CONN-5708) ### [](#known-limitations-3)Known Limitations Parsing inbound 997s in the X12 Read operation requires users to explicitly specify the 997 ESL path. X12 EDI Connector supports files up to 20MB. If you process files larger than 20MB, consider that the connector has a 40x memory requirement that corresponds to the EDI file size. For example, a 30MB X12 (or EDIFACT) file needs 1.4GB of memory, so it’s important to consider this memory requirement in conjunction with your Transaction Processing System needs for large files. As of version 2.2.0, reading and writing HIPAA 005010X231A1 999 Implementation Acknowledgments is fully supported, but when generating acknowledgments as 005010X231A1 CTX segments, these are not added. To use CTX segments, you must manually add them to the generated acknowledgment. ## [](#2-2-0)2.2.0 **January 31, 2020** ### [](#compatibility-46)Compatibility X12 EDI Connector v2.2.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, 006010, 006020, 006030, 006040, 006050, 007010, 007030, 007040, and 007050.

HIPAA

005010X210, 005010X212, 005010X214,005010X215, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3,005010X228, 005010X231, 005010X279A1 and 005010X306
### [](#features-3)Features - Support for X12 versions 006010, 006030, 006040, 006050, 007010, 007020, 007030, 007040, 007050. - Support for HIPAA versions 005010X210, 005010X215, 005010X228, 005010X231, 005010X306. - Support for generating 999 Implementation Acknowledgments in 005010X231 form. - Support for generating alpha-numeric transaction set control numbers. (SE-14275) - Added Transaction Set Trailer (SE segment) data to the X12 Read operation output. (SE-14490) - Added configuration option to allow setting output MIME type `application/edi-x12`. ### [](#fixed-issues-39)Fixed Issues - Resolved comprehensive reporting of group level errors. (CONN-346) - Users can now view the field identifier in error messages returned during X12 Write operations. (SE-14152) - Transaction set data is added to the output map only when the group as a whole is accepted. (CONN-3858) - Corrected handling of ST03 implementation convention reference field to override the value in GS08. (CONN-4519) - Removed Scala data structures from X12 Write data after the write has been completed to avoid serialization errors. (CONN-3831) ### [](#known-limitations-4)Known Limitations X12 EDI Connector supports files up to 20MB. If you process files larger than 20MB, consider that the connector has a 40x memory requirement that corresponds to the EDI file size. For example, a 30MB X12 (or EDIFACT) file needs 1.4GB of memory, so it’s important to consider this memory requirement in conjunction with your TPS needs for large files. As of version 2.2.0 reading and writing HIPAA 005010X231 999 Implementation Acknowledgments is fully supported, but when generating acknowledgments in 005010X231 CTX segments will not be added. If you need to use CTX segments you’ll have to manually add these to the generated acknowledgment. ## [](#2-1-1)2.1.1 **June 18, 2019** ### [](#compatibility-47)Compatibility X12 EDI Connector v2.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020

HIPAA

005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, and 005010X279A1
### [](#fixed-issues-40)Fixed Issues - Improved error reporting for X12 Write operations. (SE-10716, SE-10725) - Corrected metadata representation of repeated objects. ### [](#known-limitations-5)Known Limitations X12 EDI Connector supports files up to 20MB. If you process files larger than 20MB, consider that the connector has a 40x memory requirement that corresponds to the EDI file size. For example, a 30MB X12 (or EDIFACT) file needs 1.4GB of memory, so it’s important to consider this memory requirement in conjunction with your TPS needs for large files. ## [](#2-1-0)2.1.0 **May 10, 2019** ### [](#compatibility-48)Compatibility X12 EDI Connector v2.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020

HIPAA

005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, and 005010X279A1
### [](#features-4)Features - Added support for user-supplied values for control segments. These are controlled by the `useSuppliedValues` configuration parameter. ### [](#fixed-issues-41)Fixed Issues - Was passing out data for bad transaction sets in the output of the reader. (SE-11384) - Implemented lock sharing for tracking identifier numbers in the ObjectStore connector with multiple CloudHub workers. (SE-11308) - Multiple HIPAA transaction sets are now allowed in a group. (SE-9043) - Corrected issues found with metadata representation. - Logging didn’t follow Mule conventions. - Updated to latest dependency versions. - Schemas 005010X222A1 and 005010X224A2 contained errors. ## [](#2-0-1)2.0.1 **August 3, 2018** This release adds support for HIPAA X222A1 and X224A2 837 transaction sets. ### [](#compatibility-49)Compatibility X12 EDI Connector v2.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020.

HIPAA

005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, and 005010X279A1.
### [](#known-limitations-6)Known Limitations Anypoint Studio 7.x may require more memory than allowed by the default settings to support X12 and HIPAA schema definitions. See the [X12 EDI Connector Guide](https://docs.mulesoft.com/x12-edi-connector/latest/) for details on changing the Studio memory settings. ## [](#2-0-0)2.0.0 **March 23, 2018** This release adapts X12 for use with Mule 4 and Studio 7. ### [](#compatibility-50)Compatibility X12 EDI Connector v2.0.0 is compatible with the following:
Application/Service Version

Mule

4.1.0 and later

X12

003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020.

HIPAA

005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A3, and 005010X279A1.
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Xero Accounting Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Xero Accounting (Xero Connector) enables you to access the Xero Accounting APIs. Xero Accounting APIs expose accounting and related functions of the main Xero application and can be used for a variety of purposes, such as creating transactions like invoices and credit notes, to extracting accounting data using the Reports endpoint. Guide: [Xero Accounting Connector User Guide](https://docs.mulesoft.com/jp/xero-accounting-connector/latest/) ## [](#1-1-9)1.1.9 **July 27, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core library is upgraded to version 2.22.1.

  • The log4j-api library is upgraded to version 2.25.5.

W-23539258
## [](#1-1-8)1.1.8 **April 22, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-core library is upgraded to version 2.21.1 to address reported security vulnerabilities.

W-21919325
## [](#1-1-7)1.1.7 **February 1, 2026** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core is upgraded to version 2.20.0.

  • The jackson-databind is upgraded to version 2.20.0.

W-20970379
## [](#1-1-6)1.1.6 **November 8, 2025** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-core.version library is upgraded to version 2.15.0.

  • The org.json:json library is upgraded to version 20250517.

W-20146885
## [](#1-1-5)1.1.5 **May 16, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

OpenJDK

8, 11, and 17
## [](#1-1-4)1.1.4 **April 4, 2023** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue Resolution ID

The overall stability and performance of the connector are improved.

W-12649858
## [](#1-1-3)1.1.3 **October 11, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

The Cannot deserialize value of type com.mulesoft.connectors.xeroaccounting.internal.model.LineItem error no longer occurs.

W-11843208

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853420
## [](#1-1-2)1.1.2 **April 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920481
## [](#1-1-1)1.1.1 **March 22, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

W-10767370
## [](#1-1-0)1.1.0 **March 11, 2022** ### What’s New - Added the **Get Invoices** operation. - Added the **On New Or Updated Invoices** source. ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
## [](#1-0-9)1.0.9 **January 4, 2022** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9820
## [](#1-0-8)1.0.8 **December 22, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9688
## [](#1-0-7)1.0.7 **December 16, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9622
## [](#1-0-6)1.0.6 **December 14, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9557
## [](#1-0-5)1.0.5 **December 9, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CSCA-1080
## [](#1-0-4)1.0.4 **November 18, 2021** ### Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9287
## [](#1-0-3)1.0.3 **August 10, 2021** ### [](#compatibility-17)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-15)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-0-2)1.0.2 **August 6, 2021** ### [](#compatibility-18)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-16)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-0-1)1.0.1 **July 8, 2021** ### [](#compatibility-19)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#fixed-issues-17)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-0-0)1.0.0 **April 29, 2021** ### [](#compatibility-20)Compatibility
Software Version

Mule runtime engine

4.2.1 and later

Open JDK

8 and 11
### [](#features)Features This is a new connector. For a list of supported configurations and operations, see the Xero Accounting Connector Reference Guide. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # XML Module Release Notes - Mule 4 XML Module processes and extracts data from an XML document. Use XML Module for cases that involve the use of XML standards such as XSLT, XPath, and XQuery, or XSD. Guide: [XML Module User Guide](https://docs.mulesoft.com/jp/xml-module/latest/) ## [](#1-4-8)1.4.8 **October 13, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The com.google.guava:guava library is upgraded to version 33.7.2-jre to address reported security vulnerabilities.

W-24454136
## [](#1-4-7)1.4.7 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0

OpenJDK

8, 11, and 17
## [](#1-4-6)1.4.6 **August 21, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Validate schema operation now correctly resolves cross-namespace xs:import/xs:include references when multiple XSD schemas are supplied for validation.

W-14657978

The Validate schema operation now correctly resolves referenced schemas when XML Module is configured inside a Mule Domain project.

W-23443267
## [](#1-4-5)1.4.5 **July 24, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0

OpenJDK

8, 11, and 17
## [](#1-4-4)1.4.4 **June 23, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The Validate schema operation now reports the underlying schema-validation error consistently across OpenJDK 8, 11, and 17. Previously, when a schema exceeded the JAXP secure-processing limit, the actionable cause was missing from the top-level error description on JDK 11 and 17.

W-16893452

The com.google.guava:guava component is upgraded to 33.6.0-jre.

W-3300013

The commons-io:commons-io component is upgraded to 2.22.0.

W-3300013

The org.apache.commons:commons-lang3 component is added at version 3.20.0.

W-22566314
## [](#1-4-3)1.4.3 **February 3, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The net.sf.saxon:Saxon-HE library is upgraded to version 11.7.

W-11165880

XML processing now includes protections against XML External Entity (XXE) injection attacks.

W-19325353

The XPath operation now correctly reports a Transformation Exception during initialization when invalid configurations are detected. This prevents the creation of objects with invalid states that previously resulted in NullPointerExceptions (NPE).

W-19325353
## [](#1-4-2)1.4.2 **December 13, 2023** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0

OpenJDK

8, 11, and 17
## [](#1-4-1)1.4.1 **July 27, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0
### Fixed Issues
Issue Resolution ID

Updated internal dependencies.

W-13831265
## [](#1-4-0)1.4.0 **January 10, 2022** ### What’s New - The **Validate schema** operation’s new field, **Schema contents**, supports the direct text input of a schema. This enables you to perform a schema validation. ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0
## [](#1-3-3)1.3.3 **February 10, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

XSLT

3.0

Xpath

3.1

XQuery

3.1

XSD

1.0
### Fixed Issues
Issue Resolution ID

The validators cache is no longer evicted due to inactivity. This avoids unexpected schema requests.

W-10678896
## [](#1-3-2)1.3.2 **November 19, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later
### Fixed Issues
Issue Resolution ID

Improved error handling for XML with invalid input errors.

XMLM-19
## [](#1-3-1)1.3.1 **July 7, 2021** ### [](#minimum-mule-version)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements)New Features and Enhancements None. ### [](#fixed-issues-8)Fixed Issues - XML Module incorrectly merged Namespace configurations and Namespace directory. (XMLM-17) ## [](#1-3-0)1.3.0 **March 3, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-2)New Features and Enhancements - The XPath function can now receive XML namespaces to evaluate the path expression. (XMLM-16) ### [](#fixed-issues-9)Fixed Issues None ## [](#1-2-3)1.2.3 **June 25, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-3)New Features and Enhancements None. ### [](#fixed-issues-10)Fixed Issues - XML Module schema violations do not inform line and columns numbers. (MULE-18448) ## [](#1-2-2)1.2.2 **October 22, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-4)New Features and Enhancements None. ### [](#fixed-issues-11)Fixed Issues - Use of `schemaFactory` was not synchronized in the XML module. (MULE-17600) ## [](#1-2-1)1.2.1 **September 20, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-5)New Features and Enhancements None. ### [](#fixed-issues-12)Fixed Issues - XPath function fails to retrieve attribute values. (MULE-17475) ## [](#1-2-0)1.2.0 **May 27, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-6)New Features and Enhancements None. ### [](#fixed-issues-13)Fixed Issues - Upgrade Guava to the latest version in the XML module. (MULE-16910) - Fixed an issue that prevented the 'validate-schema' operation from working concurrently. (MULE-16317) - XML module suggests the wrong expression in failure scenarios. (MULE-16239) - validate-schema is not working when an XSD references other schema. (MULE-15526) - Provide the option to reset the underlying controller of XSLTTransformer. (MULE-15259) ## [](#1-1-3)1.1.3 **January 17, 2019** ### [](#minimum-mule-version-7)Minimum Mule Version Mule 4.1.1 ### [](#new-features-and-enhancements-7)New Features and Enhancements None. ### [](#fixed-issues-14)Fixed Issues - Fixed an issue that prevented the 'validate-schema' operation from working concurrenctly. (MULE-16317) ## [](#1-1-2)1.1.2 **August 9, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version Mule 4.1.0 ### [](#new-features-and-enhancements-8)New Features and Enhancements None. ### [](#fixed-issues-15)Fixed Issues - `validate-schema` is not working with an XSD referencing other schema. (MULE-15526) ## [](#1-1-1)1.1.1 **July 2, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version Mule 4.1.0 ### [](#new-features-and-enhancements-9)New Features and Enhancements None. ### [](#fixed-issues-16)Fixed Issues - Reset underlying controller of XSLTTransformer after each transformation. (MULE-15259) ## [](#1-1-0)1.1.0 **March 1, 2018** ### [](#minimum-mule-version-10)Minimum Mule Version Mule 4.1.0 ### [](#new-features-and-enhancements-10)New Features and Enhancements None. ### [](#fixed-issues-17)Fixed Issues - Cannot set media type in XSLT transformer. (MULE-14651) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # XML Threat Protection ## [](#1-2-2)1.2.2 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-2-0)1.2.0 **February 07, 2024** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## [](#1-1-4)1.1.4 **Apr 30, 2020** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. ### [](#fixed-issues)Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## [](#1-1-3)1.1.3 **Jul 24, 2019** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Several performance improvements were introduced in this release. ## [](#1-1-2)1.1.2 **Apr 26, 2019** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Performance improvements. ## [](#1-1-1)1.1.1 **Jun 25, 2018** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Added `violationCategory` in the YAML configuration for Feedback Loop. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-5)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Reduced error-handling verbosity in templates. ### [](#fixed-issues-2)Fixed Issues - Fixed `ExpressionRuntimeException` error when a WSDL proxy receives an empty payload, or an invalid XML. ## [](#1-0-0)1.0.0 **Nov 13, 2017** ### [](#minimum-mule-version-6)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [XML Threat Protection for Mule 4](#api-manager::apply-configure-xml-threat-task.adoc) - [Known Issues](https://help.salesforce.com/s/issues) # XML Threat Protection Policy The XML Threat Protection Policy policy protects against malicious XML in API requests. For configuration details, see [XML Threat Protection Policy](https://docs.mulesoft.com/gateway/latest/policies-included-xml-threat-protection). ## [](#october-1-2026)October 1, 2026 ### What’s New - XML Threat Protection Policy policy definition version 1.2.2 is now supported by Omni Gateway. - This release updates policy metadata only. There’s no functional change. ## [](#february-27-2025)February 27, 2025 ### What’s New - XML Threat Protection Policy policy implementation version 1.0.2 is now supported by Omni Gateway. - XML Threat Protection Policy policy definition version 1.2.0 is now supported by Omni Gateway. # Zendesk Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Zendesk enables you to connect to the Zendesk’s Support API. Guide: [Zendesk Connector User Guide](https://docs.mulesoft.com/jp/zendesk-connector/latest/) ## [](#1-1-14)1.1.14 **October 16, 2026** ### Compatibility
Software Version

Mule

4.2.1 or later

Zendesk Support API

N/A

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson-databind library is upgraded to version 2.22.3.

  • The guava library is upgraded to version 33.7.2-jre to address CVE-2026-102554.

W-3300013, W-24423997
## [](#1-1-13)1.1.13 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.2.1 or later

Zendesk Support API

N/A

OpenJDK

8, 11, and 17
## [](#1-1-12)1.1.12 **August 24, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule

4.2.1 or later

Zendesk Support API

N/A

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-databind library is upgraded to version 2.22.2 to address reported security vulnerabilities.

W-23441684
## [](#1-1-11)1.1.11 **July 19, 2026** ### Compatibility
Software Version

Mule

4.2.1 or later

Zendesk Support API

N/A

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.22.0.

  • The jackson-databind library is upgraded to version 2.22.0.

  • The guava library is upgraded to version 33.6.0-jre.

  • The commons-lang3 library is upgraded to version 3.18.0.

W-22899607
## [](#1-1-10)1.1.10 **April 3, 2026** ### Compatibility
Software Version

Mule

4.2.1 or later

Zendesk Support API

N/A

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The commons-io library is upgraded to version 2.21.0.

  • The json library is upgraded to version 20251224.

  • The guava library is upgraded to version 33.5.0-jre.

W-21506502

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21404087
## [](#1-1-9)1.1.9 **May 13, 2025** ### Compatibility
Software Version

Mule

4.2.1 or later

Zendesk Support API

N/A

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The New ticket created and Existing ticket updated operations now continue polling even if a 429: TOO_MANY_REQUEST error occurs.

W-18232839
## [](#1-1-8)1.1.8 **May 23, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A

OpenJDK

8, 11, and 17
## [](#1-1-7)1.1.7 **February 7, 2023** ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A

OpenJDK

8 and 11
### Fixed Issues
Issue Resolution ID

The external ID value is now represented as a string instead of a number as per the Zendesk API.

W-12360287
## [](#1-1-6)1.1.6 **December 12, 2022** ### What’s New - The com.fasterxml.jackson.core library is upgraded to version 2.13.4.1. ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
### Fixed Issues
Issue Resolution ID

The com.fasterxml.jackson.core library is upgraded to version 2.13.4.1 to address reported security vulnerabilities.

W-11933496

The connection no longer breaks when Zendesk sources are idle for long durations when deployed on CloudHub.

W-12040415
## [](#1-1-5)1.1.5 **July 7, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
### Fixed Issues
Issue ID

Previously, when a new ticket was created, the New ticket created and Existing ticket updated sources were both invoked. Now, only the New ticket created source is invoked when creating a new ticket.

W-11264280
## [](#1-1-4)1.1.4 **April 11, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.13.1 to com.fasterxml.jackson.core:jackson-databind:2.13.2.2.

W-10920460
## [](#1-1-3)1.1.3 **February 21, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
### Fixed Issues
Issue ID

Fixed Zendesk vulnerability regarding jackson-databind library.

W-10702347
## [](#1-1-2)1.1.2 **February 10, 2022** ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CSCA-1318
## [](#1-1-1)1.1.1 **November 3, 2021** ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
### [](#fixed-issues-12)Fixed Issues - Optimized the connector to improve its overall stability and performance. ## [](#1-1-0)1.1.0 **October 5, 2021** ### What’s New - Added new operations: - Upsert an organization - Upsert a user - Search - Removed **apiVersion** as a default value from the **baseUri** connection parameter. Now, **apiVersion** is a separate connection parameter in all of the connection providers. ### Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
## [](#1-0-1)1.0.1 **February 12, 2021** ### [](#compatibility-16)Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
### [](#fixed-issues-13)Fixed Issues The connector was not discoverable in Anypoint Studio. ## [](#1-0-0)1.0.0 **January 29, 2021** ### [](#compatibility-17)Compatibility
Software Version

Mule

4.2.1 and later

Zendesk Support API

N/A
Additional information can be found here: - [https://developer.zendesk.com/api-reference/introduction/introduction/](https://developer.zendesk.com/api-reference/introduction/introduction/) - [https://developer.zendesk.com/api-reference/](https://developer.zendesk.com/api-reference/) ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Zoom Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Zoom (Zoom Connector) enables you to access the Zoom API. Guide: [Zoom Connector User Guide](https://docs.mulesoft.com/jp/zoom-connector/latest/) ## [](#1-0-8)1.0.8 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-7)1.0.7 **August 26, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The JSON library is upgraded to version 20260814.

  • The commons-collections4 library is upgraded to version 4.6.0.

W-23441686
## [](#1-0-6)1.0.6 **January 31, 2026** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The commons-collections library is migrated to commons-collections4 version 4.5.0.

W-20970357
## [](#1-0-5)1.0.5 **June 20, 2024** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

You can now install Zoom Connector in Anypoint Studio as intended.

W-16051747
## [](#1-0-4)1.0.4 **May 3, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

OpenJDK

8, 11, and 17
## [](#1-0-3)1.0.3 **January 13, 2022** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9846
## [](#1-0-2)1.0.2 **December 20, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9690
## [](#1-0-1)1.0.1 **December 16, 2021** ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9563
## [](#1-0-0)1.0.0 **September 28, 2021** ### What’s New This is a new connector. For a list of supported configurations and operations, refer to the Zoom Connector Reference Guide. ### Compatibility
Software Version

Mule runtime engine

4.3.0 and later

Open JDK

8 and 11
## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Zuora AQuA Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Anypoint Connector for Zuora AQuA (Zuora AQuA Connector) enables you to connect to the Zuora platform and use all of the operations provided by the Zuora AQuA API. Guide: [Zuora AQuA Connector User Guide](https://docs.mulesoft.com/jp/zuora-aqua-connector/latest/) ## [](#1-0-19)1.0.19 **October 16, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.3.

  • The guava library is upgraded to version 33.7.2-jre.

W-24134322
## [](#1-0-18)1.0.18 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
## [](#1-0-17)1.0.17 **August 14, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The org.json library is upgraded to version 20260719.

  • The log4j-slf4j-impl library is upgraded to version 2.26.1.

  • The gson library is upgraded to version 2.14.0.

  • The commons-io library is upgraded to version 2.22.0.

W-23441687
## [](#1-0-16)1.0.16 **July 22, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The jackson-databind library is upgraded to version 2.22.1 to fix reported security vulnerabilities.

W-23467611
## [](#1-0-15)1.0.15 **June 26, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now deploys successfully with all required classes and packages included in the Mule plugin JAR, preventing deployment and production runtime failures.

W-23150920
## [](#1-0-14-deprecated)1.0.14 (Deprecated) **June 16, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The aspectj library is upgraded to version 1.9.25.1 to address reported security vulnerabilities.

W-22941391
## [](#1-0-13)1.0.13 **January 31, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The log4j-slf4j library is upgraded to version 2.25.3.

  • The gson library is upgraded to version 2.12.0.

W-20970548
## [](#1-0-12)1.0.12 **August 16, 2025** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer hangs while trying to process a failing payload.

W-17497908
## [](#1-0-11)1.0.11 **March 20, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8, 11, and 17
## [](#1-0-10)1.0.10 **October 11, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853425
## [](#1-0-9)1.0.9 **April 5, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920470
## [](#1-0-8)1.0.8 **January 4, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9806
## [](#1-0-7)1.0.7 **December 22, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9678
## [](#1-0-6)1.0.6 **December 14, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9572
## [](#1-0-5)1.0.5 **November 18, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### Fixed Issues
Issue ID

Upgraded the com.google.code.gson library due to a security vulnerability.

CONN-9288
## [](#1-0-4)1.0.4 **February 17, 2021** ### [](#compatibility-16)Compatibility Zuora AQuA Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### [](#fixed-issues-14)Fixed Issues The connector could not be used in the same flow as other REST-SDK based connectors. (CONN-7583) ## [](#1-0-3)1.0.3 **November 10, 2020** ### [](#compatibility-17)Compatibility Zuora AQuA Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### [](#fixed-issues-15)Fixed Issues - Fixed the only security vulnerability. ## [](#1-0-2)1.0.2 **June 3, 2020** ### [](#compatibility-18)Compatibility Zuora AQuA Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R249

OpenJDK

8 and 11
### [](#fixed-issues-16)Fixed Issues - Fixed a recently reported security vulnerability. ## [](#1-0-1)1.0.1 **May 4, 2020** ### [](#compatibility-19)Compatibility Zuora AQuA Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R249
### [](#fixed-issues-17)Fixed Issues - Upgraded the File Connector version to 1.3.2 to fix a dependency-related vulnerability. (CONN-5802) - Upgraded the MUnit version to 2.2.4. ## [](#1-0-0)1.0.0 **January 15, 2020** ### [](#compatibility-20)Compatibility Zuora AQuA Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R249
### [](#features)Features Zuora AQuA Connector is fully integrated with the latest AQuA REST API version. - The added operations are: - Get Last Job Completed - Returns the details of the last completed job. - Delete a Running Job - Deletes the current job, only if the job is not complete. If the job is complete, an error is thrown. - Export Deleted Data - Submits a request to export deleted records. - Get job Results - Retrieves an aggregate query using the Job ID. - Get Results Files - This REST API retrieves the results in the specified file format. - Post Query or Export Deleted Data - After a job is created, the ID of the job is stored in the Object Store, which makes the ID available for a Source. - There is a Source, which searches for a job ID in a given object store and periodically polls for the status of the jobs retrieved from the object store and returns the results of the completed jobs. - The AQuA Source has cluster support by default. - A default back pressure mechanism from Mule runtime engine is used for the Zuora AQuA Source. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues) # Zuora Connector Release Notes Support Category: [Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf) Guide: [Zuora Connector User Guide](https://docs.mulesoft.com/jp/zuora-connector/latest/) ## [](#6-0-19)6.0.19 **October 13, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.3.

  • The guava library is upgraded to version 33.7.2-jre.

W-24264132
## [](#6-0-18)6.0.18 **September 4, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
## [](#6-0-17)6.0.17 **August 14, 2026** ### What’s New - This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one. ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The JSON-Java library is upgraded to version 20260719.

  • The Jackson Databind library is upgraded to version 2.22.1.

  • The Log4j SLF4J binding library is upgraded to version 2.26.1.

W-23441688
## [](#6-0-16)6.0.16 **July 1, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The jackson library is upgraded to version 2.22.0.

  • The log4j library is upgraded to version 2.26.0.

  • The commons-io library is upgraded to version 2.22.0.

W-23136400
## [](#6-0-15)6.0.15 **June 10, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

MULE-ZUORA-CONNECTOR:CONNECTIVITY connection timeout errors no longer occur on individual CloudHub workers when the connector executes operations under heavy concurrent loads. The connector now manages thread pool resources effectively and processes token refreshes without trapping threads or stopping worker processing.

W-22494942
## [](#6-0-14)6.0.14 **April 12, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector now uses updated packaging to prevent the DuplicateExportedPackageException error and the exported packages no longer conflict with the REST SDK packages of other connectors when you use multiple REST-based connectors in the same Mule application.

W-21760377

These libraries are upgraded to address reported security vulnerabilities:

  • The json library is upgraded to version 20251224.

  • The jackson-databind library is upgraded to version 2.21.1.

  • The commons-lang3 library is upgraded to version 3.20.0.

  • The commons-text library is upgraded to version 1.15.0.

  • The commons-io library is added at version 2.21.0.

W-21526809
## [](#6-0-13)6.0.13 **January 31, 2026** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The log4j-slf4j library is upgraded to version 2.25.3.

  • The commons-lang3 library is upgraded to version 3.18.0.

W-20970555
## [](#6-0-12)6.0.12 **April 29, 2025** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Access tokens are now refreshed in the background without affecting the system’s ability to handle HTTP requests.

W-18248444

The com.fasterxml.jackson.core library is upgraded to version 2.18.3 to address reported security vulnerabilities.

W-18265115

The org.apache.logging.log4j library is upgraded to version 2.24.3 to address reported security vulnerabilities.

W-18265115
## [](#6-0-11)6.0.11 **March 14, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8, 11, and 17
## [](#6-0-10)6.0.10 **November 15, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue Resolution ID

The Create custom object records operation no longer sends an HTTP request with two authorization headers.

W-12047818
## [](#6-0-9)6.0.9 **October 25, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue ID

The component org.apache.commons library is upgraded to version 1.10.0 to address reported security vulnerabilities.

W-11913980
## [](#6-0-8)6.0.8 **October 11, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue ID

The com.fasterxml.jackson.core library is upgraded to version 2.14.0-rc1 to address reported security vulnerabilities.

W-11853412
## [](#6-0-7)6.0.7 **April 7, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue ID

Fixed reported security vulnerabilities by upgrading the Jackson Databind library from com.fasterxml.jackson.core:jackson-databind:2.12.6 to com.fasterxml.jackson.core:jackson-databind:2.12.6.1.

W-10920478
## [](#6-0-6)6.0.6 **January 4, 2022** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9815
## [](#6-0-5)6.0.5 **December 23, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9691
## [](#6-0-4)6.0.4 **December 14, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue ID

Upgraded library dependencies.

CONN-9571
## [](#6-0-3)6.0.3 **October 28, 2021** ### Compatibility
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### Fixed Issues
Issue ID

Optimized the connector to improve its overall stability and performance.

CSCA-903
## [](#6-0-2)6.0.2 **February 22, 2021** ### [](#compatibility-18)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### [](#features)Features None. ### [](#fixed-in-this-release)Fixed in this release - The connector could not be used in the same flow as other REST-SDK based connectors. (CONN-7582) - The Zuora Connector **Get subscriptions** operation returned an empty response. (SE-19359) ## [](#6-0-1)6.0.1 **November 16, 2020** ### [](#compatibility-19)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R280
### [](#features-2)Features None. ### [](#fixed-in-this-release-2)Fixed in this release The connector sent an HTTP request with two Authorization headers, which resulted in a `400 Bad Request` error. (SE-18336) ## [](#6-0-0)6.0.0 **August 25, 2020** ### [](#compatibility-20)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R280

OpenJDK

8 and 11
For detailed information about the new features and changed functionality in Zuora Connector 6.0.0, see [Zuora Connector - Upgrade and Migrate](https://docs.mulesoft.com/jp/zuora-connector/latest/zuora-connector-upgrade-migrate) ### [](#features-3)Features Zuora Connector 6.0.0 includes the following new operations: - Generate an OAuth token - Object POSTFeature - Get workflow task usage - Object PUTFeature - PUT Rev Pro Accounting Codes - Update subscription custom fields of a specified subscription version ### [](#changes)Changes The following operations were deprecated in Zuora Connector 6.0.0: - Create Usage Imports - Create usage records - Request breakdown of credit memo items by order - Request breakdown of invoice items by order - Delete schema of Usage custom field definition - Delete usage record - CRUD: Delete payment method snapshot - Get Usage custom field definition - Get rating results by account - Get rating results by charge - Get rating results by subscription - Get rated usage by account - Get rated usage by charge - Get rated usage by subscription - Get usage record - Get details of usage import - Download usage import failure file - Download usage import file - Download usage import failure file - Get status of usage import - Download usage file template - Query usage records - Query usage records in stream - Get breakdown of credit memo by order - Get breakdown of invoice by order - Get rated result for order - Set schema of Usage custom field definition - Update usage record ## [](#5-0-0)5.0.0 **January 15, 2020** ### [](#compatibility-21)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.2.1 and later

Zuora

R249
For detailed information about the new features and changed functionality in Zuora Connector 5.0.0, see [Zuora Connector - Upgrade and Migrate](https://docs.mulesoft.com/jp/zuora-connector/latest/zuora-connector-upgrade-migrate) ### [](#new-features)New Features Zuora Connector 5.0.0 includes the following new operations: - Create custom object definition - Create custom object records - Create usage records - DELETE Data Query Job - Delete a workflow by ID - Export a workflow - Get a workflow by ID - Get workflows - Import a workflow - Run a workflow - Delete schema of Usage custom field definition - Delete usage record - Download usage file template - Download usage import failure file - Download usage import file - Get usage custom field definition - Get details of usage import - Get rated usage by account - Get rated usage by charge - Get rated usage by subscription ### [](#changes-2)Changes - Four operations were removed from the connector and were added separately in the new Anypoint Connector for AQuA (AQuA Connector): - Aqua-get-job-results - Aqua-get-last-job-completed - Aqua-post-query-or-export-deleted-data - Aqua-delete-a-running-job - The schema and namespace are the same, but there are some changes in the Anypoint Studio display names. - Changes to operations names - Changes in fields and values - Changes in operations metadata ## [](#4-2-1)4.2.1 **July 22, 2019** ### [](#compatibility-22)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.1.1 and later

Zuora

R249
### [](#features-4)Features - Updated HTTP Connector dependency to version 1.5.5. (CONN-2524) ## [](#4-2-0)4.2.0 **July 16, 2019** ### [](#compatibility-23)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

Zuora

REST API version R249
### [](#features-5)Features - Version 4.2.0 of the connector supports the Zuora API release 249 from 2019-06-20. - [Zuora API updates change log](https://community.zuora.com/home). ## [](#4-1-0)4.1.0 **November 16, 2018** ### [](#compatibility-24)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later

Zuora

R220
### [](#features-6)Features This version of Zuora Connector supports the Zuora AQuA API. The newly added operations are: - Get Last Job Completed - Returns the details of the last completed job. - Delete a Running Job - Deletes the current job, only if the job is not complete. If the job is complete, an error is thrown. - Export Deleted Data - Submits a request to export deleted records. - Post Query with API Version - Submits an aggregate query with a specified API version. - Post Query with Notification - Submits an aggregate query with a request for the user to be notified once the job is complete. - Post Query with Retrieval Time - Submits an aggregate query to retrieve those records that were either newly created or modified after a specified time. ## [](#4-0-0)4.0.0 **February 27, 2018** ### [](#compatibility-25)Compatibility Zuora Connector is compatible with:
Application/Service Version

Mule

4.0.0 and later
### [](#features-7)Features This version of Zuora Connector is based on the Zuora REST API offering the entire capabilities of this API and no longer supports the SOAP API. ## [](#see-also)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Known Issues](https://help.salesforce.com/s/issues)