> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/workflow/workflow-execution-detail.md).

# Workflow Execution Detail

The Workflow Execution History Detail module is designed to provide users with comprehensive insights into the execution of workflows within the system. This module is essential for tracking the progress, status, and outcomes of workflows, allowing users to monitor their performance and troubleshoot any issues that may arise during execution.

{% hint style="info" %}
To access the Workflow Execution History Detail module, go to **Menu > Admin > Workflow > Workflow Execution Detail**
{% endhint %}

### Selecting the Workflow

The first step in leveraging the "Workflow Execution History Detail" module is to select the specific workflow for which you want to view the execution details. The "Select Workflow" dropdown option presents a list of available workflows in the system. Select the workflow for which you want to view the execution details. 

By default, the "All" option is selected, allowing you to view the execution details of all workflows in the system. Once you select a specific workflow, the details are loaded in the section below.

### Workflow Execution History Detail

The Workflow Execution History Detail section is the core component of this module, providing a comprehensive overview of the workflow execution history. This section displays all the relevant details related to the workflow execution, including workflow name, workflow step, workflow status, and message.

#### Workflow Execution History Detail Fields

<table><thead><tr><th width="200">Field</th><th>Description</th></tr></thead><tbody><tr><td>Workflow</td><td>This field displays the name of the workflow.</td></tr><tr><td>Workflow Step</td><td>Each workflow is comprised of a series of steps. This field details the specific step of the workflow in the execution history.</td></tr><tr><td>Workflow Step Type</td><td>This field indicates the type of workflow step, providing additional context for the execution details.</td></tr><tr><td>Status</td><td>This field indicates the status of the workflow step, indicating whether it was successful or it encountered an error.</td></tr><tr><td>Execution Dttm</td><td>This field shows the exact date and time when the workflow step was executed.</td></tr><tr><td>Message</td><td>This field contains the messages or logs associated with the execution of the workflow step, often used for troubleshooting or providing additional context.</td></tr></tbody></table>

### Workflow Execution History Detail  Filter <a href="#centrepageheading" id="centrepageheading"></a>

* **Select Status:** This option allows you to select the status of the workflow execution for which you want to view the results.

### Header Level Icons

* **Refresh:** This functionality empowers users to refresh search results based on selected criteria, ensuring that the displayed information is always up-to-date.
* **Save:** Save feature enables users to preserve any updated user interface (UI) settings, ensuring a personalized and consistent experience during future interactions with the module.
* **Columns:** All the columns available for the module are listed under this icon. You can use this option to hide or add the columns and tailor the module view as per your requirements.&#x20;
* **Download:** This versatile feature allows users to export and download data in various file formats, providing a summarized overview for quick reference. Options include CSV, TXT, MS-Word, MS-Excel, PDF, and MS-Excel(.xlsx), catering to diverse user preferences and use cases.


---

# 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://docs.xorosoft.com/xoroerp-1/admin/workflow/workflow-execution-detail.md?ask=<question>&goal=<endgoal>
```

`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.