@Carlos-Gross Hi, we already found the issue and its cause. Colleagues will make a fix to the upcoming version 46.2. Thank you for your patience.