Flow Designer "IF / ELSE" flow logic issue

Erik Gunther2
Kilo Guru

I've been wrestling with an issue in Flow Designer for several days and will post several questions on this topic. For this post, I setup a scenario to better understand how Flow Designer is supposed to work. See screenshot below.

find_real_file.png

Refer to 3.3.1. If the If statement on 3.2 evaluates to False and 3.3 shows Completed, why does 3.3.1 show Not Run. To me, this appears to be a bug. Note, this ties into a larger issue I'm having, but I first wanted to understand this step. If you look at step 2, the Assign Subflow Outputs status is Completed. I wanted to show what I would expect to show in 3.3.1, that the step is Completed.

Here's the subflow being called from within a larger workflow. 

find_real_file.png

I attempted to use an IF statement (step 2) to evaluate the Subflow Output value to determine if it is True. My test case should have returned True. Notice on step 2 that the IF statement evaluated to False, which is wrong. Also, I'm confused by the RUNTIME VALUE. It shows {0:B}=true. What does this mean? If anything, I would have expected it to return {0:B}=false. But I don't understand yet how to interpret the runtime values.

9 REPLIES 9

jobaldock
Mega Contributor

I'm also having this issue. I'm attempting to evaluate and filter based on three different conditions. However, when I add in a third If or Else If, one of my conditions ends up not getting evaluated altogether, coming up with the Not Run notification. I think this may be a system error or a bug with Flow Designer.

You're probably right. I confirmed that Flow Designer has a lot of issues in London. I just upgraded my personal developer instance to Madrid and will continue testing and report back.

Katlego
Tera Contributor

Hi everyone i am on Orlando Version and also experiencing this issue. has a resolution been found ?

wadeaux
Tera Contributor

Old thread but if anyone is still looking for a workaround. I am running Paris and still having this issue, Else does not run the steps underneath.

I ended up using else if (rejected or cancelled), that seems to run fine.