Error Reference

Scheduled job not executing at configured time

Scheduled job not executing at configured time

Where this appears

This error appears in the System Log under System Diagnostics > Logs > System Log when monitoring scheduled job execution. It can also be observed in the Scheduled Jobs list where the Next Run time passes without execution occurring, or when reviewing job history shows missed executions.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "Scheduled job not executing at configured time" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

The scheduled job is set to inactive state, preventing it from being queued for execution by the scheduler. (high likelihood)

The 'Run as' user account is locked, disabled, or has expired, causing the job execution to fail authentication. (high likelihood)

Node scheduler is paused or the specific node where the job should run is not processing scheduled jobs due to configuration or load issues. (medium likelihood)

System maintenance window or cluster maintenance is preventing scheduled job execution during the configured time. (medium likelihood)

Conditional execution script in the job is returning false, preventing the job from running even though it's scheduled. (low likelihood)

Fix

Step 1: Navigate to System Definition > Scheduled Jobs and locate the problematic job, then verify the Active field is checked and the State is not set to 'Paused'.

Step 2: Check the 'Run as' user field and navigate to User Administration > Users to verify the specified user account is active, not locked, and has not expired.

Step 3: Review the job's Condition field to ensure any conditional logic is not preventing execution, or temporarily clear the condition to test if the job runs.

Step 4: Go to System Scheduler > Scheduled Job Status to check if the scheduler nodes are running and processing jobs, looking for any nodes in 'Down' or 'Paused' state.

Step 5: Check System Diagnostics > Logs > System Log for any error messages related to the specific job name or scheduler, filtering by 'source' contains 'schedule'.

Step 6: Verify system maintenance windows in System Policy > Maintenance Schedule to ensure the job isn't scheduled during blackout periods.

Step 7: Test the job manually by clicking 'Execute Now' on the scheduled job record to verify the script runs without errors when triggered manually.

Step 8: If the issue persists, restart the scheduler by navigating to System Scheduler > Schedule Page and clicking 'Restart Scheduler' or contact system administrator for node-level troubleshooting.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue