Splunk® SOAR (On-premises)

Administer Splunk SOAR (On-premises)

The classic playbook editor will be deprecated soon. Convert your classic playbooks to modern mode.
After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:

View the playbook run history in

You can view the history of playbook runs on your instance.

  1. From the Home menu, select Administration.
  2. Select System Health > Playbook Run History.

The Playbook Run History page displays a sortable table of playbook runs. Each column except for Git Commit is sortable. The table displays the following columns:

Column title Description
Name The name of the playbook that was run.
Run ID The numeric ID of the Playbook Run.
Event ID The numeric ID of the event the playbook was run against.
Label The label the playbook was run against, such as event.
Start Time The time the playbook was started.
End Time The time the playbook run finished.
Status Whether the playbook run succeeded or failed.
Git Commit The Git commit ID from when the playbook version was committed to the included Git source control module.
Run By The name of the user who ran the playbook.
Last modified on 31 January, 2023
Locate long-running playbooks for debugging or troubleshooting in   View Playbook Run Statistics

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.3.3, 5.3.4, 5.3.5, 5.3.6, 5.4.0, 5.5.0, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.2.1, 6.2.2

Was this topic useful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters