That's the worse case. I have no idea how that could happen.
It must be calling a specific function (the meeting script) while the weight variable is at the default level, but there's a IF/ELSE just before that function gets called after the third day of each 'week'/cycle that forces the variable to be on one of the three branching paths.
I'm out of time for today to work on it, but if I can't figure out how the function call is being made without the immediately preceding variable change taking place I guess I can add a binary flag that prevents it from showing that intro version of the meeting more than once. So far I'm only getting complaints about the 'balanced route', if it only happens there then I can have the binary exception trigger an immediate jump to being on the first Curvy meeting, but I'd really rather figure out how this is happening in the first place instead of spaghetti-coding a mystery fix into it.
Thanks again for helping me with the context around your reboots.