The start-sleep cmdlet is involved in the script I need to use; while it's alright to trigger the execution when the task is created or modified in Task Scheduler, I am not sure how the 60 secs of sleep are interacting from within the script block along with the Task Scheduler. (I mean like, it could be the Scheduler has the task running by now, but is it the ps1 script performing sleep-start at the same time?)