Sounds like it is related to this:
Button won't run with no selection: Button won't run with no selection
This probably fits very often, but you could have script commands select things again e.g, and then the button would still not run in full. This is because DO and some commands have there own abortion logic implemented it seems.
+1, removing some of this built-in magic is something which was also suggested in the mentioned thread, since all this can become irritating at times. Not completely sure if this should be done though. Things worked liked this for years, there's a risk existing buttons and command sets could fail or act very unexpected unless you introduce some kind @modifier to toggle behaviour to "expected"-mode - so to say. o)