> For the complete documentation index, see [llms.txt](https://docs.tensorleap.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tensorleap.ai/user-interface/project/menu-bar/runs-and-processes/process-types/graph-validate-process.md).

# Graph Validate Process

### Overview

Once the [validate assets](/user-interface/project/network/network-mapping/validate-mapping.md) button was clicked, a new Graph Validation process will initiate

This process:

* Loads an Input and Ground Truth (if available) in the same as the [dataset parse](/user-interface/project/menu-bar/runs-and-processes/process-types/dataset-parse-process.md) does
* Feeds the inputs to the model 
* Feeds the model prediction and the ground truth (if available) to the metrics, losses, and visualizers.

### Common Run Issues:

{% hint style="danger" %}
Graph validate mostly fail due to these reasons:

* A bug or unexpected use of the [integration script](/tensorleap-integration/writing-integration-code.md). Can be mostly prevented with [integration testing](/tensorleap-integration/integration-test.md).
* OOM in graph validate, please adjust the limits in the [settings](/user-interface/settings.md) page.
  {% endhint %}


---

# 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.tensorleap.ai/user-interface/project/menu-bar/runs-and-processes/process-types/graph-validate-process.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.