As of version 6.4.0, the visual editor for classic playbooks is no longer part of Splunk SOAR. Before upgrading, convert your classic playbooks to modern mode. Your classic playbooks will continue to run and you can view and edit them in the SOAR Python code editor.
For details, see:
For details, see:
This documentation does not apply to the most recent version of Splunk® SOAR (On-premises).
For documentation on the most recent version, go to the latest release.
Fixed issues for
Release 6.2.2
Splunk SOAR version 6.2.2 includes fixes for the following issues.
| Date resolved | Issue number | Description |
|---|---|---|
| 2024-06-04 | PSAAS-12158 | User filtering is using first/last name to filter events instead of just username |
| 2024-05-28 | PSAAS-17857 | Update from source control failing due to playbook name with square braket and colon in its name |
| 2024-05-28 | PSAAS-17788 | "Failed to create indicator" error because indicator length is too long |
| 2024-05-28 | PSAAS-17799 | Automation Broker ver 6.2.2 container status shows unhealthy state |
| 2024-05-13 | PSAAS-17655 | Memory leak in handling of custom function results |
| 2024-05-08 | PSAAS-17560 | Playbook converter cannot convert playbooks with set_owner or add_note |
| 2024-05-06 | PSAAS-17559 | "0: command not found" error is printed to the console when running start_phantom.sh |
| 2024-04-08 | PSAAS-14125 | Users without the "Administrator" role cannot delete an Automation Broker, even when given appropriate permissions. |
| 2024-03-04 | PSAAS-14130, PSAAS-14128 | Cluster node creation/upgrade may fail due to RabbitMQ CLI commands failing to connect to RabbitMQ server |
Last modified on 04 June, 2024
| Known issues for | Compatibility with related Splunk products |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 6.2.2
Download manual
Feedback submitted, thanks!