I've found the option "Disable query" to be kind of inconsistent in terms of labelling and mental model. I would expect an option labeled "Only run when" instead, similar to how Event Handlers are treated.
What do you all think? 
Hi @emozio!
I definitely agree it is not labeled in a very intuitive way 
It should say something more along the lines of "query will run while this statement is false, but will switch and be disabled when the below statement evaluates to true".
Or to flip the logic as you said as that would be more straightforward. But that might require a very large refactor of a lot of code 
I believe the engineers likely assumed that users always want a query to run, except when 'this specific exceptional case is MET and True' which is a very engineering way of presenting logic 
I can file a FR to better label/phrase "Disable query" 
You're completely right; that would indeed have a negative impact on existing values and DX. And your explanation does make sense.
Thanks for responding and clarifying this decision, it's much appreciated!
1 Like