We have a client requirement that the Goal and Deadline of a task starts from a certain date called as Claim Notification Date (which can be a past date than the Case Creation Date). The Passed Deadline starts after the deadline has passed for certain tasks within the Claim case. The issue that we are noticing is lets assume the Claim Case got created on 22-Dec and frontend user back dates the Claim Notification Date to 2-Dec. The Goal and Deadline for the Reg E PC task that has Goal of 5 business day and Deadline of 6 business days from Claim Notification Date. The Passed Deadline of the Reg E PC Task is 9th Business Day, and if that is missed then urgency of that task should be moved from 0 to 90. From the Date numbers given below, we noticed that when Claim Case got created on 22-Dec with Claim Notification Date as 2-Dec, the Reg E PC task goal, deadline and passed deadline all are missed and the Reg E PC task urgency should have gone to 90. But when we looked at the case, the task urgency was still 0. When we investigated further, we noticed that while goal and deadline has been missed correctly, the system has still not breached the passed deadline and that is because Pega is calculating the Passed Deadline value from the execution of deadline SLA and then waiting for 3 days from there, rather than actual deadline date, which is incorrect. Is there another way that Passed Deadline need to be configured so that it calculates the SLA of Passed deadline from actual Deadline date and not from the execution of deadline SLA. This will be a problem in calculating any past passed deadline calculations otherwise.