> 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/wont-spawn.md).

# Vehicle won't spawn

The model is unknown, nothing appears, or the vehicle disappears immediately.

{% hint style="info" icon="bolt" %}
**Quick check:** Check the resource starts without errors, then compare the exact spawn/model name with the product instructions.
{% endhint %}

## Fix it

1. Use the real model name, not the store display name or resource folder name.
2. Test with an existing authorized spawn tool, outside the dealership or garage.
3. If it disappears after spawning, check entity-cleanup and garage logs.

## Check the result

A fresh test vehicle spawns and stays available. If only the dealership fails, open the garage issue below.

## Still happening?

[Vehicle missing from the garage](/studioworks-docs/vehicles/missing-from-garage.md)

[More detailed checks](/studioworks-docs/troubleshooting/spawn-issues.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/wont-spawn.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.