hi,
we have further investigated and retested this here and applied an additional fix. The next version will address this.