Sorry about that!! Can't believe we didn't catch this in testing. I think some changes relatively close to publishing must have enabled this bug