Wait points
A Wait point requires that all incoming paths must be complete before the playbook proceeds to the next step.
A simple use case is when the playbook calls for two or more tasks to complete before the playbook can end. Most likely, these user tasks are not completed at the same time.
Another use case is that you require both the results of a script and an app's function before you can process the results and proceed to the appropriate step. Here, you would connect the outputs of the function and the script to the inputs of a Wait point.
In the following graphic, a Wait point is used to make sure that users complete the two tasks before the playbook assigns the task of notifying legal counsel. Here, the users who are assigned the tasks might be in different time zones so that the tasks would not be completed at the same time.
Troubleshooting wait points
Sometimes, a wait point is passed when only one input into the wait point is complete. This scenario happens when a playbook is designed with two paths from the start node, and one of the paths branches into a third path, which is then reduced back to two paths. The following image shows an example of a playbook design that can trigger this improper handling of the wait point.
To avoid this issue, design the playbook to include a wait point each time that two paths merge.