i see. i preferred disable and enable to achieve this. the old behaviour was convenient for testing scripts that build up some data.
there is probably another issue in this context: since the update i occasionally get "comparison with nil values" in several of the resident scripts, where the nil variables have been read many times before by the same resident script (grp.getvalue...) causing odd behaviour because some of these variables have to be calculated in a different way on first call. these GAs are even conserved with a backup and restore. i have no idea, why they should get lost every 100 or 1000 calls. there was no reboot inbetween and the script has not been dis-/enabled. i have 2 LM machines, it seems the same on both (one has the latest, the other one RC1 2022 firmware).
ps: what happens after an error with a resident script, e.g. after a comparison with nil value ? does the script fully restart and lose the values of the variables ? in the versions before, it kept the variables.
there is probably another issue in this context: since the update i occasionally get "comparison with nil values" in several of the resident scripts, where the nil variables have been read many times before by the same resident script (grp.getvalue...) causing odd behaviour because some of these variables have to be calculated in a different way on first call. these GAs are even conserved with a backup and restore. i have no idea, why they should get lost every 100 or 1000 calls. there was no reboot inbetween and the script has not been dis-/enabled. i have 2 LM machines, it seems the same on both (one has the latest, the other one RC1 2022 firmware).
ps: what happens after an error with a resident script, e.g. after a comparison with nil value ? does the script fully restart and lose the values of the variables ? in the versions before, it kept the variables.