The Automate application implements several limits to improve performance for execution and triggering effects. These limits and the expected behavior are listed in the table below.
| Description | Limit | Behavior when limit is reached |
|---|---|---|
| Cycle is detected, if cycle detection is not overridden | 1 cycle (or 50 cycles, if cycle detection is overridden) | Automation will be auto-disabled |
| Max size of input for object added/modified/removed condition with scheduled execution | 100K | Error message when saving the automation OR runtime error when evaluating the automation if the input set grows beyond 100K objects |
| Max number of recipients per automation | 10,000 | Error when saving or evaluating the automation |
| Max number of objects per automation evaluation for realtime execution | 10,000 | First 10,000 object events are processed, or error is thrown |
| Max number of objects per automation evaluation for scheduled automations when per-object execution is enabled | 1000 | Runtime error when evaluating the automation |
| Max size of object type for realtime execution | 10M | Error message when saving the automation OR runtime error when evaluating the automation if the total objects in the object type grows beyond the limit - see dropped objects configuration |
| Max size of object set for manual execution with function-backed effects | 100,000 | Error message when executing the automation |
| Max size of object set for manual execution with no function-backed effects | 5,000,000 | Error message when executing the automation |
| Max batch size of automation with function-backed actions | 20 | Runtime error |
| Max batch size of automation | 1,000 | Runtime error |