Workflow Debug

When a workflow is executed, it doesn't always work as planned. The workflow debug is there to let you see a rundown of the execution and spot any errors that may have occurred.

To open the workflow debug, select the workflow you wish to debug, and on the left panel, switch to the debug tab from the activities tab.

Each execution will have an ID, completion status, execution time and execution duration, as seen below:

Where Blue means the execution is In progress, red means the execution failed, green means the execution succeeded, and amber means the execution succeeded with warnings.

Clicking on an execution will open it and show you information regarding each of the activities triggered in the execution.

Using the Activity Debug

In this example we will look at the debug for a simple workflow that receives user info and sends a heed to the given User.

Once the workflow is created, and triggered, go to the debug.

1. Select the execution you wish to debug
   
   
   
2. Now we can see the list of activities that the workflow tried to execute, and there status, with the same colour coding as the overall workflow execution. Select the activity whose output you would like to debug:
   
   
   
3. Here we can see the start and finish time of the individual activity, the duration, the configuration and the output.
   
   
   We can clearly see from the Error section, that the script was expecting a username field, and didnt receive it. This is the script:
   
   
   From here we can see no errors in the script itself, but we can see that it is using the output of the webhook activity, and is expecting to find a single user object => body.user
   
   
4. Back in the list of Activities, selecting the webhook activity and opening the output, we see the following:
   
   
   In the output here we can see the body; where the script was expecting a user object, there is instead a users array.
   
   
5. Using this debug allows us to spot the error, identify the cause, and modify the workflow accordingly, all with relative ease.
   After editing the script accordingly, here is the debug for the following execution: