There is a known bug with this, fixed in the next release. See the Known Issues report: Known Issues in Release 2.3.5.152