--- schema_version: "1" id: e3d616f8f66bc8213c6d6d6c9cefc480efc32fdc9b2c3e834159e503cd0ad98b title: Runtime Manager 2.11.x Release Notes collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/runtime-manager/runtime-manager-2.11.x-release-notes.md canonical_url: https://docs.mulesoft.com/release-notes/runtime-manager/runtime-manager-2.11.x-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: a1d0eb2c1cc8068d2d175de4fa9b9b40b48153054a71b3a3fd7fed4fcf117396 description: MuleSoft Documentation Site latest: true --- --- product: Release Notes version: master --- # Runtime Manager 2.11.x Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## 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 There are no new features or enhancements in this release. ### Changes in This Release There are no changes in this release. ### 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 There are no known limitations or workarounds in this release. ### Upgrade Requirements There are no upgrade requirements for this release. ### Compatibility Notes There are no compatibility notes in this release. ## 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 There are no new features or enhancements in this release. ### 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 - 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 There are no known limitations or workarounds in this release. ### Upgrade Requirements There are no upgrade requirements for this release. ### Compatibility Notes There are no compatibility notes in this release. ## 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 There are no new features or enhancements in this release. ### Changes in This Release This release contains no feature changes. ### Fixed Issues - The issue where orphan deployments were left in the database when concurrent deployment requests were executed is fixed. ### Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### Upgrade Requirements There are no upgrade requirements for this release. ### Compatibility Notes There are no compatibility notes in this release. ## 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 There are no new features or enhancements in this release. ### Changes in This Release This release contains no feature changes. ### 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 There are no known limitations or workarounds in this release. ### Upgrade Requirements There are no upgrade requirements for this release. ### Compatibility Notes There are no compatibility notes in this release. ## 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 - Environment information is now being sent to Audit Log for Hybrid Deployments. ### Changes in This Release This release contains no feature changes. ### Fixed Issues - SE-10644: Re-deployment fails in hybrid with "Duplicate key polling://snippet-pollerFlow/" error ### Known Limitations and Workarounds There are no known limitations or workarounds in this release. ### Upgrade Requirements There are no upgrade requirements for this release. ### Compatibility Notes There are no compatibility notes in this release. ## See Also - [Known Issues](https://help.salesforce.com/s/issues)