Flow taking the wrong parallel path

[dht6000]

Hi, I hope someone can help me understand what's happening with a Flow I've been building. It's started doing something odd and I cannot put my finger on why. The problem is around an action to retrieve a value from a database which, if it succeeds should go on to complete the Flow, but if the value can't be read to use a parallel action to end the Flow.

It's worked fine for a while but suddenly started using the wrong track and I can't see why. The screenshot below hopefully shows the problem

Although the database action succeeds and I can see the value it reads in the Run History it's triggering the action that should be run on failure. The other path is set to run on Success for the database (below).

Any pointers will be very much appreciated!

Dave

[tom_riha · Accepted solution]

Hello @dht6000 ,

the 'run after' configuration on the 'Query database...' action looks fine, the action was skipped according to the run history. I'd check the 'run after' configuration for the 'Terminate...' action, that one seems to run even if the previous action was skipped, which it shouldn't.

[dht6000]

Thanks @tom_riha that's sorted it. I obviously didn't understand the parallel actions as well as I thought I did. The Terminate action was set to run if the previous action skipped as I thought it wouldn't be evaluated unless the Flow was in the parallel branch but I can see that's not the case.