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

# Resource won't start

Check folder, manifest, and dependency errors at startup.

## Symptom

The server console reports a missing resource, missing manifest, dependency error, or an error immediately after starting the resource.

## Possible causes

A wrong folder name, extra folder level, incomplete upload, or dependency that has not started. Licensing errors are covered separately.

## Checks and fixes

1. Compare the `ensure` entry with the actual resource folder name. On Linux, letter case matters.
2. Check that the included `fxmanifest.lua` is directly inside the resource folder. If the package is nested incorrectly, extract the original ZIP properly.
3. Compare your upload with the complete package, including any supplied hidden files.
4. If you added the resource while the server was running, run `refresh` in a suitable test/maintenance window, then start that resource.
5. Read dependency errors literally. Confirm that the correct resource and version are installed and started first.
6. For configuration syntax errors, compare the changed section with a fresh original file. Back up your edits before resetting anything.

## Match the message

| Message                                 | Next check                                                                         |
| --------------------------------------- | ---------------------------------------------------------------------------------- |
| Resource not found                      | Name, resource location, and folder nesting                                        |
| Manifest missing or unreadable          | Complete original package and file access                                          |
| Missing dependency                      | Required version, folder name, and start order                                     |
| Protected resource verification failure | [Escrow & licensing](/studioworks-docs/troubleshooting/escrow-licensing.md)        |
| Missing export                          | [Integration and version](/studioworks-docs/troubleshooting/script-integration.md) |

## Confirm the fix

The resource should start without the original error. Then test the actual feature; a startup message alone does not prove the setup is complete.

**Include in your ticket:** Exact error, resource folder name, product version, first startup log, and a folder-structure screenshot with sensitive information removed.

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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/resource-wont-start.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.