Best Practices for Managing and Optimizing Scheduled Jobs in Large-Scale Instances

[mominumarfi]

Hi all,

I’m currently working in a ServiceNow environment with a growing number of Scheduled Jobs, and I’m looking for advice on how to manage and optimize them effectively to avoid performance issues.

Specifically, I’d like to understand:
• How to monitor the health and performance of Scheduled Jobs
• Ways to avoid overlapping or conflicting schedules
• Best practices for retry logic and error handling
• Any tools or features within ServiceNow that help with Scheduled Job optimization

If you’ve dealt with a similar challenge or have recommendations for maintaining performance in a large-scale setup, I’d really appreciate your insights.

Thanks in advance!

[Mark Manders]

There are a lot of OOB modules to check on what runs when (there even is a Scheduled Jobs Dashboard). Did you check that out to see what you are still missing in your requirements? 

What is a conflicting schedule? Does it matter some overlap? It doesn't make sense to have the same job run while it is already running.
If the number of jobs is growing, you should ask yourself why. What is the reason people are adding more and more jobs? Isn't is possible to do this in a different way or even combine some of them? 
What do these jobs do? Are they collecting data? Updating records? Sending out reports? Can't you introduce flows to do the same? Aren't dashboards better then sending out reports? 

Who are creating them? What is your process behind it? Is anyone checking on the what and why?