Has someone tried if this is resolved in 5.2.1 hotfix? Or found a cause/solution for the issue in 5.2?