> 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/import-model-process.md).

# Import Model Process

This describes the Import Model process

### Overview

Once an upload of a model to Tensorleap had initiated, an import model process starts.

This process:

* Uploads the model into the Tensorleap server
* Parses through the model and extracts menaingful indicators for future use
* Converts the model into a Tensorleap Format that the Engine can easily utilize for analysis

### Common Run Issues:

{% hint style="danger" %}
An import Model process can fail due to:

* Invalid model (please ensure the model you upload is able to infer locally)
* Unsupported model architecture (please contact Tensorleap team)
* The use of a custom Layer in a .h5 file. To support custom h5 layers, you need to register a [custom layer](/tensorleap-integration/writing-integration-code/custom-layers.md) to the [integration script](/tensorleap-integration/writing-integration-code.md) before upload.
  {% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tensorleap.ai/user-interface/project/menu-bar/runs-and-processes/process-types/import-model-process.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.