I noticed that this issue was linked in the v30.00 release notes but the desciption doesn’t really match up. So there a possibility that this may be fixed in this update.
