Forums

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

*Daily processing time - per rule or per site/app

Tomislav Tobijas
Community Champion
May 15, 2025

Hi,

Quick question, if anyone can confirm regarding the following > Automation service limits.

 *Daily processing time  60 min per 12 hrs This could be the case, for example, if your rule talks to slow external systems.

Are we here talking about the limit per rule or per product/app/site?

It's not clearly stated in the docs and I believe it's per rule but Rovo says that it refers to the "total processing time for all rules combined" (which is a concern for one potential Atlassian client).

If it's per rule, I guess it's combined time within that 12-hour timeframe (e.g., if the rule would run for 10 mins each hour, the limit would be reached within 6 hours and it wouldn't execute anymore until 'next' 12-hour slot start).

Now, I don't have any more details about specific use cases and concerns from this particular party, but I couldn't find a clear answer + I see a couple of older questions related to this topic, so it would be great if we could clarify it for everyone.

Cheers,
Tobi

4 answers

1 accepted

4 votes
Answer accepted
Jose Gochi
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 15, 2025

Hi @Tomislav Tobijas 

I'm Jose, with the Jira Cloud support team.

The limit you mentioned refers to the total execution time of all the rules for your app combined.

Please keep in mind that the execution time for each rule is usually in the order of milliseconds.

Also, please consider adding your feedback about our articles and documentation in the link at the bottom of their corresponding pages. There our documentation team will be able to see it and act on it in the most efficient way.

Thanks!

2 votes
Tomislav Tobijas
Community Champion
May 15, 2025

Not an answer but an additional note/concern - if you have numerous integrations with third-party systems, and you use automation, 60 min of processing time could be relatively small and you could, probably, easily breach that.

⚠️ On the additional note, if you use Delay action(s), you could easily breach the limit. All in all, I see the point in having that (so execution processes don't crash the site or something like that), but duration could be relatively small for some implementations/use cases.

2 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 15, 2025

Hiu @Tomislav Tobijas 

I think it's per rule also and indeed the running time is a total for 60 min within a 12 hour timeframe.

But I think you should get clarity by reaching out to Atlassian.

0 votes
Tomislav Tobijas
Community Champion
July 2, 2025

So, we've just tested this (accidentally 😆) and this limit actually applies only to 1 rule.

For example, this rule exceeded the allowed execution limit and all other rules executed successfully.

Apparently, the limit only applies to one rule, not to all rules combined. 👈

2025-07-03_00-26-45.png

cc @Jose Gochi 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events