Error Message. Object Reference not set to Instance

[Majordad101]

Describe the bug The error message Object Reference not set to an instance of an object, has occurred when running, both logged on and logged out

To Reproduce Steps to reproduce the behavior:

1. Load the Local Dyn from the Orkestra dialog.
2. Run the definition.
3. Immediately after run the error message pops-up
4. See error

Expected behavior The definition would run normally as per Dynamo and Player, outside of Orkestra,

Observed behavior Cleared OK and the definition completed. Appeared to complete the definition correctly.

Screenshots

Desktop (please complete the following information):

• OS: Win10
• Revit Version : 20.2.11.3, 20200206_0915(x64), 2020.2.1
• Dynamo Version : Dynamo Core 2.3.0.5885, Dynamo Revit 2.3.0.7661
  • Orkestra Version :

In Which context did it happen (please select from the following list) : Orkestra Revit Addin

Additional context

[MostafaElAyoubi]

Hi @Majordad101 , thanks for reporting this ! I am working on reproducing the issue.

• Did you open the definition from the Orkestra Revit Addin? Or from the Orkestra Dynamo View Extension?
• Does this happen consistantly?

[Majordad101]

It was from the Orkestra Revit Addin, the Orkestra Dynamo View Extension in different incidents. I checked the package versions were updated and the definitions reloaded in Revit/Dynamo not through Orkestra, to ensure these were removed from the cause. It happened and in some cases stopped after being run. I assumed it was the packages loaded were loaded.
I will check the flow of setup, settings and running the definitions from the Local, Cloud and Ribbon.

[MostafaElAyoubi]

Hi @Majordad101 , thank you very much for the extra information. The issue is now identified and is linked to this issue as well #9 . I will publish a Hotfix today.

[MostafaElAyoubi]

Fixed in v.0.1.8 Please let me know wen you get a chance to try it!