Administration · LessonBy Sneha I, ServiceNow Trainer, 8 yrs · Published · ServiceNow · all levels
Scheduled jobs
Schedule scripts, reports and imports without hurting instance performance.
Quick answer
Schedule scripts, reports and imports without hurting instance performance.
Key takeaways
- Every scheduled job consumes a background worker
- Stagger schedules instead of stacking on the hour
- Window large jobs by date so each run is bounded
- Log counts and alert on missed runs
What can be scheduled
Scheduled scripts, report distribution, data imports, flow triggers and cleanup jobs all sit in the same scheduler. Every one of them consumes a background worker while it runs.
Scheduling well
Spread jobs across the hour instead of stacking them on the hour. Long running jobs belong in the overnight window, and anything that touches a large table should be windowed by date so each run does a bounded amount of work.
Monitoring
Jobs fail quietly unless you make them noisy.
- Log a start and finish line with counts, so a silent failure is visible
- Alert when a job has not completed within its expected window
- Check the scheduler queue when jobs stop running, a stuck job blocks the worker
- Review the job list yearly, most instances carry jobs nobody remembers creating
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What is the safest way to process a very large table on a schedule?
Frequently asked questions
Why did my job not run overnight?
Either the node was busy, the job was queued behind a long running one, or the schedule is in a different timezone than you assumed.
Should heavy processing be a scheduled script or a flow?
Scheduled script for bulk data work, flow when process visibility matters more than raw throughput.