> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/help/troubleshooting/workflow-statuses.md).

# Workflow statuses

DoControl indicates these status types for executed workflows:

<table><thead><tr><th width="188">Workflow progress</th><th>Description</th></tr></thead><tbody><tr><td>Completed</td><td>The workflow was completed successfully.</td></tr><tr><td>In progress</td><td><p>The execution is still running, or is waiting for an action to take place, such as:</p><ul><li>Timeout in the <strong>Wait</strong> action</li><li>Approval from the user in the <strong>Approve</strong> action</li></ul></td></tr><tr><td>Warning</td><td><p>An industry standard status, Warning informs users when something did not complete as usual, but is not business critical and doesn’t require immediate attention.<br>The workflow execution didn’t fail but couldn’t be fully completed due to a non-urgent issue, such as:</p><ul><li><strong>File not found</strong> - 30 days passed since a file was created and it was since removed. </li><li><strong>Collaborator not found</strong> - 30 days passed since a file was shared, and it's no longer shared with a collaborator. Or public sharing was removed from a file that was not public.</li><li><strong>File not supported</strong> - Video file that could not be scanned for PII or regex.</li></ul></td></tr><tr><td>Failed/Canceled</td><td><p>The workflow was canceled or failed to execute, for example due to these reasons:</p><ul><li>Insufficient permissions to execute this action</li><li>Something went wrong in workflow execution</li><li>An internal error</li></ul></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.docontrol.io/docontrol-user-guide/help/troubleshooting/workflow-statuses.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.