Thanks Hernanfor the hints and your investigation, both were helpful. We’ve added a test case for this issue, but the solution was a bit more involved (your fix was partial). Should be resolved now and it will go into 6.2, as well as 6.1.6