MuleSoft · CloudHub 2.0
Runtime Version not supported for this target
Short answer
"Runtime Version not supported for this target" appears when deploying to CloudHub 2.0 with a Mule runtime it does not accept, such as Mule 4.3.0. Deploy on a supported LTS or Edge runtime and rebuild the JAR.
VerifiedLast verified
01Error text
Runtime Version not supported for this target02Likely causes
- Deployments on Mule 4.3.0 are blocked on CloudHub 2.0.
- The app's
minMuleVersioninmule-artifact.jsonpoints at an unsupported runtime.
03How to fix it
- Choose a supported LTS or Edge runtime version for the deployment.
- Check
minMuleVersioninmule-artifact.json. - Rebuild the application JAR and deploy again.
04Official documentation
→Related errors
- Failed to deploy to CloudHub: 400"Failed to deploy to CloudHub: 400" in Anypoint Code Builder means the root organization or business group you are deploying to does not have enough vCore allocation. Increase the vCore allocation for it in the Sandbox environment.
- 502 Bad Gateway during traffic switch to CloudHub 2.0A 502 Bad Gateway while switching traffic from CloudHub to CloudHub 2.0 usually means the dedicated load balancer cannot talk to the new app. Check that the upstream uses TLS 1.2 or higher and that the app's listener binds to 0.0.0.0.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer