We could understand & investigate this issue now. We applied a fix that will be included in the next release.