That depends on when your MobiControl server can get the location data to check if the device has exited any geofence defined in an alert rule associated with it.

The delay you mentioned may be due to one or more of the following factors:

1. GPS hardware was off or could not receive strong enough signal to determine the location, and there is no location data information available from Cellular or Wifi around

2. The location data mentioned in (1) are available on the device side, but the device connection is off or has problem such that the location data cannot be passed back to the MobiControl server

3. The error of the location data is marginally big enough such that the server algorithm consider that the device is still within the geofence region.

4. There is no data collection rule deployed to capture location data regular enough (the smallest support interval is 2 minutes) for the server algorithm to detect any geofence entry/exit in between times when device gets connected to the server. (Thus the device may be marginally within the geofence when the device get synced with the server, but is well outside the geofence in between.)

If the data collection rule has been deployed and the device gets in and out of the geofence multiple of times in between two sampling instant, server algorithm can still use the collected data samples to raise multiple alerts (though possibly delayed because location data are typically buffered and not flushed and sent to the server every minute).  

Hi James,

Thank you for posting on SOTI Pulse!

How many devices do you have that are affected by this? Which version of Mobicontrol and agent you are using?

If this issue continues to be occurring, you can create a support case with us and we can help you troubleshoot this issue and also create a developer's ticket if required.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net l Discussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter