@TanyaS58

A Wait step with case dependency pauses the flow and registers a dependency record on the case, so the platform watches the target case’s status for you. When that case hits the status you configured, the engine wakes the waiting flow automatically and moves to the next step, no manual check needed. The next assignment is then created and routed per your routing rule, so to inform the next user, turn on assignment notifications on that step or add an email notification to the routing. To avoid indefinite waiting, set a timeout on the Wait step and add an alternate path that creates an assignment or alerts a supervisor if the dependency isn’t met in time. You can also attach a service level to the Wait step and use goal or deadline actions to send reminders while it’s waiting. If you need visibility, show the dependent case ID and its current status on the parent case view so users can see what it’s waiting on. For non-child dependencies, reference the specific case IDs in the Wait step so the same resume logic applies. A simple pattern that works well: Wait step with case dependency + timeout path, then a normal assignment step with Notify assignee enabled.