Identify Scheduled Jobs not scheduled to run

RW-43
Tera Contributor

‎04-03-2024 12:49 PM

We've noticed a couple of cases recently where new scheduled jobs have not been running automatically but run as expected when you execute them manually and came to discover that scheduled job need a record in the sys_trigger table in order to run on the defined schedule.

 

Two questions:

  1. Other than exporting from both the sysauto and sys_trigger how can we ensure that both records are being migrated? We hadn't noticed this issue until recently and have created numerous scheduled jobs prior to this.
  2. How can we ensure that no other jobs are missing from this table without going through the process of marking them inactive and then active again (this adds the record to the sys_trigger table).

Thanks,

R

0 Helpfuls
  • 689 Views
1 REPLY 1

luffy3478
Tera Guru

‎04-03-2024 02:45 PM

sys trigger record automatically gets created when scheduled job is set to run automatically. If the record is missing check with ServiceNow support. You need not create a sys trigger manually or import it from lower instance.

 

update period from daily to montly and revert back in the scheduled job and see of sys trigger record getting created

0 Helpfuls