Hi Roy,

I think you have to determine why the schedules have a state of missed.

Please have a look at the client's log files.

On the server's side there might be open sessions for those nodes
and therefore the schedule did not end and other one's are not
accepted.
If you have open sessions for such a node it might be a workaround
to cancel that session before the next schedule or to stop/restart the
client's scheduler service on the node instead of rebooting.

Regards
     Meckï