Workflows Runtime Limitations
Workflow Executions
| Feature | Description | Limit Value | Notes | |
|---|---|---|---|---|
| Workflow Execution Time | Maximum duration for a workflow to run. | 12 hours (default: 2 hours) | Visit the More In-Depth Explanation of Time Limitations section, for a more detailed explanation. | |
| Execution History | Maximum number of entries stored in a workflow’s execution history from the past 40 days. | 100 in the past 40 days | Contact support if you need to increase the number of history entries. |
Steps
| Limit Description | Limit Value | Notes |
|---|---|---|
| Maximum output size for a step’s output (result) | 20MB | For larger outputs, save the result to a file using the step configuration. |
| Maximum number of steps in a workflow | 5000 | |
| Default timeout for a step | 1 minute | Visit the More In-Depth Explanation of Time Limitations section, for a more detailed explanation. |
| Maximum number of HTTP Steps per minute | 1200 | Applies to Blink Cloud Runners only. |
More In-Depth Explanation of Timeout Limitations
Timeouts can be defined at two levels: Step and Workflow
Step-Level Timeout
Step-Level Timeout
Defines the maximum time a step can run before it must complete.
-
configuration: The step timeout is adjustable in the step settings, with a default of
60 seconds. -
What happens when time runs out?
If a step exceeds its allowed time, it will fail resulting in the entire workflow to fail, unless ‘continue on error’ is enabled.
Exceptions- Interactive Actions and the Wait Action
The Wait Action and Interactive Actions pause the workflow while awaiting user response, placing it in a pending state.
-
These steps can remain paused for up to
14 days. -
If the timeout is reached, the step is automatically completed, and the workflow continues without failure.
-
The time spent in a paused state does not count toward the total workflow execution time.
Example
A workflow has a
2-hourtimeout.-
It runs for
1 hour, then pauses at step with an Interactive Action. -
The step containing the Interactive Action remains paused for
3 hours. -
Once the user responds, the workflow resumes and completes execution.
-
The total execution time is recorded as
1 hour(excluding the3-hourpause), meaning the workflow does not time out.
-
Workflow-Level Timeout
Workflow-Level Timeout
Specifies the maximum duration a workflow can run before it is terminated.
-
configuration: Set in workflow settings under ‘Execution Timeout (in hours)’ field.
- The default timeout is
2 hours. - The maximum limit is
12 hours.
- The default timeout is
-
What happens when time runs out?
-
If a workflow exceeds its configured execution time, it will fail with a timeout status.
-
Any steps that have not yet started will remain in a ‘not started’ state.
-
Actions
| Feature | Limit Description | Limit Value | Notes |
|---|---|---|---|
| Global Variables | Maximum size of a Global Variable | 1MB | |
| Set Variable Flow Control Action | Maximum size for a value in the Set Variable action | 20MB | |
| Wait Flow Control Action | Maximum timeout duration for the Wait action | 14 Days | Paused time doesn’t count toward workflow duration. E.g., a 4-hour workflow with a 1-hour pause takes 3 hours to execute. |
| Interactive Actions | Maximum timeout for Interactive Actions | 14 Days |
|
| Wait For Web Form Response Action | Maximum timeout for Web Form Response action | 14 Days |
|
| Synchronous Subflows | Timeout for Synchronous Subflows | Limited by parent workflow timeout | A synchronous subflow must finish within the parent workflow’s timeout (e.g., 10 min for a 10-minute parent workflow). |
| Webhooks | Maximum number of executions per minute per workflow | 1800 | |
| Polling Interval | Minimum time between each poll | 1 min | Default is set to 5 min |
| Scheduled Triggers | Minimum time frequency for scheduled workflows | 1 min | Default is set to 5 min |
Files
| Limit Description | Limit Value | Notes |
|---|---|---|
| Maximum file size for a single step | 500MB | Does not apply if using your own Object Storage. |
| Maximum total file size across all steps in a workflow | 1500MB | Does not apply if using your own Object Storage. |
| Maximum number of files that can be created in one workflow execution | 100 |
Workflows Runtime Limitations
Workflow Executions
| Feature | Description | Limit Value | Notes | |
|---|---|---|---|---|
| Workflow Execution Time | Maximum duration for a workflow to run. | 12 hours (default: 2 hours) | Visit the More In-Depth Explanation of Time Limitations section, for a more detailed explanation. | |
| Execution History | Maximum number of entries stored in a workflow’s execution history from the past 40 days. | 100 in the past 40 days | Contact support if you need to increase the number of history entries. |
Steps
| Limit Description | Limit Value | Notes |
|---|---|---|
| Maximum output size for a step’s output (result) | 20MB | For larger outputs, save the result to a file using the step configuration. |
| Maximum number of steps in a workflow | 5000 | |
| Default timeout for a step | 1 minute | Visit the More In-Depth Explanation of Time Limitations section, for a more detailed explanation. |
| Maximum number of HTTP Steps per minute | 1200 | Applies to Blink Cloud Runners only. |
More In-Depth Explanation of Timeout Limitations
Timeouts can be defined at two levels: Step and Workflow
Step-Level Timeout
Step-Level Timeout
Defines the maximum time a step can run before it must complete.
-
configuration: The step timeout is adjustable in the step settings, with a default of
60 seconds. -
What happens when time runs out?
If a step exceeds its allowed time, it will fail resulting in the entire workflow to fail, unless ‘continue on error’ is enabled.
Exceptions- Interactive Actions and the Wait Action
The Wait Action and Interactive Actions pause the workflow while awaiting user response, placing it in a pending state.
-
These steps can remain paused for up to
14 days. -
If the timeout is reached, the step is automatically completed, and the workflow continues without failure.
-
The time spent in a paused state does not count toward the total workflow execution time.
Example
A workflow has a
2-hourtimeout.-
It runs for
1 hour, then pauses at step with an Interactive Action. -
The step containing the Interactive Action remains paused for
3 hours. -
Once the user responds, the workflow resumes and completes execution.
-
The total execution time is recorded as
1 hour(excluding the3-hourpause), meaning the workflow does not time out.
-
Workflow-Level Timeout
Workflow-Level Timeout
Specifies the maximum duration a workflow can run before it is terminated.
-
configuration: Set in workflow settings under ‘Execution Timeout (in hours)’ field.
- The default timeout is
2 hours. - The maximum limit is
12 hours.
- The default timeout is
-
What happens when time runs out?
-
If a workflow exceeds its configured execution time, it will fail with a timeout status.
-
Any steps that have not yet started will remain in a ‘not started’ state.
-
Actions
| Feature | Limit Description | Limit Value | Notes |
|---|---|---|---|
| Global Variables | Maximum size of a Global Variable | 1MB | |
| Set Variable Flow Control Action | Maximum size for a value in the Set Variable action | 20MB | |
| Wait Flow Control Action | Maximum timeout duration for the Wait action | 14 Days | Paused time doesn’t count toward workflow duration. E.g., a 4-hour workflow with a 1-hour pause takes 3 hours to execute. |
| Interactive Actions | Maximum timeout for Interactive Actions | 14 Days |
|
| Wait For Web Form Response Action | Maximum timeout for Web Form Response action | 14 Days |
|
| Synchronous Subflows | Timeout for Synchronous Subflows | Limited by parent workflow timeout | A synchronous subflow must finish within the parent workflow’s timeout (e.g., 10 min for a 10-minute parent workflow). |
| Webhooks | Maximum number of executions per minute per workflow | 1800 | |
| Polling Interval | Minimum time between each poll | 1 min | Default is set to 5 min |
| Scheduled Triggers | Minimum time frequency for scheduled workflows | 1 min | Default is set to 5 min |
Files
| Limit Description | Limit Value | Notes |
|---|---|---|
| Maximum file size for a single step | 500MB | Does not apply if using your own Object Storage. |
| Maximum total file size across all steps in a workflow | 1500MB | Does not apply if using your own Object Storage. |
| Maximum number of files that can be created in one workflow execution | 100 |