we actually don't really consider the start time when we mark the cloud as validation=False. We would have to have a way of knowing that a future schedule is about to kick in (which means a process loop that constantly looks at the "about to kick in" schedules) and only toggle the cloud level Validation attribute to False at a designated time. I'm not sure if this is worthwhile. This is worthy of discussion.
Perhaps the code that toggles to false the notification=true and validation=true settings needs to move into the M&R functionality?