Scheduled Job times out in 10 mins , How to increase the time out for Scheduled Jobs ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2016 04:50 AM
We have defined a Scheduled Job which calls a set of Script includes which queries REST messages and fills the CMDB tables from the response json we get , It takes more than 20 mins depending on the size of the configuration we are querying through REST messages .
But , the scheduled jobs timeout in 10 mins leaving the tables half filled . Right now we have broken down the Scheduled job into multiple scheduled jobs to fill all the tables as a workaround , Is there a better way to make sure our scheduled job never time out untill the whole process is over ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2016 05:38 AM
Check to see if you have a transaction quote that is limited the scheduler.
Transaction Quotas - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2016 07:03 AM
Hi Chuck ,
Thanks for the quick reply . I see that the Transaction rules could be build only for the Global application .
In our case we have made a separate application , Is there a way we can create a Quota rule only specific to our application , So , that other existing applications on that service-now instance is not affected because of the new Transaction quota .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2016 07:04 AM
Hi,
Definately a good starting point to have a look at the transactions quotas. I've seen background jobs run for more than three hours, so this would at least narrow down the possible causes for your issue.
Search your log file browser with the following criteria and hopefully you will be able to find more information for the cause.
System Logs -> Utilities -> "Node Log File Browser"
- Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2016 11:46 AM
Hi guys ,
Sorry we could create a Transaction rule specific to an application scope .
I did create a Transaction quota rule with maximum duration as 1200 s , Still I get the error .
Cancelling transaction System Trigger2016-06-13 18:20:48 - system (maximum execution time exceeded): Thread glide.scheduler.worker.2 (system, glide.scheduler.worker.2), after 600365ms
And , the new Quota rule I defined I gave it an order less than the one which is responsible for terminating it in 600 s .
What could possibly be wrong here ?