Actual elapsed time not geting updated properly for breached task_sla records

somjyotisinha · ‎04-09-2014

Hi,

I have noticed that the actual elapsed time is not getting updated correctly for task_sla records that have been breached. For example, a particular task_sla record is displaying the actual elapsed time as 29 days when it should be 32 days. However, when the Run SLA Calculation button is clicked, the proper elapsed time is calculated and populated on the record. According the wiki, breached SLAs are supposed to be updated every day by a scheduled job. However, it seems that this is not happening. Can anybody help?

david_legrand · ‎04-09-2014

Hello,

Could you check the scheduled job named "SLA update (already breached)" on your instance?

1) It is there?

2) when will it run for the next time? field "Next action"

3) Is it still similar to https://demo019.service-now.com/nav_to.do?uri=sys_trigger.do?sys_id=361b8f25c0a80a4a00e6300ec39f79bf (for the range by example)

4) Do you have issues with the scheduled jobs globally or just this one?

Regards

View solution in original post

david_legrand · ‎08-05-2016

I just had a nice Friday Challenge and it's answer about it

Friday Challenge - 8 - SLA time!

Bhavana Ramesh1 · ‎01-22-2020

Hello,

I am also facing the same issue, did u happen to find the solution for this. Quick help would be appreciated.

Thanks and Regards,

Bhavna