> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/estados-de-los-ficheros.md). # File statuses In the same way that the application always has an associated status that depends on the signatures made on its files, the files also have their own. They are shown below: | **Status** | **Description** | | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **0 – Unsigned file** | This file has not been signed by that user. | | **1 – File signed correctly** | The user has signed the file. | | **2 – Invalid signature** | The file signature is invalid. Possible modification of the data file or signature after it was created. | | **3 – Cannot sign: order (signature level)** | The user cannot sign due to the signature order; there are other users who must sign before they can sign. | | **4 – Cannot sign: max. signatures** | The user cannot sign because the file has already reached the maximum number of signatures per file (number of signatures allowed). | | **5 – Can sign** | The user can sign the file. | | **6 – Encrypted and/or compressed file** | The file is encrypted and/or compressed; until it is decrypted and/or decompressed, the signature cannot be validated. | | **7 – Cannot sign: sending enabled** | The user cannot sign because the application is enabled for sending. | | **8 – Cannot sign: joint** | In applications with joint validation, none of the conditions the user is in can ever be met; the user cannot sign that file. | | **9 – File with sufficient signatures** | In applications with joint validation, the file already meets at least one of the joint conditions. | | **Status** | **Description** | | **10 - File is not from the standard associated with the application** | The file could not be validated/viewed using the standard associated with the application. | | **11 - The file status could not be checked (XAdES)** | In applications with XAdES signature mode, the signature associated with a file exists but could not be verified because the XAdES server is not running or not properly configured. | | **12 - Cannot sign: maximum allowed amount exceeded** | The file has a total amount greater than the maximum allowed for the user in the application-user relationship profile. | --- # 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://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/estados-de-los-ficheros.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.