How to find whether the scheduled job is running slow and if so then how to fix it ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi All,
Could you please suggest me how to find out if a scheduled job / workflow is running slow ?
I have a few custom scheduled jobs which contains oob system property(instance_name) and custom script Includes and i am not sure how to check if these are responsible for the slowness. I have gone through a few docs still could not get clarity on few things like Age, hash etc. and what is the parameter ServiceNow uses to differentiate or find out the slow scheduled jobs ? If the properties and scheduled jobs are responsible how to find the cause of slowness and to fix it ?
Please let me know if you need more info .
Thank You
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi,
You can find the details in Active Transactions (All nodes) under System Diagnostics.
You should see which node iD it is running and Age (how long the job is running) and Type as Scheduler will highlight the scheduled job which is running.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Hi @SyeAb001 ,
Could you please let me know how to find out which is long running transactions ? Is it Age ? If yes then what should be Age time for a trasaction ? And also how to find out if any Schedule job is running slow ?
Thank You
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @1_DipikaD
If you see your scheduled job in System Diagnostics > Active Transactions with a high "Age" (e.g., 20,000,000 ms), it means that job has been running for that long right now and is likely stuck or performing a massive operation. This is your #1 indicator of a currently problematic job.
1. The Application Insights Dashboard (Preferred Method)
-
Navigate to Application Insights > Application Insights > Scheduled Jobs.
-
This dashboard is built for this exact purpose.
-
You can sort by "Average processing duration" to see the worst offenders over time.
-
You can also sort by "Run count" (a fast job that runs every minute can be worse than a slow job that runs once a day) and "Error count".
2. The Transaction Logs (For Completed Jobs)
-
Navigate to System Logs > Transactions (All Users).
-
Create a filter:
-
URL starts with
/sys_trigger.do(This filters for scheduled jobs). -
Created on
Today(or your desired time).
-
-
Sort the list by Response time (descending). This will show you the longest-running completed jobs in that timeframe.
Note: Please Mark this Helpful and Accepted Solution. If this Helps you to understand. This will help both the community and me..
- Keep Learning
Thanks & Regards
Deepak Sharma
-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
see this OOTB Application Insights feature available in Yokohama
Troubleshoot a scheduled job through Application Insights
you can check slow transactions here
also try to see here
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
