I think another user actually found this bug yesterday, we’ll try and get a fix in for the next release!