Metrics generated from "Catalog Task Assignment Group Duration" gives 0 as durationIssue Users can report an issue where if they are using the metric definition 'Catalog Task Assignment Group Duration' to capture the time spent on a ticket by a specific catalog task, the duration is coming as 0 even though there are time when the assignment group has been applied, based on the task activity.Symptoms - Open any one of the tasks(sc_task)- Check the duration of the work done by the agent on a particular ticket when it is with the Assigment Group.- Check the metric_instance records for the sc_task records to see that the duration for the Assignment Group value is 0 seconds when the task was actually with this assignment group for at least a few hours.ReleaseAny ReleaseCauseThis is due to the record in sc_task created with Active as false. We can confirm this from the audit history, we can see that the record was created with the active field as empty (which would be considered as false), and the active field was later set to true with update count 1.- Due to the Active field being set to false, the OOB metric definition name "Open" gets triggered. This metric definition has a script that is for completing the calculation on any other metric definitions on the sc_task table:So, when the Active state is found to be false for a record, all the open metric_instance records at the time are marked as completed, and the duration calculation is done. As the record was just created at the time, the duration for all metrics present at that time is set to 0 seconds.So, from a metric definition point of view, this is an expected behavior.ResolutionUse needs to ensure that the catalog tasks are getting created with "Active = true". If they are being created using a workflow or script, they need to implement the logic accordingly to ensure the above.