Hi, We are also facing this same issue in 2.4.1 version. Is this issue fixed in latest version 2.5.0 ? Regards, Nishanth