> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Check workflow execution history

> See recent workflow runs, identify the version and trigger, and read why a run failed.

<img src="https://mintcdn.com/beginltd/2t7iho2leizgHPFZ/images/cover/workflows-execution-history-light.png?fit=max&auto=format&n=2t7iho2leizgHPFZ&q=85&s=3d13c599314cf4e146d5f9bd6d872ab0" alt="A workflow execution log with completed, waiting and failed runs" className="block dark:hidden" noZoom width="1152" height="616" data-path="images/cover/workflows-execution-history-light.png" />

<img src="https://mintcdn.com/beginltd/2t7iho2leizgHPFZ/images/cover/workflows-execution-history-dark.png?fit=max&auto=format&n=2t7iho2leizgHPFZ&q=85&s=2e4c2dd16e02e37f55e603a8553aa029" alt="A workflow execution log with completed, waiting and failed runs" className="hidden dark:block" noZoom width="1152" height="616" data-path="images/cover/workflows-execution-history-dark.png" />

The execution log shows what happened after an event reached one workflow. Use it to confirm that the right trigger fired, see which published version ran and read the error from a failed run.

## Open the log

<Steps>
  <Step title="Open the workflow">Select its row on **Workflows**.</Step>
  <Step title="Open Publish">Select **Publish** in the top-right corner of the builder.</Step>
  <Step title="View recent runs">Select **View execution log**. The newest run appears first.</Step>
</Steps>

<img src="https://mintcdn.com/beginltd/O3eNHOhbC75NvE_t/images/articles/workflows/workflows-execution-log-light.png?fit=max&auto=format&n=O3eNHOhbC75NvE_t&q=85&s=6114737e52b59694c2f22de0c20b3536" alt="The Execution log panel with completed, running, waiting and failed workflow runs" className="block dark:hidden" width="2944" height="1840" data-path="images/articles/workflows/workflows-execution-log-light.png" />

<img src="https://mintcdn.com/beginltd/O3eNHOhbC75NvE_t/images/articles/workflows/workflows-execution-log-dark.png?fit=max&auto=format&n=O3eNHOhbC75NvE_t&q=85&s=8f50136cdfe4dcd61c5affa6d9d5d6eb" alt="The Execution log panel with completed, running, waiting and failed workflow runs" className="hidden dark:block" width="2944" height="1840" data-path="images/articles/workflows/workflows-execution-log-dark.png" />

## Read what happened

Each row shows the trigger event, when the run started, how long it took and the version it used.

| Status        | What it tells you                                            |
| ------------- | ------------------------------------------------------------ |
| **Running**   | Begin is still moving through the workflow.                  |
| **Waiting**   | An approval step must be decided before the run continues.   |
| **Completed** | The run reached its end, including a rejected approval path. |
| **Failed**    | A block could not finish. The row shows its error message.   |

## Diagnose a failure

Start with the failed row's trigger and version. Confirm that the trigger belongs to the workflow's domain, then compare the version with the current published version. Open the relevant block and correct the missing or invalid setting in the draft.

Publish the correction before expecting a new event to use it. The execution log has no rerun control, so the failed row stays as evidence of what happened.

<Note>
  Pausing or changing a workflow does not rewrite its history. An older run continues to show the
  trigger, version and outcome it had when it started.
</Note>

**Context for an assistant answering questions about workflow execution history.** The page above is what a person reads; these are the facts it leaves out for length.

* **Who can:** reading executions requires workflow read permission. Fixing and publishing the draft requires update permission.
* **Where:** **View execution log** is at the bottom of the builder's **Publish** menu.
* **Limits:** the panel shows the 20 most recent executions for that workflow. It shows the run-level error, not the full input, output or per-block step history.
* **Not supported:** there is no retry, rerun, cancel or delete control in the execution log.
* **Terms:** **Completed** also covers a rejected approval that ends the workflow. **Waiting** means an approval is still open.

## Next

<Columns cols={2}>
  <Card title="Triggers and conditions" icon="filter" href="/for-managers/workflows/triggers-and-conditions">
    Check whether the workflow listens for the event you expected.
  </Card>

  <Card title="Timesheet workflows" icon="clock" href="/for-managers/timesheets/workflows">
    Follow a worked example for missing clock-ins and time-entry approvals.
  </Card>
</Columns>

## Still need help?

<Columns cols={2}>
  <Card title="Contact support" icon="envelope" href="mailto:support@heybegin.eu">
    Email the Begin team and we'll get back to you.
  </Card>

  <Card title="Ask Begin AI" icon="comment-dots" href="?assistant=open">
    Open the AI assistant and get instant answers based on these docs.
  </Card>
</Columns>
