@remideprez Hello, this issue should be fixed in our upcoming release of version 47.1 planned this week.