# Studio debugger, logging and error diagnosis

*MuleSoft Developer Study Guide · Debugging and Troubleshooting Mule Applications · Last updated October 28, 2026 · https://www.certifyforce.com/study-guide/mulesoft-developer/debugging-and-troubleshooting-mule-applications/studio-debugger-logging-and-error-diagnosis*

How to find the root cause of a failing Mule app: Studio breakpoints and debugger controls, remote debugging, log levels and categories in log4j2.xml, verbose and wire logging, stack traces, and reading the Mule error object.

- Certification: Salesforce MuleSoft Developer
- Exam section: Debugging and Troubleshooting Mule Applications
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-developer

**Official exam objective:**

> Identify root causes for errors when debugging Mule applications, and predict outcomes.

## What the exam expects

- Predict where the Studio debugger pauses (default, conditional and error breakpoints) and pick the Mule Debugger view tool that moves execution where you want it.
- Change a paused event's data and explain why the debugger never attaches to a Mule Kernel runtime.
- Start a standalone Mule server for remote debugging and state what that does to the other apps on it.
- Predict which Logger messages appear given the levels and categories in `log4j2.xml`, and find each log on disk and in Studio.
- Turn on verbose connector logging, HTTP wire logging and stack traces, and read the error object to name the root cause.

Key terms: **error breakpoint** (any processor that throws becomes a breakpoint); **Run to processor** (run on and stop at the selected processor); **category** (the Log4j 2 logger name a Logger writes through); **app log** versus **runtime log** (`<app-name>.log` versus `mule_ee.log`); **`error.errorMessage`** (the message a failing operation interpreted as an error).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Kernel runtime | The Studio debugger works with EE runtimes and does not connect to Mule Kernel | [Studio Debugger](https://docs.mulesoft.com/studio/visual-debugger-concept) |
| Error breakpoints | Enabled by default; no breakpoints for one specific error type | [Breakpoints](https://docs.mulesoft.com/studio/breakpoints-concepts) |
| Conditional breakpoint | DataWeave condition, pauses on `true`, editable while the app runs | [Breakpoints](https://docs.mulesoft.com/studio/breakpoints-concepts) |
| Run to processor | Stops at the selected processor even without a breakpoint | [Mule Debugger View Reference](https://docs.mulesoft.com/studio/mule-debugger-view-reference) |
| Remote debug scope | All apps on the server run in debug mode; clusters not supported | [Server Debug Mode](https://docs.mulesoft.com/studio/to-start-server-debug-mode) |
| Default level | INFO and above, asynchronous; DEBUG and TRACE discarded | [Configuring Logging](https://docs.mulesoft.com/mule-runtime/latest/logging-in-mule) |
| App log location | `MULE_HOME/logs/<app-name>.log`; Studio shows it in the Console | [Logger Component](https://docs.mulesoft.com/mule-runtime/latest/logger-component-reference) |
| Config not applied | `-M-Dlog4j.debug=true` prints which `log4j2.xml` is used | [Configuring Logging](https://docs.mulesoft.com/mule-runtime/latest/logging-in-mule) |
| Wire logging | `HttpMessageLogger` at `DEBUG` | [Troubleshooting HTTP Connector](https://docs.mulesoft.com/http-connector/latest/http-troubleshooting) |
| Stack traces | `mule.verbose.exceptions=true` shows filtered stack traces | [Configuring Mule Stack Traces](https://docs.mulesoft.com/mule-runtime/latest/configuring-mule-stacktraces) |
| HTTP status in a handler | `error.errorMessage.attributes.statusCode` | [Mule Errors](https://docs.mulesoft.com/mule-runtime/latest/mule-error-concept) |

## Check yourself

- Why might the debugger stop pausing at throwing processors after you click Mute Breakpoints?
- When does Mule hold application execution after starting in remote debug mode?
- When does an edit to `log4j2.xml` take effect without restarting Mule?
- Why would an audit trail use `Logger` and `Root` instead of `AsyncLogger` and `AsyncRoot`?

## Sources

- [Debug Mule Applications with the Anypoint Studio Debugger](https://docs.mulesoft.com/studio/visual-debugger-concept)
- [Pause and Inspect Your Flow with Breakpoints](https://docs.mulesoft.com/studio/breakpoints-concepts)
- [Mule Debugger View Reference](https://docs.mulesoft.com/studio/mule-debugger-view-reference)
- [Evaluate DataWeave Expressions While Debugging](https://docs.mulesoft.com/studio/evaluate-dw-expressions)
- [Start the Mule Server in Debug Mode](https://docs.mulesoft.com/studio/to-start-server-debug-mode)
- [Logging and Debugging](https://docs.mulesoft.com/mule-runtime/latest/logging-and-debugging)
- [Configuring Logging](https://docs.mulesoft.com/mule-runtime/latest/logging-in-mule)
- [Logger Component](https://docs.mulesoft.com/mule-runtime/latest/logger-component-reference)
- [Enable Verbose Logging](https://docs.mulesoft.com/mule-runtime/latest/enable-verbose-logging)
- [Configuring Mule Stack Traces](https://docs.mulesoft.com/mule-runtime/latest/configuring-mule-stacktraces)
- [Mule Errors](https://docs.mulesoft.com/mule-runtime/latest/mule-error-concept)
- [Troubleshooting HTTP Connector](https://docs.mulesoft.com/http-connector/latest/http-troubleshooting)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 15 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Developer pack (USD $19): https://www.certifyforce.com/practice-exams