Hi @Tedness, thanks for reporting this and apologies for the long gap in response. Based on our testing, this appears to have been resolved in more recent versions of Scaler 3.
If you’re running Scaler 3.2 and still see the issue, please let us know and we’ll be happy to take another look. Thanks again for flagging it.