I believe the issue arises from a mismatch between the data uploaded to the ZT portal and the information present on the device end. For instance, the data uploaded to the ZT portal might be IMEI1, whereas the data retrieved on the device end is IMEI...
If you can check the device via ADB to see if it declares the com.google.android.feature.AER_OPTIMIZED, if it does, it should only be a matter of a discrepancy in the verification time
To my knowledge and based on actual testing, because Zero Touch relies on the device connecting to Google's servers over the internet for verification, even if the setup wizard initially opts for an offline configuration, once the device connects to ...
