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

# Export, database, inventory or UI error

Investigate exports, databases, inventories, UI, and permissions.

## “No such export” or missing function

**Check:** Is the named resource installed and started first? Do its resource name, supported version, and documented export match? Does the call belong on the client or server?

**Fix:** Match the integration to the documented interface and installed version. Renaming a resource can break expected references. Do not invent replacement events or exports.

## Database errors

**Check:** Read the first database-adapter error. Distinguish connection failures, missing tables/columns, and invalid queries.

**Fix:** Check the selected database and installation/update instructions. Back up data before schema changes. Do not import SQL repeatedly or delete tables as general troubleshooting.

## Item or weapon does not work

**Check:** Do the item name and inventory registration match the product instructions? Are required images, components, and use mappings installed? Does the product support that inventory version?

**Fix:** Correct the inventory integration after the resource starts successfully. An inventory image does not prove the related function is registered.

## Menu or UI does not open

1. Save the related F8 error and server error.
2. Check the documented command, key binding, or interaction point.
3. Verify job, role, and ACE permissions.
4. Check required target/menu resources and their start order.
5. Test untouched settings with the required dependencies.

## “Command not allowed” or permission denied

Identify **which command** was denied and **which user or resource** attempted it. Grant only the documented permission. Allowing every command is not an appropriate fix.

## After a configuration change

Compare the edited section with the original. Missing commas, quotes, wrong value types, or outdated configuration fields can cause errors. Save your changes before testing the original settings.

**Include in your ticket:** First error, framework/inventory/adapter versions, relevant integration file or redacted excerpt, and completed tests.

***

[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/script-integration.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.