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

# Troubleshooting

## Diagnostics: SQL protocol

The **SQL protocol** records all database operations performed by GeoDin for later analysis. The protocol captures the actions executed, their execution time, and whether they succeeded. It is especially useful when debugging newly developed complex SQL queries.

### Starting and stopping the protocol

Start the protocol from the **Information** menu with **Start SQL protocol**. All SQL commands executed afterwards are recorded. To stop the protocol, select the same menu item - it is now labelled ![Stop SQL protocol](/files/W5zH7YBgc8xWKKn19ja1) **Stop SQL protocol**. The recorded protocol is then displayed in a separate window and can be saved as a text file.

You can also toggle the protocol with the keyboard shortcut **Alt+S**, without using the menu.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.geodin.com/support/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.