We are working with various ZPM patch policies, for all of which we defined "auto approve". Once in a while such a patch policy throws an error message mail, telling that auto approval was prevented, but it would not tell the reason:

"The following policies were not published because of test failure

ZPM_POL_WIN7_x64_CRITICALS_TEST"

Obviously one or more of the associated test machines have not yet successfully installed this ZPM policy's sandbox version, but we have not yet found an easy way to determine, which machine is blocking the action.
It would be very helpful, if the notification mail would not only state the patch policy, that was prevented from auto approval, but also list the device(s), being responsible for the delay.

Comments