Is my method bulletproof? Can I rely on the results of triggered backend wfs in order to take further actions based on the evaluation of only-when-conditions?

[hi_bubble]

Hello guys,

I have to evaluate 4 numbers against each other and determine if the overall direction is increasing, decreasing or fluctuating.

In order to do this I have 3 custom backend workflows in place that are being triggered based on the conditions.
The 1st and 2nd (increasing,decreasing) workflows are just triggered if their condition is met. The custom workflows have a return value “finished”:yes/no

The 3rd workflow (fluctuating) is being triggered if the 1st and 2nd workflow return “finished”:no (since this is the default for the boolean and should mean they have not run - hence the condition is not met).

This works so far. I am just not sure if this is bulletproof. What if the 1st workflow (numbers are increasing) has some more heavy stuff to do and therefore needs a few milliseconds more to have the return value “finished” set to true?

[akamarski]

Result of workflow values wait for the workflow to finish so even if it’s slow, the last step will wait for it. Except you must make sure they don’t return “no” or empty value by mistake

[mitchbaylis]

if it is just 4 numbers you could achieve it with a fairly simple string of conditions

if a < b and b < c and c < d etc

[hi_bubble]

Yes that is what do in the first picture. But I thought about outsourcing the math logic that happens if this case is true, to a different workflow in order to keep it less complex and easier to maintain.

[hi_bubble]

Thank you for bringing this up again into my attention focus. Yes indeed they will wait.

I think the default for booleans is always “no” since it’s empty which is answer every question with false. Therefore I was worried about my logic.

Thank you!