OK this is the most common case, in fact I JUST had to go in and manually change the state of a Private Boolean cause the greenhouse fan was NOT triggered ON at 80F and the temp climbed to 113F.
So thanks for SPELLING THIS OUT for me. That is the root of the problem 70% of the time, I go make a change, hit DONE...and cross my fingers that the cycle of events will sort themselves out.
Or I ponder what is active and what isn't...(ie. is that Boolean going to be changed after that WAIT [cancel-able or not] and just go in and make that overt change to the Private Boolean anyway...and then ask myself..."this rule was triggered, did I just shut it down".
....THEN later....I think to myself, could this get messed up in any other way while such that I need to put some "clean up" rule in place to mend things when I'm traveling. (along the lines of the Power Loss or Reboot Recovery Rules folks employ)
Truth be told I've even avoided editing a Rule I knew was subscribed (active) opting to not disturb it fearing messing something up (especially the case with night time Security related stuff).
Again, thanks for this discussion folks.
EDIT: At the risk of me not knowing where...and somebody saying "THAT'S IN THERE ALREADY DUDE" I have often wished I could go look at the instances (subscriptions) of a particular rule to see if I have multiple versions of it in play....and kill one or more.