• Documentation
    • Search documentation
    karat

    +

    K

    API Reference ↗
    Use case developmentAutomateLimits

    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

    DescriptionLimitBehavior when limit is reached
    Max size of input for object added/modified/removed condition with scheduled execution100,000Error message when saving the automation OR runtime error when evaluating the automation if the input set grows beyond 100,000 objects
    Max number of recipients per automation10,000Error when saving or evaluating the automation
    Max number of objects per automation evaluation for real-time execution10,000First 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 enabled1,000Runtime error during evaluation before any effects are executed; no objects are processed
    Max size of object set for manual execution5,000,000Error message when executing the automation
    Max batch size of automation1,000Runtime error

    Automation runtime limits

    DescriptionLimitBehavior when limit is reached
    Max time an automation event can wait in queue45 minsThe event is terminated and none of the effects execute
    Max time an automation event can run4 hoursThe 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.