if daily processing time of automation rules are breached then the automation rules which are pending for execution are run in next slot of 12 hours or not.
And this daily processing time is project specific or for all projects.
I have found this in from the documentary as specified below.
The following automation service limits have been applied to ensure the performance of instance.
Summary | Limit | How might this limit breach? |
Components per rule | 65 | A single rule contains more than 65 conditions, branches and actions. |
New sub-tasks per action | 100 | A rule executes the creation of over 100 sub-tasks. |
Issues searched | 1000 | A scheduled JQL search that isn't streamlined enough and returns more than 1000 issues. |
Concurrent scheduled rule executions | 1 | 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 | 5000 | Defines how many items a single rule execution can fetch. For example, a Scheduled trigger 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 | 50000 | 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 | 10 | 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. |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.