Geofences cannot be edited after creation: delete and recreate to modify

Android

When you need to change a geofence's name, coordinates, or radius, the Esper Console does not provide an edit option — geofences are immutable once created and must be deleted and recreated with the updated parameters.

Why this happens

Geofences in Esper are written as fixed configuration objects at the time of creation. The platform does not support in-place edits to geofence parameters, so any change — however minor — requires removing the existing entry and defining a new one.

How to modify a geofence

1. Open the Esper Console and navigate to Blueprints. Locate and open the blueprint that contains the geofence you want to change.
2. Find the geofence entry in the geofencing configuration section of the blueprint.
3. Delete the existing geofence entry. This removes it from the blueprint — it does not immediately affect devices until the blueprint is republished and converged.
4. Create a new geofence in the same section with your corrected parameters — updated name, adjusted coordinates, or new radius.
5. Save the blueprint.
6. Republish the blueprint and converge it to your target device group or groups. Converging pushes the updated geofence configuration to enrolled devices. You can confirm convergence status at Devices & Groups → [Device Name] → Blueprint.

Verify: After convergence completes, open Devices & Groups → [Device Name] → Blueprint and confirm the blueprint status shows In Sync. The device should begin reporting location against the new geofence boundary within a few minutes of a successful sync.

If the geofence still triggers false alerts after applying the new configuration

If devices report incorrect location alerts after the new geofence has been applied and the blueprint shows In Sync, the issue is likely GPS accuracy rather than configuration.

• Reboot the affected device and allow several minutes for GPS to reacquire a stable fix — this is especially relevant after a cold start or in low-signal environments.
• Confirm location permissions are enabled for the Esper Agent on the device.
• Check whether the device is indoors, in a basement, or inside a dense structure where GPS signal is degraded. Persistent drift in these environments is a hardware limitation, not a platform issue.

If this doesn't resolve it

If the blueprint does not reach In Sync after republishing, or if the geofence configuration is not reflected on the device, collect the following before contacting support:

• The blueprint name and the device serial number or ID
• A screenshot of the blueprint convergence status from Devices & Groups → [Device Name] → Blueprint
• The Activity Feed entries for the affected device around the time of the last convergence attempt

Contact Esper Support with this information so the issue can be investigated.

Still need help?

If you need to modify a geofence configuration, submit a support ticket with details about the geofence you're trying to update and the specific changes needed.