ID 161717 - Calling node.dependent() returns nothing the first time with groups or gizmos upstream

Problem summary
Calling node.dependent() returns nothing the first time with groups or gizmos upstream.
 

Customer reported version
nuke.13.1v2
 

Customer reported platform
centos7
 

Steps to reproduce

1) In Nuke, create a Constant node.

2) Create a TimeOffset node, and then a NoOp node.

3) Add a Dot node and then open the Script Editor.

4) Run the command: print(nuke.toNode("NoOp1").dependent(forceEvaluate=True))
 

Expected behavior
The NoOp node should evaluate and display the dependent node on the first attempt.
 

Actual behavior
The node does not evaluate on the first attempt and gives an empty list result.
 

Workaround
Running the command twice allows the node to be evaluated correctly.
 

Reproduced by Support in:
Nuke 13.2v2 - Windows 10, CentOS 7
Nuke 13.2v1 - Windows 10
Nuke 13.1v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10, CentOS 7
 

Earliest version tested
Nuke 9.0v1 - This issue appears to be in all versions of the product