Yup, thanks Bill! We’re still digging into the issue, but have not got around to deploying a fix, just yet…