How are the loop are detected in Jira Automation? false positive on loop detection

Question

Hello !

I made a set of automation based on a form, which trigger a cascading effect of multiple automation (up to 26)

Jira Automation detect this as a loop even if all rules are different and don't repeat.

Are any workaround exist ?

Can we not get the loop threshold change ?

Bill Sheboy · Answer

Hi @Fernand Ly

Adding to Jack's answer, it is difficult to know the cause of looping for your rules unless you describe the scenario fully (i.e., the problem you are trying to solve), show the complete rules' images / structure, and the rule details for options.

Until we know that information...

Reading the documentation on automation service limits, we find this information: 
https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

This states rules which trigger themselves, or through the "Allow Rule Trigger" option lead to triggering other rules, are counted as looping.

These cascading scenarios quickly become problematic when there are many issues in a chain of execution, or a rule error is leading to looping.  And...there is another possible risk of such rule designs: when there is an automation engine (or Jira Cloud) outage, there is no stated information from Atlassian that the rules will eventually trigger correctly...leading to significant manual cleanup of issues.  (My understanding is eventual triggering after an outage appears to depend on the rule designs and the events involved.)

When many cascading fields of information are needed, please consider alternative solutions, alternative rule designs, or marketplace addons for such field updates.

Kind regards,
Bill

Jack Brickey · Answer

Hi @Fernand Ly , could you explain a bit about your used case and what you are attempting to achieve? It is hard to come up with a workaround without really understanding this information.