
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 10:10 AM
Hello Community!
How do you kill/cancel/stop a Performance Analytics Job instance?
Here's the situation: I'm either building or testing things that I've built in Performance Analytics, and when I go to run the Historical Job to pull the last year or two of data, I see that one or more errors pops up immediately. I look at the error, fix the error in under two minutes, but the current instance of that job continues to run, sometimes for hours, competing with any other jobs that are currently running, which may include another instance of the same newly-fixed job.
What is the solution to stopping a currently-running instance of a Performance Analytics job?
Thanks!
Solved! Go to Solution.
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 11:01 AM
Hello Michael,
Terminating the job would entail that you know which specific app-node the job is running on. Customer's do not have access to check specific nodes so the best thing would be to contact support. Jobs on ServiceNOW run on scheduled workers so you would first need to be on the right node that is running the job and then you would need to validate that the job is running on one of the workers from that node. From here we would be able to kill the transaction from the 'All Active Transactions' module under the User Administration application menu. If you happen to manually execute the job you would then be able to see the job running from the stats page. You would also be able to see the transaction from the 'All active transactions' module. This only works if you run the job manually as the job would then execute from the node that you are on. Hope this helps.
-Chris
Sr. Technical Support Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2017 02:56 PM
Hi there,
Please see Chris Lo and Adam Stout's responses below, those should resolve the issue for you
Thanks!
Tara
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 10:28 AM
You can try going to analytics -> Jobs
Open the job and click on "Cancel Job"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 11:01 AM
Hello Michael,
Terminating the job would entail that you know which specific app-node the job is running on. Customer's do not have access to check specific nodes so the best thing would be to contact support. Jobs on ServiceNOW run on scheduled workers so you would first need to be on the right node that is running the job and then you would need to validate that the job is running on one of the workers from that node. From here we would be able to kill the transaction from the 'All Active Transactions' module under the User Administration application menu. If you happen to manually execute the job you would then be able to see the job running from the stats page. You would also be able to see the transaction from the 'All active transactions' module. This only works if you run the job manually as the job would then execute from the node that you are on. Hope this helps.
-Chris
Sr. Technical Support Engineer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 01:10 PM
Beautiful! This makes perfect sense now that it has been explained. Thank you so much for your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 01:23 PM
Glad I was able to help! Let me know if you still have trouble terminating the job. Thanks.
-Chris