ID 390816 - Reloading a LiveGroup that contains a cloned node results in an error

Problem summary

When reloading a LiveGroup that contains a cloned node, Nuke returns an error similar to the following: 

"LiveGroup1: Can't clone LiveGroup1.Grade1 because LiveGroup1 is published.

Customer reported version
Nuke 11.3v3

Customer reported platform
Windows 10

Steps to reproduce

1) Make a new script that contains a cloned node.

2) You should also ensure that this script contains an Output node.

3) Open Project Settings (Edit > Project Settings) and check the "is live group" options in the Root tab.

4) Save the script.

5) Open a new script and create a LiveGroup node.

6) Use the file browser on the LiveGroup node to load in your previously created script.

7) Click the Reload button on the LiveGroup node and an error, similar to the following, should appear:

Expected behaviour
The LiveGroup should be reloaded.

Actual behaviour
The LiveGroup script is not properly reloaded and an error is returned, like so:

Workaround
You can workaround this issue by replacing the current LiveGroup node with a new one every time you reload it.

Reproduced by support

This bug has been reproduced in:
Nuke 11.3v3 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)

Nuke 11.3v1 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra) - Regression

Unable to reproduce bug in:
Nuke 11.2v5 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)

Earliest version tested
Nuke 11.2v5
- This issue no longer appears in this version and has regressed