Issue with scheduled data import not importing automatically.

manishsures
Giga Contributor

3 weeks ago

A Scheduled Data Import runs successfully when executed manually using Execute Now, but it does not trigger automatically based on the configured schedule. The import is active and scheduled correctly, but no Import Set Runs are created at the scheduled time. Looking for possible reasons or platform-level factors that could prevent a Scheduled Data Import from running automatically while manual execution works.

0 Helpfuls
  • 198 Views
2 REPLIES 2

Maham Tahir
Mega Guru

3 weeks ago

Hi @manishsures, 

 

Following can be the possible reasons your scheduled job failing to run:

 

  1. Scheduled jobs run under the authority of the user defined in the "Run as" field (or the user who created the job if blank). If that user is Inactive, Locked Out, or has lost the required Roles, the background job will fail silently.
  2. If there is a script in the Condition field of the Scheduled Import, the system evaluates this before running. If the script returns false, the import is skipped.
  3. ServiceNow uses the System Scheduler (sys_trigger table) to fire these events. Sometimes, the trigger record for a specific job can get "stuck" (State = Error), or the Next Action date is pushed far into the future due to a timezone glitch.

Check above 3 things and lemme know why your job was not working.

 

If you find my response helpful, mark it as helpful and accepted solution.

 

Regards, 

Maham Tahir.

0 Helpfuls

manishsures
Giga Contributor
In response to Maham Tahir

3 weeks ago

We have validated the Run-As user, schedule definition, XML, scripts, and conditions.
Execute Now works consistently.
The issue occurs only in PROD and only for auto-triggering.
This points to a scheduler trigger creation or execution issue on the PROD , which requires admin intervention.

0 Helpfuls