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