# Execution node properties

**Category:** Data flows

**Version:** 1.0

**Last updated:** April 2, 2026

**Author:** Any2Info

***

### Overview

The **Execution** group contains settings that control whether and how a node is executed within a flow. These properties allow you to enable or disable nodes, define execution conditions, and control whether the flow should continue after the node has run.

***

### Configuration Options

| Setting        | Required | Description                                                            |
| -------------- | -------- | ---------------------------------------------------------------------- |
| Enabled        | No       | Determines whether the node is active during execution.                |
| Precondition   | No       | Defines whether the node is allowed to execute based on incoming data. |
| Stop Condition | No       | Determines whether the flow continues after this node.                 |

***

#### Enabled

The **Enabled** property determines whether the node is active during execution.

* When enabled, the node will be executed as part of the flow.
* When disabled, the node will be skipped.

Additional behavior:

* All downstream nodes will also **not be executed**.
* Disabled nodes are shown as **grayed out** in the designer.

***

#### Precondition

The **Precondition** property defines whether the node is allowed to execute based on incoming data.

Available options:

* **None** (default) The node is always executed, regardless of input.
* **Has Rows**\
  The node is executed only if one or more input rows are present.\
  If no data is available, the node will be skipped.
* **Is Empty**\
  The node is executed only if there are no input rows.\
  If data is present, the node will be skipped.

**Note:**\
This is similar to using a *Not Empty* condition node.\
Using a precondition keeps the flow cleaner by avoiding extra nodes.

***

#### Stop Condition

The **Stop Condition** determines whether the flow continues after this node has been executed.

Available options:

* **Continue** (default) The flow continues to the next node.
* **Terminate**\
  The flow stops immediately after this node.\
  No further nodes will be executed.

Additional behavior:

* A **red indicator icon** is shown in the bottom-right corner of the node in the designer when *Terminate* is selected.

***

### Tips & Best Practices

* Use **Precondition** to prevent unnecessary execution when no data is available.
* Prefer **Precondition** over the separate condition node to keep flows clean.
* Use **Terminate** carefully, as it stops the entire flow.