I think by exposing the magnitude of the change to RM v3.0, we might all get the idea of how much testing, then Beta testing it needs.
I've posted similar before but the Beta testers are traditionally going to find about half the remaining bugs. Release depends, I presume, on the rate at which bug reports dwindle to near zero. That's the point where the variances of the Beta Test group has been exhausted. In both meanings.
The inherent problem with testing Rule Machine is that there are an infinite set of possible rules/actions. Beta testing was preceded by extensive testing, but "extensive" is by no means exhaustive. Then beta testing shakes the tree and other bugs show up. Rinse, repeat...
Thus is all so reminiscent of CoRE's evolution. (As I recall history....) CoRE used asynchronous execution but it was hard for users to wrap their heads around all actions going at once when they were presented visually in a certain order. WebCoRE changed that to synchronous execution, then quickly made it user-selectable. I like the way the GOM (Grumpy Old Man - said lovingly as an original ST RM user) has implemented this.
I do love blowing it up trying to be fancy. That's the best kind of mess ups. It frustrates my wife when the house scream red Alert and strobe red in an every room but I forget to get it out of the loop and she just wants it to stop and go back to the nice automatic mood lighting.
I thought I would have a play with the 'while loop'.
I have defined a test rule that, in my mind anyway, should turn on a light, wait 1 minute, turn off light and repeat this sequence every 5 minutes.
When I hit the run rule button the light turns on and no other action happens. It just stays on. I've obviously misunderstood your instructions and any guidance would be much appreciated.