> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/value-stream-modeller/troubleshooting/value-streams-debugger.md).

# Value Streams Debugger

## Introduction

The Value Streams Debugger helps authorized users monitor running process instances, identify failed steps, and replay or reply to selected steps without restarting the entire process. In the debug mode, you can:

* Open a process instance overview directly from the value stream view.
* See the executed path in the model and identify failed steps.
* Open step-level details to review input, output, completion event, and status.
* Open the connected Make scenario from the selected step.
* Replay a single step and continue processing from that point.
* Reply to a failed step to recover a stuck or failed process instance.

If your value stream uses subflows, debug each child flow separately to investigate the failures.

## Debug access and permissions

Debugger access is role-based:

* The debugger icon is visible in the Value Stream Modeller, for each specific value stream, only for users with the required admin role.
* You can create a dedicated user group and assign the required role to that group.
* Users without authorization cannot see the debugger icon and cannot access debugger data.

<figure><img src="/files/MDmdMpI9aJQZZ0opQXbj" alt="Debugger icon in the Value Stream Modeller"><figcaption><p>Debugger icon visible on a value stream for users with the required admin role</p></figcaption></figure>

## Process instance overview

When you click the debugger icon, the system opens a list of process instances for the value stream. You can filter the results by status or sort them by Instance ID or time.

<figure><img src="/files/kCE7WtAlYdKOyfQ5Awjs" alt="Debugger process instances list"><figcaption><p>Process instance list in the debugger with status filters and sorting options</p></figcaption></figure>

You can terminate running instances directly from this view. Select one or more instances and choose **Terminate**. The system opens a confirmation dialog before terminating the selected instances.

<figure><img src="/files/XKSos2buhiQYrizmnNsA" alt="Terminate instances in the debugger list"><figcaption><p>Terminate selected running instances from the debugger list and confirm the action in the dialog</p></figcaption></figure>

## Instance execution view

When you select an instance, the process opens in advanced mode. In the model view:

* The actually executed path is highlighted in green.
* If the instance is still running, or a step was not executed for any reason, it is highlighted in the relevant color. You can view the details in the steps.
* Failed steps are marked with a red status icon.
* Each step shows its execution status.

You can also terminate a running instance from this view. Choose **Terminate** in the toolbar. As in the instances list, the system opens a confirmation dialog before the instance is terminated.

<figure><img src="/files/dkvWiJRbrQx4zFqijjwS" alt="Terminate a running instance from the debugger details view"><figcaption><p>Terminate a running instance from the instance details view using the Terminate button in the toolbar</p></figcaption></figure>

### Step-level details

Click any step in the executed path to open a side panel with the process details. For iterator steps, the panel shows the status of the last available iteration.

<figure><img src="/files/RArwkgGWmFnrNfAuICho" alt="Debugger step detail panel"><figcaption><p>Step detail panel showing input, output, completion event, and execution status</p></figcaption></figure>

## Replay of individual steps

The debugger lets you replay a single step of a value stream instance. Use this when you want to test a Make scenario in a step directly from VSM, without running the entire process from the trigger. Replay is available for steps built with Make scenarios that are in a **running** or **finished** status. It cannot be used for triggers.

To replay a step:

1. Open a process instance in the debugger and select the step you want to re-run.
2. Open the step menu (three dots) on the step in the executed path.
3. Choose **Replay Step**.

<figure><img src="/files/AexwBk0CKWTxPD6QcngQ" alt="Replay Step option in the debugger step menu"><figcaption><p>The step menu with the Replay Step option, used to re-execute a single step in the value stream</p></figcaption></figure>

After replay is triggered:

* The process continues from that step onward.
* You do not need to restart the entire process instance.
* Step logs are updated with the latest results, and the run is visible in Make's scenario history.
* In the debugger logs for the step, the input data includes a `replayid` that identifies the replay run. The outcome of the replayed step becomes part of the process context.

{% hint style="warning" %}
Replaying a single step does not create a new running value stream instance.
{% endhint %}

Detailed technical error payloads are not exposed in the debugger at this stage; only the success or failure state is visible.

## View related Make scenarios

From a selected step, you can open the corresponding Make scenario. This option is available only when the single sign-on integration is working.

<figure><img src="/files/7ZvVHBPtOJXNP18fMIHY" alt="Check Scenario option linking to Make"><figcaption><p>Opening the connected Make scenario from a step in the debugger</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.emporix.io/value-stream-modeller/troubleshooting/value-streams-debugger.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.