Orkestra not setting the package path

[JesseWayneJames]

Describe the bug Users scripts aren't loading packages and when checking their package path its not being set.

To Reproduce Just using the scripts as normal.

Observed behavior When orkestra runs its not setting the package path and getting the packages for the user.

Desktop (please complete the following information):

• OS: Windows 10
• Revit Version : 2019-20-21-22 (for what I've witnessed)
• Dynamo Version : all dynamo versions
  • Orkestra Version : It occurs with me and im running 1.6.1 and the others are using 1.4.1

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

[MostafaElAyoubi]

Hi @JesseWayneJames ! Thank you for letting us now. Is this specific to a workspace or is it happening across all hubs/workspaces?

[JesseWayneJames]

I'm unsure, however from both mine and the other user the error was happening from the same workspace

[MostafaElAyoubi]

Okay. We're going to run tests on that. In the meantime, can you try re uploading the whole set of packages to the workspace settings and see if it makes a difference?

[JesseWayneJames]

Hi Mostafa this error is now occurring in other workspaces. Before it only occurred in WB Dynamo but now its occurring in SYD (haven't tested other folders like MEL). see the image below to see the folders i'm referring to.

[Dre-Tas]

@MostafaElAyoubi sorry for being pushy but this really needs to be fixed ASAP!! Our people in the office can't get the scripts to work and Orkestra (and us as a consequence) is losing credibility. At this rate we won't have any more Orkestra users very quickly.

[JesseWayneJames]

Creating a new works space in the hub and reuploading the packages didn't fix it.

[JesseWayneJames]

However when i right click "open in dynamo" from revit, it opens dynamo and the script with the correct path. Opening with associated packages from dynamo already being open doesn't load the path.

[MostafaElAyoubi]

hi @Dre-Tas and @JesseWayneJames ! Thank you for the updates. We're absolutely willing to identify and fix this issue quickly, we're having trouble reproducing so I'll get in touch so we can set a call and troubleshoot this together. It does look like an issue that we looked at together and fixed by reuploading the packages.

[Dre-Tas]

It is the same issue (if I'm not mistaken, @JesseWayneJames ) but it just keeps happening. We can't keep re-uploading packages every time. Also, I think now that workaround isn't working anymore....

[MostafaElAyoubi]

Implemented in 1.7.1