> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engini.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Workflow Run History
The Workflow Run History provides a comprehensive overview of your workflow execution history. This guide will help you understand how to effectively use the Workflow Run History to monitor, analyze, and optimize your workflow performance.
## Workflow History Tile
This tile shows everything related to workflow from the last 30 days including any editing done to the workflow. The tile includes the following:
### Executions
1. *Filters -* Allows you to filter the execution list based on specific criteria such as status or date. You can sort the workflows by clicking on the filter icon located on the right side of the relevant column and entering the data in the next window that opens:
The options to filter by are:
* *Status* – Filter by execution result (Success/Failed).
* *Created By* – Filter by the user who ran the workflow.
* *Created At* – Filter by execution start date/time.
* *Closed At* – Filter by execution end date/time.
* *Created Date Period -* Filter by execution from last selected days (Default - Last 7 days)
* *Duration* – Filter by run time length.
* *Context* – Filter by execution context/environment.
* *Activities Count* – Filter by number of executed steps.
2. *Executions Count* - Displays the total number of workflow runs shown according to the selected filters.
3. *Refresh Executions* - Refreshes the execution history list to display the latest status of workflow runs. This is useful when a workflow remains in the Running status for a long time, as its updated result, such as Success or Failure, may only appear after refreshing the list.
4. *Export Executions -* Enables downloading the execution history data.
5. *Status* - Indicates the result of the workflow run (e.g., Success or Failed). The status of the workflow. There are six types of statuses:
* *Worlflow Edited* – A status that appears when the workflow has been modified.
* *Fell By Condition* – A status that appears when the workflow run failed due to specific conditions.
* *Running* – A status that appears when the workflow is running.
* *Success* – A status that appears when the workflow ran successfully.
* *Turned on* - A status that appears when the user has turned on the workflow.
* *Turned off* - A status that appears when the user has turned off the workflow.
* *Stopped* – A status that appears when the user has stopped the workflow run.
* *Failure* - A status that appears when the workflow run failed.
6. *Start Date & Time -* Shows when the workflow execution started.
7. *End Date & Time -* Shows when the workflow execution finished.
8. *Executed By -* Displays the user who triggered or ran the workflow.
9. *Duration -* Shows how long the execution took to complete.
10. *Steps Count -* Indicates the number of steps that were executed during that workflow run.
11. *Context -* The context value represents the data that is explicitly defined in the Configure Context field of an action.
### Versions
Under this tab, you can see the history of workflow changes, including the date, time, and user who made each update.
Click the three dots next to a version:
A menu opens allowing you to either restore that version or export it.
* *Restore-* Restore the chosen workflow version to make it the active, current version in your editor workspace.
* *Export* - Export the chosen workflow version to download its configuration file. This allows you to keep a local backup or easily import it into another Engini account.
## Activity status options
### Activity failed
A failed activity is marked with an icon:
The following action after a failed action will always not be executed, unless defined otherwise.
### Why did the activity failed?
There are two possibilities in which the failure explanation will be displayed:
1. *Incoming response* – when the operation performed on an external application has failed, and the external application returns a response.
2. *Parse Definition -* When Engini has failed parsing the activity definitions. Usually happens when a you try to use a parameter which is out the current scope or there are typo’s in one of the fields definition.
### Activity wasn’t executed
A activity which wasn’t executed during the workflow run will be marked without any icon, like the rightmost action in yellow:
### Activity executed successfully
A activity which was successfully executed is marked with the following icon:
## Workflow status options
### Failure
There are two options in which the workflow run status will be “Failure”:
* If a activity within a workflow fails, the workflow status will be set to “failure”, unless one of the immediate following activities is configured to run after the failure of the previous activity in which the workflow run will continue.
In order to identify why the workflow failed, try to find the activity that has a warning icon on it:
* If a “Terminate workflow” activity was executed and the status defined in it was “Failure”.
Executing this activity will end the workflow run and the run status will be the status defined in this activity.
### Fell by condition
Two types of activities can define the workflow run status as “fell on condition”: a trigger or a “Terminate workflow” activity where you can set the status that will be received when the activity is executed ending the workflow run.
Let’s see an example and explore it.
1. Enter the “details” page in order to view the history table and select the requested run.
2. By clicking on the button you enter to view the running log.
3. In order to investigate the reason why the first activity was not executed, click on the activity name.
As you can see, there is a red note “Failed” at the top of the block.
### Success
If the workflow ran from start to finish successfully, the workflow will be defined as successful.
## Structure of a history run log inside a activity
### Raw definitions
The definitions of the fields, objects, filters and conditions are displayed in the structure they are saved as.
### Outgoing Request
If the activity is to performs an action on an external application the activity log will include the “Outgoing Request” block. This block displays the request sent to the external application.
The structure of the request can vary since each application manage it differently.
### Incoming Request
If the activity is a trigger that is receiving webhooks from external applications, the activity log will include the “Incoming Request” block.
This block displays the request body received from the external application.
### Incoming Response
The response that returned from the external application the activity performed an action on. Usually appears in action activities performed on external applications.
### Output
The output of the activity after it has been parsed by Engini.
Usually appears in triggers.
## Re-run option
The ‘Re-run’ button allows you to rerun a history run.
1. *Run -* Inside the workflow click on the run logo
2. *Run History* - click on "Run History"
3. *History -* From the run history, click on the specific entry you wish to rerun.
4. *Workflow run* - Within a specific run, you will find the 'Rerun' option at the bottom of the screen.
## History Page
The Workflow History page is your central command center for everything happening behind the scenes. It keeps a complete record of every process you run, making it easy to monitor live executions, audit past data, and stay on top of your automation's performance.
To view your workflow records, simply navigate to the main left-hand sidebar menu and click on History.
1. *Refresh*- Click the circular arrow icon to instantly update the list with the latest workflow runs and status changes without reloading the entire page.
2. *Download CSV* - Click this button to export your current filtered history view into a CSV file, making it easy to analyze or report your automation data externally.
3. *Checkbox* - Select individual or multiple workflows using the checkboxes next to each run to perform bulk actions like stopping or re-running processes simultaneously.
### Sort
Use the sorting options to organize the executions list according to the information you want to display first.
To change the sorting, click the relevant column name. Text-based fields can be sorted from *A – Z* or *Z – A*, while date-based fields can be sorted from oldest to newest or newest to oldest.
1. *Name -* Sorts the executions alphabetically by workflow name.
* *A – Z* – Displays workflow names in alphabetical order.
* *Z – A* – Displays workflow names in reverse alphabetical order.
2. *Created -* Sorts the executions according to the user who created them or the execution creation date.
* *A – Z* – Sorts alphabetically by the creator’s name.
* *Z – A* – Sorts in reverse alphabetical order by the creator’s name.
* *Oldest first* – Displays executions with the oldest creation date first.
* *Newest first* – Displays executions with the newest creation date first.
3. *Closed Date -* Sorts the executions according to the date and time they were completed.
* *Oldest first* – Displays executions with the oldest closed date first.
* *Newest first* – Displays executions with the newest closed date first.
4. *Context -* Sorts the executions according to their context value.
* *A – Z* – Displays context values in alphabetical order.
* *Z – A* – Displays context values in reverse alphabetical order.
5. *Status -* Sorts the executions according to their execution status, such as *Success* or *Failure*.
* *A – Z* – Displays statuses in alphabetical order.
* *Z – A* – Displays statuses in reverse alphabetical order.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.
1. *Filters -* Allows you to filter the execution list based on specific criteria such as status or date. You can sort the workflows by clicking on the filter icon located on the right side of the relevant column and entering the data in the next window that opens:
The options to filter by are:
* *Status* – Filter by execution result (Success/Failed).
* *Created By* – Filter by the user who ran the workflow.
* *Created At* – Filter by execution start date/time.
* *Closed At* – Filter by execution end date/time.
* *Created Date Period -* Filter by execution from last selected days (Default - Last 7 days)
* *Duration* – Filter by run time length.
* *Context* – Filter by execution context/environment.
* *Activities Count* – Filter by number of executed steps.
2. *Executions Count* - Displays the total number of workflow runs shown according to the selected filters.
3. *Refresh Executions* - Refreshes the execution history list to display the latest status of workflow runs. This is useful when a workflow remains in the Running status for a long time, as its updated result, such as Success or Failure, may only appear after refreshing the list.
4. *Export Executions -* Enables downloading the execution history data.
5. *Status* - Indicates the result of the workflow run (e.g., Success or Failed). The status of the workflow. There are six types of statuses:
* *Worlflow Edited* – A status that appears when the workflow has been modified.
* *Fell By Condition* – A status that appears when the workflow run failed due to specific conditions.
* *Running* – A status that appears when the workflow is running.
* *Success* – A status that appears when the workflow ran successfully.
* *Turned on* - A status that appears when the user has turned on the workflow.
* *Turned off* - A status that appears when the user has turned off the workflow.
* *Stopped* – A status that appears when the user has stopped the workflow run.
* *Failure* - A status that appears when the workflow run failed.
6. *Start Date & Time -* Shows when the workflow execution started.
7. *End Date & Time -* Shows when the workflow execution finished.
8. *Executed By -* Displays the user who triggered or ran the workflow.
9. *Duration -* Shows how long the execution took to complete.
10. *Steps Count -* Indicates the number of steps that were executed during that workflow run.
11. *Context -* The context value represents the data that is explicitly defined in the Configure Context field of an action.
### Versions
Under this tab, you can see the history of workflow changes, including the date, time, and user who made each update.
Click the three dots next to a version:
A menu opens allowing you to either restore that version or export it.
* *Restore-* Restore the chosen workflow version to make it the active, current version in your editor workspace.
* *Export* - Export the chosen workflow version to download its configuration file. This allows you to keep a local backup or easily import it into another Engini account.
## Activity status options
### Activity failed
A failed activity is marked with an icon:
The following action after a failed action will always not be executed, unless defined otherwise.
### Why did the activity failed?
There are two possibilities in which the failure explanation will be displayed:
1. *Incoming response* – when the operation performed on an external application has failed, and the external application returns a response.
2. *Parse Definition -* When Engini has failed parsing the activity definitions. Usually happens when a you try to use a parameter which is out the current scope or there are typo’s in one of the fields definition.
### Activity wasn’t executed
A activity which wasn’t executed during the workflow run will be marked without any icon, like the rightmost action in yellow:
### Activity executed successfully
A activity which was successfully executed is marked with the following icon:
## Workflow status options
### Failure
There are two options in which the workflow run status will be “Failure”:
* If a activity within a workflow fails, the workflow status will be set to “failure”, unless one of the immediate following activities is configured to run after the failure of the previous activity in which the workflow run will continue.
In order to identify why the workflow failed, try to find the activity that has a warning icon on it:
* If a “Terminate workflow” activity was executed and the status defined in it was “Failure”.
Executing this activity will end the workflow run and the run status will be the status defined in this activity.
### Fell by condition
Two types of activities can define the workflow run status as “fell on condition”: a trigger or a “Terminate workflow” activity where you can set the status that will be received when the activity is executed ending the workflow run.
Let’s see an example and explore it.
1. Enter the “details” page in order to view the history table and select the requested run.
2. By clicking on the button you enter to view the running log.
3. In order to investigate the reason why the first activity was not executed, click on the activity name.
As you can see, there is a red note “Failed” at the top of the block.
### Success
If the workflow ran from start to finish successfully, the workflow will be defined as successful.
## Structure of a history run log inside a activity
### Raw definitions
The definitions of the fields, objects, filters and conditions are displayed in the structure they are saved as.
### Outgoing Request
If the activity is to performs an action on an external application the activity log will include the “Outgoing Request” block. This block displays the request sent to the external application.
The structure of the request can vary since each application manage it differently.
### Incoming Request
If the activity is a trigger that is receiving webhooks from external applications, the activity log will include the “Incoming Request” block.
This block displays the request body received from the external application.
### Incoming Response
The response that returned from the external application the activity performed an action on. Usually appears in action activities performed on external applications.
### Output
The output of the activity after it has been parsed by Engini.
Usually appears in triggers.
## Re-run option
The ‘Re-run’ button allows you to rerun a history run.
1. *Run -* Inside the workflow click on the run logo
2. *Run History* - click on "Run History"
3. *History -* From the run history, click on the specific entry you wish to rerun.
4. *Workflow run* - Within a specific run, you will find the 'Rerun' option at the bottom of the screen.
## History Page
The Workflow History page is your central command center for everything happening behind the scenes. It keeps a complete record of every process you run, making it easy to monitor live executions, audit past data, and stay on top of your automation's performance.
To view your workflow records, simply navigate to the main left-hand sidebar menu and click on History.
1. *Refresh*- Click the circular arrow icon to instantly update the list with the latest workflow runs and status changes without reloading the entire page.
2. *Download CSV* - Click this button to export your current filtered history view into a CSV file, making it easy to analyze or report your automation data externally.
3. *Checkbox* - Select individual or multiple workflows using the checkboxes next to each run to perform bulk actions like stopping or re-running processes simultaneously.
### Sort
Use the sorting options to organize the executions list according to the information you want to display first.
To change the sorting, click the relevant column name. Text-based fields can be sorted from *A – Z* or *Z – A*, while date-based fields can be sorted from oldest to newest or newest to oldest.
1. *Name -* Sorts the executions alphabetically by workflow name.
* *A – Z* – Displays workflow names in alphabetical order.
* *Z – A* – Displays workflow names in reverse alphabetical order.
2. *Created -* Sorts the executions according to the user who created them or the execution creation date.
* *A – Z* – Sorts alphabetically by the creator’s name.
* *Z – A* – Sorts in reverse alphabetical order by the creator’s name.
* *Oldest first* – Displays executions with the oldest creation date first.
* *Newest first* – Displays executions with the newest creation date first.
3. *Closed Date -* Sorts the executions according to the date and time they were completed.
* *Oldest first* – Displays executions with the oldest closed date first.
* *Newest first* – Displays executions with the newest closed date first.
4. *Context -* Sorts the executions according to their context value.
* *A – Z* – Displays context values in alphabetical order.
* *Z – A* – Displays context values in reverse alphabetical order.
5. *Status -* Sorts the executions according to their execution status, such as *Success* or *Failure*.
* *A – Z* – Displays statuses in alphabetical order.
* *Z – A* – Displays statuses in reverse alphabetical order.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.