# Isolated in execution: concept and application in variables

The concept of "**isolated in execution**" refers to the practice of ensuring that variables used in an integration flow are not shared or altered by other simultaneous executions. By enabling the "**isolated in execution**" option in a variable’s configuration, it becomes easier to predict and understand the flow’s behavior, avoiding conflicts and unwanted outcomes.

<figure><img src="/files/4TbwtI72wBipRpfHLkUv" alt=""><figcaption><p>Variable editing screen</p></figcaption></figure>

### **Practical Example**

Imagine a scenario with two distinct flows: one that simulates the arrival of items in a network and another that manages the updating of these items. In this example, a module responsible for saving an item needs to return a boolean value (true or false). This value influences the update of a variable called *index*, which is used to track the progress of the operation.

#### **1. Without "Isolated in execution" enabled:**

Suppose two instances of the flow are running simultaneously. Both share the same *index* variable.

When one execution alters the *index*, the other execution can also see this change. This can lead to issues such as unexpected changes and conflicts, resulting in inconsistent executions. For example, one execution might update the *index* 62 times while another updates it 57 times, leading to unpredictable behavior due to variable sharing.

#### **2. With "Isolated in execution" enabled:**

If the "**isolated in execution**" option is activated, each flow will have its own instance of the *index* variable, independent of others. In other words, one execution can modify the variable’s value without affecting another.

With "**isolated in execution**" enabled, the *index* variable’s value will be maintained separately for each execution. Thus, each execution operates within its own context, avoiding conflicts. For instance, if an execution starts with *index* set to zero, it will continue to manage that value in isolation, regardless of what happens in other executions.

In addiction, the initial value of the variable will always be as defined in the creation or editing modal. For example, if it was set to 0, every execution will start with this initial value.


---

# Agent Instructions: 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:

```
GET https://docs.skyone.cloud/english/skyone-studio/how-to/isolated-in-execution-concept-and-application-in-variables.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.