The classic playbook editor will be deprecated in early 2025. 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:
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 5.3.2
| Date resolved | Issue number | Description |
|---|---|---|
| 2022-06-10 | PSAAS-9141 | Cluster upgrades to 5.3.1 can fail any node when running intialize.py, in populate_users_and_hec_token |
| 2022-05-11 | PSAAS-7633 | C++ log truncation can result in bad json for very long messages |
| 2022-05-11 | PSAAS-8617 | Ingestion failures |
| 2022-05-11 | PSAAS-8830 | Excessive DB usage during asset or ingestion settings updates. |
| 2022-04-04 | PSAAS-6653 | VPE 2: Under certain circumstances, playbook editor will display blank screen |
Last modified on 30 September, 2022
| Known issues for | Compatibility with related Splunk products |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.3.2
Download manual
Feedback submitted, thanks!