> 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/gnx2209.md). # GNX2209 – Generation time too long Error code 2209 (GNX2209). Error that appears when document generation exceeds the 2-minute maximum because of too large a volume of data. **Error code:** `GNX2209` ## Error description The generation time exceeds 2 minutes. Your document cannot be generated because there is too much data to display. ## Solutions Document generation is affected by several factors: template complexity, conditions applied, number of tags, number of records, dependent documents and related attachments. The maximum time allowed is 2 minutes. ### Reduce the number of queries and the amount of information displayed * Reduce the volume of data displayed to stay within the 2-minute limit * Limit the number of child objects included * Add filters to make the document lighter ### Convert your document to an Excel document Word technology has limitations when processing large volumes of data. Excel is a more efficient alternative, with better processing capacity and faster row insertion. --- # 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/gnx2209.md?ask=&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.