Scheduled jobs
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
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What is the safest way to process a very large table on a schedule?
- A. One run over all rows
- B. Window each run by date or batch
- C. Increase the timeout
- D. Run it hourly
Show answer
B. Window each run by date or batch
Bounded batches keep each run predictable.
What makes a silent job failure visible?
- A. A dashboard widget
- B. Start and finish logging with counts plus alerting
- C. A knowledge article
- D. A UI policy
Show answer
B. Start and finish logging with counts plus alerting
You cannot alert on something the job never reports.