ID 583315 - Preview render does not start and errors after setting maxTimeSamples to 0 via the RenderSettings node.

Problem summary
Render does not start and produces an error after setting maxTimeSamples to 0 via the RenderSettings node.
 
Customer reported version
Katana 6.5v3
 
Customer reported platform
Rocky 9
 
Steps to reproduce
 
1)  In Katana, open the Hello Pony example project by selecting Help > Example Projects from the menu bar

2) Create a RenderSettings node downstream from the GafferThree node, set the view flag (v) on the RenderSettings node and start a Preview Render. The render completes as expected.

3) Set the edit flag (e) on the RenderSettings node and set the maxTimeSamples parameter to 0
 
4) Attempt to start another render.
 
Expected behaviour
The render will start and complete as expected.
 
Actual behaviour
The render will not start and the following error is produced in the terminal.
 

Error in event handler __on_event_idle() for event type "event_idle": ValueError: Invalid GraphState timing parameters. Utils.EventModule 2024-08-02T12:31:30Traceback (most recent call last):  File "EventModuleUI.py", line 167, in __invokeHandlerDict  File "Util/ClientManager.py", line 862, in __on_event_idle  File "Util/RenderMenu.py", line 150, in __addOrUpdateLocationCallback  File "Util/RenderMenu.py", line 389, in <lambda>  File "Util/RenderMenu.py", line 372, in __ClientManagerCallback  File "Util/RenderMenu.py", line 233, in _DoRenderNode  File "RenderManager/RenderCore.py", line 1250, in StartRender  File "RenderManager/RenderCore.py", line 893, in PrepareRenders  File "Node3D.py", line 574, in GetRenderOp  File "Node3D_geolib3.py", line 158, in ApplyTerminalOpDelegates  File "TerminalOpDelegates/UsdRenderingTerminalOpDelegate.py", line 106, in appendOp  File "Utils.py", line 17, in SetTransactionTimeValuesFromGraphState  File "__init__.py", line 821, in GetSampleTimesFromGraphStateValueError: Invalid GraphState timing parameters.

 
Workaround
Setting maxTimeSamples to 1 will allow a render to start as expected.
 
Reproduced by support
This bug has been reproduced in:
Katana 7.0v3 - Windows 11 / Rocky 9
Katana 7.0v2 - Windows 11 / Rocky 9
Katana 7.0v1 - Windows 11 / Rocky 9
Katana 6.5v3 - Windows 11 / Rocky 9
Katana 6.5v2 - Windows 11 / Rocky 9
Katana 6.5v1 - Windows 11 / Rocky 9
 
Unable to reproduce bug in:
Katana 6.0v4 - Windows 11 / CentOS 7
 
Earliest version tested
Katana 6.0v4 - This issue doesn't appear in this version and has regressed.