Thanks, indeed the issue unfortunately persists in certain cases, as recently reported here by @martam too. We are working to make available a more robust fix soon in the upcoming minor release.