Question 1

What causes Scheduled Job Not Running in ServiceNow?

Accepted Answer

Job is inactive or disabled — Navigate to System Definition > Scheduled Jobs and check the 'Active' field on your sysauto_script record. If unchecked, the job will never execute regardless of schedule. Timezone mismatch between instance and scheduled time — Check System Properties > System to see instance timezone, then compare to the 'Run' field time in your scheduled job. The job uses instance timezone, not your local time. Job already ran once and is set to run only once — Open the scheduled job record and check if 'Run' field is set to 'Once' and the 'Next action' field shows a past timestamp or is empty. Script execution failed with errors — Go to System Logs > System Log > All and filter by Source equals your job name. Look for error entries that occurred around the scheduled run time. Business rule or script logic failing silently — The script in your scheduled job contains logic errors or references invalid objects but doesn't throw exceptions. Check the script for undefined variables or improper GlideRecord queries. System scheduler node is down or overloaded — Navigate to System Diagnostics > Stats and check if the scheduler is running. Look at System Properties > Scheduler to verify it's enabled and not suspended.

Question 2

How do you fix Scheduled Job Not Running in ServiceNow?

Accepted Answer

How to fix it Navigate to System Definition > Scheduled Jobs and locate your scheduled job record. Verify the Active checkbox is checked. If not, check it and click Update. Check the Run field value. If it shows 'Once' and Next action is empty or in the past, change Run to your desired frequency (Periodically, Daily, etc.). Verify timezone alignment by navigating to System Properties > System and note the glide.sys.default.tz property value. Return to your scheduled job and ensure the time in the Run field corresponds to the instance timezone, not your local time. Check for execution errors by going to System Logs > System Log > All. Filter the log by setting Source equals the name of your scheduled job and look for error messages. Review your script code in the Script field for syntax errors, undefined variables, or improper GlideRecord operations that may fail silently. Add gs.info() statements at the beginning and end of your script to verify execution in the logs. Check if the system scheduler is running by navigating to System Diagnostics > Stats and looking for scheduler worker threads. If the scheduler appears down, go to System Properties > Scheduler and verify glide.schedule.enabled is set to 'true'.

Question 3

How do you prevent Scheduled Job Not Running in ServiceNow?

Accepted Answer

Always test scheduled jobs using the 'Execute Now' button before relying on automatic scheduling to catch script errors early. Document your instance timezone in scheduled job descriptions to avoid confusion when multiple administrators work across different time zones. Use gs.info() logging statements in scheduled scripts to track execution flow and make troubleshooting easier in the future. Set up notification emails on scheduled job failures by configuring the 'Conditional' field to send alerts when errors occur. Create a naming convention for scheduled jobs that includes the frequency and owner to make identification easier in logs and job lists.

Scheduled Job Not Running in ServiceNow

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge