Your question about the several occurences of start levels.
I had a deeper look, why I came to that perception. Every time I save the rule with trigger “…start level 70 reached”, the rule is executed. So that was confusing during development until being understood. The “ok” item was a supposedly workaround.
No more necessary. After development, I took the 2min timer and am fine with that solution. Thanks for the hint about JS flavors and cache usage.
I´m still wondering about the recurring start level. Docs say “70=User interface is up and running”. Why does saving a rule with that trigger fire up level 70 again? Isn´t “up & running” achieved only once and enough?