Overview
This article explains how workflows are structured and how they execute.
If Designing Complex Workflows with the Canvas Editor explains what workflows are, this article explains how they are organized and how they run.
Workflows are composed of steps, where each step is a full flow.
The Workflow Editor defines how those steps relate to each other.
Flow Structure
Root Workflow
Every workflow has a root flow.
The root flow:
- Represents the workflow itself
- Defines the top-level execution structure
- Contains child steps
When a workflow is executed, execution begins at the root and proceeds according to the defined structure.
Steps (Child Flows)
A step is a child flow inside a workflow.
Each step:
- Is a complete flow instance
- Has its own configuration
- May include transformations
- May contain its own nested steps
Steps are not lightweight references. They are fully defined flows operating within the workflow structure.
Hierarchy and Nesting
Workflows support unlimited nesting.
A step can:
- Execute independently
- Contain nested child steps
- Be part of another workflow
This creates a hierarchical execution structure.
For example:
- Root Workflow
- Step A
- Step A1
- Step A2 Step
- B
- Step A
Each nested level follows the same execution model.
Execution Order
Execution order is determined by the workflow structure.
Key principles:
- A parent step executes before its child steps
- Child steps execute according to their defined configuration
- Nested steps execute within the context of their parent
Execution is controlled by workflow configuration, not by visual placement alone.
The Canvas view reflects the execution structure.
Workflow-Level Configuration
Some configuration applies at the workflow level rather than within individual steps.
Examples include:
- Conditional execution
- Loop configuration
- Parallel execution settings
- Failure handling (On Exception)
- Retries
These orchestration controls define how steps behave as part of the workflow.
Detailed configuration of each feature is covered in dedicated articles.
Separation of Responsibilities
It is important to understand the separation between:
Flow logic (inside steps)
- Connections
- Transformations
- Data movement
Workflow logic (outside steps)
- Execution structure
- Conditions
- Looping Retry
- Failure handling
Workflows orchestrate flows.
They do not replace flow logic.
Keeping this separation clear results in maintainable and scalable designs.
Summary
The Workflow Editor organizes full flows into a structured execution hierarchy.
Core concepts include:
- A root workflow Steps as full child flows
- Unlimited nesting
- Structured execution order
- Workflow-level orchestration settings
Understanding these concepts is essential before configuring conditions, loops, parallel execution, or retry logic.
Those topics are covered in the next articles in this section.