I first initialize a variable called event_post_message_retry_count to 0 . This is not in anyone of the screenshots.
Iteration #1 (pic 1) runs as expected, aside from the else if in line number #20 getting evaluated even though that's not how an else if is supposed to work
If the if evaluates to true, the else if should not even be evaluated.
Pic 2 is the timer config, which wasn't big enough to fit in the other screenshots. It's has an explicit duration of 5 seconds.
Iteration #2 (pic 3) is identical to iterations 3-24. Each iteration is about 5 seconds apart, the length of the timer. I don't know why the timer is running over and over again.
Iteration #25 (pic 4) shows that even though iterations 2-24 show only the timer line is ran, the set flow variable job is also running every time, even though it says it is not, because the variable number is 25, instead of the expected 1 .
Iteration #26 (pic 5) runs as expected.
This explanation of a problem is an issue for me because I have it configured to do the code, until retry count is >= 2, and if the count is incorrectly at 25 by the time the second try gets a chance to run, it's not going to work.
I am testing executions of this flow in bulk, which may be of significance, but it is a requirement for me to test it in bulk, because that is what it will experience in the prod environment.
Also why is it still doing the loop at all if retry count is >= 2
pic 1:
pic 2:
pic 3:
pic 4:
pic 5:
