Upon setting the beacon interval to 30 minutes and creating a compliance policy to check the compromised status, the Agent is not seding the beacon immediately after enrollment. This is affecting the compromised compliance rule and could cause delays in the initial scan for compromised detection on the device.
Note: If the device is connected through GCM or the heartbeat interval is set to 30mins or less, the issue does not occur.
This affects Android Agent v5.3.
This issue has been given identifier AAGNT-175544. This issue has been resolved in Android Agent 5.3.1.