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

# Loader errors

Loader messages include a stable code. Match that code rather than guessing from the visible wording.

| Code                   | Meaning                                                 | What to do                                                                              |
| ---------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| invalid\_key           | Key is wrong or belongs to another project              | Copy the full key and check the loader's project                                        |
| key\_revoked           | Key was revoked/banned                                  | Ask the project owner to review it                                                      |
| key\_expired           | Expiry passed                                           | Renew or get another key                                                                |
| blacklisted            | Device is banned in this project                        | Ask the owner to review the hardware ban; another key won't bypass it                   |
| hwid\_mismatch         | Key is bound to another device                          | Use that device or request a legitimate reset                                           |
| payload\_too\_large    | Payload exceeds delivery size limit                     | Owner should reduce/re-publish the script                                               |
| payload\_error         | Downloaded script failed to load                        | Owner should inspect the published script and compatibility                             |
| network\_error         | Download/authorization communication failed             | Check connectivity and run again after a short wait                                     |
| rate\_limited          | Too many requests                                       | Stop looping and wait for the retry window                                              |
| loader\_not\_found     | URL no longer resolves to an available connected loader | Copy its current dashboard URL; check deletion, rotation, connection and disabled state |
| invalid\_request       | Malformed loader request                                | Use the current bootstrap/snippet; custom clients should check field formats            |
| executor\_unsupported  | Required executor features are missing                  | Use a compatible environment; inspect the missing-feature message                       |
| session\_expired       | Lease/session expired                                   | Execute again to start a fresh run                                                      |
| session\_not\_found    | Session is no longer valid or scope doesn't match       | Restart from the current loader rather than reusing a token                             |
| instance\_limit        | Key reached its concurrent lease limit                  | End an older run and allow its lease to release/expire                                  |
| configuration\_changed | Loader/project routing changed                          | Get the current snippet and execute again                                               |
| runtime\_tampered      | Read-only runtime context was modified                  | Stop assigning to VAMPAUTH or its fields                                                |

## Before reporting a loader bug

Send the code, approximate time, loader/project name, and whether the same key works in a fresh run. Keep the plaintext key and private credentials out of public screenshots. Resetting hardware doesn't repair a deleted URL or publishing error.


---

# 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://vampauth.gitbook.io/vampauth-docs/troubleshooting/loader-errors.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.