Expected Start field does not work on SLA definitionDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Retroactive Start field (planned start)does not work on SLA definition CauseNote that the sys_updated_on field value will be chosen by default as the start time if the Retroactive Start field is left empty and the SLA definition's start condition is satisfied. The code from the script includes "TaskSLA" ➔ Line number 416, which states the same.ResolutionAs per the retroactive start field mentioned in the SLA definition, make sure the field has a valid value when the start condition of the SLA definition meets so that same is considered as a start time for the task SLA.