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

# GNX2208 – JSON with corrupted data

Error code 2208 (GNX2208). Error that appears at generation when the Salesforce data sent in the JSON contains corrupted or unsupported characters.

**Error code:** `GNX2208`

## Error description

The error appears when the document is generated.

## Solutions

The system retrieves Salesforce data as it is stored. In some cases, especially for rich text fields, the data may contain unsupported characters, particularly if it comes from external sources or from synchronizations with other systems.

### Recommended actions

1. **Validate the data through Salesforce**: click Edit on the record concerned, then Save so that it goes through Salesforce validation again.
2. **Provide the JSON to support**:
   * Check the `gnx__Save_json_data_in_log__c` box on the Document template
   * Run a generation again
   * Get the information from the "JSON data send" field
   * Send it to Gonexa support


---

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