# Debugging

> To debug your agentic process, select the **Debug** option from the top-left toolbar. You can also use the **Debug step-by-step** option to debug your project one element at a time. Alternatively, if you right-click the start event, you get the **Test** and **Test step-by-step** options that deliver the same results.

To debug your agentic process, select the **Debug** option from the top-left toolbar. You can also use the **Debug step-by-step** option to debug your project one element at a time. Alternatively, if you right-click the start event, you get the **Test** and **Test step-by-step** options that deliver the same results.

![Test Configuration - Selection](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-test-configuration-selection-594402-90991b52.webp)

:::tip
Right-click on a start element in the process, and select **Simulate** to trigger the [simulation](https://docs.uipath.com/maestro/automation-suite/2.2510/user-guide/simulate).
:::

1. Open the **Debug configuration** panel.

   ![test configuration panel](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-test-configuration-panel-594572-445b7e3e.webp)

2. Select the **Debug** drop-down menu in the top toolbar and choose **Debug configuration**.
3. Assign Solution resources in the **Solution resources** tab, and map your process to the required resources:
   1. Under **Connections**, assign things like **Data Fabric Workspace**, **EmailConnection**, etc.
   2. Under **Processes**, connect to agents and RPA components (e.g., loan-validation-agent, ReadApplication bot). This ensures that when the test runs, each component is backed by a real resource.
4. Provide Project arguments switch to the **Project arguments** tab to input values needed by your process (like test email addresses, case IDs, etc.). Each argument corresponds to an input variable defined in your process. Example: LoanPortalEmail represents the test inbox used to simulate customer intake.

   ![test configuration popup](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-test-configuration-popup-594576-c3ed848e.webp)

After selecting a test option, the execution starts, and new panels are opened for you to test and debug the functionality of the process.
:::note
A **User task** step creates a task and waits for it to complete. To continue debugging, complete the task in Actions (formerly called Action Center).
:::

In debug mode, you can interact with the agentic process elements and examine their details.

   ![debugging](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-debugging-538492-3cf5e80d.webp)

:::note
In Debug mode, a process can run for maximum 30 minutes. This limit applies regardless whether the process fails or involves a long-running workflow.
:::

## Debugging properties

The **Output** tab shows the overall execution status.

The **Execution trail** tab shows you detailed information (**Details**) and variable values (**Variables**) for each step in the execution. Select the expand button to see additional variable details. You can edit variables when the debug instance is in a paused state.

The **Action history** tab shows you the comments logged from any manual interactions during the execution.

The **Global Variables** tab shows you the values of the variables for the entire process.

   ![execution trail](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-execution-trail-538499-2db952dc.webp)

## Breakpoints

You can set breakpoints on elementys tosee how they are executed. To set a breakpoint, hover over the upper left of an element and select **Click to add a breakpoint**. Currently, breakpoints can only be set once you start debugging a process. However, they will be retained between runs.

   ![breakpoint](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-breakpoint-538508-1b1eb59f.webp)

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-docs-image-587615-0f84a671.webp)

When a breakpoint is triggered in an agentic process, the process engine will pause execution, allowing you to examine the execution details. To add a breakpoint, right-click an element and select **Add Breakpoint** from the context menu.

Select the **Continue** button from the top ribbon to run the entire workflow (or next breakpoint), or choose **Next step** to advance to the next step in your automation. If you want to end the debugging process and return to your agentic process, select **Stop**.

   ![stop_continue_next step](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-stop-continue-next-step-538514-d9ab6cc4.webp)