> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/university/en/error-codes/gnx1211.md).

# GNX1211 – The generation component keeps loading or displays an error

Error code 1211 (GNX1211). The standard generation component keeps loading or displays an error, so the document template cannot be selected.

**Error code:** `GNX1211`

## Error description

When generating the document, the standard generation component keeps loading and the document template cannot be selected.

## Solutions

### Check the conditions on your document templates

Check the conditions on the main objects of the document templates. A condition may be incorrectly written and prevent the templates from being queried

### Check the "Language field on the main object" field

This field initializes the generation component with a dynamic value when translating templates, and must contain the API name of a Language-type field

### Check the visibility of the fields and objects used in the document template

Make sure users have visibility on the fields and objects used in the document template, especially the field used for the generated document's suffix


---

# 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://university.gonexa.fr/university/en/error-codes/gnx1211.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.
