Steps | Max size of step output | 5MB | Can use bigger output size by saving the step output to file using the step configuration |
Steps | The max number of steps that can run in a workflow. | 5000 | |
Steps | Default step timeout | 2 minute | |
Steps | The max number of HTTP steps that can run in one minute | 1200 | Only for Blink Cloud runners |
Workflow Executions | Maximum execution duration | The default time limit for each workflow execution is 2 hours, but you can adjust it up to a maximum of 12 hours. | Paused time doesn’t reduce the remaining execution time. |
The Wait Flow Control Action | The Max timeout duration for the Wait Flow Control Action. | 14 Days | The pending state of this action doesn’t reduce the remaining execution time. |
Interactive Actions | The Max timeout duration for all Interactive Actions | 14 Days | The pending state of this action doesn’t reduce the remaining execution time. |
Wait For Web Form Response Action | The Max timeout duration for Wait For Web Form Response Action | 14 Days | The pending state of this action doesn’t reduce the remaining execution time. |
Synchronous Subflows | The Max timeout duration for "Wait For Web Form Response Action" | Synchronous Subflows are constrained by the timeout of the parent automation. This means that the Subflow cannot run longer than the parent workflow's total timeout. | The pending state of this action doesn’t reduce the remaining execution time. |
Files | Max size of file created by a step | 500MB | |
Files | Max total size for sum of files in a workflow's steps | 1500MB | |
Files | Amount of files created in a workflow | 100 | |
Execution History | Number of entries in the workflow's execution history | 100 | If you would like to increase the amount of entries in your execution history, please contact support. |
Concurrent Workflow Executions | The number of workflow executions that can run concurrently. | In a Workspace, a maximum of 40 workflows can run concurrently and in a Tenant a maximum of 50 workflows can run concurrently. | Please note that if an async subflow is included in a workflow, it will be treated as a separate workflow and will count towards the concurrent workflow limit when executing workflows concurrently. |