> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/data-flows/execution-node-properties.md).

# 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.


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/data-flows/execution-node-properties.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.