The issue is open because we’re still working on a fix, the fix version only means we’re aiming to solve this for the 6.2.2 release.