In Playbooks, dot walking on the "wait for condition" will cause slowness that will not allow next step to not load as expectedIssue In Playbooks, dot walking on the "wait for condition" will cause slowness that will cause the next step to not load as expected. It takes a long time to load the next step and sometimes it does not load at all. It was seen that reloading the browser makes it go to the next step.CauseDot walking on "wait for condition". The record watcher does not support dot walking.ResolutionThis is expected. From SN document: https://docs.servicenow.com/bundle/utah-build-workflows/page/administer/flow-designer/reference/wait-for-condition-flow-designer.html Restrict wait conditions to fields present on the current tableThe Wait For Condition action can only monitor changes to the fields of the table to which the record belongs. The action cannot detect changes to fields in related records or catalog variables. For example, if an action waits for changes to an Incident record, then it cannot detect changes to a related record such as a catalog item or change task record. Avoid building wait conditions that dot-walk to another record as these fields actually belong to the related record. Avoid building wait conditions that rely on catalog variables. As a workaround, you can check the dot walk condition in an "if" condition before calling "wait for condition" action and remove the dot walk from the "wait for condition". To add this feature you will have to submit this enhancement request using our idea portal as per the following kb guidelines KB0755878