Scheduled Job runs multiple times when set to run periodically, instead of running only once.

[Harsh Sodiwala]

I have created a scheduled script to run a discovery process every 1 hour.

However, I see that every hour, this script runs 10-15 times, at the exact same time.

Is this behavior known ? If so, how can I prevent this from happening ?

[TIA]

[Bhagya Lakshmi]

Do you want to run only one time per day?

[Harsh Sodiwala]

Actually this is a common behavior I observed across 2 apps. The per-hour was just an example.

If I set the period to 1 hour [periodically] or set one fiexd time of the day [Daily], this happens. It runs multiple times at exact same second.

[Santosh_Ksagar]

Hi Harsh,

If Run is Periodically, the duration between each script execution.

Note: This setting does not account for Daylight Savings Time changes. For example, if you select a period of one day, this adds 24 hours to the starting time of the job. If the start time was configured during a period with Daylight Savings Time, the job executes with a one hour offset on days when that time zone is not in Daylight Savings Time.

Please refer Docs here :- https://docs.servicenow.com/bundle/london-platform-administration/page/administer/reference-pages/ta...

Mark Correct/Helpful.

Thanks and Regards

Santosh Kshirsagar

www.dxsherpa.com

[kelseyn]

Late response, but I ran into this same problem and the issue turned out to be that every time the scheduled job was updated, a new sys_trigger record was being created.

EDIT: Not sure if this is the case for you, but the reason the old sys_trigger records weren't being deleted is because my table name was too long, and it was getting truncated in the Document field of the sys_trigger table. The system couldn't find the records to delete.