The following error appears when deploying a Mule application to a CloudHub 2.0 Private Space using Anypoint CLI v4, typically via a CICD pipeline (GitHub Actions, Jenkins, etc.):
Application not found. Using 'deploy' command...
Using Exchange asset version: x.x.x
Deploying <app-name> ...
› Error: Runtime Version not supported for this target.
❌ Deployment failed with exit code 2
This occurs most often after the Private Space runtime has been upgraded (e.g. from 4.11.6 to 4.12.2) and the application has never been deployed to that environment before.
Two conditions cause this error:
1. New application deployments only accept the current Private Space runtime version.
After a Private Space upgrade, existing running applications retain their previous runtime version and can continue to be updated on it. However, when creating an application for the first time in that environment, only the version currently installed on the Private Space is accepted. Passing any older version string will fail.
2. The runtime version must use the fully-qualified build-tag format.
The CLI requires the exact version string shown in the Runtime Manager UI Runtime Version dropdown, which includes a build-tag suffix:
- Edge channel example: 4.12.2:8e
- LTS channel example: 4.6.19:1
Passing a bare version number such as 4.11.6 or 4.12.2 (without the suffix) causes this error regardless of whether that version is available on the target.
In CICD pipelines, the runtime version is commonly stored in a pipeline variable (e.g. MULE_VERSION in GitHub Actions repository variables). If that variable was set to a bare version number and has not been updated after the Private Space upgrade, both conditions are triggered simultaneously.
this value.
Step 2 — Update your deployment configuration.
CLI deploy command (new app, positional argument):
anypoint-cli-v4 runtime-mgr:application:deploy \
<appName> <target> 4.12.2:8e <artifactId> \
--releaseChannel="Edge" ...
CLI modify command (existing app):
anypoint-cli-v4 runtime-mgr:application:modify \
<appId> \
--runtimeVersion="4.12.2:8e" \
--releaseChannel="Edge" ...
CICD pipeline variable: update the variable (e.g. MULE_VERSION) from the bare version to the fully-qualified string (e.g. 4.12.2:8e). No changes to the pipeline YAML are required.
Step 3 — Add --releaseChannel to first-time deploy commands.
The runtime-mgr:application:deploy command (new app creation) does not inherit the release channel from any previous configuration. Always pass --releaseChannel explicitly (Edge or LTS) to ensure the correct channel is used and to prevent the CLI from defaulting to an unintended channel.
- Deploying Apps to CloudHub 2.0 with Anypoint CLI: https://docs.mulesoft.com/cloudhub-2/ch2-deploy-cli
- CloudHub 2.0 OS Patch Updates and version format: https://docs.mulesoft.com/cloudhub-2/ch2-patch-updates
- KB 005101382 — Runtime Version not supported for this target (Mule Maven Plugin): https://help.salesforce.com/s/articleView?id=005101382&type=1
- KB 004333268 — Mule Maven Plugin Error Runtime Version not supported: https://help.salesforce.com/s/articleView?id=004333268&type=1
005393363

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.