-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Context:
While investigating a different issue, I noticed that we perform an incorrect check of whether the current userTask has been updated in the userTask metrics script. The check is lacking the "not" and is incorrectly trying to access a field. The latter makes the condition always false, the missing "not" meant we never noticed this because it wasn't causing any updates to be skipped (instead, we always ran the metrics calculations even if the current task had not been updated).
AT:
- The above issue is resolved