You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In a Jira Automation rule, when a web request is sent from the main rule flow, it will indeed "Wait for response" as expected.
But, when a web request is sent from within an If-block flow, even if "Wait for response" is enabled, the main rule flow resumes execution immediately in parallel with the If-block flow, creating a race condition between the two flows (hence wreaking havoc on the desired logic).
AFAIK, If-blocks (unlike Branch components) are not supposed to fork flow control nor return flow control early, i.e., before the If-block completes execution.
Anyone else experience this and/or know what is going on? Is this a bug or a "feature"?
My scenario: Two web requests - the second depending on the success of the first. I check the success of the first response using an If-block, and make the second web request in the If-block. But the logic after the If-block races ahead and gets interleaved (randomly?) with the remaining logic within the If-block.