> 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/sign/en/advanced-features/interactions-and-fields/data-update-statuses.md). # Understand the data update statuses Updated \[Auto]: This status indicates that the value entered by the signer when signing the document was automatically inserted into the designated field of the designated object. * **Updated \[Auto]**: This status indicates that the value entered by the signer when signing the document was automatically inserted into the designated field of the designated object, as soon as the document was signed * **Updated \[Manual]**: This status indicates that the value entered by the signer when signing the document was accepted by the user and therefore inserted into the designated field of the designated object * **Archived**: This status indicates that the value entered by the signer when signing the document was not accepted by the user but has been processed * **Pending**: This status can indicate two different cases. Either the signer has not yet signed the document, or the value entered when signing has not yet been processed * **Error**: This status indicates that an error occurred while updating the designated field of the designated object with the value entered by the signer. In this case, a help text shows the error that occurred --- # 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/sign/en/advanced-features/interactions-and-fields/data-update-statuses.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.