ID 226712 - NukeStudio doesn't update localised frames from automatic background renders

Problem summary
NukeStudio doesn't update localised frames from automatic background renders. Instead it reads in the most recently localised footage until the auto-localisation updates and gets the rendered footage, whe the project root is in the auto-localisation location.

Customer reported version
nuke.10.0v3

Steps toreproduce

1) Open NukeStudio 10

2) In Edit > Preferences... set the auto-localize from path to a network drive, and set background renders to start background renders on Comp save.

3) Close and reopen NukeStudio to apply those changes.

4) Import some footage (I tested with a 10 frame .dpx sequence)

5) Drag the footage onto a new sequence

6) Right click the clip in the timeline, then Effects > Create Comp

7) Set the project root to a location on the network drive you set in step 2.

8) Double click the comp

9) Edit the comp to be visibly different, such as a ColorCorrect

10) Save the comp, this will now start rendering the comp. Once the comp has rendered, it will update in the project timeline.

11) Edit the comp again and save again, this time the comp will render, but won't be updated in the timeline until the auto-localisation update checks in. 

Clearing the playback cache does not help, and looking at the localised files in the directory shows they are not updated until auto-localisation kicks in.

Reproduced by support
This has been reproduced in:

NukeStudio 10.0v3 - Windows 10 - CentOS 6.8

NukeStudio 10.0v1 - Windows 10

This was not an issue in:

NukeStudio 9.0v9 - Windows 10

NukeStudio 9.0v8 - Windows 10 - CentOS 6.8

Expected behaviour
For the rendered track to appear in the timeline

Actual behaviour
The last localised clip is used instead