Geofence not triggering alerts or actions on devices: re-converge Blueprint and verify Geofence deployment in Agent logs

Android

If your devices aren't triggering geofence alerts or actions after applying a geofence Blueprint, the configuration may not have deployed correctly to the Esper Agent. This guide walks you through re-converging your Blueprint and verifying geofence deployment using device logs.

Before you begin

Check that your setup meets these requirements:

• You have a Blueprint with geofence configuration applied to your device group
• The Blueprint shows as converged in the Esper Console, but geofence alerts are not firing
• You can physically test the geofence by crossing the defined boundary
• You have access to the Esper Console and can retrieve device logs

Note: Esper currently supports only one geofence configuration per device. If you need geofencing for multiple locations, you will need to use separate device groups or update your Blueprint sequentially.

Step 1: apply Blueprint again the Blueprint

1. In the Esper Console, navigate to Devices & Groups → [Device Name] → Blueprint
2. Locate the Blueprint containing your geofence configuration
3. apply Blueprint again the Blueprint to the affected device by selecting the Blueprint and choosing the apply Blueprint again option
4. Wait for the re-convergence to complete

Important: A converged status in the Esper Console does not guarantee that the geofence configuration actually deployed to the device. Re-convergence forces the system to reapply the configuration.

Step 2: Test the geofence on the device

1. After re-convergence completes, physically test the geofence by crossing the defined boundary
2. Check whether the configured alert or action triggers (such as an email notification or audible alert)
3. Allow a reasonable time window for the alert to arrive, particularly on cellular connections where delays are common

Note: Do not rely on email timing alone to determine if geofence is working. Geofence alerts on cellular connections may arrive with noticeable delay.

Step 3: Pull a bug report if geofence still isn't working

1. If the geofence alert did not trigger after boundary crossing, immediately pull a fresh bug report from the device
2. In the Esper Console, navigate to Devices & Groups → [Device Name] → Bug Report
3. Review the Esper Agent logs in the bug report
4. Search the logs for any mention of:
   • Geofence configuration receipt
   • Geofence module initialization
   • Boundary event processing

If the logs contain no geofence-related entries, the configuration is not reaching the Esper Agent on the device.

Step 4: Update your Esper Agent (if needed)

If the logs confirm the geofence configuration is not being deployed:

1. Check the current Esper Agent version on your device
2. If you are running Esper Agent v12, update to v13 or the latest available version
3. Re-apply the Blueprint and repeat the boundary-crossing test

Earlier versions of the Esper Agent may contain a silent failure where the Blueprint appears to converge successfully, but the geofence configuration does not deploy to the device.

Troubleshooting tips

• Blueprint convergence vs. actual deployment: the Esper Console shows the Blueprint as converged, but this does not mean all sub-configurations (including geofence) have deployed successfully. Always verify by reviewing Agent logs.
• Network alerts vs. geofence alerts: Receiving network online/offline alerts does not mean geofence is working. These are separate alert types.
• Single geofence limitation: You can configure only one geofence at a time per device. If you need geofencing for multiple locations, you will need to update your Blueprint or create separate device groups.
• Field testing: If your devices are remote or field-deployed, perform controlled boundary-crossing tests immediately before pulling a bug report. Device logs may not capture older events.

Still need help?

If re-convergence and geofence testing do not resolve the issue, or if 10 or more devices are affected, contact Esper Support. include:

• The bug report and Esper Agent logs from an affected device
• Your Blueprint name and device group path
• The Esper Agent version installed on your device
• A screenshot of the Blueprint convergence status from the Esper Console