If you’re running into strange errors when installing Anypoint Code Builder (ACB)—like the dreaded Mule Platform process finished. Please, restart.—follow the steps below to start fresh and resolve common problems.
In this post, you'll find:
- How to start from scratch (remove the extension and any cache for a fresh install)
- Some best practices when opening an existing project
- How to download and/or set up a new Mule Runtime and Java versions
- How to fix the
503error when using Autodiscovery - How to fix the
400 INVALID_ASSET_METADATAerror when deploying your scaffolded Mule app to CloudHub 2.0
🧹 Start from Scratch
These steps can clear out random issues and give you a clean slate to work from.
- Uninstall the Anypoint Extension Pack from VS Code:
- Confirm you have Git installed. If not, download it here.
- Make sure your VS Code is up to date:
- Help > Check for Updates (Windows/Linux)
- Code > Check for Updates (Mac)
- Completely close VS Code (e.g.
Cmd + Qon Mac). - In your user folder, search for the
AnypointCodeBuilderdirectory and delete it:
- Still in your user folder, open the
.vscodefolder. You have two cleanup options:-
Clean slate: Delete the entire
extensionsfolder to reset all extensions (note: this removes all VS Code extensions). -
Selective cleanup: Inside
.vscode/extensions, remove only the folders starting withsalesforce.mule.
-
Clean slate: Delete the entire
- Reopen VS Code and reinstall the Anypoint Extension Pack:
✅ Once installed, wait for the extensions to finish loading completely. Most issues should now be resolved!
📁 Opening an Existing Project?
If you're working on an existing ACB project:
- Always open the project from its root folder—not from a workspace or subfolder.
Example:
- To double-check that your setup is working:
- Try designing a new API spec or
- Create a simple integration first.
Once those basic operations run smoothly, you're ready to explore the rest of your project. 🚀
👟 Runtime download / version
Once you open the project, it might ask you to download a Mule Runtime. You can either click the 'Set Versions' button or right click on a Mule Configuration File (XML file) and select Open Mule Project Properties
Select your Mule Runtime and Java Version and click on Apply
It will then ask you to sign in to Anypoint Platform in order to download the Mule Runtime. Follow the prompts to sign in. Once you log in, you will see your username at the bottom-right.
After it finishes downloading both (Mule/Java), you will find the standalone folders in your AnypointCodeBuilder folder.
🛠️ Fixing the 503 Error
If you're getting a 503 error when calling your running app:
- Open the ACB Settings:
- Search for
Mule > Runtime: Default Arguments - At the end of the existing text, append this flag:
-M-Danypoint.platform.gatekeeper=disabled
- Restart your app.
This will disable the connection to Anypoint Platform when using Autodiscovery in your Mule app to be able to test locally. If you want to be able to connecto to Anypoint Platform to apply security policies or other settings, follow the same steps but add your Anypoint Platform credentials instead, like this:
-M-Danypoint.platform.client_id=your_client_id -M-Danypoint.platform.client_secret=your_client_secret
For detailed information in both Studio and ACB, see Quick guide to applying MuleSoft's API Autodiscovery
🛠️ Fixing the 400 INVALID_ASSET_METADATA Error
When trying to deploy your Mule app to CloudHub 2.0 from ACB, you might get an error saying
Failed to deploy to CloudHub 2.0:
PUBLISH 400: INVALID_ASSET_METADATA.
The asset is invalid.
Error while trying to set type: app.
Expected type is: rest-api.
The reason is that the artifactId is the same in both:
- API Spec published in Exchange
- Mule project implementation in ACB
So, it's expecting you to publish a rest-api (the api spec that is already in Exchange) but you're trying to publish an app.
To fix it, change the artifactId you have on the Mule project in the pom.xml file and retry deploying to CH2.
Top comments (0)