Androids: Password compliance check returning incompliance, although complex password set, requirements met-> returning the wrong result?

Hi, we have set an Android compliance policy with following settings as being part:

The strange thing is that in monitoring a lot of devices still appear as incompliant with minimum pw length and type, although most of those affected users really indeed meet the password requirements set and have a 6 digit alphanumeric pw set.

Even a resync of the device policies from console or user site does not help and still is showing incompliance.

I tried to find a pattern on Android manufacturer types or Android versions. Most of the affected users /devices are Samsung Galaxy devices with Samsung Knox or some kind of Xiaomi or Vivo devices. All with Android versions 11 or lower.

But not all on Samsung Knox. Therefore this article I found https://docs.samsungknox.com/admin/knox-platform-for-enterprise/kbas/kba-360039092694.htm also did not really help.

Can you give me more information why the password sufficiency policy (compliance policy) might not work correctly or display incompliance, although there is none? What can we do to get rid of those incompliances in monitoring?

For some tested it helped to retire and reenroll the device, but we want to prevent to guide each affected user to reenrollment process. Any other idea?