--- schema_version: "1" id: 321016d4e053e206e65c4ff464ee0bbbf2203bf8171b36abf60a2b0392228e3a title: Troubleshooting collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/troubleshooting.md canonical_url: https://docs.mulesoft.com/anypoint-code-builder/troubleshooting source_site: docs.mulesoft.com content_type: documentation content_hash: 29a58a321cee348d3fa68f5c67a1c65d5deccdc850e5d557616c46f2d57d5777 description: MuleSoft Documentation Site latest: true --- --- product: Anypoint Code Builder version: master --- # Troubleshooting > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Troubleshoot errors and warnings you encounter when using Anypoint Code Builder. - [Missing or Disabled Features](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-missing-features) - [Authentication Errors](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-authentication-errors) - [Deployment Errors](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-deploy-errors) - [Implementation Errors](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-implementation-errors) - [Mule Runtime Issues and Errors](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-mule-runtime-errors) - [Project Loading Errors](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-loading-errors) - [MCP Server Issues](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-mcp-server) For other issues and workarounds, see [Known Issues](https://docs.mulesoft.com/anypoint-code-builder/acb-release-notes#known-issues) in the Anypoint Code Builder Release Notes. For tasks that support the troubleshooting process, see: - [Check for Problems and Issues](#check-logs) - [Check Console Logs for Extension Issues](#check-console-logs) - [Export Troubleshooting Information](#export-troubleshooting-info) - [Performance Troubleshooting](#performance-troubleshooting) ## 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. - To view centralized errors and warnings, open the **ACB Logs** panel. See [View Errors and Warnings in ACB Logs](https://docs.mulesoft.com/anypoint-code-builder/start-open-output-panel#acb-logs). - To view detailed logs for in-depth investigation, use the **Output** panel. See [View Detailed Logs in the Output Panel](https://docs.mulesoft.com/anypoint-code-builder/start-open-output-panel#output-panel). - To view problems, open the **Problems** tab by pressing Cmd+Shift+m (Mac) or Ctrl+Shift+m (Windows). Check the **Problems** tab proactively rather than waiting for a run or deployment to fail. Anypoint Code Builder surfaces validation errors, missing dependencies, and configuration issues at design time, so resolving warnings as they appear catches issues earlier than discovering them at runtime. ## Check Console Logs for Extension Issues If you encounter an issue with an Anypoint Code Builder extension, capture the console logs from the developer tools and share them with the MuleSoft support team. 1. Open the Developer Tools: - Select **Help** > **Toggle Developer Tools**. - Alternatively, open the Command Palette and provide this command: ```command Developer: Toggle Developer Tools ``` 2. In the Developer Tools window, click the **Console** tab. 3. Reproduce the issue to capture the relevant log entries in the console. 4. After the issue occurs, save or copy the logs: - Right-click anywhere inside the console output and select **Save as…​** to save the logs directly to a file. - Alternatively, click inside the console, press Ctrl+A (Cmd+A on Mac) to select all, then press Ctrl+C (Cmd+C on Mac) to copy the logs and paste them into a text file. 5. Save the logs as a `.txt` file, for example, `ACB_ConsoleLogs.txt`. 6. Attach the log file to your MuleSoft Support case. ## 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 - Select **View** > **Command Palette**. 2. Provide this command: ```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, Anypoint Code Builder 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. ## Performance Troubleshooting If Anypoint Code Builder is slow to start, load the canvas, or respond, rule out environment and configuration causes before you contact the MuleSoft support team. Work through these checks in order, and restart VS Code after you make changes. 1. Check your hardware and storage against the requirements. Confirm that your machine meets the minimum CPU, RAM, storage type, free disk space, and network requirements, and that the disk that hosts your user profile, Maven repository, and projects meets the storage performance minimums. See [Hardware and Storage Requirements](https://docs.mulesoft.com/anypoint-code-builder/ref-hardware-storage-requirements). On Windows, don’t run projects from network-mapped drives. See [Windows Performance](https://docs.mulesoft.com/anypoint-code-builder/ref-hardware-storage-requirements#windows-performance). 2. Apply antivirus and endpoint protection exclusions. Real-time scanning can reduce disk performance below the storage requirements. Exclude the processes and directories that Anypoint Code Builder uses, and confirm with your security team that exclusions are allowed. See [Antivirus Exclusion Paths](https://docs.mulesoft.com/anypoint-code-builder/urls-to-allow#antivirus-exclusions). 3. Check your power settings. Power saving modes can throttle CPU and disk performance. See [Power Settings](https://docs.mulesoft.com/anypoint-code-builder/ref-hardware-storage-requirements#power-settings) for Windows and macOS. 4. Close other resource-intensive applications. Applications such as Anypoint Studio compete with Anypoint Code Builder for CPU, memory, and disk resources. Close applications that you aren’t using. 5. Use one VS Code window. Each VS Code window uses its own resources. Instead of opening a separate window for each project, open related projects in a single multi-root workspace. See [Working with Workspaces](https://docs.mulesoft.com/anypoint-code-builder/start-workspaces). 6. Update to the latest version of Anypoint Extension Pack. Updates include performance improvements, such as file read and write optimizations on Windows. See [Update Anypoint Extension Pack](https://docs.mulesoft.com/anypoint-code-builder/start-acb#update-pack). To receive updates automatically, set each Anypoint extension to **Auto Update All (From Publisher)**. 7. Disable extensions that you don’t need. Other extensions, especially Java-based extensions, can compete with Anypoint Code Builder for JVM resources. In the **Extensions** panel, review your installed extensions, and disable or uninstall the ones you don’t use. Don’t disable the extensions in Anypoint Extension Pack: API, APIkit, DataWeave, Dependencies, Integration, MUnit, and Platform. If the issue persists after you complete these checks, export your troubleshooting information and provide it to the support team. See [Export Troubleshooting Information](#export-troubleshooting-info). ## Check for Anypoint Extension Pack Installation To determine whether Anypoint Code Builder extensions are installed, check for the **Anypoint Extension Pack** in the **Extensions: Marketplace** panel: 1. In the Activity Bar, click the Extensions icon to open the **Extensions: Marketplace** panel. To find this icon, see [Discovering the UI](https://docs.mulesoft.com/anypoint-code-builder/start-discover-ui). 2. In the panel’s search field, type _Anypoint_ to locate **Anypoint Extension Pack** in the list of installed extensions. - If the extension pack is _not_ installed, follow the installation steps at [Set up Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-acb#set-up-desktop). - If the extension pack is installed but the MuleSoft icon is not present in the Activity Bar, see [MuleSoft Icon Missing from Activity Bar](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-missing-features#missing-mulesoft-icon) to display the icon. ## 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](https://docs.mulesoft.com/anypoint-code-builder/ref-acb-maven#authenticating-to-mulesoft-repositories) for instructions on configuring your credentials. ## 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\\\\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](https://docs.mulesoft.com/anypoint-code-builder/ref-mule-settings#setting-home-dir). 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`: ```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\\AnypointCodeBuilder` 4. Optionally, delete cached extension data from the VS Code extensions folder: - Mac: `~/.vscode/extensions/` - Windows: `C:\Users\\.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. > [!NOTE] This procedure removes downloaded Mule runtime versions and Java versions. You can > re-download them after reinstalling. ## See Also - [Known Issues](https://help.salesforce.com/s/issues)