null chops and their selective cook is quite useful for stopping downstream cooktimes for a small cost, however they can certainly add up, especially in replicated networks.
Anyhow, one thing I’d like to be able to do is enable/disable the selective cooking feature by setting it back to “Automatic” by an expression or export when I know that optimization is not needed, but expressions seem to work setting it TO selective, but once it’s in selective, I have to force cook the null chop to get it to see the latest value.
I assume this has to do with the null chop doing minimal work during this process, and maybe checking expressions is not one of them, but curious if this is by design or a bug.
Thanks!
cookType_reference_Bug.2.toe (4.1 KB)