This topic describes the limits of Operation Orchestration Service (OOS) and the methods of extending the limits.
|Item||Limit for common users||Method of extending the limit|
|The maximum size of a template file||64 KB||The limit cannot be extended.|
|The maximum number of templates that a user can create||200||Submits a ticket or joins the DingTalk group (group ID 23330931).|
|The maximum number of concurrent executions for each account||100||Submits a ticket or joins the DingTalk group (group ID 23330931).|
|The maximum number of actions that a user can execute per day||50,000||Submits a ticket or joins the DingTalk group (group ID 23330931).|
|The maximum number of tasks that can be defined in a template||100||The limit cannot be extended.|
|The maximum number of iterations for a loop task in a template||1,000||The limit cannot be extended.|
|The maximum number of entries that can be retrieved when autopaging is enabled for an action||1,000||The limit cannot be extended.|
|Supported regions||China (Beijing)
|The limit cannot be extended.|
Supported regions indicates the regions where OOS can be deployed. By default, OOS deployed in a region can only be used to manage resources in the same region. For example, OOS deployed in China (Hangzhou) can only be used to manage 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. We do not recommend that you use this method.
You can join the OOS DingTalk group by searching group ID 23330931.