This topic describes the limits of CloudOps Orchestration Service (OOS) and the methods of increasing the limits.
Item | Limit for common users | Method of increasing the limit |
The maximum number of templates that a user can create | 200 | Apply for a limit increase in Quota Center. |
The maximum number of concurrent executions that can be performed by a user | 100 | |
The maximum number of tasks that a user can execute per day | 200,000 | |
The maximum size of a template file | 64 KB | The limit cannot be increased. |
The maximum number of actions that a user can execute per day | 50,000 | |
The maximum number of tasks that can be defined in a template | 100 | |
The maximum number of iterations for a loop task in a template | 1,000 | |
The maximum number of entries that can be retrieved when autopaging is enabled for an action | 1,000 | |
Supported regions |
| The limit cannot be increased. |
Supported regions are regions in which OOS can be deployed. By default, OOS deployed in a region can be used to manage resources only in the same region. For example, OOS deployed in the China (Hangzhou) region can be used to manage Elastic Compute Service (ECS) instances only in this region. However, OOS provides a method to manage resources deployed in other regions. If you want to call API operations in other regions, specify the region ID in the ACS::ExecuteAPI action. We recommend that you do not use this method.