Web Request Messes up Automation Execution Order

[Anthony]

Dear Community,

We have a problem with an automation, when there is a web request action included, it somehow messes up the execution order, even with checked "delay till response".

Please see attached screenshot, I created a simplified version of our automation for presentation (the original has multiple matches chained).

Without the web request action, the output is 1, 2, 3, 4. But wich web request it's 1, 2, 4, 3. So the number 3 waits correctly till the response is back. But number 4 doesn't wait. Why?

Do we have a workaround here? The thing is, we absolutely need to know the response before execution of 4. I tried to do a re-fetch before action 4 but it didn't help. I didn't set the re-fetch to 5 seconds though, because what if the response is delayed 6 seconds? So we need an more reliable way than to wait an unknown number of seconds.

Also we can't skip the "if matches" because depending on the setup, the response will already be known and saved to the issue beforehand and the web request won't be needed.

Thank you.

[David Friedrich]

Hi @Anthony ,

looking at the screen of your automation a simple work around jumps to mind. Maybe it won't work as you said that this is a simplified version of your real automation rule. But worth a try, so here goes nothing:
Have you tried to add the "Log 4" action in the If: matches thread behind "Log 3" and then create also an "Add else" thread with "Log 4"? This way "Log 4" should always happen after "Log 3".

[Marc - Devoteam]

HI @David Friedrich 

This is indeed simle and could work.

@Anthony give this a try.

[Bill Sheboy]

Hi @Anthony 

Please show images of a complete, running rule and the audit log details demonstrating the symptom you describe.  You may obscure any private company details, as needed.  Seeing the actual rule and log will provide better context for the community to help.

Until we see those images...

You appear to be using Jira Server or Data Center automation rules.  Is that correct?

If so, I recall an edge case scenario where a long series of if / else blocks could misalign the audit log entries for Server / Data Center when they occur is close time proximity.  Seeing your actual audit log may help compare to that scenario.

Kind regards,
Bill

[Bill Sheboy]

Hi @Anthony 

Just following up to check if this answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.

Thanks!