@darrenm36 Hi, we are aware of that and our colleagues work on the fix. At the moment, it seems that the issue is already fixed.