> 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/my-vehicle-didnt-stop-yet-the-trip-is-split.md). # My vehicle didn't stop, yet the trip is split Review Parking Detection settings and inspect raw data to find the cause; disable Split by stops in History to view the full track ## Question Why are my device's trips stopping and starting randomly? ## Answer The most likely cause for a trip to seemingly end and start later, farther down the road where it can't park is most likely due to Parking Detection. Please review your Parking Detection settings and compare against the data within the Raw Data Export tool. The device most likely was moving at a speed lower than the Parking Detection limit. Other possibilities include device issues due to GPS signal or the device itself not providing speed information. The Raw Data Export tool will show this specifically. A possible way around this is to uncheck the **Split by stops** option on the object widget, which shows the path as a single track. ## Links * [Parking detection](/docs/user/guide/events-and-notifications/movement-monitoring/parking-state-detection.md) * [Raw data export](/docs/user/guide/devices-and-settings/object-management/raw-data.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/my-vehicle-didnt-stop-yet-the-trip-is-split.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.