Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5, 10.6, 10.11
-
None
Description
Happens quite often:
Could probably be quickly fixed by a regex replace of the query result - doesn't really matter on which node of the loop the loop is reported - all these outcomes are correct.
It would be good to find out why this happens too.