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

# Validation

Validations can be seen in the tab under the Validate button located on the top right corner of the screen. Any problems with the script will be shown here. Double clicking on each validation error navigates the screen to the Episode, Segment etc. where the error has been detected.

![image.png](https://files.nuclino.com/files/3a336f7b-7c7e-48fa-b5f2-e4444b942759/image.png)

Validation can also be done through the Menu Bar under "Document ▸ Validate…" which will automatically open the right tab and run Validation. In order for a script to be complete and fully operational, the Validate tab should read "No issues".

### Errors & Warnings

Errors and warnings can be seen in the Validation tab on the right side of the screen. Errors are indicated with a red sign whereas the warnings indicated with a yellow. The difference between an error and a warning is primarily that an error may cause the script not to run through (see Walkthrough), whereas a warning is given simply to note that certain parts of the document are missing. There are main categories of each, and under them it is possible to see where these have occurred followed by a concise description of what they are caused by.

When an error is fixed, refreshing the Validation tab through the Refresh (⟳) icon on the top right corner of the tab will remove the error/warning sign, which indicates that the error/warning has been fixed.


---

# 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://help.ctrlmovie.com/guide/validation.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.