-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Context:
Due to the new userTask migration, we have recently observed that sometimes, userTasks imported into Optimize are missing their `flowNodeInstanceID` (formerly known as `activityInstanceId`), even after all importers have supposedly finished. To allow more visibility of how often this happens, we want to adjust the static dataset import tests to not only assert the count of userTasks (== count of flownodes with type userTask) but also that no usertasks are incomplete (ie lacking flownodeInstanceId).
AT:
- static dataset import tests also assert that no userTasks are missing their instanceId