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?
Abel
10 months agoMable
10 months agoVincent
10 months agoAbel
10 months agoDawne
10 months agoOren
10 months agoSherill
11 months agoAlecia
11 months agoOren
12 months agoNikita
1 years agoNohemi
12 months agoCherry
12 months agoCristy
12 months agoMarguerita
1 years agoLorrine
1 years agoLarae
1 years ago