Why are geofence-based policies delayed or inconsistent in Hexnode, and how can we fix it?Solved

Participant
Discussion
1 day ago May 03, 2026

Hi, We recently implemented geofencing in Hexnode for a small group of devices as part of a security setup. The idea was to restrict access when users move outside our office premises. 

It’s mostly working, but we’re seeing a few issues: 

  • Some users inside the office aren’t getting the expected access 

  • A few devices keep switching between policies even when stationary 

  • There’s also a delay when users leave the office before restrictions kick in 

Is this expected behavior, or are we missing something in the configuration? 

Replies (1)

Marked SolutionPending Review
Hexnode Expert
22 hours ago May 03, 2026
Marked SolutionPending Review

Thanks for raising this query! 

What you’re experiencing is quite common when implementing location-based policy enforcement, and it usually comes down to synchronization timing and location accuracy. Let’s break it down: 

1. User inside geofence but no policy applied: This typically points to a mismatch in directory data. Since your setup depends on AD/IdP attributes: 

  • Ensure the user’s attribute (like Title or Office Location) exactly matches what’s defined in your dynamic group filter. 

  • Also confirm that the latest directory sync has completed in Hexnode. 

Even small differences in spelling or casing can prevent the device from being grouped correctly. 

2. Devices switching policies repeatedly (policy flapping): This happens due to unstable location signals, especially indoors where GPS accuracy can fluctuate. 

A practical fix is to: 

  • Slightly increase the geofence radius to create a buffer zone This reduces rapid transitions caused by minor location shifts. 

3. Delay in applying restrictions after leaving the location: This is expected behavior tied to the device’s location update interval. 

By default, devices report location periodically (for example, every 15 minutes). So: 

  • The restriction only applies after the next location sync 

For tighter control: 

  • Reduce the location tracking interval (where feasible) 

  • During critical situations, you can manually trigger a device location scan from the console for immediate updates 

Additional recommendation: For Android devices, ensure stronger enforcement by: 

  • Enrolling devices in Device Owner mode 

  • Disabling mock location 

  • Enforcing GPS-based tracking 

This prevents users from bypassing location checks. 

Overall, your setup is correct, the behavior you’re seeing just needs a bit of tuning around sync intervals and geofence calibration to make it more consistent. 

Please do reach out if you have more queries. 

Regards,
Mary Romero

 

Save