SLA update (already breached) job running for a long timeIssue 'SLA Update' related transactions are running for more than 10 days in the system. - Job - SLA update (already breached) Start date&time - 2019-06-08 06:59:16 Age - 10 Days 6 Hours 41 Minutes Steps to reproduce: Review Schedule Item - SLA update (already breached) State : Running has been running for over 10 days Observed the following in the Node Log: ---------------------- .. main,glide.scheduler.worker.4,4,SLA update (already breached) (889972707 ms) ..... om.glide.schedules.Schedule.fetchTimeMap(Schedule.java:588) com.glide.schedules.Schedule.getTimeMap(Schedule.java:579) sun.reflect.GeneratedMethodAccessor2926.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:498) org.mozilla.javascript.MemberBox.invoke(MemberBox.java:138) org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:292) org.mozilla.javascript.ScriptRuntime.doCall(ScriptRuntime.java:2585) org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52) org.mozilla.javascript.gen.sys_script_include_c14b7dd30a6a803f2f25e0e60a457f7b_script_163._c_anonymous_14(sys_script_include.c14b7dd30a6a803f2f25e0e60a457f7b.script:347) org.mozilla.javascript.gen.sys_script_include_c14b7dd30a6a803f2f25e0e60a457f7b_script_163.call(sys_script_include.c14b7dd30a6a803f2f25e0e60a457f7b.script)..... ---------------------------------------------- From the above, the job has been running for over 10 dayson line 347 of the Script Include : DurationCalculator ---------------------- line 347: var timeMap = schedule.getTimeMap(gStartDate, gEndDate, timezone); --------------------- Checked the System Timezone in System Configuration: /$system_properties_ui.do?sysparm_title=System%20Configuration&sysparm_category=System%20Configuration ------------------------ System timezone : US/Pacific - New (custom) Observed custom System Property : com.snc.sla.timezone.source Value : sla.timezone CauseCustomization of the System Time Zone by Custom System timezone : US/Pacific - New Custom System Property : com.snc.sla.timezone.source Value : sla.timezone ResolutionStop the current long running Job.However, to avoid the issue recurring, we suggest that reverting to base system TimeZone configuration and testing thoroughly on a sub production instance first.