A user has written a playbook that calls three other playbooks, one after the other. The user notices that the second playbook starts executing before the first one completes. What is the cause of this behavior?
I was thinking it might be A. If synchronous execution isn't configured, the playbooks could run in parallel, causing the second one to start before the first finishes.
Hmm, I'm pretty sure the answer is D. The join configuration on the second playbook is likely not set up correctly to wait for the first one to complete.
Ruth
16 hours agoEllen
16 days agoReta
14 hours agoBuddy
20 days agoMozelle
21 days agoKayleigh
26 days ago