This page lists the quotas and limits that apply to Workflows.
Step limit
Workflows enforces the following step limits for each workflow:
| Limit | Description | Value |
|---|---|---|
| Assignments per step | The maximum number of assignments that may be performed in a single step | 10 |
| Conditions per switch | The maximum number of conditions that may be evaluated in a single switch block | 10 |
| Maximum call stack depth | The maximum number of levels of calling functions; for example, when a subworkflow calls itself or another subworkflow; or, standard library function calls that in turn call other functions | 20 |
| Minimum steps | The minimum number of steps within a workflow | 1 |
| Maximum steps | The maximum number of steps that may be performed in a single workflow execution | 10,000 |
Resource limit
Workflows enforces the following usage limits:
| Limit | Description | Value |
|---|---|---|
| Total workflows | The maximum number of workflows you can deploy per project | 10,000 |
| Source code size | The maximum size of the YAML or JSON file that defines your workflow | 128 kilobytes |
| Response size | The maximum size of an HTTP response (if saved to a variable, the memory limit for variables applies) | 2 megabytes |
| Memory limit for variables | The maximum amount of memory that you can use for all variables that you define in a single execution of a given workflow | 256 kilobytes |
| Arguments size | The maximum size of the arguments you can pass when creating a workflow execution | 256 kilobytes |
| Event size | The maximum size of the Eventarc payload you can pass when triggering a workflow execution | 256 kilobytes |
| Execution retention | The maximum retention period (after a workflow execution completes) of an execution's history and results | 90 days |
Request limit
Workflows enforces the following usage limits for each Google Cloud project:
| Limit | Description | Value |
|---|---|---|
| Concurrent executions | The maximum number of active workflow executions per region, per
project; concurrent executions are those that have started and not yet
completed or failed, including any that are waiting. Once the limit is
reached, new executions fail with an HTTP 429 Too many requests
status code. |
1,000 |
| Execution duration | The maximum duration (from start time to end time) for a workflow execution; any workflow that passes this limit ends with time-out error | 1 year |
| Workflow API requests | The maximum number of API requests (create,
update, list, get,
delete) per minute per location made on workflow resources
from all workflows in your project |
1,200 |
| Execution API get requests | The maximum number of get API requests per minute per
location made on execution resources from all workflows in your project |
6,000 |
| Execution API list requests | The maximum number of list API requests per minute per
location made on execution resources from all workflows in your project |
1,200 |
| Execution API write requests | The maximum number of create, update, or
delete API requests per minute per location made on
execution resources from all workflows in your project |
6,000 |
| HTTP requests to callback endpoints | The maximum number of `SendHttpCallback` API requests per minute per location made on execution resources from all workflows in your project | 1,500 |
Quota increase requests
If your project needs more of a particular resource than your quotas allow, you can request an increase to most quotas in the Google Cloud console. Find out more about quota increase requests.