Skip to main content

Orchestrate Next Gen

Rerun Playbooks from Run Logs

Before you Start

Ensure that you have the Run Playbooks and View Run Logs permission.

Rerun entire Playbook

You can rerun a playbook from the run logs page when a playbook encounters an error or if you want to rerun it from the start node.

Steps

To rerun a playbook, follow these steps.

  1. Navigate to Main Menu > Run Logs.

  2. Find the run log for the playbook you want to rerun and click the Ellipses icon.

  3. Select Run to rerun the playbooks or select Run with Input to provide input for the playbook execution and click Run Playbook. A new run log is generated, and the playbook begins to execute.

  4. Click the Refresh icon to view the real-time execution logs of the playbook.

Rerun Playbook from a Node

You can rerun a playbook from a specific node to recover from errors in playbook execution without running the entire playbook. This method utilizes data from nodes that ran successfully and resumes the playbook execution from the node where the error occurred.

You can rerun playbook execution when the playbook encounters an error, or system error, or achieves partial success during the initial run.

Steps

To rerun the execution of a playbook, follow these steps:

  1. Go to Main Menu > Playbooks > Run Logs.

  2. Select the run log of the playbook with an Error, System Error, or Partial Success status that you want to rerun from the list.

  3. Hover on the node from which you want to rerun the playbook execution and click Run from this node. This creates a new run log and navigates you to the new run log page to rerun the playbook execution. The new run log automatically references and reuses data from the old run log.

    When you perform a rerun from a node, all the data from the previous nodes that were successfully executed will be reused. For example, if you click Rerun from this node on the third node of a four-node playbook, the data from nodes one and two will be reused to resume the playbook execution from the third node.

  4. Click the Refresh icon to preview the playbook execution. The new run log shows the reused data from the previous run log. You can view the input and output data from the previously executed nodes.

You can manually execute a playbook using a reused run log as input. However, the run log does not include the original playbook input data as the start node is not referenced. To learn more, see Run a Playbook Manually.

Note

The Rerun from this node button will be disabled for nodes that are deleted in the latest playbook version.

Limitations

In the following cases, a playbook cannot be rerun from a specific node:

  • Node Removal: You cannot rerun a playbook from a specific node if the node from which you intend to rerun the playbook has been deleted or removed from the playbook. The rerun activity cannot be performed.

  • Start Node: You cannot rerun a playbook from the start node of the playbook.

  • Playbook Status: You cannot rerun a playbook from a node if the playbook status is Waiting, On-Hold, In-Queue, Terminated, or In-Progress.

  • Execution Not Started: A playbook cannot be rerun from a node if it has not started execution and has no status information.