Hi @Nreddy I think I figured it out.
one, I had slaves launched at startup, but that wasn’t the real culprit. it was the send command to launch worker after powerup command coming from powermanagement which completely ignores scheduling.
as written in my other thread :
I just want to make it know (for anyone else trying to figure stuff out) that I had an issue where
machines would render while not on schedule.
This was being caused with Powermanagement ignoring Worker Scheduling.
There's a checkbox here: `Menu > Tools > Configure Power Management > Group > Machine Startup` tab
that says `Send Remote Command To Start Worker After Waking Up Machines`.
This checkbox was throwing a wrench. It looks like that if a worker isn't running,
Power management deems the machine powered down, sends the wake-up/ start-up command,
followed by a command to start the Worker, completely by-passing Worker Scheduling.
In all fairness, the tooltip does say to turn it of if worker is started through other means, like scheduling