Workflow Limits & Constraints

This page documents the system limits and constraints for workflows. Understanding these limits helps you design workflows that operate within platform boundaries.

Summary

Constraint	Limit	Description
Nodes per Workflow	50	Maximum number of nodes in a single workflow
Payload Size	30 MB	Maximum size for data passed between nodes
Child Workflow Depth	5 levels	Maximum nesting depth when using Workflow nodes
Loop Iterations	20 items	Maximum items when using Workflow node in loop mode
Function Timeout	5 seconds	Maximum execution time for Function nodes
Workflow Retries	3	Maximum retry attempts for a workflow
Node Retries	3	Maximum retry attempts for nodes with external integrations

Workflow Structure

Maximum Nodes per Workflow

A single workflow can contain up to 50 nodes.

If your workflow requires more nodes, consider:

Breaking it into smaller, reusable workflows using the Workflow Node
Consolidating logic using Function Nodes or Decision Nodes

Payload Size

Node Payload Limit

Each node enforces a 30 MB limit on both incoming and outgoing payloads.

When multiple nodes connect to a single node (e.g., Node A and Node B both connect to Node C), the outgoing data from all upstream nodes is merged into a single JSON payload. The size is measured by the total length of this combined JSON.

Child Workflows

When using the Workflow Node to call child workflows, the following limits apply:

Maximum Nesting Depth

Workflows can be nested up to 5 levels deep.

Depth increases by 1 for each nested workflow call. Exceeding this limit throws:

Maximum child workflow depth (5) exceeded

Example of nesting depth:

Parent Workflow (depth 1)
└── Child Workflow A (depth 2)
    └── Child Workflow B (depth 3)
        └── Child Workflow C (depth 4)
            └── Child Workflow D (depth 5) ✓
                └── Child Workflow E (depth 6) ✗ Rejected

Maximum Loop Iterations

When using the Workflow node in loop mode, the array can contain a maximum of 20 items.

Exceeding this limit rejects execution before spawning child workflows.

Planning for larger datasets: If you need to process more than 20 items, consider batching your data or restructuring your workflow logic.

Function Node

Execution Timeout

Each Function node has a maximum execution time of 5 seconds (5000ms).

If your function exceeds this limit, the execution will be terminated. For complex operations, consider:

Optimising your code logic
Breaking the operation into multiple Function nodes
Moving heavy computations outside of Workflow

Decision Overview