> 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/error-codes/gnx2208.md).

# GNX2208 – JSON avec de la donnée corrompue

Code erreur 2208 (GNX2208). Erreur apparaissant à la génération lorsque les données Salesforce envoyées dans le JSON contiennent des caractères corrompus ou non supportés.

**Code erreur :** `GNX2208`

## Description de l'erreur

Lors de la génération du document, l'erreur apparait.

## Solutions

Le système récupère les données Salesforce telles qu'elles sont stockées. Dans certains cas — notamment pour les champs texte enrichi — les données peuvent contenir des caractères non supportés, particulièrement si elles proviennent de sources externes ou de synchronisations avec d'autres systèmes.

### Actions recommandées

1. **Valider les données via Salesforce** : cliquer sur modifier l'enregistrement concerné, puis enregistrer pour repasser par la vérification Salesforce.
2. **Fournir le JSON au support** :
   * Cocher la case `gnx__Save_json_data_in_log__c` dans l'onglet Document template
   * Relancer une génération
   * Récupérer l'information du champ « JSON data send »
   * Envoyer au support Gonexa


---

# 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/error-codes/gnx2208.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.