> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/dashboard/document-flow.md). # Document Flow **Document Flow** shows a document's processing steps. Numbered cards identify their order, status and duration. This example uses a fictional invoice. ## Find the document and open its flow Find the document in the dashboard first. The image shows the search for the synthetic example; document values in the table are hidden.

Find the synthetic example document in the English dashboard; document values are hidden.

Open the document in **Field Validation**. Open **More options** in the right-hand action bar and select **Document Flow**.

More options menu in English field validation with Document Flow available.

## Read the process cards Each card represents a step, such as **Imported**, **OCR**, **Classification** or **Field Extraction**. Follow the numbers and scroll to see later steps.

Process cards for a fictional invoice; technical status codes remain unchanged.

Technical identifiers and status codes such as `DOCUMENT_IMPORTED` and `COMPLETE` remain unchanged. `COMPLETE` identifies a completed step. ## Inspect a step Select a process card to inspect its details and available logs. | Detail | Meaning | | -------- | -------------------------------------- | | Module | Processing component used for the step | | Status | Current state of that step | | Duration | Recorded processing time | | Logs | Available technical task messages | For a waiting or failed step, inspect its messages before restarting processing. --- # 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.docbits.com/end-user-and-partner-section/end-user-section/dashboard/document-flow.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.