Contact Us 1-800-596-4880
  1. Homepage
  2. Anypoint Code Builder

  3. Troubleshooting

Troubleshooting

logo cloud IDE Cloud IDE

logo desktop IDE Desktop IDE

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.

Troubleshoot errors and warnings you encounter when using Anypoint Code Builder.

For tasks that support the troubleshooting process, see:

About the Cloud IDE Environment

The Anypoint Code Builder cloud IDE is a managed, hosted environment. Your workspace is a dedicated directory assigned to you at /home/your-user-name/, and you have full control to create, edit, and manage files within it.

Unlike a local development environment, you don’t have access to underlying server system folders, and you don’t need to. All troubleshooting steps provide solutions you can perform directly from the IDE without requiring server access or file system permission changes.

Check for Problems and Issues

When you don’t know how to resolve an issue, the first step is to check for and review problems, console output, and logs. Error messages and logs list underlying issues that can help you understand what went wrong and what requires attention.

Export Troubleshooting Information

If the MuleSoft support team requests troubleshooting information about your project, export a compressed file that contains your project’s workspace folders, logs, and information about environment variables, CPU, operating system, and system properties.

  1. Open the Command Palette.

    Show me how

    • Use the keyboard shortcuts:

      • Mac: Cmd+Shift+p

      • Windows: Ctrl+Shift+p

    • In the desktop IDE, select View > Command Palette.

    • In the cloud IDE, click the (menu) icon, and select View > Command Palette.

  2. Provide this command:

    MuleSoft: Export Troubleshooting Information

  3. When you receive a notification about the information that the command extracts, click Continue.

    When the process is complete, the IDE shows this message:

    Collecting information...: Generating compressed file

  4. Click Open folder to locate the file.

    The command places the file in your home directory. The filename has the prefix acb-troubleshooting, for example, /Users/me/acb-troubleshooting-w9ffppmq.tar.gz.

  5. Provide a copy of the file to the support team.

Manage Your Cloud IDE Instance

Manage your cloud IDE instance directly from the Anypoint Code Builder in Anypoint Platform.

Cloud IDE management page
1 Version and IDE Details:

Shows the version of your Anypoint Code Builder cloud IDE instance. You can hover over View IDE Details to view some internal details about your cloud IDE instance:

  • Image: The ID of the image of your cloud IDE instance.

  • URL: The URL to directly access your cloud IDE instance.
    This URL is necessary to ping your locally deployed Mule application when debugging.

  • Created at: Date and time of the creation of the cloud IDE instance.
2 Reboot: Button for rebooting your cloud IDE instance.
3 Delete: Button for deleting your cloud IDE instance.

Deletion is permanent and cannot be undone. The process removes all the projects hosted on the IDE instance.

Check for Anypoint Extension Pack Installation

To determine whether Anypoint Code Builder extensions are installed in the desktop IDE, check for the Anypoint Extension Pack in the Extensions: Marketplace panel of the IDE:

  1. In the Activity Bar, click the Extensions icon to open the Extensions: Marketplace panel.

    To find this icon, see Discovering the UI.

  2. In the panel’s search field, type Anypoint to locate Anypoint Extension Pack in the list of installed extensions.

Maven 401 Unauthorized Error

If Maven fails to download dependencies with a 401 Unauthorized error when opening or building a MuleSoft project, configure authentication for the MuleSoft Enterprise Repository.

See Authenticating to MuleSoft Repositories for instructions on configuring your credentials.

Folder Permission Error

Error:

EACCES: permission denied, mkdir '/home/XXXX/.vscode'

Cause: In the Anypoint Code Builder cloud IDE, you must save your work in your designated workspace folder to keep your projects secure and accessible. This error occurs when you attempt to create or save a project outside of that workspace, in a system-level folder such as /home, /, or .config.

Solution: Create and import your projects within your /home/your-user-name/ folder or a subdirectory under it. The cloud IDE automatically provides this folder with your username. Also avoid /home/AnypointCodeBuilder, which is reserved for Mule and Java downloads.

Settings Sync Overwrites Home Directory on a New Computer

When you sync your VS Code profile to a new computer, all profile settings are transferred, including the Mule: Home Directory setting. If the username on the new computer differs from the one on the original computer, the synced path is invalid, and the extension fails to load with an error like the following:

Error: EPERM: operation not permitted, mkdir 'C:\Users\<original-username>\AnypointCodeBuilder\java\jdk-17.0.13+11'

To fix this issue, update the Mule: Home Directory setting on the new computer to the correct path for that machine. See Mule: Home Directory.

To prevent this issue when syncing profiles across computers with different usernames, exclude the mule.homeDirectory setting from VS Code settings sync by adding the following to your settings.json:

"settingsSync.ignoredSettings": [
  "mule.homeDirectory"
]

Disable Components to Isolate Issues

When debugging a flow, you can disable (comment out) individual components directly in the canvas. This allows you to isolate and test parts of your logic without removing or rewriting anything. For example:

  • Temporarily disable a Transform or Logger to test a different path.

  • Comment out an entire flow or error handler to simplify the execution logic.

  • Disable MUnit test processors to troubleshoot specific assertions.

To disable a component:

  1. Right-click it in the canvas.

  2. Select Disable Component.

Disabled components are unavailable in the canvas and are ignored at runtime. In the code editor, the block is wrapped in an XML comment.

Once the issue is resolved, you can re-enable the component or use Delete to remove disabled items.

View Error Messages and Warnings in the Canvas

Anypoint Code Builder shows validation issues directly in the canvas to help you resolve problems faster. Hover over a component to see a tooltip listing errors and warnings, along with affected field names.

The configuration sidebar also displays validation messages at the node level.

Field-level errors appear inline during component configuration.

Hover over a component with a red dot to view error details in the canvas.

Perform a Clean Reinstallation

If you experience persistent issues that other troubleshooting steps don’t resolve, perform a clean reinstallation of Anypoint Extension Pack:

  1. Close VS Code completely.

  2. Uninstall Anypoint Extension Pack:

    1. Open VS Code.

    2. From the Activity Bar, open the Extensions panel.

    3. Find and select Anypoint Extension Pack.

    4. Click Uninstall.

    5. Close VS Code.

  3. Delete the anypoint-code-builder folder from your user directory:

    • Mac: ~/AnypointCodeBuilder

    • Windows: C:\Users\<username>\AnypointCodeBuilder

  4. Optionally, delete cached extension data from the VS Code extensions folder:

    • Mac: ~/.vscode/extensions/

    • Windows: C:\Users\<username>\.vscode\extensions\

      Remove any folders starting with salesforce.mule-dx- or mulesoftinc.mule-dx-.

  5. Reopen VS Code and reinstall Anypoint Extension Pack from the Extensions Marketplace.

This procedure removes downloaded Mule runtime versions and Java versions. You can re-download them after reinstalling.

See Also