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 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 executions count displays the total number of workflow runs shown according to the selected filters export executions enables downloading the execution history data 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 start date & time shows when the workflow execution started end date & time shows when the workflow execution finished executed by displays the user who triggered or ran the workflow duration shows how long the execution took to complete steps count indicates the number of steps that were executed during that workflow run 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 incoming response – when the operation performed on an external application has failed, and the external application returns a response 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 enter the “details” page in order to view the history table and select the requested run by clicking on the button you enter to view the running log 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 run inside the workflow click on the run logo run history click on "run history" history from the run history, click on the specific entry you wish to rerun 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 refresh click the circular arrow icon to instantly update the list with the latest workflow runs and status changes without reloading the entire page 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 checkbox select individual or multiple workflows using the checkboxes next to each run to perform bulk actions like stopping or re running processes simultaneously