Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation usage limit exceeded

Indy W
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 6, 2025

We are getting the error as "You've reached your monthly limit for one or more products. Automation usage will reset at the start of the next month" under Automation configured rules. All the automation rules are not getting triggered.
Please help us asap on how to fix it since it's affecting our productivity management.

1 answer

4 votes
Tudor Tofan
Contributor
November 6, 2025

Hi @Indy W ! Unfortunately, the only solution here is to upgrade to a higher plan. There is no way to buy extra automations.

However, if you're only a couple of days left until the month gets reset, you may ask Atlassian for some goodwill to reset the counter, and review the automations to avoid this the following months

 

Screenshot 2025-11-07 074841.png

 

 

Trudy Claspill
Community Champion
November 6, 2025

Hello @Indy W 

In addition, your administrators should review the automation rules to see if the can be modified to reduce the executions that will count against your usage. Note that simply being triggered doesn't mean the rule will count as usage. Review this information:

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

https://support.atlassian.com/cloud-automation/docs/view-your-automation-usage/

 

If you are on a paid plan from Jira your administrators can contact Atlassian support by opening a case at

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

If you are working on a free plan you are unfortunately not entitled to contact Atlassian support, except for billing, licensing, or purchasing issues.

Like Susan Waldrip likes this
Indy W
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 7, 2025

@Trudy Claspill @Tudor Tofan 

We check the usage and there is still quota for the usage. any reasons why we have the execution limitation error

Screenshot 2025-11-07 180013_Jira monthly usage.png

Indy W
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 7, 2025

@Trudy Claspill @Tudor Tofan 
Here is the error we have : rate limit exceeded

Screenshot 2025-11-07 180140_rate limit exceeded.png

Tudor Tofan
Contributor
November 7, 2025

Hi @Indy W !

Please take a look here: https://developer.atlassian.com/cloud/jira/platform/rate-limiting/

HTTP Code 429 means that you are making too many request calls in too short time, and Atlassian is limiting you.

 

However, coming back to the first error: Where do you see that error message "You've reached your monthly limit for one or more products. Automation usage will reset at the start of the next month", if Jira says you're only at 3% capacity? 

Like Susan Waldrip likes this
Indy W
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 7, 2025

@Trudy Claspill  @Tudor Tofan 

Or is there any query per second (QPS) limitation?

Indy W
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 7, 2025

@Tudor Tofan  @Trudy Claspill 

May I know how frequently the Jira would scan the gmail inbox folder ?
And

Refer to the document https://developer.atlassian.com/cloud/jira/platform/rate-limiting/

The rate limitation would be in place on 25 Nov, which is supposed to be not yet started

Indy W
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 7, 2025

@Tudor Tofan  @Trudy Claspill 
The business process is that we use the automation in the Jira to scan the gmail and automatically create the work item in the Jira.

However, we found that the other automation we created is working properly, which is also linked with gmail.

Tudor Tofan
Contributor
November 7, 2025

Hi @Indy W !

On Nov 22nd, Atlassian will introduce rate limits on API tokens. Your problem is not related to API tokens, but to actual calls to the REST APIs.

Also, your screenshot provides very little additional context. It may be that HTTP 429 comes from Google, when the automation is trying to reach the mail server.

I'm sorry, but we're going down the rabbit hole here. This issue is totally different than what you've opened this thread for.

Trudy Claspill
Community Champion
November 7, 2025

Hello @Indy W 

As @Tudor Tofan  stated the 429 error is entirely different from the you initially described. And based on the screen image you shared of the 429 error message, that doesn't even appear to be from any screen related to showing the results of automation rule execution in Jira.

I recommend that you start a new question by clicking the +Ask a question button at the top of the Forums screen and provide full details about your 429 error including screen images showing the complete automation rule, and a more complete screen image that shows the UI in which you are seeing that 429 error message.

Like Tudor Tofan likes this
Laura Campbell_Seibert
Atlassian Partner
November 7, 2025

@Indy W if you need to be able to create Jira work items from Gmail, you might have an easier to maintain set-up (and cheaper than upgrading to Premium) by using an app custom built for that. There are multiple apps on the Marketplace, but I'd suggest Jigo (I work with the people who make the app) as the team behind the app is actively adding new features.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events