Haha, yeah, that's a good point. FortiAnalyzer probably needs to make sure it has a clear runway before it can start executing your new playbook. Wouldn't want any mid-air collisions, would we?
That makes sense. But I'm also wondering if it could be to ensure that no other playbooks are running. We wouldn't want to disrupt any ongoing processes, right?
I agree, option C does seem the most plausible. And it's probably a good practice to give FortiAnalyzer a bit of time to do its thing before we start running our new playbook. Don't want any unexpected surprises, right?
Nikita
11 days agoMarguerita
12 days agoLorrine
13 days agoLarae
14 days ago