Hi @YYang, @Bassem @wangyan16 @RD_Cryo,
Thank you all for your help with this. We’ve released a patch for v4.1.1 that fixes this issue. Please see: