What are the limitations of automations?

An automation consists of steps that contain actions (for example, send a mail or disable a user account). These limits apply.

How often it runs

• An automation triggered “On Policy Violation” or “On Schedule” runs at most once a day for the same object, even when another scan runs for the same connector.
• “On Policy Violation” automations start after each scan batch that updates the policy, so they can start several times a day for different objects.
• An object that still violates the policy on a later day triggers the automation again, unless its earlier run is still waiting for approval or has not finished.
• Runs that end with the status “Error” or “Stopped” are retried after the next scan. Runs with the status “New” for more than 24 hours are also run again.
• Manually triggered automations can run several times a day.

How long it can run

• Each automation run can take up to 4 hours.

What stops it

• Threshold limit. Automations triggered “On Policy Violation” or “On Schedule” have a “Threshold limit”, as a percentage of the objects or as a number. New custom automations start at 20%, templates bring their own value, and an empty field means no limit. When the limit is reached, the automation stops processing new objects for that day. Objects started before the limit are still processed. Rencore Governance emails the recipients of the Thresholds in Automation notification.
• Daily API limit. The number of API calls an automation makes is limited per day.