Workflow Basics
Workflows Runtime Limitations
Note: These limitations apply only at the workflow level and do not extend to the tenant or workspace level
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. |
Execution Queue
Execution queue limits are defined at two levels:- The workspace level, which controls concurrency of workflows in individual workspaces.
- The tenant level, which governs overall activity across all workspaces within the tenant.
| Feature | Description | Limit Value | Notes |
|---|---|---|---|
| Execution Queue (Workspace) | The maximum number of workflows that can run concurrently within a specific workspace. | 40 | Additional workflows beyond this limit are placed in a queue and will run as capacity becomes available. While this may introduce a brief delay, all queued executions will still be processed. Visit this section, for a more detailed explanation. |
| Execution Queue (Tenant) | The maximum number of workflows that can run concurrently across all workspaces under the tenant. | 50 | The limit is shared across all workspaces in the tenant. When multiple workflows are queued across different workspaces in the tenant, Blink cycles through the workspaces in turn, giving each one a fair opportunity to run its next batch of workflow. This helps ensure balanced resource usage across the entire tenant. Visit this section, for a more detailed explanation. |
Execution Queue Exceptions
Execution Queue Exceptions
Workflows that include any Interactive Actions, Web Forms, or the Wait action with a timeout greater than
60 seconds are not immediately added to the execution queue. Instead, they are placed in a pending state while waiting for input or a response from an external user. These pending workflows do not count toward the execution concurrency limit. Once a response is received, if the execution queue has available capacity, the workflow will proceed to execute immediately. If the queue is full at that moment, the workflow will enter the queue and wait its turn to execute.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 WorkflowStep-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
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.
2-hour timeout.-
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.
- If a workflow times out while a step is still running, that step will not be cancelled. It will continue to run to completion or failure, even after the overall workflow has timed out.
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 |