> 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/release-notes/archive/2024/2024-06-07-oe-replay-debugger.md).

# 2024-06-07: OE - Digital Process Step Replay

### Overview

The new Replay feature allows you to replay a single step of a instance in a debug mode. It's applicable to all the steps that are built using scenarios and are in running or finished statuses. This enhancement enables you to test specific scenarios independently without rerunning the entire process. Each replay updates the logs with the latest results and records the run in 's scenario history for improved traceability.

| Feature                            | Benefits                                                                                     |
| ---------------------------------- | -------------------------------------------------------------------------------------------- |
| **Rerunning single process steps** | This allows testing of separate scenarios without needing to run the entire digital process. |
| **Logs for replayed steps**        | Replayed runs are visible in the logs and in 's scenario history for better debugging.       |

### Known problems

No known problems at time of release.

### Documentation and links

* [Digital Process Debugger](/oe-user-guides/troubleshooting/value-streams-debugger.md)
* [Creating Digital Processes](/oe-user-guides/value-streams/working-with-value-streams/creating-value-streams.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/release-notes/archive/2024/2024-06-07-oe-replay-debugger.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.