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:

Set the global action concurrency limit

The global action concurrency limit designates the maximum number of concurrent actions across all assets on the platform.

  • The default setting is 150 concurrent actions on the SOAR platform.
  • The Splunk Automation Broker has a limit of 50 concurrent actions per broker. Setting a higher limit of concurrent actions on the broker than on the platform does nothing.

When changing the global action limit, ensure the existing action limits set on all of your assets is still within the new global limit. Use caution when changing the global action limit as it can significantly affect performance.

To change the local concurrent action limit in , follow these steps.

  1. From the Home menu, select Administration.
  2. Click Administration Settings > Environment Settings.
  3. Enter your desired action limit in the box. Use caution when changing this limit because doing so can have a significant effect on performance.
  4. Click Save Changes.

To change the local concurrent action limit in the Automation Broker, follow these steps.

  1. Edit brokerd.conf by either:
    • navigating to your data directory on the Docker host operating system.
    • by logging into the Automation Broker container to edit the file in the /broker directory.
    See Change Splunk SOAR Automation Broker settings by editing brokerd.conf in Set Up and Manage the Splunk SOAR Automation Broker.
  2. Set the value for global_concurrency_limit to the desired value.
  3. Save and exit the file.
  4. Restart the Automation Broker. See Interact with the Splunk Automation Broker in Set Up and Manage the Splunk SOAR Automation Broker.

See also

Concurrent actions limits can be controlled at the app or connector level and on individual assets. You can also change the number of concurrent actions the Automation Broker allows by editing the brokerd.conf file on the Automation Broker container.

Last modified on 02 May, 2024
Set global environment variables   Add tags to objects in

This documentation applies to the following versions of Splunk® SOAR (On-premises): 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