ID 349541 - Exception thrown on launch when loading script with Global SmartVector node

Problem summary
When users use the 'Global' option within a SmartVector node, if the user saves the script and re-launches Nuke, the following exception will be called:

​

This issue appears to appears to happen due to the order of operations called when opening Nuke (root does not exist at the moment the node is loaded).

When using Echo mode within the script editor, frame calls are additionally called:
​

​

Customer reported version
nuke.10.5v7

Customer reported platform
centos7

Steps to reproduce

1) Open Nuke, create a SmartVector node

2) Within the SmartVector node, set the dropdown to 'Global'.

3) Save and exit Nuke

4) Open Nuke, load the script

Result: Exception displayed above is thrown in Script Editor and Terminal

Workaround
Unknown.

Reproduced by support

This bug has been reproduced in:
Nuke11.1v3 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.1v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v4 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v1 - Windows 7 - Mac10.12 - CentOS6.9

Earliest version tested
- This feature did not exist before this version

Expected behaviour
Nuke should not throw exceptions when launching script with global SmartVectors

Actual behaviour
Nuke throws exceptions due to global SmartVectors