@jon10 Hi, we were aware of this issue and it should be already solved now.