Hey @BarakIII, we’ve already determined the cause for this issue and have fixed it internally, so it should be addressed in the upcoming hotfix.