---
title: "Flow control"
slug: "flow-control"
description: "The user manual provides comprehensive guidance on using the Antavo Management UI for managing loyalty programs."
updated: 2025-03-26T15:10:11Z
published: 2025-03-26T15:10:11Z
canonical: "docs.antavo.com/flow-control"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.antavo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flow control

## Wait

The****Wait node serves as a flow controller within the Workflow editor, allowing for the **delay of workflow progression**. It’s commonly employed to ensure synchronization of data and communication with remote services is completed before advancing to the next node.

By double-clicking the Wait node, you can specify the**amount of time** and **the time period** (minutes, hours, and days). The minimum time value is 1 minute, and there is no maximum limit.

![](https://cdn.document360.io/08a474ca-8fb4-4c3c-9cd8-665242086cd3/Images/Documentation/wait_node.PNG)

You can monitor workflow executions currently paused by a Wait node under the [Running workflows tab](/v1/docs/workflow-logs#running-workflows).

### Wait output

| ![](https://cdn.document360.io/08a474ca-8fb4-4c3c-9cd8-665242086cd3/Images/Documentation/then.PNG) | The **then output** serves as the point where all subsequent workflow nodes should be connected. |
| --- | --- |

**What happens if you change or inactivate the workflow?**

- Inactivation: If you [inactivate](/engine/docs/workflow-configuration#activate-and-inactivate-a-workflow) the workflow, new runs will stop, but **workflows that are already waiting will continue**.
- Impact of changes: Workflows run based on a snapshot taken when they start. Any **changes you make will only apply to new runs**, not to workflows that are already waiting.

---

## Variable assign

The Variable assign node stores information as **transport data in the subsequent nodes** until the workflow is completed. Variables are useful when a value is only relevant during the execution of the current workflow eliminating the necessity to store it for a longer term in an entity attribute field.

- Set the **name** of the new variable This name is used to reference the variable in subsequent filters and actions.
- Define the **value** of the variable Use volt expressions for advanced-level calculations of variable values.

![](https://cdn.document360.io/08a474ca-8fb4-4c3c-9cd8-665242086cd3/Images/Documentation/variable_assign.PNG)

*These examples illustrate how the date of the purchase can be calculated and stored in a variable.*

### Variable assign output

| ![](https://cdn.document360.io/08a474ca-8fb4-4c3c-9cd8-665242086cd3/Images/Documentation/variable_assign_node.PNG) | The **success** output serves as the point where all subsequent workflow nodes should be connected. |
| --- | --- |