> 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

## Overview

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 will alert 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, please refer to the Parking Detection article.

To monitor dwell time in specific areas, bind the rule to the designated geofences.

For common settings, please refer to [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 will not trigger more frequently than once every 10 seconds. If an event occurs while the rule is waiting for the reset, the platform will omit 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 trackers simultaneously. This flexibility enables users to manage several trackers 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/user/guide/events-and-notifications/scheduling-and-dispatching/parking-time.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.