Task_sla records on sn_vul_vulnerability records are attaching with Business Elapsed Time already elapsed by 60% - why?Issue When a vulnerability group is created, the attached task_sla record will begin immediately with 60% of Business Elapsed Time already accounted for. For some reason, it believes the vulnerability group record was created almost 60 days before (the SLA Definition in question has a 90-day duration). SLA repair does fix an individual record, but new groups being created continue to show the error.CauseThere is a custom Business Rule which targets task_sla records on the "sn_vul_vulnerability" table and is manipulating the start_time field value of the task_sla record upon insert.ResolutionAs mentioned above, there is a custom Business Rule that targets task_sla for "sn_vul_vulnerability" only, which modifies the start_time of the task_sla. Going by the logic in the Business Rule this occurs when the sn_vul_vulnerability record has a parent that also has a task_sla, as it gets the start_time of the parent's task_sla and sets the new record's task_sla start_time accordingly. Setting this custom Business Rule to active = false resolves the issue, as the start_time field value of the task_sla record is then no longer being manipulated via the custom Business Rule.