Sequence of execution of automation rules

[Osama Al-Areky]

I have two rules and the problem is that the first gets executed immediately so it affects the execution of the second. Is there a way to delay execution of rules so that I can delay it until the first rule is executed?

[Bill Sheboy]

Hi @Osama Al-Areky 

Without seeing the design of the rules, were you intending the actions of one rule to trigger the other, is that an error, or do they happen to have the same trigger?

If you did not intend one rule to trigger the other, please check if you have incorrectly enabled the "Allow Rule Trigger" option for one of the rules.

If you want the actions of one rule to lead to more actions with the other rule, or they have the same trigger, please consider if you can merge the rules.  This may be valuable to you as there is an upcoming change to the packaging model for rules, leading to lower limits per month.  Please look here to learn more about that change:

https://community.atlassian.com/t5/Automation-articles/Introducing-our-new-packaging-model-for-Jira-Cloud-Automation/ba-p/2446099

Kind regards,
Bill

[Stanley Duback]

Are you able to provide more specific information in regards to what is happening?

If you are using two separate rules have you tried combining them into one? Things happen in order that you place them into the rule. Multiple rules can happen at the same time.

[Bill Sheboy]

Hi @Stanley Duback 

FYI components in rules do not necessarily happen in the order defined in the rule...for example:

Branches which could be on more than one thing are executed in parallel and asynchronously.  There is no guarantee of when such branches will complete, up to the last step of the rule.

And for the Send Web Request action, that will not pause execution unless that option is selected.

Kind regards,
Bill