@Zacharias-Schoen Hi, thank you for reporting this. I already forwarded the issue to colleagues, so they will fix this in the new version.