N
Nandhini Soundarapandian
Whenever we create an yearly/monthly job thru Task Scheduler, we need to set the start date of the job, prior to the current year/month Trigger date irrespective of Implementation date of the new job.
For Eg.
Implementation date of the new job : Jan 17 2020 (the day i implemented this job in PROD server)
Job Trigger date : Day 1,2,3,4,5,6,7,8,9 of Jan every year
Job Start date : Jan 17 2020
Lets say if the new job is implemented on Jan 17 2020 (which is already past the Job Trigger date of the current year which is Jan 01-Jan 09 2020) , still we require to set the Start date as 1/1/2020 and not any date after that.Else the Next run time of the new job is not set properly. It randomly displays some time. Example in my case , I implemented my new job on Jan 17 2020, so I set the start date of new job to Jan 17 2020 thinking my next run time will be set Jan 01 2021.
Is this the bug in Task Scheduler or this is how Task Scheduler behaves ?
Continue reading...
For Eg.
Implementation date of the new job : Jan 17 2020 (the day i implemented this job in PROD server)
Job Trigger date : Day 1,2,3,4,5,6,7,8,9 of Jan every year
Job Start date : Jan 17 2020
Lets say if the new job is implemented on Jan 17 2020 (which is already past the Job Trigger date of the current year which is Jan 01-Jan 09 2020) , still we require to set the Start date as 1/1/2020 and not any date after that.Else the Next run time of the new job is not set properly. It randomly displays some time. Example in my case , I implemented my new job on Jan 17 2020, so I set the start date of new job to Jan 17 2020 thinking my next run time will be set Jan 01 2021.
Is this the bug in Task Scheduler or this is how Task Scheduler behaves ?
Continue reading...