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

# General errors

Start with the symptom and test one possible cause at a time.

## Which message or symptom do you see?

| I see this                                                                   | Open this fix                                                                               |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Resource not found, missing manifest, or missing dependency                  | [Resource won't start](/studioworks-docs/troubleshooting/resource-wont-start.md)            |
| “You lack the required entitlement” or “Failed to verify protected resource” | [Entitlement and protected files](/studioworks-docs/troubleshooting/escrow-licensing.md)    |
| A model is unknown or will not load                                          | [Model won't spawn](/studioworks-docs/troubleshooting/spawn-issues.md)                      |
| A model is invisible or has broken textures                                  | [Invisible model or missing textures](/studioworks-docs/troubleshooting/models-textures.md) |
| Tuning, extras, lights or sirens do not work                                 | [Missing tuning, extras or lights](/studioworks-docs/troubleshooting/tuning-lights.md)      |
| Missing export, SQL error, inventory or UI failure                           | [Integration error](/studioworks-docs/troubleshooting/script-integration.md)                |
| Crash, freeze, low FPS or slow script                                        | [Crashes and performance](/studioworks-docs/troubleshooting/crashes-performance.md)         |

{% hint style="info" icon="magnifying-glass" %}
Search the exact error wording with **Ctrl + K**. If you know the asset category, its sidebar lists more specific problems.
{% endhint %}

## What should I capture first?

Save the **first error**, the action that triggered it, and whether it affects one client, everyone, or the server. Test one change at a time on a development server.

[My issue is still unresolved](/studioworks-docs/support/preparing-a-ticket.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://studioworks.gitbook.io/studioworks-docs/troubleshooting.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.