- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
05-30-2022 02:34 AM
Can you talk about how workers traverse a playbook and sub-playbooks?
** Note: this is a question from our Customer Success Webinar: Playbook optimization in Cortex XSOAR
05-30-2022 02:37 AM - edited 05-31-2022 10:14 AM
Reply by @RahulVijaydev
Workers are assigned to each automated task from a worker pool as they execute. The worker pool consists of (number of CPU cores X 16) workers for ex. 64 workers in a 4 core machine. When an automated task has to execute, it picks a worker from the pool, keeps it for the entire duration of the operation, and releases it back to the pool upon execution. When all the workers have been consumed, and the worker pool is exhausted, tasks wait until a worker is released. NOTE: Be careful while implementing parallel branches in a playbook, as too many branches can lead to workers getting tied up.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!