Hi @carlosbtlr, thanks for reporting this. We were aware of the issue and have now added it to our known issue list. It’s currently under investigation and will hopefully be fixed in the 3.1 update. Cheers.
1 Like