You must follow specific limits on the use of CloudFlow. This topic describes the following types of limits that you must follow on the use of CloudFlow: naming-related limits and account-related limits.
Naming-related limits
You can name the flows and executions based on the following rules:
The name can contain letters, digits, underscores (_), and hyphens (-).
The name must start with a letter or an underscore (_).
The name is case-sensitive.
The name must be 1 to 128 characters in length.
Account-related limits
Table 1. Resource limits
Item | Default value | Description |
Maximum number of executions in progress* | 10,000 | The maximum number of executions in the Running state under the account. To increase the upper limit, submit a ticket. |
Maximum step execution rate* | Initial number of tokens: 100. Token recovery rate: 100 tokens per second. | The maximum number of concurrent steps per second under the account. To increase the upper limit, submit a ticket. |
Maximum number of flows that can be created | 10,000 | The number of flows that can be created under the account. |
Table 2. Limits on API call speeds
Operation name | Maximum number of supported tokens | Token recovery rate (tokens/s) | Description |
StartExecution* | 100 | 100 | To increase the upper limit, submit a ticket. |
DescribeExecution | 50 | 5 | N/A |
GetExecutionHisotry | 50 | 5 | N/A |
Other operations | 10 | 2 | N/A |
Table 3. Limits on flows, executions, and historical events
Item | Dimension | Default value | Description |
Maximum number of events per execution | Execution | 5,000 | To increase the upper limit, submit a ticket. |
Maximum event data size | Event | 32 KiB (Serverless workflow) 64 KiB (CloudFlow) | N/A |
Maximum request size | Request | 1,024 KiB | N/A |