Idea: It'd be helpful to be able to re-order logic within conditions on actions

[mishav]

Hey Scott, Emmanuel’s explanation clarifies

Today's update: Can we hear more about the the workflow engine improvements?

What the change means is that before, when you had an action with a condition (‘current user is logged in’), even if the condition was true (the user wasn’t logged in), the properties of the action were still evaluated, which was could use some time and capacity. From now on, the properties used to run the action will only be calculated if the condition evaluates to yes. For most workflows that won’t make a difference, but for long workflows with a lot of condition, things should be faster.

In other words, the condition itself is (probably) evaluated the same way as before the change.

You have a good point worth discussion, if the condition has several components with AND/OR operations.

The evaluation rule of left to right makes those general rules more specific.

Only AND operations: Stop evaluating on the first “no”
Only OR operations: Stop evaluating on the first “yes”
Final OR operation: Last component “yes” don’t need to evaluate the first components

You could build up a list of such optimisations.

It would be helpful to know if Bubble does or doesn’t apply these optimisations, so we can keep expensive components in a less-used portion. Or your suggestion is much better, having Bubble optimise it according to which is cheapest.