Flow with simple condition 1 > 2 taking too long

[vllanso]

Hello everybody,

I know this is a recurring topic, but I think I found an explanation that could explain that a flow with a simple condition is taking too long to process, and hopefully someone knows how to solve it.

From what I understand, the problem of taking too long is not related with the condition itself or using variables instead of composes or parallel execution, but is related with the number of actions that it has to skip ... and I will try to explain.

Imagine a flow with a YES/NO condition (1 > 2) that:
- in the YES condition has 300 compose actions

- and in the NO condition you only have one compose action

The condition is as simple as 1 > 2, so in this case the flow will branch to the NO condition and execute a single compose.

This should take very very little, but as it has to skip the 300 compose actions in the YES condition, instead of taking a few milliseconds, it is taking 5 seconds.

And if the YES branch, instead of having 300 composes you have 500 composes, when executing the NO condition, it will take almost double.

So the question is why the number of non executed actions influences the process time of the executed actions ?

Or am I mis-interpreting the results ?

Of course this example is just that, an example, but demonstrates the problems that I have in real flows where very simple conditions are taking too long (in one of the cases is a web service that answers a request made by end users, and I am not able to have a response time below 15 seconds, that is too much for an end user).

I was trying to attaching some screenshots from the execution and from the flow definition, but I am not sure how to attach them 😞 

Any advice will be greatly appreciated.

Thanks, Victor

[vllanso]

Hello, 

finally I have found how to upload images, so here they are.

I have also found a way to reduce the time from 5 seconds to 0, and it was move the 300 composes in the YES condition to a child flow, and that way having the YES condition only with one action (the child flow).

I still can't understand why, if the NO condition has only one simple compose action, it takes 5 seconds because in the YES condition there are many (300 compose) skipped/not executed actions.

Comment____________________	Image_________________________________________________________________________________
Initial flow execution - 5 seconds for a simple condition (1>2) and a simple compose action
Initial flow definition: NO condition has just one simple compose action. YES condition has 300 simple compose actions (grouped in 10 scopes of 30 compose actions each, to make it ease to cut-and-paste)
Modified flow execution - 0 seconds for a simple condition (1 = 2 ) and a simple compose action
Modified flow definition Instead of the 300 composes in the YES condition, it was replaced by a child flow that would execute the 300 compose actions if true.

Regards, Victor.