Troubleshooting | MuleSoft Documentation
# Troubleshooting
Cloud IDE 
Desktop IDE 
**Open Beta Release** : The **cloud IDE is in open beta**. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.
Troubleshoot errors and warnings you receive when using Anypoint Code Builder:
  * Missing or Disabled Features
  * Authentication Errors
  *   * Implementation Errors
  * Mule Runtime Issues and Errors
  * Project Loading Errors
For other issues and workarounds, see Known Issues in the Anypoint Code Builder Release Notes.


For tasks that support the troubleshooting process, see:
  * Check for Problems and Issues
  * Export Troubleshooting Information
  * Manage Your Cloud IDE Instance


## 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.
The **Output** panel provides build details and access to logs. The **Problems** tab lists warnings and error messages. Error messages and logs list underlying issues that can help you understand what went wrong and what requires attention.
  * To view project logs from the **Output** panel, see Compare Project UIs in the IDE.
  * To view problems, open the **Problems** tab by pressing Cmd+Shift+m (Mac) or Ctrl+Shift+m (Windows).


## 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.
**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.

  
---  
**Reboot** : Button for rebooting your cloud IDE instance.  
**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.
     * If the extension pack is _not_ installed, follow the installation steps at Set up the Desktop IDE.
     * If the extension pack is installed but the MuleSoft icon is not present in the Activity Bar, see MuleSoft Icon Missing from Activity Bar to display the icon.


## Folder Permission Error
Some high-level folders in the cloud IDE are protected and not available for your projects. Examples include `/home`, `/`, and `.config`. Attempts to create an integration, implementation, or design project in a protected folder produces the following error:
```
EACCES: permission denied, mkdir '/home/XXXX/.vscode'
```

To avoid this error, create and import your projects within your `/home/_your-user-name_/`folder or in a subdirectory that you create under this folder. The cloud IDE automatically provides the folder with your username.
Also avoid creating your projects under `/home/AnypointCodeBuilder`, which is intended for downloads of Mule and Java versions and for acb_settings.xml.
## 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 XML 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.