A unit drove into or through a geofence. Yet a geofence visits report has no row for it, or a geofence alert rule opened no incident.
The app compares each position a unit reports with the geofences. Alert rules react when a unit crosses the outline; reports count a visit from entry to exit. Everything on this page comes back to one question: did a position the app counts fall inside a geofence the account may use?
A small geofence, crossed at speed, can fall between two positions. If no position lands inside the outline, the app sees no entry.
Check
Fix
The app checks a visit against the account's own geofences and the shared ones from accounts above it. It never uses geofences of accounts below. A parent account's geofence counts in a sub-account only with Share with child accounts on.
Check
Fix
When GPS fails, the app can estimate a position from cell towers or Wi-Fi. These positions do not trigger geofence entries and exits unless the device's Position filter tab has Count for geofence entry and exit on.
Check
Fix
These positions can be off by hundreds of metres, so expect false entries near the edge.
Most platforms only mark a position that fails the GPS checks as rejected, and still use it. On a platform that runs strict filtering, the app replaces a failed position with the last good one. A run of bad fixes inside a geofence can then hide the visit.
Check
Fix
The tab applies to new messages only.
Reports read stored visits that the app works out as messages arrive. After a change to the unit's devices or sensors, the app recalculates the period. Until it finishes, the Generate screen shows a notice.
Fix
Follow the notice. See A report or dashboard widget is empty, out of date or shows an error.
If the visit is in the report but no alert came, the cause is in the rule: its Applies to, schedule, hold time or caps.
Fix
Contact support@getgps.eu with: