> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/workflows/see-workflow-run-history.md). # See workflow run history Every time a published workflow runs — whether it was triggered automatically, run by hand, or is still waiting on something — Essential records it in the **Run history** table. Use it to answer "what have my workflows actually done, and for whom?" without waiting for something to go wrong. > **Where to find it:** Open **Automations**, then select **Workflows**, once Workflows is enabled for your business. The **Run history** table sits at the bottom of the page and shows the most recent runs, newest first. ## What a row tells you * **Workflow** — the workflow that ran, and beneath it the specific step. Steps driven by AI carry an **AI-driven** badge. * **Customer** — the customer the run acted on, when there is one. * **Trigger** — the raw name of the event that set the run off (for example, `customer.created`), not a plain-language phrase. * **Status** — where the run stands. See the list below. * **Result** — the run's own summary of what it did, when the step produces one. * **Started** — when the run began. Sort any column by selecting its header. ## Statuses * **Running** — the run is in progress right now. * **Waiting for approval** — the run paused before doing anything and is waiting for a person to approve it from the Tasks page. Nothing happens until someone decides. * **Completed** — the run finished and its actions succeeded. * **Nothing to do** — the run finished, and the workflow correctly decided no action was needed for this customer. This is normal, not a problem. * **Failed** — something went wrong. The run also appears in the **Needs attention** list with a diagnosis and one-click actions — see [Fix a failed workflow](/field-operations/workflows/fix-a-failed-workflow.md). * **Blocked** — a safety guardrail or policy stopped the run (for example, a spend budget was reached or an approval was declined). The system protected you; nothing was done. Test runs made while building a workflow are previews, not real activity, so they don't appear here. --- # 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://learn.withessential.com/field-operations/workflows/see-workflow-run-history.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.