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.

There are 2 ways to see the history of the workflows:

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. 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 with x icon:

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.

Example #

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 “details” 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 “Fell by condition” at the top of the block.
4. From the “Conditions” text box we can learn two things:
   • The condition was not met (=false)
   • The condition was that “statdes” would be equal to “מחכה לאישור” (“waiting for confirmation”)
     
5. In the text box of the “output” you can see that in practice the statdes in the incoming request was equal to “טיוטא” (“draft”).
   

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. Click on the ‘Workflows’ option on the sidebar.
   
   
2. Go to ‘History’
   Option 1:
   • Click on the name of the workflow you want to re-run.
     
     Option 2:
   1. Click on the 3 dots •••
   2. Click on ‘Details’
      
      
3. Choose which run you want to re-run in ‘History’ at the bottom of the page.
   1. Click on ‘Details’ for the log you want to re-run.
      
      
4. Click on the ‘Re- run’ button located on the right side of the top bar.