> 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/gnx1201.md). # GNX1201 – Elements in a Word document split across two pages Error code 1201 (GNX1201). Elements of a generated Word document (paragraphs, table rows) split across two pages because Keep with next is not enabled. **Error code:** `GNX1201` ## Error description After a document is generated, its elements (paragraph, table row…) split across two pages. How do you keep elements together? ## Solutions ### "Keep with next" feature not enabled * Enable the Word feature: select the parts to keep together, right-click > Paragraph… (or Option + Command + M) > Line and Page Breaks > check Keep with next and Keep lines together, then apply * Check that Keep with next is enabled by showing formatting marks. A black square should appear in front of the lines and paragraphs kept together ### Keeping a whole page together * The feature should be applied to table rows or relatively short paragraphs. Several full pages cannot be kept together. Select smaller areas instead ## Limitations * The feature is not available in Word Online, Excel, PowerPoint or PDF. * This option should be limited to a few paragraphs: applied to your whole document, it can create many blank spaces. See the Word pagination control features described in the following article: --- # 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/gnx1201.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.