> 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/gnx1202.md).

# GNX1202 – A Gonexa tag based on a main object is not identified or displays nothing

Error code 1202 (GNX1202). A Gonexa tag based on the main object is not recognized in the merge fields and stays empty at generation because its syntax is incorrect.

**Error code:** `GNX1202`

## Error description

When a document is generated, the Gonexa tag is not replaced or displays an empty value. The element is not recognized in the merge fields of the document template.

## Solutions

### Tag not identified: created or edited manually

* The tag does not follow the strict format starting with `{!` and ending with `}`, so it is not identified in the merge fields
* Open the assistant and check the construction against the naming convention: `{!Etiquette|NomAPI}`


---

# 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/gnx1202.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.