I can confirm that the issue is resolved with release 6.2.7

Thank you for the effort - we really appreciate it!