We are having the same/similar issue. We just recently upgraded to 3.2.0.2 and seemed to break our rule.