Automation "aborted" status errors and incorrect/inaccurate usage log.

[Thomas Brennan]

Had a couple of automations not run this month, saying they had been aborted due to "exceeding automation limit". However, when I look at usage there has only been 2 of our automations used of our total 1700. Typically a month we may run about 50 so I've not seen an issue like this before. Nothing has been changed with the automations in months and they never have an Issue running correctly. 

When I looked at the usage chart it was displaying that the past couple of months have had very few automations, (5 & 11 for November and October). Underneath that if I select the the month I get the correct number of uses. 

Am I missing something obvious or might there be something wrong? has anything changed recently with Jira and/or automations that may affect this?

[Thomas Brennan · Accepted solution]

Thank you @Bill Sheboy and @Trudy Claspill I managed to get a response back form Atlassian support copied below:

"

Upon reviewing the current setup, I noticed that the automation rule "Notify *******" has been aborted with the reason: "Monthly rule executions have been exceeded." Similarly, the automation rule “ “ has been aborted for the same reason. However, the current automation usage is only at 1%.

This issue may arise when a site has a previously issued license that has expired or is no longer valid. For instance, if a site had both Jira and Jira Service Management (JSM) and JSM was subsequently removed, a rule with a global scope will still check for both licenses. If a valid license for JSM is not found, it can trigger an error. I observed that JSM was removed from the site on December 02, 2025, which might be contributing to this issue.

To address this, could you please adjust the scope of the automation rules "Notify *******" and “Automatic Serial linking of repair cases“ to multiple spaces instead of Global? Please select all relevant spaces and see if this resolves the issue.

For further details, you may refer to this Knowledge Base Article: " https://support.atlassian.com/automation/kb/monthly-limit-for-rule-execution-has-been-reached-but-the-usage-is-below-the-limit/ " "

This seems to be why it reported as "aborted", as it believed there wasn't any availability, as my department doesn't use JSM, I didn't even know it was removed. 

My automations are now slightly different to check across multiple Spaces rather than globally, so if any new spaces are made I'll have to add them to the automations if they are using the relevant fields. 

[Trudy Claspill]

Thank you for sharing @Thomas Brennan !

I have not heard of this problem before, but will definitely be adding it to my bookmarks for future reference.

[Bill Sheboy]

Thanks for that update, @Thomas Brennan -- This is good information!

I recall related and unexpected limit exceeded errors two times in the past: when JPD went live from free-to-paid product and when the packaging model for automation changed (i.e., the global-rule and limit changes).  But neither of those showed as ABORTED in the logs.  Quite curious...

Seems like an opportunity for Atlassian to improve / clarify the audit log entries for various root causes.

[Trudy Claspill]

Hello @Thomas Brennan 

If you drill into the details of that aborted rule execution, what else does it say? Can you share the details with us?

There are other reasons than the monthly rule usage limit breach for a rule to be aborted. There should be more details in the rule execution log entry to tell you which limit was exceeded.

[Bill Sheboy]

Hi @Thomas Brennan 

Two of the "normal" occurrences when I have observed the ABORTED status in the audit logs, when it was not from the monthly / service limits, are:

1. When one is in the rule editor, and either the rule is running or you have selected to run immediately after updating the rule, the current execution may abort.  I hypothesize this is a racetrack timing thing, where the automation engine's get / compile of the rule is colliding with the update...and / or there are multiple executions when run directly from the editor.
2. During an Atlassian outage impacting rule executions, when "weird stuff" happens

There is uncertainty around this ABORTED status.  There are monthly usage limits and separate service limits, only two of which are covered by the other status values.  Perhaps that is one of the reasons it is not listed under What do the different statuses mean?

As you appear to be the Product Admin of a paid Jira license, I recommend directly contacting Atlassian Support and asking them to investigate:

https://support.atlassian.com/contact/#/

When you hear back from them, please post what you learn to benefit the community.  Thank you!

Kind regards,
Bill