Protocol

Protocols show up when a workflow is executed. They can be viewed separately for every workflow under Bildschirmfoto_2020-10-27_um_15.42.05.png in the workflow overview. The workflow log has pagination, which prevents long loading times for large logs with several thousand workstep entries. With a click on the Bildschirmfoto_2020-10-27_um_15.42.27.pngprotocol icon, the overview will open:

Bildschirmfoto_2020-10-27_um_15.43.06.png

On the left hand side under «Execution number», you can see the number of executions of each workflow, the date, time, duration, and the end result of the execution. The execution can be filtered by date and time as well as by end result.

The workflow result indicates if the workflow was performed correctly or not. To receive more information about a specific execution, click on a specific row. You’ll get to this overview: 

Bildschirmfoto_2020-10-27_um_15.47.03.png

Here, you can view the specific worksteps, the result and the duration of the process. For more information about an individual workstep, click on one of them:

Bildschirmfoto_2020-10-27_um_15.48.13.png

This is how you gain insights on the inputs and outputs of an individual workstep.

 

With the protocol icon Bildschirmfoto_2020-10-27_um_15.42.27.pngyou can switch directly to the respective protocol in the workflow listing. With a click on the name of the workflow you can go back to the workflow effortlessly. 

So the events are defined as follows:

ok
During the execution of the workflow everything went without errors.
warning
The execution of the workflow was faulty, but the workflow could still run or was continued.
error
The workflow could not be continued due to an error.
time-out
If a workflow is not finished after 60 seconds, this is logged as a time-out.

Hint:
While viewing a workflow log entry, it is possible to navigate to the next or previous workflow execution.

Likewise, a specific workflow execution can be restarted. This can be done from within the workflow log. A re-execution can only be started if the original data that triggered the workflow is still available.

Was this article helpful?
0 out of 0 found this helpful