> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/vehicles/missing-from-garage.md).

# Vehicle missing from the garage

The vehicle spawns manually, but is missing from a garage, dealership, or saved vehicle list.

{% hint style="info" icon="bolt" %}
**Quick check:** Confirm the direct model test works before editing vehicle files.
{% endhint %}

## Fix it

1. Compare the garage/dealership model mapping with the exact model identifier.
2. Check that the system's required catalog, category, ownership and database entries exist.
3. Test a new entry and a fresh vehicle separately from an old saved vehicle.

## Check the result

The vehicle appears in the intended list and can be retrieved using the correct ownership rules.

## Still happening?

If it also fails to spawn manually, use [Vehicle won't spawn](/studioworks-docs/vehicles/wont-spawn.md).

[More detailed checks](/studioworks-docs/vehicles/installation.md) · [Prepare a support ticket](/studioworks-docs/support/preparing-a-ticket.md)

Include the product version, first error, and the steps you tried. Keep secrets out of logs and screenshots.


---

# 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://studioworks.gitbook.io/studioworks-docs/vehicles/missing-from-garage.md?ask=<question>&goal=<user_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.