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