Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

if Daily processing time for automation rule is breached

if Daily processing for automation rule is breached then is the pending rules will execute in next slot of 12hours or not.

Daily processing time is project specific or global.

Please refer below table for more clarity.

The following automation service limits have been applied to ensure the performance of  instance.



How might this limit breach?

Components per rule


A single rule contains more than 65 conditions, branches and actions.

New sub-tasks per action


A rule executes the creation of over 100 sub-tasks.

Issues searched


A scheduled JQL search that isn't streamlined enough and returns more than 1000 issues.

Concurrent scheduled rule executions


A scheduled rule that takes longer than 5 minutes to execute, scheduled every 5 mins. Only single concurrent executions of this rule is allowed.

Associated items for a rule


Defines how many items a single rule execution can fetch.

For example, a fetching 100 issues, followed by a related branch fetching 10 subtasks per issue, would add 100 * 10 = 1000 associated items to this limit.

Items queued globally


Similar to Items queued by rule, but applies to rules in progress across your Jira instance globally.

*Daily processing time

60 min per 12 hrs

A rule executes every 5 mins and each execution takes longer than 5 seconds. This could be the case, for example, if your rule talks to slow external systems.

Loop detection


This controls how many times a rule can trigger itself (or other rules) in quick succession before the execution is stopped and marked as a LOOP.

1 answer

0 votes


Based on reviewing the documentation, I believe that the processing limits apply to each rule individually. If it does breach the service limit, it'll queue it up to run when it next has bandwidth. If it queues too many of those rules, it will automatically disable the rule to prevent it from piling up. Does that help?



Suggest an answer

Log in or Sign up to answer
Community showcase
Asked in Jira Service Desk

Calling all Mindville Insight users, we need your help! (there might be swag involved)

Hello Insight users,  As part of our (Mindville's) acquisition by Atlassian, our training team is looking to build some new Insight training materials and we want to hear from you!  ...

276 views 4 6
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you