ID 275031 - Error when utilising render_order to stagger outputs when using the nuke.executeBackgroundRenderNuke

Problem summary
Error when utilising render_order to stagger outputs when using the nuke.executeBackgroundRenderNuke 

Customer reported version
nuke.10.0v5

Customer reported platform
n_a_linux

Steps to reproduce

1. Launch Nuke via terminal
2. ensure Switch2 is set to 0
3. ensure output folder is empty, ie "rm -f write*.exr" (though ensure all necessary folder paths are created i.e. /temp/51/render_order_error/)
4, Modify Write 1 to: /temp/51/render_order_error/write1.####.exr (or whatever makes sense on your system)
5. Modify Read1 to: /temp/51/render_order_error/write1.####.exr
6. Modify Write2 to: /temp/51/render_order_error/write2.####.exr
7. Modify Read2 to: /temp/51/render_order_error/write2.####.exr
8. Run the code in the StickyNote in the script, in the script editor
Result: After a moment the following error dialog appears:
"Background render had errors, please view the error console."

And the following appears in the Error Console:

Error in render with process id 44764:

[14:41.22] Warning: Could not find value "PaintSpace" for "int16Lut". It will be appended to the menu list.

[14:41.22] Warning: Could not find value "dnLog" for "logLut". It will be appended to the menu list.

Error in render with process id 44764:

[14:41.22] ERROR: Read1: /temp/51/render_order_error/write1.1001.exr: Read error: No such file or directory

[14:41.22] ERROR: Text2: Can't read font file /usr/share/fonts/msttcore/comic.ttf

[14:41.22] ERROR: Text1: Can't read font file /usr/share/fonts/msttcore/comic.ttf

The background rendered crashed for some reason.

9. Check the output folder to see if it contains "write1.1001.exr"
Result: It does
10. Re-run the nuke.executeBackgroundNuke... command
Result: Renders go through as expected

Repro steps for take 2:

1. ensure Switch2 is set to 1 (attempted workaround)
2. ensure output folder is empty, ie "rm -f write*.exr"
3. run the code in the StickyNode
Result: "write1.1001.exr" is rendered to directory
4. Re-run the nuke.executeBackgroundNuke... command
Result: Renders go through as expected, but write2.1001.exr has a black background 
- the error Switch node has stuck to input 1 for that first frame

Repro steps for take 3:

1. ensure Switch2 is set to 0
2. ensure output folder is empty, ie "rm -f write*.exr"
3. Modify nuke.executeBackgroundNuke function to:
nuke.executeBackgroundNuke(nuke.EXE_PATH, writeNodes, ranges, ["main"], limits=limits, continueOnError=True)
4. Run entire code with modified nuke.executeBackgroundNuke
Result: Renders go through, but write2.1001.exr has a black background 

Workaround
Unknown.

Reproduced by support
Nuke 10.5v4 - OSX 10.11.6 - Windows 7
Nuke 10.0v5 - OSX 10.11.6 
Nuke 10.0v1 - OSX 10.11.6
Nuke 8.0v6 - OSX 10.11.6
Nuke 8.0v1 - OSX 10.11.6


Expected behaviour
render_order to stagger outputs when using the nuke.executeBackgroundRenderNuke 

Actual behaviour
error would occur