> For the complete documentation index, see [llms.txt](https://docs.tagshelf.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tagshelf.dev/endpoints/file/file-status.md).

# File Status

The FileStatus entity in Alfred represents the current state of a file within the document processing workflow, indicating its progress from initiation to completion

In Alfred, each file progresses through a series of distinct statuses, reflecting key points in its lifecycle. These statuses are integral to understanding and effectively managing the flow of document processing tasks. They provide users with clear markers of a file's journey from upload to completion, highlighting critical moments such as processing, waiting for input, encountering issues, and successful resolution.

This documentation page offers a detailed overview of the File statuses in Alfred. By comprehending these statuses, users gain valuable insights into the current state and progress of each file. This understanding is crucial for efiicient monitoring, managing, and interacting with files in Alfred, ensuring a smooth and effective document processing experience.

<table data-full-width="true"><thead><tr><th width="95">Code</th><th width="363">Status</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td><code>uploaded</code></td><td>Indicates the file has been successfully uploaded to the system.</td></tr><tr><td>1</td><td><code>metadata</code></td><td>The file is currently in the process of Metada acquisition.</td></tr><tr><td>2</td><td><code>pre_processing</code></td><td>The file is currently undergoing its corresponding preprocessing pipeline</td></tr><tr><td>3</td><td><code>pre_processed</code></td><td>The file has succesfully completed the preprocessing pipeline.</td></tr><tr><td>4</td><td><code>decomposing</code></td><td>The file is being decomposed into separate elements.</td></tr><tr><td>5</td><td><code>decomposed</code></td><td>The decomposition of the file into manageable elements is complete.</td></tr><tr><td>6</td><td><code>ocr</code></td><td>The file is currently undergoing the extraction of information throught the Optical Character Recognition (OCR) processing.</td></tr><tr><td>7</td><td><code>transformed</code></td><td>The file has been transformed as needed for further processing.</td></tr><tr><td>8</td><td><code>classifying</code></td><td>The file is in the process of being classified into a Tag.</td></tr><tr><td>9</td><td><code>classified</code></td><td>The file has been succesfully completed the classification pipeline.</td></tr><tr><td>10</td><td><code>indexing</code></td><td>The file's components are currently being indexed.</td></tr><tr><td>11</td><td><code>indexed</code></td><td>The indexing process for the file has been succesfully completed.</td></tr><tr><td>12</td><td><code>extracting</code></td><td>The corresponding Data Points for the file are currently being extracted.</td></tr><tr><td>13</td><td><code>extracted</code></td><td>The Data Point extraction for the file has been completed.</td></tr><tr><td>14</td><td><code>confirmation_required</code></td><td>The file requires user confirmation for further processing.</td></tr><tr><td>15</td><td><code>confirmation_submitted</code></td><td>User confirmation for the file has been submitted.</td></tr><tr><td>16</td><td><code>confirmed</code></td><td>The file has been confirmed by the user.</td></tr><tr><td>17</td><td><code>finished</code></td><td>The file has completed its assigned pipeline.</td></tr><tr><td>18</td><td><code>re_tagged</code></td><td>The file has been retagged.</td></tr><tr><td>19</td><td><code>tag_removed</code></td><td>Tags associated with the file have been removed.</td></tr><tr><td>20</td><td><code>failed_classification</code></td><td>The file has failed the classification process.</td></tr><tr><td>21</td><td><code>deleted</code></td><td>The file has been deleted from the system.</td></tr><tr><td>22</td><td><code>duplicate</code></td><td>The file is marked as a duplicate of another file.</td></tr><tr><td>23</td><td><code>waiting_to_be_sent_to_third_party</code></td><td>The file is waiting to be sent to a third party.</td></tr><tr><td>24</td><td><code>sent_to_third_party</code></td><td>The file has been sent to a third party.</td></tr><tr><td>25</td><td><code>re_queued</code></td><td>The file has been re-queued for processing.</td></tr><tr><td>26</td><td><code>failed_extraction</code></td><td>The file has failed the data extraction process.</td></tr><tr><td>27</td><td><code>failed_to_send_to_third_party</code></td><td>Sending the file to a third party has failed.</td></tr><tr><td>28</td><td><code>failed_file_operation</code></td><td>A file operation has failed.</td></tr><tr><td>29</td><td><code>failed_transformation</code></td><td>The file transformation process has failed.</td></tr><tr><td>30</td><td><code>failed_job</code></td><td>The job associated with the file has failed.</td></tr><tr><td>31</td><td><code>canceled_job</code></td><td>The job associated with the file has been canceled.</td></tr></tbody></table>


---

# 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.tagshelf.dev/endpoints/file/file-status.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.