---
schema_version: "1"
id: 077dea4b64ea6aa1b4e7b1fd10b947f37987934b9f22e3236e9038a541c7750e
title: Debug Mule Applications with the Anypoint Studio Debugger
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/studio/visual-debugger-concept.md
canonical_url: https://docs.mulesoft.com/studio/visual-debugger-concept
source_site: docs.mulesoft.com
content_type: documentation
content_hash: a0f1a63cc62f91eaaa9b21918b63f5b5bb61f9d83e1f43ed9757650ac271d68e
description: MuleSoft Documentation Site
latest: true
---
---
product: Studio
---

# Debug Mule Applications with the Anypoint Studio Debugger

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

With Anypoint Studio debugger, you can run your application from Studio in debug mode and configure
breakpoints to stop application execution at a specific message processor. In the **Mule Debugger**
view, inspect the content of the message as it exists at that point in the flow and evaluate a
DataWeave expression against it.

The debugger works with Enterprise Edition runtimes and doesn’t connect to Mule Kernel runtimes.

When you run your application in debug mode for the first time, Anypoint Studio prompts you to load
the **Mule debug** perspective. The **Mule debug** perspective is a list of views that help you
debug your application:

- **Mule Debugger**

- **Evaluate DataWeave Expressions**

- **Mule Breakpoints**

## Debug Your Project in Studio

To debug your application in Studio:

1.  Right-click your project in **Package Explorer**.

2.  Select **Debug As** > **Mule Application**.

    Studio requests permission to switch to the **Mule debug** perspective.

3.  Click **Yes**.

Alternatively, run your application in debug mode by right-clicking in the canvas and selecting
**Debug Project**, or by clicking ![A bug icon](/mulesoft/current/en-us/studio/_images/to-run-debug-mode-e7b7b.png) (**Debug**) on
the toolbar.

## Configure Studio Debugger

Enable precise control over application debugging by setting the debugger connections and maximum
values. To modify the default configuration values, click **Run** > **Debug configurations** and
select the **Debug** tab.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Option</th><th>Description</th><th>Default Value</th></tr></thead><tbody><tr><td><div><div><p>Connection Properties</p></div></div></td><td><div><div><p>Configure the Studio debugger to listen for incoming TCP connections. Click <strong>Suspend</strong> to pause debugger listening activities.</p></div></div></td><td><div><div><ul><li><p>TCP connections: <code>localhost</code></p></li><li><p>Port: <code>6666</code></p></li></ul></div></div></td></tr><tr><td><div><div><p>Debugger Maximum Consumption Stream Properties</p></div></div></td><td><div><div><p>Control the maximum amount of data the debugger can consume from a stream when inspecting or debugging applications.</p></div></div></td><td><div><div><p>2 MB</p></div></div></td></tr><tr><td><div><div><p>Debugger Maximum Payload Collection Size</p></div></div></td><td><div><div><p>Determine the maximum size of the payload data that the debugger collects and displays during a debugging session. Manage the memory usage of the debugger to ensure it doesn’t consume excessive system resources to avoid performance degradation or crashes, especially when dealing with large data payloads.</p></div></div></td><td><div><div><p>100 bytes</p></div></div></td></tr></tbody></table>

## See Also

- [Mule Debugger View Reference](https://docs.mulesoft.com/studio/mule-debugger-view-reference)