FAQ

What are the Limitations of Automations?

Automation consists of multiple steps that contain actions (e.g. Send a mail, disable a user account...). As such, there are some limitations to automation

What are the Limitations of Automations

Automation consists of multiple steps that contain actions (e.g. Send a mail, disable a user account…). As such, there are some limitations to automation

  • An Automation that is triggered by “on policy violation” or “on schedule” will never be triggered twice a day for the same object (even when another scan gets enforced for the same service).

  • There is no limit to the number of automation runs per day, unless a threshold has been set.

  • Each automation run is restricted to a maximum duration of 4 hours.

  • Automations triggered by “On Policy Violation” are limited to running on 20% of the total items in the triggered inventory by default (this limit can be disabled or altered).

    • If automations exceed this limit, they will not execute, and the author will receive an email notification.

  • Automation runs that end with the status “Error” or “Stopped” will be retried after the next scan.

    • Automation runs with the status “New” for over 24 hours will also be rerun during the next scan.

  • Manually triggered automations can be run multiple times per day.

  • The number of API calls made by an automation is limited to a specific number per day.