Limits（限制）¶
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.
Automation scale limits¶
| Description | Limit | Behavior when limit is reached |
|---|---|---|
Maximum input size for Objects added or Objects removed conditions with scheduled execution |
100,000 | Error message when saving the automation OR runtime error when evaluating the automation if the input set grows beyond the limit |
Maximum input size for Run on all objects condition with scheduled execution |
1,000,000 | Error message when saving the automation OR runtime error when evaluating the automation if the input set grows beyond the limit |
| Max number of recipients per automation | 10,000 | Error when saving or evaluating the automation |
| Max number of objects per automation evaluation for real-time 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 | 10,000 | Runtime error during evaluation before any effects are executed; no objects are processed |
| Max size of object set for manual execution | 5,000,000 | Error message when executing the automation |
| Max batch size of automation | 1,000 | Runtime error |
Automation runtime limits¶
| Description | Limit | Behavior when limit is reached |
|---|---|---|
| Max time an automation event can wait in queue effect execution | Configurable | The event is terminated and none of the effects execute |
| Max time an automation event can wait in execution queue | 45 mins | The event is terminated and none of the effects execute |
| Max time an automation event can run | 4 hours | The event is terminated; effects that completed before the timeout are preserved, but remaining effects do not execute |
Automation events may wait in a queue for several reasons:
- Queue effect executions setting: When Queue effect executions is enabled, events execute sequentially and must wait for previous events to complete before starting.
- Internal parallelism limits: Even when the Queue effect executions setting is not toggled on, there is an internal limit on how many events can execute in parallel. When many events are triggered in quick succession, they enter the queue in trigger order and begin executing in trigger order, but may not complete in trigger order depending on each event's runtime.
中文翻译¶
限制¶
Automate 应用实施了若干限制，以提升执行和触发效果的性能。下表列出了这些限制及其预期行为。
自动化规模限制¶
| 描述 | 限制 | 达到限制时的行为 |
|---|---|---|
使用计划执行时，Objects added 或 Objects removed 条件的最大输入规模 |
100,000 | 保存自动化时显示错误消息，或在输入集超出限制时评估自动化时出现运行时错误 |
使用计划执行时，Run on all objects 条件的最大输入规模 |
1,000,000 | 保存自动化时显示错误消息，或在输入集超出限制时评估自动化时出现运行时错误 |
| 每个自动化的最大收件人数 | 10,000 | 保存或评估自动化时出错 |
| 实时执行时，每次自动化评估的最大对象数 | 10,000 | 处理前 10,000 个对象事件，或抛出错误 |
| 启用逐对象执行时，计划自动化每次评估的最大对象数 | 10,000 | 在效果执行前评估期间出现运行时错误；不处理任何对象 |
| 手动执行的对象集最大规模 | 5,000,000 | 执行自动化时显示错误消息 |
| 自动化的最大批处理规模 | 1,000 | 运行时错误 |
自动化运行时限制¶
| 描述 | 限制 | 达到限制时的行为 |
|---|---|---|
| 自动化事件在效果执行队列中等待的最长时间 | 可配置 | 事件被终止，且不执行任何效果 |
| 自动化事件在执行队列中等待的最长时间 | 45 分钟 | 事件被终止，且不执行任何效果 |
| 自动化事件运行的最长时间 | 4 小时 | 事件被终止；超时前完成的效果得以保留，但剩余效果不执行 |
自动化事件可能因以下原因在队列中等待：
- 效果执行队列设置： 当启用效果执行队列时，事件按顺序执行，必须等待前一个事件完成后才能开始。
- 内部并行限制： 即使未开启效果执行队列设置，系统内部仍对并行执行的事件数量有限制。当多个事件在短时间内被触发时，它们会按触发顺序进入队列并开始执行，但根据每个事件的运行时间，可能不会按触发顺序完成。