> 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/oe/troubleshooting/faq/errors-handling.md).

# Value Streams Blocked by Scenario Errors

## Make scenario settings

Make's scenario settings provide different options for handling errors and scenarios data storage.

### Allow storing of incomplete processes

The storage of incomplete processes is not enabled by default. To enable it go to **Your scenario** -> **Scenario Settings**.

If the storage of incomplete processes is not enabled, the scenario stops and all instances of process contexts are blocked. With this setup, the overall outcome is that you have a queue of process context instances, which are blocked at a specific scenario step, until the scenario is manually reactivated.

If the storage is enabled, you can check the records of the incomplete processes at any time in the **Incomplete Processes** folder. You can use the record to reprocess the data. The incomplete processes need to be resolved to unblock the specific process context instance.

<figure><img src="/files/NT1QF0zwqP89bTfjKKWL" alt=""><figcaption></figcaption></figure>

### Set up a number of consecutive errors

The consecutive errors feature helps to separate sporadic issues from those that are fundamentally broken. Using advanced scenario settings, you can customize the number of failed processes before a scenario gets deactivated.

<figure><img src="/files/SVGNhz1lHORIYFXTvmzt" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To learn more about error handling in Make, see [Receiving Alerts for Scenario Errors](/oe/troubleshooting/faq/receiving-alerts.md) and Make's [Errors](https://www.make.com/en/help/errors) documentation.
{% endhint %}


---

# 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/oe/troubleshooting/faq/errors-handling.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.