- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2022 08:10 AM

var gr = new GlideRecord('sc_request');
gr.query();
while(gr.next()) {
gr.u_opened_for=gr.requested_for.getDisplayValue();
gr.setLimit(5);
gr.query(); gr.print();
//gr.update();
}
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2022 08:18 AM
Your current instance node is looping the script. Until it is able to clear itself by timing out you will likely need to switch nodes.
Logout of your instance and clear your browser cache. Then do a fresh login and you should get a different node. If this doesn't work you can switch nodes via browser plugins like SN Utils.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2022 08:11 AM
Below are the steps to stop an already running scheduled job:
- In the Navigation browser, open System Diagnostics > Active Transactions (all Nodes). This will open all the running scheduled jobs.
- Select the job which you want to stop and select the "Kill" option, which will stop the job.
Setting the scheduled job to 'active = false' and deleting the scheduled job,will not stop it if it has already started.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2022 08:12 AM

But it is not loading any pages, as the option Cancel after 4 hours is checked, will this script be canceled after 4 hours of execution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2022 08:32 AM
Killing the transaction will work, but it is not immediate in the response. It sends the kill command but it will need to be processed

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2022 08:13 AM
This is happening because request table will have a lot of records, instead break it down by running your code in batches.
var gr = new GlideRecord('sc_request');
gr.setLimit(5);
gr.query();
while(gr.next()) {
gr.u_opened_for=gr.requested_for;
gr.update();
}
Aman Kumar