ID 476517 - The [value frame] expression gives incorrect data when upstream of the ContactSheet node.

Problem summary
The [value frame] expression gives incorrect data when upstream of the ContactSheet node.

Customer reported version
nuke.13.0v2

Customer reported platform
windows10

Steps to reproduce

1) In Nuke, create a Text node, and add the command [value frame]​ in the message knob.

2) Add a ContactSheet downstream, and enable the "use frames instead of inputs" knob.

3) In the ContactSheet node, set the frame range for 1 to 10, and view the node. 

Expected behavior
The [value frame] expression should display the correct current frame in each area of the ContactSheet node.

Actual behavior
Only the initial frame of the upstream Text node is appearing in the ContactSheet node. Adding a FrameHold node upstream of the ContactSheet node can modify the initial frame range, so if setting to 1005, it will display 1005 for each frame in the sheet.

Workaround
Using the command [frame], [expression frame] or [python {nuke.frame()}] works as expected.

Reproduced by Support in:
Nuke 13.0v2 - Windows 10, CentOS 7

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

Nuke 8.0v1 - Windows 10, CentOS 7

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