Understand the difference between Automation limits and usage in Jira Cloud

Summary

Learn the difference between Automation service limits and Automation usage.

Solution

Usage limit

• This is the total number of rule executions allowed for the product on your site.

• Each time an automation rule runs and successfully performs a valid action, such as creating, updating, or querying items, it counts towards your usage limit.

  • Usage limits are set based on your subscription tier (Free, Standard, Premium, and Enterprise).

  • Actions like conditions that do not result in further operations or setups (e.g., logging actions or creating variables) are not counted towards the limit.

  • For example, if you are on the standard plan of Jira Software, then you get 1700 executions/month. So every time a rule runs successfully, it keeps deducting from the 1700 executions.

• Once you hit the limit of executions for the product, the rules will stop running until the next month.

• For more details, see How is my usage calculated?

Service limit

• This is the limit on how much processing a rule can do during an execution without affecting your site's performance.

• Each component of a rule requires processing power, and there's a limit on how much processing you can use at once.

• Each rule execution has to abide by the Service limits, or else the rule will be "Throttled" during the execution.

  • For example, if your rule returns more than 1000 work items from a JQL search, the rule will be throttled. To fit within the service limits, you need to optimize your JQL to return fewer than 1000 work items and split the rule into two rules based on Created date/Project/Status, etc.

• For more details, see Automation service limits.