> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/workflow/workflow-execution-history.md).
# View run history
This article explains the workflow run history screen. It covers reviewing the run list, reviewing the details of each run, and accessing artifacts. For how to stop, resume, and review a run, see [Run a workflow](/workflow/workflow-execution.md).
## Reviewing the run history list
This section explains how to access the workflow run history list and how to read each column.
### Accessing the Runs tab
1. Open the workspace page.
2. Select the **Workflows** tab at the top.
3. Click the **Runs** tab.
Run history list
### Reading the list
The run history list shows the following columns.
| Column | Description |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Workflow name. Runs started as a preview from the workflow builder are marked with a "Preview" badge. |
| Overall progress | Shows the number of completed blocks out of the total as a progress bar. |
| Started | Timestamp when the run was created. |
| Status | Current run state. For details on each status, see [Run a workflow](/workflow/workflow-execution.md). |
| Artifacts | The number of artifacts generated by the run. For **Review pending** runs, this column also shows **Review artifact** so you can open the waiting output. |
In the **Status** column, **Review pending** runs use a warning icon instead of the running spinner, so you can tell they are waiting for human action.
### Searching and refreshing runs
* Type a workflow name into the search field (**Search runs...**) at the top of the screen to filter the list in real time.
* To refresh the list manually, click the refresh icon to the right of the search field.
### Loading more
The list shows the first 50 runs. When there are more than 50, **Load more runs** appears at the bottom of the list. Click it to load the next 50 runs.
## Reviewing run details
This section explains how to open the run details screen and what information you can review on it.
### Opening the details screen
Click a row in the run history list to navigate to the details screen for that run.
Run details screen
### Reviewing the execution header
At the top of the details screen, **Triggered by** shows who started the run. Manual runs display the user's name. API-triggered and GitHub-triggered runs display the trigger type when a user name is not available.
When the run uses an older saved version of the workflow, the header also shows **Workflow version** with the version number and the time that version was saved.
### Reviewing the graph view
The graph view on the left shows the blocks that make up the workflow as nodes. Each block is colored according to its status. Click a block to show its details in the side panel on the right.
### Reviewing the side panel
The side panel shows the following information from top to bottom.
**Past executions**
A dropdown lets you select past runs of the same workflow. Switching runs lets you compare results.
**Overall progress**
Shows the number of completed blocks out of the total as a progress bar.
**Block details**
Shows information about the block selected in the graph view.
* **Run time**: Start time → end time and duration.
* **Inputs**: Input values to the block.
* **Output**: Output value of the block (text, structured data, or other formats).
* **Condition result / Reasoning**: For Conditional blocks, the condition result (true or false). When the AI evaluates the condition, the "Reasoning" section also shows the AI's rationale.
* **View execution result**: For a Workflow Call block, a link to the execution details of the child workflow.
* Error message (if the block failed).
## Reviewing artifacts
When artifacts are generated by a run, the count appears in the **Artifacts** column of the list. For runs in **Review pending**, the same column also shows **Review artifact**, which opens the execution details so you can review the waiting output.
1. Click the count in the **Artifacts** column.
2. A popup shows the list of generated artifacts.
3. Click an artifact name to open its content in a new tab.
## Troubleshooting
### Failure to load run history
| Situation | Cause | Resolution |
| -------------------------------------------------- | ------------------------------------------------ | -------------------------------------------------------- |
| The run history list does not load | Network or server error | Reload the page. If the issue persists, contact support. |
| An error message appears on the run details screen | The run ID is invalid, or you do not have access | Verify the URL. If the issue persists, contact support. |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.genesis.autify.com/workflow/workflow-execution-history.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.