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:
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:
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!