> 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/parking-time.md). # Parking time Get notified when a vehicle remains parked beyond a configured time limit. Bind to geofences to monitor dwell time in specific locations. The Parking Time rule is designed to notify users when a vehicle's parking duration exceeds a specified limit. This rule is crucial for monitoring how long vehicles remain stationary, ensuring that drivers adhere to set time standards for parking and dwell periods. For instance, if the allowed parking duration is set to 30 minutes, the system alerts users whenever a vehicle remains parked beyond this limit. These notifications can be delivered through the user interface, email, or SMS, and users can also generate reports to review these events historically. ## Rule settings **Allowed parking time**: The parking time begins counting as soon as the vehicle enters a parked state. Users can configure the allowed parking duration, with options ranging from 5 to 60,000 minutes. The timer resets when the vehicle exits the parked state. For more detailed information on parking detection, see the [Parking detection](https://www.navixy.com/docs/user/guide/devices-and-settings/location-and-movement/parking-detection) article. To monitor dwell time in specific areas, bind the rule to the designated geofences. For common settings, see [Rules and alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * The **Parking time** alert has a 10-second reset timer, meaning the alert doesn't trigger more frequently than once every 10 seconds. If an event occurs while the rule is waiting for the reset, the Navixy platform omits the event, including in reports. * This rule is processed in the cloud and is not tied to any specific hardware, allowing it to be applied to multiple GPS devices simultaneously. This flexibility enables users to manage 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/parking-time.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.