I have a custom SharePoint job that I created. When I make updates to it, I restart the timer service programmatically to make sure that older, cached copy of DLLs are not used. However, this design came into question recently, and I have been unable to find any literature to suggest that restarting the timer service will cause disruptions to scheduled or runnings jobs.

If this does cause a problem, is there an alternate way to clear the cache after installing/re-installing my job that does not cause adverse reactions?


Recycling the timer service is not a big issue as it will cause the minor outage for a couple of seconds, During the Restart process, all the running jobs will go into paused state and jobs which are scheduled during that time frame will not run But will catch on next schedule once the Timer Service is back.

Another thing, there is Scheduled timer job in Sharepoint which automatically recycle the Timer Service every day 6 am( default scheduled). Read this blog to understand more about it.https://blogs.msdn.microsoft.com/besidethepoint/2012/01/10/the-timer-recycle-job-job-timer-recycle/

Note: dont kill the timer service from the Task manager always use the script

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.