ID 593034 - Exported .nk scripts from the timeline sometimes contain incorrect colorspace values

Problem summary
Randomly, .nk scripts exported from the timeline will contain the incorrect colorspace. The colorspace value will not match the set colorspace on the Read node, and may be an invalid colorspace altogether.

The issue occurs quite infrequently until it happens once, then it seems to happen a lot more often.

Customer reported version
Hiero 15.0v1

Customer reported platform
Windows 10

Steps to reproduce

1) Reconfigure the attached batch script for the local device. To do this, change:

SET OCIO=/some/valid/path/to/a/config

2) Change the nuke directory to a valid path on your system to launch hiero.

3) Launch hiero using the batch script.

4) Import several clips.

5) Add the clips to the timeline.

6) In the read node properties of each clip, set the colorspace to the same value e.g. "Output - sRGB".

7) In the timeline, marquee select all the track items and right-click > export.

8) Load the attached export preset by draging the .xml file into the preset window.

9) Switch the "Render With" option to "Single Render Process".

10) Click "Export."

11) Open the file in a text editor and do a find-all for the colorspace e.g.: colorspace "Output - sRGB"

Expected behaviour
The colorspace should be the same as set on the timeline Read nodes.

Actual behaviour
The Read node may sometimes contain the incorrect colorspace. It may take re-exporting multiple times to encounter the issue.

Workaround
Unknown.

Reproduced by support
This bug has been reproduced by our development team in:
Hiero 14.0v7 - Windows 

Earliest version tested
Hiero 14.0v7 - Windows 
- This issue appears to be in all tested versions of the product