> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/troubleshooting/diagnostic-families.md).

# Diagnostic families

<table data-search="false"><thead><tr><th>Range</th><th>Phase</th><th>Meaning</th></tr></thead><tbody><tr><td><code>GPC10xx</code></td><td>lexer warnings</td><td>token recognized with a recoverable issue</td></tr><tr><td><code>GPC11xx</code></td><td>lexer errors</td><td>invalid/unterminated token or out-of-range literal</td></tr><tr><td><code>GPC2xxx</code></td><td>parser errors</td><td>grammar, delimiter, or required-form failure</td></tr><tr><td><code>GPC30xx</code></td><td>semantic warnings</td><td>valid source with suspicious/dead/suboptimal meaning</td></tr><tr><td><code>GPC40xx</code></td><td>semantic errors</td><td>invalid name, scope, array, flow, or declaration meaning</td></tr><tr><td><code>GPC51xx</code></td><td>compiler errors</td><td>code generation, argument, limit, or internal failure</td></tr><tr><td><code>GPC60xx</code></td><td>extended warnings</td><td>suspicious calculations, unused items, stack risk, or data width</td></tr><tr><td><code>GPC9xxx</code></td><td>function-specific</td><td>targeted API warnings</td></tr></tbody></table>

The catalog contains a few target-specific messages for non-Live modes because they exist in the compiler's diagnostic universe. This book's working target remains Zen Studio Live 32-bit.


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/troubleshooting/diagnostic-families.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.
