Cyware Orchestrate

Run Log ID: A 12-digit unique ID to identify a run log. For example, RL6e5daa85-0

Playbook and Node Run Status: The run status of a Playbook and Playbook node. For more information on the run statuses, see Playbook Run Status

Run By: The user, scheduler, Playbook, or event that has run the Playbook. For example, John Doe

Run Time: The run time of the Playbook in seconds.

Run On: The date and time of the Playbook run. For example, Jan 16, 2023 03:28 PM

Sub-Playbooks Run Logs: Click the run logs count to navigate to the run logs of the sub-playbooks.

Node Input and Output Values: Click I/O and select a node to view the node input and output values. The input and output preview displays data up to 4 MB. You can click More > Download to download the complete data up to 64 MB for offline analysis.

Node Run Time: Displays the run time of each Playbook node in seconds to analyze and optimize node performance. This also helps in identifying nodes that are taking additional time to execute and potentially causing delays in the Playbook's performance.

Run Log Details Screen: You can navigate to the required run log and click the count of Sub-playbooks Run Logs available on the right side of the screen. 

The associated sub-playbooks count is not displayed in the following scenarios:

Sub-playbook Node: To view the sub-playbook run logs, do the following:

Success: Displays Success status if the Playbook has successfully performed the defined actions and produced the output.

Partial Success: Displays PartialSuccess status if the user has not configured Abort Playbook if this Action Fails for any of the Playbook nodes, and the Playbook execution has interrupted in an intermediate node. To rerun a Playbook from Run Logs, see Rerun Playbooks from Run Logs.

Error: Displays Error status if the Playbook has failed to execute the configured workflow. This condition occurs when the nodes cannot exchange the configured input or output data. To rerun a Playbook from Run Logs, see Rerun Playbooks from Run Logs.

On Hold: Displays On Hold status if the Playbook is waiting for the user to manually input data. This condition occurs only for Playbooks configured with manual input actions.

Waiting: Displays Waiting status if a particular node is yet to complete execution despite the completion of the Playbook workflow. This condition occurs when a node is configured to Run Asynchronously independent of the Playbook workflow. For example, Sub-Playbooks can be configured in the node of a parent Playbook to run asynchronously.

In Progress: Displays In Progress status if the Playbook workflow is in progress and yet to be completed.

System Error: Displays SystemError status if the Playbook workflow could not execute due to failure of multiple functions in the defined workflow. To rerun a Playbook from Run Logs, see Rerun Playbooks from Run Logs.

Terminated: Displays Terminated status if the Playbook workflow is manually terminated or stopped while execution. A terminated Playbook will skip the remaining nodes in the Playbook workflow and stop the execution.

In Queue: Displays In Queue status if the Playbook is waiting for other tasks to be completed. Once the preceding tasks are completed the Playbook status will change to In Progress status.

You can sort the run logs based on Playbooks latest execution time, run activity, and run duration.

You can filter and view specific run logs as per your requirement. You can also save the filter and reuse it by clicking Save Filter.

You can clear out the applied filters by clicking the cross icon or Clear All in the Filters view.

You can use the following filters to view specific run logs: