# Why does my history show too many stops?

## Question

My device has too many short stops. How do I fix this?

## Answer

* If your route history shows multiple short stops or “gaps,” it usually means the device’s speed often drops below the defined **min\_speed** threshold for longer than the **min\_parking** time. In this scenario, the system interprets each drop in speed as a new parked state, ending one trip and starting another when the speed picks up again.
* Other factors like ignition status or motion sensor data can also influence whether the system flags a stop. For example, if the ignition is off or motion is not detected for the duration of **min\_parking**, the track is considered ended.
* To reduce gaps, review and adjust the **min\_speed** and **min\_parking** settings as needed. You can learn more by visiting the official Parking detection documentation.

## Links

* [Parking detection documentation](/docs/user/guide/events-and-notifications/movement-monitoring/parking-state-detection.md)


---

# Agent Instructions: 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/qna/using-navixy/why-does-my-history-show-too-many-stops.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.
