You've reached your monthly rule execution limit

Question

Hi Atlassian Support,

I hope this message finds you well. Our company is currently facing a critical issue with our Jira instance related to automatic rules. Despite having a rule configured for only one project, we have received a warning about reaching our execution limit. This unexpected situation is causing significant disruptions to our team's workflow.

Upon researching the matter, we discovered that using an automatic rule for a single project should not count toward the execution limit, as indicated in this ticket. We have verified that our automatic rule is for just one project.

This is an unusual occurrence for us, especially considering that we had over 200 rule executions last October without any issues.

We urgently seek your assistance in resolving this matter and appreciate your prompt attention to help us restore normal operations for our team.

Thank you for your support.

Ollie Guan · Accepted Answer

Hi @Ky Nguyen ,

The post you gave is for 2022. The billing rules have changed slightly since November 2023.

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#How-is-my-automation-usage-calculated

Each automation rule is assigned to a product, and will count towards that product’s monthly limit. This is based on the following criteria:

* Rules scoped to a specific project will be billed to that project’s product.

* Rules scoped to a project type will be billed to that product

* E.g. if a rule is set to run for all Software projects, it will be assigned to Jira Software.

* Rules scoped to multiple projects will be assigned to the product that has the highest monthly limit

* E.g. Let’s say you’ve signed up to Premium plans for Jira Work Management, Jira Service Management, and Jira Software. And let’s say you create a rule that runs across all three

* Global rules will be billed to the product with the highest automation limit.

Bill Sheboy · Accepted Answer

Hi @Ky Nguyen -- Welcome to the Atlassian Community!

The packaging structure and execution limits for automation rules changed significantly on 1 November 2023.  One of those changes is project-scope rule execution is no longer unlimited.  Please look here to learn more: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

An additional change is only certain rule actions count against the limits; that is also described in the article.

Please read that entire article, review your automation rules, and consider your next steps.  Some customers can change their rule structure to include more conditions to help with the limits.  Others may need to upgrade their license level to continue to use automation.

If you have questions about improving a specific rule, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill