Limits for Workflows
There are restrictions to the elements that comprise a workflow. These limits ensure a quality functioning workflow.
You can create a maximum of 1000 workflows; however, the size of each workflow can affect the performance of your system.
Activities, local variables, and expressions (used for conditions, bindings, and so on) all contribute to the size of a workflow. The type of activity also contributes; for example, a call method uses more memory to initialize than a simple write activity does. Each branch of an If/Else or parallel activity is considered an activity. For example, an If/Else activity with two branches is considered three activities before you add anything to either branch.
Keep the following guidelines in mind when you are building workflows.
- Keep the total activity count to fewer than 2000 (across all subprocesses)
- Keep the total number of variables, parameters, external events, and data items to fewer than 500 (across all subprocesses)
Note: Global subprocesses and user activities each count as single activities regardless of the number of child items they contain. These activities can be used to help reduce the size of your workflows.
Important: Data item limits include child activities.
| Limit | Restriction | Result |
|---|---|---|
| Data items and External events (including contained activities) | 100 | Validation error. |