Hi everyone! Why is my automation being aborted (both this month and last month) with the message “Monthly rule executions have been exceeded,” when both the audit log and the usage statistics clearly show that no rules have been run this month (or even in the previous month)?
I’ve also read this article and verified that none of our rules have a “Global scope”:
https://support.atlassian.com/automation/kb/monthly-limit-for-rule-execution-has-been-reached-but-the-usage-is-below-the-limit/
Could you please help? Thanks!
Hi @Giuditta Badone
As I understand issue is with your rule. You reached maximum number of runs for this rule in this months. Please check your rule and optimize it.
If you want you can share details of your rule here and I can help you with this.
Regards,
Seba
You can find the automation usage limits for every plan in https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits
As you have tagged this question under free plan category, it would be 100 rules per month for your site.
Edit: Sorry, the screenshot just loaded and i can see that you have checked on the audit to show no run. Could you check whether this was for current month and the last month was exceeded that resulted in the failures?
Hi @Fazila Ashraf
these are the screenshots from this month and last month. I have two automations per month; as you can see, only one worked last month (the other was aborted with the same justification “Monthly rule executions have been exceeded”), and none have worked this month... but the 100-run-per-month limit certainly hasn't been reached.
Hi @Sebastian Krzewiński
As you can see from the screenshot, my automation rule attempted to run only once this month and was aborted for “Monthly rule executions have been exceeded”; nothing else has run since the beginning of the month.
Hello @Giuditta Badone
There is actually a known Atlassian bug around this. The Support KB explains that this false error can happen when a Jira product was previously removed from the site, because automation still checks for a license that is no longer valid. The KB mentions this for global rules, but the current public bug AUTO-1785 says the same behavior can also affect project-scoped rules, not only global ones.
Automation error - monthly limit for rule execution has been reached but the usage is below the limit | Automation | Atlassian Support
[AUTO-1785] When having a deactivated product, project-scoped & global-scoped rules fail with the usage limit error message. - Create and track feature requests for Atlassian products.
It looks like you're new here. Sign in or register to get started.
