Hi @omonymos - just to close this one out, this issue was fixed in Scaler 3.1.2. The latest version is Scaler 3.2. Cheers!