Hello @Juan_Lopez … Did you manage to solve the problem or find it’s cause?
I have noticed a similar problem in our 3.3.0.8 installation: