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

# GNX2207 – JSON with invalid tag extensions

Error code 2207 (GNX2207). Error that appears at generation when rich text field tags use invalid extensions.

**Error code:** `GNX2207`

## Error description

The error appears when the document is generated. Your document contains one or more tags with invalid extensions on rich text area fields.

Here are examples of tags with incorrect extensions:

* `{!Account|Commentaires__c(HTML,f,c,e)}`: the "e" extension does not exist
* `{!Account|Commentaires__c(HTML,a,p)}`: the "a" and "p" extensions do not exist

## Solutions

### Provide the JSON to support

Check the `gnx__Save_json_data_in_log__c` box on the Document template concerned to save the JSON in the logs. Then run a generation again and get the information from the "JSON data send" field. Copy it and send it to Gonexa support so that we can investigate.

{% hint style="info" %}
If a tag extension is invalid, it returns nothing.
{% 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://university.gonexa.fr/university/en/error-codes/gnx2207.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.