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.
Upgrade or maintain warm standby instances
In order to perform system maintenance or to upgrade on a warm standby pair, warm standby must be disabled.
- Disable warm standby on the primary.
- Disable warm standby on the warm standby.
- Perform system maintenance or upgrade for both instances. See upgrade overview and prerequisites in Install and Upgrade .
- Create a warm standby pair. See Create a warm standby.
If you make any changes to warm standby using different flags, warm standby must be deactivated and then reconfigured on both the primary instance and the standby instance for the changes to take effect.
Last modified on 30 November, 2023
| Recreate warm standby after a failover | Manage warm standby features and options |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1, 5.3.1, 5.3.2
Download manual
Feedback submitted, thanks!