Troubleshooting and Best Practices


Issue	Possible Cause	Recommended Action
Geofence policies not applied	Device not enrolled or offline	Ensure devices are enrolled, connected, and synced with the MDM server
Location-based triggers not firing	GPS or location services disabled on device	Confirm that location services are enabled and the app has required permissions
Policy applied incorrectly	Incorrect device or group targeting	Review device assignment and confirm geofence boundaries
Delayed policy application	Network connectivity issues or server sync delay	Check device connectivity and server status; wait for automatic sync or trigger manual refresh
Wipe/lock actions not executing	Device not supervised or not enrolled properly	Verify device supervision and enrollment status

Recommended Practices for Stable Geofence Operations

Use Static Device Groups: Since smart group targeting is not supported in version 3.5, always assign geofencing policies to static groups or individual devices.
Test Policies in a Controlled Environment: Apply geofencing policies to a small set of test devices before full deployment.
Maintain Up-to-Date Device Location Settings: Ensure that location services are always enabled on devices and that the MDM app has necessary permissions.
Monitor Policy Status Regularly: Use the WebUI to track geofence policy deployment and status. Address any failed actions promptly.
Limit Overlapping Geofences: Avoid overlapping zones that may trigger conflicting policies. Clearly define boundaries for each geofence.
Schedule Critical Actions Appropriately: For sensitive actions like Wipe or Lock, notify users in advance and schedule actions during off-peak hours if possible.


Issue	Possible Cause	Quick Fix / Recommended Action
Geofence policy not applied	Device offline or not enrolled	Ensure device is enrolled, supervised, and online; trigger a manual sync if needed
Location-based triggers not firing	GPS/location services disabled or permissions missing	Enable location services and verify MDM app permissions
Policy applied to wrong devices	Incorrect device/group selected	Double-check device assignment and group membership
Delayed policy execution	Network connectivity issues or server sync delay	Check network connectivity; wait for automatic sync or trigger manual refresh
Wipe/Lock/Restrictive action fails	Device not supervised or not properly enrolled	Verify device supervision/enrollment; reassign if necessary
Overlapping geofence policies cause conflicts	Multiple geofences overlapping	Redefine geofence boundaries to avoid overlap; assign distinct zones
Frequent policy failures	Outdated MDM agent or app	Update MDM agent/app to latest version and verify compliance