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

# Troubleshooting

Compiler errors, warnings, tracing, runtime bisection, output order, persistence, and optimization.

<figure><img src="https://611779084-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyIhlDMEOMB6JOWTfU9zr%2Fuploads%2FFLag8XOo9JlbEuswpwtT%2Fdebug-from-the-first-trustworthy-signal.svg?alt=media&amp;token=77d42743-2b0d-4219-9c48-22d4f72c08e0" alt=""><figcaption></figcaption></figure>

Fix the first trustworthy failure, trace system boundaries, isolate runtime bugs, and optimize from measured compiler results.

***

**Work through these pages in order the first time. Return directly to any page later as a reference.**

* [Fix the first diagnostic first](/gpcscripting/gpc-script-guide/troubleshooting/fix-the-first-diagnostic-first.md)
* [Diagnostic families](/gpcscripting/gpc-script-guide/troubleshooting/diagnostic-families.md)
* [High-value compiler errors](/gpcscripting/gpc-script-guide/troubleshooting/high-value-compiler-errors.md)
* [High-value warnings](/gpcscripting/gpc-script-guide/troubleshooting/high-value-warnings.md)
* [Trace the right boundary](/gpcscripting/gpc-script-guide/troubleshooting/trace-the-right-boundary.md)
* [Binary-search a runtime bug](/gpcscripting/gpc-script-guide/troubleshooting/binary-search-a-runtime-bug.md)
* [Output-order diagnosis](/gpcscripting/gpc-script-guide/troubleshooting/output-order-diagnosis.md)
* [Persistence diagnosis](/gpcscripting/gpc-script-guide/troubleshooting/persistence-diagnosis.md)
* [Optimization order](/gpcscripting/gpc-script-guide/troubleshooting/optimization-order.md)
* [Live-only review checklist](/gpcscripting/gpc-script-guide/troubleshooting/live-only-review-checklist.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://guide.cronuszen.com/gpcscripting/gpc-script-guide/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.