> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/how-geofence-exit-events-work.md). # How geofence exit events work Platform checks location updates against geofences in real time; a 60-second timer prevents duplicate entry and exit events ## Question How do geofence exit events work? ## Answer Each geofence has its own set of coordinates defining its boundaries. Devices regularly send their current location to the platform. If a device's coordinates move **outside** a geofence and there is an active rule for geofence entry/exit for that geofence, the platform generates an event. In other words, the platform continuously checks incoming location updates against all geofences and their corresponding rules in real time. To avoid duplicate events, there's a timer in place: once an entry or exit event is triggered, the platform doesn't register the same type of event again for the next 60 seconds. Here's a simple example to show how this works: * 00:00:00 — The device enters the geofence → entry event is triggered. * 00:00:15 — The device exits the geofence → exit event is triggered. * 00:00:30 — The device enters again → no event triggered (less than 60 seconds since the previous entry event). * 00:01:20 — The device exits again → exit event is triggered (more than 60 seconds since the previous exit event). This mechanism helps filter out noise from devices moving near geofence borders and prevents flooding the system with repeated events. ## Links * [Geofence entrance/exit: system details](/docs/user/guide/events-and-notifications/movement-monitoring/geofence-entrance-or-exit.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/qna/using-navixy/how-geofence-exit-events-work.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.