"let" keyword causes scheduled job not to run?

shaunwassel
Tera Contributor

5 hours ago

Hi all,

 

I've come across some unusual behavior on my ServiceNow Certified System Admin dev instance - apparently when I use the JavaScript "let" keyword in a scheduled job script, it causes the script not to execute at all. I haven't checked yet whether this applies to other "modern JavaScript" syntax. In the attached screenshot, you can see the script and my settings - I do have ES12 enabled, and the script is quite simple:

(function() {
	gs.info("Hello world from a scheduled job! " + new GlideDateTime());

	let x = 5;

	gs.info("Done with scheduled job! " + new GlideDateTime());
})();

 When I click "execute now" for this, nothing at all is logged out to the System logs. When I comment out the "let" line, both messages are logged. When I change "let" to "var", both messages are logged. Why is this? The "let" keyword has worked for me on all other server-side scripts (i.e. Business Rules)

Preview file
95 KB
0 Helpfuls
  • 104 Views
1 REPLY 1

lauri457
Giga Sage

2 hours ago - last edited 2 hours ago

The es12 mode in global is not extremely robust at least when it comes to things that are processed by the scheduler. I've noticed similar behaviour in email scripts as well. Probably best to stick to es5 in server-side scripting if you can't for some reason build in a scoped app. 

 

The error can be found in the node log of the node that processed the sys_trigger for your scheduled script. From my pdi on zurich patch 2:

14:23:00.621Warningworker.0 

worker.0 txid=6d85408e8371 ScriptEvaluator *** WARNING *** Javascript compiler exception: let is an ECMAScript 6 feature - not supported (<refname>; line 4) in:
(function () {
gs.info("Hello world from a scheduled job! " + new GlideDateTime());

let x = 5;


gs.info("Done with scheduled job! " + new GlideDateTime());
})();
Stack trace: