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

# GNX1203 – A dependent document is not added at generation

Error code 1203 (GNX1203). The configured related (dependent) document is not added after the main document at generation.

**Error code:** `GNX1203`

## Error description

When document generation is triggered, the configured related document does not appear after the main document.

## Solutions

### Missing dependency

* Add a dependency between your main document and your related document(s)

### Related document type

* Make sure the related document template has a Type: Single or Multiple

### Filter on the dependency

* Make sure the condition displays the related document; check the conditions created on the dependency, if any

### Object names of a multiple-type related document

* If the related document is of type Multiple, the child object of the main document must have the same name as the main object of the related document


---

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