> 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/user/guide/events-and-notifications/scheduling-and-dispatching/deviation-from-the-route.md). # Deviation from the route Get notified when a vehicle deviates from a planned route. Uses route-type geofences to define the permitted path and alerts when the object moves outside it. The route deviation rule enables monitoring of deviations from a predefined route. This rule ensures that vehicles or objects adhere to planned routes, improving efficiency and enhancing security by promptly identifying and addressing any deviations. Users receive notifications whenever a vehicle or object deviates from the specified route, helping to maintain compliance and optimize operations. ## Rule settings ### Route geofences around paths To use the route deviation rule, you must first create one or more route geofences in the Navixy platform. Follow these steps to set up the rule: 1. **Create route Geofences**: Before setting up the rule, ensure you have created route geofences categorized as **Route**. 2. **Select Geofences**: Choose the route geofences you want to monitor for deviations. Only geofences categorized as **Route** can be used for this purpose. For common settings, see [Rules and alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * The **Deviation from the route** alert has a 10-second reset timer, meaning the alert event doesn't occur more often than once every 10 seconds. If an event occurs while the rule is waiting for the reset, the platform omits the event, including in reports. * This rule is processed in the cloud and not tied to any specific hardware, allowing it to be applied to multiple GPS devices simultaneously. This flexibility enables you to select several GPS devices within a single rule. --- # 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/user/guide/events-and-notifications/scheduling-and-dispatching/deviation-from-the-route.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.