> For the complete documentation index, see [llms.txt](https://docs.high-mobility.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.high-mobility.com/changelog/readme/july-2025.md). # July 2025 High Mobility platform updates on July 2025 * Introduce new [reject reason](/docs/getting-started/fleet-clearance/activation-process.md#pending-and-reject-reasons) to VW brands. When a vehicle is not able to be added to fleet–usually due to it being activeated via another provider– we expose that to our customer using the new reject reason `OEM fleet assignement failed` for VW brands * Map new [reject reason](/docs/getting-started/fleet-clearance/activation-process.md#pending-and-reject-reasons) for VW brands when it's not possible to activate a vehicle, the new reason is called `ineligible or constrained VIN` . In most cases it means the vehicle is not elligiable and in some rare case it means its activation is blocked by VW. * Reject vehicles when an invalid VIN is provided while activating BMW/MINI vehicles. it's mapped to `invalid VIN` [reject reason](/docs/getting-started/fleet-clearance/activation-process.md#pending-and-reject-reasons). * Maintenance on KIA integration --- # 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://docs.high-mobility.com/changelog/readme/july-2025.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.